What does this equation mean?

Evidence formats extend today’s protocol-level convergence — MCP for tool calls, SLSA-style attestations for provenance, an SSDF-derived vocabulary for what was checked — into something that also standardizes what counts as sufficient evidence to merge without a human re-check [ 5 , 15 , 14 ] . A change vetted under one tool’s policy carries a portable record a different tool or organization can act on directly. Review capacity effectively pools across the industry instead of being rebuilt separately by every team, which is what keeps $\mu$ rising in step with $\lambda$ even as agent fleets scale. The developer’s role shifts furthest in this world: closer to the 20-percent execution share Claude Code’s usage study already measures than to the 70-percent planning share [ 4 ] , with most attention spent auditing evidence bundles rather than reading diffs line by line.