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.4 KiB
2.4 KiB
name, description
| name | description |
|---|---|
| hal-status | 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 — 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
| Section | Files | Frontmatter |
|---|---|---|
| Research | 01-RESEARCH/NNN-*/00-overview.md |
status (active / graduated / abandoned), initiated, touches, became |
| Design | 03-DESIGN/**/*.md (not READMEs) |
layer (as-is / to-be), status (designed / in-progress / implemented / abandoned), code, updated, decisions |
| Decisions | 02-DECISIONS/NNNN-*.md |
status (proposed / accepted / superseded), date, deciders, reconstructed, superseded-by, extends |
| Issues | 04-ISSUES/NNN-*/00-report.md |
status (open / diagnosing / located / resolved / wontfix), opened, located-in, fixed-by, amended-design |
Steps
- Read the frontmatter block from every file above — a grep across each tree is enough, no need to load bodies.
- Render what was asked as Markdown tables. Group and sort sensibly. The ADR index is one of these views: records ordered by number, with title, date and status, and reconstructed ones marked.
- Flag anything inconsistent at the end, as flags — do not silently correct the render:
- a
graduatedorabandonedeffort with an emptybecame: - an
implementeddesign with an emptycode: - a
supersededrecord with nosuperseded-by: - an
openordiagnosingissue with no activity - a to-be design whose
decisions:points at a record that does not exist - an as-is design whose claims are older than its
updated:date suggests
- a
Do not
- Do not write a status file. Central status files are explicitly rejected. The view is always generated, always ephemeral. This includes the ADR index — the hand-written one had already drifted after a single addition, which is why it was removed.
- Do not infer status from prose. Trust only the frontmatter; if it is wrong, flag it.