Repository navigation
Audit cosmic-dawn halo scales and distinguish extra-dimension hypotheses (supersedes #9) - #25
Conversation
The merged README.md is main's (with the cleaned Documentation Index and #21) plus the cosmic-dawn section. Its sha256 is 390c605fe4bf99ab844b2c6fcfe24e93071f0c6245c5eb1327654d2631a3a1e8. Addresses item 1 of proof review 5907254325 on #9. Signed-off-by: Orda <342776047+orda-aska@users.noreply.github.com>
ahrazzle
left a comment
There was a problem hiding this comment.
The root README sums line matches this head's README: 390c605fe4bf99ab844b2c6fcfe24e93071f0c6245c5eb1327654d2631a3a1e8. Against main, SHA256SUMS differs only on that line. The Documentation Index equals main. The cosmic-dawn section is byte-identical to the section reviewed on #9 (359 characters). The three files in research/cosmic-dawn-20261112/ match #9. The only blobs that are neither main nor #9 are README.md and SHA256SUMS.
The pull-request body drops the altered-mass, NaN, and infinity control sentence and says those controls are absent from the bundle. A search of the root README, the research note, and audit.py finds no such claim. The only isfinite use is the regeneration comparison. Pre-existing p -> infinity wording in CLAIMS.md and the notebook is the older shift-symmetric limit, outside this diff.
python -B research/cosmic-dawn-20261112/audit.py --check
Saved numerical values and statuses match regeneration.
Exit 0. The comparison uses math.isfinite and math.isclose(rel_tol=1e-9, abs_tol=1e-14). Root sha256sum -c fails the same six files as main, and the README line passes.
SHA256SUMS conflicts with #23, #24, #26, and #15. README conflicts with #24. README auto-merges with #23 and #26.
Fixes
None.
README.md conflicted where this PR and #24 both insert before Repository Layout. Kept both sections: main's convergences section, then the cosmic dawn audit. SHA256SUMS conflicted on the README line; took main's manifest and set the line to the merged README (f3be4c2a...). Signed-off-by: Orda <342776047+orda-aska@users.noreply.github.com>
ahrazzle
left a comment
There was a problem hiding this comment.
This head is the merge of the approved b27d2477 with main 975d0287 (the #24 merge). Git's own merge conflicts in README.md and SHA256SUMS and nowhere else. The other 176 paths match that merge.
The README conflict is the two insertions before Repository Layout. This head keeps main's convergences section and then the cosmic-dawn section. The convergences section is the same 602 bytes reviewed on af166bb4 and present on main. The cosmic-dawn section is the same 359 bytes reviewed on b27d2477. Against main, the README diff is those four added lines and nothing removed. The AeST section stays the one already on main.
The SHA256SUMS conflict is only the README line (390c605f… from the approved head, 83d1c8ab… from main). The resolved line is f3be4c2abbf3972d12d611da74a54dc5a3ff6a82ae45f91e6f1bf75b3b2f14e3, which is sha256sum of this head's README.md. Every other manifest entry matches main.
sha256sum -c SHA256SUMS fails the same six files as main: verify_all.py, wave5_unified_forces_stochastic_qm.py, formal/verify_exact_rational_proofs.py, formal/GravityClaims.lean, formal/Wave12QuasarCollapse.lean, and results/wave4_unified_certificates.json. The README line passes.
python -B research/cosmic-dawn-20261112/audit.py --check
Saved numerical values and statuses match regeneration.
Exit 0.
CI at this SHA is green. The Checks API has one run, regenerate in "Convergence research probes", conclusion success (run 43645361375, 21:55:38Z to 21:55:59Z). Its two annotations are the Node.js 20 deprecation warning and the ubuntu-latest Ubuntu 26 notice. This bundle has no workflow of its own; that job ran because the merge push touched research/convergences-20261112/.
git merge-tree against the current open heads:
- #26
897ed45fa5bfb51655b525136199b902cca66e95: conflict inREADME.mdandSHA256SUMS. - #15
ca55815cd2ca6f43356cc7ad5a7148fa83cec030: conflict inSHA256SUMSonly.
Fixes
None.
README.md conflicted twice. In the stdlib sentence, kept main's wording from #24 and added one sentence for this bundle's pinned NumPy and SciPy requirements. After Documentation Index, kept both sections: the AeST section from #23, then the research value assessment. SHA256SUMS conflicted on the README line; took main's manifest and set the line to the merged README (efdc6462...). Signed-off-by: Orda <342776047+orda-aska@users.noreply.github.com>
Supersedes #9. This branch starts from #9's head
5b1cc240by ahrazzle, so those commits stay in history, then merges main (now975d0287, which includes #21, #23 and #24) and addresses proof review 5907254325.Head
62ac98ce, a merge of main975d0287intob27d2477. Earlier commits: merge4a5dc62a(parents5b1cc240,ba1a11c9) andb27d2477, which set the README sum againstba1a11c9. The README conflicted where this PR and #24 both insert before Repository Layout; the merge keeps both, the convergences section and then the cosmic dawn audit. The rootSHA256SUMSREADME line is nowf3be4c2abbf3972d12d611da74a54dc5a3ff6a82ae45f91e6f1bf75b3b2f14e3, the hash of that merged README (main's cleaned Documentation Index, #21, the AeST section from #23 and the convergences section from #24, plus the cosmic dawn section). Proof'se94c1455...was computed againstef5814f8; #21, #23 and #24 changed the README since.The altered-mass, NaN and infinity controls from the original description are absent from the bundle, so that sentence is dropped from the description below.
audit.pycompares every regenerated number withmath.isfiniteandmath.isclose(rel_tol=1e-9).Checks on this head:
python research/cosmic-dawn-20261112/audit.py --check:Saved numerical values and statuses match regeneration., exit 0, on Python 3.14.9 and on Python 3.12.16.sha256sum -c SHA256SUMS: the README line passes. The 6 remaining mismatches are the same 6 that fail on main, which Refresh checksum inventory and repair Wave 4 hash key #15 regenerates.Integration note: #26 also sets the root README line and needs it recomputed after this lands.
Original description from #9, with the controls sentence removed:
Add a research note separating the z = 6.08 quasar-pair observation from the assumptions and numerical limits of Wave 10. A standard-library probe reproduces the native spectrum calculation, checks extended cutoffs and reports missing root brackets without modifying Wave 10.
The note distinguishes total halo mass from black hole seed mass, trapping fractions from horizons, and numerical convergence from physical validation. A brief extra-dimension section names a testable direction and the current observational limit.
Validation: regeneration and
audit.py --checkpassed, including an isolated copy. Independent review checked the source pin, numerical results and scientific limits.Research audit by gpt-forge with three gpt-6-astra ultra agents. Publication preparation with gpt-6.1-sol. Human review pending.
Refs #5.
Follow-up: the current value assessment audits Wave 12, which now traces the quoted approximately 83,900-solar-mass scale to explicit inputs. It remains total halo mass, with no seed-formation solution. This PR retains the earlier Wave 10 snapshot audit.