When they ask, hand them this.

An auditor asks what your AI did last Tuesday. You send one sealed file. They check it on their own computer, for free, and if anyone changed a word, the check points to it.

The rules that ask for a record

  • EU AI ActArticle 12 · record-keeping
  • EU AI ActArticle 19 · logs kept by providers
  • EU AI ActArticle 26 · logs kept by deployers
  • Regulation (EU) 2026/1744Annex III from 2 Dec 2027
  • SEC Rule 17a-4records preserved
  • FINRA Rule 4511books and records
  • SOC 2automated actions evidenced

The chain

Every step holds the one before it.

A sealed record is a run written as a chain. Each step is locked to the one before it, so a change anywhere shows at the exact step, and every step after it stops matching.

The check, on a loop: find the changed mark, name it, show the chain as sealed.

A run of 240 steps, one dot each, every one sealed onto the one before it.

A drawing of the rule, not a record. The real check runs on a real record further down.

The question

Someone will ask how you know.

An auditor, a regulator, an insurer, opposing counsel. Each of them wants to see what the agent did, and the tools watching your agents keep that story in their own systems and ask to be believed.

A sealed record lets the person asking check it for themselves, on their own machine, with a checker they run or write from the published format. Nobody has to take your word for it, or ours.

The four checks

Four questions, in the order they get asked.

A wrought-iron gate grille on a pale sweep, raked by one hard window light.

01 · Before it runs

What was it allowed to do?

Before the agent runs, shows you which of its add-ons and instructions could reach your secrets, send data out, delete files or override its orders, each with the line that says so. It reads them and never runs them.

Its receipt proves the review ran on those exact bytes.

Scan the Instruction Layer →
A fan of clear glass plates, each resting on the one before it, lit from one side.

02 · While it works

What did it actually do?

Every step of the run lands in one sealed file, each step locked to the one before it. Alter any part afterwards and the check fails at the step that changed.

Proves the record is unchanged since it was sealed.

See a Sealed Run →
A black assayer’s slate streaked with gold, beside a brass needle, under window light.

03 · After it finishes

Is the result actually true?

Takes a claim the agent made, like “the tests pass”, and tries to break it. The verdict comes from checks that ran, never from the agent’s say-so.

The verdict holds for the evidence captured at that moment.

Break a Claim →
A satin steel ring binder standing on a pale floor in a beam of window light.

04 · When someone asks

Will an auditor accept it?

Maps what the first three left behind onto your control framework and tells you, control by control, what exists and what is missing. Every line is cited by file, digest and field.

Evidence you assembled; the audit opinion and any cover stay with your auditor and insurer.

Assemble a Pack →

The foundation

One kind of record. One seal.

All four write the same record and seal it the same way, so the files work together and nothing you keep is locked to us. See how it is built →

Before the price

What this does not prove.

Six words are banned in our code and checked on every commit. If your job is to find the overclaim, here it is first, at full size, above the money.

  • tamper-proof
  • unforgeable
  • guaranteed
  • immutable
  • forge-proof
  • authentic run
  • Changes show up

    not unchangeable

    Anyone can edit the file. What they cannot do is edit it without the edit becoming obvious to the next person who checks.

  • Signed by that key

    not a trustworthy run

    The signature proves which key sealed it. Whether the key’s owner is honest, and whether the work was any good, are different questions.

  • Scanned for signals

    not certified clean

    A scan reports the patterns its rules match, with the file and line. Nothing matching is not the same as nothing there.

  • Complete as captured

    not all-seeing

    The agent cannot quietly drop a step, because it is not the one writing them down. But nothing can record what the system running it never saw.

Try it

Check this record. Then break it.

This sealed record is real: an AI adding a limit to a payments API, five steps long. Press Check It and your browser checks every step and the seal, right here.

Then press Tamper With It. One word changes, and the check stops at the step that changed. Every part of Rotairo hands you a file you can question the same way.

sample-record.json · sealed 2026-08-11 09:19:05Z

Not checked yetIDLE

Press Check It to run the check on the record above.

The in-page checker needs JavaScript. The command-line checker does not, and everything else on this page reads without scripts.

Who asks

Three of them, one request.

Each already asks the same thing in its own words: a lasting record of what the machine did, that someone outside your company can review.

Applies · 2 Dec 2027

EU AI Act

Automatic event logs, kept at least six months, for high-risk AI systems.

  • Regulation (EU) 2026/1744 set 2 December 2027 for the Annex III list and 2 August 2028 for AI built into regulated products.
  • Articles 12, 19 and 26: providers keep the logs, deployers keep them too.
  • Fines run to €15M, or 3% of worldwide turnover.

In force

SEC 17a-4 · FINRA 4511

Records preserved so they cannot be rewritten or erased.

  • FINRA’s 2026 report names generative AI a recordkeeping risk outright.
  • A sealed record shows a rewrite at the step it happened.

Ongoing

Auditors and insurers

SOC 2 auditors now ask how automated actions are evidenced.

  • Carriers are writing AI exclusions and asking for the logs in writing.
  • Binder maps your records onto the framework they hand you.

The technical detail

Forward this to whoever reads the code.

The stack, the standards it uses and what each part gives you, on one page. Whoever reviews this for you can check every claim on this site without asking us anything.

Pricing

Checking is free. Always will be.

Every tool in the stack runs free. You pay when you want the records stored and timestamped, identities issued, or someone standing in front of your auditor with you.

  • A slate and a brass needle, the object of this plan

    Verifier

    $0

    Permanently, with no time limit.

    • All four tools, run on your machine
    • The offline checker, no dependencies
    • The published record format
    • Development keys and test files
    Check a Record →
  • A fan of glass plates, the object of this plan

    Team

    $49 / month

    Opening soon. One workspace with five agents, then $10 a month for each agent after that.

    • Hosted timestamping and a public log
    • Retention with a stated posture
    • Real identity issuance (OIDC)
    • Record search for the whole team
    Join the Waitlist →
  • A steel binder, the object of this plan

    Compliance

    From $25,000 / year

    Start with a 60-day evaluation for $5,000, credited to your first year. Design partners pay $15,000 for year one with three seats, then renew at list.

    • EU AI Act evidence packs
    • 17a-4 and 4511 retention mapping
    • Auditor-facing exports and a named liaison
    • SSO, SLAs, named support
    Become a Design Partner →

The rule we will not break

Checking a record never costs money. The moment the check sits behind a subscription, “you do not have to trust the issuer” becomes something you buy from the issuer, and the reason to hold a sealed record is gone.

Seal your next run. Then try to break it.

Tomorrow’s run can leave a record anyone can check. Break the sample first.