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/003-service-supervision/analysis.md

@@ -1,3 +1,8 @@
+---
+effort: 003-service-supervision
+updated: 2026-08-22
+---
+
 # Who supervises a service — the cost of leaving systemd
 
 Measured 2026-08-22. Every claim is a file location or a count.
@@ -123,10 +128,10 @@ What it costs, honestly:
 
 ---
 
-## 5. Why it cannot be all-or-nothing — and ADR 0001 already says so
+## 5. Why it cannot be all-or-nothing — and ADR 0015 already says so
 
 Some of what runs under systemd today **cannot** be containerised, and the reason is
-already in the domain model. ADR 0001:
+already in the domain model. ADR 0015:
 
 > a non-human agent acts through a spawned session — a human agent acts through a shell or
 > desktop
@@ -203,7 +208,7 @@ found by grep.
 **This no longer gates Phase 0.** When this was written, the local mesh was assumed to be
 built from application containers, which forced the question — there is no natural way to
 run an init system inside one. The decision of 2026-08-22 to build development nodes as
-**system containers** (see [`02-DESIGN/01-end-to-end-testing.md`](../../02-DESIGN/01-end-to-end-testing.md))
+**system containers** (see [`02-DESIGN/01-end-to-end-testing.md`](../../02-DESIGN/01-to-be/01-end-to-end-testing.md))
 removes that pressure entirely: a system container runs a real init, so the existing model
 works unmodified and the lab needs no answer here to exist.
 
@@ -218,7 +223,7 @@ fate-sharing reason in §3.
 ## References
 
 - [`002-local-mesh`](../002-local-mesh/analysis.md) — the effort this came out of
-- [`adr/0001`](../../adr/0001-mesh-brokers-nodes-host-agents-think.md) — agent modality, which
+- [`adr/0001`](../../adr/0015-mesh-brokers-nodes-host-agents-think.md) — agent modality, which
   decides what cannot leave the host
 - `modules/hal/meshware/daemon/src/cerebellum.ts:815-828` — the self-restart workaround
 - `modules/hal/meshware/systemd/hal-module@.service` — the per-module Docker lifecycle