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,7 +1,7 @@
|
||||
# HAL — HQ
|
||||
# Novox HQ
|
||||
|
||||
The single source of truth for what the HAL mesh **is**, what it is **becoming**, and
|
||||
why. Implementation lives in `modules/`; the reasoning behind it lives here.
|
||||
The single source of truth for what Novox builds — what it **is**, what it is **becoming**,
|
||||
and why. Today that is almost entirely **Novox Mesh**, the substrate everything else runs on. Implementation lives in `modules/`; the reasoning behind it lives here.
|
||||
|
||||
## Structure
|
||||
|
||||
@@ -78,7 +78,7 @@ particular installation, it is either a note in the wrong place or a disclosure.
|
||||
|
||||
## Why this is its own repository
|
||||
|
||||
It began inside the code repository, on the reasoning that HAL already has a mesh-native
|
||||
It began inside the code repository, on the reasoning that the mesh already has a mesh-native
|
||||
knowledge store and that adding a fourth knowledge system would repeat the mistake this
|
||||
folder was created to fix.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user