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
Hierarchical branch command lock: Lock ownership ignores self or ancestor branch · case 01
Lock ownership ignores self or ancestor branch produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Lock ownership ignores self or ancestor branch · case 02
Lock ownership ignores self or ancestor branch produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Lock ownership ignores self or ancestor branch · case 03
Lock ownership ignores self or ancestor branch produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Lock ownership ignores self or ancestor branch · case 04
Lock ownership ignores self or ancestor branch produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Lock ownership ignores self or ancestor branch · case 05
Lock ownership ignores self or ancestor branch produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Lock explanation chooses outermost instead of nearest owner · case 01
Lock explanation chooses outermost instead of nearest owner produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Lock explanation chooses outermost instead of nearest owner · case 02
Lock explanation chooses outermost instead of nearest owner produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Lock explanation chooses outermost instead of nearest owner · case 03
Lock explanation chooses outermost instead of nearest owner produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Lock explanation chooses outermost instead of nearest owner · case 04
Lock explanation chooses outermost instead of nearest owner produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Lock explanation chooses outermost instead of nearest owner · case 05
Lock explanation chooses outermost instead of nearest owner produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Read-only inspection and state-changing commands share wrong lock policy · case 01
Read-only inspection and state-changing commands share wrong lock policy produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Read-only inspection and state-changing commands share wrong lock policy · case 02
Read-only inspection and state-changing commands share wrong lock policy produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Read-only inspection and state-changing commands share wrong lock policy · case 03
Read-only inspection and state-changing commands share wrong lock policy produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Read-only inspection and state-changing commands share wrong lock policy · case 04
Read-only inspection and state-changing commands share wrong lock policy produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Read-only inspection and state-changing commands share wrong lock policy · case 05
Read-only inspection and state-changing commands share wrong lock policy produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Missing or read-only branch accepts mutation · case 01
Missing or read-only branch accepts mutation produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Missing or read-only branch accepts mutation · case 02
Missing or read-only branch accepts mutation produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Missing or read-only branch accepts mutation · case 03
Missing or read-only branch accepts mutation produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Missing or read-only branch accepts mutation · case 04
Missing or read-only branch accepts mutation produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Missing or read-only branch accepts mutation · case 05
Missing or read-only branch accepts mutation produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Busy denial names target instead of locking ancestor · case 01
Busy denial names target instead of locking ancestor produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Busy denial names target instead of locking ancestor · case 02
Busy denial names target instead of locking ancestor produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Busy denial names target instead of locking ancestor · case 03
Busy denial names target instead of locking ancestor produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Busy denial names target instead of locking ancestor · case 04
Busy denial names target instead of locking ancestor produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Busy denial names target instead of locking ancestor · case 05
Busy denial names target instead of locking ancestor produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: New lock map resurrects released operation · case 01
New lock map resurrects released operation produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: New lock map resurrects released operation · case 02
New lock map resurrects released operation produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: New lock map resurrects released operation · case 03
New lock map resurrects released operation produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: New lock map resurrects released operation · case 04
New lock map resurrects released operation produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: New lock map resurrects released operation · case 05
New lock map resurrects released operation produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Rejected or read-only command starts a subtree lock · case 01
Rejected or read-only command starts a subtree lock produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Rejected or read-only command starts a subtree lock · case 02
Rejected or read-only command starts a subtree lock produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Rejected or read-only command starts a subtree lock · case 03
Rejected or read-only command starts a subtree lock produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Rejected or read-only command starts a subtree lock · case 04
Rejected or read-only command starts a subtree lock produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Rejected or read-only command starts a subtree lock · case 05
Rejected or read-only command starts a subtree lock produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Busy exposure fails to follow subtree boundary · case 01
Busy exposure fails to follow subtree boundary produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Busy exposure fails to follow subtree boundary · case 02
Busy exposure fails to follow subtree boundary produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Busy exposure fails to follow subtree boundary · case 03
Busy exposure fails to follow subtree boundary produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Busy exposure fails to follow subtree boundary · case 04
Busy exposure fails to follow subtree boundary produces the wrong hierarchical widget state in a regression fixture.
Hierarchical branch command lock: Busy exposure fails to follow subtree boundary · case 05
Busy exposure fails to follow subtree boundary produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Failed move rolls back a newer transaction · case 01
Failed move rolls back a newer transaction produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Failed move rolls back a newer transaction · case 02
Failed move rolls back a newer transaction produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Failed move rolls back a newer transaction · case 03
Failed move rolls back a newer transaction produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Failed move rolls back a newer transaction · case 04
Failed move rolls back a newer transaction produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Failed move rolls back a newer transaction · case 05
Failed move rolls back a newer transaction produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Successful or superseded move is rolled back · case 01
Successful or superseded move is rolled back produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Successful or superseded move is rolled back · case 02
Successful or superseded move is rolled back produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Successful or superseded move is rolled back · case 03
Successful or superseded move is rolled back produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Successful or superseded move is rolled back · case 04
Successful or superseded move is rolled back produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Successful or superseded move is rolled back · case 05
Successful or superseded move is rolled back produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback leaves accessible parent at optimistic destination · case 01
Rollback leaves accessible parent at optimistic destination produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback leaves accessible parent at optimistic destination · case 02
Rollback leaves accessible parent at optimistic destination produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback leaves accessible parent at optimistic destination · case 03
Rollback leaves accessible parent at optimistic destination produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback leaves accessible parent at optimistic destination · case 04
Rollback leaves accessible parent at optimistic destination produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback leaves accessible parent at optimistic destination · case 05
Rollback leaves accessible parent at optimistic destination produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback source reconstruction discards surviving siblings · case 01
Rollback source reconstruction discards surviving siblings produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback source reconstruction discards surviving siblings · case 02
Rollback source reconstruction discards surviving siblings produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback source reconstruction discards surviving siblings · case 03
Rollback source reconstruction discards surviving siblings produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback source reconstruction discards surviving siblings · case 04
Rollback source reconstruction discards surviving siblings produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback source reconstruction discards surviving siblings · case 05
Rollback source reconstruction discards surviving siblings produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rolled-back root returns at wrong sibling index · case 01
Rolled-back root returns at wrong sibling index produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rolled-back root returns at wrong sibling index · case 02
Rolled-back root returns at wrong sibling index produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rolled-back root returns at wrong sibling index · case 03
Rolled-back root returns at wrong sibling index produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rolled-back root returns at wrong sibling index · case 04
Rolled-back root returns at wrong sibling index produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rolled-back root returns at wrong sibling index · case 05
Rolled-back root returns at wrong sibling index produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Destination retains rolled-back subtree or removes committed root · case 01
Destination retains rolled-back subtree or removes committed root produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Destination retains rolled-back subtree or removes committed root · case 02
Destination retains rolled-back subtree or removes committed root produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Destination retains rolled-back subtree or removes committed root · case 03
Destination retains rolled-back subtree or removes committed root produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Destination retains rolled-back subtree or removes committed root · case 04
Destination retains rolled-back subtree or removes committed root produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Destination retains rolled-back subtree or removes committed root · case 05
Destination retains rolled-back subtree or removes committed root produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Inverse depth correction misses moved descendants · case 01
Inverse depth correction misses moved descendants produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Inverse depth correction misses moved descendants · case 02
Inverse depth correction misses moved descendants produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Inverse depth correction misses moved descendants · case 03
Inverse depth correction misses moved descendants produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Inverse depth correction misses moved descendants · case 04
Inverse depth correction misses moved descendants produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Inverse depth correction misses moved descendants · case 05
Inverse depth correction misses moved descendants produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback overwrites user focus moved after optimistic operation · case 01
Rollback overwrites user focus moved after optimistic operation produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback overwrites user focus moved after optimistic operation · case 02
Rollback overwrites user focus moved after optimistic operation produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback overwrites user focus moved after optimistic operation · case 03
Rollback overwrites user focus moved after optimistic operation produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback overwrites user focus moved after optimistic operation · case 04
Rollback overwrites user focus moved after optimistic operation produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback overwrites user focus moved after optimistic operation · case 05
Rollback overwrites user focus moved after optimistic operation produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback restores stale selection snapshot · case 01
Rollback restores stale selection snapshot produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback restores stale selection snapshot · case 02
Rollback restores stale selection snapshot produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback restores stale selection snapshot · case 03
Rollback restores stale selection snapshot produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback restores stale selection snapshot · case 04
Rollback restores stale selection snapshot produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Rollback restores stale selection snapshot · case 05
Rollback restores stale selection snapshot produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Superseded operation is reported as committed or rolled back · case 01
Superseded operation is reported as committed or rolled back produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Superseded operation is reported as committed or rolled back · case 02
Superseded operation is reported as committed or rolled back produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Superseded operation is reported as committed or rolled back · case 03
Superseded operation is reported as committed or rolled back produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Superseded operation is reported as committed or rolled back · case 04
Superseded operation is reported as committed or rolled back produces the wrong hierarchical widget state in a regression fixture.
Optimistic subtree move rollback ownership: Superseded operation is reported as committed or rolled back · case 05
Superseded operation is reported as committed or rolled back produces the wrong hierarchical widget state in a regression fixture.
Bounded accessible branch expansion eviction: Expansion budget admits disabled or nonbranch target · case 01
Expansion budget admits disabled or nonbranch target produces the wrong hierarchical widget state in a regression fixture.
Bounded accessible branch expansion eviction: Expansion budget admits disabled or nonbranch target · case 02
Expansion budget admits disabled or nonbranch target produces the wrong hierarchical widget state in a regression fixture.
Bounded accessible branch expansion eviction: Expansion budget admits disabled or nonbranch target · case 03
Expansion budget admits disabled or nonbranch target produces the wrong hierarchical widget state in a regression fixture.
Bounded accessible branch expansion eviction: Expansion budget admits disabled or nonbranch target · case 04
Expansion budget admits disabled or nonbranch target produces the wrong hierarchical widget state in a regression fixture.
Bounded accessible branch expansion eviction: Expansion budget admits disabled or nonbranch target · case 05
Expansion budget admits disabled or nonbranch target produces the wrong hierarchical widget state in a regression fixture.
Bounded accessible branch expansion eviction: Budget reservation omits requested path ancestors or target · case 01
Budget reservation omits requested path ancestors or target produces the wrong hierarchical widget state in a regression fixture.
Bounded accessible branch expansion eviction: Budget reservation omits requested path ancestors or target · case 02
Budget reservation omits requested path ancestors or target produces the wrong hierarchical widget state in a regression fixture.
Bounded accessible branch expansion eviction: Budget reservation omits requested path ancestors or target · case 03
Budget reservation omits requested path ancestors or target produces the wrong hierarchical widget state in a regression fixture.
Bounded accessible branch expansion eviction: Budget reservation omits requested path ancestors or target · case 04
Budget reservation omits requested path ancestors or target produces the wrong hierarchical widget state in a regression fixture.
Bounded accessible branch expansion eviction: Budget reservation omits requested path ancestors or target · case 05
Budget reservation omits requested path ancestors or target produces the wrong hierarchical widget state in a regression fixture.
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 ↗