Proposed change
reason
Bound and construction look correct under the Nathanson hypothesis but I want a Lean stub before promoting to accepted-core. The proof step that reduces geometric to polynomial diameter needs an explicit witness.
frontiers / frontier
Reviewable change
back to reviewThe h-squared-dissociated set construction needed for the polynomial bound has diameter polynomial in k, replacing geometric components in the original construction.
This is a proposal, not yet accepted frontier state. It names what it would change and who proposed it. Only an accepted review event, signed under reviewer authority, writes it into the frontier. Until then it carries no authority over the record.
Proposed change
reason
Bound and construction look correct under the Nathanson hypothesis but I want a Lean stub before promoting to accepted-core. The proof step that reduces geometric to polynomial diameter needs an explicit witness.
Provenance
proposed by
reviewer:will-blair
actor type
human
created at
2026-05-09
target type
finding
Affected finding
inspect finding →The h-squared-dissociated set construction needed for the polynomial bound has diameter polynomial in k, replacing geometric components in the original construction.
vf_3bde881fed68d7ddThe diff is computed against current frontier state, the same diff a reviewer reads before deciding.
The live diff is computed from a writable workspace. This frontier is read-only here, so the change is shown as recorded without a recomputed before / after.
Canopus treats material changes like reviewable requests: one bounded packet, check output, reviewer decision, and accepted frontier effect.
Additive combinatorics: Sidon sets and N(h,k) bounds receives a reviewable source, finding, caveat, replication, evaluation, or proof-affecting edit.
The packet names affected record objects, evidence, rationale, reviewer-facing fields, and expected proof impact.
Schema, provenance, benchmark, contradiction, and proof checks decide whether the request is ready to read.
A steward accepts, rejects, caveats, revises, or retracts the request under an inspectable identity.
Only the accepted event mutates frontier state. Atlases, constellations, and search update from that record state.