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
The target phase chooses the first ancestor · case 01
The target phase chooses the first ancestor; the returned lifecycle plan violates the stated transition contract.
The target phase chooses the first ancestor · case 02
The target phase chooses the first ancestor; the returned lifecycle plan violates the stated transition contract.
The target phase chooses the first ancestor · case 03
The target phase chooses the first ancestor; the returned lifecycle plan violates the stated transition contract.
The target phase chooses the first ancestor · case 04
The target phase chooses the first ancestor; the returned lifecycle plan violates the stated transition contract.
The target phase chooses the first ancestor · case 05
The target phase chooses the first ancestor; the returned lifecycle plan violates the stated transition contract.
Immediate propagation stop still advances to another node · case 01
Immediate propagation stop still advances to another node; the returned lifecycle plan violates the stated transition contract.
Immediate propagation stop still advances to another node · case 02
Immediate propagation stop still advances to another node; the returned lifecycle plan violates the stated transition contract.
Immediate propagation stop still advances to another node · case 03
Immediate propagation stop still advances to another node; the returned lifecycle plan violates the stated transition contract.
Immediate propagation stop still advances to another node · case 04
Immediate propagation stop still advances to another node; the returned lifecycle plan violates the stated transition contract.
Immediate propagation stop still advances to another node · case 05
Immediate propagation stop still advances to another node; the returned lifecycle plan violates the stated transition contract.
Ordinary propagation stop suppresses current-node sibling callbacks · case 01
Ordinary propagation stop suppresses current-node sibling callbacks; the returned lifecycle plan violates the stated transition contract.
Ordinary propagation stop suppresses current-node sibling callbacks · case 02
Ordinary propagation stop suppresses current-node sibling callbacks; the returned lifecycle plan violates the stated transition contract.
Ordinary propagation stop suppresses current-node sibling callbacks · case 03
Ordinary propagation stop suppresses current-node sibling callbacks; the returned lifecycle plan violates the stated transition contract.
Ordinary propagation stop suppresses current-node sibling callbacks · case 04
Ordinary propagation stop suppresses current-node sibling callbacks; the returned lifecycle plan violates the stated transition contract.
Ordinary propagation stop suppresses current-node sibling callbacks · case 05
Ordinary propagation stop suppresses current-node sibling callbacks; the returned lifecycle plan violates the stated transition contract.
A passive callback cancels the event default action · case 01
A passive callback cancels the event default action; the returned lifecycle plan violates the stated transition contract.
A passive callback cancels the event default action · case 02
A passive callback cancels the event default action; the returned lifecycle plan violates the stated transition contract.
A passive callback cancels the event default action · case 03
A passive callback cancels the event default action; the returned lifecycle plan violates the stated transition contract.
A passive callback cancels the event default action · case 04
A passive callback cancels the event default action; the returned lifecycle plan violates the stated transition contract.
A passive callback cancels the event default action · case 05
A passive callback cancels the event default action; the returned lifecycle plan violates the stated transition contract.
A previously cancelled event runs its default action · case 01
A previously cancelled event runs its default action; the returned lifecycle plan violates the stated transition contract.
A previously cancelled event runs its default action · case 02
A previously cancelled event runs its default action; the returned lifecycle plan violates the stated transition contract.
A previously cancelled event runs its default action · case 03
A previously cancelled event runs its default action; the returned lifecycle plan violates the stated transition contract.
A previously cancelled event runs its default action · case 04
A previously cancelled event runs its default action; the returned lifecycle plan violates the stated transition contract.
A previously cancelled event runs its default action · case 05
A previously cancelled event runs its default action; the returned lifecycle plan violates the stated transition contract.
Callback current-target metadata points at the terminal target · case 01
Callback current-target metadata points at the terminal target; the returned lifecycle plan violates the stated transition contract.
Callback current-target metadata points at the terminal target · case 02
Callback current-target metadata points at the terminal target; the returned lifecycle plan violates the stated transition contract.
Callback current-target metadata points at the terminal target · case 03
Callback current-target metadata points at the terminal target; the returned lifecycle plan violates the stated transition contract.
Callback current-target metadata points at the terminal target · case 04
Callback current-target metadata points at the terminal target; the returned lifecycle plan violates the stated transition contract.
Callback current-target metadata points at the terminal target · case 05
Callback current-target metadata points at the terminal target; the returned lifecycle plan violates the stated transition contract.
Propagation exposes only the ancestor portion of the event path · case 01
Propagation exposes only the ancestor portion of the event path; the returned lifecycle plan violates the stated transition contract.
Propagation exposes only the ancestor portion of the event path · case 02
Propagation exposes only the ancestor portion of the event path; the returned lifecycle plan violates the stated transition contract.
Propagation exposes only the ancestor portion of the event path · case 03
Propagation exposes only the ancestor portion of the event path; the returned lifecycle plan violates the stated transition contract.
Propagation exposes only the ancestor portion of the event path · case 04
Propagation exposes only the ancestor portion of the event path; the returned lifecycle plan violates the stated transition contract.
Propagation exposes only the ancestor portion of the event path · case 05
Propagation exposes only the ancestor portion of the event path; the returned lifecycle plan violates the stated transition contract.
Ignored prevent-default calls are not diagnosed for passive listeners · case 01
Ignored prevent-default calls are not diagnosed for passive listeners; the returned lifecycle plan violates the stated transition contract.
Ignored prevent-default calls are not diagnosed for passive listeners · case 02
Ignored prevent-default calls are not diagnosed for passive listeners; the returned lifecycle plan violates the stated transition contract.
Ignored prevent-default calls are not diagnosed for passive listeners · case 03
Ignored prevent-default calls are not diagnosed for passive listeners; the returned lifecycle plan violates the stated transition contract.
Ignored prevent-default calls are not diagnosed for passive listeners · case 04
Ignored prevent-default calls are not diagnosed for passive listeners; the returned lifecycle plan violates the stated transition contract.
Ignored prevent-default calls are not diagnosed for passive listeners · case 05
Ignored prevent-default calls are not diagnosed for passive listeners; the returned lifecycle plan violates the stated transition contract.
Recoverable callback errors abort unrelated observer callbacks · case 01
Recoverable callback errors abort unrelated observer callbacks; the returned lifecycle plan violates the stated transition contract.
Recoverable callback errors abort unrelated observer callbacks · case 02
Recoverable callback errors abort unrelated observer callbacks; the returned lifecycle plan violates the stated transition contract.
Recoverable callback errors abort unrelated observer callbacks · case 03
Recoverable callback errors abort unrelated observer callbacks; the returned lifecycle plan violates the stated transition contract.
Recoverable callback errors abort unrelated observer callbacks · case 04
Recoverable callback errors abort unrelated observer callbacks; the returned lifecycle plan violates the stated transition contract.
Recoverable callback errors abort unrelated observer callbacks · case 05
Recoverable callback errors abort unrelated observer callbacks; the returned lifecycle plan violates the stated transition contract.
A throwing observer callback skips resource cleanup · case 01
A throwing observer callback skips resource cleanup; the returned lifecycle plan violates the stated transition contract.
A throwing observer callback skips resource cleanup · case 02
A throwing observer callback skips resource cleanup; the returned lifecycle plan violates the stated transition contract.
A throwing observer callback skips resource cleanup · case 03
A throwing observer callback skips resource cleanup; the returned lifecycle plan violates the stated transition contract.
A throwing observer callback skips resource cleanup · case 04
A throwing observer callback skips resource cleanup; the returned lifecycle plan violates the stated transition contract.
A throwing observer callback skips resource cleanup · case 05
A throwing observer callback skips resource cleanup; the returned lifecycle plan violates the stated transition contract.
An error handled by an observer error listener is also unhandled · case 01
An error handled by an observer error listener is also unhandled; the returned lifecycle plan violates the stated transition contract.
An error handled by an observer error listener is also unhandled · case 02
An error handled by an observer error listener is also unhandled; the returned lifecycle plan violates the stated transition contract.
An error handled by an observer error listener is also unhandled · case 03
An error handled by an observer error listener is also unhandled; the returned lifecycle plan violates the stated transition contract.
An error handled by an observer error listener is also unhandled · case 04
An error handled by an observer error listener is also unhandled; the returned lifecycle plan violates the stated transition contract.
An error handled by an observer error listener is also unhandled · case 05
An error handled by an observer error listener is also unhandled; the returned lifecycle plan violates the stated transition contract.
A new callback failure overwrites earlier collected failures · case 01
A new callback failure overwrites earlier collected failures; the returned lifecycle plan violates the stated transition contract.
A new callback failure overwrites earlier collected failures · case 02
A new callback failure overwrites earlier collected failures; the returned lifecycle plan violates the stated transition contract.
A new callback failure overwrites earlier collected failures · case 03
A new callback failure overwrites earlier collected failures; the returned lifecycle plan violates the stated transition contract.
A new callback failure overwrites earlier collected failures · case 04
A new callback failure overwrites earlier collected failures; the returned lifecycle plan violates the stated transition contract.
A new callback failure overwrites earlier collected failures · case 05
A new callback failure overwrites earlier collected failures; the returned lifecycle plan violates the stated transition contract.
A fatal callback failure is routed through recovery · case 01
A fatal callback failure is routed through recovery; the returned lifecycle plan violates the stated transition contract.
A fatal callback failure is routed through recovery · case 02
A fatal callback failure is routed through recovery; the returned lifecycle plan violates the stated transition contract.
A fatal callback failure is routed through recovery · case 03
A fatal callback failure is routed through recovery; the returned lifecycle plan violates the stated transition contract.
A fatal callback failure is routed through recovery · case 04
A fatal callback failure is routed through recovery; the returned lifecycle plan violates the stated transition contract.
A fatal callback failure is routed through recovery · case 05
A fatal callback failure is routed through recovery; the returned lifecycle plan violates the stated transition contract.
Falsey callback results are converted to absent results · case 01
Falsey callback results are converted to absent results; the returned lifecycle plan violates the stated transition contract.
Falsey callback results are converted to absent results · case 02
Falsey callback results are converted to absent results; the returned lifecycle plan violates the stated transition contract.
Falsey callback results are converted to absent results · case 03
Falsey callback results are converted to absent results; the returned lifecycle plan violates the stated transition contract.
Falsey callback results are converted to absent results · case 04
Falsey callback results are converted to absent results; the returned lifecycle plan violates the stated transition contract.
Falsey callback results are converted to absent results · case 05
Falsey callback results are converted to absent results; the returned lifecycle plan violates the stated transition contract.
Failure accounting claims skipped siblings executed · case 01
Failure accounting claims skipped siblings executed; the returned lifecycle plan violates the stated transition contract.
Failure accounting claims skipped siblings executed · case 02
Failure accounting claims skipped siblings executed; the returned lifecycle plan violates the stated transition contract.
Failure accounting claims skipped siblings executed · case 03
Failure accounting claims skipped siblings executed; the returned lifecycle plan violates the stated transition contract.
Failure accounting claims skipped siblings executed · case 04
Failure accounting claims skipped siblings executed; the returned lifecycle plan violates the stated transition contract.
Failure accounting claims skipped siblings executed · case 05
Failure accounting claims skipped siblings executed; the returned lifecycle plan violates the stated transition contract.
A successful callback accidentally clears active dispatch state · case 01
A successful callback accidentally clears active dispatch state; the returned lifecycle plan violates the stated transition contract.
A successful callback accidentally clears active dispatch state · case 02
A successful callback accidentally clears active dispatch state; the returned lifecycle plan violates the stated transition contract.
A successful callback accidentally clears active dispatch state · case 03
A successful callback accidentally clears active dispatch state; the returned lifecycle plan violates the stated transition contract.
A successful callback accidentally clears active dispatch state · case 04
A successful callback accidentally clears active dispatch state; the returned lifecycle plan violates the stated transition contract.
A successful callback accidentally clears active dispatch state · case 05
A successful callback accidentally clears active dispatch state; the returned lifecycle plan violates the stated transition contract.
An absent exception is marked handled merely because a handler exists · case 01
An absent exception is marked handled merely because a handler exists; the returned lifecycle plan violates the stated transition contract.
An absent exception is marked handled merely because a handler exists · case 02
An absent exception is marked handled merely because a handler exists; the returned lifecycle plan violates the stated transition contract.
An absent exception is marked handled merely because a handler exists · case 03
An absent exception is marked handled merely because a handler exists; the returned lifecycle plan violates the stated transition contract.
An absent exception is marked handled merely because a handler exists · case 04
An absent exception is marked handled merely because a handler exists; the returned lifecycle plan violates the stated transition contract.
An absent exception is marked handled merely because a handler exists · case 05
An absent exception is marked handled merely because a handler exists; the returned lifecycle plan violates the stated transition contract.
Fail-fast policy misclassifies every callback error as fatal · case 01
Fail-fast policy misclassifies every callback error as fatal; the returned lifecycle plan violates the stated transition contract.
Fail-fast policy misclassifies every callback error as fatal · case 02
Fail-fast policy misclassifies every callback error as fatal; the returned lifecycle plan violates the stated transition contract.
Fail-fast policy misclassifies every callback error as fatal · case 03
Fail-fast policy misclassifies every callback error as fatal; the returned lifecycle plan violates the stated transition contract.
Fail-fast policy misclassifies every callback error as fatal · case 04
Fail-fast policy misclassifies every callback error as fatal; the returned lifecycle plan violates the stated transition contract.
Fail-fast policy misclassifies every callback error as fatal · case 05
Fail-fast policy misclassifies every callback error as fatal; the returned lifecycle plan violates the stated transition contract.
Envelope copy drops the first callback payload element · case 01
Envelope copy drops the first callback payload element; the returned lifecycle plan violates the stated transition contract.
Envelope copy drops the first callback payload element · case 02
Envelope copy drops the first callback payload element; the returned lifecycle plan violates the stated transition contract.
Envelope copy drops the first callback payload element · case 03
Envelope copy drops the first callback payload element; the returned lifecycle plan violates the stated transition contract.
Envelope copy drops the first callback payload element · case 04
Envelope copy drops the first callback payload element; the returned lifecycle plan violates the stated transition contract.
Envelope copy drops the first callback payload element · case 05
Envelope copy drops the first callback payload element; the returned lifecycle plan violates the stated transition contract.
Private observer envelope headers escape to callbacks · case 01
Private observer envelope headers escape to callbacks; the returned lifecycle plan violates the stated transition contract.
Private observer envelope headers escape to callbacks · case 02
Private observer envelope headers escape to callbacks; the returned lifecycle plan violates the stated transition contract.
Private observer envelope headers escape to callbacks · case 03
Private observer envelope headers escape to callbacks; the returned lifecycle plan violates the stated transition contract.
Private observer envelope headers escape to callbacks · case 04
Private observer envelope headers escape to callbacks; the returned lifecycle plan violates the stated transition contract.
Private observer envelope headers escape to callbacks · case 05
Private observer envelope headers escape to callbacks; the returned lifecycle plan violates the stated transition contract.
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 ↗