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.
2.4 KiB
status, opened, located-in, fixed-by, amended-design
| status | opened | located-in | fixed-by | amended-design | ||
|---|---|---|---|---|---|---|
| open | 2026-08-23 |
|
006 — This repository is not indexed into the knowledge base, and the claim that it is holds up a decision
Symptom
README.md states, as the answer to the objection against creating this
repository:
These documents are still indexed into the knowledge base, so
recall_searchreturns them beside everything else. One source, many surfaces — which was always the actual requirement.
Searching the knowledge base for this repository's content returns nothing.
Evidence
Verified 2026-08-23, two searches against the mesh's operational memory:
| Query | Result |
|---|---|
| The full title of a decision record in this repository | No results |
| A distinctive phrase from the decision ledger | No results |
No entry, no partial match, no stale copy. The indexing does not exist and appears never to have existed.
Why this is an issue and not a task
The claim is load-bearing. Decision 27 separates HQ into its own repository, and the objection it answers was that a fourth knowledge system repeats the mistake the mesh's knowledge consolidation was created to fix. The recorded answer is "indexing, not location" — that the split is safe because these documents remain searchable alongside everything else.
Without the indexing, the objection stands unanswered and this repository is precisely the fourth knowledge system it was argued not to be. Either the indexing is built, or decision 27's reasoning is amended to something that is true.
It is also, exactly, the failure this repository names in its own rules: a document stating a rule about the mesh must say how the rule is checked. This one stated a mechanism and nobody checked it — including in the same commit that wrote the rule.
Open questions
- Where would the indexing run? The operational memory is written through a mesh capability; is this a periodic sync of a repository into it, or a search surface that reads the repository directly?
- Which store — the flat symptom-indexed memory, the structured archive, or both? They have
different lifecycles (
02-DESIGN/00-as-is/07-knowledge.md), and this content is governed rather than incidental. - Public repository, private mesh: the sync direction must not become a path for mesh-specific content to arrive into these documents.