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
Persistent heap publishes the copied root rather than the copied target or old root · case 01
The bounded persistent path copy certificate reports an incorrect root.
Persistent heap publishes the copied root rather than the copied target or old root · case 02
The bounded persistent path copy certificate reports an incorrect root.
Persistent heap publishes the copied root rather than the copied target or old root · case 03
The bounded persistent path copy certificate reports an incorrect root.
Persistent heap publishes the copied root rather than the copied target or old root · case 04
The bounded persistent path copy certificate reports an incorrect root.
Persistent heap publishes the copied root rather than the copied target or old root · case 05
The bounded persistent path copy certificate reports an incorrect root.
Persistent heap target handle resolves into the new version · case 01
The bounded persistent path copy certificate reports an incorrect target.
Persistent heap target handle resolves into the new version · case 02
The bounded persistent path copy certificate reports an incorrect target.
Persistent heap target handle resolves into the new version · case 03
The bounded persistent path copy certificate reports an incorrect target.
Persistent heap target handle resolves into the new version · case 04
The bounded persistent path copy certificate reports an incorrect target.
Persistent heap target handle resolves into the new version · case 05
The bounded persistent path copy certificate reports an incorrect target.
Heap meld ownership follows the full representative chain · case 01
The bounded meld ownership certificate reports an incorrect representatives.
Heap meld ownership follows the full representative chain · case 02
The bounded meld ownership certificate reports an incorrect representatives.
Heap meld ownership follows the full representative chain · case 03
The bounded meld ownership certificate reports an incorrect representatives.
Heap meld ownership follows the full representative chain · case 04
The bounded meld ownership certificate reports an incorrect representatives.
Heap meld ownership follows the full representative chain · case 05
The bounded meld ownership certificate reports an incorrect representatives.
Heap meld attaches the source representative to the destination representative · case 01
The bounded meld ownership certificate reports an incorrect union.
Heap meld attaches the source representative to the destination representative · case 02
The bounded meld ownership certificate reports an incorrect union.
Heap meld attaches the source representative to the destination representative · case 03
The bounded meld ownership certificate reports an incorrect union.
Heap meld attaches the source representative to the destination representative · case 04
The bounded meld ownership certificate reports an incorrect union.
Heap meld attaches the source representative to the destination representative · case 05
The bounded meld ownership certificate reports an incorrect union.
Heap self-component meld preserves source wrapper size instead of clearing live ownership · case 01
The bounded meld ownership certificate reports an incorrect source size.
Heap self-component meld preserves source wrapper size instead of clearing live ownership · case 02
The bounded meld ownership certificate reports an incorrect source size.
Heap self-component meld preserves source wrapper size instead of clearing live ownership · case 03
The bounded meld ownership certificate reports an incorrect source size.
Heap self-component meld preserves source wrapper size instead of clearing live ownership · case 04
The bounded meld ownership certificate reports an incorrect source size.
Heap self-component meld preserves source wrapper size instead of clearing live ownership · case 05
The bounded meld ownership certificate reports an incorrect source size.
Heap meld sums disjoint sizes but does not double-count alias wrappers · case 01
The bounded meld ownership certificate reports an incorrect destination size.
Heap meld sums disjoint sizes but does not double-count alias wrappers · case 02
The bounded meld ownership certificate reports an incorrect destination size.
Heap meld sums disjoint sizes but does not double-count alias wrappers · case 03
The bounded meld ownership certificate reports an incorrect destination size.
Heap meld sums disjoint sizes but does not double-count alias wrappers · case 04
The bounded meld ownership certificate reports an incorrect destination size.
Heap meld sums disjoint sizes but does not double-count alias wrappers · case 05
The bounded meld ownership certificate reports an incorrect destination size.
Heap meld preserves handles from the entire source ownership component · case 01
The bounded meld ownership certificate reports an incorrect accepted.
Heap meld preserves handles from the entire source ownership component · case 02
The bounded meld ownership certificate reports an incorrect accepted.
Heap meld preserves handles from the entire source ownership component · case 03
The bounded meld ownership certificate reports an incorrect accepted.
Heap meld preserves handles from the entire source ownership component · case 04
The bounded meld ownership certificate reports an incorrect accepted.
Heap meld preserves handles from the entire source ownership component · case 05
The bounded meld ownership certificate reports an incorrect accepted.
Heap meld detects aliasing through representatives even when wrapper ids differ · case 01
The bounded meld ownership certificate reports an incorrect noop.
Heap meld detects aliasing through representatives even when wrapper ids differ · case 02
The bounded meld ownership certificate reports an incorrect noop.
Heap meld detects aliasing through representatives even when wrapper ids differ · case 03
The bounded meld ownership certificate reports an incorrect noop.
Heap meld detects aliasing through representatives even when wrapper ids differ · case 04
The bounded meld ownership certificate reports an incorrect noop.
Heap meld detects aliasing through representatives even when wrapper ids differ · case 05
The bounded meld ownership certificate reports an incorrect noop.
Twin heap erasure removes exactly the selected min-side identity · case 01
The bounded twin heap delete certificate reports an incorrect min ids.
Twin heap erasure removes exactly the selected min-side identity · case 02
The bounded twin heap delete certificate reports an incorrect min ids.
Twin heap erasure removes exactly the selected min-side identity · case 03
The bounded twin heap delete certificate reports an incorrect min ids.
Twin heap erasure removes exactly the selected min-side identity · case 04
The bounded twin heap delete certificate reports an incorrect min ids.
Twin heap erasure removes exactly the selected min-side identity · case 05
The bounded twin heap delete certificate reports an incorrect min ids.
Twin heap erasure removes the same identity on the opposite endpoint heap · case 01
The bounded twin heap delete certificate reports an incorrect max ids.
Twin heap erasure removes the same identity on the opposite endpoint heap · case 02
The bounded twin heap delete certificate reports an incorrect max ids.
Twin heap erasure removes the same identity on the opposite endpoint heap · case 03
The bounded twin heap delete certificate reports an incorrect max ids.
Twin heap erasure removes the same identity on the opposite endpoint heap · case 04
The bounded twin heap delete certificate reports an incorrect max ids.
Twin heap erasure removes the same identity on the opposite endpoint heap · case 05
The bounded twin heap delete certificate reports an incorrect max ids.
Twin heap shared record deletion preserves equal-priority neighbors · case 01
The bounded twin heap delete certificate reports an incorrect records.
Twin heap shared record deletion preserves equal-priority neighbors · case 02
The bounded twin heap delete certificate reports an incorrect records.
Twin heap shared record deletion preserves equal-priority neighbors · case 03
The bounded twin heap delete certificate reports an incorrect records.
Twin heap shared record deletion preserves equal-priority neighbors · case 04
The bounded twin heap delete certificate reports an incorrect records.
Twin heap shared record deletion preserves equal-priority neighbors · case 05
The bounded twin heap delete certificate reports an incorrect records.
Twin heap slot cross-links are rebuilt after both sides shift · case 01
The bounded twin heap delete certificate reports an incorrect cross index.
Twin heap slot cross-links are rebuilt after both sides shift · case 02
The bounded twin heap delete certificate reports an incorrect cross index.
Twin heap slot cross-links are rebuilt after both sides shift · case 03
The bounded twin heap delete certificate reports an incorrect cross index.
Twin heap slot cross-links are rebuilt after both sides shift · case 04
The bounded twin heap delete certificate reports an incorrect cross index.
Twin heap slot cross-links are rebuilt after both sides shift · case 05
The bounded twin heap delete certificate reports an incorrect cross index.
Twin heap minimum is read from the surviving min-side head · case 01
The bounded twin heap delete certificate reports an incorrect minimum.
Twin heap minimum is read from the surviving min-side head · case 02
The bounded twin heap delete certificate reports an incorrect minimum.
Twin heap minimum is read from the surviving min-side head · case 03
The bounded twin heap delete certificate reports an incorrect minimum.
Twin heap minimum is read from the surviving min-side head · case 04
The bounded twin heap delete certificate reports an incorrect minimum.
Twin heap minimum is read from the surviving min-side head · case 05
The bounded twin heap delete certificate reports an incorrect minimum.
Twin heap maximum is read from the surviving max-side head · case 01
The bounded twin heap delete certificate reports an incorrect maximum.
Twin heap maximum is read from the surviving max-side head · case 02
The bounded twin heap delete certificate reports an incorrect maximum.
Twin heap maximum is read from the surviving max-side head · case 03
The bounded twin heap delete certificate reports an incorrect maximum.
Twin heap maximum is read from the surviving max-side head · case 04
The bounded twin heap delete certificate reports an incorrect maximum.
Twin heap maximum is read from the surviving max-side head · case 05
The bounded twin heap delete certificate reports an incorrect maximum.
Replacement selection keeps equal keys in the current run · case 01
The bounded replacement selection certificate reports an incorrect active.
Replacement selection keeps equal keys in the current run · case 02
The bounded replacement selection certificate reports an incorrect active.
Replacement selection keeps equal keys in the current run · case 03
The bounded replacement selection certificate reports an incorrect active.
Replacement selection keeps equal keys in the current run · case 04
The bounded replacement selection certificate reports an incorrect active.
Replacement selection keeps equal keys in the current run · case 05
The bounded replacement selection certificate reports an incorrect active.
Replacement selection freezes only keys that would decrease the output run · case 01
The bounded replacement selection certificate reports an incorrect frozen.
Replacement selection freezes only keys that would decrease the output run · case 02
The bounded replacement selection certificate reports an incorrect frozen.
Replacement selection freezes only keys that would decrease the output run · case 03
The bounded replacement selection certificate reports an incorrect frozen.
Replacement selection freezes only keys that would decrease the output run · case 04
The bounded replacement selection certificate reports an incorrect frozen.
Replacement selection freezes only keys that would decrease the output run · case 05
The bounded replacement selection certificate reports an incorrect frozen.
Replacement selection current heap excludes next-run frozen records · case 01
The bounded replacement selection certificate reports an incorrect active order.
Replacement selection current heap excludes next-run frozen records · case 02
The bounded replacement selection certificate reports an incorrect active order.
Replacement selection current heap excludes next-run frozen records · case 03
The bounded replacement selection certificate reports an incorrect active order.
Replacement selection current heap excludes next-run frozen records · case 04
The bounded replacement selection certificate reports an incorrect active order.
Replacement selection current heap excludes next-run frozen records · case 05
The bounded replacement selection certificate reports an incorrect active order.
Replacement selection rebuilds frozen records in increasing priority for the next run · case 01
The bounded replacement selection certificate reports an incorrect frozen order.
Replacement selection rebuilds frozen records in increasing priority for the next run · case 02
The bounded replacement selection certificate reports an incorrect frozen order.
Replacement selection rebuilds frozen records in increasing priority for the next run · case 03
The bounded replacement selection certificate reports an incorrect frozen order.
Replacement selection rebuilds frozen records in increasing priority for the next run · case 04
The bounded replacement selection certificate reports an incorrect frozen order.
Replacement selection rebuilds frozen records in increasing priority for the next run · case 05
The bounded replacement selection certificate reports an incorrect frozen order.
Replacement selection has no current candidate when every replacement is frozen · case 01
The bounded replacement selection certificate reports an incorrect next.
Replacement selection has no current candidate when every replacement is frozen · case 02
The bounded replacement selection certificate reports an incorrect next.
Replacement selection has no current candidate when every replacement is frozen · case 03
The bounded replacement selection certificate reports an incorrect next.
Replacement selection has no current candidate when every replacement is frozen · case 04
The bounded replacement selection certificate reports an incorrect next.
Replacement selection has no current candidate when every replacement is frozen · case 05
The bounded replacement selection certificate reports an incorrect next.
Replacement selection ends a run only when no active replacement remains · case 01
The bounded replacement selection certificate reports an incorrect run ended.
Replacement selection ends a run only when no active replacement remains · case 02
The bounded replacement selection certificate reports an incorrect run ended.
Replacement selection ends a run only when no active replacement remains · case 03
The bounded replacement selection certificate reports an incorrect run ended.
Replacement selection ends a run only when no active replacement remains · case 04
The bounded replacement selection certificate reports an incorrect run ended.
Replacement selection ends a run only when no active replacement remains · case 05
The bounded replacement selection certificate reports an incorrect run ended.
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 ↗