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.
2.0 KiB
2.0 KiB
name, description
| name | description |
|---|---|
| hal-sync-constitution | Use after changing a rule in hal-hq's 00-GENESIS/how-we-build.md, to publish the derived constitution page the mesh injects into design sessions. Triggers on "sync the constitution", "publish the rules", "I changed how-we-build", "update the governed page". |
hal-sync-constitution
Publishes the derived constitution from its source. Authoritative playbook:
00-GENESIS/process/05-constitution-sync.md.
What this is
00-GENESIS/how-we-build.md is the source. The
knowledge base carries a derived page that the mesh injects into every eligible design
session, and against which a check phase can block work.
Two texts stating the same rules drift, and the enforced copy wins by default — so the reasoned copy quietly stops being true. This skill is the mechanism that prevents that, and it is how the claim "HQ is the source" is checked.
Steps
- Confirm the source change is recorded as a decision. A rule the mesh enforces is
architecturally significant; if there is no record, run
hal-graduatefirst. - Derive the page: the rules without the reasoning. Section numbering is stable — the orchestrator and the review fragments cite sections by number, so never renumber to tidy.
- Publish it to the knowledge base under the constitution slug, replacing the body.
- Read it back and verify the change is present. A publish that reported success and did nothing is exactly the failure class this repository exists to name — do not skip this.
- Note the sync in the decision's ledger line.
Do not
- Never edit the derived page directly. An edit there survives until the next sync and then vanishes, taking its reasoning with it.
- Do not relax a rule in the derived page. Overrides may only tighten.
- Do not report the sync as done without the read-back. If it could not be performed, say so — an unsynced rule is a rule the mesh does not enforce, whatever the source says.