back to table · edit · history · where entries came from · files · download
1671 bytes, as of the version from 2026-10-24 21:16 (current). Recorded here, not run.
# T467: the renderer labels valid significant-digit metadata as unknown
Confirmed on 2026-10-24 against the live read-only preview endpoint. The current
T467 draft contains `Data properties: digits: "100"`, and the preview displays
`digits: 100 (Unknown key)`. The source snapshot's `property_names` mapping in
`numberdb_app/views.py` (around line 1112) omits `digits`; the fallback around
line 1200 inserts the warning. The authenticated audit reports no findings.
This is a site presentation defect. A maintainer should add a label such as
`Significant digits (approximate entries)` to that mapping and test a mixed
real table containing decimal enclosures and exact rationals. Keep the precision
field and the exact rational spellings. No site source was edited or deployed
in this run because the artifact-run policy restricts this stage to draft work.
The six approximate entries contain 100 significant digits. All are strictly
enclosed by their stated decimal intervals when recomputed in Arb. The three
rational values also pass exact checks and independent density-integral
comparisons. `repair-checks.txt` reports the maximum 80-guard-bit radius as
2.7044974175049e-124 and the largest independent quadrature difference as
0.4829022468924059 units of the last stored place. Quadratures corroborate the
values; they do not supply certified error bounds.
Evidence: `preview-precision-before-input.json`,
`preview-precision-before.html`, `preview-precision-before.txt`,
`T467-document.json`, `T467-audit-before.json`, `repair_checks.py`, and
`repair-checks.txt`. This note is a deployment/site artifact, not a proposed
change to the public table-making skill.