Requesting Code Review

Review request template

## What
1 sentence: what changed.

## Why
Link to design.md or issue.

## How verified
- [test output / curl / screenshot]

## Open questions for reviewer
- Should X live in `services/` or `ml/`?
- Is the 1.5s latency on cold-start acceptable?

## Out of scope (for follow-up)
- Caching layer (ADR-0007 tracks this).

Receiving review

• Every comment gets a response — applied, pushed back on with reasoning, or logged as follow-up.
• Pushing back is fine; silent dismissal is not.
• Treat nits as free quality improvements. Reject them only with a real reason.

Blocking severity

• Blocker: security, data loss, wrong behavior, missing test.
• Major: design drift, significant perf regression, accessibility failure.
• Minor: naming, style, micro-perf.
• Nit: preference, bikeshed.

Do not merge with unresolved blockers. Majors require ack.