hq/03-DESIGN/01-to-be

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 0015
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 0031
03-scenario-lifecycle.md	What happens to a scenario — raise, snapshot, restore, move, destroy	ADR 0032
04-lab-installation.md	Getting the lab onto a clean machine, and why it verifies capability rather than installation	ADR 0008
05-the-node-host.md	Tier 0 — the one thing installed by hand, and the only thing that changes a machine	ADR 0037
06-the-control-plane.md	Tier 2 — what the term means, and the test for what belongs in it	ADR 0037
07-the-substrate.md	Tier 1 — what the control plane consumes and cannot grant itself	ADR 0038, 0048
08-connectivity.md	One context in full — overlay, resolution, exposure, filtering, certificates	ADR 0049, 0050, 0051

Not yet written

• The remaining contexts. ADR 0015 decides the decomposition; connectivity is the first written in full (08) and the others do not exist yet. The work breakdown says in what order they are needed.
• Domain grouping outside the core. Not needed. ADR 0017 is superseded by ADR 0044: 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.