jochen
a28da1734b
ADR 0244 sorts the mesh's concepts into ten domains (ADR 0006's contexts carry over as domains), keeps machine and node as distinct words, and makes the glossary the authority with every retired word on its replacement's Not: line. To-be 49 draws the domains; the glossary is reorganised by them, its two contradictions removed and the missing words added. words.py now fails on a retired word in running prose and on a word defined twice, so the rule is enforced rather than believed; the 63 documents it failed on are reworded here, and research 034 is kept as the record of the words it studied.
3.2 KiB
layer, status, code, updated, decisions
| layer | status | code | updated | decisions | |||||
|---|---|---|---|---|---|---|---|---|---|
| as-is | implemented |
|
2026-09-30 |
|
Knowledge
The mesh keeps no knowledge store. What it knows is what its modules answer, and the way a person or an agent asks is the mesh MCP server's tool list on the machine they sit at (13 — The mesh MCP server). This document used to describe two stores; it is rewritten because neither exists from the mesh's side, and an as-is document that describes what is gone is a brochure.
What was here, and where it went
Until the cut-over of 2026-09-28 the predecessor ran two stores: an operational memory of notes indexed on symptoms, and a structured archive of governed documents with a librarian approving promotion. Both were reached through the predecessor's tool server over the bus the mesh removed (issue 147). Nothing in the mesh reaches them now, and nothing in the mesh has replaced them: there is no note store, no archive, no librarian, and the lessons of the last days were written into this repository by hand. That is a gap, and it is stated here rather than papered over. What replaces a symptom-indexed memory, if anything does, is undecided.
The record
The design record is read where it is written. Since 2026-09-30 a module, records, keeps a
checkout of this repository from the forge — cloned from the git seat, reset to the origin on every
merge the forge announces and every ten minutes — and answers over the bus: where a phrase appears as
written, one document whole, what a folder holds, and where the checkout stands, each naming the
commit it read. Which repository it reads is a setting on its assignment; the module names no mesh.
It is listed by the mesh MCP server beside every other tool, with a description that says to search the literal words of a symptom before forming a hypothesis. That is what ADR 0025 meant by beside everything else, in a mesh with no store to be beside (ADR 0153).
Nothing is copied. A checkout lags the source by seconds after an announced merge and by minutes otherwise, and says so.
The constitution
00-META/how-we-build.md is the source of the mesh constitution
(ADR 0021). The page it used to be
synchronised into lived in the predecessor's archive and is unreachable; the constitution today is
read from this repository, through the same module, and playbook 05's sync has nothing to write to.
Where this repository sits
A third thing beside two that are gone, which makes it the first: the one governed record the mesh has, public, read by a module the mesh assigns, and edited nowhere else.