Live cross-package harness: load every VP volume in one process and verify the shared substrate, hepatic seam, analgesic map and felt-symptom endpoint against the live sibling engines (out of gate)

This section is the live cross-package harness — the last frontier item of the work order. It loads this volume together with its sibling VP volumes (circulatory, musculoskeletal, neuro) in one process and verifies, against the live sibling engines, the four cross-volume identities the §27 seam and §28 analgesic layers had taken on trust: the shared R19 substrate (every volume's spinodal and barrier byte-identical, drift 0), circulatory's live hepatic clearance reproducing the vendored snapshot (Q_H = 1500 mL/min, E = 0.75, F = 0.25), the 27-target analgesic map re-deriving through every volume's spinodal, and the neuro nociceptor the felt-symptom pointer targets. It runs outside every gate — each volume still verifies alone from its own archive with the siblings absent, the engines loaded by file path not imported — so the build stays sibling-free and the harness digest is byte-identical with or without the siblings on disk. [V] the live checks; [F] the closed-form identity and the out-of-gate firewall; no new [O].

The §27 seam layer and the §28 inherited analgesic map both rest on a cross-volume identity they could only take on trust, because the governing discipline is verify-alone: every VP volume re-establishes its entire trusted state from its own archive with the siblings absent, so neither layer may import a sibling. The seam vendored circulatory's hepatic snapshot (verified once at vendoring time); the analgesic map asserted that its firing-threshold scale is exactly this volume's §18 afferent spinodal. This section supplies the standing live proof — a harness that loads every VP volume into one process and checks those identities against the live sibling engines. Four identities are confirmed. (1) The shared R19 substrate: sweeping γ across the inherited analgesic-target gammas, every present volume's firing-threshold spinodal |h_sp| = 2(g/3)^1.5 and barrier g²/4 are byte-identical (cross-volume drift 0) — the foundation that lets a primitive derived in one volume be read in another without a refit. (2) The circulatory hepatic seam: circulatory's live hepatic_clearance() reproduces the snapshot this volume vendored (Q_H = 1500 mL/min, extraction E = 0.75, bioavailability F = 0.25, clearance CL_H = 1125 mL/min), so the §24 NAFLD/MASLD lipid delivery and §25 bile cholesterol delivery rest on a verified value. (3) The analgesic 27-target map: the inherited firing-threshold map re-derives bit-for-bit through every volume's own spinodal, so 'inherited once, read many times, drift 0' is a live cross-volume fact rather than a per-package claim, and the built second host (musculoskeletal, which already carries the analgesic layer) reads its own levers on the same spinodal. (4) The neuro felt-symptom endpoint: the peripheral nociceptor the §18→mind one-way pointer targets exists in neuro on the shared substrate — a high-threshold polymodal cell (master PRDM12, Na_V1.7 / SCN9A, the same channel the §28 L1 lever blocks) that fires only to noxious drive — so the firewall pointer lands on a real, shared-substrate reading rather than a dangling reference. The harness runs outside every gate: the research gate (repro/run_all.py) and this canonical build compute nothing here and never import a sibling, so the pages were produced with the siblings absent (verify-alone intact); the sibling engines are loaded by file path under unique module names (the package-internal module table cleared between loads, so two volumes' identically-named vp_substrate cannot collide) — loading, not importing — and the harness's own source carries zero sibling import statements (self-checked). The harness digest hashes only the in-package digestive-side contract (the closed-form substrate values, the vendored snapshot, the drift-0 reverify, the neuro-endpoint descriptor), all computed from this archive alone, so it is byte-identical whether or not the siblings are on disk, and the engine, disease, C6, seam and analgesic digests are all unchanged. The live cross-volume readings are [V]; the closed-form substrate identity and the out-of-gate firewall (file-path load only, the build sibling-free, verify-alone preserved) are forced [F]; and because this is a verification layer that introduces no new primitive and makes no new claim there is no new [O] of its own — the only thing it cannot do offline is the live run itself, which needs the sibling archives present, which is exactly why the build and the gate stay sibling-free and the live check is a separate runner.

The §27 seam layer and the §28 inherited analgesic map both rest on a cross-volume identity they could only take on trust, because the governing discipline is verify-alone: every VP volume re-establishes its entire trusted state from its OWN archive with the siblings absent, so neither layer is allowed to import a sibling. The seam vendored circulatory’s hepatic snapshot (verified once, at vendoring time); the analgesic map asserted that its firing-threshold scale is exactly this volume’s §18 afferent spinodal. This section supplies the standing LIVE proof: a harness that loads every VP volume into one process and checks those identities against the live sibling engines — the last frontier item of the §8 work order.

The harness runs outside every gate. The research gate (repro/run_all.py) and this canonical build compute nothing here and never import a sibling — the pages you are reading were produced with the siblings absent, the verify-alone guarantee intact. The sibling engines are loaded by file path under unique module names (with the package-internal module table cleared between loads, so two volumes’ identically-named vp_substrate cannot collide); that is loading, not importing, and the harness’s own source carries 0 sibling import statements (self-checked, file-path-load discipline ok = True). Because the harness digest hashes only the in-package digestive-side contract — the closed-form substrate values, the vendored snapshot, the drift-0 reverify and the neuro-endpoint descriptor, all computed from this archive alone — it is byte-identical whether or not the siblings are on disk (2×sha256 = 21509b67aaa6…), exactly what a deterministic, sibling-free build requires. The engine, disease, C6, seam and analgesic digests are all unchanged; this layer carries only its own.

With the sibling packages present, repro/run_harness.py loads all four volumes in one process and confirms the four identities the seam and analgesic layers depend on:

The foundation of all four is the shared R19 substrate: a primitive derived in one volume can be READ in another only because the double-well closed forms are the same function everywhere. The live check sweeps γ across the map and finds the sibling spinodals match this volume’s bit-for-bit (drift 0); the closed-form values they must match — |h_sp| = (2/3√3)γ^1.5 and barrier = γ²/4, evaluated at a span of the inherited analgesic-target gammas — are:

The live cross-volume readings — substrate drift 0 across the volumes, circulatory’s live clearance reproducing the vendored snapshot, the 27-target map re-deriving through every spinodal, and the neuro nociceptor firing only to noxious drive on the shared substrate — are [V]; the closed-form substrate identity and the out-of-gate firewall (file-path load only, the build sibling-free, verify-alone preserved) are forced [F]. This is a verification layer: it introduces no new primitive and makes no new claim — it confirms, live, what the earlier layers asserted, so there is no new [O] of its own. The single thing it cannot do offline is the live run itself (which needs the sibling archives present); that is precisely why the build and the gate stay sibling-free and the live check is a separate runner. The felt pain remains mind’s (only the peripheral nociceptor term crosses, the §27 firewall kept), and every clinical magnitude remains [O] as inherited.