# Flow Diagram Implementation Parity Check

## Context

App: {{APP_NAME}}
Business flow doc: {{BUSINESS_FLOW_DOC}}
Backend sources: {{BACKEND_RESOLVERS}} + {{BACKEND_EXECUTORS}} + {{BACKEND_MODULES}}

## Check

A diagram can claim behavior the implementation never got. For every claim the
`## Flow Diagram` makes, find its implementation counterpart. Judge semantically —
wording differs — and cite the file for each verified claim.

1. **Statuses and transitions** — every status value the diagram names exists in the
   corresponding model's enum, and the named transition is performed by a command,
   resolver, or scheduled job.
2. **Error and validation branches** — every `alt`/`else` error branch is enforced
   somewhere (a reject/throw path in a resolver or module command).
3. **Notifications and events** — every "notify …" / event step has an emitting
   counterpart in the implementation.

Report findings per [impl-parity-report-format.md](impl-parity-report-format.md).

## Gaps to report

- A status value or transition the implementation does not have.
- An error branch no code enforces.
- A notification or event no code emits.
- (Informational) an implemented status/error central to the flow that the diagram omits.