Handle transient failure
Add bounded retries and backoff without blocking unrelated work.
Can you separate retryable from terminal failure?Preparing this page…
Your current navigation and account state stay available while the next page loads.
Preparing this page…
Your current navigation and account state stay available while the next page loads.
Review staged prompts that begin with a small in-memory worker, then introduce retries, duplication, cancellation, and process restarts. This independent, original scenario is designed for ML / Inference Systems, Agents / Evals, Software / Infrastructure preparation. Work through the stages in order, explain each decision, and use the review dimensions to test whether the result remains defensible when constraints change.
Add bounded retries and backoff without blocking unrelated work.
Can you separate retryable from terminal failure?Protect downstream systems when jobs are delivered more than once.
Can you reason honestly about at-least-once execution?Replace volatile assumptions with a durable state and lease model.
Can you preserve correctness across process boundaries?Use these checks after a first draft. They are review prompts, not six more questions to answer.
Clarifies goals, constraints, and ambiguous requirements.
Protects invariants and handles boundary conditions.
Identifies realistic failures and designs recovery paths.
Makes ownership and transitions explicit.
Provides enough visibility to diagnose and run the system.
Explains what is gained, lost, and intentionally deferred.
Use a different system, project, or situation and check whether the structure still produces a specific, defensible answer.