jschoubben
702efca6bb
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.
1.9 KiB
status, opened, located-in, fixed-by, amended-design
| status | opened | located-in | fixed-by | amended-design | |
|---|---|---|---|---|---|
| open | 2026-08-22 |
|
005 — The end-to-end pipeline harness has not built since the workspace was removed
Symptom
The repository's end-to-end pipeline test harness depends on a workspace that no longer exists. It has not been buildable since 2026-06-04. Nothing runs it, and nothing reports that nothing runs it.
Why this matters
The delivery pipeline is the mesh's most consequential machinery — every module reaches every node through it — and its only end-to-end coverage has been silently dead for over two and a half months.
That interval is not incidental. Several of the pipeline's most expensive defects landed inside it: packaging that was never actually split from build, migrations and provisioning scripts reading a source layout that no longer ships, selection files never packaged at all. Whether this harness would have caught any of them is unknown — which is itself the point. The coverage was assumed, not checked.
Evidence
- The workspace was removed by pull request #240 on 2026-06-04 (ADR 0007).
- The harness has not built since that date.
- Recorded in the knowledge base as a standing entry, not as a fixed incident.
Relationship to the lab
02-DESIGN/01-to-be/01-end-to-end-testing.md
designs end-to-end testing on a lab mesh, which would replace this harness rather than repair
it. That is a reason to decide its fate deliberately, not a reason to leave it broken and
unmentioned: until the lab exists, this is the coverage the pipeline is presumed to have.
Open questions
- Repair, or retire in favour of the lab? Leaving it in the repository unbuilt is the one option that keeps the false impression of coverage.
- Was anything relying on it, or had it already stopped running before the workspace removal?