Engineering
API Contract Drift
Find where the API contract forked and bring every consumer back to one truth.
Use when
Backend, frontend, docs, and SDKs may describe different realities.
Cadence
After API changes or SDK releases
Verification
Server behavior, client types, examples, and docs agree on request/response contracts.
Advanced specStructured loop spec
| Field | Value |
|---|---|
| Name | API Contract Drift |
| Category | Engineering |
| Trigger | After API changes or SDK releases |
| Objective | Find where the API contract forked and bring every consumer back to one truth. |
| Allowed inputs | Relevant files, source notes, logs, tests, screenshots, metrics, or task state for this loop |
| Allowed actions | Define the exact scope, source of truth, and approval boundary.; Inspect current state and rank the highest-risk gap.; Make one small, reversible improvement.; Run the stated verification and record evidence.; Stop on success, budget, no progress, or approval required. |
| Verification | Server behavior, client types, examples, and docs agree on request/response contracts. |
| Stop condition | Stop when the verifier passes, the budget is exhausted, no progress is made, a blocker appears, or approval is required. |
| Budget | Set a time, turn, token, retry, file, or dollar cap before running the loop. |
| Approval boundary | Human approval required before publishing, sending, deleting, spending, changing accounts, touching production, or making reputational/legal/financial commitments. |
| Safe output | Pull request, patch, report, or evidence log |
| Works with | Claude Code, OpenAI Codex, Cursor, Gemini CLI, any tool-using coding agent |
RunbookSteps
- Define the exact scope, source of truth, and approval boundary.
- Inspect current state and rank the highest-risk gap.
- Make one small, reversible improvement.
- Run the stated verification and record evidence.
- Stop on success, budget, no progress, or approval required.
Copy promptPrompt
Run the API Contract Drift loop. Use it when Backend, frontend, docs, and SDKs may describe different realities. Work in bounded iterations: inspect current state, choose the highest-risk gap, make one reversible improvement, verify it, and record evidence. Stop when Server behavior, client types, examples, and docs agree on request/response contracts. or when blocked, budget exhausted, or approval is required.