01 / DECIDE
Architecture decision
Use it whenever model, endpoint, pricing, limits, or tool behavior can change independently of application code.
Record source date, active assumptions, pinned identifiers, migration owner, tests, and rollback for every volatile dependency. Map input, output, state, tools, and side effects as one observable path, then name the owner of maintain a release and deprecation ledger.
02 / OPERATE
Three-step field procedure
- 01
Lock the contract
Write down the caller, data classification, success condition, timeout, cancellation, and ownership. Use it whenever model, endpoint, pricing, limits, or tool behavior can change independently of application code.
- 02
Run one bounded path
Build one end-to-end path with correlation, typed state, and reversible failure handling. Record source date, active assumptions, pinned identifiers, migration owner, tests, and rollback for every volatile dependency.
- 03
Verify the signal
Turn acceptance into a repeatable fixture, contract test, or browser test. Scheduled review links each live assumption to an official page and an executable regression check.
03 / BOUND
Operational boundary
A changelog is evidence, not automatic authorization to upgrade production.
04 / PROVE
Acceptance evidence
Scheduled review links each live assumption to an official page and an executable regression check.
SOURCE / HTTP
Reproducible source probe
curl -fsSI 'https://docs.x.ai/developers/release-notes' | sed -n '1,5p'