diff --git a/docs/analysis/cryptanalysis/report-acceptance-rule.md b/docs/analysis/cryptanalysis/report-acceptance-rule.md
index cca958f68..0cf90918e 100644
--- a/docs/analysis/cryptanalysis/report-acceptance-rule.md
+++ b/docs/analysis/cryptanalysis/report-acceptance-rule.md
@@ -826,7 +826,11 @@ and the full igneum-pow suite (waiting since 00:55 with 0 free; my three holders
 32-thread line where the pool's pre-emption did not reach them). Ended by pgid file: sweep-s08 (46,044 rows
 kept, frontier 849304) and sweep-s06c (40,679 rows kept, frontier 652538); my two adv waiters (s04b, s00g)
 withdrawn so they do not take the freed cores; sweep-s02e (23 cores) left running. The four shards re-queue
-from their frontiers once the v5 runs hold cores (or after 20 minutes).
+from their frontiers once the v5 runs hold cores (or after 20 minutes). Record: at 01:04 and 01:07 BST
+`lease status` on box 2 showed no class-v5 or release waiter or holder at all, so the v5 lane's two runs
+go through another path than the pool (the bounded suite slot, most likely) and the 64 freed cores stood
+free; at 01:07 the live chain on the three tail seeds that surfaced after the 23:50 count (228763, 638990,
+623492) took 32 of them, with their 2^20 read queued beside it at 8 cores.
 
 ## Where the pass stands: the 00:00 BST reading (count refreshed 01:08 BST, 8 October; pool state at 23:50 BST)