AI Governance Evidence Toolkit
Evidence by default, made practical. Build an AI inventory that sets each use case's control depth, see the board view it generates, and check whether an audit trail has been altered.
These tools implement two controls from the Laurenceo Production Control Specification: the Living AI Inventory (LPC-01), with board information generated from it (LPC-10), and the Tamper-Evident Audit Trail (LPC-04). Not sure where to start? Take the Readiness Assessment first, or run your written policy through the Policy Gap Analyzer.
1AI Inventory Builder
Register every AI use case, including AI embedded in vendor software. Materiality and inherent risk are rated separately and the higher of the two sets control depth, as Laurenceo's consultation response proposes. Your inventory is saved on this device only.
No use cases yet. Add one above, import the template, or load the example inventory.
| ID | Use case | Control depth | Controls that apply | Actions |
|---|
2Board View
Generated from the inventory, so every figure traces back to its source records (LPC-10).
3Evidence Record Verifier
Paste evidence records, one JSON object per line, or open a .jsonl file. Each record is checked against the Laurenceo Evidence Record schema, its SHA-256 hash is recomputed, and its link to the previous record is confirmed. A single edited, deleted or reordered record breaks the chain. Nothing is uploaded.
Downloads
- AI inventory template (CSV): suggested minimum fields for LPC-01, with one example row. Opens in Excel or Google Sheets and imports back into the builder.
- Laurenceo Evidence Record schema (JSON Schema): the record format and the hash chain rule.
- Sample evidence chain (JSONL): five linked records for a claims triage use case.
How the Hash Chain Works
Each record's record_hash is the SHA-256 of the record without record_hash, written in canonical form: JSON with object keys sorted at every level and no extra whitespace. Each prev_hash is the previous record's record_hash, and the first record uses 64 zeros. Any system can produce this with a few lines of code, and anyone can check it without trusting the system that wrote it.
Terms
The schema and template are offered under CC BY 4.0 (opens in a new tab): use and adapt them freely with credit to Laurenceo. They are illustrative reference formats from Laurenceo's independent response to the Bermuda Monetary Authority's consultation, not an official BMA standard, and not legal, regulatory or financial advice.