Recovery-Integrity Check

What does your agent do when its OWN workflow breaks halfway?

An agent runs a multi-step side-effecting workflow. Step 1 succeeds — money debited, a row deleted, an external email sent, an external API committed — then a later step fails or the agent abandons the plan, and it leaves the world in a half-committed, inconsistent state with no compensating / rollback action: an orphaned irreversible side-effect, money moved without the matching order, a delete with no restore, a partial saga with no compensation. Transaction-integrity grades the stale-read→act race BEFORE the action, action-idempotency grades DUPLICATE execution, approval-discipline grades the GATE, capability grades CO-OCCURRENCE — none grade orphaned side-effects after a partial failure. AgentSmack scores a compensating-action / saga-rollback transcript for exactly this — surfacing the committed→failure→ (missing) compensation lineage as evidence, mapped to OWASP LLM / NIST AI RMF coverage with paste-able remediation, a synthetic-attacker gauntlet, and audience report variants. A complete, correctly-LIFO compensation set after an abort scores clean. Load a sample to watch the gauge swing with no live infra.