# Agent recovery and compensation matrix

**Version:** 1.0
**Last updated:** 2026-11-16
**Source:** KLA Digital (kla.digital/blog/ai-agent-rollback-recovery-compensation)

---

## About this matrix

Use this matrix when an AI agent run stops after a consequential tool call: a booking, a payment,
a record update or a message sent to another system. It classifies each external action by what
the available evidence establishes, names the recovery step to assess, and records who owns the
remaining obligation.

Research date: 26 October 2026. The matrix is editorial guidance informed by these sources, read
at the stated versions:

- Guo, Chen, Vaswani, Paverd and Pietzuch, *Planarian* (arXiv 2609.35366v1, 28 September 2026),
  sections 3 to 7. https://arxiv.org/html/2609.35366v1
- Wang and Qi, *Recoverability and Verifier Strength* (arXiv 2610.27465v1, 20 October 2026),
  sections 5 and 6 and Appendix C. https://arxiv.org/html/2610.27465v1
- Xiao et al., *When Harnesses Lose the Signal* (arXiv 2610.00372v1, 30 September 2026).
  https://arxiv.org/html/2610.00372v1
- Perera, Hapuarachchi, Leymann and Khalaf, *Robust Agent Compensation* (RAC, arXiv 2605.03409v2,
  18 May 2026), and its public repository at commit `068c327ab3f9b79a86a39503946e26320b74b97a`.
  https://github.com/wso2-incubator/research-rac/tree/068c327ab3f9b79a86a39503946e26320b74b97a
- Zheng, Yang, Zhang and Quinn, *ACRFence* (arXiv 2603.20625v1, 21 March 2026).
  https://arxiv.org/html/2603.20625v1

All five papers are preprints. Their results are the authors' own.

Assumptions and limits:

- Each provider's operation and cancellation contract determines which recovery actions exist.
  The matrix assumes no action can be undone by default.
- The provider, bank, carrier or other external system is the authoritative source for whether an
  effect committed. A local success flag establishes only the condition its implementation defines.
- The matrix has not been validated experimentally and is not a KLA product specification. The
  worked example below is synthetic.
- Our own check of the RAC core (21 upstream tests and six local SQLite scenarios, 26 October 2026)
  informed the "uncertain outcome" and "compensation failed" rows. It used no language model, paid
  API or live provider, and it does not reproduce the RAC paper's benchmarks.

## Decision matrix

| What the available evidence establishes | Record this state | Recovery step to assess | Evidence needed for closure |
| --- | --- | --- | --- |
| Provider confirms rejection and no effect | Known absent | Retry under the same intended action and valid authority | Provider receipt for the eventual outcome |
| Provider confirms a committed effect with an available compensation operation | Known committed; compensation available | Obtain any required authorization and perform compensation | Provider-confirmed corrective result and remaining obligations |
| Call timed out after dispatch and no authoritative outcome is available | Uncertain outcome | Query provider status or reconcile before deciding whether a retry is safe | Provider state tied to the original request identity |
| Compensation was rejected, expired or timed out | Compensation failed or uncertain | Assign a responsible operator and an appropriate corrective process | Confirmed resolution or an explicitly recorded residual obligation |
| Consequence persists beyond available undo operations | Persistent consequence | Record impact and determine an authorized remedy | Accountable decision and evidence of the remedy's outcome |

## Record for each affected action

| Field | Entry |
| --- | --- |
| Workflow and action identity | |
| Intended business effect | |
| Provider and authoritative status source | |
| Original request identity and dispatch time | |
| Receipt, or the reason the outcome remains uncertain | |
| Current classification from the matrix | |
| Proposed recovery operation | |
| Recovery authorization and expiry, where applicable | |
| Recovery receipt and observed provider state | |
| Remaining obligation or residual impact | |
| Responsible role, next action and review time | |
| Closure evidence | |

Keep the original action and every corrective action in the same incident record. Verify the
business outcome against the provider's authoritative state before closing an obligation.

## Worked example (synthetic)

A fictional procurement agent reserves stock, books transport and updates an order. The transport
service accepts the booking, then the connection drops before the receipt reaches the agent. The
agent's workspace is restored to its last checkpoint. All names and identifiers below are invented.

| Action | Evidence at the failure boundary | Classification | Recovery step | Owner and closure evidence |
| --- | --- | --- | --- | --- |
| Stock reservation `RES-0417` | Warehouse receipt confirms the reservation | Known committed; compensation available | Keep it if the order proceeds; release it under the warehouse's release operation if the order is cancelled | Procurement operations; warehouse state matches the accepted order |
| Transport booking, request `TRN-REQ-88` | Request dispatched; no receipt; connection dropped | Uncertain outcome | Query the carrier for request `TRN-REQ-88` before any new booking request | Logistics operator; carrier status for the original request identity |
| Transport cancellation, after the carrier confirms booking `BK-5521` | Carrier rejects cancellation after the dispatch cut-off | Compensation failed | Start the carrier's return process under a separate authorization | Logistics lead; return confirmation or a recorded residual cost |
| Order update `ORD-2290` | Order system shows no write | Known absent | Retry with the same intended change once transport status is settled | Order system owner; order record matches the final transport state |

Closure for this run requires evidence that the stock reservation and transport booking match the
accepted order, or that each remaining obligation has an owner, a next action and a review time.
Restoring the agent's workspace gives it a place to continue. The record above shows what the
organization still owes, owns or needs to correct.
