What Is Actually Running

The public preview is honest about live computation versus packaged proof artifacts.

Live in this session

API routes compute canonical hashes, reproducibility checks, tamper mutations, rollback identity, ledger entries, and JSON exports.

Packaged verified receipts

Source snapshots, demo expert encodings, the change report, and the proof receipt are bundled with hashes and checked at runtime.

Not live in public preview

No autonomous legal interpretation, no live Python modality execution, no fresh proof generation, and no live LLM provider call.

Section C / Auditor Walkthrough

Replay the decision as it existed at the time.

Instrument State

canonicalarmed

ledgerrecording

proof modepackaged

The examiner is not asking the system to reinterpret the regulation today. The examiner is checking the committed encoded artifact, its hash lineage, and the deterministic replay path from the committed policy encoding baseline.

In plain English: this is the examiner request. Show me the committed artifact, replay it, support the lineage with receipts, and export the packet I can review later.

Panel 1 - Request Original Encoding

Examiner request: show the bank's committed encoded policy after the update reflected in the referenced supervisory source.

What If It Had Been Procedural AI?

Examiner Packet: Current Method vs Triaxis Atum

Typical ad hoc AI audit packet

Evidence: Audit trail depends on every procedural record surviving and being interpreted consistently.
Replay: Can document process, but usually does not provide byte-stable artifact replay by default.
Hash behavior: No single canonical packet root is produced by default.
Typical gap: In informal AI workflows, proof receipts, rollback identity, and exact canonical replay are not built in.

Triaxis Atum structural record

Evidence: Canonical source encoding, artifact hashes, proof receipt, and exportable bundle.
Replay: The committed artifact can be regenerated to the same canonical bytes.
Preview mode: Live now: canonical replay, hashing, rollback identity, and bundle export. Packaged for this public preview: proof receipt and change-report evidence.
Canonical hash: Generated after verification
Proof and rollback: Proof receipt available in the verification flow. Rollback identity is shown where a policy delta is composed.

Verification Ledger0 entries

Session checks can be reviewed here on mobile and exported as JSON.

Ledger is empty. Run a verification to begin.