Step 1
State the proof target
Pin the repository revision, Lean and mathlib versions, theorem statement, allowed assumptions, target files, and acceptance conditions.
Quick answer
It is a specialized Lean 4 model with Apache-2.0 weights and a public-preview Mistral API. Use compiler feedback, inspect every assumption and edit, and reproduce the result from clean state before calling a proof verified.
Lean 4 formal proof engineering, automated theorem proving, autoformalization, and repository-scale proof work.
Mistral's release says 119B total and 6B active parameters; the current model card says 119B total and 6.5B active. Preserve that source difference.
Apache 2.0, with downloadable weights linked by Mistral from the release post.
The model card checked July 30, 2026 lists Public Preview, $0 pricing, 256k context, 128k maximum output, and the alias labs-leanstral-1-5.
The July 2 release calls the endpoint free and names leanstral-1-5. Verify the live model catalog before coding because it differs from the current model card.
Not established. Mistral weights or API availability does not prove a Flowith model mapping.
Proof engineering
Step 1
Pin the repository revision, Lean and mathlib versions, theorem statement, allowed assumptions, target files, and acceptance conditions.
Step 2
Use Lean compiler and language-server feedback in the loop. A plausible proof string is not a verified proof.
Step 3
Check for changed statements, added axioms, unsafe declarations, admitted results, dependency drift, and edits outside the approved scope.
Step 4
Compile in a clean environment, run repository checks, inspect the diff, and retain a human proof-engineering review.
The release and model card disagree on the API name and active-parameter rounding. This page preserves both records instead of choosing an undocumented replacement.