PR · [Short title]

Purpose & Small Spec: [Why? Link to the current spec version]
Change & boundaries: [What changes? What is explicitly out of scope?]
Risk & affected areas: [Possible impact, interfaces, data, permissions]
Evidence: [Tests/checks performed + results + links; agent-review findings/version; name checks not performed]
Known limitations & open points: [Finding, blocker, owner; or none known]
Operations & rollback (if relevant): [Monitoring, alerts, rollback and recovery; otherwise not relevant + reason]
Review & merge approval: [Named human reviewer in the Delivery Team; reviewed commit/version, decision and date]

REVIEW CHECKLIST
Conditional items may be marked “not relevant” with a brief reason.
- [ ] Spec & scope: Does the change meet the spec and stay within the agreed scope?
- [ ] Clarity & architecture: Are the change’s structure, maintainability and architecture sound?
- [ ] Security & data access: Are security, data access and permissions adequately protected? [checked / not relevant + reason]
- [ ] Tests & failure cases: Are tests and checks meaningful, including relevant failure cases?
- [ ] Interfaces & existing functionality: Have effects on interfaces and existing functionality been checked? [checked / not relevant + reason]
- [ ] Operations & rollback: Where operations are affected: are monitoring, alerting, rollback and recovery defined and supported by evidence? [checked / not relevant + reason]
- [ ] Blocking findings resolved and rechecked; relevant changes after approval resubmitted for review.