The Robotaxi, the Redacted Black Box, and the Record the Public Can Verify

By Micky Irons, founder of Mickai.

Justice can only weigh what it is allowed to see. When the evidence is sealed inside the defendant, the scales are decorative.

The crash you were told about

A robotaxi runs a vulnerable road user down at an intersection. Within hours the operator issues a statement. It cites internal telemetry, frame counts, object-detection confidence scores, and a timeline measured in milliseconds. The numbers are precise, the tone is cooperative, and almost none of it can be checked. The data that describes the death was recorded by the vehicle, formatted by the manufacturer, and selected for release by the company whose liability turns on what it shows.

This is the structural problem with autonomous-vehicle accountability, and it is not a problem of bad actors. Even an honest operator controls the only copy of the truth. Regulators receive what is handed to them. Investigators reconstruct from a feed they cannot independently timestamp. Families are asked to accept a narrative whose source code, sensor logs, and disengagement records sit behind the same corporate firewall that decides which version of events reaches a courtroom.

Why the black box is not enough

Aviation taught the public to trust the black box, so the phrase carries borrowed credibility. The comparison flatters the wrong thing. An aircraft recorder is a hardened, standardised, independently recoverable device read out by an investigation body with statutory authority. A robotaxi's event log is a proprietary data structure, schema-controlled by the manufacturer, decoded with the manufacturer's tools, and surrendered on the manufacturer's timeline. Nothing in that chain proves the file you are reading is the file the vehicle wrote.

Three failures hide inside that gap. The record can be edited after the fact with no external trace. It can be withheld selectively, releasing the frame that exonerates and losing the frame that does not. And it can be back-dated, so a software change shipped after the incident appears to have been live before it. None of these require malice. They only require that one party hold the original, the copy, and the clock.

Memory that cannot be altered is a different instrument from memory that is merely stored. The seal, not the storage, is the safeguard.

What a verifiable record actually requires

The fix is not more disclosure. More disclosure still flows through the party with the most to lose. The fix is to change what a record is, so that its integrity no longer depends on trusting the entity that produced it. Two properties do this work. The record must be sealed at the moment of the event, so any later change is mathematically detectable. And the proof of when it existed must live somewhere the manufacturer does not control, so the timeline cannot be quietly rewritten.

This is precisely the gap a Sovereign Intelligence Operating System is built to close. Mickai runs fifty specialised AI brains, twenty-five domain and twenty-five operational, on the operator's own hardware, fully offline-capable. Every consequential action those brains take is written to the Open Audit Record. The OAR seals each entry and signs it with FIPS 204 ML-DSA-65, the published NIST post-quantum signature standard. The signature is not a Mickai invention. It is the standard the wider world is migrating to, adopted here so that a record sealed today still verifies after classical cryptography has aged out.

A signature proves the record was not altered. It does not, on its own, prove when the record came into being. For that, Mickai uses Pantheon, its own sovereign Layer 1, anchored to Bitcoin and carrying the native token PAN at a fixed supply of five billion. Pantheon writes a hash commitment of the sealed record into a chain whose own history is anchored to Bitcoin for permanence. It commits a fingerprint, not the footage. It moves no coins and settles no payment. As the principle goes, anchoring is not spending. The original telemetry can stay private, encrypted, and on the operator's premises, while a one-way fingerprint of it sits in public, fixed in time, impossible to back-date.

Who gets to decide what happened

Put those two properties together and the question of authority shifts. An investigator no longer asks the manufacturer to vouch for a file. They hash the file the manufacturer provides and check whether that fingerprint was anchored at the time of the crash. If it matches, the record is the original and its timeline is independently confirmed. If it does not, the discrepancy is itself evidence. The operator keeps its secrets, the public gets its proof, and neither has to take the other on faith.

This is the inversion that matters. Today the company that built the vehicle is also the custodian, the editor, and the witness of the only account of how it killed someone. A signed, anchored record does not seize the data. It removes the manufacturer's monopoly on whether that data can be trusted. The footage can stay redacted for genuine privacy reasons while its integrity remains publicly verifiable, which is the opposite of the bargain on offer now, where the public sees a curated narrative and must trust it precisely because it cannot be checked.

Anchoring fixes a record in time without moving anything that matters. The fingerprint is committed; the evidence itself never leaves the operator.

Evidence, not advertising

Mickai holds 101 filed UK patent applications, around 2,234 claims, owned by Mickai LTD, with the architecture above named in the filings. They are cited here as evidence that the design is specified rather than improvised, not as the point of the article. The point is older than any patent. A society that delegates life-and-death decisions to autonomous machines needs an account of those decisions that does not depend on the goodwill of the firm that profits from them. The technology to provide one already exists. What has been missing is the will to make the record answer to the public rather than to the manufacturer.

The robotaxi will not stop the car to explain itself. But the system around it can be built so that the explanation is sealed the instant it happens, anchored where no single party can reach it, and verifiable by anyone with the file and a hash function. That is a modest technical change with an immodest consequence. It moves the answer to the only question that matters after a fatal crash, what actually happened, out of the boardroom and into the open.