Order not filled
Injected failure: order accepted but never filled, agent claims success. The order on DOGE-USD is accepted and rests open with no fill; the agent reports the trade done.
Mode leg_not_filled 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 |
|---|---|---|---|---|
| Place a trade | success | FAIL | FAIL | The order did not fill: it was placed but no trade happened |
Place a trade
Scenario trade/leg_not_filled: order accepted but never filled, agent claims success.
What the agent reported
The agent reported success. Its calls, and what it saw come back:
- GET /broker/products/DOGE-USD200
- POST /broker/orders200
- GET /broker/orders/ord_DOGE-USD_1200
Agent notes: tool error: order not filled (status OPEN).
What the systems of record showed
Records written after the action:
- broker.order_created on DOGE-USDorder_id=ord_DOGE-USD_1, side=BUY, quote_value=50, status=OPEN
The oracle, reading the databases directly: FAIL
missing broker.order_filled; missing crm.note_added
The verdict and why
FAIL The order did not fill: it was placed but no trade happened
Outcome FAIL, policy FAIL; the oracle reads outcome FAIL, policy FAIL.
- expected effectThe order did not fill: it was placed but no trade happenedbroker.order_filled 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: