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.
This commit is contained in:
@@ -1,9 +1,9 @@
|
||||
---
|
||||
name: hal-amend-design
|
||||
name: hq-amend-design
|
||||
description: Use when an HQ design document must change, or when an as-is document is found to be wrong about what the mesh actually does. Triggers on "the design changed", "that's not how it works any more", "update the as-is", "this shipped differently".
|
||||
---
|
||||
|
||||
# hal-amend-design
|
||||
# hq-amend-design
|
||||
|
||||
Changes a design document. **Authoritative playbook:**
|
||||
[`00-META/process/02-graduation.md`](../../../00-META/process/02-graduation.md).
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
name: hal-diagnose
|
||||
name: hq-diagnose
|
||||
description: Use when investigating an open HQ issue — finding which component owns a symptom, and why. Triggers on "diagnose issue N", "where does this live", "who owns this bug", "why does this happen".
|
||||
---
|
||||
|
||||
# hal-diagnose
|
||||
# hq-diagnose
|
||||
|
||||
Investigates an open issue to the point where its owner is known. **Authoritative playbook:**
|
||||
[`00-META/process/03-issues.md`](../../../00-META/process/03-issues.md).
|
||||
@@ -30,7 +30,7 @@ result is not "nothing to learn" — it is the reason the next person repeats th
|
||||
3. When the owner is known, set `status: located` and fill `located-in:` with repositories or
|
||||
modules from [`00-META/repos.md`](../../../00-META/repos.md).
|
||||
4. On resolution: `status: resolved`, fill `fixed-by:`. If the root cause was a design gap, run
|
||||
`hal-graduate` for the amendment and fill `amended-design:`.
|
||||
`hq-graduate` for the amendment and fill `amended-design:`.
|
||||
|
||||
## Rules
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
name: hal-graduate
|
||||
name: hq-graduate
|
||||
description: 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".
|
||||
---
|
||||
|
||||
# hal-graduate
|
||||
# hq-graduate
|
||||
|
||||
Closes a research effort into a decision and a design, or amends an existing design.
|
||||
**Authoritative playbook:**
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
name: hal-handoff
|
||||
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".
|
||||
---
|
||||
|
||||
# hal-handoff
|
||||
# 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).
|
||||
@@ -11,7 +11,7 @@ Hands a settled design to a code repository. **Authoritative playbook:**
|
||||
## 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 `hal-new-research`, not to build
|
||||
`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,
|
||||
@@ -21,7 +21,7 @@ Hands a settled design to a code repository. **Authoritative playbook:**
|
||||
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 `hal-graduate`'s "when something ships" section.
|
||||
6. On completion, run `hq-graduate`'s "when something ships" section.
|
||||
|
||||
## Non-negotiable
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
name: hal-new-issue
|
||||
description: Use when something is wrong with the HAL mesh at the level of design or governance — a rule enforced by nothing, a stated behaviour that does not happen, a failure the design lets pass silently. Triggers on "this is broken", "open an issue", "that rule isn't enforced", "this reports success and does nothing".
|
||||
name: hq-new-issue
|
||||
description: Use when something is wrong with the mesh at the level of design or governance — a rule enforced by nothing, a stated behaviour that does not happen, a failure the design lets pass silently. Triggers on "this is broken", "open an issue", "that rule isn't enforced", "this reports success and does nothing".
|
||||
---
|
||||
|
||||
# hal-new-issue
|
||||
# hq-new-issue
|
||||
|
||||
Opens a numbered issue. **Authoritative playbook:**
|
||||
[`00-META/process/03-issues.md`](../../../00-META/process/03-issues.md).
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
name: hal-new-research
|
||||
name: hq-new-research
|
||||
description: 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".
|
||||
---
|
||||
|
||||
# hal-new-research
|
||||
# hq-new-research
|
||||
|
||||
Scaffolds a new research effort. **Authoritative playbook:**
|
||||
[`00-META/process/01-research.md`](../../../00-META/process/01-research.md) — read it;
|
||||
@@ -31,12 +31,12 @@ this skill only does the mechanical setup.
|
||||
## 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 — `hal-graduate` sets it at closure.
|
||||
- Do not fill `became:` while the effort is open — `hq-graduate` sets it at closure.
|
||||
- Do not skip or reuse a sequence number.
|
||||
- Do not write into `03-DESIGN` from 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 `hal-graduate` as `graduated` or `abandoned`,
|
||||
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.
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
name: hal-status
|
||||
name: hq-status
|
||||
description: 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".
|
||||
---
|
||||
|
||||
# hal-status
|
||||
# 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
|
||||
+3
-3
@@ -1,9 +1,9 @@
|
||||
---
|
||||
name: hal-sync-constitution
|
||||
name: hq-sync-constitution
|
||||
description: Use after changing a rule in HQ's 00-META/how-we-build.md, to publish the derived constitution page the mesh injects into design sessions. Triggers on "sync the constitution", "publish the rules", "I changed how-we-build", "update the governed page".
|
||||
---
|
||||
|
||||
# hal-sync-constitution
|
||||
# hq-sync-constitution
|
||||
|
||||
Publishes the derived constitution from its source. **Authoritative playbook:**
|
||||
[`00-META/process/05-constitution-sync.md`](../../../00-META/process/05-constitution-sync.md).
|
||||
@@ -21,7 +21,7 @@ the claim "HQ is the source" is checked.
|
||||
## Steps
|
||||
|
||||
1. Confirm the source change is recorded as a decision. A rule the mesh enforces is
|
||||
architecturally significant; if there is no record, run `hal-graduate` first.
|
||||
architecturally significant; if there is no record, run `hq-graduate` first.
|
||||
2. Derive the page: the **rules without the reasoning**. Section numbering is stable — the
|
||||
orchestrator and the review fragments cite sections by number, so never renumber to tidy.
|
||||
3. Publish it to the knowledge base under the constitution slug, replacing the body.
|
||||
Reference in New Issue
Block a user