igneum-network/igneum
1
0
Fork 0
Code Issues Pull requests Releases Activity

adv-accept report: ledger of the 21:26 to 21:36 BST clearances and re-queues

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-07 20:38:02 +00:00
parent bda21085f3
commit 2e48abab54
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/analysis/cryptanalysis/report-acceptance-rule.md
View file

@ -597,6 +597,17 @@ re-submitted through the ranked lease at 32/16 in order: the 3 remaining random
202482, shard 00 from 11830, shards 04/06/08. The yield stays mechanical: a class-v5 or attack-pass
v5-labelled waiter means release at shard end unasked.
21:26 to 21:36 BST, clearances for the decisive 2^20 reads (main's five-program job and my 1738 read were
starved behind my own shard holders): box 2, ended sweep-s00b (4,482 rows kept as part 1, frontier 16319)
and withdrew the waiting shards, then ended sweep-s02 (9,642 rows kept, frontier 212128) and withdrew again,
so gap-hot2 took 8 cores at 21:31 and the two five-program leases ran at 21:32 to 21:35; re-queued at 21:36:
s02c from 212128, s00c from 16319, s04/06/08. Box 1, ended sweep-s05 (2,124 rows kept, frontier 502127) and
withdrew attempts-20k and the shards, then ended sweep-s01b (27,131 rows kept as part 1, frontier 138766),
re-queued s01c from 138766 plus attempts-20k, s05 from 502127, s03/07/09; gap-hot3 still waited at 21:36
(other lanes' adv waiters ahead by arrival). Every end was by pgid file; no rows were lost (every sweep
writes its rows as they land); the inline-deletion rule of 21:33 BST touches nothing here (run-box.sh has no
rm and no truncation inside a bash -c string; the clearances renamed logs with mv).
## 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) |