Lean 4 is both a functional language and theorem prover: write performant code and prove it correct in one place.
Our practical tutorial steps through two small programs and the machine-checked proofs of their contracts:
🔗 github.com/scidonia/ver...
Our practical tutorial steps through two small programs and the machine-checked proofs of their contracts:
🔗 github.com/scidonia/ver...
GitHub - scidonia/vericoding-tutorial: Vericoding Tutorial
Vericoding Tutorial. Contribute to scidonia/vericoding-tutorial development by creating an account on GitHub.
github.com
November 9, 2026 at 10:45 AM
Lean 4 is both a functional language and theorem prover: write performant code and prove it correct in one place.
Our practical tutorial steps through two small programs and the machine-checked proofs of their contracts:
🔗 github.com/scidonia/ver...
Our practical tutorial steps through two small programs and the machine-checked proofs of their contracts:
🔗 github.com/scidonia/ver...
Here's No. 5 From Proof to Binary of our 6 part vericoding overview.
This one details how we compile from proof assistant to runnable code.
#formalverification #vericoding
This one details how we compile from proof assistant to runnable code.
#formalverification #vericoding
November 3, 2026 at 11:48 AM
Here's No. 5 From Proof to Binary of our 6 part vericoding overview.
This one details how we compile from proof assistant to runnable code.
#formalverification #vericoding
This one details how we compile from proof assistant to runnable code.
#formalverification #vericoding
We believe that formal methods are now integral to software development.
However, going from vibecoding to vericoding can seem like a chasm.
It doesn't have to be a jump as this article explains.
scidonia.ai/blog/from-bd...
However, going from vibecoding to vericoding can seem like a chasm.
It doesn't have to be a jump as this article explains.
scidonia.ai/blog/from-bd...
From Vibecoding to Vericoding: A Gradient, Not a Jump | Scidonia
You do not have to go from zero to verified in one step. You can start with Gherkin scenarios, graduate to executable contracts with specsaver, and then bring in a theorem prover when you are ready.…
scidonia.ai
November 2, 2026 at 1:29 PM
We believe that formal methods are now integral to software development.
However, going from vibecoding to vericoding can seem like a chasm.
It doesn't have to be a jump as this article explains.
scidonia.ai/blog/from-bd...
However, going from vibecoding to vericoding can seem like a chasm.
It doesn't have to be a jump as this article explains.
scidonia.ai/blog/from-bd...
AI can exploit software vulnerabilities at terrifying speed.
AI-generated code and legacy systems are at risk.
At Scidonia, we use vericoding to verify that code is safe, secure and correct.
Visit scidonia.ai to learn more or book a discovery call.
#formalverification #vericoding
AI-generated code and legacy systems are at risk.
At Scidonia, we use vericoding to verify that code is safe, secure and correct.
Visit scidonia.ai to learn more or book a discovery call.
#formalverification #vericoding
November 1, 2026 at 10:19 AM
AI can exploit software vulnerabilities at terrifying speed.
AI-generated code and legacy systems are at risk.
At Scidonia, we use vericoding to verify that code is safe, secure and correct.
Visit scidonia.ai to learn more or book a discovery call.
#formalverification #vericoding
AI-generated code and legacy systems are at risk.
At Scidonia, we use vericoding to verify that code is safe, secure and correct.
Visit scidonia.ai to learn more or book a discovery call.
#formalverification #vericoding
Continuing the 6-part Vericoding Introduction. No. 4: Two Ways to Specify.
This one looks at intrinsic and extrinsic methods and provides some handy rule of thumb guidance when performing verification for programming languages.
#formalverification #vericoding
This one looks at intrinsic and extrinsic methods and provides some handy rule of thumb guidance when performing verification for programming languages.
#formalverification #vericoding
October 31, 2026 at 12:47 PM
Continuing the 6-part Vericoding Introduction. No. 4: Two Ways to Specify.
This one looks at intrinsic and extrinsic methods and provides some handy rule of thumb guidance when performing verification for programming languages.
#formalverification #vericoding
This one looks at intrinsic and extrinsic methods and provides some handy rule of thumb guidance when performing verification for programming languages.
#formalverification #vericoding
Here's number 3 in our 6-part Vericoding introduction series.
Your first contract.
#formalverification #vericoding
Your first contract.
#formalverification #vericoding
October 30, 2026 at 1:00 PM
Here's number 3 in our 6-part Vericoding introduction series.
Your first contract.
#formalverification #vericoding
Your first contract.
#formalverification #vericoding
No. 2 of Vericoding in 6 parts - Proofs are programs.
This video explains how and why theorem provers can be thought of as a programming language.
#formalverification #vericoding
This video explains how and why theorem provers can be thought of as a programming language.
#formalverification #vericoding
October 29, 2026 at 12:11 PM
No. 2 of Vericoding in 6 parts - Proofs are programs.
This video explains how and why theorem provers can be thought of as a programming language.
#formalverification #vericoding
This video explains how and why theorem provers can be thought of as a programming language.
#formalverification #vericoding
Formal verification is having a moment.
This is something we strongly advocate (and provide as a service).
We've put a 6-part explainer series together explaining vericoding. Here's the first:
What is vericoding.
#vericoding #formalverification
This is something we strongly advocate (and provide as a service).
We've put a 6-part explainer series together explaining vericoding. Here's the first:
What is vericoding.
#vericoding #formalverification
October 27, 2026 at 10:01 AM
Formal verification is having a moment.
This is something we strongly advocate (and provide as a service).
We've put a 6-part explainer series together explaining vericoding. Here's the first:
What is vericoding.
#vericoding #formalverification
This is something we strongly advocate (and provide as a service).
We've put a 6-part explainer series together explaining vericoding. Here's the first:
What is vericoding.
#vericoding #formalverification
Vericoding is an entertaining development
Its almost like
We acknowledge AI has little or no upside so let's retool a big downside ..
bad insecure, hard to explain or replicate code
OK lets 'inspect' that using the very AI behind the bad insecure....
Its almost like
We acknowledge AI has little or no upside so let's retool a big downside ..
bad insecure, hard to explain or replicate code
OK lets 'inspect' that using the very AI behind the bad insecure....
October 23, 2026 at 10:48 PM
Vericoding is an entertaining development
Its almost like
We acknowledge AI has little or no upside so let's retool a big downside ..
bad insecure, hard to explain or replicate code
OK lets 'inspect' that using the very AI behind the bad insecure....
Its almost like
We acknowledge AI has little or no upside so let's retool a big downside ..
bad insecure, hard to explain or replicate code
OK lets 'inspect' that using the very AI behind the bad insecure....
Can you write a concurrency library directly in a theorem prover?
Can you write real software with it, perhaps a webserver?
Can it be similar in performance to servers used in industrial production?
What language should I use for Vericoding?
Yes, yes and yes! And Lean clearly viable.
Can you write real software with it, perhaps a webserver?
Can it be similar in performance to servers used in industrial production?
What language should I use for Vericoding?
Yes, yes and yes! And Lean clearly viable.
October 19, 2026 at 8:57 AM
Can you write a concurrency library directly in a theorem prover?
Can you write real software with it, perhaps a webserver?
Can it be similar in performance to servers used in industrial production?
What language should I use for Vericoding?
Yes, yes and yes! And Lean clearly viable.
Can you write real software with it, perhaps a webserver?
Can it be similar in performance to servers used in industrial production?
What language should I use for Vericoding?
Yes, yes and yes! And Lean clearly viable.
A Benchmark for Vericoding: Formally Verified Program Synthesis
Ionel Emilian Chiosa, Sergiu Bursuc, Theodore Ehrenborg et al.
Action editor: Serguei Barannikov
https://openreview.net/forum?id=Zgh5kpGAm8
#vericoding #coding #benchmark
Ionel Emilian Chiosa, Sergiu Bursuc, Theodore Ehrenborg et al.
Action editor: Serguei Barannikov
https://openreview.net/forum?id=Zgh5kpGAm8
#vericoding #coding #benchmark
September 27, 2026 at 8:21 AM
A Benchmark for Vericoding: Formally Verified Program Synthesis
Ionel Emilian Chiosa, Sergiu Bursuc, Theodore Ehrenborg et al.
Action editor: Serguei Barannikov
https://openreview.net/forum?id=Zgh5kpGAm8
#vericoding #coding #benchmark
Ionel Emilian Chiosa, Sergiu Bursuc, Theodore Ehrenborg et al.
Action editor: Serguei Barannikov
https://openreview.net/forum?id=Zgh5kpGAm8
#vericoding #coding #benchmark
Open-source specification manager and Code-by-Contract developer environment to help engineers get closer to verifying code is correct.
github.com/scidonia/axi...
#Python #FormalVerification #SoftwareEngineering #AI #Vericoding #OpenSource #ModelContextProtocol #SoftwareArchitecture #DevTools
github.com/scidonia/axi...
#Python #FormalVerification #SoftwareEngineering #AI #Vericoding #OpenSource #ModelContextProtocol #SoftwareArchitecture #DevTools
GitHub - scidonia/axiomander: Code by Contract Dev Environment
Code by Contract Dev Environment. Contribute to scidonia/axiomander development by creating an account on GitHub.
github.com
September 27, 2026 at 9:47 AM
Open-source specification manager and Code-by-Contract developer environment to help engineers get closer to verifying code is correct.
github.com/scidonia/axi...
#Python #FormalVerification #SoftwareEngineering #AI #Vericoding #OpenSource #ModelContextProtocol #SoftwareArchitecture #DevTools
github.com/scidonia/axi...
#Python #FormalVerification #SoftwareEngineering #AI #Vericoding #OpenSource #ModelContextProtocol #SoftwareArchitecture #DevTools
Cheap, fast, or correct?
With AI and formal verification, you no longer have to pick just two.
We have entered the age of vericoding.
Humans write the specs, and AI + theorem provers do the rest.
Read more: scidonia.ai/blog/ai-guid...
#formalverification #vericoding
With AI and formal verification, you no longer have to pick just two.
We have entered the age of vericoding.
Humans write the specs, and AI + theorem provers do the rest.
Read more: scidonia.ai/blog/ai-guid...
#formalverification #vericoding
AI-Guided Certified Program Refinement | Scidonia
Software's core problem is knowing what it should do. AI-guided certified program refinement — vericoding — makes specification the artefact we tinker with, and lets AI guess program transformations t...
scidonia.ai
September 24, 2026 at 8:02 AM
Cheap, fast, or correct?
With AI and formal verification, you no longer have to pick just two.
We have entered the age of vericoding.
Humans write the specs, and AI + theorem provers do the rest.
Read more: scidonia.ai/blog/ai-guid...
#formalverification #vericoding
With AI and formal verification, you no longer have to pick just two.
We have entered the age of vericoding.
Humans write the specs, and AI + theorem provers do the rest.
Read more: scidonia.ai/blog/ai-guid...
#formalverification #vericoding
this is a point made by e.g. tegmark in the vericoding paper, if we wanted to send someone to the moon, we don't send a physicist that understands the three body problem really well, we have them encode their determinsitic knowledge about the problem in a large body of algorithms which we then get
September 15, 2026 at 9:17 PM
this is a point made by e.g. tegmark in the vericoding paper, if we wanted to send someone to the moon, we don't send a physicist that understands the three body problem really well, we have them encode their determinsitic knowledge about the problem in a large body of algorithms which we then get
▶️ Watch San Diego Alignment Workshop video: youtu.be/zBX7FCH3JAE&...
📄 Provably safe systems: the only path to controllable AGI - arxiv.org/abs/2309.01933
📄 A benchmark for vericoding: formally verified program synthesis - arxiv.org/abs/2509.22908
📄 Provably safe systems: the only path to controllable AGI - arxiv.org/abs/2309.01933
📄 A benchmark for vericoding: formally verified program synthesis - arxiv.org/abs/2509.22908
Max Tegmark - Provably Safe AI [Alignment Workshop]
Max Tegmark (MIT) presents vericoding as an alternative to directly deploying powerful neural networks, instead using them to generate formally verified code. His research shows significant progress:…
youtu.be
February 3, 2026 at 4:30 PM
▶️ Watch San Diego Alignment Workshop video: youtu.be/zBX7FCH3JAE&...
📄 Provably safe systems: the only path to controllable AGI - arxiv.org/abs/2309.01933
📄 A benchmark for vericoding: formally verified program synthesis - arxiv.org/abs/2509.22908
📄 Provably safe systems: the only path to controllable AGI - arxiv.org/abs/2309.01933
📄 A benchmark for vericoding: formally verified program synthesis - arxiv.org/abs/2509.22908
"It's easier to verify a proof than to find it." Max Tegmark: "It's easier to verify a proof than to find it." Vericoding has AI generate formally verified code, achieving 82% success. Superintelligent AI may be easier to verify, thus more controllable. 👇
February 3, 2026 at 4:30 PM
"It's easier to verify a proof than to find it." Max Tegmark: "It's easier to verify a proof than to find it." Vericoding has AI generate formally verified code, achieving 82% success. Superintelligent AI may be easier to verify, thus more controllable. 👇
I just came across this paper arxiv.org/abs/2509.22908 which coins the term "vericoding" for using LLMs to generate formally verified code, and presents benchmark results for several languages
January 15, 2026 at 9:52 AM
I just came across this paper arxiv.org/abs/2509.22908 which coins the term "vericoding" for using LLMs to generate formally verified code, and presents benchmark results for several languages
Bursuc, Ehrenborg, Lin, Astefanoaei, Chiosa, Kukovec, Singh, Butterley, Bizid, Dougherty, Zhao, Tan, Tegmark: A benchmark for vericoding: formally verified program synthesis https://arxiv.org/abs/2509.22908 https://arxiv.org/pdf/2509.22908 https://arxiv.org/html/2509.22908
September 30, 2025 at 6:34 AM
Bursuc, Ehrenborg, Lin, Astefanoaei, Chiosa, Kukovec, Singh, Butterley, Bizid, Dougherty, Zhao, Tan, Tegmark: A benchmark for vericoding: formally verified program synthesis https://arxiv.org/abs/2509.22908 https://arxiv.org/pdf/2509.22908 https://arxiv.org/html/2509.22908
The approach to Vericoding in axiomander in a nutshell
June 17, 2026 at 10:55 AM
The approach to Vericoding in axiomander in a nutshell
Did a survey of all LLM-based VeriCoding benchmarks
Seems like everyone's focusing on single-file programs.
Have you ever seen a REAL verified system? a file-system? a OS? the specs for every function are HUGE.
It looks nothing like your fibonacci leetcode spec. We're cooked.
Seems like everyone's focusing on single-file programs.
Have you ever seen a REAL verified system? a file-system? a OS? the specs for every function are HUGE.
It looks nothing like your fibonacci leetcode spec. We're cooked.
April 30, 2026 at 9:23 PM
Did a survey of all LLM-based VeriCoding benchmarks
Seems like everyone's focusing on single-file programs.
Have you ever seen a REAL verified system? a file-system? a OS? the specs for every function are HUGE.
It looks nothing like your fibonacci leetcode spec. We're cooked.
Seems like everyone's focusing on single-file programs.
Have you ever seen a REAL verified system? a file-system? a OS? the specs for every function are HUGE.
It looks nothing like your fibonacci leetcode spec. We're cooked.
Here’s a relevant paper evaluating LLM generation of formally verified code from specifications. They compare Dafny, Verus/Rust, and Lean code written by nine different LLMs. Seems like a promising path ahead! 🤓
arxiv.org/abs/2509.22908
arxiv.org/abs/2509.22908
A benchmark for vericoding: formally verified program synthesis
We present and test the largest benchmark for vericoding, LLM-generation of formally verified code from formal specifications - in contrast to vibe coding, which generates potentially buggy code from ...
arxiv.org
January 22, 2026 at 4:10 AM
Here’s a relevant paper evaluating LLM generation of formally verified code from specifications. They compare Dafny, Verus/Rust, and Lean code written by nine different LLMs. Seems like a promising path ahead! 🤓
arxiv.org/abs/2509.22908
arxiv.org/abs/2509.22908
Is vericoding a solution?
Maybe not.
If it is difficult to read code generated by a machine, it is much more difficult, I believe, to read a formal specification generated by a machine.
Maybe not.
If it is difficult to read code generated by a machine, it is much more difficult, I believe, to read a formal specification generated by a machine.
The problem with LLM as guarantee of correctness is one of infinite regress.
The software engineers must now validate the validation.
The software engineers must now validate the validation.
April 17, 2026 at 9:34 AM
Is vericoding a solution?
Maybe not.
If it is difficult to read code generated by a machine, it is much more difficult, I believe, to read a formal specification generated by a machine.
Maybe not.
If it is difficult to read code generated by a machine, it is much more difficult, I believe, to read a formal specification generated by a machine.
#vericoding
I hope this has the same level of success as Ariane 5
"We present and test the largest benchmark for vericoding, LLM-generation of formally verified code from formal specifications — in contrast to vibe coding, which generates potentially buggy code...."
arxiv.org/html/2509.22...
I hope this has the same level of success as Ariane 5
"We present and test the largest benchmark for vericoding, LLM-generation of formally verified code from formal specifications — in contrast to vibe coding, which generates potentially buggy code...."
arxiv.org/html/2509.22...
A benchmark for vericoding: formally verified program synthesis
arxiv.org
April 17, 2026 at 8:21 AM
#vericoding
I hope this has the same level of success as Ariane 5
"We present and test the largest benchmark for vericoding, LLM-generation of formally verified code from formal specifications — in contrast to vibe coding, which generates potentially buggy code...."
arxiv.org/html/2509.22...
I hope this has the same level of success as Ariane 5
"We present and test the largest benchmark for vericoding, LLM-generation of formally verified code from formal specifications — in contrast to vibe coding, which generates potentially buggy code...."
arxiv.org/html/2509.22...
Everyone says AI now writes production code. But 3,500 LLM-generated artifacts were just formally verified — over half broke under security prompts. We generate faster than we prove. "Vericoding" is the swing back to math.
Are you shipping code you cannot prove?
#DevTools
Are you shipping code you cannot prove?
#DevTools
August 8, 2026 at 5:05 PM
Everyone says AI now writes production code. But 3,500 LLM-generated artifacts were just formally verified — over half broke under security prompts. We generate faster than we prove. "Vericoding" is the swing back to math.
Are you shipping code you cannot prove?
#DevTools
Are you shipping code you cannot prove?
#DevTools
How much AI code is in prod that no human has read?
Our blog looks at formal verification and how you can take it step by step.
1 BDD (test concrete examples)
2 Executable Contracts (enforce Python rules)
3 Mechanised Proofs (guarantees)
Get the machine to verify code
scidonia.ai/blog/from-bd...
Our blog looks at formal verification and how you can take it step by step.
1 BDD (test concrete examples)
2 Executable Contracts (enforce Python rules)
3 Mechanised Proofs (guarantees)
Get the machine to verify code
scidonia.ai/blog/from-bd...
From Vibecoding to Vericoding: A Gradient, Not a Jump | Scidonia
You do not have to go from zero to verified in one step. You can start with Gherkin scenarios, graduate to executable contracts with specsaver, and then bring in a theorem prover when you are ready. C...
scidonia.ai
July 28, 2026 at 10:01 AM
How much AI code is in prod that no human has read?
Our blog looks at formal verification and how you can take it step by step.
1 BDD (test concrete examples)
2 Executable Contracts (enforce Python rules)
3 Mechanised Proofs (guarantees)
Get the machine to verify code
scidonia.ai/blog/from-bd...
Our blog looks at formal verification and how you can take it step by step.
1 BDD (test concrete examples)
2 Executable Contracts (enforce Python rules)
3 Mechanised Proofs (guarantees)
Get the machine to verify code
scidonia.ai/blog/from-bd...