nx_uxf_tsv_persist_gate.nx

nx_uxf_tsv_persist_gate.nx -- the D001 MIGRATION of nx_uxf_tsv_persist onto nx_gate_verdict (2026-09-06). THE FULL DATA PIPELINE ON REAL DATA: a real registry TSV becomes per-row canonical content-addressed records, is PERSISTED into the immutable segment store with an fsync, REOPENED FRESH FROM DISK, and every row is retrieved by its content-address through a binary search of the NXK1 index and compared BYTE FOR BYTE against the original. This is what makes the replace-the-TSVs claim a measurement rather than a plan. ALL FOUR ORIGINAL TEETH PRESERVED IN ORDER AND PREDICATE, plus one strengthening: the original asserted only that SOME rows were persisted, so a parser that produced a single row would have passed T1. The row count is now asserted against the known population of the fixture file, which is what makes T2 and T3 non-vacuous -- hits equal to nrows is trivially true when nrows is one. FIXTURE SCOPED, WHICH THE ORIGINAL DID NOT DO: it wrote /tmp/uxf_sci.docs and /tmp/uxf_sci.keys, names a production beat or a sibling gate could collide with, and the estate has measured that class -- a gate sharing its fixture reports on the FIXTURE rather than on the code. These paths carry this gate's own name. license_tier: ORIGINAL No hw writes (Rule 26).