Files
hq/01-RESEARCH/README.md
T
jschoubben 418261213c
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
Remove the decision records and research efforts, which the knowledge base now holds whole (issue 426)
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.
2026-10-11 12:56:09 +02:00

940 B

01-RESEARCH

The research efforts live in the knowledge base, not here (ADR 0290). The knowledge base is the module mesh-knowledge, holding the seat knowledge-base; it holds every effort whole — its number, title, status, the day it began, its documents, its links and every version — and it is the only place an effort is read. This repository keeps no copy. From any node and any folder, through the mesh MCP server: knowledge-base.ask with a question in plain words, or knowledge-base.get with kind: research and a number (reasoning: true, or section with a document's name, for its documents). An effort is started with knowledge-base.reserve and knowledge-base.propose, as playbook 01 says, and closed through playbook 02. The efforts left this folder at hq commit f08920199d, which the knowledge base's import read (issue 426).