01 / DECIDE
Architecture decision
Use it for any feature whose generated text enters a UI, workflow, or stored record.
Define instructions, user input, expected output, terminal states, and retention instead of exposing a raw completion throughout the app. Map input, output, state, tools, and side effects as one observable path, then name the owner of treat text generation as a typed product contract.
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 any feature whose generated text enters a UI, workflow, or stored record.
- 02
Run one bounded path
Build one end-to-end path with correlation, typed state, and reversible failure handling. Define instructions, user input, expected output, terminal states, and retention instead of exposing a raw completion throughout the app.
- 03
Verify the signal
Turn acceptance into a repeatable fixture, contract test, or browser test. Fixtures cover success, refusal, empty output, truncation, timeout, and policy rejection.
03 / BOUND
Operational boundary
Generated prose can be incomplete or wrong; consequential facts and actions require independent validation.
04 / PROVE
Acceptance evidence
Fixtures cover success, refusal, empty output, truncation, timeout, and policy rejection.
SOURCE / HTTP
Reproducible source probe
curl -fsSI 'https://docs.x.ai/developers/model-capabilities/text/generate-text' | sed -n '1,5p'