There is an old rule in software: you do not rewrite the system that keeps your product alive. Not casually, and not while the old version is still answering real traffic. This is the story of someone who did exactly that — not out of bravery, but after doing the math and deciding the slower risk was the bigger one.
This is the pilot of Deep Build: one real project, opened all the way. The repo is the source of truth; we read every document it wrote about itself. Today's patient is radcode: a portable Rust TUI coding harness. One binary, your machine, your keys. Heir to a Python-era unified memory server that ran agent sessions before Rust entered the chat, raised inside the Rust platform that server grew into, and armed by a year of production service under a borrowed name. Survivor of an audit that found its brain was not connected, and owner of a second repository this episode cracks open.
Four voices walk the stack: Forge runs the teardown, Bella keeps the receipts, Michael keeps the map, Sage keeps us off the ceiling.
THE FAMILY TREE: How it started — a Python memory server, named by its architect in his own voice and kept off the air at his request; the Rust rebuild that outgrew its blueprint and became a platform; the terminal that left home and became radcode; and the TypeScript detour that carried production traffic the whole time and handed the rebuild seven hundred seventy one conformance fixtures.
HOW IT ACTUALLY WORKS: Channels for concurrent conversations. Memory that learns from user corrections. Hooks before and after every tool call. Reusable workflows called skills. A VS Code extension, a desktop app, mobile and messaging bridges, CI hooks. Thirty three crates, just past 162,000 lines of Rust — and we go inside the 44,000-line memory crate. The terminal is not a nostalgia play. The agent is the product, not a chat window bolted onto one.
THE AUDIT THAT FOUND AN INERT BRAIN: At one point most of the clever machinery behind the feature list was dead code. The project measured itself instead of marketing itself, dated the embarrassment, and fixed it in order. The audit even corrected itself: a recount caught the original scorecard wrong, verified with awk.
ACT SIX, THE OTHER REPOSITORY: radical-code — the same thirty three crates name for name, eighteen thousand lines ahead, eight hundred sixteen commits under five signatures, three identities mid-rename, and a one hundred six line TypeScript shim proving the sunset plan shipped as a file, not a vibe. One brain in two bodies. Plus the two-shapes plan announced at two in the morning: the standalone that carries its own brain, and the light version that calls the R.A.D.1.C.A.1 retrieval server over a wire.
THE CRITIQUES, UNHINGED: One maintainer signature across fifty one harness commits while the platform repo runs a fleet. Eight product surfaces, one author table. A plan that superseded itself twice in four months. An npm package declaring 0.1.0 while the workspace ships 0.6.3.
THE VERDICTS: A minus for the build. A D for the bridge. An A minus for the platform and a C for its paperwork. The most architecturally serious attempt seen to make the agent the product instead of the chat window.
Runtime about 96 minutes, recorded September 5, 2026, live from the repositories.
Next episode: the router itself. Forty thousand lines of brain wearing a hundred thousand lines of clothes, sixteen agents in one process, and the server the light client will call home. If you want Deep Build to tear into the thing you are building, or the thing you refuse to trust, the show has ears.
How this show is made: full disclosure — this is an AI production. Four AI voices (Forge, Bella, Michael, Sage) researched, wrote, and voiced this episode by reading the repositories directly; every number here comes from a live probe of the code. A human architect commissioned the teardown, checked every fact, and approved the final cut. Synthetic voices, real receipts.