01 / DECIDE
Architecture decision
Use it when documents or media must be referenced by later API operations.
Track owner, purpose, content type, processing state, retention, expiry, derived indexes, and deletion. Map input, output, state, tools, and side effects as one observable path, then name the owner of give uploaded files a lifecycle.
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 documents or media must be referenced by later API operations.
- 02
Run one bounded path
Build one end-to-end path with correlation, typed state, and reversible failure handling. Track owner, purpose, content type, processing state, retention, expiry, derived indexes, and deletion.
- 03
Verify the signal
Turn acceptance into a repeatable fixture, contract test, or browser test. Lifecycle tests cover upload, processing, reject, expire, delete, unauthorized access, and orphan cleanup.
03 / BOUND
Operational boundary
Validate type and size, avoid public exposure, and make deletion propagate to every dependent resource.
04 / PROVE
Acceptance evidence
Lifecycle tests cover upload, processing, reject, expire, delete, unauthorized access, and orphan cleanup.
SOURCE / HTTP
Reproducible source probe
curl -fsSI 'https://docs.x.ai/developers/advanced-api-usage/files' | sed -n '1,5p'