Engineering
Agent Finder and ARD: Engineering Governance Guide
Published June 17, 2026 by Dillip Chowdary
Agent Finder and ARD becoming generally available gives engineering organizations a stronger control plane for agentic development. Discovery and routing are useful only when they are tied to repository policy and measurable outcomes.
The rollout should answer a practical question: which agent should handle which task, in which repository, under which review gates?
Governance Checklist
- Agent catalog: Maintain approved agents with owner, scope, and supported task types.
- Repository sensitivity: Block or restrict agents in regulated, security-critical, and deployment repositories.
- Routing policy: Map task classes to allowed agents and required reviewers.
- Telemetry: Track accepted patches, failed checks, review comments, and rollback rate.
Review Controls
Keep CODEOWNERS, branch protections, required checks, and security scanning in place. Agent routing should speed work discovery, not weaken merge standards.
Rollback Criteria
Disable an agent route when it increases review load, repeatedly fails CI, touches prohibited files, or lacks a clear owner for remediation.