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
Four Tap Sensor Storage: Readout tap ID swaps quadrant axes or assigns center boundary to wrong tap · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at tap.
Four Tap Sensor Storage: Readout tap ID swaps quadrant axes or assigns center boundary to wrong tap · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at tap.
Four Tap Sensor Storage: Readout tap ID swaps quadrant axes or assigns center boundary to wrong tap · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at tap.
Four Tap Sensor Storage: Readout tap ID swaps quadrant axes or assigns center boundary to wrong tap · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at tap.
Four Tap Sensor Storage: Readout tap ID swaps quadrant axes or assigns center boundary to wrong tap · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at tap.
Four Tap Sensor Storage: Right readout tap is not mirrored or mirror applied to wrong taps · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at local_x.
Four Tap Sensor Storage: Right readout tap is not mirrored or mirror applied to wrong taps · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at local_x.
Four Tap Sensor Storage: Right readout tap is not mirrored or mirror applied to wrong taps · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at local_x.
Four Tap Sensor Storage: Right readout tap is not mirrored or mirror applied to wrong taps · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at local_x.
Four Tap Sensor Storage: Right readout tap is not mirrored or mirror applied to wrong taps · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at local_x.
Four Tap Sensor Storage: Bottom readout tap is not reversed or reversal applied to top taps · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at local_y.
Four Tap Sensor Storage: Bottom readout tap is not reversed or reversal applied to top taps · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at local_y.
Four Tap Sensor Storage: Bottom readout tap is not reversed or reversal applied to top taps · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at local_y.
Four Tap Sensor Storage: Bottom readout tap is not reversed or reversal applied to top taps · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at local_y.
Four Tap Sensor Storage: Bottom readout tap is not reversed or reversal applied to top taps · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at local_y.
Four Tap Sensor Storage: Tap packet lookup ignores storage permutation or uses forward map · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at storage_slot.
Four Tap Sensor Storage: Tap packet lookup ignores storage permutation or uses forward map · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at storage_slot.
Four Tap Sensor Storage: Tap packet lookup ignores storage permutation or uses forward map · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at storage_slot.
Four Tap Sensor Storage: Tap packet lookup ignores storage permutation or uses forward map · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at storage_slot.
Four Tap Sensor Storage: Tap packet lookup ignores storage permutation or uses forward map · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at storage_slot.
Four Tap Sensor Storage: Tap packet pitch omits header or allocates full sensor per tap · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at packet_pitch.
Four Tap Sensor Storage: Tap packet pitch omits header or allocates full sensor per tap · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at packet_pitch.
Four Tap Sensor Storage: Tap packet pitch omits header or allocates full sensor per tap · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at packet_pitch.
Four Tap Sensor Storage: Tap packet pitch omits header or allocates full sensor per tap · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at packet_pitch.
Four Tap Sensor Storage: Tap packet pitch omits header or allocates full sensor per tap · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at packet_pitch.
Four Tap Sensor Storage: Tap packet start uses logical tap order or drops relocation · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at packet_origin.
Four Tap Sensor Storage: Tap packet start uses logical tap order or drops relocation · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at packet_origin.
Four Tap Sensor Storage: Tap packet start uses logical tap order or drops relocation · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at packet_origin.
Four Tap Sensor Storage: Tap packet start uses logical tap order or drops relocation · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at packet_origin.
Four Tap Sensor Storage: Tap packet start uses logical tap order or drops relocation · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at packet_origin.
Four Tap Sensor Storage: Readout sample includes packet header or uses full sensor row pitch · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at address.
Four Tap Sensor Storage: Readout sample includes packet header or uses full sensor row pitch · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at address.
Four Tap Sensor Storage: Readout sample includes packet header or uses full sensor row pitch · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at address.
Four Tap Sensor Storage: Readout sample includes packet header or uses full sensor row pitch · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at address.
Four Tap Sensor Storage: Readout sample includes packet header or uses full sensor row pitch · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at address.
Four Tap Sensor Storage: Sensor buffer omits tap headers or fourth tap packet · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at allocation_end.
Four Tap Sensor Storage: Sensor buffer omits tap headers or fourth tap packet · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at allocation_end.
Four Tap Sensor Storage: Sensor buffer omits tap headers or fourth tap packet · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at allocation_end.
Four Tap Sensor Storage: Sensor buffer omits tap headers or fourth tap packet · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at allocation_end.
Four Tap Sensor Storage: Sensor buffer omits tap headers or fourth tap packet · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at allocation_end.
Role token scanning ignores tab separators · case 01
Role token scanning ignores tab separators.
Role token scanning ignores tab separators · case 02
Role token scanning ignores tab separators.
Role token scanning ignores tab separators · case 03
Role token scanning ignores tab separators.
Role token scanning ignores tab separators · case 04
Role token scanning ignores tab separators.
Role token scanning ignores tab separators · case 05
Role token scanning ignores tab separators.
An abstract role token terminates fallback resolution · case 01
An abstract role token terminates fallback resolution.
An abstract role token terminates fallback resolution · case 02
An abstract role token terminates fallback resolution.
An abstract role token terminates fallback resolution · case 03
An abstract role token terminates fallback resolution.
An abstract role token terminates fallback resolution · case 04
An abstract role token terminates fallback resolution.
An abstract role token terminates fallback resolution · case 05
An abstract role token terminates fallback resolution.
Interactive nodes accept a presentation override · case 01
Interactive nodes accept a presentation override.
Interactive nodes accept a presentation override · case 02
Interactive nodes accept a presentation override.
Interactive nodes accept a presentation override · case 03
Interactive nodes accept a presentation override.
Interactive nodes accept a presentation override · case 04
Interactive nodes accept a presentation override.
Interactive nodes accept a presentation override · case 05
Interactive nodes accept a presentation override.
A mandatory native semantic is overwritten · case 01
A mandatory native semantic is overwritten.
A mandatory native semantic is overwritten · case 02
A mandatory native semantic is overwritten.
A mandatory native semantic is overwritten · case 03
A mandatory native semantic is overwritten.
A mandatory native semantic is overwritten · case 04
A mandatory native semantic is overwritten.
A mandatory native semantic is overwritten · case 05
A mandatory native semantic is overwritten.
Last role token replaces first usable role · case 01
Last role token replaces first usable role.
Last role token replaces first usable role · case 02
Last role token replaces first usable role.
Last role token replaces first usable role · case 03
Last role token replaces first usable role.
Last role token replaces first usable role · case 04
Last role token replaces first usable role.
Last role token replaces first usable role · case 05
Last role token replaces first usable role.
Missing role tokens fabricate generic semantics · case 01
Missing role tokens fabricate generic semantics.
Missing role tokens fabricate generic semantics · case 02
Missing role tokens fabricate generic semantics.
Missing role tokens fabricate generic semantics · case 03
Missing role tokens fabricate generic semantics.
Missing role tokens fabricate generic semantics · case 04
Missing role tokens fabricate generic semantics.
Missing role tokens fabricate generic semantics · case 05
Missing role tokens fabricate generic semantics.
A platform unsupported role leaks through · case 01
A platform unsupported role leaks through.
A platform unsupported role leaks through · case 02
A platform unsupported role leaks through.
A platform unsupported role leaks through · case 03
A platform unsupported role leaks through.
A platform unsupported role leaks through · case 04
A platform unsupported role leaks through.
A platform unsupported role leaks through · case 05
A platform unsupported role leaks through.
Unsupported native roles are used as a fallback · case 01
Unsupported native roles are used as a fallback.
Unsupported native roles are used as a fallback · case 02
Unsupported native roles are used as a fallback.
Unsupported native roles are used as a fallback · case 03
Unsupported native roles are used as a fallback.
Unsupported native roles are used as a fallback · case 04
Unsupported native roles are used as a fallback.
Unsupported native roles are used as a fallback · case 05
Unsupported native roles are used as a fallback.
Native roles are incorrectly marked as author overrides · case 01
Native roles are incorrectly marked as author overrides.
Native roles are incorrectly marked as author overrides · case 02
Native roles are incorrectly marked as author overrides.
Native roles are incorrectly marked as author overrides · case 03
Native roles are incorrectly marked as author overrides.
Native roles are incorrectly marked as author overrides · case 04
Native roles are incorrectly marked as author overrides.
Native roles are incorrectly marked as author overrides · case 05
Native roles are incorrectly marked as author overrides.
Role fallback retains the explicit-source marker · case 01
Role fallback retains the explicit-source marker.
Role fallback retains the explicit-source marker · case 02
Role fallback retains the explicit-source marker.
Role fallback retains the explicit-source marker · case 03
Role fallback retains the explicit-source marker.
Role fallback retains the explicit-source marker · case 04
Role fallback retains the explicit-source marker.
Role fallback retains the explicit-source marker · case 05
Role fallback retains the explicit-source marker.
Unknown relationship types enter the platform bridge · case 01
Unknown relationship types enter the platform bridge.
Unknown relationship types enter the platform bridge · case 02
Unknown relationship types enter the platform bridge.
Unknown relationship types enter the platform bridge · case 03
Unknown relationship types enter the platform bridge.
Unknown relationship types enter the platform bridge · case 04
Unknown relationship types enter the platform bridge.
Unknown relationship types enter the platform bridge · case 05
Unknown relationship types enter the platform bridge.
Relations cross embedded document boundaries · case 01
Relations cross embedded document boundaries.
Relations cross embedded document boundaries · case 02
Relations cross embedded document boundaries.
Relations cross embedded document boundaries · case 03
Relations cross embedded document boundaries.
Relations cross embedded document boundaries · case 04
Relations cross embedded document boundaries.
Relations cross embedded document boundaries · case 05
Relations cross embedded document boundaries.
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 ↗