01 / DECIDE
Architecture decision
Use it when one model family serves tasks with materially different complexity and response budgets.
Route simple extraction, interactive work, and deep analysis through distinct latency, quality, and cost profiles. Map input, output, state, tools, and side effects as one observable path, then name the owner of budget reasoning by workload.
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 one model family serves tasks with materially different complexity and response budgets.
- 02
Run one bounded path
Build one end-to-end path with correlation, typed state, and reversible failure handling. Route simple extraction, interactive work, and deep analysis through distinct latency, quality, and cost profiles.
- 03
Verify the signal
Turn acceptance into a repeatable fixture, contract test, or browser test. Evals compare quality, latency, tool success, and total usage across workload profiles.
03 / BOUND
Operational boundary
More reasoning is not proof of correctness; validate the final result and hide private internal process from product contracts.
04 / PROVE
Acceptance evidence
Evals compare quality, latency, tool success, and total usage across workload profiles.
SOURCE / HTTP
Reproducible source probe
curl -fsSI 'https://docs.x.ai/developers/models' | sed -n '1,5p'