diff --git a/docs/plans/cryptanalysis/in-house-pass.md b/docs/plans/cryptanalysis/in-house-pass.md index 197decd2d..1871c94db 100644 --- a/docs/plans/cryptanalysis/in-house-pass.md +++ b/docs/plans/cryptanalysis/in-house-pass.md @@ -43,7 +43,7 @@ Three per target, one question class each, from funding.md's ranked list for tha | adv-accept-2 | acceptance rule | header grinding for locality: header bytes and nonce against DRAM rows, lines and items; cost against gain | `adv-accept-2` | `igneum-wt-adv-accept-2` | `plan-acceptance-rule-2.md` | `report-acceptance-rule-2.md` | 20:25 | | adv-accept-3 | acceptance rule | exhaustion or steering of the draw: the 256-attempt cap, the last-resort draw, seed steering, the program id | `adv-accept-3` | `igneum-wt-adv-accept-3` | `plan-acceptance-rule-3.md` | `report-acceptance-rule-3.md` | NOT YET SPAWNED at 19:26 BST (the session's 20-subagent cap); spawned when a slot frees, plan due one hour after | -Plans live in `docs/plans/cryptanalysis/`, reports in `docs/analysis/cryptanalysis/`. Each lane's branch starts from the build mirror's `master` (`3f0afcd5`) and is pushed to the build mirror only. GitHub is dark tonight. +Plans live in `docs/plans/cryptanalysis/`, reports in `docs/analysis/cryptanalysis/`. Each lane's branch was cut from the build mirror's `master` and is pushed to the build mirror only; GitHub is dark tonight. BASE CORRECTION (main, 19:4x BST, from the hash lane): build-2's mirror master was stale (`a4bca198`, pre-fix) until 18:25:42Z, and the first branches were cut from `3f0afcd5`, whose `igneum-pow` differs from the frozen object by 6 files (verified by this lane: 30 insertions, 635 deletions). Every lane merges build-1's `master` (`7a7caa34` or later; `001e32ec` is the earliest good tip) before any run or report and proves `git diff --quiet 017e7037 HEAD -- igneum-pow` identical, stating the commit in its plan; anything built or measured on a stale tree is void. `crypto-engage` itself merged `7a7caa34` at 19:27 BST (355ac2ae, identical). ## 3. The rule set @@ -83,7 +83,7 @@ Standing rule from the project lead through main (7 October 2026, 19:1x BST), bi | Rule | What it means for a lane | |---|---| -| Every idle core on both boxes | A lane runs on build-1 and build-2 together, on every idle core, at nice 10, no core band; release builds and the class v5 suites keep priority | +| Every idle core on both boxes | A lane runs on build-1 and build-2 together, on every idle core, at nice 10, no core band; release builds and the class v5 suites keep priority. the project lead's read at 19:4x BST: build-1 at 11 percent, build-2 at 56; his word is both near max, so CPU-bound sweeps go to build-1 explicitly (`--box 1`) and both boxes stay above 80 percent until the queue is empty; the build-server lane raises the lease pool to about 88 cores per box | | Yield to builds | The capacity layer's pattern (`infra/build-server`, the yield-to-builds workload): the run polls `/srv/builds/_locks` every 5 s, SIGSTOPs its own process group while any `build-` or `measure` lock is held, SIGCONT when clear | | Back to back | Question `n + 1`'s sweep starts the minute question `n`'s ends; no waiting for a human to read; each result row lands in the report and is pushed as it lands | | No lane idle | Every planned sweep is a self-contained executable in `/srv/builds/_adv//queue/NN--.sh` on build-2 (binary path, args, log path, pid file); a lane claims a file before running it with `mkdir /srv/builds/_adv//claims/` (atomic); a lane whose own queue is empty claims the next unclaimed file of any sibling on its target, runs it, and names the owner in its report |