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.
2.4 KiB
2.4 KiB
name, description
| name | description |
|---|---|
| hq-status | Use when you need a cross-cutting view of where HQ stands — research state, design implementation state, open issues, or the decision-record index. Triggers on "what's the status", "show the ADR index", "where do things stand", "what's in progress", "what's open". |
hq-status
Generates a cross-cutting view from frontmatter. This is a read-and-render skill, not a workflow — HQ has no central status file by design (decision 35). Every view is generated on demand and never written back to disk.
What to read
| Section | Files | Frontmatter |
|---|---|---|
| Research | 01-RESEARCH/NNN-*/00-overview.md |
status (active / graduated / abandoned), initiated, touches, became |
| Design | 03-DESIGN/**/*.md (not READMEs) |
layer (as-is / to-be), status (designed / in-progress / implemented / abandoned), code, updated, decisions |
| Decisions | 02-DECISIONS/NNNN-*.md |
status (proposed / accepted / superseded), date, deciders, reconstructed, superseded-by, extends |
| Issues | 04-ISSUES/NNN-*/00-report.md |
status (open / diagnosing / located / resolved / wontfix), opened, located-in, fixed-by, amended-design |
Steps
- Read the frontmatter block from every file above — a grep across each tree is enough, no need to load bodies.
- Render what was asked as Markdown tables. Group and sort sensibly. The ADR index is one of these views: records ordered by number, with title, date and status, and reconstructed ones marked.
- Flag anything inconsistent at the end, as flags — do not silently correct the render:
- a
graduatedorabandonedeffort with an emptybecame: - an
implementeddesign with an emptycode: - a
supersededrecord with nosuperseded-by: - an
openordiagnosingissue with no activity - a to-be design whose
decisions:points at a record that does not exist - an as-is design whose claims are older than its
updated:date suggests
- a
Do not
- Do not write a status file. Central status files are explicitly rejected. The view is always generated, always ephemeral. This includes the ADR index — the hand-written one had already drifted after a single addition, which is why it was removed.
- Do not infer status from prose. Trust only the frontmatter; if it is wrong, flag it.