Understand the failure.
Verify the repair.
Small, reproducible software failures. The broken implementation, the fix that didn’t work, and the one that passed—preserved together.
Explore the cases ↓How results are verified ↗WHAT THE ARCHIVE CONTAINS
100840 executable cases. 20168 are open.
Every case records the implementation that fails, the fix that did not work, and the repair that passed its checks—with recorded outputs and source hashes. This release adds 100840 cases across 20168 failure mechanisms and 254 domains.
The open tier gives you the failure and the unsuccessful fix for one case in every mechanism. The remaining 80672 cases, 5 variants per mechanism, are member-only: the verified repair, its recorded checks, and the full fixture suite are held in the member archive. Read the methodology ↗
A RECORD OF WHAT WENT WRONG
Browse the archive / 100840
Nested client render failure boundaries: Render only catch · case 01
Render only catch.
Nested client render failure boundaries: Render only catch · case 02
Render only catch.
Nested client render failure boundaries: Render only catch · case 03
Render only catch.
Nested client render failure boundaries: Render only catch · case 04
Render only catch.
Nested client render failure boundaries: Render only catch · case 05
Render only catch.
Nested client render failure boundaries: Unhandled root escalation · case 01
Unhandled root escalation.
Nested client render failure boundaries: Unhandled root escalation · case 02
Unhandled root escalation.
Nested client render failure boundaries: Unhandled root escalation · case 03
Unhandled root escalation.
Nested client render failure boundaries: Unhandled root escalation · case 04
Unhandled root escalation.
Nested client render failure boundaries: Unhandled root escalation · case 05
Unhandled root escalation.
Nested client render failure boundaries: Capture path inside out · case 01
Capture path inside out.
Nested client render failure boundaries: Capture path inside out · case 02
Capture path inside out.
Nested client render failure boundaries: Capture path inside out · case 03
Capture path inside out.
Nested client render failure boundaries: Capture path inside out · case 04
Capture path inside out.
Nested client render failure boundaries: Capture path inside out · case 05
Capture path inside out.
Nested client render failure boundaries: Reported error dedup · case 01
Reported error dedup.
Nested client render failure boundaries: Reported error dedup · case 02
Reported error dedup.
Nested client render failure boundaries: Reported error dedup · case 03
Reported error dedup.
Nested client render failure boundaries: Reported error dedup · case 04
Reported error dedup.
Nested client render failure boundaries: Reported error dedup · case 05
Reported error dedup.
Nested client render failure boundaries: Boundary disabled fallback · case 01
Boundary disabled fallback.
Nested client render failure boundaries: Boundary disabled fallback · case 02
Boundary disabled fallback.
Nested client render failure boundaries: Boundary disabled fallback · case 03
Boundary disabled fallback.
Nested client render failure boundaries: Boundary disabled fallback · case 04
Boundary disabled fallback.
Nested client render failure boundaries: Boundary disabled fallback · case 05
Boundary disabled fallback.
Nested client render failure boundaries: Reset clears handled marker · case 01
Reset clears handled marker.
Nested client render failure boundaries: Reset clears handled marker · case 02
Reset clears handled marker.
Nested client render failure boundaries: Reset clears handled marker · case 03
Reset clears handled marker.
Nested client render failure boundaries: Reset clears handled marker · case 04
Reset clears handled marker.
Nested client render failure boundaries: Reset clears handled marker · case 05
Reset clears handled marker.
Nested client render failure boundaries: Event error propagation · case 01
Event error propagation.
Nested client render failure boundaries: Event error propagation · case 02
Event error propagation.
Nested client render failure boundaries: Event error propagation · case 03
Event error propagation.
Nested client render failure boundaries: Event error propagation · case 04
Event error propagation.
Nested client render failure boundaries: Event error propagation · case 05
Event error propagation.
Incremental client response projection: Append only unseen chunks · case 01
Append only unseen chunks.
Incremental client response projection: Append only unseen chunks · case 02
Append only unseen chunks.
Incremental client response projection: Append only unseen chunks · case 03
Append only unseen chunks.
Incremental client response projection: Append only unseen chunks · case 04
Append only unseen chunks.
Incremental client response projection: Append only unseen chunks · case 05
Append only unseen chunks.
Incremental client response projection: Render budget prefix · case 01
Render budget prefix.
Incremental client response projection: Render budget prefix · case 02
Render budget prefix.
Incremental client response projection: Render budget prefix · case 03
Render budget prefix.
Incremental client response projection: Render budget prefix · case 04
Render budget prefix.
Incremental client response projection: Render budget prefix · case 05
Render budget prefix.
Incremental client response projection: Cursor advances by consumed count · case 01
Cursor advances by consumed count.
Incremental client response projection: Cursor advances by consumed count · case 02
Cursor advances by consumed count.
Incremental client response projection: Cursor advances by consumed count · case 03
Cursor advances by consumed count.
Incremental client response projection: Cursor advances by consumed count · case 04
Cursor advances by consumed count.
Incremental client response projection: Cursor advances by consumed count · case 05
Cursor advances by consumed count.
Incremental client response projection: Cancel freezes visible text · case 01
Cancel freezes visible text.
Incremental client response projection: Cancel freezes visible text · case 02
Cancel freezes visible text.
Incremental client response projection: Cancel freezes visible text · case 03
Cancel freezes visible text.
Incremental client response projection: Cancel freezes visible text · case 04
Cancel freezes visible text.
Incremental client response projection: Cancel freezes visible text · case 05
Cancel freezes visible text.
Incremental client response projection: Finished but buffered state · case 01
Finished but buffered state.
Incremental client response projection: Finished but buffered state · case 02
Finished but buffered state.
Incremental client response projection: Finished but buffered state · case 03
Finished but buffered state.
Incremental client response projection: Finished but buffered state · case 04
Finished but buffered state.
Incremental client response projection: Finished but buffered state · case 05
Finished but buffered state.
Incremental client response projection: Empty chunk consumes position · case 01
Empty chunk consumes position.
Incremental client response projection: Empty chunk consumes position · case 02
Empty chunk consumes position.
Incremental client response projection: Empty chunk consumes position · case 03
Empty chunk consumes position.
Incremental client response projection: Empty chunk consumes position · case 04
Empty chunk consumes position.
Incremental client response projection: Empty chunk consumes position · case 05
Empty chunk consumes position.
Incremental client response projection: Unconsumed tail after frame · case 01
Unconsumed tail after frame.
Incremental client response projection: Unconsumed tail after frame · case 02
Unconsumed tail after frame.
Incremental client response projection: Unconsumed tail after frame · case 03
Unconsumed tail after frame.
Incremental client response projection: Unconsumed tail after frame · case 04
Unconsumed tail after frame.
Incremental client response projection: Unconsumed tail after frame · case 05
Unconsumed tail after frame.
Incremental client response projection: Completion event once drained · case 01
Completion event once drained.
Incremental client response projection: Completion event once drained · case 02
Completion event once drained.
Incremental client response projection: Completion event once drained · case 03
Completion event once drained.
Incremental client response projection: Completion event once drained · case 04
Completion event once drained.
Incremental client response projection: Completion event once drained · case 05
Completion event once drained.
Incremental client response projection: Render frame needed · case 01
Render frame needed.
Incremental client response projection: Render frame needed · case 02
Render frame needed.
Incremental client response projection: Render frame needed · case 03
Render frame needed.
Incremental client response projection: Render frame needed · case 04
Render frame needed.
Incremental client response projection: Render frame needed · case 05
Render frame needed.
Incremental client response projection: Abort discards buffered suffix · case 01
Abort discards buffered suffix.
Incremental client response projection: Abort discards buffered suffix · case 02
Abort discards buffered suffix.
Incremental client response projection: Abort discards buffered suffix · case 03
Abort discards buffered suffix.
Incremental client response projection: Abort discards buffered suffix · case 04
Abort discards buffered suffix.
Incremental client response projection: Abort discards buffered suffix · case 05
Abort discards buffered suffix.
Client worker task handoff: Result matches pending job · case 01
Result matches pending job.
Client worker task handoff: Result matches pending job · case 02
Result matches pending job.
Client worker task handoff: Result matches pending job · case 03
Result matches pending job.
Client worker task handoff: Result matches pending job · case 04
Result matches pending job.
Client worker task handoff: Result matches pending job · case 05
Result matches pending job.
Client worker task handoff: Worker instance result owner · case 01
Worker instance result owner.
Client worker task handoff: Worker instance result owner · case 02
Worker instance result owner.
Client worker task handoff: Worker instance result owner · case 03
Worker instance result owner.
Client worker task handoff: Worker instance result owner · case 04
Worker instance result owner.
Client worker task handoff: Worker instance result owner · case 05
Worker instance result owner.
Client worker task handoff: Result removes exact job · case 01
Result removes exact job.
Client worker task handoff: Result removes exact job · case 02
Result removes exact job.
Client worker task handoff: Result removes exact job · case 03
Result removes exact job.
Client worker task handoff: Result removes exact job · case 04
Result removes exact job.
Client worker task handoff: Result removes exact job · case 05
Result removes exact job.
INSPECTABLE BY DESIGN
Every result has a runnable source.
Runnable implementations with recorded outputs, source hashes, and explicit contracts. Related variants share a failure mechanism and belong together in evaluation splits.
Read the methodology ↗