The audit chain
What is recorded, how each entry links to the one before, what Verify chain proves, and what it does not.
What is recorded
Every persisted mutation in Oabo writes one audit entry the moment it commits: registering an AI system, adding a tool, saving a benefit, linking evidence, submitting, validating or attesting a claim, resolving a finding, connecting or revoking a source, importing a CSV, turning the weekly email on, sealing an audit pack, inviting a person. An entry carries who, when, the action and the organization.
The entry is staged in the same transaction as the change and committed with it. If the change rolls back, the entry never exists; there are no phantom entries for things that did not happen, and no change without its entry.
How the chain works
- Each organization has its own chain. An entry carries the hash of the entry before it in that organization.
- Several entries in one transaction chain one after another, not side by side; the chain tail is tracked for the transaction so the links are in order.
- The current chain format signs each entry with a key the database does not hold, so a row rewritten in the database alone does not carry a valid signature.
Note
Audit entries are append-only. There is no edit and no delete, in the product or in the API. Correcting a record is a new entry that says so.
Verify chain
Audit log (/audit-log) shows the chain on screen for an Administrator, Governance lead or Auditor; other roles see a segregation-of-duties note instead of a refusal. Verify chain recomputes the current chain on the server and checks that every entry links to the one before and that each signature holds.
The same guarantee leaves the building as an audit pack: a SHA-256 over the pack's contents, and one per source file inside it, that a reviewer recomputes on the copy they received.
Limits
- Verify chain proves internal consistency: no entry was altered or reordered without breaking a link. It does not prove the database history was never rewritten whole or tail-truncated.
- A hash on an audit pack held outside Oabo is what proves the pack has not changed since it was generated. Keep the hash with the auditor, not only in Oabo.
- An audit trail records that a claim was made and approved. It does not establish economic causality, and Oabo never says it does.