AutoCore Incident Checklists and Records
A practical incident record structure for detection through closeout.
Complete the smallest applicable checklist and link the evidence. Never use a public documentation page as the incident record or paste secrets into it.
Release candidate source
This article reflects the audited AutoCore source revision 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60 and immutable release-candidate tag v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f. Configuration and external provider behavior remain deployment-dependent.
Source boundary
| Control | Source-verified behavior |
|---|---|
| Record | Incident ID, detector, time, scope, affected edition, severity, and current owner. |
| Timeline | Detection, containment, provider communication, recovery, validation, and closeout events. |
| Decisions | What was disabled, why, by whom, with which expected risk and verification result. |
| Impact | Use approved aggregate impact measures; avoid publishing personal or financial details. |
| Closeout | Residual risk, follow-ups, owners, due dates, and whether a release or configuration change is required. |
High-risk operation
Use explicit authorization, a written reason, a confirmation gate, and post-action verification. Documentation does not grant permission to change a deployment.
Operational controls
Use the smallest verified control for the task. Keep provider, host, legal, and operator responsibilities separate from application behavior. When a control is not implemented or not verified, leave it disabled or mark it as a limitation.
Verification
Verify the route, relevant API or configuration state, negative path, audit/evidence result, and public effect before closing the task. Record unknown or configuration-dependent behavior as a limitation.