Guide · Proof, Evidence, And Approval Control
AI work evidence: what a good AI audit trail looks like
AI work evidence is the owner-visible record of what an AI employee actually did: what it checked, why it acted or held, what changed, what it cost, what it learned, and whether accepted work reached an honest ending. Good evidence is what lets you decide whether Require approval stays on for one Action from proof instead of a promise; current safety floors still apply.
Why evidence beats a promise
It's easy to be told an AI “handled it”. Evidence is what turns that claim into something you can check. Without it, turning Require approval off is transferring risk you can't see. With it, you can make that decision for one Action from the record and catch a mistake early. Current safety floors still apply.
The six things good run evidence answers
- What it checked — the sources, records, and facts it looked at before acting.
- Why it acted or held — its reasoning and the rule it followed, or why it stopped and asked.
- What changed — the before-and-after of any draft, record, or action.
- What it cost — the model usage a run consumed, with a failed no-output run billing nothing.
- What it couldn't safely do — where it reached an untrusted edge, held, and asked instead of guessing.
- What it learned — the correction that became a durable rule, with before/after eval proof.
Evidence matters most when work is interrupted
Once Vavio accepts a job, it creates the run record before saying it is on it. If execution is interrupted, that accepted work stays under the same run and may retry from durable state where safe; it cannot silently become Completed. Every ending is measured against what the run promised — its ending record, evidence, usage, and delivery answers — and a run that could not keep part of its own record still ends, and says so on itself rather than hiding the gap. If bounded retries cannot finish it, the same run ends visibly failed with a receipt instead of disappearing.
An honest ending is not guaranteed success
This is a product contract for accepted work, not customer evidence, an uptime SLA, or a promise that every job will succeed. It also does not claim that every Connector and Channel has been live-walked through every interruption. The promise is narrower: accepted work must not vanish or be called complete without the required proof.
Evidence and approval control go together
The point of good evidence isn't paperwork — it's a defensible approval decision. Start with Require approval on, inspect what happened, and use the proof to decide whether it stays on for one Action. Current safety floors still apply independently, so turning it off never promises that oversight disappears.
The honest limit today
Inspectable evidence, not a compliance certificate
Vavio is pre-launch and has no formal enterprise compliance certifications (SOC 2 and the like) yet. The honest proof today is the run evidence itself, which you can inspect for every run — what it checked, why it acted or held, what changed, what it cost, and what it learned. If your requirement is a certified enterprise audit right now, that's not something Vavio can prove yet.
Frequently asked questions
- What is AI work evidence (or AI run evidence)?
- The owner-visible record of a piece of AI work: what it checked, why it acted or held, what changed, what it cost, what it couldn't safely do, and what it learned. It's the audit trail that lets you trust — or correct — the work without watching every run.
- What happens to the evidence if an AI run is interrupted?
- Once Vavio accepts a job, the same run remains the record of that work. It may retry from durable state where safe, or end visibly failed with a receipt if bounded retries cannot finish it. Every ending is measured against what the run promised, and a run that could not keep part of its own record still ends, and says so on itself rather than hiding the gap. That is not a promise every job succeeds; it prevents accepted work from disappearing or being called done without proof.
- Why does run evidence matter before turning Require approval off?
- Because turning Require approval off without evidence is just risk transfer. Evidence lets you see why the employee acted, catch a mistake, and decide from proof while current safety floors still apply.
- What should good AI run evidence include?
- Six things: what it checked, why it acted or held, what changed (before and after), what it cost, what it couldn't safely do, and what it learned. If a tool can't show you those, you're trusting a promise, not evidence.
- Does Vavio have formal audit certifications?
- Not yet — Vavio is pre-launch and has no formal compliance certifications like SOC 2. The honest proof today is the run evidence itself, which you can inspect for every run. If you need a certified enterprise audit right now, that's not something Vavio can prove yet.
Keep reading
Hire your first AI employee
Brief one real job in plain English, watch it prepare the held draft, and approve the exact message. Free to start — no card needed.