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.
3.5 KiB
layer, status, code, updated, decisions
| layer | status | code | updated | decisions | |
|---|---|---|---|---|---|
| as-is | implemented |
|
2026-08-23 |
Knowledge
The mesh keeps two knowledge stores. They are not redundant, and knowing which is which is the difference between finding an answer in one search and rediscovering it over several hours.
The operational memory
A store of operational notes, written and read by whoever — human or agent — is working. Each note is a slug and a body: how something works, what went wrong, what the fix was, what assumption turned out to be false.
It is indexed on symptoms. The entry someone needs is usually titled after the error they are staring at, which is why the standing instruction is to search the literal error text before forming a hypothesis rather than after one fails.
Its content is overwhelmingly the record of previous debugging: a large body of troubleshooting entries, module conventions, and standing notes about work that is open. It is the mesh's institutional memory of what has already gone wrong.
The cost of skipping it is documented in the mesh's own record: entries have been rediscovered from scratch, over hours, in sessions where the search was skipped because the trail felt confident. It fires hardest on familiar ground, not unfamiliar ground.
The structured archive
A second store, structured rather than flat: spaces, pages, revisions, tiers, and full-text search. Where the operational memory is a note, this is a document with an owner and a lifecycle.
Content is promoted through tiers — private, then team, then platform — with a librarian agent owning approval and promotion at the boundary. Proposals to edit are reviewed rather than applied.
This is where the mesh's governed documents live, including the constitution injected into design sessions (ADR 0005).
Why both
The distinction is by lifecycle, not by subject.
| Operational memory | Structured archive |
|---|---|
| Written the moment something is learned | Written deliberately, reviewed |
| Flat, symptom-indexed | Structured, tiered, owned |
| Anyone writes; nothing approves | Promotion is approved |
| Truth is "this happened" | Truth is "this is agreed" |
Collapsing them would cost one of the two properties: either every hard-won note waits for review, or governed documents can be changed by anyone mid-incident.
Where this repository sits
This repository is a third thing, and the objection was raised when it was created: a fourth knowledge system repeats the mistake the split was made to fix.
The answer given was indexing, not location — that these documents are indexed into the knowledge base so that a symptom search returns them alongside everything else. One source, many surfaces.
That indexing does not currently exist. A search for this repository's content returns
nothing. The claim is load-bearing for the decision to separate the repository at all, and
until it is true, this repository is exactly the fourth knowledge system the objection
described. Recorded here because it is a statement about how the mesh's knowledge actually
works today, and as 04-ISSUES/006.
The librarian
A single agent owns the archive's approvals and promotions. Its approval capabilities have at times not been reachable as tools, which does not affect the operational memory but does mean promotion stops silently — the store keeps accepting proposals that nothing can approve.