The 4 Laws of Probabilistic Software
Four foundational laws governing the behavior, economics, and maintenance of AI-generated code. Law 1: AI code is probabilistic, not deterministic. Law 2: Complexity scales non-linearly with AI assistance. Law 3: The verification cost of AI code exceeds the generation cost. Law 4: AI-generated code accumulates debt faster than human-written code. These laws, coined in Built In, form the baseline for managing modern, AI-augmented engineering teams.
“We have automated the typing, but we have not automated the thinking.”
The industry is treating AI-generated code as a free lunch, assuming that faster code generation strictly equates to higher productivity. The 4 Laws establish that the physics of software engineering have changed. Because the code is probabilistic, it introduces subtle, compounding errors that require massive human oversight. Ignoring these laws leads directly to the negative-carry code crisis, where systems become unmaintainable due to the sheer volume of unverified, machine-generated complexity.
Multi-Hop Causal Traversal Engine
Explore how concepts dynamically feed into each other across 1-hop, 2-hop, and 3-hop transitive relationships. Click any node to navigate the causal highway.
The 4 Laws of Probabilistic Software
Four foundational laws governing the behavior, economics, and maintenance of AI-generated code. Law 1: AI code is probabilistic, not deterministic. Law 2: Complexity scales non-linearly with AI assistance. Law 3: The verification cost of AI code exceeds the generation cost. Law 4: AI-generated code accumulates debt faster than human-written code. These laws, coined in Built In, form the baseline for managing modern, AI-augmented engineering teams.
Direct Relationships (6)
Transitive Neighbors (Connected via Hop 1)
Extended Causal Ripple Effects
Richard Ewing’s Research Thesis
Embrace AI generation, but govern it with ruthless, deterministic verification.
Why This Specification Exists
Engineering teams are blindly accepting AI-generated code and accumulating massive technical debt.
Treating AI tools as standard IDE autocomplete features.
No fundamental principles defining the unique economic and structural reality of probabilistic code.
Four laws that clarify the necessary operational shift for AI-augmented teams.
What Changes If You Believe This?
Processes shift focus from writing code to reading, reviewing, and testing code.
Accounts for the verification tax when forecasting engineering bandwidth.
Adjusts release expectations acknowledging the verification bottleneck.
Implements stricter scanning on AI-generated pull requests.
Recommended Action by Role
Enforce deterministic governance boundaries across all code generation tools because the verification cost of AI code inevitably exceeds its generation cost.
Build automated verification gates that treat AI-generated code as untrusted input requiring rigorous regression testing.
Adjust release timelines to account for the human verification bottleneck instead of assuming AI coding tools double delivery speed.
Train engineers to spend their time reviewing architectural boundaries and failure modes rather than generating untyped vibe code.
Latest Publications & Research Activity
The Engineering Bottleneck Illusion: What Copilot Adoption Taught Us
Typing code was never the primary constraint in software engineering. When enterprises deploy AI coding assistants like GitHub Copilot, they do not eliminate system bottlenecks, but shift them downstream into code review traffic jams, security and architectural drift, and staging validation delays. To capture real economic ROI, engineering leaders must measure deployment lead time, review cycle time, and defect escape rate, bounded by automated runtime allowlists and deterministic state checks.
Cursor vs Google Antigravity for Production AI Building
Examining the operational shift from unconstrained conversational AI coding assistants (like Early Cursor) to structured development environments (Google Antigravity). By enforcing immutable root rule files, modular step-by-step execution, and terminal-level zero-trust type verification, context loss incidents dropped by over 90% and debugging overhead was reduced from hours to minutes during the production engineering of Exogram.ai and CareerWin.ai.
Most Companies Shouldn’t Be Using Autonomous Coding Agents Yet
The technology is getting ahead of the environments we are putting it in. Autonomous coding agents operating in shared environments create investigation and cleanup bottlenecks that erase productivity. Before increasing agent autonomy, engineering teams must establish strict boundary controls, autonomous verification loops, and failure recovery harnesses.
The AI Coding Tool Battle Is Moving Somewhere More Important Than Code
As foundation models become hot-swappable commodities (exemplified by GitHub retiring six older Copilot models), developer tool competition shifts to the surrounding execution harness. The true economic value of an AI coding platform is defined by environment pre-provisioning, recovery mechanisms, and making failure cheap rather than raw autocomplete benchmark velocity.
Frequently Asked Questions
Q:Why does AI code accumulate debt faster?
AI often generates verbose, locally-optimized code that lacks systemic architectural awareness, leading to fragmentation and duplicate logic over time.
Q:What does probabilistic mean in this context?
It means the same prompt can yield different code on different days, removing the predictable, mechanical certainty traditional engineers rely upon.
Canonical Specification Origin
Embrace AI generation, but govern it with ruthless, deterministic verification.
Corpus Interconnections
Richard Ewing artifacts developed around this canonical framework, including publications, execution tools, and diagnostic models.
External Adoption & Peer Citations
Documented instances where independent researchers, engineering teams, and publications have cited, implemented, or referenced this concept outside Richard Ewing’s ecosystem.
External Evidence: No independently verified references recorded yet.
This concept is part of Richard Ewing’s original baseline canon. External citations and implementations are added only upon rigorous empirical verification.
Inspectable Evidence Ledger
Classified evidence items supporting, extending, or refining this canonical research specification.
| Evidence Item | Publisher | Evidence Type | Strength | Role | Action |
|---|---|---|---|---|---|
| The Negative-Carry Code Crisis | Beehiiv | Newsletter | ★★★★★ | Origin | Inspect ↗ |
| The Vibe Coding Era | Built In | Industry Article | ★★★★ | Supports | Inspect ↗ |
| The Copilot Bottleneck | CIO.com | Tier-1 Article | ★★★★★ | Extends | Inspect ↗ |
| Model Collapse | CIO.com | Tier-1 Article | ★★★★ | Extends | Inspect ↗ |
| The Engineering Bottleneck Illusion: What Copilot Adoption Taught Us | Newsletter | ★★★★★ | Extends | Inspect ↗ | |
| Cursor vs Google Antigravity for Production AI Building | Beehiiv | Executable | ★★★★★ | Supports | Inspect ↗ |
| Most Companies Shouldn’t Be Using Autonomous Coding Agents Yet | Executable | ★★★★★ | Supports | Inspect ↗ | |
| The AI Coding Tool Battle Is Moving Somewhere More Important Than Code | Beehiiv | Executable | ★★★★★ | Supports | Inspect ↗ |
| How Does Meta’s Muse Code Compare to Other AI Coding Tools? | Built In | Executable | ★★★★★ | Supports | Inspect ↗ |
| I Used AI to Build My Startup. Here’s What I Learned. | Built In | Executable | ★★★★★ | Supports | Inspect ↗ |
| I Used AI to Build My Startup. Here’s What I Learned. | Built In | Executable | ★★★★★ | Supports | Inspect ↗ |
| In the Vibe Coding Era, What Does a Software Engineer Even Do? | Built In | Evergreen | ★★★★★ | Supports | Inspect ↗ |
Recommended Citation
Ewing, R. (2026). "The 4 Laws of Probabilistic Software." Richard Ewing Research Canon. Available at: https://www.richardewing.io/concepts/four-laws-probabilistic-software
@article{ewing_four_laws_probabilistic_software,
author = {Ewing, Richard},
title = {The 4 Laws of Probabilistic Software},
journal = {Richard Ewing Research Canon},
year = {2026},
url = {https://www.richardewing.io/concepts/four-laws-probabilistic-software}
}