Operations Guide Overview
The operational map for installation, service health, evidence, and safe recovery.
Use evidence-backed checks and stop when the next action could mutate production state.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
Production operations span API, web, admin, worker, PostgreSQL, Redis, Meilisearch, media storage, reverse proxy, monitoring, and release artifacts. Each dependency has a distinct health and recovery boundary.
| Check | Source-backed expectation |
|---|---|
| Scope | Operations documentation is a runbook aid, not deployment authorization. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | curl -fsS https://api.example.invalid/ready |
| 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.
curl -fsS https://api.example.invalid/ready
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.