# Quality Gates

## Documentation Normalization

- Every extracted source has `source_id`, path, type, status, and notes.
- Every requirement-like claim has at least one `source_ref`.
- Duplicates are merged, contradictions are preserved.
- Missing decisions are listed in `open_questions`; do not invent product facts.

## UX Construction

- Unresolved blocking open questions have been surfaced to the user before UX generation.
- Every screen maps to a user goal, flow step, or explicit assumption.
- Major UX decisions have citations or explicit rationale.
- Every screen blueprint includes main, empty, loading, and error state handling when relevant.
- Acceptance criteria are testable.

## Figma Build

- Use native Figma MCP and existing design-system assets when available.
- Create/edit incrementally and return node IDs from each write.
- Product screen frames contain only final-product UI.
- Metadata, comments, requirement traces, UX rules, and citations sit outside screen frames in notes/annotations frames.
- Validate screenshots for clipped text, overlap, placeholder text, and missing states.
- Update `figma_build_manifest.json` after every write session.