Novox Mesh, Nox, and HQ becomes company-scoped

ADR 0027 — the product is Novox Mesh, shortened to mesh internally. HAL was
never chosen: it arrived with the dotfiles repository this grew out of, it
is borrowed, and it is borrowed from the canonical untrustworthy machine
intelligence, which is an odd flag for infrastructure trusted with
credentials. Timing is the substance of the decision, not an aside — the
skeleton is not built, so renaming costs a search and replace now and a
migration later.

Nox is an identity of Novox, and specifically the agent of the MESH rather
than of a node. Nodes keep their own identities. Nox addresses them, and a
human mostly talks to Nox — which makes it the concrete form of the
mission's vision: state an intent, and the mesh works out which node holds
the thing. It holds no private channel. The gap this opens is recorded:
ADR 0012 binds every agent to a home node, and a mesh-scoped agent has
none, so the model needs extending.

ADR 0028 — HQ is company-scoped, novox/hq, with the mesh as its first
product. Checked rather than assumed: the company organisation already
holds live projects that the mesh builds and deploys, so they are tenants
rather than peers, and the mesh is the ground they stand on. There is also
company work outside the mesh already, which strengthens the case and means
the eventual split is closer than "some day" — so each document's scope is
fixed now, in a table, making that split mechanical instead of
archaeological. The folders are deliberately not restructured yet.

The skeleton takes the new vocabulary: mesh-host, mesh-substrate,
mesh-control, mesh-surfaces, mesh-catalog. Substrate drops to four services
now that identity is a hosted workload rather than a dependency.

Research 009 opens the migration, with the reframing that lowers its risk:
replace the control plane, do not move the workloads. Their data never
moves, so it is re-declared rather than adopted — which keeps adoption out
of scope, as the lab design requires. Self-hosting is the last phase, or a
failed cutover takes away the means to fix it.

.claude/skills/hal-amend-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hal-amend-design
-description: Use when a hal-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".
+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

.claude/skills/hal-diagnose/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hal-diagnose
-description: Use when investigating an open hal-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".
+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

.claude/skills/hal-graduate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hal-graduate
-description: Use when a hal-hq research effort 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".
+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

.claude/skills/hal-handoff/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hal-handoff
-description: Use when a hal-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".
+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
@@ -20,7 +20,7 @@ Hands a settled design to a code repository. **Authoritative playbook:**
    `03-DESIGN/00-as-is/` before it is changed. Building against an undocumented as-is is how
    shipped behaviour gets lost.
 4. **Flip the status** to `in-progress`, `updated:` today.
-5. Build in the code repository. hal-hq never carries implementation.
+5. Build in the code repository. HQ never carries implementation.
 6. On completion, run `hal-graduate`'s "when something ships" section.
 
 ## Non-negotiable

.claude/skills/hal-new-research/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hal-new-research
-description: Use when starting a new research effort in hal-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".
+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

.claude/skills/hal-status/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: hal-status
-description: Use when you need a cross-cutting view of where hal-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".
+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
 
 Generates a cross-cutting view **from frontmatter**. This is a read-and-render skill, not a
-workflow — hal-hq has **no central status file by design** (decision 35). Every view is
+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

.claude/skills/hal-sync-constitution/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hal-sync-constitution
-description: Use after changing a rule in hal-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".
+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