Be first. Stay first.
Agents move fast. Untraced is unsafe. When the EU AI Act asks, show your work.
Preparing the proof.
Serial AWAITING
Patents pending
No one checks.
A wrong answer looks like a right one, so the failure goes straight through and nobody sees it.
re-runs the record's own steps on your machine. OK, REJECT, or ERROR. An ERROR never turns into an OK. Free and Apache-2.0, over every record you emit and every agent action.
From 2 August 2026 the EU AI Act prices unmarked AI content at up to €15 million or 3% of worldwide turnover. The high-risk deadlines moved. This one did not.
One re-run, two jobs.
The records you keep
The number you signed, re-run by whoever asks.
No reconstruction, no chasing whoever signed it and left. They re-run it themselves.
What changes
- Answer a demand with a re-run, not weeks of review.
- Check the whole population, not a sample.
- Nothing you defend rests on your word.
The agents you run
Every action, checked at agent speed.
One more check costs almost nothing, so nothing ships on trust, even at a thousand runs a day.
What changes
- Every agent action carries a record anyone re-runs.
- Keep pace with deployment, not a sampling budget.
- Answer for what an agent did, when anyone asks.
Where it breaksSudoku is the easy case, because its rule is the same for every puzzle ever printed. Here the rule has to be pinned to each claim before anything is checked, and picking the right rule is still a human call.
Upcoming EU AI rules want the log behind every AI decision. That log is a re-run, and eight of its articles turn on it, from 2 December 2027. See the eight articles →
Where we fit.
One seal covers sixteen regulated sectors. Open a note for its use case file.
Live demo: strike and verify a receipt
Break it yourself.
Tamper one byte below and watch it void, or read how it works.
- org
- Specimen · non‑production
- control
- SEC 17a-4(f) · SR 26‑2
- case_id
- C-2317
- inputs
- decision_rules.v.yaml · features.jsonl · model.sha
- amount_cents
- 1000000
- committed
- re-derived
- bits matched
- bits changed
- hashes equal
Computing receipt...
What fails the re-run.
Four failures, each one named first by a standards body, a regulator, or a court. Each one fails the re-run on the spot.
Bring one record.
Any number you'd have to defend, or a whole workflow. It re-runs in front of you.
[email protected] Have your own team check a receipt first. veriker is open and free ↗Patents pending