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.

README.md

@@ -8,23 +8,26 @@ and why. Today that is almost entirely **Novox Mesh**, the foundation everything
 | Folder | Purpose |
 |--------|---------|
 | [`00-META`](00-META/) | Mission, foundational context, the rules that hold across the mesh, the repository map, and the process playbooks. The northern star for every decision. |
-| [`01-RESEARCH`](01-RESEARCH/) | Active and historical investigations, before they harden into design. |
-| [`02-DECISIONS`](02-DECISIONS/) | Numbered decision records, in the order the decisions were taken — what was chosen, and what was rejected. |
+| [`01-RESEARCH`](01-RESEARCH/) | A pointer: research efforts — investigations before they harden into design — live in the knowledge base (ADR 0290). |
+| [`02-DECISIONS`](02-DECISIONS/) | A pointer, and the reading order's six topics: decision records — what was chosen, and what was rejected — live in the knowledge base (ADR 0290). |
 | [`03-DESIGN`](03-DESIGN/) | The authoritative specification, in two layers: [`00-as-is`](03-DESIGN/00-as-is/) — the mesh that exists — and [`01-to-be`](03-DESIGN/01-to-be/) — the one being built toward. |
 | [`04-ISSUES`](04-ISSUES/) | The front door for "something is wrong" at the level of design or governance. |
 
 **The numbering is the flow.** Research produces a decision; the decision authorises a design.
 That is why decisions are `02` and design is `03` — a reader following the numbers walks the
-process in the order it happens.
+process in the order it happens. The research efforts and decision records themselves live in the knowledge
+base, the seat `knowledge-base`, read and written through the mesh MCP server from any node (ADR 0290).
 
 ## The flow
 
 ```
-idea ──► 01-RESEARCH ──► decision (02-DECISIONS/) ──► 03-DESIGN/01-to-be ──► built (code repo)
- │            │                                      │
- │            │                                      └─► 03-DESIGN/00-as-is once shipped
+idea ──► research ──► decision ──► 03-DESIGN/01-to-be ──► built (code repo)
+ │            │                            │
+ │            │                            └─► 03-DESIGN/00-as-is once shipped
  │            └────► abandoned (recorded, kept)
- └─(small/obvious, still recorded in 02-DECISIONS)──────────► 03-DESIGN directly
+ └─(small/obvious, still a decision record)──────────► 03-DESIGN directly
+
+research and decisions: in the knowledge base (knowledge-base.reserve, propose, ask, get, holds)
 
 symptom ──► 04-ISSUES ──► diagnosis ──► code-repo fix and/or design amendment
 
@@ -91,7 +94,7 @@ is authored is then a separate question.
 on 2026-08-23 and returned nothing; the knowledge base it named was the predecessor's, and since the
 mesh moved to its own bus on 2026-09-28 nothing can reach it at all. The claim is recorded as
 [`04-ISSUES/006`](04-ISSUES/006-hq-is-not-indexed-into-the-knowledge-base/00-report.md) and answered
-by [ADR 0025](02-DECISIONS/0025-the-design-record-is-read-not-copied.md): these documents are
+by ADR 0025: these documents are
 **read, not copied** — an agent reads this repository and a search consults it — and that agent is
 not built. So today this repository is reachable by whoever knows to open it and surfaces to nobody
 else. Said here rather than quietly reworded, because a claim that held up a decision and was never
@@ -103,14 +106,14 @@ Answered separately, a repository of its own is the better home:
   changes. Tying documents to a code branch means they merge on the code's schedule.
 - **The reviewers are different.** A design argument is not reviewed the way an
   implementation is, and it should not queue behind a build.
-- **The scope is wider than one repository.** [ADR 0001](02-DECISIONS/0001-mesh-brokers-nodes-host-agents-think.md) sends most modules out of the
+- **The scope is wider than one repository.** ADR 0001 sends most modules out of the
   monorepo entirely. Documentation that governs several repositories cannot live inside one
   of them.
 
 The trade is real and worth naming: a change to a document and the change to the code it
 describes can no longer land in one commit. Keeping them honest is a discipline now rather
 than a mechanism — which is why every decision is recorded in
-[`02-DECISIONS`](02-DECISIONS/) as it is taken, and why a document that states a rule should
+the knowledge base as it is taken, and why a document that states a rule should
 say how the rule is checked.
 
-Recorded as [ADR 0019](02-DECISIONS/0019-how-this-repository-works.md).
+Recorded as ADR 0019.