6 Commits

Include renames

Author	SHA1	Message	Date
glenn schrooyenandClaude Opus 5.5	88b9cd470a	SAFETY-96: a battery the loop cannot move does not freeze it ... At N>=2 a battery out of the split (stale link), with refused writes, or settling after a step the loop did not make (a charge end, a rejoin) now counts in the freeze test at its command, not its reading. Its real power still reaches the loop through the meter. At a drop its share leaves the loop's start point (the others take over one slew step a cycle); at a rejoin it enters at its reading. No refusal is learned while a battery's writes are refused. N=1 and the 46 identity digests are byte-identical. test_safety78 part 2: the dropped-drain case now rests at B 1510 W (grid at its -10 W aim) instead of 1500 W; the drop no longer sends B to 2500 W. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-06 04:02:03 +02:00
glenn schrooyenandClaude Opus 5.5	4b81387908	SAFETY-85: no false 'not keeping up' while maintenance or the peak guard sets the battery ... The loop's integrator bound counts only on a cycle the loop decided. A battery another owner set (maintenance, the peak guard, a safety limit) alarms only when it gives more than saturation_w less than told for saturation_cycles cycles. At N>=2 the loop is bounded while maintenance holds a battery, so it does not wind and control comes back one slew step a cycle. The status row counts episodes, not cycles. Digests re-pinned where behaviour changed on purpose; DECISIONS/SAFETY-85-no-false-not-keeping-up.md has the list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019DBUfvndgHwaV339Fvd2gr	2026-10-01 19:05:27 +02:00
adminandClaude Opus 5.5	d77f1b1fdf	SAFETY-83: peak guard outranks the maintenance drain at N=1 ... At N=1 the drain is the site SET at P_MAINTENANCE (60), so the peak floor (P_PEAK, 50) was not applied and the house imported what the drain left. Where the floor asks for more than the drain rate, main.py now refiles the peak claim at P_MAINTENANCE, so it wins; safety SETs still park everything. Nothing else changes: safety78_identity --diff against 35cdffe changes only cycles where the guard wanted more than the drain; N=2 is byte-identical. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-29 22:40:14 +02:00
goodwe-review	044fc0d5bd	SAFETY-78 review: card truth while the drain waits, more checks ... - homeview: no "This one does not charge" while the draining battery waits (no floor then, so the other battery may charge from solar). - test_safety78: one wait line across a probe, a second episode logs again, the card while waiting, and a seeded sweep of the floor against every other claim (part 6). - DECISIONS: the wait case, and the measured N=1 peak and N=2 charge follow-ups. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-29 21:13:31 +02:00
Claude	af39c10893	SAFETY-78: test_safety78 points at MUTATION.md (test_bytecode) ... Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-29 20:14:33 +02:00
Claude	5d27f8496f	SAFETY-78: maintenance drain at N=2 no longer stalls ... At two inverters the drain pins its pack and the site target is split around the pin. Below the pin the other pack had to charge, the allocator refused the opposite directions, and the site sat at 0 W with an ARBITER line every cycle (house below or above the drain rate, or a grid charge). main.py now files a site limit `drain` (lo = what the pin places, at P_MAINTENANCE) at N>=2 while a pack drains, so the other pack only adds power in the same direction. A drain that cannot give power waits with one log line. With battery modes on, no grid charge while a pack drains, and the other battery's card says why. N=1 is byte-identical. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-29 19:52:51 +02:00