Skip to content

Design Baseline Gate (Before Feature Coding)

Purpose

Enforce a consistent pre-coding baseline for product, contracts, UX mocks, and governance.

Required Inputs

  • doc/product/PRD.md
  • doc/product/UX_Journeys.md
  • doc/product/UX_Implementation_Spec.md
  • doc/product/ux-mocks/README.md
  • doc/product/Brand_Guidelines.md
  • doc/governance/UX_Contract_Gate.md
  • doc/api/openapi.draft.yaml
  • doc/api/asyncapi.draft.yaml
  • doc/api/API_Surface.md

Gate Rules

  1. No feature code before contract alignment.
  2. New UX interaction requires corresponding OpenAPI/AsyncAPI operation.

  3. Contract additions must land before implementation.

  4. No screen implementation before mock completion.

  5. Route must have a mock in doc/product/ux-mocks/.

  6. Mock must include full state matrix: loading, empty, error, success, restricted, rate_limited.

  7. No branding drift.

  8. UI naming/tokens/logo usage must follow Brand_Guidelines.md.

  9. External marketing images are reference-only and must not be hotlinked in app code.

  10. No hidden policy assumptions.

  11. Behavior-sensitive constants must be policy/config-driven and represented in docs/contracts.

Definition of Ready

  • PRD and UX docs include the target route/flow.
  • OpenAPI/AsyncAPI specs include all required operations/payloads.
  • API surface list is updated.
  • Screen mock is created and reviewed.
  • Error and auth behavior are explicit in contract and mock.
  • Roadmap phase linkage is documented in doc/Implementation_Roadmap.md.

Review Note

This gate is a stop condition. If any checkbox is unmet, implementation should not start.