Autonomy is earned, not assumed.
Every run is recorded the same way: what happened, why, with which data and who approved it.
Approvals are concrete
A real action, waiting on a named human.
Refund €1,180 · Bergmann AG
Policy allows up to €1,500 · invoice #4411 matched · reason: duplicate charge
gates you pin stay human forever · no run can skip them
Every run is replayable
Inputs, outputs, decisions, tool calls, version.
▸ trigger invoice.csv · 3 rows
✓ parse 3 records · 0.3s
✓ match 2 exact · 1 fuzzy · 0.4s
◆ judgment “Meridian ≈ Meridian Grp” · 2.1s
⏸ gate approved · L. Krug · 38m
✓ post ledger + slack · 0.2s
run #1,284 · v12replay ▸
Failures explain themselves
The exact step, a plain diagnosis, two ways forward.
Step S3 failed · 14 runs queued
The vendor portal changed its upload form. A patched step already passed 3 replays of past examples.
queued work waits and flows through the fixed version
In place today, or marked as planned.
Talk to us about security →isolated executionaccess scoped to the process ownerimmutable audit trailversion historystaging & productionhuman approval policysafe retriesSSO & RBAC · planneddata residency · planned
Bring your security questions. We answer in plain language.
Thirty minutes with the people who built the runtime — honest answers about what is shipped and what is planned.
Book a discovery call