Knowledge Routing

alt_routeGuideline

Every piece of knowledge has exactly one correct destination — never free-form memory.

Rule

Memory is reserved for type: user and type: feedback. Knowledge of type: project or type: reference MUST be written to a governance-eligible artifact — ADR, Context Inventory entry, plan amendment, or insights.md pointer — never directly to a memory file.

Why

Memory is friction-less by design — no gate, no evidence block, no provenance. When project-knowledge lives there, it bypasses Rule 7 ("Decisions are signed") and Rule 8 ("Approval requires evidence"). Decisions become invisible and insights.md becomes a black hole.

How

Before saving a memory, classify the content. If type would be project or reference, route to the matching artifact instead. insights.md entries are pointers to where the learning landed, not the learning itself.

Routing Table

Knowledge kind	Destination	Memory?
User role / preferences / working style	`memory/`	✓ user
Correction or validated approach	`memory/`	✓ feedback
Architectural decision	new ADR via `/new-adr`	×
Domain or system fact	Context Inventory entry	×
Confirms / refutes a plan hypothesis	plan body + evidence block	×
Surprise during Exp/Production	`insights.md` pointer	×
External system pointer	Context Inventory `external-references`	×
Fact that changes scope of active plan	plan amendment (with provenance)	×

Decision Tree

Is the knowledge about the human (role, preference, correction)?
├── Yes → memory (type: user or feedback). Done.
└── No  → it is project / reference knowledge.
         │
         ├── Does it state a decision ("we will / we will not …")?
         │   └── Yes → ADR.
         │
         ├── Does it describe how the system is, or where to find something?
         │   └── Yes → Context Inventory entry.
         │
         ├── Does it confirm/refute/extend an active plan's hypothesis?
         │   └── Yes → that plan's body + evidence: block.
         │
         └── Is it a surprise that does not yet have a home?
             └── Yes → insights.md, pointer to its future home

menu_book guidelines/knowledge-routing.mdopen_in_new