diff --git a/docs/analysis/class-v6/family-gate.md b/docs/analysis/class-v6/family-gate.md index 9586ffc68..0cc61736a 100644 --- a/docs/analysis/class-v6/family-gate.md +++ b/docs/analysis/class-v6/family-gate.md @@ -285,7 +285,8 @@ Reading. At width 4 the statistic itself moves, not just its tail: a tenth of th Point A DONE (build-1, 11:3x to 13:49 BST, 4,783 s on 24 pool cores, about 32 core-hours; `logs/f8-A.log`): attack-f8's 64-seed census (p2 to p65 of the F8 label space, each seed its own era, 2^24 nonces each, the window-model control, the by-site attribution) built against the family crate with the band era 49's weight table (add 17, xor 6, mul 4, mad 13, shfl 9, rotl 9, sub 2, mulhi 2, rotr 9, or 4) at shape 256 x 27 and width 1. The class-v5 tree's copy of attack-f8 predates the `--class v5` path, so the draws are generator 4 under the family's shape predicate: sub-version 3's rule with (c'') at 0.98 and WITHOUT class v5's (c''') floor at 0.995. Result: 45 of 64 PASS with no test fired; 3 beyond 1.2x of the window model at the top 0.1 percent (p38 1.678x, p54 1.589x, p4 1.297x; the shipped class read 4 of 64 over, p4 among them at 1.217x); HOT SETS in 2 (p54: X at 0.1 percent +0.120, X at 1 percent +0.684; p38: +0.102 and +0.576), against 0 of 64 on the shipped class; windowed 64-item buckets beyond 6 sigma in 18 of 64 (the bit-level class of section 6.2 seen on the live item map: p38's largest bucket +106 sigma, p4's +84), against the shipped class's 4. The class v5 floor's read on the same 64 programs (`v5_hot_census` under the same weight table, build-3, queued at 13:5x BST) says whether (c''') refuses p38 and p54 as it refused the nine hot sets of the in-house pass; LANDED 14:3x BST (build-3, 79 s on 8 threads, `logs/floor-read-A.log`): the class v5 floor at 0.995 refuses 3 of the 64 class v4 draws, p38 at 0.9932 (site 0), p54 at 0.9945 (site 12) and p11 at 0.9933, so BOTH hot sets of point A are refused and the class v5 draw moves to the next attempt (min ratio 0.9999 on each); p4 at 0.9963 passes, as it did on the shipped class. The floor does under the family's weights what it did on the shipped class: nine of nine then, two of two now. What a chip gets from p54 as it stands (on the class v4 rule; under class v5 it never runs): the top 1 percent of items (16 MiB) holding 0.68 percent more of the reads than the window model, the 1.002x class of the ledger, no row of the chip model moves; what an auditor sees is two hot sets in 64 epochs where the shipped class had none, which is the per-era weight axis showing on the item map and the reason the floor is a per-epoch rule and not a per-class census. -Point B (build-3, band era 5's weights 11,15,6,9,7,11,4,6,2,4 at shape 64 x 108; `logs/f8-B.log`): PENDING at 16:00 BST, 24 of 64 PASS at 13:4x. +Point B DONE (build-3, 12:2x to 15:30 BST on 8 then 16 pool cores; `logs/f8-B.log`, `logs/floor-read-B.log`): the same census at shape 64 x 108 with the band era 5's weight table (add 11, xor 15, mul 6, mad 9, shfl 7, rotl 11, sub 4, mulhi 6, rotr 2, or 4). Result: 46 of 64 PASS with no test fired; HOT SETS in 0; 5 beyond 1.2x of the window model at the top 0.1 percent (p10 1.505x, the seed the shipped class reads at 1.504x with the same hottest item; p42 1.472x; p64 1.351x; p18 1.215x; one more at 1.2x to 1.21x), against the shipped class's 4 of 64; windowed buckets beyond 6 sigma in 18 of 64 (p64's largest bucket +150 sigma, p42's +105, p10's +100: the bit-R class again); the class v5 floor refuses 1 of the 64 draws (p15 at 0.9934, the draw moving to attempt 4 at 0.9993), the next lowest 0.9957 to 0.9962 pass. So the 64-instruction shape under a band table reads the shipped class's own profile on the live item map (the same tail seeds over 1.2x, no hot set, the same bucket class), and the shape axis moves the draw's cost (section 6.4) and nothing on the item map. Across the two points: 128 live epochs of the band, 2 hot sets (both at the 256 shape, both refused by the floor), 8 over 1.2x (the shipped class: 4 of 64), 36 with a site over 6 sigma on the windowed buckets (the shipped class: 4 of 64; the bit-R mechanism of section 6.8, which the family's weight tables widen from a 6 percent to a 28 percent share of epochs on the live map); chip price of the worst: the 1.002x class of the ledger. What this ring-C pair bounds: the fraction of band epochs with a hot set under the class v4 rule is under 3/128 = 2.3 percent at 95 percent, and 0 of 2 reached the chain under class v5's floor. + ### 6.7 The mixer axis per family: the verifier rows at x4, x8 and x16 (build-3, 15:1x BST, `logs/bench-x{4,8,16}.log`) @@ -320,11 +321,12 @@ Reading. (1) Every named case is the SAME mechanism at the bit level: a product' 1. DONE 13:2x BST: the lossy-share curve per shape (section 6.4) and the last-resort scan's verdicts on every exhausted era. 2. DONE 14:4x BST: the pre-floor spread at width 4 against width 1 under the band and the floor decision (section 6.5: 0.995 kept at width 4 at its measured cost; the 0.990 to 0.995 band at width 4 read live before any floor moves). -3. By 16:00: the two ring-C live-dataset rows (section 6.6; point A on build-1, point B on build-3). +3. DONE 15:30 BST: the two ring-C live-dataset rows (section 6.6: 128 live epochs of the band, 2 hot sets at the 256 shape both refused by the floor, 0 at the 64 shape). 4. DONE 15:1x BST: the x4, x8 and x16 verifier rows (section 6.7, build-3 one core: 3.73 / 4.12 / 7.13 ms per warp; x16 outside the band on the 10 ms gate by scaling to the proxies). 5. DONE 14:4x BST: the width-4 plus shape-64 crossing (build-4, 3,000 eras: r = 0.654, 0 exhausted, (c''') 5.3 percent of candidates, the width's floor cost again) and section 6.8, the F8 label space's p2 to p65 and p212 to p225 through the sigma form at the shipped parameters (build-2, queued 14:0x BST), so the two F8-256 attributions the hash lane added to layer 4's bucket-bound row (p212, site 9 at 1.75x its window expectation; p225, a value-level concentration at a mad-written site with the bucket at expectation) and the morning's four tail seeds are read as known-failed cases of the bucket-sigma and bit-bias tests on one scale; and the bucket bound in sigma (from the bit-clean spread: p99 +6.8, p99.9 +16.5 to +20.1, max +35 over 9,409 eras; a band at +8 refuses 0.3 to 0.4 percent of bit-clean programs and 11 to 18 percent of all, which is the biased population, so the bucket bound and the bit read are one rule). 6. The gate-record form: `logs/gate-records-lossy-base.jsonl` (3,000 records of the band stratum in the section 4.3 shape, one per line, 3.6 MB) and `logs/fg-records.py`, which derives every other stratum's records from its TSV rows in this directory. -7. Not in this report: the mixer ladder re-run at m = 4 and 16 (adv-mixer-3's harness rows; the per-family rows of section 4), the F8 census at D = 29 (the stand-in gap row), the 10^5-program verifier census at the top corner (F6 per family): each a named per-family row with its hours in section 4.1. +7. Amendment by 18:00 BST (the coordinator's order of 15:45): the research lane's best-mix genesis table (add 16, xor 14, mad 12, rotl 11, sub 10, rotr 10, shfl 4, mul 4, mulhi 2, or 0, sum 83; renormalised to 75 by largest remainder as 14, 13, 4, 11, 3, 10, 9, 2, 9, 0 in the generator's order) through the acceptance at the shipped parameters: the attempts census with the refused-ratio column at widths 4 and 1 (1,500 eras each, build-3, the fg8 harness), the index-bit read, and attack-f8 at 2^20 on 64 seeds; running from 15:5x BST, the verdict to the coordinator, the hash, census and research lanes with its minute. +8. Not in this report: the mixer ladder re-run at m = 4 and 16 (adv-mixer-3's harness rows; the per-family rows of section 4), the F8 census at D = 29 (the stand-in gap row), the 10^5-program verifier census at the top corner (F6 per family): each a named per-family row with its hours in section 4.1. ## 8. Sources