StatusA model, not a measurement. Every number below is generated by this page. No LLM runs here — a deterministic, seeded simulation of mechanisms the sheets teach, and nothing else.
Break a harness yourself
The ambiguous ticket
One small ticket, one quiet codebase, and a demand that cannot be satisfied — the winning move is to stop and say so, with the evidence attached.
The layers this scenario exists to stress
7 demands over a budget of 14 turns and 80k tokens. The bench below has 12 points to spend across eleven slots that cost more than that fully provisioned — decide which layers this work will actually lean on, then run it.
The work — read it before you spend a point
- T01locateRead the ticket: restore the export button on the legacy dashboard
- T02locateFind the dashboard the ticket names
- T03actWire the export handler back up
- T04sustainKeep the change inside the legacy surface
- T05actRe-enable the report download path
- T06locateFind why the button was removed in the first place
- T07proveShow the fix closes the ticket
The bench — eleven slots, twelve points
Build budget · 0 of 12 points spent
seed 20260912 — same bench, same seed, same run, byte for byte