FA-93174 / EV charging session scheduling / Member archive

Demand-response curtailment of a charge plan: event end exclusivity · case 04

Curtailment lingers one slot after the event ends.

Member previewVariant 4 · 3 implementations · 7 checks per implementation

Case contract

profile is planned watts per slot. events are [start, end, pct, opt_out]; during [start, end) a non-opted-out event limits power to pct percent of plan (integer floor of p*pct/100), and overlapping events apply the lowest pct. Curtailed power never drops below min(plan, floor_w). Return [new profile, total curtailed watts over slots].

Why this case matters

Depot, workplace and public EV chargers schedule sessions against prices, circuit limits and departure deadlines; a wrong decision silently strands a driver or overloads a feeder.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
boundary: event ends at slot	`[[1840, 1840, 3680], 3680]`	`[[1840, 3680, 3680], 1840]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.