# vendor_row24_eps12 -- the objects of the eps^1, eps^2 gate of record (row 24, the two-mass non-planar hexa-box; 2026-09-07)

The served `hexabox-vop-data.json.gz` (sha256 `f9e64518cb2e9ef3...`; until the (97,0,2..4) succession of 2026-09-11 `04bfd5f45c625ae8...`, kept under `superseded_04bfd5f45c625ae8/`) is the SUCCEEDED bundle of the sec255 layer recursion: the full exact A (8151 entries; the 5018 served before byte-equal), the 28 candidate kernels entered from the eleven files below, the three (97,0,2..4) layers entered exact on 2026-09-11 from the same (97,0) object (its layers 2, 3, 4; vendored under `vendor_row24_kernels/`), and the 196 fit-point seed cells at orders [3, 4] for all 98 rows (the 506 served cells kept).  `hexabox-evaluate.py --kmax 5` runs the recursion to eps^2 of the top sector on it and gates eps^1, eps^2 against the served 60-digit strings and the two records here (the module docstring, EPS^1, EPS^2 SUCCESSION); every file in this directory is sha256-pinned in that script (missing -> exit 4, mismatch -> exit 3).

## The gate of record

- `GATE_EPS12.json` (sha256 `607db54afff0e76a...`; stamp 2026-09-07T05:27:52Z): the layer recursion on the gated bytes `c4d86690801bcef6...` (this bundle before its provenance strings were re-cut) at KMAX 5, NC 220, engine dps 85 / 115, read at the verification point against both records: eps^1 40.21 d, eps^2 35.29 d, eps^-4..eps^0 control 44.59 d (complex-relative, the verdict rule; real-part convention eps^1 39.2 d, eps^2 34.97 d); the two-precision pair eps^1 74.26 d, eps^2 71.34 d; the goal-60 record and the served strings agree with the recursion to 57.05 d and more; planted digit-20 control 21.31 d FAIL.  Rule: GATED iff min over masters and over {vs goal-60 string, vs goal-30 value, vs goal-60 out, two-precision pair} >= 30 d at BOTH eps^1 and eps^2.  Walls {'dps85': 501.7, 'dps115': 594.0} s.
- The goal-30 record is the floor of the minimum at eps^1, eps^2 (its own precision there); the eps^-4..eps^0 orders agree with the goal-30 record to 44.59 d and with the goal-60 record to 56.54 d.

## The two records (AMFlow, the verification point, precision goals 30 and 60)

- `ORACLE_goal30.json` (sha256 `92b3be0b6044a8e9...`) and `ORACLE_goal60.json` (sha256 `c980694afed36786...`): the three top-sector masters through eps^2 at the point {'s12': '-3', 's23': '-5', 's34': '-7', 's45': '-11', 's15': '-17', 'mm': '2'} = the served verification point (both files are the record bytes; the point check is the gate's own); the goal-60 record is the source of the served deep-60 strings in `hexabox-data.json` sec255 (identical to >= 40 d on 21 of 21 strings, the gate's INFO line).  Their eps^1, eps^2 values were never used in any fit.

## The eleven candidate kernel files (exact rationals; candidates reproducing both records, not proofs)

- `KERNELS_CANDIDATE_v2_item56_86_70_20260907T050708Z.json` (sha256 `8557dca8be0d111f...`): coupling (86,70), layers [8, 9] in the file; entered into the bundle: m 8 (deg P,Q 29,32), m 9 (deg P,Q 35,38); record layers reproduced as exact identities: 5 of 5.
- `KERNELS_CANDIDATE_v2_item56_87_70_20260907T050708Z.json` (sha256 `ab598f5548aeec02...`): coupling (87,70), layers [8, 9] in the file; entered into the bundle: m 8 (deg P,Q 31,32), m 9 (deg P,Q 37,38); record layers reproduced as exact identities: 5 of 5.
- `KERNELS_CANDIDATE_v2_item56_88_70_20260907T050708Z.json` (sha256 `8334f28d2a322aa6...`): coupling (88,70), layers [8, 9] in the file; entered into the bundle: m 8 (deg P,Q 41,41), m 9 (deg P,Q 47,47); record layers reproduced as exact identities: 5 of 5.
- `KERNELS_CANDIDATE_v2_item56_89_70_20260907T050709Z.json` (sha256 `574b83c2b5bd3da2...`): coupling (89,70), layers [8, 9] in the file; entered into the bundle: m 8 (deg P,Q 31,33), m 9 (deg P,Q 37,39); record layers reproduced as exact identities: 5 of 5.
- `KERNELS_CANDIDATE_v2_item56_90_70_20260907T050709Z.json` (sha256 `da419b51885bb069...`): coupling (90,70), layers [8, 9] in the file; entered into the bundle: m 8 (deg P,Q 32,33), m 9 (deg P,Q 38,39); record layers reproduced as exact identities: 5 of 5.
- `KERNELS_CANDIDATE_v2_item56_91_70_20260907T050709Z.json` (sha256 `4e1ac068ebd3c43a...`): coupling (91,70), layers [8, 9] in the file; entered into the bundle: m 8 (deg P,Q 43,43), m 9 (deg P,Q 49,49); record layers reproduced as exact identities: 5 of 5.
- `KERNELS_CANDIDATE_v2_item56_95_70_20260907T044009Z.json` (sha256 `bbb18253ce1df847...`): coupling (95,70), layers [8, 9] in the file; entered into the bundle: m 8 (deg P,Q 89,92), m 9 (deg P,Q 103,106); record layers reproduced as exact identities: 5 of 5.
- `KERNELS_CANDIDATE_v2_item56_96_70_20260907T044009Z.json` (sha256 `675a49ffd2885b2b...`): coupling (96,70), layers [8, 9] in the file; entered into the bundle: m 8 (deg P,Q 90,92), m 9 (deg P,Q 104,106); record layers reproduced as exact identities: 5 of 5.
- `KERNELS_CANDIDATE_v2_item56_97_0_20260907T043901Z.json` (sha256 `13f543565bf26ce4...`): coupling (97,0), layers [2, 3, 4, 5, 6, 7, 8, 9] in the file; entered into the bundle: m 5 (deg P,Q 207,209), m 6 (deg P,Q 236,238), m 7 (deg P,Q 265,267), m 8 (deg P,Q 294,296), m 9 (deg P,Q 323,325); record layers reproduced as exact identities: 2 of 2.
- `KERNELS_CANDIDATE_v2_item56_97_2_20260907T043900Z.json` (sha256 `0544894bfdc1de7e...`): coupling (97,2), layers [5, 6, 7, 8, 9] in the file; entered into the bundle: m 5 (deg P,Q 174,176), m 6 (deg P,Q 199,201), m 7 (deg P,Q 224,226), m 8 (deg P,Q 249,251), m 9 (deg P,Q 274,276); record layers reproduced as exact identities: 5 of 5.
- `KERNELS_CANDIDATE_v2_item56_97_70_20260907T044008Z.json` (sha256 `b1fa1929c6a382b5...`): coupling (97,70), layers [8, 9] in the file; entered into the bundle: m 8 (deg P,Q 99,100), m 9 (deg P,Q 113,114); record layers reproduced as exact identities: 5 of 5.

## The audit and the build receipt

- `SUPPORT_AUDIT.json` (sha256 `256ea5ba8bc4e5c4...`; stamp 2026-09-07T05:19:44Z): the couplings of rows 61-97 whose layer support stops below the reach at KMAX 5 on the gated bytes: 146 of 896 audited, none at the record ceiling M_EPS 7; the reading: no coupling truncated at the record ceiling M_EPS 7 below the reach at KMAX 5; the 146 other short coupling(s) stop at m <= 4 (the record's own per-entry support; whether those entries' higher layers vanish identically is NOT ESTABLISHED here); (70,70) at max m 1 against a reach of 9 is NOT a truncation: on the 101 nodes its layers m = 2, 3, 4, 5, 6, 7 vanish identically (the entry is a polynomial of degree 1 in eps over a t-only denominator: D' has no d-dependence, deg D_a 1); the recursion's rule consumes every layer in SUPP (L496-500) and nothing is excluded -- there is nothing beyond m = 1 to consume
- `BUILD_RECEIPT.json` (sha256 `d68d6e14d0c8094c...`; stamp 2026-09-06T14:22:37Z): the full bundle the candidate kernels were entered into -- exact entries 5018 -> 8151 from the exact reconstruction of record `cc93c54cd2067d0a...`; seed cells added 196 at orders [3, 4] from the fit-point evaluations `acfdd714dce80bf6...` (goal 60) / `ec9aab6eecc4d347...` (goal 30); the entries the exact pickle lacked ((97,0,2), (97,0,3), (97,0,4), (97,0,5), (97,0,6), (97,0,7), (97,2,5), (97,2,6), (97,2,7)) are the three kernels (97,0,2..4), then served as certified-numeric fits and entered exact on 2026-09-11, and the six m >= 5 entries now entered from the candidate files.

## Not established by these objects

- the four m >= 5 top-row kernels (97,0,5), (97,2,5), (97,0,6), (97,2,6) beyond the gate: exact candidates reproducing both records through eps^2, no analytic proof;
- the 146 non-top couplings of rows 61-97 whose record support stops at m <= 4: their higher layers vanish by the oracle reading only (the gate reproduces both records with them as they are);
- the m >= 5 layers of the bivariate lift as kernels (the paper's own fence); the 187 path samples of record (deleted; D_spec reconstructed); the per-node wall at scale (one pilot node).

`VENDOR_MANIFEST.sha256` lists every file of this directory; the bundle's `MANIFEST.sha256` pins this directory's files too.