SLAs for Agent Teams

Treat your roster like a team with an SLA. Define expected throughput (e.g., "a planner+builder+reviewer cycle completes in under 15 minutes 95% of the time"). Define quality (e.g., "reviewer-approved diffs need rework after merge less than 5% of the time"). Define cost ("average run cost stays under $4"). Track all three and treat regressions as incidents.

Without SLAs, agent teams drift. With them, you have a forcing function for the same engineering rigor you apply to services.