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.4 KiB
1.4 KiB
name, description
| name | description |
|---|---|
| hal-handoff | Use when a hal-hq design is settled and implementation is about to start in a code repository. Triggers on "start building this", "hand this off", "ready to implement", "who owns this now". |
hal-handoff
Hands a settled design to a code repository. Authoritative playbook:
00-GENESIS/process/04-build-handoff.md.
Steps
- Confirm it is settled.
status: designed, and every claim traceable to a record inadr/. An open question in the text is a reason to runhal-new-research, not to build around it. - Name the owner. Set
code:from00-GENESIS/repos.md. If the repository does not exist yet, add it torepos.mdin the same change. - Read the as-is counterpart. What is being replaced must be written down in
02-DESIGN/00-as-is/before it is changed. Building against an undocumented as-is is how shipped behaviour gets lost. - Flip the status to
in-progress,updated:today. - Build in the code repository. hal-hq never carries implementation.
- On completion, run
hal-graduate's "when something ships" section.
Non-negotiable
- Every merge is a human checkpoint, without exception.
- Never open a pull request unprompted. A permissions list saying it is allowed is not a request.
- Work in an isolated worktree, never a shared checkout.
- Never push to the main branch.