# Investigate an application incident — acceptance checklist

Record evidence for every checked item. Unchecked or untested is not a pass. This checklist does not execute an integration or authorise external actions.

## Required inputs

- [ ] An incident window and affected environment.

- [ ] Redacted event identifiers, logs and recent change context.

- [ ] A concrete symptom and a usable reproduction environment for the debugging agent; record the gap if either is unavailable.

## Output checks

- [ ] Every event uses a recorded time zone and the affected environment is unambiguous.

- [ ] Observed events are separated from inferred causes.

- [ ] The proposed fix explains the original symptom and contradictory evidence is retained.

- [ ] Recovery checks preserve command exit status; deployment and incident closure remain separate decisions.

## Deliverables

- [ ] Timestamped incident timeline

- [ ] Competing-hypothesis ledger

- [ ] Minimal reproduction or stated gap

- [ ] Recovery verification plan

## Evidence and decision

Evidence links: [fill in]
Untested paths: [fill in]
Unresolved findings: [fill in]
Reviewer: [fill in]
Decision and scope: [fill in]

## Boundaries

- Choose a host for each stage and verify its tool mapping. Pass evidence explicitly between stages; the listed resources do not automatically configure or invoke one another.

- Configure Sentry access and the definition’s tool mapping separately. Record adapter and self-hosted feature limits before treating an event set as complete.

- Do not resolve issues, change alerts, edit production or publish incident data during the evidence-gathering pass.

Workflow: https://undominated.ai/workflows/#investigate-an-incident