jschoubben
87f4f29cc6
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.
2.0 KiB
2.0 KiB
name, description
| name | description |
|---|---|
| hal-sync-constitution | 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
Publishes the derived constitution from its source. Authoritative playbook:
00-META/process/05-constitution-sync.md.
What this is
00-META/how-we-build.md is the source. The
knowledge base carries a derived page that the mesh injects into every eligible design
session, and against which a check phase can block work.
Two texts stating the same rules drift, and the enforced copy wins by default — so the reasoned copy quietly stops being true. This skill is the mechanism that prevents that, and it is how the claim "HQ is the source" is checked.
Steps
- Confirm the source change is recorded as a decision. A rule the mesh enforces is
architecturally significant; if there is no record, run
hal-graduatefirst. - 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.
- Publish it to the knowledge base under the constitution slug, replacing the body.
- Read it back and verify the change is present. A publish that reported success and did nothing is exactly the failure class this repository exists to name — do not skip this.
- Note the sync in the decision record's Consequences.
Do not
- Never edit the derived page directly. An edit there survives until the next sync and then vanishes, taking its reasoning with it.
- Do not relax a rule in the derived page. Overrides may only tighten.
- Do not report the sync as done without the read-back. If it could not be performed, say so — an unsynced rule is a rule the mesh does not enforce, whatever the source says.