Base layer: the mesh as it is, under the mesh as it should be

HQ held only the to-be. Every reader had to already know the system the
decisions were about, and an as-is claim had nowhere to live except inside
an intention.

Adds 02-DESIGN/00-as-is — eleven documents written from the implementation
and the operational record, not from intent, including the parts nobody
would choose again. The two existing designs move under 01-to-be. Layers
are declared in frontmatter and never mix: a design that ships does not
move, its as-is counterpart is written, and both stand.

Back-fills adr/0001-0014 for decisions taken in implementation and never
recorded — the broker, the module abstraction, the mesh database, managed
files, provisioning, migrations, the workspace removal, failing loudly,
the constitution, application placement, linking, the employee model, the
artifact, the three silos. Each marked reconstructed, dated from the
history, and citing the evidence it was recovered from. The two existing
records renumber to 0015 and 0016 so the ledger runs oldest first;
0017 extends 0015 to modules outside the core, principle only — the
domain list is deliberately not invented here.

how-we-build.md becomes the source of the mesh constitution, with a sync
playbook, so the enforced copy stops being the only one that is true.

Process becomes explicit: five playbooks, eight thin skills that defer to
them, a repository map, and AGENTS.md with CLAUDE.md as its include.

The five Observations become 04-ISSUES 001-005 where they can be owned and
closed. 006 is new and uncomfortable: HQ is not indexed into the knowledge
base. That claim is what decision 27 rests on, it was never checked, and
the README now says so instead of repeating it.

Also corrects the ADR index into something generated, the "02-DESIGN is
empty" claim, the VISION.md pointer that did not survive the repo split,
and a note asserting the symlink rule was contradicted — it was a
misreading; the rule forbids hand-made links, the installer links by design.

01-RESEARCH/002-local-mesh/analysis.md

@@ -1,3 +1,8 @@
+---
+effort: 002-local-mesh
+updated: 2026-08-22
+---
+
 # A mesh that runs locally — current state and obstacles
 
 Evidence for Phase 0. Every claim here is either a file location or something measured on
@@ -231,7 +236,7 @@ over either way.
    a local-mesh implementation detail — if the answer is that the mesh should own
    supervision, Phase 0 should not build a container-only workaround first. Under
    investigation; findings will land in [`003-service-supervision`](../003-service-supervision/)
-   and, if it goes ahead, ADR 0002.
+   and, if it goes ahead, a decision record of its own.
 
 2. **What replaces `~/.config/hal/env` and `/services/` inside a container?** A configurable
    root keeps one code path; container-specific targets keep the host paths untouched. This
@@ -248,9 +253,9 @@ over either way.
 
 ## References
 
-- [`adr/0001`](../../adr/0001-mesh-brokers-nodes-host-agents-think.md) — the decision this
+- [`adr/0001`](../../adr/0015-mesh-brokers-nodes-host-agents-think.md) — the decision this
   phase unblocks
-- [`02-DESIGN/00-work-breakdown.md`](../../02-DESIGN/00-work-breakdown.md) — Phase 0 tasks
+- [`02-DESIGN/00-work-breakdown.md`](../../02-DESIGN/01-to-be/00-work-breakdown.md) — Phase 0 tasks
   and checkpoint
 - `troubleshooting/provision-adoption-rotates-live-credential` — fixture B, root cause open
 - `troubleshooting/deploy-reports-transport-not-effect` — the nine defects that shipped

01-RESEARCH/002-local-mesh/status.md

@@ -1,6 +1,12 @@
+---
+status: graduated
+initiated: 2026-08-22
+touches: [02-DESIGN/00-as-is/04-delivery.md, 02-DESIGN/00-as-is/05-runtime-and-installation.md]
+became: [02-DESIGN/01-to-be/01-end-to-end-testing.md, adr/0016-a-lab-node-is-a-virtual-machine.md]
+---
+
 # 002 — A mesh that runs locally
 
-- **Status:** GRADUATED — the design is [`02-DESIGN/01-end-to-end-testing.md`](../../02-DESIGN/01-end-to-end-testing.md)
 - **Initiated by:** jochen, 2026-08-22
 - **Areas touched:** `install.d/`, `hal/meshware`, `hal/coordinator`, `hal/brain`,
   `hal/developer` (`dev_up`), `hal/sdk` (env generation, feature handlers, artifact
@@ -9,7 +15,7 @@
 
 ## Summary
 
-Phase 0 of [`02-DESIGN/00-work-breakdown.md`](../../02-DESIGN/00-work-breakdown.md) requires
+Phase 0 of [`02-DESIGN/00-work-breakdown.md`](../../02-DESIGN/01-to-be/00-work-breakdown.md) requires
 a mesh that comes up in containers, runs its own pipeline, and reproduces known faults on
 demand. Nothing else in the decomposition starts until it exists, because every fault the
 decomposition addresses was found in production — there was nowhere else to find it.
@@ -18,7 +24,7 @@ This effort establishes what already runs in a container, what is welded to the
 what it would take to close the gap. It does **not** choose an approach: the central
 question — how a containerised node executes a module service, when a module service is
 defined today as a systemd unit shelling to `docker compose` in `/services/` — is not
-answered by ADR 0001 and is recorded below rather than decided.
+answered by ADR 0015 and is recorded below rather than decided.
 
 ## What was established