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
Nested sky cell address: Nested sky child address uses binary rather than quadtree stride · case 01
The adapter reports an incorrect child local while other fields remain valid.
Nested sky cell address: Nested sky child address uses binary rather than quadtree stride · case 02
The adapter reports an incorrect child local while other fields remain valid.
Nested sky cell address: Nested sky child address uses binary rather than quadtree stride · case 03
The adapter reports an incorrect child local while other fields remain valid.
Nested sky cell address: Nested sky child address uses binary rather than quadtree stride · case 04
The adapter reports an incorrect child local while other fields remain valid.
Nested sky cell address: Nested sky child address uses binary rather than quadtree stride · case 05
The adapter reports an incorrect child local while other fields remain valid.
Nested sky cell address: Nested sky descendant range expands by a linear or binary scale · case 01
The adapter reports an incorrect descendant first while other fields remain valid.
Nested sky cell address: Nested sky descendant range expands by a linear or binary scale · case 02
The adapter reports an incorrect descendant first while other fields remain valid.
Nested sky cell address: Nested sky descendant range expands by a linear or binary scale · case 03
The adapter reports an incorrect descendant first while other fields remain valid.
Nested sky cell address: Nested sky descendant range expands by a linear or binary scale · case 04
The adapter reports an incorrect descendant first while other fields remain valid.
Nested sky cell address: Nested sky descendant range expands by a linear or binary scale · case 05
The adapter reports an incorrect descendant first while other fields remain valid.
Nested sky cell address: Nested sky half-open descendant stop is emitted as an inclusive endpoint · case 01
The adapter reports an incorrect descendant stop while other fields remain valid.
Nested sky cell address: Nested sky half-open descendant stop is emitted as an inclusive endpoint · case 02
The adapter reports an incorrect descendant stop while other fields remain valid.
Nested sky cell address: Nested sky half-open descendant stop is emitted as an inclusive endpoint · case 03
The adapter reports an incorrect descendant stop while other fields remain valid.
Nested sky cell address: Nested sky half-open descendant stop is emitted as an inclusive endpoint · case 04
The adapter reports an incorrect descendant stop while other fields remain valid.
Nested sky cell address: Nested sky half-open descendant stop is emitted as an inclusive endpoint · case 05
The adapter reports an incorrect descendant stop while other fields remain valid.
Nested sky cell address: All-sky nested pixel count omits the base-face multiplicity · case 01
The adapter reports an incorrect face count while other fields remain valid.
Nested sky cell address: All-sky nested pixel count omits the base-face multiplicity · case 02
The adapter reports an incorrect face count while other fields remain valid.
Nested sky cell address: All-sky nested pixel count omits the base-face multiplicity · case 03
The adapter reports an incorrect face count while other fields remain valid.
Nested sky cell address: All-sky nested pixel count omits the base-face multiplicity · case 04
The adapter reports an incorrect face count while other fields remain valid.
Nested sky cell address: All-sky nested pixel count omits the base-face multiplicity · case 05
The adapter reports an incorrect face count while other fields remain valid.
Multiorder sky cell encoding: Multiorder sky encoding uses the wrong order-band prefix · case 01
The adapter reports an incorrect uniq while other fields remain valid.
Multiorder sky cell encoding: Multiorder sky encoding uses the wrong order-band prefix · case 02
The adapter reports an incorrect uniq while other fields remain valid.
Multiorder sky cell encoding: Multiorder sky encoding uses the wrong order-band prefix · case 03
The adapter reports an incorrect uniq while other fields remain valid.
Multiorder sky cell encoding: Multiorder sky encoding uses the wrong order-band prefix · case 04
The adapter reports an incorrect uniq while other fields remain valid.
Multiorder sky cell encoding: Multiorder sky encoding uses the wrong order-band prefix · case 05
The adapter reports an incorrect uniq while other fields remain valid.
Multiorder sky cell encoding: Multiorder order-band origin is confused with all-sky pixel count · case 01
The adapter reports an incorrect band start while other fields remain valid.
Multiorder sky cell encoding: Multiorder order-band origin is confused with all-sky pixel count · case 02
The adapter reports an incorrect band start while other fields remain valid.
Multiorder sky cell encoding: Multiorder order-band origin is confused with all-sky pixel count · case 03
The adapter reports an incorrect band start while other fields remain valid.
Multiorder sky cell encoding: Multiorder order-band origin is confused with all-sky pixel count · case 04
The adapter reports an incorrect band start while other fields remain valid.
Multiorder sky cell encoding: Multiorder order-band origin is confused with all-sky pixel count · case 05
The adapter reports an incorrect band start while other fields remain valid.
Multiorder sky cell encoding: Nested sky cell area scales linearly with resolution instead of quadratically · case 01
The adapter reports an incorrect cell area while other fields remain valid.
Multiorder sky cell encoding: Nested sky cell area scales linearly with resolution instead of quadratically · case 02
The adapter reports an incorrect cell area while other fields remain valid.
Multiorder sky cell encoding: Nested sky cell area scales linearly with resolution instead of quadratically · case 03
The adapter reports an incorrect cell area while other fields remain valid.
Multiorder sky cell encoding: Nested sky cell area scales linearly with resolution instead of quadratically · case 04
The adapter reports an incorrect cell area while other fields remain valid.
Multiorder sky cell encoding: Nested sky cell area scales linearly with resolution instead of quadratically · case 05
The adapter reports an incorrect cell area while other fields remain valid.
Multiorder sky cell encoding: Sky probability density is exported as cell probability without area conversion · case 01
The adapter reports an incorrect cell mass while other fields remain valid.
Multiorder sky cell encoding: Sky probability density is exported as cell probability without area conversion · case 02
The adapter reports an incorrect cell mass while other fields remain valid.
Multiorder sky cell encoding: Sky probability density is exported as cell probability without area conversion · case 03
The adapter reports an incorrect cell mass while other fields remain valid.
Multiorder sky cell encoding: Sky probability density is exported as cell probability without area conversion · case 04
The adapter reports an incorrect cell mass while other fields remain valid.
Multiorder sky cell encoding: Sky probability density is exported as cell probability without area conversion · case 05
The adapter reports an incorrect cell mass while other fields remain valid.
Multiorder sky cell encoding: Multiorder child encoding appends a child digit to the wrong payload · case 01
The adapter reports an incorrect child uniq while other fields remain valid.
Multiorder sky cell encoding: Multiorder child encoding appends a child digit to the wrong payload · case 02
The adapter reports an incorrect child uniq while other fields remain valid.
Multiorder sky cell encoding: Multiorder child encoding appends a child digit to the wrong payload · case 03
The adapter reports an incorrect child uniq while other fields remain valid.
Multiorder sky cell encoding: Multiorder child encoding appends a child digit to the wrong payload · case 04
The adapter reports an incorrect child uniq while other fields remain valid.
Multiorder sky cell encoding: Multiorder child encoding appends a child digit to the wrong payload · case 05
The adapter reports an incorrect child uniq while other fields remain valid.
Multiorder sky cell encoding: Multiorder order-band exclusive endpoint is mistaken for pixel payload length · case 01
The adapter reports an incorrect order stop while other fields remain valid.
Multiorder sky cell encoding: Multiorder order-band exclusive endpoint is mistaken for pixel payload length · case 02
The adapter reports an incorrect order stop while other fields remain valid.
Multiorder sky cell encoding: Multiorder order-band exclusive endpoint is mistaken for pixel payload length · case 03
The adapter reports an incorrect order stop while other fields remain valid.
Multiorder sky cell encoding: Multiorder order-band exclusive endpoint is mistaken for pixel payload length · case 04
The adapter reports an incorrect order stop while other fields remain valid.
Multiorder sky cell encoding: Multiorder order-band exclusive endpoint is mistaken for pixel payload length · case 05
The adapter reports an incorrect order stop while other fields remain valid.
Fits split time reference: FITS split time reference loses fractional reference or TIMEZERO · case 01
The adapter reports an incorrect absolute day while other fields remain valid.
Fits split time reference: FITS split time reference loses fractional reference or TIMEZERO · case 02
The adapter reports an incorrect absolute day while other fields remain valid.
Fits split time reference: FITS split time reference loses fractional reference or TIMEZERO · case 03
The adapter reports an incorrect absolute day while other fields remain valid.
Fits split time reference: FITS split time reference loses fractional reference or TIMEZERO · case 04
The adapter reports an incorrect absolute day while other fields remain valid.
Fits split time reference: FITS split time reference loses fractional reference or TIMEZERO · case 05
The adapter reports an incorrect absolute day while other fields remain valid.
Fits split time reference: FITS TIMEZERO is added after rather than before time-unit conversion · case 01
The adapter reports an incorrect elapsed seconds while other fields remain valid.
Fits split time reference: FITS TIMEZERO is added after rather than before time-unit conversion · case 02
The adapter reports an incorrect elapsed seconds while other fields remain valid.
Fits split time reference: FITS TIMEZERO is added after rather than before time-unit conversion · case 03
The adapter reports an incorrect elapsed seconds while other fields remain valid.
Fits split time reference: FITS TIMEZERO is added after rather than before time-unit conversion · case 04
The adapter reports an incorrect elapsed seconds while other fields remain valid.
Fits split time reference: FITS TIMEZERO is added after rather than before time-unit conversion · case 05
The adapter reports an incorrect elapsed seconds while other fields remain valid.
Fits split time reference: Fractional reference day is interpreted as a time-column unit · case 01
The adapter reports an incorrect reference seconds while other fields remain valid.
Fits split time reference: Fractional reference day is interpreted as a time-column unit · case 02
The adapter reports an incorrect reference seconds while other fields remain valid.
Fits split time reference: Fractional reference day is interpreted as a time-column unit · case 03
The adapter reports an incorrect reference seconds while other fields remain valid.
Fits split time reference: Fractional reference day is interpreted as a time-column unit · case 04
The adapter reports an incorrect reference seconds while other fields remain valid.
Fits split time reference: Fractional reference day is interpreted as a time-column unit · case 05
The adapter reports an incorrect reference seconds while other fields remain valid.
Fits split time reference: FITS time zero offset is reported in seconds while labeled days · case 01
The adapter reports an incorrect zero day offset while other fields remain valid.
Fits split time reference: FITS time zero offset is reported in seconds while labeled days · case 02
The adapter reports an incorrect zero day offset while other fields remain valid.
Fits split time reference: FITS time zero offset is reported in seconds while labeled days · case 03
The adapter reports an incorrect zero day offset while other fields remain valid.
Fits split time reference: FITS time zero offset is reported in seconds while labeled days · case 04
The adapter reports an incorrect zero day offset while other fields remain valid.
Fits split time reference: FITS time zero offset is reported in seconds while labeled days · case 05
The adapter reports an incorrect zero day offset while other fields remain valid.
Fits split time reference: Reference-relative astronomical time accidentally includes the absolute reference epoch · case 01
The adapter reports an incorrect relative day while other fields remain valid.
Fits split time reference: Reference-relative astronomical time accidentally includes the absolute reference epoch · case 02
The adapter reports an incorrect relative day while other fields remain valid.
Fits split time reference: Reference-relative astronomical time accidentally includes the absolute reference epoch · case 03
The adapter reports an incorrect relative day while other fields remain valid.
Fits split time reference: Reference-relative astronomical time accidentally includes the absolute reference epoch · case 04
The adapter reports an incorrect relative day while other fields remain valid.
Fits split time reference: Reference-relative astronomical time accidentally includes the absolute reference epoch · case 05
The adapter reports an incorrect relative day while other fields remain valid.
Fits split time reference: Absolute-day import subtracts TIMEZERO in seconds instead of column units · case 01
The adapter reports an incorrect inverse tick while other fields remain valid.
Fits split time reference: Absolute-day import subtracts TIMEZERO in seconds instead of column units · case 02
The adapter reports an incorrect inverse tick while other fields remain valid.
Fits split time reference: Absolute-day import subtracts TIMEZERO in seconds instead of column units · case 03
The adapter reports an incorrect inverse tick while other fields remain valid.
Fits split time reference: Absolute-day import subtracts TIMEZERO in seconds instead of column units · case 04
The adapter reports an incorrect inverse tick while other fields remain valid.
Fits split time reference: Absolute-day import subtracts TIMEZERO in seconds instead of column units · case 05
The adapter reports an incorrect inverse tick while other fields remain valid.
Barycentric arrival corrections: Barycentric geometric delay omits source-direction projection · case 01
The adapter reports an incorrect roemer delay while other fields remain valid.
Barycentric arrival corrections: Barycentric geometric delay omits source-direction projection · case 02
The adapter reports an incorrect roemer delay while other fields remain valid.
Barycentric arrival corrections: Barycentric geometric delay omits source-direction projection · case 03
The adapter reports an incorrect roemer delay while other fields remain valid.
Barycentric arrival corrections: Barycentric geometric delay omits source-direction projection · case 04
The adapter reports an incorrect roemer delay while other fields remain valid.
Barycentric arrival corrections: Barycentric geometric delay omits source-direction projection · case 05
The adapter reports an incorrect roemer delay while other fields remain valid.
Barycentric arrival corrections: Barycentric timestamp drops supplied nongeometric propagation terms · case 01
The adapter reports an incorrect arrival while other fields remain valid.
Barycentric arrival corrections: Barycentric timestamp drops supplied nongeometric propagation terms · case 02
The adapter reports an incorrect arrival while other fields remain valid.
Barycentric arrival corrections: Barycentric timestamp drops supplied nongeometric propagation terms · case 03
The adapter reports an incorrect arrival while other fields remain valid.
Barycentric arrival corrections: Barycentric timestamp drops supplied nongeometric propagation terms · case 04
The adapter reports an incorrect arrival while other fields remain valid.
Barycentric arrival corrections: Barycentric timestamp drops supplied nongeometric propagation terms · case 05
The adapter reports an incorrect arrival while other fields remain valid.
Barycentric arrival corrections: Topocentric residual delay fails to subtract geocentric position already corrected · case 01
The adapter reports an incorrect topocentric residual while other fields remain valid.
Barycentric arrival corrections: Topocentric residual delay fails to subtract geocentric position already corrected · case 02
The adapter reports an incorrect topocentric residual while other fields remain valid.
Barycentric arrival corrections: Topocentric residual delay fails to subtract geocentric position already corrected · case 03
The adapter reports an incorrect topocentric residual while other fields remain valid.
Barycentric arrival corrections: Topocentric residual delay fails to subtract geocentric position already corrected · case 04
The adapter reports an incorrect topocentric residual while other fields remain valid.
Barycentric arrival corrections: Topocentric residual delay fails to subtract geocentric position already corrected · case 05
The adapter reports an incorrect topocentric residual while other fields remain valid.
Barycentric arrival corrections: Geocentric timing request accidentally retains observatory position · case 01
The adapter reports an incorrect geocentric arrival while other fields remain valid.
Barycentric arrival corrections: Geocentric timing request accidentally retains observatory position · case 02
The adapter reports an incorrect geocentric arrival while other fields remain valid.
Barycentric arrival corrections: Geocentric timing request accidentally retains observatory position · case 03
The adapter reports an incorrect geocentric arrival while other fields remain valid.
Barycentric arrival corrections: Geocentric timing request accidentally retains observatory position · case 04
The adapter reports an incorrect geocentric arrival while other fields remain valid.
Barycentric arrival corrections: Geocentric timing request accidentally retains observatory position · case 05
The adapter reports an incorrect geocentric arrival while other fields remain valid.
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 ↗