Name the commit the knowledge base's records now come from, and link research with touches and decisions with rests-on (review of #312)
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

This commit is contained in:
2026-10-11 13:25:21 +02:00
parent 418261213c
commit 0afc8cc5f8
10 changed files with 15 additions and 15 deletions
+2 -2
View File
@@ -7,8 +7,8 @@ place a record is read. This repository keeps no copy. From any node and any fol
server: `knowledge-base.ask` with a question in plain words, `knowledge-base.get` with a number (and
`reasoning: true` for the why), `knowledge-base.holds` with a topic below for the clauses in force. A record
is written with `knowledge-base.reserve` and `knowledge-base.propose`, as playbook
[02](../00-META/process/02-graduation.md) says. The records left this folder at hq commit f08920199d25,
which the knowledge base's import read (issue 426).
[02](../00-META/process/02-graduation.md) says. The records left this folder at hq commit 76b346af,
the commit the knowledge base's records name as their source (issue 426).
## Reading order