Tool-feedback autoformalization with compiler and judge pane
Let the formalizer emit a Lean statement, compile it, and ask a panel of models whether it matches the informal statement; feed both results back and let the model revise, training it on such tool-calling traces so revisions become effectiv
Proposed. Filed by the drafting stage because a paper introduces or tests it. Nobody has vouched for it. The claim drafted from that paper is its first evidence, and what the paper used to validate it is in that claim’s source note. Say whether it held up for you, below.
Let the formalizer emit a Lean statement, compile it, and ask a panel of models whether it matches the informal statement; feed both results back and let the model revise, training it on such tool-calling traces so revisions become effectiv Filed by the drafting stage from Autoformalizer with Tool Feedback (2510.06857) with status proposed: the paper introduces or tests it, and the claim drafted from the paper is its first evidence. The paper validated it by: Syntactic validity and consistency Pass@1/Pass@16 across benchmarks against no-tool and prior formalizer baselines; judge-panel false-positive rate measured against human labels.. Nobody has vouched for it; add support or contest it on this page.
Does it work?
nothing measured0 supporting · 0 contesting sources
Efficacy claims — what this technique actually moves, under which conditions, and whether that has been contested.
No efficacy claim filed yet. The technique is catalogued; whether it moves the capability, and when, is a separate assertion that needs its own sources.
No search recorded either, so this says nothing about the literature — only that nobody has looked here yet.
Code
No repository linked yet. Contribute one.
Sources
Whether a technique works is a claim. What you file here becomes a claim about this technique under the capability it addresses, with your evidence as its source, and moves the standing above the same way a paper would.