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
Post-charge idle occupancy fee: unfinished session handling · case 01
Sessions that never finished charging are charged an idle fee.
Post-charge idle occupancy fee: unfinished session handling · case 02
Sessions that never finished charging are charged an idle fee.
Post-charge idle occupancy fee: unfinished session handling · case 03
Sessions that never finished charging are charged an idle fee.
Post-charge idle occupancy fee: unfinished session handling · case 04
Sessions that never finished charging are charged an idle fee.
Post-charge idle occupancy fee: unfinished session handling · case 05
Sessions that never finished charging are charged an idle fee.
Shared circuit current allocation: minimum pilot current eligibility · case 01
Vehicles whose onboard charger accepts exactly 6 A are left paused.
Shared circuit current allocation: minimum pilot current eligibility · case 02
Vehicles whose onboard charger accepts exactly 6 A are left paused.
Shared circuit current allocation: minimum pilot current eligibility · case 03
Vehicles whose onboard charger accepts exactly 6 A are left paused.
Shared circuit current allocation: minimum pilot current eligibility · case 04
Vehicles whose onboard charger accepts exactly 6 A are left paused.
Shared circuit current allocation: minimum pilot current eligibility · case 05
Vehicles whose onboard charger accepts exactly 6 A are left paused.
Shared circuit current allocation: admission headroom · case 01
One more EV is admitted than the circuit can hold at the minimum current.
Shared circuit current allocation: admission headroom · case 02
One more EV is admitted than the circuit can hold at the minimum current.
Shared circuit current allocation: admission headroom · case 03
One more EV is admitted than the circuit can hold at the minimum current.
Shared circuit current allocation: admission headroom · case 04
One more EV is admitted than the circuit can hold at the minimum current.
Shared circuit current allocation: admission headroom · case 05
One more EV is admitted than the circuit can hold at the minimum current.
Shared circuit current allocation: priority ordering · case 01
Low-priority vehicles charge while high-priority vehicles are paused.
Shared circuit current allocation: priority ordering · case 02
Low-priority vehicles charge while high-priority vehicles are paused.
Shared circuit current allocation: priority ordering · case 03
Low-priority vehicles charge while high-priority vehicles are paused.
Shared circuit current allocation: priority ordering · case 04
Low-priority vehicles charge while high-priority vehicles are paused.
Shared circuit current allocation: priority ordering · case 05
Low-priority vehicles charge while high-priority vehicles are paused.
Shared circuit current allocation: capped vehicle surplus return · case 01
Amps released by vehicles with low onboard limits are not given to other vehicles.
Shared circuit current allocation: capped vehicle surplus return · case 02
Amps released by vehicles with low onboard limits are not given to other vehicles.
Shared circuit current allocation: capped vehicle surplus return · case 03
Amps released by vehicles with low onboard limits are not given to other vehicles.
Shared circuit current allocation: capped vehicle surplus return · case 04
Amps released by vehicles with low onboard limits are not given to other vehicles.
Shared circuit current allocation: capped vehicle surplus return · case 05
Amps released by vehicles with low onboard limits are not given to other vehicles.
Shared circuit current allocation: leftover amp ceiling · case 01
A vehicle is commanded one amp above the limit it advertised.
Shared circuit current allocation: leftover amp ceiling · case 02
A vehicle is commanded one amp above the limit it advertised.
Shared circuit current allocation: leftover amp ceiling · case 03
A vehicle is commanded one amp above the limit it advertised.
Shared circuit current allocation: leftover amp ceiling · case 04
A vehicle is commanded one amp above the limit it advertised.
Shared circuit current allocation: leftover amp ceiling · case 05
A vehicle is commanded one amp above the limit it advertised.
Shared circuit current allocation: leftover recipients · case 01
Paused vehicles receive a 1 A setpoint, below the minimum pilot current.
Shared circuit current allocation: leftover recipients · case 02
Paused vehicles receive a 1 A setpoint, below the minimum pilot current.
Shared circuit current allocation: leftover recipients · case 03
Paused vehicles receive a 1 A setpoint, below the minimum pilot current.
Shared circuit current allocation: leftover recipients · case 04
Paused vehicles receive a 1 A setpoint, below the minimum pilot current.
Shared circuit current allocation: leftover recipients · case 05
Paused vehicles receive a 1 A setpoint, below the minimum pilot current.
Shared circuit current allocation: equal share rounding · case 01
The sum of commanded currents exceeds the circuit breaker limit.
Shared circuit current allocation: equal share rounding · case 02
The sum of commanded currents exceeds the circuit breaker limit.
Shared circuit current allocation: equal share rounding · case 03
The sum of commanded currents exceeds the circuit breaker limit.
Shared circuit current allocation: equal share rounding · case 04
The sum of commanded currents exceeds the circuit breaker limit.
Shared circuit current allocation: equal share rounding · case 05
The sum of commanded currents exceeds the circuit breaker limit.
Charging profile stack resolution: validity end exclusivity · case 01
A profile keeps limiting current for one tick after it expired.
Charging profile stack resolution: validity end exclusivity · case 02
A profile keeps limiting current for one tick after it expired.
Charging profile stack resolution: validity end exclusivity · case 03
A profile keeps limiting current for one tick after it expired.
Charging profile stack resolution: validity end exclusivity · case 04
A profile keeps limiting current for one tick after it expired.
Charging profile stack resolution: validity end exclusivity · case 05
A profile keeps limiting current for one tick after it expired.
Charging profile stack resolution: relative schedule origin · case 01
Relative profiles step through their periods on the wall clock instead of session elapsed time.
Charging profile stack resolution: relative schedule origin · case 02
Relative profiles step through their periods on the wall clock instead of session elapsed time.
Charging profile stack resolution: relative schedule origin · case 03
Relative profiles step through their periods on the wall clock instead of session elapsed time.
Charging profile stack resolution: relative schedule origin · case 04
Relative profiles step through their periods on the wall clock instead of session elapsed time.
Charging profile stack resolution: relative schedule origin · case 05
Relative profiles step through their periods on the wall clock instead of session elapsed time.
Charging profile stack resolution: period ordering · case 01
The applied limit depends on the order periods were listed in the message.
Charging profile stack resolution: period ordering · case 02
The applied limit depends on the order periods were listed in the message.
Charging profile stack resolution: period ordering · case 03
The applied limit depends on the order periods were listed in the message.
Charging profile stack resolution: period ordering · case 04
The applied limit depends on the order periods were listed in the message.
Charging profile stack resolution: period ordering · case 05
The applied limit depends on the order periods were listed in the message.
Charging profile stack resolution: stack level precedence · case 01
Two equal-stack profiles resolve to the later one in the list.
Charging profile stack resolution: stack level precedence · case 02
Two equal-stack profiles resolve to the later one in the list.
Charging profile stack resolution: stack level precedence · case 03
Two equal-stack profiles resolve to the later one in the list.
Charging profile stack resolution: stack level precedence · case 04
Two equal-stack profiles resolve to the later one in the list.
Charging profile stack resolution: stack level precedence · case 05
Two equal-stack profiles resolve to the later one in the list.
Charging profile stack resolution: tx replaces default · case 01
A transaction profile raising the limit is ignored because the default profile still applies.
Charging profile stack resolution: tx replaces default · case 02
A transaction profile raising the limit is ignored because the default profile still applies.
Charging profile stack resolution: tx replaces default · case 03
A transaction profile raising the limit is ignored because the default profile still applies.
Charging profile stack resolution: tx replaces default · case 04
A transaction profile raising the limit is ignored because the default profile still applies.
Charging profile stack resolution: tx replaces default · case 05
A transaction profile raising the limit is ignored because the default profile still applies.
Charging profile stack resolution: bounding source tie order · case 01
The reported bounding source is the hardware limit even though a max profile equals it.
Charging profile stack resolution: bounding source tie order · case 02
The reported bounding source is the hardware limit even though a max profile equals it.
Charging profile stack resolution: bounding source tie order · case 03
The reported bounding source is the hardware limit even though a max profile equals it.
Charging profile stack resolution: bounding source tie order · case 04
The reported bounding source is the hardware limit even though a max profile equals it.
Charging profile stack resolution: bounding source tie order · case 05
The reported bounding source is the hardware limit even though a max profile equals it.
Charging profile stack resolution: relative profile without session · case 01
A relative profile applies before any transaction has started.
Charging profile stack resolution: relative profile without session · case 02
A relative profile applies before any transaction has started.
Charging profile stack resolution: relative profile without session · case 03
A relative profile applies before any transaction has started.
Charging profile stack resolution: relative profile without session · case 04
A relative profile applies before any transaction has started.
Charging profile stack resolution: relative profile without session · case 05
A relative profile applies before any transaction has started.
Connector reservation conflict check: trailing buffer boundary · case 01
A reservation starting exactly one buffer after the previous one is rejected.
Connector reservation conflict check: trailing buffer boundary · case 02
A reservation starting exactly one buffer after the previous one is rejected.
Connector reservation conflict check: trailing buffer boundary · case 03
A reservation starting exactly one buffer after the previous one is rejected.
Connector reservation conflict check: trailing buffer boundary · case 04
A reservation starting exactly one buffer after the previous one is rejected.
Connector reservation conflict check: trailing buffer boundary · case 05
A reservation starting exactly one buffer after the previous one is rejected.
Connector reservation conflict check: leading buffer · case 01
A new reservation may end right as the next one starts, leaving no turnover time.
Connector reservation conflict check: leading buffer · case 02
A new reservation may end right as the next one starts, leaving no turnover time.
Connector reservation conflict check: leading buffer · case 03
A new reservation may end right as the next one starts, leaving no turnover time.
Connector reservation conflict check: leading buffer · case 04
A new reservation may end right as the next one starts, leaving no turnover time.
Connector reservation conflict check: leading buffer · case 05
A new reservation may end right as the next one starts, leaving no turnover time.
Connector reservation conflict check: connector range · case 01
Requests for the highest-numbered connector are rejected and connector 0 is accepted.
Connector reservation conflict check: connector range · case 02
Requests for the highest-numbered connector are rejected and connector 0 is accepted.
Connector reservation conflict check: connector range · case 03
Requests for the highest-numbered connector are rejected and connector 0 is accepted.
Connector reservation conflict check: connector range · case 04
Requests for the highest-numbered connector are rejected and connector 0 is accepted.
Connector reservation conflict check: connector range · case 05
Requests for the highest-numbered connector are rejected and connector 0 is accepted.
Connector reservation conflict check: empty request window · case 01
A zero-length reservation is accepted and blocks a connector.
Connector reservation conflict check: empty request window · case 02
A zero-length reservation is accepted and blocks a connector.
Connector reservation conflict check: empty request window · case 03
A zero-length reservation is accepted and blocks a connector.
Connector reservation conflict check: empty request window · case 04
A zero-length reservation is accepted and blocks a connector.
Connector reservation conflict check: empty request window · case 05
A zero-length reservation is accepted and blocks a connector.
Connector reservation conflict check: same-connector filter · case 01
A booking on connector 2 blocks a free connector 3.
Connector reservation conflict check: same-connector filter · case 02
A booking on connector 2 blocks a free connector 3.
Connector reservation conflict check: same-connector filter · case 03
A booking on connector 2 blocks a free connector 3.
Connector reservation conflict check: same-connector filter · case 04
A booking on connector 2 blocks a free connector 3.
Connector reservation conflict check: same-connector filter · case 05
A booking on connector 2 blocks a free connector 3.
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 ↗