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-graduate | 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
Closes a research effort into a decision and a design, or amends an existing design.
Authoritative playbook:
00-META/process/02-graduation.md — read
it; this skill adds only the scaffolding.
Steps
- Check against GENESIS —
mission.md,context.md,effect.md. If the conclusion conflicts, say which is wrong, in writing, before proceeding. - Write the decision record in
02-DECISIONS/, next free number, frontmatter per02-DECISIONS/README.md.reconstructed: false— this one is being taken, not recovered. Record the rejected options. - Write the design under
03-DESIGN/01-to-be/withlayer: to-be,status: designed, emptycode:, today'supdated:, anddecisions:pointing at the record. - Close the effort — the research
00-overview.mdgetsstatus: graduatedandbecame:pointing at both.
Amending an existing design
A design changes only through a decision. Write the record first; if it reverses an earlier
one, set that record's status: superseded and superseded-by: — never edit its text.
Then edit the design and set updated:.
When something ships
Write or update the matching 03-DESIGN/00-as-is/ document so it describes what now runs,
including anything that shipped differently from the intent. Set the to-be document's
status: implemented and its code:. The to-be document does not move — both stand.
status: implemented must be defensible from the owning repository's main branch. If it
cannot be checked, it is in-progress.
Do not
- Do not move a to-be document into
00-as-is/. - Do not edit an as-is document to describe an intention.
- Do not change a decision record's meaning. Supersede it.