# vendor_row24_kernels -- the exact kernel objects of couplings (97,0) and (97,2) and the eps^1, eps^2 gate of record (row 24, the two-mass non-planar hexa-box; 2026-09-09)

The served bundle `hexabox-vop-data.json.gz` carries the three kernels (97,0,m), m = 2, 3, 4, EXACT in `exactA` since the succession of 2026-09-11; the bundle served before it (kept under `superseded_04bfd5f45c625ae8/`) carried them as certified-numeric rational fits under `hybrid_kernels`.  This directory holds those exact forms and documents their origin -- the factored read of 2026-09-07: CRT + rational reconstruction on 101 path nodes, 8 withheld nodes reproduced -- with the objects they came from; every tier of `hexabox-evaluate.py` runs the exact kernels, and `--boundary-regenerate` asserts the bundle's three layers equal this directory's object before it runs the sec255 recursion on the from-definition seeds (the module docstring, BOUNDARY REGENERATE).

- `KERNELS_CANDIDATE_item56_97_0_20260907T041028Z.json` (sha256 `adbae0c89d3db900...`; re-cut by field, cure 3: 1 narrative field(s) withheld, 2 path field(s) re-cut to basename + sha256, 1 numerical-term field(s) kept as written, every numeric leaf and key name as emitted; the object as emitted sha256 `d223992d5ee27c02...`; stamp 2026-09-07T04:10:28Z): the exact layers m = 2, 3, 4, 5, 6, 7 of coupling (97,0) from the factored read of the eps^1, eps^2 succession (exact by CRT + rational reconstruction on 101 path nodes, 8 withheld nodes reproduced; 14 primes, 854 CRT bits; full identity on 101 of 101 nodes); layer degrees (P,Q) m 2: (120,122), m 3: (149,151), m 4: (178,180), m 5: (207,209), m 6: (236,238), m 7: (265,267); Q monic; P/Q coefficient strings low to high in t.  Its layers 2, 3, 4 are the three kernels the served bundle carries in `exactA` (served as fits before 2026-09-11); its layers 2..7 are byte-equal to layers 2..7 of the served candidate file `vendor_row24_eps12/KERNELS_CANDIDATE_v2_item56_97_0_20260907T043901Z.json` (which enters m = 5..9 into the bundle) -- the evaluator asserts the equality of layers 2, 3, 4 at every regenerate run.
- `KERNELS_CANDIDATE_item56_97_2_20260907T040525Z.json` (sha256 `752b050c0877963e...`; re-cut by field, cure 3: 1 narrative field(s) withheld, 2 path field(s) re-cut to basename + sha256, 1 numerical-term field(s) kept as written, every numeric leaf and key name as emitted; the object as emitted sha256 `5679228f87735129...`; stamp 2026-09-07T04:05:25Z): the exact layers m = 5, 6, 7 of coupling (97,2) from the same read (13 primes, 793 CRT bits; full identity on 101 of 101 nodes); layer degrees (P,Q) m 5: (174,176), m 6: (199,201), m 7: (224,226); byte-equal to layers 5, 6, 7 of `vendor_row24_eps12/KERNELS_CANDIDATE_v2_item56_97_2_20260907T043900Z.json`.  Vendored as the exact object of record beside its sibling; the regenerate tier reads (97,0) only (the bundle already carries (97,2) m = 5..9 exact).
- `GATE_ITEM56_EPS12_20260907T052752Z.json` (sha256 `1ef0b8a96ddebacb...`; re-cut by field, cure 3: 1 narrative field(s) withheld, 3 path field(s) re-cut to basename + sha256, every numeric leaf and key name as emitted; the object as emitted sha256 `65d5566cb74da059...`; stamp 2026-09-07T05:27:52Z): the eps^1, eps^2 gate of record in its v4 form -- GATED, eps^1 40.21 d, eps^2 35.29 d, control 44.59 d (complex-relative; bar 30.0 d); the served `vendor_row24_eps12/GATE_EPS12.json` is the same object as emitted with four path strings re-cut in its own form (every numeric leaf equal).  Both name the three kernels (97,0,2..4) absent from the exact bundle of the gate (`kernels_absent`): the gate ran the fits.

The three objects are vendored with their string VALUES re-cut by field (2026-09-09, cure 3; the served-files rule: a narrative string value -> "withheld", a path value -> its basename with the sha256 of the file it named, or "(directory)"; every numeric leaf, every layer string, every key name as emitted; the certification-rule sentence of the two kernel objects is kept as written, a numerical term); the objects as emitted are named by sha256 here and in the evaluator's REGEN['vendored_from'] block:

- vendored_from: `GATE_ITEM56_EPS12_20260907T052752Z.json` <- sha256 `65d5566cb74da059cf152a7eff372f0bdddb1b51ceed7d5cb32eef708185797a` (cure 3: 1 narrative field(s) withheld, 3 path field(s) re-cut to basename + sha256; now sha256 `1ef0b8a96ddebacbada56b4f1801cbf7e3b4dc99fa3f1d2758d5939869d5d804`)
- vendored_from: `KERNELS_CANDIDATE_item56_97_0_20260907T041028Z.json` <- sha256 `d223992d5ee27c0270d8ba7ac9c3bc690aa4e702223ff5ad478af56db562d2c4` (cure 3: 1 narrative field(s) withheld, 2 path field(s) re-cut to basename + sha256, 1 numerical-term field(s) kept as written; now sha256 `adbae0c89d3db90024dde6740e5d99d18b9dbea93e9d5fdf8f084fab91e8ea4d`)
- vendored_from: `KERNELS_CANDIDATE_item56_97_2_20260907T040525Z.json` <- sha256 `5679228f877351295f11bc217046528a46fa9fce54239278585842fb3e6e03cd` (cure 3: 1 narrative field(s) withheld, 2 path field(s) re-cut to basename + sha256, 1 numerical-term field(s) kept as written; now sha256 `752b050c0877963eb6aa8be081933a1de39a01e4b9a4840e7af03d7e1f6bf980`)

Not established by these objects: the exact kernels beyond the 101-node reconstruction (candidates reproducing both oracle records, no proof); the numeric fits of the earlier bundles are kept under `superseded_04bfd5f45c625ae8/`.

Pins: hexabox-evaluate.py --boundary-regenerate pins every .json file here in-code and refuses a mismatch (exit 3) or a missing file (exit 4) before any check runs

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