Skip to main content

​
Canonical where implemented

Structured sessions, events, learning records, authority, confidence, status, evidence references, predecessor links, document metadata, source checksums, immutable originals, normalized document artifacts, durable job/audit state, migrations, policy definitions, and evidence records are canonical within their respective stores.

​
Derived and rebuildable

Embeddings, chunk/vector index state, caches, temporary provider state, and presentation views are derived. The provider/model/dimension metadata needed to rebuild a compatible index is retained. A vector must never be the only copy of knowledge. Git owns source, migrations, configuration templates, tests, and project documentation. PostgreSQL and portable artifacts own runtime cognitive/source data. See storage.