This release presents a sealed proof interface to audit the Yang–Mills mass gap in physics, suggesting enhanced reliability.
# YM Mass Gap — v10.9 (sealed proof-interface release) ## OverviewThis record releases **YM Mass Gap v10.9** together with a **sealed witness packet**that implements a *fail-closed, mechanically auditable* proof interface for aconditional Yang–Mills mass-gap program on an OS-window (PB⋆). **Included files**- `YM_MG_v10.9.pdf` — main paper (PDF)- `YM_MG_pkt_v10.9.zip` — sealed witness packet (ZIP) The paper proves a soundness chain of the form\[PASS(E5-min/v1.3) \;⇒\; δ_φ(t_0)>0 \;⇒\;λₘᵢₙ(-ΔM)≥ κgeoδ_φ(t_0)^2\;⇒\; m_0 ≥ cgapδ_φ(t_0)^2>0,\]with PB⋆-registered constants and strict IOA/exchange principles (see the paper for details). --- ## What is new in v10.9### 1) Harder, reviewer-facing completeness- The program is reorganized around a **single hard trigger**: a *finite, public* report that passes the **E5-min/v1.3** checked-inequality interface under mechanical audit.- A one-page **TCB/Dependency map** is surfaced so reviewers can see what is proven in-text vs what is verified by the packet. ### 2) Level-B “config → samples” binding (physics_strict-ready)This release strengthens the “non-toy” direction by supporting a **Level-B** binding:the `raw_samples.json`/`raw_summary.json` used by E5-min can be deterministically recomputedfrom (i) hash-bound SU(2) configuration files and (ii) a hash-bound per-configurationobservable sidecar:- `raw/obs/cfg_observables_qball_bc.json` (Protocol P-OBS) A stdlib-only extractor recomputes `results/raw_samples.json` from the sidecar and binds:- `configs_dir_manifest` SHA256- `domain_items` SHA256- sidecar SHA256- script digest ### 3) Protocol P-OBS is enforced (fail-closed)For the **physics_strict** track, the packet includes an **audited** check(`audit_cfg_observables.py`) that enforces Protocol P-OBS:- ordering / uniqueness rules- exact cfg SHA256 matching- placeholder tokens forbidden- finite/valid numeric recordsA P-OBS violation is a hard FAIL under `physics_strict`. --- ## Packet status in this record (important)The witness packet is *fail-closed*: the audit rejects any mismatch of hashes, schemas, orderived fields. - **`strict_simulation` profile:** The included report is intended to **PASS** under the sealed packet auditor.- **`physics_strict` profile:** This record ships a complete **import + audit pipeline** and Protocol P-OBS enforcement, but **requires a REAL external SU(2) ensemble** (non-synthetic provenance + physics sanity) to produce a PASS anchor. In other words: `physics_strict` is provided as a *ready-to-run closure interface*, and becomes PASS only after importing a REAL ensemble and re-sealing. This separation is deliberate to avoid over-claiming while making the completion criterion explicit:a single **physics_strict PASS anchor** would upgrade the record from a program interfaceto a finite public witness for the physical target instantiation. --- ## How to run (minimal)Unzip the packet and run the audit in a bytecode-clean environment. ```bashunzip YM_MG_pkt_v10.9.zipcd YM_MG_pkt_v10.9 # Strict simulation audit (expected to PASS for the included report)python3 -B scripts/audit_all.py --packet_root . \ --report results/e5_min_report.json --profile strict_simulation
No takes yet. Share an insight, caveat, or question.
Byoungwoo Lee (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: