mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it…
mesh/delivery superseded: a newer head of the same pull request
ADR 0290 rule 9: once the import is checked record by record, hq keeps no copy. The records and efforts are removed; every link or path to them reads "ADR NNNN" or "research NNN"; a design's decisions: lists "ADR NNNN". 02-DECISIONS keeps a pointer README with the reading order's six topics, which the knowledge base reads through the records module; 01-RESEARCH keeps a pointer README. The checks drop the rules that judged records (the knowledge base holds each at propose; checks/README.md says where) and refuse a record written here again. Playbooks 01 and 02 and the skills write and read records with the knowledge base's verbs.
59 lines
2.8 KiB
Markdown
59 lines
2.8 KiB
Markdown
---
|
|
layer: as-is
|
|
status: implemented
|
|
code: [mesh-catalog modules/records, mesh-catalog modules/mesh-console]
|
|
updated: 2026-09-30
|
|
decisions:
|
|
- "ADR 0025"
|
|
- "ADR 0153"
|
|
- "ADR 0152"
|
|
---
|
|
|
|
# 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](13-the-console.md)). 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](../../04-ISSUES/147-the-operators-tools-still-dial-the-bus-that-was-removed/00-report.md)).
|
|
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`](../../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.
|