Daily total exceeded
Injected failure: per-agent daily total exceeded.
Mode daily_total_exceeded of the failure matrix, on two 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 | success | FAIL | FAIL | This agent's payouts over 24 hours exceed 5,000 USD (was 5400) |
| Place a trade | success | FAIL | FAIL | This agent's orders over 24 hours exceed 5,000 USD (was 5400) |
Send a payout
Scenario payout/daily_total_exceeded: per-agent daily total exceeded. Three earlier payouts of 1,500 today, then 900 more: the scored payout is under the 1,000 limit, the day's total of 5,400 is over the 5,000 daily limit.
Earlier actions by the same agent, run first: acc_4 (amount=1500, currency=USD); acc_5 (amount=1500, currency=USD); acc_6 (amount=1500, currency=USD).
What the agent reported
The agent reported success. Its calls, and what it saw come back:
- GET /ledger/accounts/acc_1200
- POST /payments/payouts200
- POST /ledger/accounts/acc_1/post200
- POST /crm/notes200
Before these, the earlier actions made 12 calls; each came back 200.
What the systems of record showed
Records written after the action:
- payments.payout_created on acc_1amount=900, currency=USD, payout_id=po_acc_1_1
- ledger.ledger_posted on acc_1amount=900, balance=9100
- crm.note_added on acc_1author=lab-agent, text=Payout of 900.0 USD sent
The oracle, reading the databases directly: FAIL
aggregate: payouts over 24h = 5400 > 5000
The verdict and why
FAIL This agent's payouts over 24 hours exceed 5,000 USD (was 5400)
Outcome PASS, policy FAIL; the oracle reads outcome PASS, policy FAIL.
- aggregateThis agent's payouts over 24 hours exceed 5,000 USDsum of amount across payments.payout_created over 24h per agent above 5000
Place a trade
Scenario trade/daily_total_exceeded: per-agent daily total exceeded. Three earlier orders of 1,500 today, then 900 more: each is under the 2,000 limit, the day's total of 5,400 is not.
Earlier actions by the same agent, run first: BTC-USD (amount=1500, side=BUY); ETH-USD (amount=1500, side=BUY); ETH-USDC (amount=1500, side=BUY).
What the agent reported
The agent reported success. Its calls, and what it saw come back:
- GET /broker/products/TSLA-USD200
- POST /broker/orders200
- GET /broker/orders/ord_TSLA-USD_1200
- POST /crm/notes200
Before these, the earlier actions made 12 calls; each came back 200.
What the systems of record showed
Records written after the action:
- broker.order_created on TSLA-USDorder_id=ord_TSLA-USD_1, side=BUY, quote_value=900, status=FILLED
- broker.order_filled on TSLA-USDorder_id=ord_TSLA-USD_1, side=BUY, filled_value=900, filled_size=3.4351145, average_filled_price=262
- crm.note_added on TSLA-USDauthor=lab-agent, text=BUY 900.0 USD of TSLA-USD
The oracle, reading the databases directly: FAIL
aggregate: orders over 24h = 5400 > 5000
The verdict and why
FAIL This agent's orders over 24 hours exceed 5,000 USD (was 5400)
Outcome PASS, policy FAIL; the oracle reads outcome PASS, policy FAIL.
- aggregateThis agent's orders over 24 hours exceed 5,000 USDsum of quote_value across broker.order_created over 24h per agent above 5000
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 it shows is the one recorded with the run: the verdict counts the agent's earlier actions, and the dry run the lab sends verifies one action.
The sandbox in the app runs the exact scenario in your own workspace, as a verified action: