Health and Readiness Operations
Interpreting probes, version identity, and dependency readiness.
Check process health, readiness, dependency state, and user-facing effect separately.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
/health and /ready are unversioned. Health and readiness evidence should include release identity, timestamp, route, status, and request ID where applicable; it should not include secrets or raw dependency credentials.
| Check | Source-backed expectation |
|---|---|
| Scope | Green probes do not prove search relevance, media delivery, payment settlement, or legal readiness. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | curl -i 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 -i 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.