project-knowledge

Project knowledge consolidation captures, validates, and stores durable memory across docs, decisions, glossary terms, and runbooks. It routes updates to canonical owners and appropriate documentation targets to maintain a single, inspectable memory source.

Knowledge routing directs project updates to canonical owners and appropriate documentation targets like docs/ directories, runbooks, and the knowledge core. This ensures memory consolidation maintains provenance and ownership before non-trivial architecture work begins.

Knowledge validation enforces provenance, owner assignment, evidence verification, and lifecycle status across repository documentation. This governance keeps project memory accurate, up-to-date, and auditable for future architectural or policy changes.

Crystallize project knowledge into canonical references before undertaking architecture or policy changes. This reduces drift by ensuring future work starts from a validated, single source of durable memory rather than scattered notes.

Yes, memory consolidation applies to glossary terms, decisions, runbooks, and documentation across the repository. It enforces canonical provenance and lifecycle status to keep knowledge accurate and up-to-date before non-trivial work.