01 / DECIDE
Architecture decision
Use it for offline evaluation, enrichment, media jobs, or high-volume work without interactive latency.
Use immutable input manifests, stable custom IDs, per-item status, bounded replay, and an explicit partial-result policy. Map input, output, state, tools, and side effects as one observable path, then name the owner of reconcile every batch item.
02 / OPERATE
Three-step field procedure
- 01
Lock the contract
Write down the caller, data classification, success condition, timeout, cancellation, and ownership. Use it for offline evaluation, enrichment, media jobs, or high-volume work without interactive latency.
- 02
Run one bounded path
Build one end-to-end path with correlation, typed state, and reversible failure handling. Use immutable input manifests, stable custom IDs, per-item status, bounded replay, and an explicit partial-result policy.
- 03
Verify the signal
Turn acceptance into a repeatable fixture, contract test, or browser test. Reconciliation proves there is no silent loss and every input has one terminal disposition.
03 / BOUND
Operational boundary
Limit sensitive datasets, define expiry, and download time-limited media results promptly when applicable.
04 / PROVE
Acceptance evidence
Reconciliation proves there is no silent loss and every input has one terminal disposition.
SOURCE / HTTP
Reproducible source probe
curl -fsSI 'https://docs.x.ai/developers/advanced-api-usage/batch-api' | sed -n '1,5p'