# Final Answer Contract

For substantial coding work, the final answer should cover these boundaries clearly.

## Required Sections

### Objective

What the task actually was in engineering terms.

### Assumptions

Only include assumptions that mattered and could not be quickly verified.

### Changes Made

Keep this concise. Focus on what changed, not every file touched.

### Verification Performed

State:

- commands run
- checks performed
- what each check actually proved

### Residual Risk

State what remains unproven, blocked, or risky.

## Language Rules

- Do not present inferences as verified facts.
- Do not hide missing verification behind confident phrasing.
- Do not bury the result under a changelog.
- If verification could not run, say why in one line.

## Review Mode Rule

For reviews, findings come first. Summary comes second.