# Closure review checklist

<!-- ASSURED Methodology by Timothy Zilber, © Block, Inc., CC BY 4.0
     (https://creativecommons.org/licenses/by/4.0/). Reuse and adapt freely
     with attribution; note any changes you make.
     Template version: 2.0
     ASSURED documentation standards: the closure review
     (https://assured-methodology.vercel.app/docs/documentation/standards#closure-review).
     Every record ends in a closure review, and a review only calibrates the
     team if every reviewer checks the same things. The reviewer is not the
     record's author. Where this list and the standards page differ in
     wording, the standards page is the reference. -->

- Case ID:
- Record reviewed (event report / alert report / pattern-close record), and
  its author:
- Reviewer:
- Reviewed at (UTC):

## Checklist

<!-- Tick a box only when the record meets it as written. For every box left
     open, write one line under Findings naming the section and what is
     missing. -->

- [ ] The decision header is complete: verdict on both axes in the fixed vocabulary, the Escalation decision with who made it and when, priority with its matrix cell or override, and a bottom line a non-technical reader can follow
- [ ] Every factual claim cites its source: a query and time range, a log record ID, or an artifact hash
- [ ] Confidence is labeled per claim on the shared rubric, not once for the case
- [ ] Negative findings are recorded with what was examined, not just "nothing found"
- [ ] The timeline is in UTC with the date, and each entry has an actor, rationale, and outcome
- [ ] Every open question from the handoff packet is resolved in section 2 or 3, or carried into section 8
- [ ] Every indicator and observable has a disposition (malicious, suspicious, or known-good)
- [ ] Shared and training versions are sanitized, and people are written about neutrally
- [ ] Material AI use is declared, "none" included
- [ ] Benign and authorized closes state their reopen conditions

## Findings

-

## Outcome

- Outcome (accept / request clarification / flag as a training case):
- Clarification requested from (author), due by (UTC), and resolved at (UTC):
- Training-case note (what the case teaches, in one line; optional):