01 / DECIDE
Architecture decision
Use it when long model work exceeds an interactive connection budget.
Persist a request identifier, explicit status, expiry, cancellation, idempotent retrieval, and a user-visible terminal result. Map input, output, state, tools, and side effects as one observable path, then name the owner of represent deferred work as a job.
02 / OPERATE
Three-step field procedure
- 01
Lock the contract
Write down the caller, data classification, success condition, timeout, cancellation, and ownership. Use it when long model work exceeds an interactive connection budget.
- 02
Run one bounded path
Build one end-to-end path with correlation, typed state, and reversible failure handling. Persist a request identifier, explicit status, expiry, cancellation, idempotent retrieval, and a user-visible terminal result.
- 03
Verify the signal
Turn acceptance into a repeatable fixture, contract test, or browser test. State tests cover queued, running, completed, failed, cancelled, expired, and duplicate retrieval.
03 / BOUND
Operational boundary
Review storage and data-retention compatibility before using deferred execution with sensitive data.
04 / PROVE
Acceptance evidence
State tests cover queued, running, completed, failed, cancelled, expired, and duplicate retrieval.
SOURCE / HTTP
Reproducible source probe
curl -fsSI 'https://docs.x.ai/developers/advanced-api-usage/deferred-chat-completions' | sed -n '1,5p'