Research notes on every problem, and a library of the papers behind them. Built from the open erdos repository.
Updated
Evidence for the height-three attack
The entry point main.py checks the finite statements used by
the height-three attack. It
retains three selected union trees for the first shape -- and
second shape --, and the explicit event schedule. It checks
both projections of each union tree, replays the three games, and
separately derives the actual convex leaf cells to check every nonfinal
maximum. A negative control replaces the first single mark by a double
and must fail the cell check. Exhaustive merging for this fixed pair
also confirms that no schedule keeps the first tree entirely synchronized.
The owning page gives the symbolic obstruction and the expansion proof
for arbitrary infinite sets and finite move thresholds.
The adjacent shape pair -- / -- is also checked:
it has a schedule, but none keeping the last tree entirely synchronized.
The full shape census covers height one with degree and leaf bounds , height two with degree bound and leaf bound , and height three with degree bound and leaf bound : respectively , and pairs, including an empty second shape when appropriate. Every found schedule is checked by both the turn replay and the cell reconstruction. The quick mode reduces only the height-three range to degree bound and leaf bound , or pairs. Height-one boundary cases and the other stated witnesses run in both modes.
The separate adversary probe permits counts at every selected node, including the roots, with access to the whole three-game state. Its lower-total filter ignores bounded upper totals and does not establish correct completion or game locality. Its reported wins are outcomes of that artificial finite process, not actual winning Architect strategies. The program and owning page state all of its cases.
Run from the repository root:
uv run --no-sync python wiki/research/erdos_592/height_three_evidence/main.pyAdd --quick for the reduced census or -O immediately after python
to check that optimization cannot remove the obligations. The program
uses exact integer counts, deterministic finite enumeration, the standard
library and the root tools package. It needs no external data, writes
no output files, and fails through a nonzero exit. The full run takes
about nine minutes and can use about four gigabytes; the quick run takes
under a minute. These are author checks, not independent review. No
partition relation or strategy reading arbitrary numerical histories is
certified.