WHAT TO TESTTest refunds, account changes and escalations.
Refunds, account changes, system writes and escalations each carry a different boundary. Choose the one your agent needs to respect.
$750 + $500$1,250 total
Configured limit: $1,000Cumulative limit exceeded
Illustrative testCumulative concessionsRefunds & credits
A locally reasonable credit can break a cumulative limit. Include earlier concessions in the same evaluation.
What evidence makes this inspectable?
Earlier credits, the next write, the configured ceiling and the resulting total.
Scenario coverage and the available interface are scoped before connecting an agent. This is not a promise of a prebuilt integration.
New destinationVerification missing
Verify before the actionInspect the supporting evidence
Illustrative testDestination integrityAccount & destination changes
A customer introduces a new destination. Check that the agent establishes the required verification before using it.
What evidence makes this inspectable?
The verified destination, requested change, verification evidence and actual destination used.
Scenario coverage and the available interface are scoped before connecting an agent. This is not a promise of a prebuilt integration.
Evidence → writeSequence matters
Required evidence comes firstConnect each action to its basis
Illustrative testEvidence before writesConsequential writes
A refund or account update can succeed technically while lacking the evidence required by policy.
What evidence makes this inspectable?
The required evidence, when it became available and the ordered write trace.
Scenario coverage and the available interface are scoped before connecting an agent. This is not a promise of a prebuilt integration.
Handoff requiredStill unresolved
Follow-up does not clear the ruleKeep the condition in view
Illustrative testEscalation persistenceEscalations & handoffs
A follow-up request must not silently remove a required escalation. Check the state across the conversation.
What evidence makes this inspectable?
The escalation trigger, subsequent messages, unresolved condition and any restricted action.
Scenario coverage and the available interface are scoped before connecting an agent. This is not a promise of a prebuilt integration.
Which action would you
want to test first?
Start with a workflow, a boundary and an inspectable trace.