jschoubben
e1febe8e0f
The consolidation left a sparse sequence -- 1, 4, 6, 7, 9, 10, 12, 15, 16, 18, 19, 25, 34, 35, 36, 37, 40, 42, 44, 45, 48, 49, 58 -- where the gaps were only the archaeology of what used to be there. Renumbered contiguously. Renames run in ascending order, so every target number is already free and no two files ever collide. The reference rewrite is one simultaneous pass rather than a sequence of replacements. Numbers moved into slots other numbers were vacating -- the node host went 37 to 16 while the lab went 16 to 9 -- so replacing one at a time would have cascaded and silently pointed things at the wrong record. Seven plain-text references survived the merges as prose rather than links, naming records that no longer existed: the enrolment token, the link boundary, what a declaration is, reachability, the repository structure. Each mapped to the consolidated record that now holds it. Verified rather than assumed: every [ADR NNNN](path) link now has matching text and target, checked across the whole repository, and the checker passes. Frontmatter `consolidates:` lists dropped -- they named records that are gone, and each consolidated record already says in prose what it absorbed.
4.3 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 (
03-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.
Proposed direction — Nox is the search
Added 2026-08-23. Rather than syncing these documents into the knowledge base, Nox (ADR 0011) works from within this repository and holds its knowledge directly. Retrieval becomes an agent reading the source, not a copy living in a second store.
This is a better answer than the one the README originally promised, on three counts:
- No sync, so no drift. The failure mode of a derived copy — the enforced copy winning while the reasoned one quietly stops being true — cannot occur when there is no copy.
- It dissolves the original objection properly. The argument against a separate repository was that it adds a fourth knowledge system. An agent with read access adds no store at all.
- It is always current, including for uncommitted work in progress.
But it changes the promise, and that is worth stating rather than glossing. ADR 0011's answer was that these documents would be returned beside everything else in a symptom search. An agent that must be asked is reachable; it is not surfacing. The two differ in exactly the case the operational memory is designed for: someone debugging an error who has no reason to think HQ knows anything about it.
So the open question narrows to one thing:
When a symptom is searched and the answer happens to live in a design document or a decision record here, does the searcher find it without already suspecting it exists?
If Nox is the only path, the answer is no, and the reasoning in ADR 0011 needs amending rather than satisfying. If Nox also contributes what it knows to a symptom search — or the search consults Nox — the answer is yes and the original promise holds.
That is a design question for Nox, not a defect in this repository, and it should be settled before ADR 0011 is treated as answered.