Safe Commands Reference
Read-only and approval-gated command families for common operations.
Run commands only in the intended environment and record the result.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
Commands are grouped as read-only inspection, local service control, build/test, and approval-gated mutation. Examples use placeholders and local endpoints; production operators must follow the approved environment procedure.
| Check | Source-backed expectation |
|---|---|
| Scope | Do not turn a command example into an authorization to execute it. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | docker compose config |
| Stop condition | Unknown authorization, destructive impact, secret exposure, or conflicting evidence. |
Verification
Run the safe check, record its result, and compare the outcome with the documented contract. If the result depends on external configuration or provider availability, mark it as configuration-dependent rather than claiming a product guarantee.
docker compose config
Safety boundary
Examples are non-production and use placeholders. Do not deploy, reset, force a migration, create secrets, activate providers, replay sensitive work, or expose private data from this page.