proof-driven-development

Proof-driven development uses Lean 4 to formally specify and prove algorithm correctness before translation. It targets logic-rich software like data structures and parsers, providing a verified formal reference to guide implementation and reduce errors.

To verify algorithm correctness using lake, initialize a Lean 4 proof project, write the formal specification, and execute proofs to ensure properties hold across edge cases before translating the verified algorithm to the target language.

Yes, proof-driven development requires differential testing after translation. It compares outputs from the Lean 4 specification against the target-language implementation to validate equivalence and catch any translation bugs.

Yes, you can apply formal specification and proof to state machines and parsers. Lean 4 captures types, function signatures, and properties to verify logic-rich software components before implementation.

To maintain proofs alongside production code, store them in a dedicated proofs directory and keep them synchronized with the target-language implementation to ensure ongoing formal verification.

The best way to translate a verified Lean 4 algorithm is to first prove the specification with lake, then translate the verified algorithm to the target language, and finally run differential tests to validate equivalence.