# Republish AP30 — The Resistance — FINAL v1.0 · dated notes 7 September 2026

The body of this docx is byte-identical to the published FINAL (verified paragraph
by paragraph). Five dated notes are appended at the end of §8 — Connections.
Metadata is neutral (Studio G).

## Steps

1. Open `AP30_The_Resistance_FINAL_v1_0_dated_notes_2026-09-07.docx` in Word.
2. Contents page: the three typed page numbers for
   - "What This Establishes and What Remains Open"
   - "Claim Summary"
   - "Conditionality Footer"
   each move by one page because the notes add a page. Check the numbers Word
   shows and type those. Dress only — nothing in the body changes.
3. Export to PDF. Replace the AP30 PDF on the420code.org.
4. Site listing line, exactly:
   **AP30 · The Resistance · FINAL v1.0 · dated notes 7 September 2026**
5. Zenodo / OSF: publish as a NEW VERSION of the AP30 record. The previous
   version stays beside it, never replaced. (Claude Code maintains these; the
   instruction is in 3_paste_to_claude_code.)
6. The OneDrive `AP30_The_Resistance_FINAL.docx` (73 KB, "zero fitted
   parameters") is NOT the published text. Do not publish from it. It is marked
   superseded in the Museum's source index by this file.

## The five notes, for the record

1. KS-NPP.1 fired 2 August 2026 at 7.24σ — no repair; AP47 KS-FLIP.1 beside.
2. KS-30.3 paid 6 September 2026 by AP49 §4 and §7; the closed form supersedes
   §6's truncation by reference, beside it.
3. §6's "CODATA 2022" label is the 2018 adjustment; CODATA 2022 = 1836.152673426(32);
   the O(α) result stands at 5.30 ppb; the truncated value sits 0.57σ above.
4. KS-NPP.3 retired as subsumed (ruling of 7 September 2026, for the registry's
   next build) — it names the fired value, and lattice QCD cannot test a ppm
   candidate at 0.3–0.7 MeV precision.
5. §8 attributes 21 to AP10; AP10 carries no channel count; the 21 is AP28's,
   as §0.2 states.

Rule locked 7 September 2026: a locked body is never edited, replaced or removed —
corrections go beside it by dated note. A lemma that must be rewritten becomes
v2.0 with v1.0 kept beside it.

## The two published files, both kept

*Beside, never replaced* applies to the rendered PDF as well as the text.

| | file | sha256 | pages |
|---|---|---|---|
| **published to 6 Sep 2026** | `proofs/instruments/AP30/AP30_The_Resistance_FINAL_v1_0_published_to_2026-09-06.pdf` | `acb4621c1d3e6258de70897980427fc7f367dde3f57f38b1a1f35f926e3239ce` | 26 |
| **published from 7 Sep 2026** | `/AP30_The_Resistance.pdf` | `3b86e7819d850ce6ec815e8a1e902a547635f91fd36e12a84430b4ad39eb0e96` | 27 |

The previous file is not superseded in the sense of being wrong — it is the
paper without its dated notes, and it is the file two frozen records point at.
**The AP49 freeze bundle of 6 September 2026 cites `acb4621c…` for
`inputs/AP30_The_Resistance.pdf`**, in `freezes/2026-09-06-AP49/SHA256SUMS.txt`
and in `proofs/instruments/AP49/SHA256SUMS.txt`. Those are frozen files and are
not edited. The digest they cite resolves to the preserved file above, which is
why it is kept at a stable path rather than only in git history.

Nothing else in the corpus cites the AP30 PDF by digest — checked across every
`.md`, `.txt` and `.html` in the repository on 7 September 2026.