One request to the finance capability, eight governed stages, and a governed answer at the end.
Honest by construction: this is a scripted replay with illustrative data, not a live instance. The SHA-256 hash chain in the audit stage and the tamper test below are computed live in your browser. Signature strings are illustrative and labelled as such; verify real signatures with stock tools on the Verify page.
Below is the same audit chain, hashed live. Change one field of entry 4 and re-verify. The recomputed SHA-256 no longer matches, and every entry from that point on fails. A production AIF refuses to start on a chain that fails this check.
This is what tamper-evident actually means. The maths, not our word, is the guarantee.
The stages above are not a storyboard. Each one maps to a running surface a real AIF deployment gives your operators and your auditors.
Status, audit trail, compliance readiness, agent roster, and the kill switch, in one view. The Live preview shows the exact layout your team opens on day one.
Open the Live preview → Regulator timelineGET /api/v1/regulator/timeline returns the signed narrative of every intent and the actions that fulfilled it. Evidence packs bundle a W3C Verifiable Credential an auditor verifies offline. Run the public probes on the Verify page.
Verify the cryptography → Compliance one-pagersEU AI Act Article 12, ISO 42001, and NIST AI RMF, one page each, generated from the audit chain and signed as a Verifiable Credential. See exactly what we claim and how each claim is backed.
Read what we claim →