Files
jschoubben 93a1231e00 Retire the HAL name where it points forward
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.
2026-08-23 21:26:09 +02:00

2.0 KiB

name, description
name description
hq-graduate Use when a research effort in HQ concludes and becomes design, or when a design must change. Triggers on "graduate this research", "this is decided", "write the ADR", "close the effort", "the design changed".

hq-graduate

Closes a research effort into a decision and a design, or amends an existing design. Authoritative playbook: 00-META/process/02-graduation.md — read it; this skill adds only the scaffolding.

Steps

  1. Check against GENESIS — mission.md, context.md, effect.md. If the conclusion conflicts, say which is wrong, in writing, before proceeding.
  2. Write the decision record in 02-DECISIONS/, next free number, frontmatter per 02-DECISIONS/README.md. reconstructed: false — this one is being taken, not recovered. Record the rejected options.
  3. Write the design under 03-DESIGN/01-to-be/ with layer: to-be, status: designed, empty code:, today's updated:, and decisions: pointing at the record.
  4. Close the effort — the research 00-overview.md gets status: graduated and became: pointing at both.

Amending an existing design

A design changes only through a decision. Write the record first; if it reverses an earlier one, set that record's status: superseded and superseded-by: — never edit its text. Then edit the design and set updated:.

When something ships

Write or update the matching 03-DESIGN/00-as-is/ document so it describes what now runs, including anything that shipped differently from the intent. Set the to-be document's status: implemented and its code:. The to-be document does not move — both stand.

status: implemented must be defensible from the owning repository's main branch. If it cannot be checked, it is in-progress.

Do not

  • Do not move a to-be document into 00-as-is/.
  • Do not edit an as-is document to describe an intention.
  • Do not change a decision record's meaning. Supersede it.