# Review worksheet

Use one entry per supported finding. Keep entries as short as the evidence
allows. File locations refer to the code under review, not to this worksheet.

## Finding

- **Title and impact:** What fails, and how seriously does it affect the user?
- **Location:** File and line or symbol; include the relevant caller if needed.
- **Contract:** Which requested or documented behavior is violated?
- **Trigger:** Initial state and the shortest relevant sequence of actions.
- **Result:** Expected behavior, actual or predicted behavior, user consequence.
- **Cause:** The code path connecting that trigger to that result.
- **Evidence:** Executed, source-traced, or unresolved. Name the test, observation,
  code path or primary reference that supports the assessment.
- **Correction:** The smallest change that restores the contract.
- **Next check:** A targeted verification for the correction or an untested risk.

## Evidence labels

**Executed:** The relevant behavior was exercised. Record the command or flow,
configuration and result. A build alone does not establish interaction behavior.

**Source-traced:** The relevant callers and data flow support the conclusion,
but the interaction was not executed. State any runtime assumption explicitly.

**Unresolved:** A missing requirement, caller, environment or measurement could
change the conclusion. Keep this in open questions until it is established.

## Review close

Record the reviewed scope, important paths inspected, checks run and remaining
limits. List optional improvements separately only when they are requested or
materially useful. Avoid implying that a source review certifies accessibility,
performance, security or App Store acceptance.