
UX Engineer @Microsoft | creator of those easing functions | building next-gen motion & graphics tools | formal verification, Lean, Dafny, Bend2
Brooklyn, NY
Joined October 2008
- Tweets26.6K
- Following2.4K
- Followers10.4K
- Likes81.8K
Pinned Tweet
I'm building a motion curve editor beyond your wildest fantasies.
I've been head down solving new easing equations for the last 13 months.
I promise nothing less than a quantum leap in easing technology.
Robert Penner retweeted
Rewind me 6 months and tell me LemmaScript will be used to formalize and uncover bugs in XState.
I would have believed you, actually. There's a reason we built it, iterated relentlessly, and stuck with it through a dead zone.
Be like Robert. Go formalize stuff.
Replying to @robertpenner
Now I'm tackling something more ambitious: formalizing XState's runtime behavior with LemmaScript.
I started with XState's lightweight FSM, proving 31 laws governing state transitions, context updates and sequences of events.
Comparing the formally verified model against XState's implementation helped uncover two bugs, both since fixed upstream.
That led me deeper into XState's runtime. In my first week, I filed 7 bug reports involving subtle problems with transitions, event ordering and state behavior.
It's exciting to see formal verification help uncover bugs in a mature, widely used open-source library.
TypeScript isn't enough for me anymore. I want stronger guarantees that my code behaves as intended.
TypeScript catches many bugs that JavaScript misses, but its types can only go so far in specifying behavior.
I still write unit tests, but they only check specific examples, leaving gaps in coverage.
That's where formal verification shows great promise: proving that my code obeys the laws I care about for every valid input. It can uncover bugs that unit tests tend to miss.
The challenge is that TypeScript isn't exactly designed for mathematical proofs (thanks, JavaScript!).
Rewriting the logic in a proof-oriented language usually means maintaining two implementations: the real code vs. the formalized model code.
+
Now I'm tackling something more ambitious: formalizing XState's runtime behavior with LemmaScript.
I started with XState's lightweight FSM, proving 31 laws governing state transitions, context updates and sequences of events.
Comparing the formally verified model against XState's implementation helped uncover two bugs, both since fixed upstream.
That led me deeper into XState's runtime. In my first week, I filed 7 bug reports involving subtle problems with transitions, event ordering and state behavior.
It's exciting to see formal verification help uncover bugs in a mature, widely used open-source library.
Lean vs. Dafny
I've used both Lean and Dafny for formal verification. Lean is incredibly powerful, and I've used it for more advanced mathematical proofs, particularly in algebra.
But for everyday TypeScript logic, I prefer Dafny. Its familiar syntax, contracts and automated prover make it easier to specify and verify behavior without writing detailed proofs by hand.
LemmaScript supports both Lean and Dafny, so you can choose the prover that best suits your needs. I prefer Dafny for this kind of work, while keeping TypeScript as my source of truth.
Formal verification is making a comeback. It eliminates entire classes of bugs, and AI makes it practical to define laws and prove that code obeys them.
But verification grows more complex as behaviors become interconnected. I see 4 levels:
1. Constrain possible states
2. Verify individual functions
3. Verify composition of functions
4. Verify state behavior over time
Each level needs a richer spec:
1. Types: which states are representable
2. Properties: laws each function must obey for every valid input
3. Contracts: guarantees functions make to each other
4. Temporal logic: laws governing paths through state space
The higher you go, the harder it is to read a spec and say: "Yes, that's what I meant."
Our challenge now is to define new languages that bridge human intuition and machine precision.
Because an AI proof is useless if you specified the wrong thing.
Of course, formal verification goes beyond the previous 4 levels. Continuing the pattern:
5. Concurrency: verify synchronization and interference
6. Distributed systems: verify communication and failure
7. Quantitative behavior: verify timing, probability and resource limits
8. Hyperproperties: verify relationships between multiple execution histories
129
Robert Penner retweeted
Our long-term goal is scalable autoverification of all future software. A first step is out today: an executable Lean model of the Linux kernel's WireGuard handshake, derived from its C source.
We aim to prove that code is correct.
math.inc/position
Robert Penner retweeted
Since it seems that formal verification is going viral again, I might as well drop what I have been working on the side-ish for the past 2.5 weeks over weekends. here is Janus: a Lean 4 framework that formally verifies compiled Go machine code. Not the Go source, the actual arm64 and amd64 bytes the CPU runs.
I already ran on a target successfully: holiman/uint256, the 256-bit math library under go-ethereum. All 146 exported functions are proven correct on both arm64 and amd64: 293 machine-checked theorems covering arithmetic, modular math, Exp, Sqrt, parsing and JSON/SSZ/RLP encoding. Each one says: for every valid input, this machine code returns exactly what the spec says.
How it works:
1. Compile the Go code and pull the function's machine code out of the real binary.
2. Write a short, readable spec in Lean, e.g. "z = x + y mod 2^256".
3. Prove the machine code meets it, instruction by instruction, on a Lean model of the CPU.
4. Lean's kernel checks every step of the proof.
Incredibly enough it found real bugs in the library's latest releast. e.g uint256's Float64() truncates instead of rounding to the nearest value, as its documentation promises. It also turned up several places where the docs/expected behaviour and the ACTUAL behaviour disagreed.
Janus can also prove things about performance: uint256's Add executes exactly 17 instructions on both arm64 and amd64, on every call and that has an upper-bound proof/spec.
Every uint256 spec (plain Lean, one file per function): github.com/Giulio2002/fv-uin…
Full list of findings: gist.github.com/Giulio2002/0…
Code: github.com/Giulio2002/Janus
Proofs: github.com/Giulio2002/fv-uin…
Robert Penner retweeted
Claude Fable 5.2 made this 90's toy commercial
Everything you see was made with code. Animated in Python and rendered in Blender
Robert Penner retweeted
I had Opus 5.5 formalize CPython in Lean: 613,318 lines of Lean that copy Python's internals line by line, tested against the real interpreter and checked by Lean.
On the way it found real bugs in Python, including crashes from plain Python code. 🧵
The state machine renaissance
There's a renaissance happening for state machines in software development.
A prompt circulating on X this week tells coding agents to find all the implicit state machines lurking in a codebase. It's like a magic spell that brings submerged structures to the surface.
Suddenly, scattered booleans, conditional branches, and ad hoc state transitions are revealed as parts of state machines.
Once you've identified them, you can model them explicitly, constrain their transitions and eliminate entire classes of bugs.
For JavaScript and web development, XState is an excellent tool for wrangling your state into a disciplined and diagrammable structure.
From code monkeys to lawmakers
"Who am I? Why am I here?"
AI agents have largely conquered the tactics of coding. Now they're climbing the ladder of strategic decision-making. Where does that leave us software engineers?
We're actually being promoted: from code monkeys to lawmakers. Your new mission, if you choose to accept it:
Write the constitution of your codebase.
What must always be true? What must never happen? What are the inviolable laws governing this little universe we've created?
Is your code up to code?
Architects can design extraordinary buildings, but every structure must meet building codes. In agentic software development, code can be generated and rebuilt without detailed blueprints.
With AI-assisted formal verification, we can establish the code for the code: laws every implementation must obey, and proof they did.
Then you can let agents tear down walls, rebuild foundations, and construct entirely new architectures. Give them room to innovate.
Just make sure they build to code.
1
198









