# Development Readiness Gate

Purpose: define the minimum documentation and engineering controls required before assigning implementation teams.

---

## Go/No-Go Decision

A kickoff is Go only when all P0 items are complete and signed off.

| Priority | Area | Requirement | Owner | Status |
|----------|------|-------------|-------|--------|
| P0 | Contracts | REST API baseline approved | Architecture + API Team | [ ] |
| P0 | Contracts | Event contract baseline approved | Architecture + Platform Team | [ ] |
| P0 | Security | Phase 0-2 security baseline approved | Security + Platform Team | [ ] |
| P0 | Delivery | Phase plan owners assigned | PM + Engineering Manager | [ ] |
| P0 | Testing | Test strategy and CI quality gates approved | QA + Platform Team | [ ] |
| P0 | Operations | Runbooks reviewed and on-call ownership assigned | SRE + Platform Team | [ ] |
| P1 | Architecture | Capacity assumptions and SLA targets validated | Architecture | [ ] |
| P1 | Governance | Risk register created and prioritized | PM + Security | [ ] |
| P1 | Compliance | Audit and data retention requirements signed off | Compliance | [ ] |

---

## Team Assignment Model

Use this split to avoid unclear ownership across umbrella apps.

| Team | Primary Scope | Secondary Scope |
|------|----------------|-----------------|
| Team North | gateway_api, gateway_ws, gateway_mobile, gateway_web | API versioning and channel contracts |
| Team Core | mw_kernel, mw_auth, mw_router, mw_transform, mw_audit | Cross-cutting policy enforcement |
| Team South | adapter_banking, adapter_dw, adapter_http, adapter_file | Downstream integration testing |
| Team Infra | infra_repo, infra_cache, infra_queue, infra_telemetry | CI/CD, observability, reliability |

---

## Entry Criteria Per Phase

1. Phase 0: repository builds, CI runs, environment bootstrap documented. — ✅ COMPLETE (2026-04-26)
2. Phase 1: auth contract agreed, banking adapter stub contract agreed. — 🚧 In Progress
3. Phase 2: file and DW schemas approved, DLQ policy approved.
4. Phase 3: WebSocket topic and payload contracts approved.
5. Phase 4: admin authorization matrix and audit access controls approved.
6. Phase 5: mobile payload contract and push notification policy approved.
7. Phase 6: production hardening checklist and load test plan approved.

---

## Sign-Off

| Role | Name | Date | Decision |
|------|------|------|----------|
| Architecture Lead |  |  |  |
| Security Lead |  |  |  |
| QA Lead |  |  |  |
| SRE Lead |  |  |  |
| Engineering Manager |  |  |  |