When AI ships code faster than anyone can review it, velocity metrics go vertical, and code drifts rapidly and silently from the original intent, accumulating problems and vulnerabilities in its wake. The Production Drift Ratio is the first metric designed to make that cost visible.
TL;DR
- Drift is defined as the silent and accumulating gap between design intent and code output.
- AI-assisted development creates code drift faster and at greater volume than human review can catch.
- Standard velocity metrics (story points, PRs, time-to-merge) do not measure drift.
- The Production Drift Ratio (PDR) expresses drift as a number that quantifies the amount of drift weighted by how much time and effort would be required to address it.
- A PDR below 0.30 is low; above 0.70 is severe.
- AI should be used to detect and fix drift, not just generate it.
The Problem: AI Has Become a Drift Engine
Software has accepted a quiet bargain: ship faster, ship more, ship anything — and stop asking whether it's any good. AI made the trade feel free. Generate a component in thirty seconds, refactor by prompting, spin up a feature before the standup ends. The velocity charts went vertical. Underneath them, the codebases started coming apart.
This is drift — the silent and widening gap between the standard a codebase is supposed to meet and the state it's actually in. No single commit causes it; a raw hex value here, a dropped focus state there, an API call in the wrong layer, each defensible alone but corrosive together. Drift has always existed. What's new is the pace. A model that emits plausible code faster than anyone can review it is, by the same token, a drift engine. We argue that , and follow along at reweaver.ai.
Frequently Asked Questions
What causes drift in AI-generated code?
Drift occurs when small deviations from a codebase's intended standards accumulate faster than human review can catch them. No single commit causes drift — it compounds across hundreds of small decisions: a raw value here, a misplaced API call there, a focus state stripped from a component. The structural cause is that AI generation speed has outpaced the review processes designed for human-pace development.
How is the Production Drift Ratio different from code quality scores?
Traditional code quality scores measure static properties of code — test coverage, complexity, linting violations. The Production Drift Ratio measures the gap between what a codebase was specified to be and what it actually is, expressed in hours of engineering time required to close that gap. A codebase can pass every linter and still carry a high PDR if AI-generated components have drifted from the design system, accessibility requirements, or architectural standards.
What is a good Production Drift Ratio score?
A PDR below 0.30 is considered low — an amount that a normal development week absorbs without dedicated cleanup. Between 0.30 and 0.50 is moderate and worth sprint time. Above 0.50 requires dedicated remediation. Above 0.70, the codebase has substantially diverged from production readiness and represents a compounding liability.
Does the Production Drift Ratio replace code review?
No. The PDR is designed to make drift visible and quantifiable so that human review can focus on decisions that require judgment. It automates the identification of deviations with unambiguous resolutions, clearing noise so engineers and designers can focus on the architectural and design questions that cannot be pattern-matched.
What types of drift does ReWeaver AI detect?
ReWeaver AI's drift-detection engine identifies deviations across design system alignment, accessibility compliance, architectural patterns (such as business logic placed inside UI components), and production readiness standards. The engine does not require the use of an LLM — findings come from deterministic drift detection, not inference.
How does AI-assisted development create accessibility drift?
AI models generate code based on statistical patterns in training data, not on an understanding of a specific user's needs or a team's accessibility standards. As a result, AI-generated components frequently omit semantic markup, skip focus management, and miss ARIA requirements. Because these gaps ship continuously at AI-generation speed, accessibility drift accumulates faster than traditional review cycles are designed to catch.
SOCIAL SHARE CARD GENERATOR