Skip to content

Drop the unverified asterisk on the C₃b record - #176

Closed
chessing234 wants to merge 1 commit into
teorth:mainfrom
chessing234:fix/c3b-drop-unverified-asterisk
Closed

chessing234 wants to merge 1 commit into
teorth:mainfrom
chessing234:fix/c3b-drop-unverified-asterisk

Conversation

@chessing234

@chessing234 chessing234 commented Sep 6, 2026 •

Copy link
Copy Markdown
Contributor

Refs #168 (item 5).

The README cell showed `1.77898 (1.77898884*)` while the constant page lists `1.77898884` without a star and the recent-progress line does the same. The bound has a zenodo entropy certificate, so it is not a minimally verified claim under the table's own convention.

The numerical record is unchanged; only the star is removed.

The README cell marked 1.77898884 with a star while the constant page and the recent-progress line did not. The bound has a zenodo entropy certificate, so it is not a minimally verified claim under the table's own convention.
@teorth

teorth commented Sep 26, 2026

Copy link
Copy Markdown
Owner

Thanks for flagging the inconsistency — it was real, but I have resolved it the other way, by marking the page rather than unmarking the README.

The $1.77898884$ record rests on a Zenodo entropy certificate that, as far as I know, nobody has replayed. A deposit is an archive, not a check: Zenodo issues a DOI and stores the file, and performs no refereeing or verification of the contents. That is squarely what the asterisk is for, and treating it as verified here would be inconsistent with #159, where three weeks ago I asterisked a Steiner-ratio bound on exactly those grounds.

So in d793db4 the constant page row now carries the * and says why, and the "Recent progress" line reads (unverified), which was the third place the three disagreed.

This was applied from precedent rather than from anything written down, which is partly why it was ambiguous, so I have also written the rule into CONTRIBUTING:

The asterisk marks bounds whose verification is currently minimal. [...] In practice this means a result that is both too large to verify independently by hand and available only as a self-archived artifact — a personal repository, a gist, a Zenodo deposit, a preprint server that performs no refereeing or verification of its own. Either condition alone is usually not enough [...] The marker is about the verification available today and is removed when that changes.

If the 13-point certificate does get independently replayed, or formalized, the asterisk comes off — that is the point of it. Closing this, and I would happily take a PR that removes it on those grounds.

@teorth teorth closed this Sep 26, 2026
teorth pushed a commit that referenced this pull request Oct 18, 2026
… replayed

Per the asterisk rule in CONTRIBUTING and the note on #176. Replay:
https://carlostoledo.co/reports/optimization-constants.html (doi:10.5281/zenodo.23171167).
Prepared with AI assistance (Claude); reviewed by the contributor.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants