01 / DECIDE
Architecture decision
Use it when models, permissions, plugins, MCP servers, hooks, or enterprise policy differ by scope.
Environment, user, project, managed, and requirements scopes can contribute settings; effective state must be visible for the current directory. Map input, output, state, tools, and side effects as one observable path, then name the owner of inspect effective configuration before trusting it.
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 models, permissions, plugins, MCP servers, hooks, or enterprise policy differ by scope.
- 02
Run one bounded path
Build one end-to-end path with correlation, typed state, and reversible failure handling. Environment, user, project, managed, and requirements scopes can contribute settings; effective state must be visible for the current directory.
- 03
Verify the signal
Turn acceptance into a repeatable fixture, contract test, or browser test. An inspect artifact records sources, merged values, disabled extensions, and policy locks for review.
03 / BOUND
Operational boundary
Configuration files must not contain secrets, and a project cannot silently grant itself unrestricted user authority.
04 / PROVE
Acceptance evidence
An inspect artifact records sources, merged values, disabled extensions, and policy locks for review.
SOURCE / HTTP
Reproducible source probe
curl -fsSI 'https://docs.x.ai/build/settings' | sed -n '1,5p'