back to table · edit · history · where entries came from · files · download
3354 bytes, as of the version from 2026-10-25 19:59 (current). Recorded here, not run.
# T501 repair evidence, 2026-10-25
The live draft still contained the critique's unfinished sentence, precision
renderer warning, and late companion link. The repair removes “These counts
are” and attaches its citations to the complete alternating-permutation
formula. It moves the existing T500 link to the completeness note and leaves
the later mention as plain text. No number, parameter, precision metadata,
other formula, reference, or companion link was changed.
The attached `repair_verify_T501.py` includes the displayed zeta/Hurwitz-zeta
generator and independent checks. Under Sage 10.9 and numberdb 0.1.10, it:
- Recomputed all 21 values, with 397-bit Arb arithmetic for the 20 approximate
entries and the exact integer K_0=1.
- Counted alternating permutations by dynamic programming on the final rank,
checked by exhaustive enumeration through order eight and the exact
differential equation F'=(1+F^2)/2 for F=sec+tan through order twenty.
- Evaluated A_r*pi^r/(2^r*r!) independently at 600 bits and certified that
each finite ball lies entirely within the stored decimal interval.
- Confirmed exactly 100 significant digits in each approximate value, the
parity inequalities on the stored range, and all 190 T500 relations.
All 21 integer counts match the first 21 lines of
https://oeis.org/A000111/b000111.txt, retrieved through the web tool after
direct requests returned HTTP 403. Elkies's equation (8) and Theorem 2 were
read at https://arxiv.org/html/math/0101168v5. They support the existing
normalisation and alternating-permutation interpretation; no new theorem or
numerical claim was added to the table.
The displayed program's multiplication order gives a largest Arb radius of
approximately 2.2592972e-119 in this check. This is not a failure of any
100-digit interval. A separate Sage check using (4*sum)/pi instead gives a
maximum radius of 1.8889961e-119, consistent with the recorded build bound
1.9e-119. A run's radius depends on expression evaluation order. The table's
historical build measurement was preserved; the attached JSON records the
displayed program's actual radii rather than asserting that they reproduce
that historical measurement.
The public /T501 page returned HTTP 404, and its unauthenticated API read
reported no such table, while authenticated reads succeeded. Accordingly,
this run verified the two affected sections through the live, read-only
/preview route. Playwright 1.64.1 rendered the original and proposed sections
with no JavaScript or MathJax errors. Screenshots were inspected. The new
companion link appears in the completeness note, and the unfinished phrase
is gone. This is not an authenticated whole-page layout check.
The live renderer still prints “digits: 100 (Unknown key)”. The source
snapshot's property_names mapping lacks a label for digits. This is a site
defect, not invalid table metadata. It remains for a person to fix; the
artifact-only campaign does not change or deploy website source.
The document was re-fetched immediately before writing, compared with the
original, written through the authenticated API, and read back exactly equal
to the proposed document. The API returned reviewed=false and the post-edit
audit returned clean=true with no findings. No publish, offer, review,
commit, deployment, or issue-comment action was taken.