Verification for AI and automation that can act

Keep automated actions tied to the approval behind them.

For product teams adding AI actions to workflows with approvals, queues, and retries. DVS is designed to check that an action still matches its authorization at the last controllable point before execution. Start with one action path in your existing application.

Checking evaluation availability…

Evaluate one action path Review the evidence

Illustrative scenario — not a customer record within approval

Original approval

Refund up to$500.00

RecipientCUST #4417

Proposed action Refund$ Recipient

Example decisionillustrative

ProposedRefund $500.00 → CUST #4417

ApprovedRefund ≤ $500.00 → CUST #4417

Limits intactYES

Released in this illustrationPermitted

Recorded test evidence

See which requests reached the target.

These controls show recorded results from local tests and a test between two computers, all controlled by the founder. They do not run DVS or display live customer activity.

Client / agentTool requestLocal test

Final checkDVSapproval check

Receiving systemProtected toolcount: 1

Public outcomeAllow Receiving system1 call Recorded resultThe allowed request reached the tool once.

Recorded local test: the valid request reached the tool once. Changed approval, missing approval and reuse attempts reached it zero times. This is development evidence.

First computerFinal checkdecision

Second computerReceiverarrivals: 1

Protected targetEXECUTEDexecutions: 1

Remote receiver1 Protected target1 Recorded test6 June 2026

In this controlled test, the allowed request reached the receiving computer and target once. The blocked request reached neither. This does not establish production use, public-internet deployment, certification or independent validation.

Further recorded results and their limits are on the Evidence page.

When approval and action differ

An approved action can change before it happens.

An automated request may wait in a queue, be changed by another step, or be sent again after a failure. The final request needs to stay within the original approval.

A service may have permission to issue refunds while a particular refund exceeds its approval. Your existing controls may already prevent that; the first step is to find out.

DVS is designed to compare the proposed action with its approval before passing it on. Start with one workflow where your team owns that final step.

Where it matters

For teams adding actions to their products.

AI actions

A product assistant proposes a record change, refund or account update. Check that the action sent to the application still matches what was allowed.

Actions that happen later

A person or rule approves an action, then automation carries it out later. Delays, changes and retries are the reason to check again.

Current status

Initial in-house tests complete Broader testing underway No customer pilot or revenue established Claims follow the evidence →

Bring one approved action. Agree on a comparison with your existing controls before adding software.

Evaluate one action path See how an evaluation works