# Cross-Verification: [feature / screen / design under review]
Verification date: YYYY-MM-DD

## Role 1 — Backend developer perspective
Question: Is this structure stable? Where does it break first when users grow?
- Issues found:
- Action: [applied / deferred + reason]

## Role 2 — UI/UX designer perspective
Question: Where will a first-time user get confused?
- Issues found:
- Action:

## Role 3 — Security reviewer perspective (Ch.14)
Question: Doubt everything, verify everything. Especially permissions, inputs, defaults.
- Issues found:
- Action:

## Role 4 — Cost manager perspective
Question: Where are API calls excessive? Where is money leaking?
- Issues found:
- Action:

## Functional verification (focus on failure paths — generate with AI)
- [ ] Happy path: ___ (PASS/FAIL)
- [ ] Failure path: ___ (PASS/FAIL)
- [ ] Failure path: ___ (PASS/FAIL)

## Overall verdict + next review date (3:1 rule — Ch.16):