vericoding
Vericoding: write code together with a machine-checked proof that it meets a frozen formal spec, Lean 4 first (Dafny and Verus experimental), and refuse to call it done until a gate confirms the verifier accepted it, the spec is untouched, and no sorry/admit/axiom/assume or other bypass was slipped in. Use whenever the user wants verified, proven-correct or correct-by-construction code; asks to implement a def and prove its spec theorem; to fill sorry placeholders in a program and its correctness theorems; to solve vericoding benchmark tasks (<vc-preamble>, <vc-helpers>, <vc-definitions>, <vc-theorems>, <vc-spec>, <vc-code> tags, Verina, FVAPPS, CLEVER, DafnyBench); to prove a Hoare triple about a monadic Lean program with mvcgen; to write a formal spec from intent before implementing it; or to audit whether an agent's "verified" result cheated. Not for pure mathematics with no program in it.
