Reformalization of the Jordan Curve Theorem
Translating large formal developments between proof assistants (reformalization) is hindered by mismatched logical foundations and poor library alignment, producing unnatural, non-idiomatic proofs.
The task takes an existing formal proof as an exact specification and uses an LLM agent with tool use and a verification loop to build a native, idiomatic development in a target assistant. Three case studies port the Jordan Curve Theorem: Mizar to Lean, HOL Light to Lean, and HOL Light to Agda. Workflows involve dependency extraction, catalogue building, skeletons with sorry placeholders, and section-by-section proof filling, keeping the target proof checker in the loop.
Lean targets used well-developed libraries and tooling; the HOL Light to Agda port reached only foundational sections plus parts of section E (about 27,000 lines) and is incomplete. Libraries, tooling, and explicit handling of foundational mismatches (e.g., Agda's empty types) strongly affected success.
