diff --git a/docs/analysis/cryptanalysis/report-acceptance-rule.md b/docs/analysis/cryptanalysis/report-acceptance-rule.md
index e1d3f645d..ba2e19260 100644
--- a/docs/analysis/cryptanalysis/report-acceptance-rule.md
+++ b/docs/analysis/cryptanalysis/report-acceptance-rule.md
@@ -633,6 +633,18 @@ s04 and s08 so the live hot-set chain on the five new lowest seeds of 88,051 (12
 602822; stand-in ratios 0.9885 to 0.9942) queues ahead of them; s06b from 603875, s04 and s08 re-queued
 behind it. Build-1: the 2^20 ratio read of the same five queued at 8 cores, min 4 (gap-newlow5).
 
+22:07 to 22:18 BST, box 2: the mechanical yield fired. At 22:08 an attack-pass "v5 gate" waiter (class v5)
+appeared while I held three sweeps; main's order followed at 22:17 (the F8 gate on the frozen class v5 tip,
+two halves of 32 at min 24, cannot start because the pool pre-empts only above 32 threads). Ended by pgid
+file: sweep-s02c (9,406 rows kept, frontier 221536, ended 22:07 to make room for the 122960 read),
+sweep-s00c (13,176 rows, frontier 29496), sweep-s06b (5,914 rows, frontier 609791), sweep-s04 (601 rows,
+frontier 400603), sweep-s08 (no rows yet). Box 2 read 0 sweep holders of mine at 22:17:57 and both F8
+halves held 32 and 30 cores. Kept on box 2: gap-122960 at 8 cores (the decisive 2^20 read of the deepest hot
+set), queued at 22:06 and still waiting for cores at 22:18 (its first 600 s window passed with no DONE line;
+a blank summary from that window is not a result and is not reported). The box-2 shards re-queue from their
+frontiers once the halves finish. Rule from here, mechanical: on any box where `lease status` shows a class
+v5 waiter, an adv-accept lease releases at its shard end whatever its size.
+
 ## Where the pass stands (for the 00:00 BST reading; numbers refreshed as rows land)
 
 | Item | Reading (20:50 BST; rows that land later are added above this table) |