jschoubben
702efca6bb
HQ held only the to-be. Every reader had to already know the system the decisions were about, and an as-is claim had nowhere to live except inside an intention. Adds 02-DESIGN/00-as-is — eleven documents written from the implementation and the operational record, not from intent, including the parts nobody would choose again. The two existing designs move under 01-to-be. Layers are declared in frontmatter and never mix: a design that ships does not move, its as-is counterpart is written, and both stand. Back-fills adr/0001-0014 for decisions taken in implementation and never recorded — the broker, the module abstraction, the mesh database, managed files, provisioning, migrations, the workspace removal, failing loudly, the constitution, application placement, linking, the employee model, the artifact, the three silos. Each marked reconstructed, dated from the history, and citing the evidence it was recovered from. The two existing records renumber to 0015 and 0016 so the ledger runs oldest first; 0017 extends 0015 to modules outside the core, principle only — the domain list is deliberately not invented here. how-we-build.md becomes the source of the mesh constitution, with a sync playbook, so the enforced copy stops being the only one that is true. Process becomes explicit: five playbooks, eight thin skills that defer to them, a repository map, and AGENTS.md with CLAUDE.md as its include. The five Observations become 04-ISSUES 001-005 where they can be owned and closed. 006 is new and uncomfortable: HQ is not indexed into the knowledge base. That claim is what decision 27 rests on, it was never checked, and the README now says so instead of repeating it. Also corrects the ADR index into something generated, the "02-DESIGN is empty" claim, the VISION.md pointer that did not survive the repo split, and a note asserting the symlink rule was contradicted — it was a misreading; the rule forbids hand-made links, the installer links by design.
1.8 KiB
1.8 KiB
Playbook 05 — Constitution sync
Trigger. how-we-build.md changed a rule that the mesh enforces at
runtime.
Who runs it. Whoever made the change.
Why this playbook exists
The mesh injects a constitution into every eligible design meeting; agents check their output
against it and a constitution-check phase can block a meeting. That text is derived.
how-we-build.md is the source.
Two texts stating the same rules will drift, and the enforced copy winning by default means the reasoned copy quietly stops being true. This playbook is the mechanism that stops that — and, per the repository's own rule, it is how the rule "HQ is the source" is checked.
Steps
- Edit
how-we-build.md. Each rule keeps the reasoning that earned it; the derived page carries the rule alone. - Record the change as a decision — a rule the mesh enforces is architecturally significant. Playbook 02.
- Publish the derived page to the knowledge base under the constitution slug, replacing its body. Keep the section numbering stable: the meeting orchestrator and the review fragments cite sections by number.
- Verify the derived page reads back with the change present. A publish that reported success and did nothing is exactly the failure class this repository exists to name.
- Note the sync in the ledger line for the decision.
Rules
- Never edit the derived page directly. An edit there survives until the next sync and then vanishes, taking its reasoning with it.
- The derived page may only be tightened by per-team override pages, never relaxed.
- If the sync cannot be performed, say so in the ledger line. An unsynced rule is a rule the
mesh does not enforce, whatever
how-we-build.mdsays.