Say what the old 'knowledge base' meant, now that the word names the module (issue 430)

The record and the records module for symptom search, the constitution page by its own name.
2026-10-11 20:54:15 +02:00
parent 4336fdfb11
commit c77378fa19
4 changed files with 12 additions and 12 deletions
@@ -8,15 +8,15 @@ design permits.

 ## What belongs here, and what does not

-| Belongs in `04-ISSUES` | Belongs in the knowledge base |
+| Belongs in `04-ISSUES` | Belongs in the operational lessons |
 |---|---|
 | The design permits a failure to be silent | How to fix one occurrence of it |
 | A documented rule is enforced by nothing | A command that works around it |
 | A stated invariant is false in practice | A node-specific quirk |
 | The owning component is unknown and finding it needs the whole mesh in view | Symptom → fix, once the answer is known |

-The knowledge base already holds the operational record and is indexed on symptoms. This
-folder is not a second copy of it. An issue here is a question HQ must **answer**, not an
+The operational lessons (symptom → fix) are found by their literal symptom text through the records
+module (`records.records_search`). This folder is not a second copy of them. An issue here is a question HQ must **answer**, not an
 incident someone must **clear**.

 ## The issue tracker holds the number and the status
@@ -109,8 +109,8 @@ import read, which every imported issue names (`imported.commit` in `issue-track
 - A number never moves. A folder carries the number the tracker gave; a folder whose number collides with
  another (one numbered before the tracker, or by hand) is a fault, and `cycle.py` refuses two records
  sharing a number.
- An issue whose answer is a general lesson should also be written to the knowledge base, so
-  the next person searching a symptom finds it. Both, not either.
+- An issue whose answer is a general lesson also says that lesson in its resolution, in the symptom's
+  own words, so the next person searching that symptom finds it. Both, not either.
 - `wontfix` is legitimate and requires a sentence saying why; the tracker refuses it without one.
 - **An agent says when it starts work on an issue**, by moving it to `diagnosing` or `fixing` with `by`. Two agents
  never start the same work without knowing: the second is refused, naming the first.
@@ -1,7 +1,7 @@
 # Playbook 05 — Constitution sync

 Implements ADR 0021: HQ is
-the source of the constitution, and the knowledge-base page is derived, never edited.
+the source of the constitution, and the constitution page is derived, never edited.

 **Trigger.** [`how-we-build.md`](../how-we-build.md) changed a rule that the mesh enforces at
 runtime.
@@ -24,7 +24,7 @@ and, per the repository's own rule, it is how the rule "HQ is the source" is che
   the derived page carries the rule alone.
 2. Record the change as a decision — a rule the mesh enforces is architecturally significant.
   Playbook [02](02-graduation.md).
-3. Publish the derived page to the knowledge base under the constitution slug, replacing its
+3. Publish the derived page where the mesh keeps the constitution page, under its slug, replacing its
   body. Keep the section numbering stable: the meeting orchestrator and the review fragments
   cite sections by number.
 4. Verify the derived page reads back with the change present. A publish that reported success