Formula
AGVR = (agent-authored PRs merged
with no completed
CDA audit
÷ total agent-authored
PRs merged)
× 100Thresholds
No bypass — governed
Target stateBypass detected
Alert — investigate immediatelySystematic bypass
Red — enforce branch protectionReading it
AGVR is not about code quality — it is about process integrity. A non-zero AGVR means the CDA enforcement layer can be circumvented, intentionally or accidentally, by agent workflows. The audit gate that every agent-authored PR is supposed to pass through was bypassed: the PR merged without a completed CDA audit event ever being recorded.
This metric is especially critical because agents merge PRs at high velocity. A process gap that would be rare at human scale — one missed review in a quarter — becomes frequent at agent scale, where dozens of PRs may merge per day. A 5% bypass rate that seems minor in isolation translates to hundreds of unreviewed agent PRs per year entering the main branch.
AGVR should be structurally zero in a well-configured repository. The target is not near-zero — it is zero. Any non-zero value is a signal that the enforcement layer has a gap: a misconfigured webhook, a missing branch protection rule, or a repository that was connected to rkito after agent workflows were already active. Each gap is diagnosable and fixable. The metric exists to surface them before they become a pattern.
How rkito produces it
AGVR is detected by correlating merge events with CDA pipeline completion events. Agent authorship is identified from commit signatures and MCP logs. A merge with no associated COMPLETED audit record increments AGVR. Every such PR is individually flagged for retroactive review.
- 01
PR merge event received via GitHub webhook
rkito records the merge timestamp, branch, and commit metadata
- 02
Agent authorship determined
Commit signatures (Co-Authored-By: Claude Code, Copilot metadata, Devin session ID) and MCP server access logs are checked
- 03
CDA audit completion event looked up for the PR
rkito checks whether a COMPLETED CDA audit event was recorded before or at merge time
- 04AGVR++
Agent-authored + no COMPLETED audit event found
AGVR increments — governance bypass confirmed, PR flagged for retroactive review
- 05GOVERNED
Agent-authored + COMPLETED audit event present
Governed merge — not counted in AGVR
- 06
AGVR computed as percentage of bypassed agent merges
Updated on each merge event and surfaced on the org dashboard
Who reads it
Any non-zero AGVR means AI-generated code is entering production without architectural review. This is not a code quality finding — it is a structural risk signal. The governance process that is supposed to gate every agent PR was bypassed. At high agent velocity, even a small bypass rate compounds into a significant unreviewed change surface.
AGVR > 0 means security-relevant agent code may have merged without Lens evaluation. This is an audit finding, not just a metric alert. Each bypassed PR is a potential unreviewed security-relevant structural change. In a regulated environment, a non-zero AGVR requires documented retroactive review of every flagged PR.
How it misleads
What to do at each threshold
Step-by-step response playbook for each signal state.
The correct state. Every agent-authored PR that merged had a completed CDA audit on record.
- Monitor that webhook delivery remains healthy at
/settings/integrations. A healthy AGVR of zero is contingent on reliable webhook delivery — a silent webhook failure is the most common path from zero to non-zero. - Confirm branch protection rules are enforced on all repositories with active agent workflows — not just the ones you know about. A repository added to an agent workflow without a corresponding rkito connection will not appear in AGVR at all; it will appear as a coverage gap in ABR instead.
At least one agent-authored PR merged without a completed CDA audit. Determine the root cause before the next merge window.
- For each bypassed PR, determine the root cause from three possibilities: webhook failure (configuration issue — fix webhook and verify delivery), force-merge (process gap — enforce branch protection rules to prevent future force-merges), or repository not connected (coverage gap — connect the repository to rkito immediately).
- Every bypassed PR requires a retroactive CDA review regardless of root cause. The review determines whether ungoverned architectural changes were introduced. Do not close the bypass finding without a completed retroactive audit on record.
Systematic bypass in progress. More than two percent of agent merges are reaching main without governance review.
- Audit all recent agent-authored merges — not just the flagged ones. A systematic bypass pattern often indicates a configuration problem that has been active longer than the current AGVR window reflects.
- Enforce branch protection rules requiring the
rkito/cdastatus check to pass before merge. Review GitHub repository settings to confirm the status check is required, not optional — an optional status check can be bypassed by merging while the check is pending or not yet triggered.