Know what is still missing.
Make the outstanding condition specific: a source, a test result, a scope check or an approval.
Acceptance assurance for agentic work
AI can do the work.Decide what
gets accepted.
Your agents produce the work. AAC’s acceptance model brings the evidence, policy and human authority together before that work moves forward.
AACWORKSPACE / SOFTWARE DELIVERY
REL-042 / CANDIDATE 01
Repair authentication regression
Evidence & requirements
POLICY / release-policy-v1INTERACTIVE EXAMPLE · NO RELEASE
A product concept for decisions that matter.
No live agent or production connection in this preview.
One acceptance model. Many kinds of work.
Evidence before acceptance
Explicit human authority
Policy-bound decisions
Inspectable records
01 / Watch the work, not a promise
A workflow.
A decision that matters.
Follow the agents, inspect the evidence, and see the exact moment a human decision is required. Then take control of the example.
Interactive workflow story
Follow the work.
Examine the decision.
Enable JavaScript to play or control this illustrative workflow. The worked-example pages below remain readable.
A proposed output starts the review. It does not finish it.
01 / 0600:00 / 00:36
Fictional workflow. Agent activity, evidence, checks and approval are simulated. No downstream action is executed.
Read the story without motion
Watch the story. Change the outcome. Inspect the record.Open the detailed evidence workbench ↗Watch the captioned film ▷
What changes for your team
Less reconstruction.
More informed decisions.
The value to test is not another approval screen. It is a clearer handoff between proposed work and an accountable decision.
Build your evaluation case ↗Review the work with its context.
Bring the candidate, policy, evidence and named authority into one inspectable handoff.
Keep the decision with the version.
Preserve why work was accepted without letting changed work inherit that acceptance.
Authority / reserved
Some decisions
stay human.
Candidate submitted
Evidence checked
Requirements met
Platform lead review
Checks complete.
Approval still required.
02People. Policy. Evidence.
More automation.
Not less accountability.
An agent can prepare the work. The acceptance conditions should still say what evidence is needed—and which decisions remain with a person.
01
Define the conditions before the decision.
Make the requirements, permitted scope and next action explicit.
02
Bring the evidence into view.
Distinguish a passing check from everything needed for acceptance.
03
Keep authority where it belongs.
Reserve human approval when the workflow calls for it.
03 / Find the decision in your work
Not just code.
Work across the business.
Explore 18 concrete evaluation patterns. Each one shows the proposed output, the acceptance gap, the human owner and the benefit to measure.
+ 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 Amount | 4,800 units | 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
Proposed application patterns, not customer deployments or a claim of production support.
04The integration boundary
Put the boundary
where the work
becomes consequential.
Producing work, accepting it and executing the next action are separate responsibilities. Make the hand-off between them explicit.
Select a component to inspect its responsibility.
Intended architecture
Make acceptance explicit.
AAC’s proposed role is to relate a candidate to its requirements, evidence, checks and reserved approvals. The connected downstream system must enforce the decision.
05Trust you can examine
A decision should
come with its reasons.
What was required? What was checked? Who approved it? Which candidate does the decision apply to?
AAC’s intended model makes those questions part of the record—not a reconstruction after the fact.
AAC / Assurance record
A reason to move forward.
Example record · software-release scenario
Work itemREL-042
Candidateauth-patch-v1
Acceptance policyrelease-policy-v1
Required authorityPlatform lead · simulated
DecisionACCEPTED · example
Downstream effectNot executed
Inspectable example. Unsigned. No attestation.
Inspect a working decision record →A clearer line for agentic work
Bring one workflow
that matters.
Start where an agent’s output becomes your organisation’s responsibility. Define what has to be true before it moves forward.
A focused technical conversation. An explicit next step.