# vendor_row24_gatepoint -- the two-precision gate-point strings of all 98 masters (row 24, the two-mass non-planar hexa-box; 2026-09-09)

Release note (2026-09-29): the three `path` values of the strings object were re-cut from absolute paths to basenames; the object's sha256 below is the served bytes after that re-cut; every string and figure in it is as emitted.

`DATA_C24g60_pair_strings_20260909T075018Z.json` (sha256 `2045567bf9c52d39...`; stamp 2026-09-09T07:50:18Z) is the served data file of the two-precision boundary at the verification point {s12: -3, s23: -5, s34: -7, s45: -11, s15: -17, mm: 2}: for every one of the 98 masters and every order eps^-4..eps^4, the goal-30 and the goal-60 Arb-ball strings verbatim from the two evaluations of record (precision goals 30 and 60; their output files named by sha256 in the `ref` / `test` blocks) and the matched digits per component (1298 digit cells; 106 components null = numerical zeros by the comparison tool's rule, not counted).  The digits are a two-precision agreement of one program; the lower member bounds them.

Read from this file's own digit fields: through eps^0 min 48.4 d, through eps^2 min 42.2 d, all orders min 32.8 d -- the integer floors of the row's Table-2 cell.  `hexabox-evaluate.py --gatepoint` recomputes every cell's digits from the two strings (the record pair's own function) and reads its floors against the PAIR v2 keys of record (object `bb0b69e312ea86f6...`), the settled receipt `8a3c9183d633a417...` naming this file by sha256 as the data leg; `--gatepoint --mutate-gatepoint` is the control.

Pins: hexabox-evaluate.py --gatepoint pins the .json file here in-code and refuses a mismatch (exit 3) or a missing file (exit 4) before any string is read

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