Troubleshooting Checklists
Ready-to-use checklists for triage, escalation, recovery, and closure.
Close only when verification evidence and residual risk are recorded.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
The checklist covers symptom, scope, source/release identity, dependency state, safe tests, approvals, action owner, verification, user impact, and follow-up documentation. It complements the operations decision matrices.
| Check | Source-backed expectation |
|---|---|
| Scope | A resolved symptom without a verified cause remains an open follow-up. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | git status --short |
| 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.
git status --short
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.