Alphabeta Math
RemarkRemark: Literature-sourcedProof: Not applicableSession-authored (Fable 5 assisted)audited 2026-08-16
How statement and proof provenance work

The first chip identifies the source of the statement or construction; the second identifies the source of its local proof or verification.

  • Literature-sourced: the exact statement appears in a cited source; only wording and notation differ.
  • AI-adapted: a semantically identical restatement of literature-sourced material, modulo indexing, notation, and boundary cases adopted by the library.
  • AI-generated: a genuinely novel statement formulated by AI, with no source for the claim itself.

These labels describe origin, not correctness: citations and verification chips remain separate evidence.

Ordinary regularity gives tower upper bounds; strong regularity gives wowzer upper bounds only when the regularity sequence depends on the coarse part count

Remark

The energy-increment proof of ordinary regularity in Szemerédi regularity lemma with an equitable partition and an explicit tower-type upper bound for graphs of order at least m0 iterates an exponential part-count recurrence only a bounded number of times and therefore gives a tower-type upper bound. The proof of Equitable strong regularity lemma: a very regular refinement that changes energy only slightly repeatedly invokes ordinary regularity at parameters indexed by an already enormous partition size, so when the regularity sequence genuinely depends on the coarse part count the nested iteration gives a wowzer-type upper bound. That dependence is what Induced graph removal lemma for a fixed graph does not need: the parameter it requires of its representative pairs comes from Induced counting lemma: regular edge and nonedge pairs force many induced copies and depends only on the pattern and the density threshold, so a constant sequence suffices, the nesting collapses to boundedly many applications at one fixed parameter, and the bound stays tower-type. These are upper bounds delivered by the displayed proofs, not claims of optimality.

Depends on

Used by

Nothing in the library uses this result yet.

Dependency tree · next 3 levels

Direct dependencies and their dependencies through the next three levels: 11 results over 8 levels. An arrow runs from a result to what uses it, and this result sits at the bottom with a heavier outline. Click the chart to enlarge it.

Sources