# Report title

Use a precise title describing the observed behavior.

## Scope and version

- Project and authorization reference:
- Supplied source files:
- Exact commit or release:
- Relevant program rule or impact category:

## Observed behavior

Describe what the supplied code or recorded evidence actually shows. Cite filenames and lines.

## Expected behavior

State the intended rule and the source that establishes it.

## Supporting evidence

Record existing authorized observations and safe local regression results. Separate local behavior from a deployed-system outcome. Do not include live credentials or other users' data.

## Impact

Describe the affected party and consequence supported by the evidence. Leave severity unrated when it is not established.

## Strongest counterargument

State the strongest reason this claim may be wrong, out of scope, intentional, or already known. Record whether the evidence resolves it.

## Known issues and prior art

List dated sources and compare root cause, entry point, method, and fix. Same-root overlap stays on hold until distinctness is established.

## Defensive remediation

Recommend a focused fix and a safe local regression check.

## Unresolved questions and next steps

Preserve missing evidence and the smallest useful next action. Verify the current program rules before any submission.