MICKAI
Mickai Ebook · 18 pages · 19 June 2026

The Trust Layer Between AI and the Chain

Everyone is building models and everyone is building chains. Almost no one is building what makes a model's output admissible.

By , Founder and named inventor, Mickai LTD · Crunchbase · LinkedIn · GitHub
Download PDF  →Free · English · PDF
Inside this ebook

Two enormous waves are rising at once. The first is artificial intelligence, where every week brings a model larger, faster and more capable than the one before. The second is the chain, the long quiet revolution in cryptographic ledgers that lets strangers agree on what happened without trusting a central referee. Both are real and both are accelerating. What almost nobody is building is the bridge between them, the layer that takes the output of a model and turns it into something a court, a regulator, an auditor or an adversary can actually rely on. That bridge is the subject of this book,

Part I · The Problem
1. The demonstration trap
2. The output is not the artefact
3. Why logging is not proof
Part II · The Anatomy of Proof
4. Sealing: making tampering visible
5. Anchoring: borrowing time you cannot fake
6. Authority: the binding most systems forget
Part III · Why It Cannot Be Bolted On
7. The retrofit fallacy
8. Proof at the substrate, not the application
9. The cost of getting the order wrong
Part IV · The Trust Layer in Practice
10. What changes when actions are admissible
11. The open record and the right to verify
12. Building the bridge, not another tower
Frequently asked questions

A model can be brilliant and still be worthless as evidence?

Walk into any technology showcase in 2026 and you will see something remarkable. A model reads a contract in seconds, flags the unusual indemnity clause, drafts a response and recommends a position. The room nods. The demonstration works. Then someone asks the only question that matters in the real world, the one the demonstration is designed never to provoke. Six months from now, when this recommendation is challenged, how do we prove the model actually saw that clause, that

Three things turn an output into evidence: a seal, an anchor and an authority?

The first pillar of proof is the seal. Sealing binds the record so that any change to it, however small, becomes detectable by anyone. The mechanism is a cryptographic signature computed over the full content of the record, the output and all its context, using a private key only the signing system holds. Anyone with the matching public key can verify that the record is exactly as it was when signed, and that the holder of that key signed it. Change a single character and the

Proof captured after the fact is proof you already lost?

The most expensive belief in enterprise artificial intelligence is that accountability is a layer you add later. Ship the capability now, the reasoning goes, and wrap it in audit and compliance once the value is proven. This is the retrofit fallacy, and it fails for a reason that is structural, not a matter of effort or budget. Most of what makes a record provable exists only at the instant of the action. The model version, the exact input, the configuration, the authority co

Cite this work
Irons, M. (2026). The Trust Layer Between AI and the Chain. Mickai LTD. https://mickai.co.uk/ebooks/the-trust-layer-between-ai-and-the-chain.
About the author

Micky Irons

Founder of Mickai LTD (Companies House 17166618, England and Wales). Named inventor on the Mickai SIOS patent corpus, recorded on the UK Intellectual Property Office public register at numbers GB2607309.8 to GB2611702.8. Trade mark Mickai registered at UK00004373277 (classes 9 and 42, filed 15 April 2026). Before founding Mickai, Micky was a Sellafield site worker, and the egress constraint observed from inside the regulated workstation is the engineering origin of the substrate.

More ebooks