novox/hq

Files

T

jschoubben 00e98f1f92 The vocabulary has no word for a unit that runs and exits

Found by the firewall: every packet filtered as declared, and the machine
reported as not doing what it was told, because the unit that loaded the rules
had finished. Stated as a gap rather than worked around silently.

2026-08-31 01:20:58 +02:00

00-work-breakdown.md

A module claims; it does not list its rivals. And flavor is retired.

2026-08-29 21:00:13 +02:00

01-end-to-end-testing.md

Order the records the way the system is learned

2026-08-28 23:30:42 +02:00

02-scenario-declaration.md

Order the records the way the system is learned

2026-08-28 23:30:42 +02:00

03-scenario-lifecycle.md

Order the records the way the system is learned

2026-08-28 23:30:42 +02:00

04-lab-installation.md

Order the records the way the system is learned

2026-08-28 23:30:42 +02:00

05-the-node-host.md

An action's own idea of being finished must be its verify's

2026-08-31 01:03:50 +02:00

06-the-control-plane.md

Fold the control plane's build decisions into 0006 and 0008

2026-08-29 03:08:50 +02:00

07-the-substrate.md

A bare machine became a mesh, and something joined it

2026-08-30 02:37:37 +02:00

08-connectivity.md

The vocabulary has no word for a unit that runs and exits

2026-08-31 01:20:58 +02:00

09-the-node-lifecycle.md

A node's identity is a keypair it generates. This was never open.

2026-08-29 15:21:36 +02:00

10-delivery.md

Order the records the way the system is learned

2026-08-28 23:30:42 +02:00

11-a-board.md

The three questions a board answers, in the order they are asked

2026-08-30 18:09:17 +02:00

12-a-module-repository.md

The mesh runs its own registry, certifies its own names, and computes its own filtering

2026-08-31 00:37:34 +02:00

README.md

Order the records the way the system is learned

2026-08-28 23:30:42 +02:00

README.md

03-DESIGN / 01-to-be

The mesh being built toward. Every statement here traces to a record in 02-DECISIONS/; nothing arrives by drafting.

A document here describes an intention. What currently runs is in 00-as-is/, and the two are never merged — when something ships, the as-is document is written and this one's status becomes implemented.

Document	Covers	Rests on
`00-work-breakdown.md`	How the decomposition gets built, in what order, and where a human must look	ADR 0001
`01-end-to-end-testing.md`	The lab: a real mesh a change can be run against before it reaches nodes	ADR 0016, 0029
`02-scenario-declaration.md`	What a scenario declares — the underlay, and what to place on it	ADR 0016
`03-scenario-lifecycle.md`	What happens to a scenario — raise, snapshot, restore, move, destroy	ADR 0016
`04-lab-installation.md`	Getting the lab onto a clean machine, and why it verifies capability rather than installation	ADR 0010
`05-the-node-host.md`	Tier 0 — the one thing installed by hand, and the only thing that changes a machine	ADR 0005
`06-the-control-plane.md`	Tier 2 — what the term means, and the test for what belongs in it	ADR 0005
`07-the-substrate.md`	Tier 1 — what the control plane consumes and cannot grant itself	ADR 0004, 0048
`08-connectivity.md`	One context in full — overlay, resolution, exposure, filtering, certificates	ADR 0007, 0050, 0051, 0055
`09-the-node-lifecycle.md`	How a machine becomes a node, stays one, and stops being one	ADR 0004, 0051
`10-delivery.md`	Modules, the three edges, and how a change becomes a running thing	ADR 0010, 0064, 0065

Not yet written

The remaining six contexts. ADR 0006 settles the list at seven; connectivity is the first written in full (08) and the other six do not exist yet. The work breakdown says in what order they are needed.
~~Domain grouping outside the core.~~ Not needed. ADR 0009 is superseded by ADR 0009: there is no domain module to group into, so there is no domain list to settle. Relationships are edges, and grouping is a tag and a query.