# Quality Gate Matrix

Every implementation pass must satisfy the relevant gates.

| Gate | Backend | Frontend | Data/GIS | AI | Required before merge |
|---|---|---|---|---|---|
| Import/build | app imports | TS builds | processing modules import | model adapters import | yes |
| Contract | response envelope | API client typed | metadata shape stable | detection output shape stable | yes |
| Validation | request schemas | form errors | CRS/file errors | threshold/model errors | yes |
| Tests | unit/contract | component where feasible | fixture processing | adapter test | yes for touched area |
| Docs | route/service docs | UI states docs | source/operation docs | model notes | yes |
| No fake success | errors visible | empty states real | unsupported explicit | unavailable explicit | yes |

## Minimum gates for Day 1

- Backend health passes.
- Project/area/dataset contracts pass.
- Frontend shell builds.
- Fixture metadata tests pass.
- Smoke script documents exact failures if any remain.

## Gate failure response

If a gate fails, Codex must either fix it or mark the pass incomplete. Do not claim completion when validation was skipped.