jschoubben
3f6d939930
papa-hq has no ledger. Its root is AGENTS.md, CLAUDE.md, README.md, every decision is a numbered record, and its graduation playbook has no path for an unrecorded decision. hal-hq now matches. The ledger's 41 entries classified as: 10 restating a record, 11 restating design docs, 15 describing how this repository works with the reasoning sitting in a README rather than anywhere citable, 3 small rules with no home, 2 superseded stubs. Mostly a copy — and a hand-maintained index, the exact pattern ADR 0022 had just rejected for the decision index on the grounds it drifted after one addition. Keeping one copy of that while removing another is not a position. It also collided by name with 02-DECISIONS/ in any directory listing. Nothing was dropped. Records 0019-0025 give the repository decisions the reasoning they never had: HQ is its own repository and is public, design has two layers, work moves through playbooks, status lives in frontmatter, issues have a front door, the numbering is the flow, HQ is the source of the constitution. 0026 records the ledger's own removal. The three orphan rules went to how-we-build, where a rule is enforced and keeps the incident that earned it — the package rule was genuinely unwritten anywhere. Two lab decisions stated only in the ledger went into the lab design. "Deliberately not decided" went to the research effort and design document each question actually belongs to. The chronological view the ledger provided is now generated from record frontmatter, which is what it was for. The cost, stated in 0026 rather than glossed: a record is more work than a table row, so the risk is a small decision going unrecorded because nobody wanted to write a document. how-we-build takes rules cheaply, which is the mitigation, not a solution.
39 lines
2.0 KiB
Markdown
39 lines
2.0 KiB
Markdown
---
|
|
name: hal-sync-constitution
|
|
description: Use after changing a rule in hal-hq's 00-META/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-META/process/05-constitution-sync.md`](../../../00-META/process/05-constitution-sync.md).
|
|
|
|
## What this is
|
|
|
|
[`00-META/how-we-build.md`](../../../00-META/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
|
|
|
|
1. Confirm the source change is recorded as a decision. A rule the mesh enforces is
|
|
architecturally significant; if there is no record, run `hal-graduate` first.
|
|
2. 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.
|
|
3. Publish it to the knowledge base under the constitution slug, replacing the body.
|
|
4. **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.
|
|
5. Note the sync in the decision record's Consequences.
|
|
|
|
## 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.
|