SAFETY-129 round 3: the real reason for the 16 s limit, a slow-start check, the row's tail

Co-Authored-By: Claude <noreply@anthropic.com>
2026-11-07 00:12:33 +01:00
parent 03541a1eee
commit c70eeb6916
3 changed files with 22 additions and 8 deletions
@@ -174,8 +174,10 @@ M_SHARE, M_BETTER = 0.4, 0.7
 # SAFETY-129: a meter slower than that (a 5 s P1) has fewer than M_ROWS values
 # in M_FIT_S, so it is fitted over M_SLOW_FIT_S instead, from the same M_ROWS
 # values. It calls a delay late only over M_SLOW_LATE_S and on ON_FITS fits in
-# a row: the slow-battery runs (10-12 s dead time, R2-1) read up to 15 s at a
-# 5 s meter, and a 10 s lag cannot be told from them, nor does it swing.
+# a row. Alone it reads 35-90 s on healthy runs, a few times in a row; what
+# keeps those from a verdict is the slow-start and battery-fit check in
+# watch(), not the limit. A 10 s lag is not found: it cannot be told from a
+# slow battery (R2-1), nor does it swing at 5 s.
 M_SLOW_FIT_S = 120.0
 M_SLOW_LATE_S = 16.0
 # A meter fit counts only after an ask that took this long to start moving a