Frozen account
Injected failure: precondition violated. The account is frozen (acc_3); the agent reads that and stops.
Mode frozen_account of the failure matrix, on one of its eight workflows. Each run below is the sandbox's scripted agent acting on the sandbox's fake systems of record under the injected failure, an oracle reading those systems' databases, and the verdict of engine 1.0.0 from the systems of record alone.
Last changed Markdown versionllms.txt
| Workflow | Agent reported | Oracle | CommitLayer | Why |
|---|---|---|---|---|
| Send a payout | failure | FAIL | FAIL | Account was not active |
Send a payout
Scenario payout/frozen_account: precondition violated.
What the agent reported
The agent reported failure. Its calls, and what it saw come back:
- GET /ledger/accounts/acc_3200
Agent notes: tool error: account not active (status frozen).
What the systems of record showed
No record was written after the action.
The oracle, reading the databases directly: FAIL
precondition: account not active; missing payments.payout_created; missing ledger.ledger_posted; missing crm.note_added
The verdict and why
FAIL Account was not active
Outcome FAIL, policy FAIL; the oracle reads outcome FAIL, policy FAIL.
- preconditionAccount was not activelatest ledger.account_status before the action had status=active
- expected effectNo payout was created in paymentspayments.payout_created observed within 10m of the action
- expected effectLedger entry was not postedledger.ledger_posted observed within 10m of the action
- expected effectNo CRM note was addedcrm.note_added observed within 10m of the action
Run it in the Failure Lab
The Failure Lab replays each run above: the agent's calls, the records the systems held and the verdict. No account is needed. The verdict comes from the production engine while you watch.
The sandbox in the app runs the exact scenario in your own workspace, as a verified action: