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
Rank-loss accounting measures actual decrease magnitude with the correct sign · case 01
The bounded rank loss propagation certificate reports an incorrect drops.
Rank-loss accounting measures actual decrease magnitude with the correct sign · case 02
The bounded rank loss propagation certificate reports an incorrect drops.
Rank-loss accounting measures actual decrease magnitude with the correct sign · case 03
The bounded rank loss propagation certificate reports an incorrect drops.
Rank-loss accounting measures actual decrease magnitude with the correct sign · case 04
The bounded rank loss propagation certificate reports an incorrect drops.
Rank-loss accounting measures actual decrease magnitude with the correct sign · case 05
The bounded rank loss propagation certificate reports an incorrect drops.
Rank-loss repair counts the stopping ancestor while avoiding later unrelated nodes · case 01
The bounded rank loss propagation certificate reports an incorrect visited.
Rank-loss repair counts the stopping ancestor while avoiding later unrelated nodes · case 02
The bounded rank loss propagation certificate reports an incorrect visited.
Rank-loss repair counts the stopping ancestor while avoiding later unrelated nodes · case 03
The bounded rank loss propagation certificate reports an incorrect visited.
Rank-loss repair counts the stopping ancestor while avoiding later unrelated nodes · case 04
The bounded rank loss propagation certificate reports an incorrect visited.
Rank-loss repair counts the stopping ancestor while avoiding later unrelated nodes · case 05
The bounded rank loss propagation certificate reports an incorrect visited.
Skew heap heavy-edge threshold includes the current root and is strict · case 01
The bounded skew heavy certificate certificate reports an incorrect heavy.
Skew heap heavy-edge threshold includes the current root and is strict · case 02
The bounded skew heavy certificate certificate reports an incorrect heavy.
Skew heap heavy-edge threshold includes the current root and is strict · case 03
The bounded skew heavy certificate certificate reports an incorrect heavy.
Skew heap heavy-edge threshold includes the current root and is strict · case 04
The bounded skew heavy certificate certificate reports an incorrect heavy.
Skew heap heavy-edge threshold includes the current root and is strict · case 05
The bounded skew heavy certificate certificate reports an incorrect heavy.
Skew heap light-right edges exclude missing right children · case 01
The bounded skew heavy certificate certificate reports an incorrect light right.
Skew heap light-right edges exclude missing right children · case 02
The bounded skew heavy certificate certificate reports an incorrect light right.
Skew heap light-right edges exclude missing right children · case 03
The bounded skew heavy certificate certificate reports an incorrect light right.
Skew heap light-right edges exclude missing right children · case 04
The bounded skew heavy certificate certificate reports an incorrect light right.
Skew heap light-right edges exclude missing right children · case 05
The bounded skew heavy certificate certificate reports an incorrect light right.
Skew heap subtree weight includes the node and both disjoint child subtrees · case 01
The bounded skew heavy certificate certificate reports an incorrect subtree sizes.
Skew heap subtree weight includes the node and both disjoint child subtrees · case 02
The bounded skew heavy certificate certificate reports an incorrect subtree sizes.
Skew heap subtree weight includes the node and both disjoint child subtrees · case 03
The bounded skew heavy certificate certificate reports an incorrect subtree sizes.
Skew heap subtree weight includes the node and both disjoint child subtrees · case 04
The bounded skew heavy certificate certificate reports an incorrect subtree sizes.
Skew heap subtree weight includes the node and both disjoint child subtrees · case 05
The bounded skew heavy certificate certificate reports an incorrect subtree sizes.
Skew heap potential counts heavy right edges rather than their subtree mass · case 01
The bounded skew heavy certificate certificate reports an incorrect potential.
Skew heap potential counts heavy right edges rather than their subtree mass · case 02
The bounded skew heavy certificate certificate reports an incorrect potential.
Skew heap potential counts heavy right edges rather than their subtree mass · case 03
The bounded skew heavy certificate certificate reports an incorrect potential.
Skew heap potential counts heavy right edges rather than their subtree mass · case 04
The bounded skew heavy certificate certificate reports an incorrect potential.
Skew heap potential counts heavy right edges rather than their subtree mass · case 05
The bounded skew heavy certificate certificate reports an incorrect potential.
Skew heap path charge separates light visits from potential-paid heavy visits · case 01
The bounded skew heavy certificate certificate reports an incorrect light visits.
Skew heap path charge separates light visits from potential-paid heavy visits · case 02
The bounded skew heavy certificate certificate reports an incorrect light visits.
Skew heap path charge separates light visits from potential-paid heavy visits · case 03
The bounded skew heavy certificate certificate reports an incorrect light visits.
Skew heap path charge separates light visits from potential-paid heavy visits · case 04
The bounded skew heavy certificate certificate reports an incorrect light visits.
Skew heap path charge separates light visits from potential-paid heavy visits · case 05
The bounded skew heavy certificate certificate reports an incorrect light visits.
Skew heap amortized delta subtracts the prior heavy-edge potential · case 01
The bounded skew heavy certificate certificate reports an incorrect potential delta.
Skew heap amortized delta subtracts the prior heavy-edge potential · case 02
The bounded skew heavy certificate certificate reports an incorrect potential delta.
Skew heap amortized delta subtracts the prior heavy-edge potential · case 03
The bounded skew heavy certificate certificate reports an incorrect potential delta.
Skew heap amortized delta subtracts the prior heavy-edge potential · case 04
The bounded skew heavy certificate certificate reports an incorrect potential delta.
Skew heap amortized delta subtracts the prior heavy-edge potential · case 05
The bounded skew heavy certificate certificate reports an incorrect potential delta.
An already aborted signal acquires a listener hook · case 01
An already aborted signal acquires a listener hook; the returned lifecycle plan violates the stated transition contract.
An already aborted signal acquires a listener hook · case 02
An already aborted signal acquires a listener hook; the returned lifecycle plan violates the stated transition contract.
An already aborted signal acquires a listener hook · case 03
An already aborted signal acquires a listener hook; the returned lifecycle plan violates the stated transition contract.
An already aborted signal acquires a listener hook · case 04
An already aborted signal acquires a listener hook; the returned lifecycle plan violates the stated transition contract.
An already aborted signal acquires a listener hook · case 05
An already aborted signal acquires a listener hook; the returned lifecycle plan violates the stated transition contract.
Signal cancellation skips active subscription disposal · case 01
Signal cancellation skips active subscription disposal; the returned lifecycle plan violates the stated transition contract.
Signal cancellation skips active subscription disposal · case 02
Signal cancellation skips active subscription disposal; the returned lifecycle plan violates the stated transition contract.
Signal cancellation skips active subscription disposal · case 03
Signal cancellation skips active subscription disposal; the returned lifecycle plan violates the stated transition contract.
Signal cancellation skips active subscription disposal · case 04
Signal cancellation skips active subscription disposal; the returned lifecycle plan violates the stated transition contract.
Signal cancellation skips active subscription disposal · case 05
Signal cancellation skips active subscription disposal; the returned lifecycle plan violates the stated transition contract.
An inactive subscription leaves its cancellation hook attached · case 01
An inactive subscription leaves its cancellation hook attached; the returned lifecycle plan violates the stated transition contract.
An inactive subscription leaves its cancellation hook attached · case 02
An inactive subscription leaves its cancellation hook attached; the returned lifecycle plan violates the stated transition contract.
An inactive subscription leaves its cancellation hook attached · case 03
An inactive subscription leaves its cancellation hook attached; the returned lifecycle plan violates the stated transition contract.
An inactive subscription leaves its cancellation hook attached · case 04
An inactive subscription leaves its cancellation hook attached; the returned lifecycle plan violates the stated transition contract.
An inactive subscription leaves its cancellation hook attached · case 05
An inactive subscription leaves its cancellation hook attached; the returned lifecycle plan violates the stated transition contract.
Cancellation reason disappears after the signal aborts · case 01
Cancellation reason disappears after the signal aborts; the returned lifecycle plan violates the stated transition contract.
Cancellation reason disappears after the signal aborts · case 02
Cancellation reason disappears after the signal aborts; the returned lifecycle plan violates the stated transition contract.
Cancellation reason disappears after the signal aborts · case 03
Cancellation reason disappears after the signal aborts; the returned lifecycle plan violates the stated transition contract.
Cancellation reason disappears after the signal aborts · case 04
Cancellation reason disappears after the signal aborts; the returned lifecycle plan violates the stated transition contract.
Cancellation reason disappears after the signal aborts · case 05
Cancellation reason disappears after the signal aborts; the returned lifecycle plan violates the stated transition contract.
Cancelled observer work remains pending · case 01
Cancelled observer work remains pending; the returned lifecycle plan violates the stated transition contract.
Cancelled observer work remains pending · case 02
Cancelled observer work remains pending; the returned lifecycle plan violates the stated transition contract.
Cancelled observer work remains pending · case 03
Cancelled observer work remains pending; the returned lifecycle plan violates the stated transition contract.
Cancelled observer work remains pending · case 04
Cancelled observer work remains pending; the returned lifecycle plan violates the stated transition contract.
Cancelled observer work remains pending · case 05
Cancelled observer work remains pending; the returned lifecycle plan violates the stated transition contract.
Disposal destroys a borrowed cancellation signal · case 01
Disposal destroys a borrowed cancellation signal; the returned lifecycle plan violates the stated transition contract.
Disposal destroys a borrowed cancellation signal · case 02
Disposal destroys a borrowed cancellation signal; the returned lifecycle plan violates the stated transition contract.
Disposal destroys a borrowed cancellation signal · case 03
Disposal destroys a borrowed cancellation signal; the returned lifecycle plan violates the stated transition contract.
Disposal destroys a borrowed cancellation signal · case 04
Disposal destroys a borrowed cancellation signal; the returned lifecycle plan violates the stated transition contract.
Disposal destroys a borrowed cancellation signal · case 05
Disposal destroys a borrowed cancellation signal; the returned lifecycle plan violates the stated transition contract.
Repeated cancellation notifies the observer twice · case 01
Repeated cancellation notifies the observer twice; the returned lifecycle plan violates the stated transition contract.
Repeated cancellation notifies the observer twice · case 02
Repeated cancellation notifies the observer twice; the returned lifecycle plan violates the stated transition contract.
Repeated cancellation notifies the observer twice · case 03
Repeated cancellation notifies the observer twice; the returned lifecycle plan violates the stated transition contract.
Repeated cancellation notifies the observer twice · case 04
Repeated cancellation notifies the observer twice; the returned lifecycle plan violates the stated transition contract.
Repeated cancellation notifies the observer twice · case 05
Repeated cancellation notifies the observer twice; the returned lifecycle plan violates the stated transition contract.
A disposed listener accepts a new cancellation linkage · case 01
A disposed listener accepts a new cancellation linkage; the returned lifecycle plan violates the stated transition contract.
A disposed listener accepts a new cancellation linkage · case 02
A disposed listener accepts a new cancellation linkage; the returned lifecycle plan violates the stated transition contract.
A disposed listener accepts a new cancellation linkage · case 03
A disposed listener accepts a new cancellation linkage; the returned lifecycle plan violates the stated transition contract.
A disposed listener accepts a new cancellation linkage · case 04
A disposed listener accepts a new cancellation linkage; the returned lifecycle plan violates the stated transition contract.
A disposed listener accepts a new cancellation linkage · case 05
A disposed listener accepts a new cancellation linkage; the returned lifecycle plan violates the stated transition contract.
Cancellation underflows an unattached hook reference · case 01
Cancellation underflows an unattached hook reference; the returned lifecycle plan violates the stated transition contract.
Cancellation underflows an unattached hook reference · case 02
Cancellation underflows an unattached hook reference; the returned lifecycle plan violates the stated transition contract.
Cancellation underflows an unattached hook reference · case 03
Cancellation underflows an unattached hook reference; the returned lifecycle plan violates the stated transition contract.
Cancellation underflows an unattached hook reference · case 04
Cancellation underflows an unattached hook reference; the returned lifecycle plan violates the stated transition contract.
Cancellation underflows an unattached hook reference · case 05
Cancellation underflows an unattached hook reference; the returned lifecycle plan violates the stated transition contract.
Cancellation clears a preexisting terminal state · case 01
Cancellation clears a preexisting terminal state; the returned lifecycle plan violates the stated transition contract.
Cancellation clears a preexisting terminal state · case 02
Cancellation clears a preexisting terminal state; the returned lifecycle plan violates the stated transition contract.
Cancellation clears a preexisting terminal state · case 03
Cancellation clears a preexisting terminal state; the returned lifecycle plan violates the stated transition contract.
Cancellation clears a preexisting terminal state · case 04
Cancellation clears a preexisting terminal state; the returned lifecycle plan violates the stated transition contract.
Cancellation clears a preexisting terminal state · case 05
Cancellation clears a preexisting terminal state; the returned lifecycle plan violates the stated transition contract.
Scope teardown runs children in acquisition order · case 01
Scope teardown runs children in acquisition order; the returned lifecycle plan violates the stated transition contract.
Scope teardown runs children in acquisition order · case 02
Scope teardown runs children in acquisition order; the returned lifecycle plan violates the stated transition contract.
Scope teardown runs children in acquisition order · case 03
Scope teardown runs children in acquisition order; the returned lifecycle plan violates the stated transition contract.
Scope teardown runs children in acquisition order · case 04
Scope teardown runs children in acquisition order; the returned lifecycle plan violates the stated transition contract.
Scope teardown runs children in acquisition order · case 05
Scope teardown runs children in acquisition order; the returned lifecycle plan violates the stated transition contract.
Scope exit claims ownership of borrowed listeners · case 01
Scope exit claims ownership of borrowed listeners; the returned lifecycle plan violates the stated transition contract.
Scope exit claims ownership of borrowed listeners · case 02
Scope exit claims ownership of borrowed listeners; the returned lifecycle plan violates the stated transition contract.
Scope exit claims ownership of borrowed listeners · case 03
Scope exit claims ownership of borrowed listeners; the returned lifecycle plan violates the stated transition contract.
Scope exit claims ownership of borrowed listeners · case 04
Scope exit claims ownership of borrowed listeners; the returned lifecycle plan violates the stated transition contract.
Scope exit claims ownership of borrowed listeners · case 05
Scope exit claims ownership of borrowed listeners; 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 ↗