01 / DECIDE
Architecture decision
Use least-privilege profiles for inspection, routine edits, automation, and trusted maintenance.
Permissions decide which calls may run; the sandbox limits filesystem and network impact after a call is approved. Map input, output, state, tools, and side effects as one observable path, then name the owner of separate permission from sandbox enforcement.
02 / OPERATE
Three-step field procedure
- 01
Lock the contract
Write down the caller, data classification, success condition, timeout, cancellation, and ownership. Use least-privilege profiles for inspection, routine edits, automation, and trusted maintenance.
- 02
Run one bounded path
Build one end-to-end path with correlation, typed state, and reversible failure handling. Permissions decide which calls may run; the sandbox limits filesystem and network impact after a call is approved.
- 03
Verify the signal
Turn acceptance into a repeatable fixture, contract test, or browser test. Policy tests prove denied commands, paths, and networks remain blocked across interactive and headless modes.
03 / BOUND
Operational boundary
Always-approve does not remove deny rules, hooks, or the need for a sandbox; explicit allow rules carry real authority.
04 / PROVE
Acceptance evidence
Policy tests prove denied commands, paths, and networks remain blocked across interactive and headless modes.
SOURCE / HTTP
Reproducible source probe
curl -fsSI 'https://docs.x.ai/build/features/permissions' | sed -n '1,5p'