01 / DECIDE
Architecture decision
Use it before traffic spikes, batch jobs, or agent loops can consume shared capacity.
Queue, budget, shed, and retry work by user and workload instead of allowing every request to collide at the provider edge. Map input, output, state, tools, and side effects as one observable path, then name the owner of turn rate limits into admission control.
02 / OPERATE
Three-step field procedure
- 01
Lock the contract
Write down the caller, data classification, success condition, timeout, cancellation, and ownership. Use it before traffic spikes, batch jobs, or agent loops can consume shared capacity.
- 02
Run one bounded path
Build one end-to-end path with correlation, typed state, and reversible failure handling. Queue, budget, shed, and retry work by user and workload instead of allowing every request to collide at the provider edge.
- 03
Verify the signal
Turn acceptance into a repeatable fixture, contract test, or browser test. Load tests demonstrate bounded queues, fair tenants, retry ceilings, and graceful degradation.
03 / BOUND
Operational boundary
Retries need jitter, a cap, and idempotency; never retry policy or validation failures.
04 / PROVE
Acceptance evidence
Load tests demonstrate bounded queues, fair tenants, retry ceilings, and graceful degradation.
SOURCE / HTTP
Reproducible source probe
curl -fsSI 'https://docs.x.ai/developers/faq' | sed -n '1,5p'