From 4c487c013dfa1a1e15fdd7068614353997312e03 Mon Sep 17 00:00:00 2001 From: igneum-labs <337424239+igneum-labs@users.noreply.github.com> Date: Wed, 7 Oct 2026 19:32:27 +0000 Subject: [PATCH] adv-accept report: yield test by owner (class-v5, or attack-pass with v5 in the label; never adv-) Co-Authored-By: Claude Fable 5.1 --- docs/analysis/cryptanalysis/report-acceptance-rule.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/analysis/cryptanalysis/report-acceptance-rule.md b/docs/analysis/cryptanalysis/report-acceptance-rule.md index e2b85b73e..62c439d59 100644 --- a/docs/analysis/cryptanalysis/report-acceptance-rule.md +++ b/docs/analysis/cryptanalysis/report-acceptance-rule.md @@ -401,7 +401,9 @@ Yield rule widened at 20:3x BST: whenever `lease status` shows a waiter whose ow label contains "v5" (the v5 census is queued as "class v5 c3 census"), any run of mine HOLDING pool cores is ended by its pgid file and re-queued at the back of the pool (a sweep from its frontier seed, its rows kept; a live chain minus the programs already done). I do this by hand from the status polls; nothing changes -while my leases are waiters. +while my leases are waiters. Refined at 20:3x BST: the test is by OWNER: yield to a waiter whose owner is +class-v5, or whose owner is attack-pass with "v5" in its label; never to a waiter whose owner starts with +adv- (so my own "v5-exemplar" label and the sibling lanes' leases are not yield triggers). ## Where the pass stands (for the 00:00 BST reading; numbers refreshed as rows land)