What is 4 Laws of Probabilistic Software?
The 4 Laws of Probabilistic Software Development are principles coined by Richard Ewing in Built In that define the fundamental constraints of AI-generated code: **Law 1: Code generated by probability is correct by probability, not by proof.** AI-generated code may work for common cases but fail for edge cases.
The 4 Laws of Probabilistic Software Development are principles coined by Richard Ewing in Built In that define the fundamental constraints of AI-generated code:
Law 1: Code generated by probability is correct by probability, not by proof. AI-generated code may work for common cases but fail for edge cases. Unlike code written with deliberate reasoning, probabilistic code's correctness is statistical, not guaranteed.
Law 2: The confidence of the generator does not equal the correctness of the output. AI models express equal confidence whether the output is correct or hallucinated. Confidence is not a reliability signal.
Law 3: Every layer of abstraction added by AI is a layer of understanding removed from the human. As AI generates more of the system, human developers understand less of the system. This creates a fragility that compounds over time.
Law 4: The cost of AI-generated code is paid at verification time, not generation time. Generation is instant and cheap. Verification — finding the bugs, confirming correctness, validating security — is where the real cost lives. Organizations that skip verification accumulate invisible debt.
Why It Matters
These laws establish the fundamental economics of vibe coding: generation is cheap, verification is expensive, and skipping verification creates exponentially compounding technical debt.
Frequently Asked Questions
What are the 4 Laws of Probabilistic Software?
Four principles by Richard Ewing defining the constraints of AI-generated code: 1) Correctness is probabilistic, 2) Confidence ≠ correctness, 3) AI abstraction removes human understanding, 4) Real cost is verification.
Why do these laws matter?
They explain why vibe coding creates a new category of technical debt and why verification skills (not generation skills) are the scarce human capability in AI-age engineering.
Related Terms
Need Expert Help?
Richard Ewing is a Product Economist and AI Capital Auditor. He helps companies translate technical complexity into financial clarity.
Book Advisory Call →