# 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**- `YMMGᵥ10. 9. pdf` — main paper (PDF) - `YMMGₚktᵥ10. 9. zip` — sealed witness packet (ZIP) The paper proves a soundness chain of the form (E5-min/v1. 3) \;\; _ (t₀) >0 \;\;_ (- ₌) ₆₄₎_ (t₀) ²\;\; m₀ c₆₀_ (t₀) ²>0, 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ₛtrict-ready) This release strengthens the “non-toy” direction by supporting a **Level-B** binding: the `rawₛamples. json`/`rawₛummary. 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ₒbservablesqballbc. json` (Protocol P-OBS) A stdlib-only extractor recomputes `results/rawₛamples. json` from the sidecar and binds: - `configsdirₘanifest` SHA256- `domainᵢtems` SHA256- sidecar SHA256- script digest ### 3) Protocol P-OBS is enforced (fail-closed) For the **physicsₛtrict** track, the packet includes an **audited** check (`auditcfgₒbservables. 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ₛtrict`. --- ## Packet status in this record (important) The witness packet is *fail-closed*: the audit rejects any mismatch of hashes, schemas, orderived fields. - **`strictₛimulation` profile: ** The included report is intended to **PASS** under the sealed packet auditor. - **`physicsₛtrict` 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ₛtrict` 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ₛtrict 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 YMMGₚktᵥ10. 9. zipcd YMMGₚktᵥ10. 9 # Strict simulation audit (expected to PASS for the included report) python3 -B scripts/auditₐll. py --packetᵣoot. \ --report results/e5ₘinᵣeport. json --profile strictₛimulation
Byoungwoo Lee (Tue,) studied this question.