Installation Operations
Preflight, installation locking, first administrator, and verification.
Complete preflight and retain the installation manifest before handing over an environment.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
Installation is explicit, repeatable, and installation-scoped. Verify domain/TLS, service reachability, database schema, cache/search dependencies, storage, email, and legal configuration without publishing secrets.
| Check | Source-backed expectation |
|---|---|
| Scope | If installation identity or lock state is ambiguous, stop and escalate. |
| 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.