01 / DECIDE
Architecture decision
Use it when fast, deep, visual, and coding workloads have different requirements.
Describe modality, tool support, latency, quality, context, and budget, then resolve the profile to a current model in configuration. Map input, output, state, tools, and side effects as one observable path, then name the owner of route by capability profile.
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 fast, deep, visual, and coding workloads have different requirements.
- 02
Run one bounded path
Build one end-to-end path with correlation, typed state, and reversible failure handling. Describe modality, tool support, latency, quality, context, and budget, then resolve the profile to a current model in configuration.
- 03
Verify the signal
Turn acceptance into a repeatable fixture, contract test, or browser test. A route change passes task-specific evals and records quality, latency, tools, and usage.
03 / BOUND
Operational boundary
Catalog names and availability change; keep identifiers out of domain logic and preserve rollback.
04 / PROVE
Acceptance evidence
A route change passes task-specific evals and records quality, latency, tools, and usage.
SOURCE / HTTP
Reproducible source probe
curl -fsSI 'https://docs.x.ai/developers/models' | sed -n '1,5p'