Repository navigation
#941 Units 3–4: Introduction corrections R-15, X-2, Har04 - #1160
Merged
Merged
Conversation
…ary (#941 Units 3-4) Three edits to papers/Introduction.md, with .tex/.pdf regenerated from the same source by `sh ./build.sh Introduction` (pandoc 3.1.3, XeTeX 3.141592653-2.6-0.999995, TeX Live 2023/Debian; 16 pages, 0 missing glyphs). - R-15 (L93): restore the reviewed wording of f5efa7a:172, "Doukas states the contraction argument concurrently, as a no-revival obstruction to Markovian realizers [Dou26, Prop. 1]" (owner ruling item 4, #941 c.6677500012). - X-2 (L163): add "for a uniformly distributed message" to the zero-advantage floor, the scope of BH-01 REPORT.md C2 (:42-44, :92, :297) (ruling item 9). - Har04 (L133): "[Mon08; Har04]" -> "[Mon08, citing Har04]"; Har04 is closed-access and was not read first-hand, Montina's report was (arXiv:0711.4770v2 pp. 2, 9) (ruling item 8). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011zDyUSyEszk3JJx83uXKKq
This was referenced Nov 6, 2026
Integrates #1159 (#941 Unit 2) per owner ruling #1031 c.6678672357; it touches no Introduction file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011zDyUSyEszk3JJx83uXKKq
Units 3-4) "the stretches of time an observer can examine are short compared with the recurrence time of a large world" -> "... may be short compared with ..." (+1 word), per owner ruling #1031 c.6678672357 (amaybaum, 2026-11-06): replace the categorical assertion with a qualified "may be" statement and keep the explanation that delayed memory may be observationally inaccessible. Main:141 states k*tau_S << t_R as a requirement, not as a derived fact; book ch01:121 uses "can be". .tex/.pdf regenerated from the same source by `sh ./build.sh Introduction` (pandoc 3.1.3, XeTeX 3.141592653-2.6-0.999995, TeX Live 2023/Debian; 16 pages, 0 missing glyphs). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011zDyUSyEszk3JJx83uXKKq
Owner
Author
Independent exact-head review: ACCEPTReviewed head
The revised head is ready for a separate owner merge decision, subject to final head/base and CI guards. |
amaybaum
marked this pull request as ready for review
November 6, 2026 06:58
This was referenced Nov 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#941 Units 3–4. One narrowly scoped Introduction correction PR, as the owner rulings allow:
main.Writer:
writer-941. Draft. Do not merge automatically. Merging needs exact-head review, green CI and an owner merge decision.Head:
dd79b705fab22963676330cbb5685d6702a3c415. History, in order:41d70e799565a4a0f072914e793575e65052d701: the R-15, X-2 and Har04 edits, single parent424f28b1e7b1201e9a13bd0e608e1b0e4ad9f93b(the first-reviewed head).3dc6e4f35af93e65ab538bb80877d0b76c4a419e: merge of updatedmain(git merge --no-ff origin/main), with parents41d70e79and374b2ef3d0af1f3233a1d6bc74bee3c32683e3c0(Merge #941 Unit 2: SC17/SC31/SC33 provenance narrowings, README 29-declaration inventory, closure ledger #1159). It merged cleanly, with no rebase, amend or force-push.README.md,papers/introduction_repro/README.mdand four files underverification/audits/manuscript/intro-corpus-audit-20261026/.papers/Introduction.*file:main's Introduction blobs are still.mde85f6699,.tex99d1775cand.pdf80091191.dd79b705fab22963676330cbb5685d6702a3c415: the S9-I7 edit plus a single rebuild of.texand.pdf, parent3dc6e4f3.Diff against
main(374b2ef3): onlypapers/Introduction.md,.texand.pdf, all generated from the same source revision. There are no Main, companion, book, FULL or Explainer edits.The four edits below each map to one ledger row and one owner-ruling item. The R-15, X-2 and S9-I7 changes are each traced to reviewed evidence.
1. R-15 (= X-1 = #918 rF-10). Ruling item 4: "Approve restoring the previously reviewed, narrower Doukas wording."
Intro L93
That is +7 words, which matches the ledger.
Reviewed evidence on
main. The sentence is the landed text of the #918 Introduction landing,f5efa7a0813218b580272f7fd80a6b0c87eb6657(Merge #1124), which is reachable frommain.git show f5efa7a0:papers/Introduction.md | sed -n 172pcontains:The reviewed correction was #918 round finding rF-10, which is FINDINGS R-15. Its proposed text for this site is the same string, citation bracket included:
The current L93 wording, "the same argument", is rF-10's pre-correction wording, and it came back in the rewrite.
How the citation bracket is handled. I restored the reviewed clause verbatim, with
[Dou26, Prop. 1]kept after "realizers". That is the bracket's position atf5efa7a0:172 and in rF-10's proposed text. A byte check confirms the new L93 contains exactly the landed clause,grep -Fwith one match in each.Keeping the bracket as landed makes the edit a pure restoration, and the +7 count holds: 9 → 16 words, bracket unchanged. The clause's role is also the same as at
f5efa7a0. It follows the contraction step ("the standard contraction criterion for divisibility [RHP14, Thm 2.4; BD16]"). It attributes the contraction argument, not the overlap-and-return theorem, which is what rF-10 corrected.First-hand source check (this PR). I read Dou26 = arXiv:2602.22095v3 (19 Oct 2026, matching reference entry L231) on 2026-11-06 at 05:30Z.
So the restored wording, "the contraction argument … as a no-revival obstruction to Markovian realizers", is supported as stated.
2. X-2 (= R-20 prior leg = R-35 bound = S9-A2 Introduction side). Ruling item 9: "Approve the narrow correction, but first independently verify the prior conditions. If missing, add only the supported uniform-message qualifier."
Intro L163
That is +5 words, and nothing else in the sentence changes.
Reviewed evidence on
main. The paragraph cites [BHa], which isverification/programmes/black-hole-information/bh01_access_v1/REPORT.mdat424f28b1.REPORT.md:42–44: "Zero accessible advantage (P_succ = 1/|M|) requires the inaccessible endpoint set to have at least|M|joint values: by C2, a bijective instance with|K| < |M|hasP_succ >= 1/|K| > 1/|M|"REPORT.md:92: "P_succ = (1/(|M| N)) sum_y max_m c_m(y)". The 1/|M| weight is the uniform message prior, with equal-size supports|X_m| = N(:91).REPORT.md:297 (Scope): "Uniform message prior with equal-size supports."The cited source therefore proves the "joint values ≥ possible messages" floor only for a uniformly distributed message, and L163 stated it with no prior. The qualifier narrows the sentence to what [BHa] proves. Its wording is R-35's own ("for a uniformly distributed message").
Prior condition independently verified (Unit 4 check, before the edit).
|M| = 3,|K| = 2,P_succ = 1/2, equal to the maximum prior. The same review states that the uniform-message qualifier is a correct and sufficient fix.|K|< |supp M| under non-uniform priors;Placement. The qualifier goes between "and" and "hiding", not before "Reading". The recovery clause is C1, which
REPORT.md:52–54 states for every encoding and prior. No mirror of this sentence exists anywhere in the corpus (see the re-grep below).3. Har04 (ledger OD-8 Har04 row). Ruling item 8: "Require a first-hand source check for any substantive claim attributed directly to Har04. Otherwise, explicitly qualify the attribution as secondary."
Intro L133
The reference entry [Har04] (L241) is kept, and "citing Har04" still cites it.
First-hand check: Har04 itself is unreachable.
is_oa: falseandhas_repository_copy: false, and OpenAlex reportsclosed. No arXiv copy was found.First-hand check: Montina's report is supported. Source: Mon08 = arXiv:0711.4770v2, Phys. Rev. A 77, 022104 (2008), matching L259. Re-read for this PR.
Why this form. The Introduction's brackets use
[Key, locator]and[Key; Key], so "[Mon08; Har04]" presented Har04 as a co-equal direct source. "[Mon08, citing Har04]" keeps Mon08, the source that was checked, as the cited source, puts the secondary qualifier in the locator slot, and leaves the prose ("Montina reports …") unchanged.papers/Juno.md:59 "[18, §7.1, citing Mason et al.]".papers/oi_lattice_code/citation_check.pypasses with 0 broken citations.4. S9-I7 (leg 3, t ≪ t_R). Ruling #1031 c.6678672357 §2: "replacing the categorical assertion that observable timescales are short relative to recurrence with a qualified may be statement. Do not claim that has been derived or controlled." "Use the minimum correction, preserving the explanation that delayed memory may be observationally inaccessible."
Intro L97. The text was verified on the updated
main(374b2ef3) before editing.The change is "are" → "may be", +1 word. Nothing else in the sentence or paragraph changes.
Ledger row and finding. The row is S9-I7, an independent proof review finding (
proofs/README.md:62 in the audit records): "t ≪ t_R is not controlled". The independent Units 3–4 consistency check found legs 1 and 2 supported, but leg 3 not supported at L97:Reviewed evidence on
main.papers/Main.md:141 states the timescale separation as a requirement, not a result: "(C4) and condition (ii) of §3.4 require an accessible order,papers/Main.md:447's "exponentially large" is stated only for Hamiltonian flow under its own assumptions.book/ch01-observation.md:121 and its FULL mirror use the modal form: "the recurrence timeThe Introduction's categorical "are short" was therefore stronger than its cited support [Main §2.3, Scope]. The qualified form matches what Main provides.
Why "may be". It is the owner's wording, and it reads correctly in context. The sentence still explains why the failure need not be "of anything an observer will see": memory can first appear after every examinable stretch whenever those stretches are short. The paragraph's conclusion needs only that possibility, so the explanation the ruling says to preserve is intact.
The consistency check had proposed "can be". I used the ruling's "may be", since both are within the one-to-two-word limit and the ruling names that form. The edit asserts no derivation or control of the separation. The register scan confirms no "derived" or "controlled" wording was added at L97.
Mirrors. None. "recurrence time of a large world", "stretches of time an observer can examine", "memory can first appear" and "not necessarily of anything an observer" occur only at Intro L97 and its
.tex.S9-I2 and S9-I8 are not touched, as ruling §2 requires.
No-change rows recorded (sources from the independent Units 3–4 check)
doi.org/10.5281/zenodo.19060318→zenodo.org/records/23608753, with version 3.1.4, published 2026-10-24, version DOI 10.5281/zenodo.23608753 and conceptdoi 10.5281/zenodo.19060318.README.md:143 onmain("concept DOI 10.5281/zenodo.19060318, which resolves to the latest version").§A.42 item 8: off-
mainreferences in this PR16fc745d, not onmain)mainatf5efa7a0:172, and the attribution it makes is supported by the external Dou26 v3 Prop. 1, which I re-read first-hand above. Neither the claim nor its support uses the off-mainfile.proofs/bha-c1-c3/REVIEW.mdS9-A2 (commit16fc745d, not onmain)REPORT.md:42–44, :92 and :297 onmain. The counterexample shows why the qualifier is needed, but the sentence as edited does not use it.main)maincontent or by a public external source quoted above.mainmain)papers/Main.md:141 onmain, which states the separation as a requirement. The check's counterexample shows why the qualifier is needed, but the sentence as edited does not use it.proofs/README.md:62 (proof-review records, commit16fc745d, not onmain)Main.md:141 onmain.16fc745d)README.md:143 onmain, and it was re-resolved.No reference is classified "support off
main", so no gap remains.Corpus-wide re-grep (§A.25, §A.14)
I grepped all tracked
papers/*.{md,tex},book/*.md(chapters andThe-Incompleteness-of-Observation-FULL.md) and every other tracked file outsideverification/.Doukas|Dou26|Montina|Har04|ontological excess|perfect secret sharing|Shamir|joint values|uniform(ly distributed)? message|drawn uniformly.papers/Introduction.md(L93, L97, L133, L163) and its generated.tex. The L97 terms are listed in section 4.verification/.papers/Main.md:218, :228 and :836 (withMain.tex) cite Doukas [22] for different claims (correspondence scope, phase uniqueness), so they are left unchanged..mdand.tex: 0.main(each a whole paragraph) for the meta-commentary, reader-instruction, history-phrase and label-restating families, and for mid-sentence ALL-CAPS outside acronyms: 0 hits. I also checked for added "derived" or "controlled" wording. The only match is the existing L163 text "none is derived from the substratum's dynamics", which is not new wording.tools/voice_check.pypasses.Rebuild (c.6643207092 conditions; AGENTS.md build recipe)
sh ./build.sh Introduction, which runs pandoc with--include-in-header=tools/unicode-fix.texfor both the.texand the.pdf.lmodern.styis present, so no shim was used and the PDF is not provisional..md,.texand.pdfcome from one source revision. The.texfooter reads% source-sha256: 9be0977202f1aa885ee2e4a817b074950003d61a2dcb8ef93ddbc34c0ee8a43a, which equalssha256sum papers/Introduction.mdat head, andtools/staleness_check.pypasses..texdiff againstmain(374b2ef3) is confined to the four edited paragraphs (re-wrapped) plus that footer line. One rebuild atdd79b705covers all four edits.mainPDFMissing characterwarnings (separate verbose build log)mainPDF shows the four edits plus layout reflow only: page-number positions, one line-end hyphen ("classical-dimension") in the L133 paragraph, and one page break.Checks run locally (no Lean build, no dispatch)
All of the following passed at head
dd79b705(and earlier at41d70e79):toolchain,staleness,voice,voice-scope,ci-gate-presence,artifact-placement,manifest-drift,claims,duplicate,mirror,citation(109 citations, 0 broken),architecture,dependency-label --strict,coverage,lean-manuscript(census),baseline-label;legacy-records(303 records intact);v3_verifier --self-test,--corpusand--receipts(53 receipts hold);citation-roles.Not run:
lean-axioms, which needs a Lean build and runs in CI.Push-triggered workflows were inspected before each push. None fires on this branch. The path filters match neither
papers/nor the merged #1159 paths (README.md,papers/introduction_repro/,verification/audits/manuscript/intro-corpus-audit-20261026/), #1159 changed no workflow, andverify.ymlandhidden-sector-replay.ymltrigger on push only formain. The draft PR runs the ordinaryverify.ymlpull-request CI. That run tests a synthetic merge and is not an exact-head attestation.Not done (outside authority)
No merge, no workflow dispatch, no Issue state change, and no edit beyond the four above. S9-I7 is to be recorded as corrected only after this revised text passes review (ruling §2).
https://claude.ai/code/session_011zDyUSyEszk3JJx83uXKKq
Generated by Claude Code