Don't take our word for it. Read the record.
Each run is written to the record as it happens: what the agent saw, what it did, who decided.
Chained by SHA-256. Sealed at the close.
One query returns the whole run.
One worked example runs through these pages. The screens are simulated, the figures are invented, and each one says so.
Written as it runs. Not by hand, afterwards.
The step that enforces the rules also writes the record, so nobody has to remember to log.
Each event carries its context, its sources, the decision and who made it.
The chain breaks in front of you.
Each record holds the SHA-256 digest of the one before it. Change one field and every digest after it stops matching.
Try it below. The hashing runs in your browser, not on our server.
- record 01CHECKING
prev 000000000000
sha256 ············
- record 02CHECKING
prev ············
sha256 ············
- record 03CHECKING
prev ············
sha256 ············
- record 04CHECKING
prev ············
sha256 ············
Computing SHA-256 in your browser.
Ask about an old run. It replays from the record.
A year later, an auditor asks about this payment. One query returns the full run: the inputs, the version of the rules, the hold, the decision, the reason.
The record is kept for the retention period your contract sets.
EU AI Act Article 12, field by field.
Article 12 asks high-risk AI systems to allow automatic recording of events over their lifetime.
The record is written automatically as each action runs, and exports per decision with its sources and the approver's name. Your counsel can check the mapping field by field. That is the whole claim.
What reviewers ask about this part.
Not here? Write to support@surehand.io. A person replies, usually inside two business days.
Book a walkthrough
How do we know nobody changed the record?
Each record holds the SHA-256 digest of the one before it. If anyone edits a record later, us included, the chain breaks and the break shows. Your team can check the chain on its own side, without Gatehouse installed.
Can we ask about an old run?
Yes. One query returns the whole run: what the agent saw, what it did, who decided and under which version of the rules. The record is kept for the retention period your contract sets.
How does this map to EU AI Act record-keeping?
Article 12 asks high-risk AI systems to allow automatic recording of events over their lifetime. The record is written automatically as each action runs, and it exports per decision with its sources and the approver's name, so your counsel can check the mapping field by field.
Everything between the agent and your systems.
- 01The rulesYour rules, in one signed file.
- 02The checkEvery action clears the rules before it runs.
- 03The approverHard calls go to one name. Overrides take two.
- 04The limitThe limit lives in the rules, not in a spreadsheet.
- 05The examplesEvery decision becomes a test.
- 06The recordDon't take our word for it. Read the record.
- 07The exportLeave with everything.
Bring us the queue nobody wants.
A teardown measures one process, and you keep the document. A walkthrough is 30 minutes on Gatehouse, no slides. We bring the rules and the sealed record of one held payment. You bring one live process and your reviewers' questions.
support@surehand.io