Files
hq/01-RESEARCH
jschoubben 0afc8cc5f8
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 delivered
Name the commit the knowledge base's records now come from, and link research with touches and decisions with rests-on (review of #312)
2026-10-11 13:25:21 +02:00
..

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 76b346af, the commit the knowledge base's records name as their source (issue 426).