MICKAIAll articles
Field guide

Auditable AI: a field guide to sovereign, verifiable artificial intelligence.

Governance is an engineering property, not a policy statement. You either signed the record at the moment of the act, or you did not. This guide is the map to the writing behind that idea: what an audit trail for artificial intelligence has to be, why it must be signed before execution and verifiable offline, what sovereignty means when the treasury is paying, how autonomous agents are contained, and why a tamper-evident record is the precondition for liability. Use it as a reference, or hand it to a procurement team.

101
Filed UK patents
2,234
Claims
50
Brains
FIPS 204
Post-quantum
What auditable AI actually means

Auditable artificial intelligence is not a dashboard and it is not a quarterly responsibility report. It is the property that you can prove, to someone who does not trust you, exactly what an AI system did. Most AI logs fail this test: they are written after the fact, sit on infrastructure the operator controls, and can be edited. The Open Audit Record is the answer, an append-only, hash-chained ledger of every action.

Signed before it executes, and post-quantum

The decisive engineering choice is to sign each action before it runs, not after, so the record cannot be reconstructed to flatter the operator. The signatures are post-quantum, using the United States National Institute of Standards and Technology standard FIPS 204 (ML-DSA-65), so a record signed today is still sound against the cryptography of the next decade. Procurement that ignores this builds a cliff into its own future.

Verifiable offline, trusting nothing

A record only matters if an outsider can check it without your cooperation. The Open Audit Record is verifiable offline, by a verifier that runs inside an ordinary web browser, with no network connection and no trust in the vendor. That is what turns a claim into evidence a regulator, an insurer, or a court can rely on.

Sovereignty: own the hardware, the keys, the chain

Owning a data centre is not owning the audit. Sovereignty means the operator holds the hardware, the keys, and the audit chain, so trust is replaced by verification and the off switch is theirs. It is the same principle whether the subject is a nation's intelligence or a community's water and power.

Containing agents that act on their own

Autonomous agents now take actions and trigger other agents without a human in the loop. The defence is containment as an engineering property, not alignment alone: see every action, stop it instantly on your own hardware, and prove what it did. Prompt injection is structural, so the system around the agent must be the deterministic control.

Liability, and why the record is the precondition

Security improves when someone is liable and has to pay for failure. As 2026 law shifts artificial intelligence risk onto deployers, liability requires a provable account of what a system did. A tamper-evident, signed record is the precondition that makes liability assignable rather than deniable, and that closes the old defence that nobody can prove what the machine decided.

The substrate: a cooperative of brains, anchored to Bitcoin

Underneath the record sits the system that produces it: fifty specialised brains (twenty-five domain and twenty-five operational) on the Poseidon silicon substrate, and Pantheon, a sovereign Layer 1 blockchain that takes the audit root on-chain and anchors it to Bitcoin so the timeline cannot be quietly rewritten. The whole design is protected by 101 filed United Kingdom patent applications.

The thesis

Every page linked above defends one idea from a different angle: that trust in artificial intelligence cannot be declared, only demonstrated, and that demonstration is an engineering task. Mickai is the Sovereign Intelligence Operating System built to make it one. Read the full corpus, or start with the record itself.