Agentic AI · Service operations
Refund Assurance — the system that reopens a case when “refund processed” was a lie
When an AI service session closes with “your refund has been processed,” this agent waits out the processing window, checks Order Management, and reopens the case — only on confirmed failure.
The problem
Async refunds fail silently at the gateway; the session still counts as resolved, and nobody knows until the customer calls back.
- TypeScript
- React
- Zod
- Vitest
- Playwright
Live demo Architecture & README
The proof
73/73
tests passing
1
bounded, idempotent, permission-checked write
8
step pipeline with independent read-after-write proof
- Session-resolved eventFires when an AI support session closes.
- Promise extractorFinds refund promises in the closing message, using rules.
- Policy engineDecides from fixed rules whether the refund needs action.
- openRefundExceptionThe only mutating tool: bounded, idempotent, permission-checked.
- Read-after-write verifierRe-reads the order to confirm the failure is real.
Silently closed caseOwned recovery case (v7 → v8, audit-logged)
ScopeSalesforce-style systems simulated and labeled; no model called at runtime — the LLM slot is a proven, schema-guarded boundary.