loading…

Releasable Patch Rate

The Releasable Patch Rate is the north-star factory metric for autonomous and AI-assisted software engineering. It measures the fraction of generated changes that satisfy every necessary quality, security, architectural, and operational gate required for production release.

flowchart TD
    G[Candidate Patch] --> C1{Correctness}
    C1 -->|Pass| C2{Regression Safety}
    C1 -->|Fail| F[Rejected / Rework]
    C2 -->|Pass| C3{Security Baseline}
    C2 -->|Fail| F
    C3 -->|Pass| C4{Architecture Conformance}
    C3 -->|Fail| F
    C4 -->|Pass| C5{Scope Authorization}
    C4 -->|Fail| F
    C5 -->|Pass| R[Releasable Patch]

The Multiplicative Reliability Law

Quality is not a scalar average; it is a vector of orthogonal constraints that multiply at the release boundary:

$$\text{Releasable Patch Rate} = P(\text{Correctness} \land \text{Regression Safety} \land \text{Security} \land \text{Architecture} \land \text{Scope})$$

A patch that achieves 100% test coverage and passes linting but leaks an API credential or exceeds its authorized file allowlist is 0% releasable. Averaging metrics hides catastrophic tail risks.

High-Leverage Metrics vs. Vanity Proxies

Dimension	Reliable Metric	Distrusted / Poison Proxy
Factory Throughput	Releasable patches per dollar / hour	Lines of Code (LOC) generated
Delivery Success	Escaped defect rate & rollback frequency	Merge rate & PR count
Review Efficiency	Actionable findings per reviewer minute	Review comment count
Verification Strength	Mutation score & differential assertion passes	Raw line coverage percentage
Scope Discipline	Touched paths within declared allowlist	“Task Complete” self-report

Mitigating the Orchestration Tax

When raw code generation outpaces downstream human review and verification bandwidth, organizations experience the orchestration tax. Increasing agent concurrency without scaling independent oracles reduces overall software delivery throughput and stability.

---

Related Concepts

• agentic code quality — The risk-conditioned control architecture.
• agentic software factory — Operating models for autonomous development at scale.
• five debts of agentic engineering — Debt categories that reduce patch releasability.
• conformance suites as fitness functions — Deterministic fitness functions for autonomous loops.