Immutable Ledger
1. Immutable Ledger
The Immutable Ledger is a cryptographically verifiable audit trail of every governance decision made by Theseus Guard. Each entry is secured using a tamper-evident HMAC chain with version binding so that any tampering can be detected mathematically.
1.1 What is Recorded
Every significant governance event creates a provenance record in the ledger. This includes:
- Every AI interaction evaluated by a Guard
- Every human review decision (approve / reject)
- Every policy enforcement action (block, rewrite, allow, safe degrade)
- Every policy change proposed and endorsed
1.2 Ledger Table
The ledger is displayed as a paginated table (15 records per page) with the following columns:
| Column | Description |
|---|---|
| Provenance ID | Unique identifier for this ledger entry |
| Event Ref | Reference to the underlying drift event this record is derived from |
| L1 Score | The semantic divergence score at the time of the decision, color-coded by risk level |
| Lane | The governance lane that processed this event (design, detect, prove, route) |
| Action Type | What governance action was taken (e.g., allow, block, rewrite, human_review) |
| Actor | The identity that took the action (system, operator email, or agent ID) |
| Audit Status | The verification status of this entry (verified, pending, failed) |
| SHA-256 Hash | A truncated cryptographic hash displayed in monospace format |
| Date | Timestamp of the governance event |
1.3 Filtering & Search
- Search by Provenance ID, Event Reference, or Employee ID
- Department Filter — Restrict the view to entries associated with a specific organizational department (e.g., Engineering, AI & Analytics, Human Resources)
1.4 Chain Verification
Two verification modes are available from the page header:
Full Chain Verify
Validates the cryptographic integrity of every entry in the entire ledger from the first record to the most recent. The system confirms that each entry's hash correctly links to its predecessor. A success toast confirms the number of entries checked.
Partial Verify (Last 50)
Performs incremental verification on only the most recent 50 entries. This is faster and suitable for routine operational checks.
If verification fails, the system identifies the exact index at which the chain was broken, along with the expected and actual hash values for forensic analysis.
1.5 Export
The full ledger can be exported as a structured JSON file. The export is timestamped and named theseus-guard-provenance-{ISO timestamp}.json. This file can be submitted to external auditors, regulatory bodies, or SIEM systems.
1.6 Ledger Entry Detail (Side Sheet)
Clicking any ledger entry opens a side sheet with the complete record:
Cryptographic Verification Banner
A banner confirms that the entry matches its on-chain hash and has not been tampered with.
Request & Response Context
- Request Context — A preview of the original AI request that triggered this governance event
- Enforced Response — The response that was actually delivered after governance enforcement
Metadata Grid
- Provenance ID
- Action Type (with visual label)
- Lane / Protocol
- Actor identity
- Model used
- Kernel / Guard name
- Timestamp
- L1 Divergence score (color-coded: green = low risk, amber = medium, red = high)
Merkle Root Hash
The full SHA-256 Merkle root hash of this entry, displayed in a copyable monospace code block.
Raw Metadata
The complete system metadata payload for the entry, rendered as an expandable property grid. A "Show Full Metadata" toggle reveals the complete nested structure.