FA-92480 / HVAC thermostat control / Member archive

Schedule entries are scanned in the order they were entered · case 05

Editing an earlier period after a later one makes the lookup stop at the wrong event.

Member previewVariant 5 · 3 implementations · 8 checks per implementation

Case contract

Programmable thermostat weekly schedule. schedule is an unordered list of [day 0=Monday..6, minute_of_day, setpoint]; queries are [day, minute]. The active setpoint is that of the latest event at or before the query time within the week; if none, the last event of the week carries over from the previous week. Return the active setpoint per query.

Why this case matters

Residential and light-commercial thermostats make these decisions sample by sample; each defect changes equipment calls in a way that shows up as short cycling, comfort complaints or equipment stress.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
regression: scenario 4	`[600, 700, 600, 700, 700, 700, 700, 700, 720]`	`[600, 680, 600, 700, 650, 680, 650, 700, 700]`	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.