Exact Zarankiewicz Values On Two Finite Frontier Slices
This paper presents a combined, certificate-based computer-assisted proof establishing exact Zarankiewicz numbers for specific finite slices and a neighboring frontier of the Z(m,n,3,3) problem, utilizing orbit certificates, deletion lemmas, and rigorous arithmetic verification to confirm values such as Z(12,n,3,3)=6n for 18≤n≤22 and Z(13,22,3,3)=137.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are a city planner trying to build the most efficient road network possible. You have two groups of locations: a set of "Hubs" on one side and a set of "Destinations" on the other. Your goal is to draw as many roads (connections) as you can between them to keep traffic flowing. However, there is a strict zoning law: you are forbidden from building a specific, messy intersection pattern. In math-speak, this forbidden pattern is a "complete bipartite subgraph," or simply, you can't have a situation where three Hubs are all connected to the same three Destinations. If you do, you've broken the rule.
This puzzle is known as the Zarankiewicz problem. It's a classic brain-teaser in the field of combinatorics, which is the branch of mathematics dedicated to counting, arranging, and organizing things. While mathematicians have figured out how to solve this for massive, theoretical cities, the real challenge lies in the "medium-sized" towns. For these specific sizes, the number of possible road maps is so huge that you can't check them all by hand, but they are also too complex for simple formulas to solve. It's a Goldilocks zone of difficulty: too big for a pencil-and-paper proof, but too small for the "asymptotic" shortcuts that work for infinite cities. Solving these exact numbers matters because they reveal the hidden limits of efficiency in networks, from computer chips to social media connections.
Enter Koyar Afrasyab, a researcher who has just cracked open a particularly stubborn set of these medium-sized puzzles. Think of the problem as trying to find the absolute maximum number of roads you can draw on a grid without creating that forbidden "three-by-three" traffic jam. Afrasyab didn't just guess; they built a digital detective agency to hunt down the answer. The paper focuses on two specific "slices" of this problem: grids with 12 rows and grids with 13 rows, paired with various numbers of columns.
The main discovery is a list of exact "speed limits" for these grids. For a grid with 12 rows and anywhere from 18 to 22 columns, the maximum number of roads (edges) you can have without breaking the rule is exactly (where is the number of columns). For example, a 12-by-18 grid can hold exactly 108 roads, and a 12-by-22 grid can hold exactly 132. The paper proves this by showing that if you try to add just one more road to these grids, you inevitably create the forbidden traffic jam.
The most dramatic part of the story involves a 13-by-22 grid. Previous guesses suggested the limit might be as high as 140 roads. Afrasyab's computer-assisted proof acts like a sieve, filtering out every single impossible arrangement. They started by assuming someone could build a grid with 138 roads without breaking the rules. Through a clever process of elimination—checking the "profiles" of how many roads connect to each point—they proved that 138 is impossible. They narrowed it down until they found the true ceiling: 137 roads. They even provided a specific, verified map of 137 roads that works, proving you can reach that number but not go higher.
The paper also fixes the map for several neighboring grids, determining the exact limits for sizes like 13-by-18, 14-by-17, and 15-by-18. For one tricky case, a 16-by-17 grid, the proof confirms you can definitely build 132 roads, but the upper limit is still a tight range between 132 and 133.
What makes this work special is how it was done. The author didn't just run a black-box computer program that said "No solution found." Instead, they created a "certificate-based" proof. Imagine a detective leaving a trail of breadcrumbs: for every impossible scenario they ruled out, they left a mathematical "receipt" (a certificate) that anyone can check with a simple calculator to verify the error. The paper includes a digital package where you can run a single command to replay the entire investigation, checking millions of these receipts to ensure no mistakes were made. It's a rigorous, transparent, and fully reproducible victory for the math community, turning a set of "maybe" answers into a set of "definitely" facts.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.