Repository navigation
Publish cross-repository convergence research and reproducible probes (supersedes #8) - #24
Conversation
ahrazzle
left a comment
There was a problem hiding this comment.
The root README sums line matches this head's README: a90c7e762852d7d8c96ed727b25b8b8b9938d0dbd758cc7b607b04f5acde9f12. Against main, SHA256SUMS differs only on that line. The Documentation Index equals main. The convergences section is byte-identical to the section reviewed on #8 (02013ae9, 602 characters). All 62 files under research/convergences-20261112/ match #8, as does .github/workflows/convergences-probes.yml. The only blobs that are neither main nor #8 are README.md and SHA256SUMS, which is the merged text plus this digest.
python -m unittest discover -s research/convergences-20261112 -p test_check.py
Ran 6 tests OK
python -B research/convergences-20261112/check.py
PASS all nine probes; historical inputs match pinned SHA-256 digests
Both exit 0. The worktree gains only an untracked __pycache__. Root sha256sum -c fails the same six files as main, and the README line passes.
SHA256SUMS conflicts with #23, #25, #26, and #15. README conflicts with #25, because both insert a section before Repository Layout, and with #26, because they rewrite the standard-library sentence differently. README auto-merges with #23.
Fixes
None.
README.md merged cleanly and keeps both the convergences section and the AeST section from #23. SHA256SUMS conflicted on the README line; took main's manifest and set the line to the merged README (83d1c8ab...). 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 af166bb4 with main 73de1fdf (the #23 merge). Git's own merge of those parents conflicts only in SHA256SUMS, and the conflict hunk is the README line (a90c7e76… from the approved head, 0b347aed… from main). Every other file matches that merge: 175 paths, no additions, no omissions, and the auto-merged README is byte-identical.
The convergences section is the same 602 bytes reviewed on af166bb4. The AeST section is the same 609 bytes reviewed on 479a28ca and present on main 73de1fdf. The Documentation Index equals main. The root sums line is 83d1c8ab1eff15c1fac3d8c77ff647a0e757a323febfef38d71316b31d3802a3, which is sha256sum of this head's README.md. Against main, SHA256SUMS differs only on that line.
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 -m unittest discover -s research/convergences-20261112 -p test_check.py
Ran 6 tests OK
python -B research/convergences-20261112/check.py
PASS all nine probes; historical inputs match pinned SHA-256 digests
Both exit 0 on Python 3.12.3 with the bundle's NumPy, SciPy, and SymPy pins.
CI at this SHA is green. The Checks API has one run, regenerate in "Convergence research probes", conclusion success (run 43644849215, 21:49:41Z to 21:49:58Z). Its two annotations are a Node.js 20 deprecation warning for actions/checkout@v4 and actions/setup-python@v5, and a notice that ubuntu-latest will move to Ubuntu 26. The legacy combined-status API has no statuses for this SHA.
git merge-tree against the current open heads:
- #25
b27d2477af5da5d4e2ca2a78ce506a6fb766cfce: conflict inREADME.mdandSHA256SUMS. - #26
897ed45fa5bfb51655b525136199b902cca66e95: conflict inREADME.mdandSHA256SUMS. - #15
ca55815cd2ca6f43356cc7ad5a7148fa83cec030: conflict inSHA256SUMSonly.
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>
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 #8. This branch starts from #8's head
02013ae9by ahrazzle, so those commits stay in history, then merges main (now73de1fdf, which includes #21 and #23) and fixes the one item in proof review 5907254579.Head
17eb42ad, a merge of main73de1fdfintoaf166bb4. Earlier commits: mergeb9d57a59(parents02013ae9,ba1a11c9) andaf166bb4, which set the README sum againstba1a11c9. The rootSHA256SUMSREADME line is now83d1c8ab1eff15c1fac3d8c77ff647a0e757a323febfef38d71316b31d3802a3, the hash of the merged README. That README is main's (cleaned Documentation Index, #21 and the AeST section from #23) plus the convergences section. Proof's518c652d...was computed againstef5814f8; #21 and #23 changed the README since.Checks on this head (Python 3.14.9, NumPy 2.5.4, SciPy 1.18.1, SymPy 1.14.0):
python -m unittest discover -s research/convergences-20261112 -p test_check.py: 6 tests OK.python research/convergences-20261112/check.py:PASS all nine probes; historical inputs match pinned SHA-256 digests, exit 0, tree left clean.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: #25 and #26 also set the root README line. Whichever lands later needs that line recomputed from the merged README.
Original description from #8:
Publish nine exploratory research reports connecting gravity, fractals, physics0 and astr0, with primary-source ledgers, reproducible probes, independent agent reviews and concrete next tests. The repository README makes the collection discoverable.
The bundle includes an AeST collapse test specification, a compensated linear initial-state calculation, quantum-record comparisons, lattice mechanics and complementary-observation examples. Its source links retain the historical revisions actually studied. Downloaded papers and private operational material are excluded.
Validation: all nine probes regenerate ten saved artifacts in a fresh environment. Stale-result and altered-input controls fail as intended. Independent publication review checks privacy, links, preserved scientific qualifications and reproducibility. Six comparison regression tests also pass.
Hosted verification: all nine probes and comparison tests passed on Ubuntu.
Refs #5. The complete canonical initial-data map, nonlinear AeST collapse and a new galaxy-data fit remain uncomputed. This research record does not resolve the collapse issue or claim a new physical law. Human scientific review remains pending.
Research assistance by gpt-forge with gpt-6-astra at ultra reasoning. Publication preparation used gpt-6.1-sol. Full attribution and reviewed revisions are recorded in the bundle.
Companion notes:
Follow-up: the current value assessment tests the remaining mechanics, closure, photon-record and calibration questions, with explicit research gates. This PR retains the historical nine-route exploration and its reviewed source snapshots.