04 — Build order

Summary

Fixtures, read path, write path, mandates and grants, the three-session demo — with one rule: the read path ships first, because it has no policy content, it is the half a genuinely public registry shares unchanged, and every later phase reports through it. Each phase is also an experiment with a stated question: where does a literal reader trip, how long does an agent identity actually live, is the mandate vocabulary usable before a broker enforces it, and where does the human actually remain in the loop.

Key concepts

• Fresh-session acceptance tests — the documentation standard promoted to the definition of done
• One capability, deeply — repo.pull-request.create drags in constraint semantics on day one — the point
• Phase 0 upgraded by C3 — the fixture class, named and bounded, before any key is generated

Key ideas

• Phase 1 has no policy content, which is why it goes first.
• The processor logs every decision publicly, keeping the trust boundary auditable.
• Phase 4's write-up names every step that needed a human — the honest residue is the publishable finding.

Read the document