# Defect report

> **What this teaches:** I can turn “it is broken” into reproducible evidence, a bounded impact statement, and testable acceptance for a repair.

Predict the smallest input or state that can still expose the problem. Preserve actual output separately from your explanation of its cause.

## Summary

Describe the wrong observable behavior without guessing at the root cause.

[One sentence describing the observable wrong behavior.]

## Impact

Separate who is affected and how badly from how often the defect occurs; these facts guide priority.

- Affected user or system:
- Severity and reason:
- Frequency:

## Reproduction

Give another person a known starting state and deterministic actions. Actual and expected results must remain separate.

1. Start from **[known state/version]**.
2. Perform **[action]**.
3. Observe **[actual result]**.

Expected: **[expected result]**

## Smallest failing case

Reducing the case removes unrelated variables and gives you a cheap regression test.

[Provide sanitized input, exact redacted output, and the smallest command or test that reproduces the defect.]

## Acceptance criteria for the fix

These checks require evidence that the original failure is repaired without breaking relevant existing behavior.

- [ ] The smallest failing case now passes.
- [ ] A regression test fails before the fix and passes after it.
- [ ] Relevant existing behavior remains green.
- [ ] The root cause and one plausible recurrence path are explained.

## Evidence

Link the failure before the change to the exact fix and the green result after it.

- Failing test/run:
- Fix commit:
- Green test/CI run:
- Release or follow-up:

## Explain it back

Explain how to reproduce the defect, which evidence supports the root cause, and one plausible path by which the defect could recur.