Repository navigation
Remove the asterisk from C3b, C3c and C71: certificates independently replayed - #216
Merged
Merged
Conversation
… replayed Per the asterisk rule in CONTRIBUTING and the note on teorth#176. Replay: https://carlostoledo.co/reports/optimization-constants.html (doi:10.5281/zenodo.23171167). Prepared with AI assistance (Claude); reviewed by the contributor.
teorth
added a commit
that referenced
this pull request
Oct 18, 2026
Combined with #216 on the shared C_3c README cell: that PR drops the asterisk from 1.6747338950414058 on the strength of an independent replay, this one adds 1.674894211307116 as the new unreplayed record, so the cell carries both as "certified (unverified*)". This PR also corrects the definition at the top of the page: the relation A +-^G rB ranges over (a,b) in G, not over a in A and b in B. Read the old way the constant would be at most 3/2 by Plunnecke-Ruzsa and Ruzsa's triangle inequality, which is below every bound the page records -- so the page was self-inconsistent, not merely imprecise. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
carlostoledo1891
added a commit
to carlostoledo1891/optimizationproblems
that referenced
this pull request
Oct 18, 2026
… and reverted by the teorth#221 merge, whose branch predated it Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
teorth
added a commit
that referenced
this pull request
Oct 18, 2026
First recorded improvement on the GHR2007 upper bound for C_3a, from 4/3 to 1.312373302115... Asterisked. The Lean 4 formalization and proof paper are self-hosted and, unlike the C_4b and C_47 entries, are not registered with a verifying service and have not been independently replayed, which is the condition CONTRIBUTING sets. The marker comes off on either. Row comment expanded to say what the proof actually does, which the submitted one-liner did not. Resolved against #216 and #221 on the 3b/3c rows of the same README block. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Oct 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On #176 you wrote: "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." CONTRIBUTING now states the rule: the marker "is removed when that changes — when the paper is refereed and published, or when the argument is formalized or independently replayed."
This PR offers that replay for three asterisked lower bounds, decided from the certificate bytes the registry cites with no code shared with the claimants. Markdown only.
c3b_pr92/certificate_3b_13pt.json, sha2562efe99360a1f…, 13 points62621d2d,certificate_3c_147pt.json, sha256b3dc9587ba7a…, 147 pointsfei_c71_n18_artifact.json, sha25657f5a1ad2bf5…How. For C3b and C3c, pushforwards are exact rationals and every$-p \ln p$ is an outward-rounded interval. Two implementations do this, sharing no code with each other or with the claimants' checkers: JavaScript over BigInt, and the Python standard library alone. For C71: the integer Walsh–Hadamard transform of all $2^{18}$ entries, the exact influence, and the entropy in outward-rounded intervals. The amplification rule $C \geq H/(I-1)$ is cited, not re-proved.
Re-derive from https://github.com/carlostoledo1891/cert-machine at
422b952(archived as doi:10.5281/zenodo.23171167):Write-up: https://carlostoledo.co/reports/optimization-constants.html
What changes:
Happy to split this per constant.
Related: the 147-point certificate's own checker compares at 53 bits, so it would also print OK for the false$C_{3c} \geq 1.6747338950414059$ (reported to its author: https://gist.github.com/CoolRmal/5368357cd781d7e5c676c9d68ad24d22#gistcomment-6408607). The bound above is decided without it.
Whether a replay by a third party is enough is yours to judge; if you would rather the marker stay until a formalization, I will close this.
AI-assisted: built with Claude (Anthropic) in a certified-arithmetic setting; the replay code, the records and this pull request were prepared with it, and I have checked every number and reference above against the records and the upstream files.