HLV-R-MECH-001: Deterministic One-Click Engine for Triangle-Matched Rewire Mechanism Testing — Corrected Implementation Freeze v0.1.2

Abstract

This record contains Corrected Implementation Freeze v0.1.2 for HLV-R-MECH-001. The controlling scientific protocol remains: Krūger, M. (2026). HLV-R-MECH-001: Prospective Triangle-Matched Mechanism Test of the Surviving Degree-Preserving Rewire Spectral Residual — Pre-Execution Protocol Freeze v0.1.0. Zenodo. DOI: 10.5281/zenodo.22166283 The public corrected predecessor implementation is: Krūger, M. (2026). HLV-R-MECH-001: Deterministic One-Click Engine for Triangle-Matched Rewire Mechanism Testing — Corrected Implementation Freeze v0.1.1 [Computer software]. Zenodo. DOI: 10.5281/zenodo.22170138 Version v0.1.2 corrects only the numerical-runtime bootstrap of the One-Click Colab launcher. The scientific engine itself is unchanged and remains byte-identical to the engine used in the earlier implementation freezes. Frozen scientific engine SHA-256: 317df650991120f686768ffc07d12f044f58e38ce8f2c47c083901bf1d7a8a14 The need for v0.1.2 arose after the v0.1.1 launcher correctly detected that the assigned Colab host environment did not match the frozen numerical environment but then failed during creation of an isolated Python virtual environment. The v0.1.1 execution stopped before the scientific engine began. Therefore no confirmatory HLV-R-MECH-001 spectrum was evaluated, no target QSPEC or RRESP score was computed, and no scientific mechanism verdict was exposed. The exact lower-level cause of the managed Colab virtual-environment failure is not asserted beyond the observed failure at the venv-creation stage. Version v0.1.2 removes dependence on Python venv. The corrected runtime bootstrap now operates as follows: 1. reconstruct and SHA-256 verify the byte-identical frozen scientific engine; 2. inspect the assigned host NumPy and SciPy versions; 3. if the host environment already provides the exact frozen versions, use that environment directly; 4. otherwise install exact binary packages NumPy 2.3.5 and SciPy 1.17.0 into a private target directory using pip --target; 5. launch a fresh Python subprocess with the private target directory placed first on PYTHONPATH; 6. verify that the subprocess reports exactly NumPy 2.3.5 and SciPy 1.17.0; 7. verify that both NumPy and SciPy are physically imported from the private target directory; 8. only after those checks execute the unchanged frozen HLV-R-MECH-001 scientific engine. This correction is restricted entirely to the external runtime-bootstrap layer. No scientific element of HLV-R-MECH-001 is changed. In particular, v0.1.2 does not modify: - the DG-001 target identity; - the target graph; - the R_DEG family; - the R_TRI family; - the confirmatory seed streams; - candidate ordering; - accepted-swap counts; - proposal caps; - structural admission criteria; - exact degree-sequence preservation; - exact triangle-count preservation T = 6960 in R_TRI; - the 40–45% edge-replacement-depth requirement; - the 31-control family size; - the between-family rewiring-depth gate; - QSPEC; - RRESP; - spectral-band definitions; - leave-one-out scoring; - the robust-margin threshold; - numerical scientific hard gates; - or scientific verdict logic. The prospective mechanism design therefore remains exactly the design specified by DOI 10.5281/zenodo.22166283. The two confirmatory control families remain: R_DEG: fresh degree-preserving structural rewires of the fixed DG-001 target graph. R_TRI: fresh rewires preserving both the exact labelled target degree sequence and the exact global target triangle count T = 6960. Each family requires 31 accepted controls. The scientific structural firewall is also unchanged. The complete R_DEG and R_TRI control banks must be generated, structurally validated, written to disk, and hash-fixed before any confirmatory spectral evaluation may begin. No control may be admitted or rejected using eigenvalues, QSPEC, RRESP, target-control spectral distances, band scores, or scientific verdict information. The primary signatures remain the prospectively frozen QSPEC and RRESP observables inherited from the DS-SPEC-001R chain. The underlying mechanism motivation also remains unchanged. For a simple graph Laplacian L = D - A, Tr(L) = sum_i d_i Tr(L^2) = sum_i d_i^2 + sum_i d_i Tr(L^3) = sum_i d_i^3 + 3 sum_i d_i^2 - 6T. Thus the R_TRI controls match the target exactly in the first three raw Laplacian spectral moments through simultaneous preservation of the exact degree sequence and exact global triangle count T = 6960. This does not imply matching of the complete spectrum, lambda_max, QSPEC, RRESP, local triangle structure, four-cycle structure, or higher-order incidence organization. The v0.1.2 correction does not inspect or optimize any of those scientific outcomes. No confirmatory seed stream was used while preparing this correction. No confirmatory target spectrum was computed. No confirmatory QSPEC or RRESP score was computed. No scientific HLV-R-MECH-001 verdict was generated during correction preparation. The corrected v0.1.2 One-Click notebook SHA-256 is: c360d318d97575b56d8fb65327bfd4cb34255325fa2d5509794311d5fa5622cf The corrected implementation-freeze PDF SHA-256 is: fb826a84eee955236c8922559ceeb8e2587854b3c8d9ef5b539a3bb0695469a2 The unchanged scientific engine SHA-256 is: 317df650991120f686768ffc07d12f044f58e38ce8f2c47c083901bf1d7a8a14 The complete corrected implementation package SHA-256 is: 724837c73506bbd001082d9b9b6aec0412304fd467ed55c3705c70d59acd719b This record supersedes corrected implementation freeze v0.1.1 only with respect to the runtime-bootstrap mechanism. It does not alter or supersede the scientific protocol. HLV-R-MECH-001 remains a finite graph-mechanism test within the Helix–Light–Vortex Framework (HLV), positioned as a Cut-and-Project and Incidence-Spectral Research Programme. Neither this corrected implementation nor any later HLV-R-MECH-001 result can by itself establish unique HLV geometry, physical selection of the golden ratio, extra dimensions, spacetime, particle physics, an absolute energy scale, gravity, dark matter, dark energy, cosmology, or experimental validation. The sole purpose of this corrected implementation freeze is to make the already prospectively frozen scientific engine executable in a reproducible numerical environment despite restrictions of the externally managed Colab runtime.