Operations
Production Error Sweep
Turn recurring production errors into verified patches.
Use when
Production telemetry should become repairs, not vibes.
Cadence
Daily or after incident
Verification
Actionable errors are fixed with reproduction or tests, or explicitly classified as noise.
Structured loop spec
| Field | Value |
|---|---|
| Name | Production Error Sweep |
| Category | Operations |
| Trigger | Daily or after incident |
| Objective | Turn recurring production errors into verified patches. |
| 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 | Actionable errors are fixed with reproduction or tests, or explicitly classified as noise. |
| 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 | Draft, report, checklist, table, or approval-gated recommendation |
| Works with | Claude, ChatGPT, Gemini, any tool-using AI assistant |
Steps
- 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.
Prompt
Run the Production Error Sweep loop. Use it when Production telemetry should become repairs, not vibes. Work in bounded iterations: inspect current state, choose the highest-risk gap, make one reversible improvement, verify it, and record evidence. Stop when Actionable errors are fixed with reproduction or tests, or explicitly classified as noise. or when blocked, budget exhausted, or approval is required.Run in Claude Code
Paste this into Claude Code (or any tool-using agent) to run the loop bounded: one change per round, the same verification every round, durable state files, and explicit stop conditions.
Run the "Production Error Sweep" loop from AI Loop Library (https://ailooplibrary.com/loops/production-error-sweep/) as a bounded loop.
Goal: Turn recurring production errors into verified patches.
Rules: one change per round; run the same verification every round (Actionable errors are fixed with reproduction or tests, or explicitly classified as noise.); append each round to docs/loops/production-error-sweep/progress.md and update docs/loops/production-error-sweep/state.json; stop on verifier pass, 8 rounds, 3 consecutive failed verifications, no progress, a blocker, or anything needing human approval (money, production, outbound, deletion). Finish with a proof report: rounds used, changes made, verification output, remaining risk, and the next human decision.