Provenance Ledger
Log every agent decision and state change with enough metadata to explain or reverse it later.
Problem
Without an immutable, append-only record of every decision and state change tied to a justification, agent behaviour becomes inscrutable after the fact. Rolling back a specific bad action is impossible because there is no event identifier to reverse, and patterns of failure across time are invisible because the trail is not queryable. The team is forced to choose between trusting that nothing will ever be questioned or attempting to reconstruct months-old behaviour from logs that were never designed for audit.
Solution
Append events to an immutable log with: timestamp, actor, action, target, justification (link to thought or decision), diff hash. Enable rollback by id. Reject events that lack the required fields.
When to use
- Agent decisions and state changes must be explainable or reversible after the fact.
- An immutable, append-only log can be operated and queried.
- Each event can carry timestamp, actor, action, target, and justification fields.
Open the full interactive page →
Diagram, neighbourhood map, code examples, related patterns and full provenance.
Related
- Append-Only Thought Stream
- Decision Log
- Compensating Action
- Lineage Tracking
- Black-Box Opaqueness
- Sandbox Escape Monitoring
- Memo-As-Source Confusion
- Emotional State Persistence
- World-Model Separation
- Durable Workflow Snapshot
- Errors Swept Under the Rug
- Rigor Relocation
- Hidden State Coupling
- Policy-Gated Agent Action (KRITIS)