01 / DECIDE
Architecture decision
Use it for new integrations that need state, agentic tools, or multi-step responses.
Typed output items and native server tools make messages, reasoning, searches, code, and function calls observable in one request contract. Map input, output, state, tools, and side effects as one observable path, then name the owner of use responses for stateful agentic work.
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 new integrations that need state, agentic tools, or multi-step responses.
- 02
Run one bounded path
Build one end-to-end path with correlation, typed state, and reversible failure handling. Typed output items and native server tools make messages, reasoning, searches, code, and function calls observable in one request contract.
- 03
Verify the signal
Turn acceptance into a repeatable fixture, contract test, or browser test. Contract tests parse every item type, refusal, incomplete output, tool result, and terminal state.
03 / BOUND
Operational boundary
Select storage and deletion intentionally; provider state is not your product database.
04 / PROVE
Acceptance evidence
Contract tests parse every item type, refusal, incomplete output, tool result, and terminal state.
SOURCE / HTTP
Reproducible source probe
curl -fsSI 'https://docs.x.ai/developers/model-capabilities/text/comparison' | sed -n '1,5p'