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.

04-ISSUES/002-stale-package-index-fails-silently/00-report.md

@@ -0,0 +1,40 @@
+---
+status: open
+opened: 2026-08-22
+located-in: []
+fixed-by:
+amended-design:
+---
+
+# 002 — A declared package can fail purely because the node's index is stale
+
+## Symptom
+
+A package install ran without first synchronising the node's package index. It therefore
+requested a version the mirrors had already superseded, and received a 404 from every one of
+them.
+
+The package exists. The declaration is correct. The node's view of what exists is old.
+
+## Why this matters
+
+The failure has nothing to do with the module, the manifest or the mirror. It is a property of
+when the node last synchronised, which nothing in the mesh manages or reports. Two nodes given
+the same declaration on the same day can produce different outcomes, and neither says why.
+
+Combined with [issue 001](../001-failed-package-install-reports-success/00-report.md), the
+failure is not only environmental but silent: today the node ends up without the package and
+the job is green.
+
+## Evidence
+
+- Observed 2026-08-22, same declaration as issue 001.
+- Documented as a recurring shape in the knowledge base under package installation failures,
+  where it is recorded as appearing in two disguises.
+
+## Open questions
+
+- Should the mesh own package-index freshness as a node property, the way it owns module
+  versions — or is an index sync part of the install step?
+- A partial sync is unsafe on the platform in use; a full upgrade is the only sanctioned fix.
+  Does that make index freshness a scheduled node concern rather than a pipeline one?