# Gap register: <integration name>

Analyst: <you>
Date: <date>
Artifacts reviewed: OpenAPI v<version>, requirements v<version>, sample responses (<count>), business rules (<date>)

| # | Finding | Severity | Requirement / rule | Evidence (artifact, location) | Question for the API team | Status |
|---|---|---|---|---|---|---|
| 1 | <one sentence: what disagrees with what> | High / Medium / Low | REQ-xx, BR-x | <file, path or line> | <one line, answerable in one line> | Open |
| 2 | | | | | | |

Severity guide
- High: wrong money movement, duplicates, or failed reconciliation if unresolved.
- Medium: a client that follows the contract will break on real traffic.
- Low: documentation debt; costs a support ticket or an hour.

Rules for a good row
- Name the exact field, header, code, or state. Never "the pagination" or "the errors".
- Evidence is a location someone else can open, not a memory.
- One question per row. If you need two, it is two findings.