Know what needs attention.
See the exact missing source, test result or approval—not just an unexplained hold.
Evidence and approval for AI-agent work
AI can do the work.Decide what
gets accepted.
Know what is ready to use—and what still needs attention. Agent Assurance Core (AAC) is being developed to bring an agent’s work, its required checks and the right approval into one review.
AAC is in development.
Try the interactive demo. It uses fictional data and takes no live actions.
Find the review that matters to your team.
Evidence with the work
Approval by the right person
Your acceptance requirements
A record with reasons
SEE AAC IN MOTION
See what happens before
work moves forward.
Watch the work happen, see exactly why it stops, then take control of the evidence, checks and approval.
See the reason for the decision. Then test a different outcome.Test the evidence and approval ↗Watch the 36-second film ▷
What changes for your team
Less chasing.
A clearer decision.
The aim is to spend less time finding the evidence and more time deciding what it means. Evaluate whether AAC improves that review in your workflow.
Estimate the value to your team ↗Review the work and evidence together.
Keep the version under review, its requirements, supporting records and responsible reviewer together.
Know which version was accepted.
Keep the reason for the earlier decision. Require a fresh review when the work changes.
When human approval is required
Some decisions
stay human.
Work submitted
Evidence checked
Requirements met
Platform lead review
Checks complete.
Approval still required.
02Your requirements. Your reviewers.
More automation.
Not less accountability.
Let agents prepare the work. Define the evidence it needs and the decisions your people must still make.
01
Agree what ready means.
Specify the output, its limits and the checks needed before the next action.
02
See what each check covers.
A passing test may cover one requirement while leaving another unresolved.
03
Keep the required approval.
A passing check must not skip a decision reserved for your reviewer.
03 / Find your workflow
Beyond code.
Reviews across the business.
Explore 18 application examples, from releases and invoices to customer messages. See the work, the missing evidence and the person responsible for approval.
+ requireAuthenticatedUser(request); + return next(request); // Protected endpoint: /account // Required unauthenticated result: 401
SEC-14 Evidence outstanding
Purchase order | PO-084 | MATCHED Invoice | INV-218 | MATCHED Invoice total | GBP 4,800 | MATCHED Goods received | GR-084 | MISSING
REC-03 Evidence outstanding
Subject: Service incident update We are investigating increased latency. The next update is scheduled in one hour. Approved incident-source snapshot: MISSING
SRC-05 Evidence outstanding
Engineering & IT3 workflows↗Finance & procurement3 workflows↗Customer operations3 workflows↗Data & knowledge3 workflows↗Commercial & legal3 workflows↗Operations & assurance3 workflows↗
Explore all 18 use cases
These are application examples to evaluate, not a list of available production integrations.
04Where the check belongs
Put the boundary
where the work
becomes consequential.
Your agent produces the output. AAC’s proposed role is to check its acceptance requirements. Your connected system must use that decision before it releases, posts or sends the work.
Select a component to see what it does.
Proposed integration
Check readiness before action.
AAC is intended to connect the work with its requirements, evidence and approvals. The system taking the next action must check that the decision is current and applies to this version.
05Evidence behind the decision
A decision should
come with its reasons.
What was required? What was checked? Who approved it? Which version did they review?
Those are the questions AAC is designed to answer in the decision record, so a reviewer can see the basis for acceptance.
AAC / Decision record
A decision you can examine.
Example record · software release
Work itemREL-042
Version under reviewauth-patch-v1
Acceptance policyrelease-policy-v1
Required approverPlatform lead · simulated
DecisionACCEPTED · example
Next actionNot executed
Demo record · unsigned · not independent assurance
Inspect the example record →Start with your workflow
Bring one workflow
that matters.
Bring an example output, the action that follows and the person responsible for approval. Use the first conversation to decide whether a focused evaluation makes sense.
Discuss fit, required evidence and the next step. No rollout commitment.