Monday, 10 a.m.: I stared at a customer’s screenshot, palms sweating

Last month, I delivered a small outsourced website. After the customer clicked “Submit order,” the page sometimes went blank. I had tested it locally ten times, and everything worked. The customer stayed calm and asked one question: “So, can you guarantee it now?” That was when I realized how fast AI could write code—and how incapable I was of identifying the hidden problem. That was also when I started learning about formal verification. It isn’t asking AI to declare, “No problem.” You write down the rules the system must follow, then make a computer prove the code follows them.

Not another code generator, but a gate before delivery

Formal verification isn’t as mysterious as it sounds. First, you describe rules such as “an order must not be charged twice” or “the amount must never be negative.” Then a tool tries to prove, using logic and mathematics, that the program always follows them. This differs from asking AI to run tests or review the code, because those approaches can still miss cases nobody thought of. Formal verification gets closer to logically ruling out specified errors.

Stanford professor Clark Barrett, a co-founder of &Truth, helped develop the cvc5 reasoning tool. Amazon uses it for specification analysis and test generation in the Kiro development environment, with billions of calls every day. Harmonic is another company in this space, while Theorem and Axiom Math are also exploring AI-assisted formal verification.

I also got this step wrong at first: seeing the words “mathematical proof,” I assumed I had to complete an entire university logic course before I could try it. Later, I realized a small team can usually start by verifying its single most critical, highest-risk rule. There’s no need to prove the entire system on day one.

What would it cost to try today?

For an individual experiment, I calculated that the replication cost could start at $0 in cash: public materials and open-source tools are enough for an initial trial. If I wanted a commercial team plan, I’d reserve about $200 per month, though I’d need to confirm the current price with the vendor.

In terms of time, choosing one business rule, preparing the verification environment, and getting a first result would take roughly 5–10 hours. The technical barrier is manageable: I need to understand the basic business rule and be willing to turn a vague requirement into an explicit “if… then…” condition. I don’t need to become a mathematics expert.

The first step isn’t installing complicated software. It’s opening the &Truth, Harmonic, or relevant open-source project website and finding the demo, trial, or documentation. If I don’t know where to begin writing rules, I can start with one scenario—duplicate order submissions must not trigger duplicate charges—and put the normal flow, failure flow, and expected result on paper.

This tool isn’t essential for everyone. If my product is tiny and the risk is low, trying it now may not be worth it; solid manual testing and a rollback plan may matter more right now.

Match the next step to my team’s size

If I’m just starting, focused on a personal brand or one-off projects, I’d skip full verification for now. I’d turn the one rule I worry about most into an acceptance checklist, have AI generate the tests, and review them manually. It’s cheaper and more realistic.

If I already have one or two paying customers, I’d choose a rule that directly affects payment, privacy, or delivery. Then I’d try a small formal verification exercise and keep side-by-side records of what looked true before and after verification.

If I’m scaling and multiple people are now changing the code, I’d add formal verification to the release checklist. Every change would include its rule-verification result, and engineers would explain anything they couldn’t prove or had temporarily excluded.

The point isn’t to pursue “proof of everything.” It’s to let the team know which critical promises have actually been checked—and which ones we’re still merely trusting. I’m still mapping the boundaries, and I’ll keep recording the real time, costs, and mistakes.