A registered result in its source context
Original ledger classification: Formal/prose guard [E]
Recorded statement: 4D OVER-CLAIM WORDING GUARD (2026-06-18): bare 4D over-claims ('TFPT solves 4D QFT', 'SM couplings unify', '4D GUT prediction', 'unbroken E8 gauge') are absent from the active docs, and the scoped fork-policy phrases ('boundary only is…
Statement, assumptions and sources
Paper context: Research contracts
The exact identifier, original classification and full claim are available below.
The source wording and classification below are preserved as recorded. A paper link, shared script or authored topic relation does not upgrade the claim or report a new proof run. Read later reviewed findings separately.
Read the exact registered claim and its dependencies
QFT4D.NO_OVERCLAIM.01
Original ledger classification: Formal/prose guard [E]
Original claim text
4D OVER-CLAIM WORDING GUARD (2026-06-18): bare 4D over-claims ('TFPT solves 4D QFT', 'SM couplings unify', '4D GUT prediction', 'unbroken E8 gauge') are absent from the active docs, and the scoped fork-policy phrases ('boundary only is canonical', 'SM-only ... killed', 'not claimed by default') are present.
Original classification detail
[E] prose sentinel over the active .tex: forbidden bare over-claims absent (6/6) + required scoped policy phrases present (3/3).
Dependencies as recorded
QFT4D.FORK.01
Open the original ledger source, row 357Location recorded in the ledger
These document locations are recorded directly on the ledger row. They are document level navigation, rather than a newly inferred section citation.
- Research contracts
Sections that explicitly cite this claim
A literal claim identifier is present in these paper sections. The section and its premises determine what the citation supports.
- 2026-06-18 (The 4D-QFT fork frozen as a branch policy: boundary-only canonical, Pati–Salam a falsifiable UV branch, SM-only GUT killed, v265)Research changelog; TFPT — Introduction and reading guide
Navigation through a shared verification script
These sections cite a script associated with the claim. This is a source navigation join, rather than an explicit citation of the claim or a theorem equivalence.
- The closure ledger: what is done, and what genuinely remainsTFPT — Introduction and reading guide
- 2026-06-24 (Harvesting the QFT/gravity machinery: v385 the UV-branch kill-test surface, v386 the graviton-exchange amplitude, v387 the gap-driven correction calculus)Research changelog; TFPT — Introduction and reading guide
- Research Contract 1 — [formula in source]tfpt research contracts
- 2026-06-18 (4D QFT: the perturbative S-matrix as an Epstein–Glaser / pAQFT skeleton, v269)Research changelog; TFPT — Introduction and reading guide
- Front matter / supportResearch contracts
- Front matter / supportTFPT — Introduction and reading guide; Verification reference catalog
- 2026-06-18 (Branch B decided: the explicit PS threshold model [formula in source] proton-decay window — minimal content killed, [formula in source] survives, Hyper-K decisive, v266)Research changelog; TFPT — Introduction and reading guide
- Target F — the perturbative 4D-QFT [formula in source] scale round (v269–v275)Red-team audit
All 10 linked sections
Registered verification modules
- v265_qft4d_fork_freeze.pyRegistered verification module · registry
Read the description recorded in the module registry
QFT4D.FORK.01 — freeze the 4D-QFT fork as a Branch Policy (not an open ambiguity); writes qft4d_fork_freeze.json + a prose guard, no new physics. A=boundary-only is the canonical 4D reading (no 4D-GUT claim by default); SM-only 4D-GUT unification is killed (1-loop spread ~8.8 at 2e16, v246); B=carrier-native Pati-Salam is a falsifiable UV branch (E8 content {1,10,16,45} no 126 v247, sin^2 thetaW=3/8 v248, kappa O(1) band v249/v253, threshold+proton kill test). Proton safety rule: no fake tau_p window. Wording guard: bare 4D over-claims absent + scoped policy phrases present. Frozen decision tree, not an open ambiguity.
A registered module is a source reference. Its presence does not assert that the module was executed in this snapshot.