Ideas · Builder Notes
Pinned evidence, replay and erasure in Kognita
How Kognita alpha pins policy and content hashes so a decision can be replayed later, and how the retention store handles erasure without breaking the chain.
Context
Replaying a decision months later is meaningless if the policy or the retrieved content has changed underneath it.
Decision
- Each policy check records the hash of the policy row as evaluated.
- Replay fails if that row no longer matches or its effective window no longer covers the decision.
- In-place edits of a policy that is or was in force are refused; supersede_policy closes the window and inserts a new effective-dated row.
- Retrieval records a content hash and the embedding model per item.
Why
Policies became effective-dated history instead of mutable configuration. That is what a supervisor needs.
Outcome
A content retention store with erasure landed, and the erasure checkbox was ticked.
Open
The tamper item stayed open until the reconstruction command shipped, because that line of the definition of done needed both.
Never edit a rule that has made a decision. Supersede it, and keep the old one replayable.
Sources
Kognita is an open-source alpha. This note comes from Kognita PR #15 in the Kognita repository.