Working state — a note taken while the work happens, not a specification. The system as it is meant to be is in Architecture.

State

This is not law. Everything in the other tracks — Guide, Library, Shop, Architecture, Reference — describes the system as it is meant to be, in the present tense, and is corrected when it goes wrong. This track is the opposite kind of writing: notes taken while the work is happening. Plans are temporary by definition. A page here can be half-decided, out of date within the week, or contradicted by the page next to it. That is the point — it is the state of the work, not a description of the system.

Read it when you want to know what is being done and why, what was already tried, and what was decided and does not need re-arguing. Read Architecture when you want to know what the system is.

What is here

Everything below is rendered straight out of the repository’s plans/ directory. Nothing on this page or in the site’s templates names an individual plan: a lane that starts a plan, retires one, or moves one into the archive changes what the site shows without touching the site.

Live

audit/

• docs-vs-system audit — 2026-08-07Base: dev @ a1057e153c6060a9fb19a8f6d3682d94fe5b0aa9. All 64 pages of docs/

• CarriedPer work-proposal.md §5: items carried out of the retired plans, plus defects
• The compiler, after the spine — the opportunity mapWritten 2026-07-27 for planning the compiler pass that begins when the finalization
• A standing performance measurement suiteStatus: DESIGN + partial prototype. Written 2026-08-05 against c13443301.
• The memory arc — two numbers, one residency policyJohn's rulings of 2026-08-07, which are law for this design, plus the
• How this work goesWritten for whoever picks this up — including a future me. The durable, project-owned
• Programs — shipping them, reloading them, debugging themthe execution plan and the remaining seven rulings were answered the same day in

proposal-notes/

• B3 — what the builder live-set diet cut, and where the floor isLane arc/builder-diet, base dev @ 8791b2c91, 2026-08-05.
• Why a builder actor reaches 128 MB, and why 15 of them cost gigabytesInvestigation notes, 2026-08-05, worktree agitated-dubinsky-a3501e @ c13443301.
• Can the compiler be broken apart? — seam investigationRepo: /Users/johnalanbrook/Documents/work/cell/.claude/worktrees/agitated-dubinsky-a3501e
• Deletion inventory — plans/programs.md R1–R9Worktree: /Users/johnalanbrook/Documents/work/cell/.claude/worktrees/agitated-dubinsky-a3501e
• R6 one-pool: exactly what is left, measured from D2too large, REPORT precisely what it needs" half of that brief, and it is a
• The R5 "stone drop" — there was no dropThe compiler-emitted module freeze works. What looked for most of a session
• Cross-actor shared-state audit — ƿit runtime CWorktree: /Users/johnalanbrook/Documents/work/cell/.claude/worktrees/agitated-dubinsky-a3501e
• C3 — the send path, measuredC3 closes with evidence and no scheduler change.

• Rejected / narrowed findings — verified as non-defects at the recorded commitJournal, harvested from the retired defect inventory (2026-07-24). These are claims that a
• Tonight (2026-08-07): interrogation → tight cleanup → playdate on hardwareJohn heavily in the loop for all of it. The culmination: the playdate build
• Work proposal — the programs arc, with its measurement floor and deletionsInputs: plans/programs.md rev 2 (the rulings), plans/measurement-suite.md