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.
1.5 KiB
1.5 KiB
name, description
| name | description |
|---|---|
| hq-new-research | Use when starting a new research effort in HQ — an idea, technology or approach worth investigating before it is committed to design. Triggers on "research X", "investigate X", "spike X", "should we use X", "is X worth doing". |
hq-new-research
Scaffolds a new research effort. Authoritative playbook:
00-META/process/01-research.md — read it;
this skill only does the mechanical setup.
Steps
-
Find the next free number: list
01-RESEARCH/NNN-*, take the highest plus one, zero-padded to three digits. -
Create
01-RESEARCH/NNN-descriptive-name/(kebab-case from the topic). -
Create
00-overview.mdin it with exactly this frontmatter, then a prose summary of what is being investigated, why, and what it touches:--- status: active initiated: YYYY-MM-DD touches: [] became: [] --- -
Do the research in further documents in the same folder. Keep the summary current.
Do not
- Do not restate the status in prose. It lives in frontmatter, in one place.
- Do not fill
became:while the effort is open —hq-graduatesets it at closure. - Do not skip or reuse a sequence number.
- Do not write into
03-DESIGNfrom an open effort. - Do not name the mesh being observed. Evidence is required; identification is forbidden.
Closing
An effort never just stops. It closes through hq-graduate as graduated or abandoned,
always with became: pointing at what it turned into. Nothing is deleted.