Room 05 · Finished Work
Completed work lands, sorted by project.
The destination is a finished, verified deliverable — code most often, but also documentation, research, configuration, or a decision — with the intent-to-evidence thread still attached.
The end of the line
When the merge system pushes an exact, gate-verified candidate, the work is done — and it lands here, sorted by project. Room 05 is deliberately the quietest room in the factory: nothing is decided here, because every decision already happened upstream.
What makes it interesting is what stays attached. The deliverable — the merged code, the published document, the changed configuration — keeps its whole thread: the note that captured the intent, the plan and Beads that shaped it, the runs that built it, the gate evidence that proved it, and the cost it took. The deliverable changes; the reason the work began remains findable.
Not only code
The factory’s output is verified deliverables, not merges. Most work ends as code on a target branch, but a note can just as legitimately end as documentation, research, analysis, data, an operational change, or a recorded decision. The contract is the same either way: the work reaches a completed outcome or becomes explicitly blocked with the reason on the record — it never simply disappears.
From here the record flows outward: the work ledger and run statistics count it, model economics prices it, and the change log tells the story of the factory that produced it.