Inspect the argument
Follow the geometric reading path, then its proof and recorded review.
ONE CALCULATION, FROM SOURCE TO RESULT
Start with an exact calculation in two and three dimensions. It produces a narrow interval for each coefficient, using rational arithmetic with controlled rounding.
Pinned source observation: . Compare this timestamp with the present time; observation is not scientific revalidation.
main cefdb56e87a1787be2874ec260a70a730bbbddd7 · Math- 6e502c1f8a5632eb90670fd9fc0d52e421c015a2
Current status source · Current research guide · Current proof index
Current mathematical atlas · Current static graph and complete source inventory · Exact current observation payload · Historical mathematical material (original pins and observation). Scientific effect: NONE.
8 of 3373 indexed public files shown. Historical, recovery and operational paths are outside this discovery population.
History capacity: 2 of 512 mathematical archives; 25985735 of 805306368 conservative retained bytes (including registry and release-key allowances). Publication refuses additional versions at capacity; no history is pruned.
THE SIDE24 COEFFICIENT EXAMPLE
You need Git and Python 3.10 or later, and internet access for the source download. The calculation and its tests then run offline using Python’s standard library. Choose a new directory named side24-replay.
This shallow checkout avoids downloading the repository’s full Git history. The explicit commit below fixes the example even when the default branch advances.
git clone --depth 1 https://github.com/d6g8k5htny-coder/Math-.git side24-replay
cd side24-replay
git fetch --depth 1 origin f430fdecbb1d8802d8af40419b701f12af87c039
git checkout --detach f430fdecbb1d8802d8af40419b701f12af87c039
python3 -B -S -m unittest discover -s coefficients/side24_v1 -p "test_*.py" -v
python3 -B -S coefficients/side24_v1/coefficient.pySelect the command block above to copy manually. This page does not run commands.
On Windows, use py -3 in place of python3. No GPU, API key, account, or numerical package is needed.
Repository: Math- at f430fdecbb1d8802d8af40419b701f12af87c039. The entry point is coefficient.py; its 30 tests passed in a fresh checkout with Python 3.11.16 on 30 September 2026. Download time depends on the connection.
At this commit, PROOF.md has SHA-256 c06daccc4ba4b9168522b9888b76a7d599934fc3b91bd753ee5d492262917769, the same bytes the Library pins at Math 9d7b6802 and the source record quotes at Math d6628da; coefficient.py has SHA-256 03ae6d0f15160cb681f9bbb19a84dc861c3a0db3e881291ea621061cc90c86ab at all three commits (recomputed from the repository on 8 October 2026). Identity of bytes is not a change of review scope.
As read on 8 October 2026 (Math- 7014efec), coefficients/side24_v1 has no commit after f430fdec, so the pinned replay is also the current package; a later change would not alter this pinned example.
WHAT YOU SHOULD SEE
The test command ends with Ran 30 tests and OK. The calculation prints JSON containing these exact decimal endpoints:
| Dimension | Lower endpoint | Upper endpoint |
|---|---|---|
| 2 | 0.07340691930603427103 | 0.07340691930603427104 |
| 3 | 0.04177593184059834334 | 0.04177593184059834335 |
Copies preserve the decimal strings above and include the historical source. They do not run the calculation or update its scientific status.
Select the endpoints in the table to copy manually.
The output also retains scientific_acceptance: false and its original parent theorem unreviewed scope. That is part of the historical calculation’s output; later reviews have their own source and scope.
This replay checks this coefficient calculation. It does not establish the parent lifetime theorem, identify an elder-pairing event, verify every mathematical result, or run the separate Lean package. The coefficient’s recorded review explains its scientific boundary.
GO FURTHER WHEN YOU WANT TO
Follow the geometric reading path, then its proof and recorded review.
The full execution guide covers other mathematical packages, deliberate error controls, source lookup and historical research branches.
Cite the source you used, including the full commit, file path, and any relevant review.
Formal checks have a separate introduction and pinned Lean environment and build instructions.