3 Commits

Include renames

Author	SHA1	Message	Date
glenn schrooyenandClaude	a66a7f1a0f	SAFETY-126 round 2: state what the 10 W tolerance costs; test the latch reset ... Text only (DECISIONS, DOCS, CHANGELOG): a step load alarms on the same cycle as before; a steadily rising load alarms a little later; with peak_margin_w 0 a period can end up to 10 W over the limit without this alarm, as for 'Load too high' (SAFETY-81). Owner accepted 2026-10-31. test_safety126.py part 2: after a real overrun ends, _peak_landing()'s latch is reset and the night's later landings are quiet (review F3). Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-31 11:52:27 +01:00
glenn schrooyenandClaude	8e2463bc32	SAFETY-126: test reads through named_absence; points at MUTATION.md ... Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-31 01:54:16 +01:00
glenn schrooyenandClaude	40595e42ae	SAFETY-126: a landing error on the aim is not an overrun ... During the night grid charge under the peak reserve the guard alarmed (ERROR PEAK_GUARD_FLOOR_LIMITED, "Battery stopped limiting the peak") and the Batteries "Why" said "The peak limit needs power" at quarter ends, while every quarter landed on the aim. The charge lands the period 0-7 W over the aim and excess_w()'s 900 / remaining turns that into tens of kW in the last second; with nothing able to give, check_peak_floor_limited() alarmed on any wanted > 0. Each cycle the guard wants power, _peak_landing() asks misses_aim(): with the batteries at 0 W, does the period end more than ALARM_MISS_W over the aim? If not, the decision is within_aim: no reserve alarm, no red peak row, no "Why" peak. The claim and the commands are unchanged. A real overrun under the reserve alarms on the same cycle as before. Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-31 01:26:02 +01:00