Repeatability
High
OAuth2 token validation patterns for Google, GitHub, and Microsoft are well-established and structurally consistent. The FastAPI middleware and decorator pattern is a standard architectural problem with known solutions, making this highly repeatable.
Ambiguity Tolerance
High
Success criteria are concrete: a working decorator, centralized middleware, token refresh handling, sub-100ms overhead, and standardized error responses across 15+ endpoints. A non-human can verify these against the spec with reasonable confidence.
Data & Tool Availability
Medium
The OAuth2 provider specs and FastAPI documentation are publicly available and well-known to current models. However, the agent lacks access to the existing codebase, current route structure, and provider credentials, requiring the human to supply those or accept a greenfield implementation.
Error Cost
Medium
A flawed implementation could introduce authentication bypasses or token-handling bugs, which are serious security issues. However, the output is code that must be reviewed and tested before deployment, so errors are catchable before they reach production.
Human Judgment Required
Low
The architectural decisions here — middleware vs. dependency injection, error response schema, refresh token strategy — are standard engineering choices with well-known tradeoffs. No significant taste, ethics, or relationship judgment is needed.