jschoubben
93a1231e00
Skills take the hq- prefix: they are HQ process workflows, not mesh workflows, and HQ is company-scoped now. hq-new-research, hq-graduate, hq-new-issue, hq-diagnose, hq-amend-design, hq-handoff, hq-sync-constitution, hq-status. Forward-looking prose becomes Novox Mesh or simply the mesh — the root README, AGENTS.md, the 00-META README, the mission's module example, and one to-be document that addressed 'someone working on HAL'. Three categories deliberately keep HAL, per ADR 0027: The monorepo is still called hal on the forge. repos.md, every code: field and every located-in: field name a repository that exists under that name, and renaming them in prose would make them false. The as-is layer and the research that measured it describe the system that runs, and that system is called HAL. 124 modules, 9 daemons, a dead containerised node — those are observations, not intentions. Records 0001-0026 are immutable. A record says what was decided when it was decided, and no record is edited for a name. Also repoints ADR 0022's link at the renamed skill — a path fix, which the immutability rule permits, not a change of meaning.
33 lines
1.4 KiB
Markdown
33 lines
1.4 KiB
Markdown
---
|
|
name: hq-handoff
|
|
description: Use when an 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".
|
|
---
|
|
|
|
# hq-handoff
|
|
|
|
Hands a settled design to a code repository. **Authoritative playbook:**
|
|
[`00-META/process/04-build-handoff.md`](../../../00-META/process/04-build-handoff.md).
|
|
|
|
## Steps
|
|
|
|
1. **Confirm it is settled.** `status: designed`, and every claim traceable to a record in
|
|
`02-DECISIONS/`. An open question in the text is a reason to run `hq-new-research`, not to build
|
|
around it.
|
|
2. **Name the owner.** Set `code:` from
|
|
[`00-META/repos.md`](../../../00-META/repos.md). If the repository does not exist yet,
|
|
add it to `repos.md` in the same change.
|
|
3. **Read the as-is counterpart.** What is being replaced must be written down in
|
|
`03-DESIGN/00-as-is/` before it is changed. Building against an undocumented as-is is how
|
|
shipped behaviour gets lost.
|
|
4. **Flip the status** to `in-progress`, `updated:` today.
|
|
5. Build in the code repository. HQ never carries implementation.
|
|
6. On completion, run `hq-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.
|