Skip to content
back to the quest log
Heavy Element Avoidance repository with its machine-checked scope and build instructions
epic∎ researchshipped

Heavy Element Avoidance

A total-search core, checked in Lean

A machine-checked Lean 4 formalization of the finite explicit-sampler core behind the Heavy Avoid problem from FOCS 2024.

role
Formalization author
org
Independent research
when
2026

What it is

The work defines the induced distribution of a finite sampler, formalizes heavy sets, and proves that a light output exists in the total-search regime.

It also implements a deterministic exhaustive solver and proves that its output satisfies the specification using exact rational arithmetic.

The scope is deliberately narrow: it proves the finite existence and search core, not a polynomial-time solver for the general problem.

where the effort went

  • Proof96
  • Specification94
  • Auditability96
  • Algorithms74

the numbers

Proof escapes
0
Arithmetic
Exact ℚ
Solver
Exhaustive
Lean
4.33.1

built with

  • Lean 4
  • Mathlib
  • Lake
  • Exact rationals

delivery record

What I made

I wanted to separate the exact combinatorial statement that can be verified today from the broader complexity claim that remains research work.

  • 01

    Finite sampler and induced-distribution definitions

  • 02

    Heavy-set cardinality bounds over exact rationals

  • 03

    Machine-checked proof that a light output exists

  • 04

    Deterministic exhaustive solver with a proved specification

  • 05

    Source-audited build with no sorry, admit, custom axiom, or unsafe escape

Hard problems

The constraints mattered as much as the finished interface.

01field note

Keeping the theorem honest

problem
An executable exhaustive solver could be mistaken for progress on the polynomial-time complexity question.
response
The formal statement, README, and complexity note separate totality from efficiency and record the exponential search bound.
02field note

Finite probability without floating point

problem
Approximate arithmetic would weaken the exact threshold statements used by the proof.
response
The development uses finite sums and rational values throughout, so every inequality is checked symbolically.

Screens

after shipping

What stayed with me

  • Formalization is most useful when it narrows a claim to exactly what the proof establishes.

  • A proved exponential solver can still be valuable as a specification and a base for future refinements.