Phase Reference

Architecture enforcement phases. All projects must progress through these gates.

P0—Intent

Define project intent, stakeholders, and success criteria. No code allowed.

Key Outputs

Problem statement, stakeholder map, success criteria document.

Next: Phase 1 — Domain & Golden Flows

P1—Domain & Golden Flows

Map domain entities, relationships, and define golden user flows.

Key Outputs

Domain entity diagram, golden flow documentation, data shape definitions.

Next: Phase 2 — UI Reference Build (Mock)

P2—UI Reference Build (Mock)

Build complete UI with mock data. No backend integration.

Key Outputs

Complete UI with all routes, interactive mock data, stakeholder approval.

Next: Phase 3 — Platform Binding (Core)

P3—Platform Binding (Core)

Connect UI to backend platform. Database, auth, and core APIs.

Key Outputs

Database schema, authentication integration, core API functionality.

Next: Phase 4 — API Exposure

P4—API Exposure

Expose APIs for external integrations and mobile clients.

Key Outputs

API documentation, versioned endpoints, integration test suite.

Next: Phase 5 — Identity & Onboarding

P5—Identity & Onboarding

Implement user identity, roles, and onboarding flows.

Key Outputs

Role definitions, onboarding flows, identity verification.

Next: Phase 6 — Hardening & Compliance

P6—Hardening & Compliance

Security audit, performance optimization, and compliance.

Key Outputs

Security audit report, performance benchmarks, compliance documentation.

Next: Phase 7 — Replication

P7—Replication

Document for replication. Handoff and maintenance protocols.

Key Outputs

Technical documentation, operations runbook, handoff confirmation.