diff --git a/docs/analysis/cryptanalysis/report-acceptance-rule.md b/docs/analysis/cryptanalysis/report-acceptance-rule.md
index 2fb030e7b..5bb1d22aa 100644
--- a/docs/analysis/cryptanalysis/report-acceptance-rule.md
+++ b/docs/analysis/cryptanalysis/report-acceptance-rule.md
@@ -5,8 +5,19 @@ internal adversarial pass, not an independent review
 - Target commit: 017e70376489251e18564c0abce7e466e606c8b3 (class v4 sub-version 3, object byte 7).
 - Crate built: igneum-pow at the frozen commit (this worktree's igneum-pow/ is reset to it; build/master
   diverged by 635 deletions and is not used). Harness: tools/attack/adv-accept (depends on igneum-pow by path).
-- Binary sha256: e3d35f4464937f91aac0648e2ee7134f33c85c7aa314b87b33f91059dedc6682
-- Box: igneum-build-2 (build class, nice 10, core band 0-31). Logs under /srv/builds/igneum-wt-adv-accept/adv/.
+- Re-base (19:3x BST): build/master moved to 7a7caa34 whose igneum-pow IS the frozen object; merged at
+  8748e955ceb48be5a6cbf7f8718a4884d3de9828; `git diff --quiet 017e7037 HEAD -- igneum-pow` prints IDENTICAL.
+  Nothing measured here was on a stale tree: igneum-pow/ had been reset to the frozen object before the first build.
+- Binary sha256 (first build, box 2): e3d35f4464937f91aac0648e2ee7134f33c85c7aa314b87b33f91059dedc6682 (adv-accept
+  single-binary build); the two-binary build (adv-accept, adv-live = the unmodified f8 harness) sha256 is logged per
+  box in the run sections below.
+- Boxes: igneum-build-1 (CPU-bound sweeps, by the coordinator's order) and igneum-build-2 (shard 0, already there).
+  nice 10 on every idle core, the capacity layer's yield (run-box.sh). Logs under
+  /srv/builds/igneum-wt-adv-accept/adv/ on each box (spared from the checkout clean by .igneum-scratch-spare; the
+  first 10k log on box 2 was wiped by a rebuild before the spare existed and is void anyway: old labels, old binary).
+- Lane scope since 19:2x BST: THE BYPASS (Q1, Q2, Q5). Q3 is lane adv-accept-3's, Q4 lane adv-accept-2's.
+- Seed space: the attack-pass F8 label space (program k = seed_words("igneum-attack-f8/program/k"), era
+  ".../era/k"), so `adv-live warps --program k` measures the live hot set of exactly the program the sweep reports.
 - rustc 1.99.0 both sides. First results by 8 October 2026 18:00 BST. GPU: not available, so any per-card
   hash-rate confirmation of a gain is BLOCKED and said so.
 - Box-hours spent so far: about 0.1 (one 7 s build, three short runs). Budget 8.
@@ -35,13 +46,25 @@ source register immediately before the load makes the rule reject with "(a') loa
 fresh by dataflow in the loop's steady state". So the harness reads the real rule, not a copy.
 Command: `adv-accept plant --seed 0` on box 2.
 
-## Q1 and Q5: the accepted-program sweep (RUNNING)
+## Q1 and Q5: the accepted-program sweep (RUNNING, sharded)
 
-Command (box 2, background): `adv-accept sweep --seeds 10000 --threads 32 --ratio-units 256 --out
-/srv/builds/igneum-wt-adv-accept/adv/sweep-10k.txt`. Log
-/srv/builds/igneum-wt-adv-accept/adv/sweep-10k.log, pid file beside it. Seeds: epoch bytes =
-LE words of seed_words_from_bytes("igneum-adv-accept/epoch/k"), era bytes of ".../era/k", for
-k = 0..9999; each drawn through the chain path generate_era(V4_CLASS, V3_ALLOWED), which runs the
+Ten shards of 100,000 seeds (k = 2..1,000,001 of the F8 label space), each
+`adv-accept sweep --seed-start S --seeds 100000 --threads 96 --ratio-units 256 --out
+/srv/builds/igneum-wt-adv-accept/adv/sweep-sNN.txt`, started through run-box.sh (nice 10, yield to
+builds, pid/pgid/yield pid files beside the log). Shard 00 (S = 2) on box 2, started 18:27Z. Shard 01
+(S = 100,002) on box 1, started 18:30Z. Shards 02..09 sit as self-contained scripts in
+/srv/builds/_adv/accept/queue/ on box 2 (claim by mkdir under claims/), to be run back to back on
+whichever box has idle cores. Every row is written as it lands, so a partial shard is data.
+
+Live hot set (the measure the chip model prices): `adv-live warps --program k --nonces N` (the
+unmodified f8 harness: the day's items derived into a table, the cross-hash item histogram, the
+hot-set test X_f >= f against the window-model control, the 6-sigma test, library agreement checks).
+Known-failed shape run first: `--plant const-item` on program 2 at 10^6 nonces (box 1, 18:30Z, log
+adv/live-plant-p2.log) beside its clean control (adv/live-control-p2.log). The plant must be FLAGGED
+and the control clear before any live number below is trusted.
+
+Seeds: epoch bytes = LE words of seed_words_from_bytes("igneum-attack-f8/program/k"), era bytes of
+".../era/k"; each drawn through the chain path generate_era(V4_CLASS, V3_ALLOWED), which runs the
 full attempt loop and the real acceptance rule.
 
 Per accepted program the sweep records: attempt, program id, the closed-form distinct-item mean per
diff --git a/docs/plans/cryptanalysis/plan-acceptance-rule.md b/docs/plans/cryptanalysis/plan-acceptance-rule.md
index 598fa8842..12e7c70dc 100644
--- a/docs/plans/cryptanalysis/plan-acceptance-rule.md
+++ b/docs/plans/cryptanalysis/plan-acceptance-rule.md
@@ -28,6 +28,13 @@ worktree to the frozen crate and packs:
 Every build and run in this pass is against the frozen crate. My harness crate depends on it by
 path (../../../igneum-pow), as f8-uniform does.
 
+Re-base (coordinator's order, 19:3x BST): build/master moved to 7a7caa34, whose igneum-pow/ IS the
+frozen object. Merged into this branch at 8748e955ceb48be5a6cbf7f8718a4884d3de9828;
+`git diff --quiet 017e7037 HEAD -- igneum-pow` prints IDENTICAL, and the same check against
+build/master 7a7caa34 prints IDENTICAL. Nothing I built or measured was on the stale tree: this
+worktree's igneum-pow/ had already been reset to the frozen object (byte-identical) before the first
+build, so the harness binaries are of the frozen crate; they are rebuilt at the merged HEAD anyway.
+
 ## 1. Files I opened
 
 Only the public kit, read at the frozen commit unless marked HEAD: