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
Duplicate callback settlement decrements outstanding work twice · case 01
Duplicate callback settlement decrements outstanding work twice; the returned lifecycle plan violates the stated transition contract.
Duplicate callback settlement decrements outstanding work twice · case 02
Duplicate callback settlement decrements outstanding work twice; the returned lifecycle plan violates the stated transition contract.
Duplicate callback settlement decrements outstanding work twice · case 03
Duplicate callback settlement decrements outstanding work twice; the returned lifecycle plan violates the stated transition contract.
Duplicate callback settlement decrements outstanding work twice · case 04
Duplicate callback settlement decrements outstanding work twice; the returned lifecycle plan violates the stated transition contract.
Duplicate callback settlement decrements outstanding work twice · case 05
Duplicate callback settlement decrements outstanding work twice; the returned lifecycle plan violates the stated transition contract.
Cancelled async callback skips its acquired-resource cleanup · case 01
Cancelled async callback skips its acquired-resource cleanup; the returned lifecycle plan violates the stated transition contract.
Cancelled async callback skips its acquired-resource cleanup · case 02
Cancelled async callback skips its acquired-resource cleanup; the returned lifecycle plan violates the stated transition contract.
Cancelled async callback skips its acquired-resource cleanup · case 03
Cancelled async callback skips its acquired-resource cleanup; the returned lifecycle plan violates the stated transition contract.
Cancelled async callback skips its acquired-resource cleanup · case 04
Cancelled async callback skips its acquired-resource cleanup; the returned lifecycle plan violates the stated transition contract.
Cancelled async callback skips its acquired-resource cleanup · case 05
Cancelled async callback skips its acquired-resource cleanup; the returned lifecycle plan violates the stated transition contract.
A successful None observer result is confused with rejection · case 01
A successful None observer result is confused with rejection; the returned lifecycle plan violates the stated transition contract.
A successful None observer result is confused with rejection · case 02
A successful None observer result is confused with rejection; the returned lifecycle plan violates the stated transition contract.
A successful None observer result is confused with rejection · case 03
A successful None observer result is confused with rejection; the returned lifecycle plan violates the stated transition contract.
A successful None observer result is confused with rejection · case 04
A successful None observer result is confused with rejection; the returned lifecycle plan violates the stated transition contract.
A successful None observer result is confused with rejection · case 05
A successful None observer result is confused with rejection; the returned lifecycle plan violates the stated transition contract.
Asynchronous rejection diagnostics attribute an old callback to the current generation · case 01
Asynchronous rejection diagnostics attribute an old callback to the current generation; the returned lifecycle plan violates the stated transition contract.
Asynchronous rejection diagnostics attribute an old callback to the current generation · case 02
Asynchronous rejection diagnostics attribute an old callback to the current generation; the returned lifecycle plan violates the stated transition contract.
Asynchronous rejection diagnostics attribute an old callback to the current generation · case 03
Asynchronous rejection diagnostics attribute an old callback to the current generation; the returned lifecycle plan violates the stated transition contract.
Asynchronous rejection diagnostics attribute an old callback to the current generation · case 04
Asynchronous rejection diagnostics attribute an old callback to the current generation; the returned lifecycle plan violates the stated transition contract.
Asynchronous rejection diagnostics attribute an old callback to the current generation · case 05
Asynchronous rejection diagnostics attribute an old callback to the current generation; the returned lifecycle plan violates the stated transition contract.
A failing asynchronous error observer hides the original callback rejection · case 01
A failing asynchronous error observer hides the original callback rejection; the returned lifecycle plan violates the stated transition contract.
A failing asynchronous error observer hides the original callback rejection · case 02
A failing asynchronous error observer hides the original callback rejection; the returned lifecycle plan violates the stated transition contract.
A failing asynchronous error observer hides the original callback rejection · case 03
A failing asynchronous error observer hides the original callback rejection; the returned lifecycle plan violates the stated transition contract.
A failing asynchronous error observer hides the original callback rejection · case 04
A failing asynchronous error observer hides the original callback rejection; the returned lifecycle plan violates the stated transition contract.
A failing asynchronous error observer hides the original callback rejection · case 05
A failing asynchronous error observer hides the original callback rejection; the returned lifecycle plan violates the stated transition contract.
Closing observer completes while another asynchronous callback remains · case 01
Closing observer completes while another asynchronous callback remains; the returned lifecycle plan violates the stated transition contract.
Closing observer completes while another asynchronous callback remains · case 02
Closing observer completes while another asynchronous callback remains; the returned lifecycle plan violates the stated transition contract.
Closing observer completes while another asynchronous callback remains · case 03
Closing observer completes while another asynchronous callback remains; the returned lifecycle plan violates the stated transition contract.
Closing observer completes while another asynchronous callback remains · case 04
Closing observer completes while another asynchronous callback remains; the returned lifecycle plan violates the stated transition contract.
Closing observer completes while another asynchronous callback remains · case 05
Closing observer completes while another asynchronous callback remains; the returned lifecycle plan violates the stated transition contract.
A future-generation settlement is incorrectly treated as current · case 01
A future-generation settlement is incorrectly treated as current; the returned lifecycle plan violates the stated transition contract.
A future-generation settlement is incorrectly treated as current · case 02
A future-generation settlement is incorrectly treated as current; the returned lifecycle plan violates the stated transition contract.
A future-generation settlement is incorrectly treated as current · case 03
A future-generation settlement is incorrectly treated as current; the returned lifecycle plan violates the stated transition contract.
A future-generation settlement is incorrectly treated as current · case 04
A future-generation settlement is incorrectly treated as current; the returned lifecycle plan violates the stated transition contract.
A future-generation settlement is incorrectly treated as current · case 05
A future-generation settlement is incorrectly treated as current; the returned lifecycle plan violates the stated transition contract.
Cancelled callback completion can be retried as if unsettled · case 01
Cancelled callback completion can be retried as if unsettled; the returned lifecycle plan violates the stated transition contract.
Cancelled callback completion can be retried as if unsettled · case 02
Cancelled callback completion can be retried as if unsettled; the returned lifecycle plan violates the stated transition contract.
Cancelled callback completion can be retried as if unsettled · case 03
Cancelled callback completion can be retried as if unsettled; the returned lifecycle plan violates the stated transition contract.
Cancelled callback completion can be retried as if unsettled · case 04
Cancelled callback completion can be retried as if unsettled; the returned lifecycle plan violates the stated transition contract.
Cancelled callback completion can be retried as if unsettled · case 05
Cancelled callback completion can be retried as if unsettled; the returned lifecycle plan violates the stated transition contract.
Type-rejected values still invoke a user observer predicate · case 01
Type-rejected values still invoke a user observer predicate; the returned lifecycle plan violates the stated transition contract.
Type-rejected values still invoke a user observer predicate · case 02
Type-rejected values still invoke a user observer predicate; the returned lifecycle plan violates the stated transition contract.
Type-rejected values still invoke a user observer predicate · case 03
Type-rejected values still invoke a user observer predicate; the returned lifecycle plan violates the stated transition contract.
Type-rejected values still invoke a user observer predicate · case 04
Type-rejected values still invoke a user observer predicate; the returned lifecycle plan violates the stated transition contract.
Type-rejected values still invoke a user observer predicate · case 05
Type-rejected values still invoke a user observer predicate; the returned lifecycle plan violates the stated transition contract.
Filter input index advances only for accepted values · case 01
Filter input index advances only for accepted values; the returned lifecycle plan violates the stated transition contract.
Filter input index advances only for accepted values · case 02
Filter input index advances only for accepted values; the returned lifecycle plan violates the stated transition contract.
Filter input index advances only for accepted values · case 03
Filter input index advances only for accepted values; the returned lifecycle plan violates the stated transition contract.
Filter input index advances only for accepted values · case 04
Filter input index advances only for accepted values; the returned lifecycle plan violates the stated transition contract.
Filter input index advances only for accepted values · case 05
Filter input index advances only for accepted values; the returned lifecycle plan violates the stated transition contract.
Rejected filtered values advance the downstream output index · case 01
Rejected filtered values advance the downstream output index; the returned lifecycle plan violates the stated transition contract.
Rejected filtered values advance the downstream output index · case 02
Rejected filtered values advance the downstream output index; the returned lifecycle plan violates the stated transition contract.
Rejected filtered values advance the downstream output index · case 03
Rejected filtered values advance the downstream output index; the returned lifecycle plan violates the stated transition contract.
Rejected filtered values advance the downstream output index · case 04
Rejected filtered values advance the downstream output index; the returned lifecycle plan violates the stated transition contract.
Rejected filtered values advance the downstream output index · case 05
Rejected filtered values advance the downstream output index; the returned lifecycle plan violates the stated transition contract.
Filtering drops valid falsey event payloads · case 01
Filtering drops valid falsey event payloads; the returned lifecycle plan violates the stated transition contract.
Filtering drops valid falsey event payloads · case 02
Filtering drops valid falsey event payloads; the returned lifecycle plan violates the stated transition contract.
Filtering drops valid falsey event payloads · case 03
Filtering drops valid falsey event payloads; the returned lifecycle plan violates the stated transition contract.
Filtering drops valid falsey event payloads · case 04
Filtering drops valid falsey event payloads; the returned lifecycle plan violates the stated transition contract.
Filtering drops valid falsey event payloads · case 05
Filtering drops valid falsey event payloads; the returned lifecycle plan violates the stated transition contract.
Predicate exceptions are emitted as accepted values · case 01
Predicate exceptions are emitted as accepted values; the returned lifecycle plan violates the stated transition contract.
Predicate exceptions are emitted as accepted values · case 02
Predicate exceptions are emitted as accepted values; the returned lifecycle plan violates the stated transition contract.
Predicate exceptions are emitted as accepted values · case 03
Predicate exceptions are emitted as accepted values; the returned lifecycle plan violates the stated transition contract.
Predicate exceptions are emitted as accepted values · case 04
Predicate exceptions are emitted as accepted values; the returned lifecycle plan violates the stated transition contract.
Predicate exceptions are emitted as accepted values · case 05
Predicate exceptions are emitted as accepted values; the returned lifecycle plan violates the stated transition contract.
Rejected filtered events consume downstream demand · case 01
Rejected filtered events consume downstream demand; the returned lifecycle plan violates the stated transition contract.
Rejected filtered events consume downstream demand · case 02
Rejected filtered events consume downstream demand; the returned lifecycle plan violates the stated transition contract.
Rejected filtered events consume downstream demand · case 03
Rejected filtered events consume downstream demand; the returned lifecycle plan violates the stated transition contract.
Rejected filtered events consume downstream demand · case 04
Rejected filtered events consume downstream demand; the returned lifecycle plan violates the stated transition contract.
Rejected filtered events consume downstream demand · case 05
Rejected filtered events consume downstream demand; the returned lifecycle plan violates the stated transition contract.
A rejected value permanently loses upstream demand · case 01
A rejected value permanently loses upstream demand; the returned lifecycle plan violates the stated transition contract.
A rejected value permanently loses upstream demand · case 02
A rejected value permanently loses upstream demand; the returned lifecycle plan violates the stated transition contract.
A rejected value permanently loses upstream demand · case 03
A rejected value permanently loses upstream demand; the returned lifecycle plan violates the stated transition contract.
A rejected value permanently loses upstream demand · case 04
A rejected value permanently loses upstream demand; the returned lifecycle plan violates the stated transition contract.
A rejected value permanently loses upstream demand · case 05
A rejected value permanently loses upstream demand; the returned lifecycle plan violates the stated transition contract.
Predicate chains invoke callbacks after a preceding predicate already rejected · case 01
Predicate chains invoke callbacks after a preceding predicate already rejected; the returned lifecycle plan violates the stated transition contract.
Predicate chains invoke callbacks after a preceding predicate already rejected · case 02
Predicate chains invoke callbacks after a preceding predicate already rejected; the returned lifecycle plan violates the stated transition contract.
Predicate chains invoke callbacks after a preceding predicate already rejected · case 03
Predicate chains invoke callbacks after a preceding predicate already rejected; the returned lifecycle plan violates the stated transition contract.
Predicate chains invoke callbacks after a preceding predicate already rejected · case 04
Predicate chains invoke callbacks after a preceding predicate already rejected; the returned lifecycle plan violates the stated transition contract.
Predicate chains invoke callbacks after a preceding predicate already rejected · case 05
Predicate chains invoke callbacks after a preceding predicate already rejected; the returned lifecycle plan violates the stated transition contract.
Predicate failure leaves the filtering observer active · case 01
Predicate failure leaves the filtering observer active; the returned lifecycle plan violates the stated transition contract.
Predicate failure leaves the filtering observer active · case 02
Predicate failure leaves the filtering observer active; the returned lifecycle plan violates the stated transition contract.
Predicate failure leaves the filtering observer active · case 03
Predicate failure leaves the filtering observer active; the returned lifecycle plan violates the stated transition contract.
Predicate failure leaves the filtering observer active · case 04
Predicate failure leaves the filtering observer active; the returned lifecycle plan violates the stated transition contract.
Predicate failure leaves the filtering observer active · case 05
Predicate failure leaves the filtering observer active; the returned lifecycle plan violates the stated transition contract.
A predicate exception is treated as a false predicate result · case 01
A predicate exception is treated as a false predicate result; the returned lifecycle plan violates the stated transition contract.
A predicate exception is treated as a false predicate result · case 02
A predicate exception is treated as a false predicate result; the returned lifecycle plan violates the stated transition contract.
A predicate exception is treated as a false predicate result · case 03
A predicate exception is treated as a false predicate result; the returned lifecycle plan violates the stated transition contract.
A predicate exception is treated as a false predicate result · case 04
A predicate exception is treated as a false predicate result; the returned lifecycle plan violates the stated transition contract.
A predicate exception is treated as a false predicate result · case 05
A predicate exception is treated as a false predicate result; the returned lifecycle plan violates the stated transition contract.
The first None distinct key is mistaken for an initialized cache · case 01
The first None distinct key is mistaken for an initialized cache; the returned lifecycle plan violates the stated transition contract.
The first None distinct key is mistaken for an initialized cache · case 02
The first None distinct key is mistaken for an initialized cache; the returned lifecycle plan violates the stated transition contract.
The first None distinct key is mistaken for an initialized cache · case 03
The first None distinct key is mistaken for an initialized cache; the returned lifecycle plan violates the stated transition contract.
The first None distinct key is mistaken for an initialized cache · case 04
The first None distinct key is mistaken for an initialized cache; the returned lifecycle plan violates the stated transition contract.
The first None distinct key is mistaken for an initialized cache · case 05
The first None distinct key is mistaken for an initialized cache; the returned lifecycle plan violates the stated transition contract.
Distinct suppression removes nonconsecutive repeated event keys · case 01
Distinct suppression removes nonconsecutive repeated event keys; the returned lifecycle plan violates the stated transition contract.
Distinct suppression removes nonconsecutive repeated event keys · case 02
Distinct suppression removes nonconsecutive repeated event keys; the returned lifecycle plan violates the stated transition contract.
Distinct suppression removes nonconsecutive repeated event keys · case 03
Distinct suppression removes nonconsecutive repeated event keys; the returned lifecycle plan violates the stated transition contract.
Distinct suppression removes nonconsecutive repeated event keys · case 04
Distinct suppression removes nonconsecutive repeated event keys; the returned lifecycle plan violates the stated transition contract.
Distinct suppression removes nonconsecutive repeated event keys · case 05
Distinct suppression removes nonconsecutive repeated event keys; 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 ↗