AI Governance & Assurance · live demo
The evidence binder that can prove what the auditor received.
The PBC scramble is the top cause of reporting delay: requests arrive as free-text emails, artifacts go back as attachments, versions fork, and weeks later the auditor says an item was never received. This binder draws the trust boundary the way I believe every finance agent should. The model may only locate artifacts and quote what it matched on, and it must abstain when nothing fits. Four deterministic gates (period, entity, TB tie-out to the cent, SHA-256) decide whether a binding can be delivered, a named controller clicks Deliver on every handover, and the hash-chained manifest answers any later dispute by recomputation rather than by memory. Synthetic data · 74 PBC requests · runs in your browser
The dispute, replayed from the chain
recomputed live, in this browserMake your own request · the auditor seat
bind, or abstain into Open ItemsType a request, or click a chip. The model locates candidates by their claimed metadata and quotes what it matched on. The four gates then check the actual content in code, one decision at a time. If every gate passes, you hold the controller seat and nothing moves until you click Deliver.
The request register · zero silent gaps
| request | area | text | status | secs |
|---|
The handover manifest · the fee-negotiation artifact
Every delivery lists its artifact SHA-256 and chain position. Recompute checks the files still in the binder against what the manifest says was delivered; alter one artifact and the recompute locates it exactly.
Request list shaped on the NAIHC Prepared-by-Client list · artifact row schema modelled on State of CT Open Expenditures ledger fields (Public Domain) · the locator "model" is a deterministic stub, so runs reproduce exactly · amounts in integer cents · in-run timestamps are simulated