The Architect's Builders Review: pi-mega-compact EP1.

pi-mega-compact is a local context compression extension for the pi coding agent. It sits between the developer and the model and manages the context window — compressing, deduplicating, and recalling conversation history so that long coding sessions don't degrade or crash when context fills up. It's fully local. Zero telemetry. No phone-home. BSD-3-Clause licensed. Everything runs on your machine, in your SQLite databases, with your own embeddings. No data ever leaves the host.

Why are we talking about it? Because it may be the most sophisticated piece of context management infrastructure in the open-source coding agent space, and almost nobody knows it exists. While the AI industry spent 2026 arguing about which model has the largest context window — one million tokens, one-point-zero-five million, one-point-zero-four-eight million — pi-mega-compact was solving the actual problem that nobody was talking about: what happens when that context fills up with redundant, stale, or corrupted data. A million-token window doesn't help you if ninety percent of it is duplicate file reads and stale summaries from three hours ago. The context isn't overflowing — it's unhealthy. And pi-mega-compact is the only open-source tool that diagnoses and treats that condition.

The architecture is dense. A three-stage compaction pipeline called Trident — supersede, collapse, cluster — that replaced the naive single-pass summarization used by every other coding agent. A three-layer semantic deduplication stack: exact hash for byte-identical content, MinHash with LSH banding for near-duplicates at scale, and cosine similarity over trigram embeddings for fuzzy semantic overlap. A RAPTOR memory hierarchy — Recursive Abstractive Processing for Tree-Organized Retrieval — that builds a hierarchical summary tree over your entire conversation history and serves multi-level recall with leaf expansion and MMR diversity re-ranking. Per-turn tracking with a contract-first TurnStore interface that enforces provenance on every write. Cross-repo recall via PGlite HNSW vector search. An auto-categorizing wiki that clusters conversation topics with k-means++ and TF-IDF labeling. A React dashboard with eleven tabs, SSE real-time updates, and a gamified achievement system. Fifty-two sprints of shipped engineering. Seven hundred and forty-five tests. All in twenty-one days from first commit.

But this episode is also the debut of a new format for ArchitectIT. We are not reviewing a project we found on GitHub. We are reviewing code that was architected through the AI-assisted development workflow we cover on this show. The human designs the sprint plan. The AI implements it. Gate scripts enforce scope compliance, evidence verification, and test coverage. The human reviews and releases. The panel — Alex, Dana, and Morgan — is not pretending to be a neutral observer. We are examining the output of the development pattern we believe represents the future of software engineering. The reviewer is part of the pipeline that built the thing being reviewed. That recursion is the point.

This is the "Then" — the baseline recording from July 31, 2026, at version 0.11.13. The gap analysis is honest: the RAG suite exists only as spec, provider cache visibility is missing, dedup thresholds need empirical validation, and the dashboard's eleven tabs may be front-running actual operational needs. These gaps become the measuring stick for episode two.