SAPZ Navier–Stokes Support Notes v1.0: Entry Note, Bridge Notes, Dependency Map, and Object Ledger

**Title:** SAPZ Navier--Stokes Support Notes v1.0 **Record role:** analyst-facing bridge/support documents for the journal-cut SAPZ Navier--Stokes package **Current snapshot DOI:** 10.5281/zenodo.18890269 **Date:** March 2026 # OverviewThis record releases **v1.0** of an analyst-facing **support-note set** for the SAPZ Navier--Stokes journal-cut package. These documents are **not** the primary proof package.They are intended instead to help analysts and referees approach the main package in a modular way by making explicit: - the package architecture,- the main dependency chain,- the principal nonstandard core modules,- the reusable fixed-scale bridge mechanisms,- and the main object dictionary needed to avoid notation-level confusion. The corresponding **primary proof package** is a separate Zenodo record containing:- the main paper,- the companion proof modules,- and the minimal formal verification note. This support record adds **no new proof inputs** to that primary package.Its role is explanatory, bridge-building, and analyst-facing. --- ## Relation to the primary packageThis record should be read as a **support layer** for the SAPZ Navier--Stokes journal-cut proof package, not as an alternative proof record. In the primary package, the intended structure is:\[\text{CRIT} + \text{DISCHARGE} + \text{CONTINUE}.\] More concretely: - **CRIT (main paper):** finite-horizon threshold criterion and threshold-reach necessity statement;- **DISCHARGE (companion):** finite-horizon discharge, including the principal nonstandard modules;- **CONTINUE (endpoint closure):** the final handoff to standard Caffarelli--Kohn--Nirenberg \(\varepsilon\)-regularity / continuation;- **Minimal Verification Note:** a referee-facing reduction of the independent verification burden to a small trusted core. The present support record serves a different purpose:it makes that architecture easier to read, isolates reusable local PDE bridges, and reduces the risk of architecture-level or object-level misreading. --- ## Files in this recordThis support set contains five documents. ### 1. Analyst's Entry Note v1.0A short analyst-facing reading guide to the SAPZ Navier--Stokes package. Its purpose is to explain how the journal-cut set should be read as\[\text{CRIT} + \text{DISCHARGE} + \text{CONTINUE},\]to identify the genuinely nonstandard core,and to recommend an efficient reading order for first serious inspection. ### 2. Route--T Bridge Note v1.0A fixed-scale local PDE bridge note isolating the localized commutator transport-extraction mechanism for suitable weak solutions. Its emphasis is on:- fixed-scale approximation,- strong--strong product passage,- fixed-scale commutator-factor convergence,- and localized transport extraction. ### 3. CT3 Persistence Note v1.0A fixed-scale short-window persistence note isolating the local contradiction-window persistence mechanism under a one-sided residual budget. Its emphasis is on:- residual-budget selection,- common-sequence / diagonal scale choice,- and fixed-scale short-window persistence. ### 4. One-Page Dependency Proof-Map v1.0A compact dependency sheet showing how the journal-cut package decomposes into\[\text{CRIT} + \text{DISCHARGE} + \text{CONTINUE},\]and identifying the small trusted nonstandard core. ### 5. One-Page Object Ledger v1.0A compact object dictionary designed to prevent the main reading hazard of the package:conflating distinct residual, defect, envelope, and bookkeeping objects that live at different analytic levels. --- ## Why this support set existsThe SAPZ Navier--Stokes journal-cut package is modular, but its genuinely nonstandard burden is concentrated in a small number of analytic cores.Without an explicit reading guide, a first-time reader can easily spend too much effort on secondary bookkeeping or lose track of where the actual verification burden lies. This support set exists to make the following points transparent. ### 1. The package is modularThe journal-cut package is not intended to be read as a single black-box theorem.It is organized as\[\text{criterion} + \text{finite-horizon discharge} + \text{standard endpoint closure}.\] ### 2. The genuinely nonstandard burden is intentionally compressedFor a first serious audit, the independent verification burden is compressed to a small trusted core.At the level of the present support set, the main core modules are: - Gate A,- short-window fixed-scale persistence,- fixed-scale Route--T transport extraction. ### 3. Standard endpoint closure is kept separateOnce the nonstandard core modules are accepted, the remaining endpoint continuation step is intended to proceed through standard Caffarelli--Kohn--Nirenberg \(\varepsilon\)-regularity / continuation machinery. ### 4. Object confusion is the main reading hazardA major risk in reading the package is to conflate:- envelope-side quantities,- localized transport residuals,- defect functionals,- and named non-bulk budgets. The proof-map and object ledger are included specifically to reduce this risk. --- ## Scope and disciplineThese five documents are **support notes**, not replacements for the primary proof package. They do **not**:- introduce new proof inputs beyond the main journal-cut package,- replace the primary main paper, companion, or verification note,- add numerical evidence as a proof ingredient,- claim global regularity independently of the primary package,- or eliminate the need for line-by-line verification of the core lemmas in the companion. They are intended to:- clarify the package architecture,- isolate reusable local PDE bridge mechanisms,- and make the proof burden more legible to analysts and referees. --- ## What is isolated hereThis support set isolates two reusable bridge mechanisms in particular. ### A. Fixed-scale commutator transport extractionThe Route--T bridge note reformulates the transport-extraction core as a standalone fixed-scale local PDE lemma chain, without taking a small-scale limit in the theorem statement. ### B. Fixed-scale short-window persistenceThe CT3 persistence note reformulates the contradiction-window mechanism as a local fixed-scale persistence statement under a one-sided residual budget, with explicit common-sequence / diagonal scale selection. Together with the entry note, proof-map, and object ledger, these documents are intended to make the primary proof package more accessible to independent analysts. --- ## Relation to later standalone recordsThis support record is an analyst-facing **support / bridge layer**.Some of its themes were later separated further into standalone records with narrower theorem-level roles, including: - standalone Route--T bridge records,- standalone CT3 persistence records,- standalone Gate A endpoint-bridge records,- and a short closure / implication note for the finite-horizon criterion chain. Those later records do not change the role of the present support set.The purpose of this record remains:to provide entry points, bridge explanations, dependency summaries, and object-discipline guidance for readers approaching the main package. --- ## Intended useThis record is primarily intended for: - analysts who want an efficient entry point into the SAPZ Navier--Stokes package,- referees who want to identify the genuine nonstandard core before reading the full companion,- and readers interested in whether the main package contains independently reusable local PDE bridge mechanisms. The support notes are best read alongside the separate journal-cut proof-package record. --- ## Mathematical positioningThis record should be read as an **analyst-facing support layer** for a modular proof package. Its intended mathematical role is:- to explain the package architecture,- to isolate local bridge mechanisms that are useful for reading the full companion,- to identify the genuinely nonstandard verification burden,- and to reduce ambiguity in the object dictionary. It should **not** be read as an independent proof record for the full Navier--Stokes regularity problem. --- ## Proof disciplineThe support notes are intentionally explanatory. They are meant to:- reorganize,- isolate,- and clarify selected parts of the existing proof architecture. They add **no new proof inputs** to the primary journal-cut package. --- ## Recommended citationLee Byoungwoo, **SAPZ Navier--Stokes Support Notes v1.0** (Analyst's Entry Note, Route--T Bridge Note, CT3 Persistence Note, One-Page Dependency Proof-Map, and One-Page Object Ledger), Zenodo, March 2026. Current snapshot DOI: 10.5281/zenodo.18890269 --- ## Record-navigation noteThis record is a **support / bridge record**, not the primary proof-package record. It is intended to be cited when referring specifically to:- the analyst-facing entry guide,- the Route--T bridge note,- the CT3 persistence note,- the dependency proof-map,- or the standalone object ledger. For the primary journal-cut SAPZ Navier--Stokes proof package, see the separate Zenodo record containing:- the main paper,- the companion proof modules,- and the minimal formal verification note.