platform-blueprintlisted

# Platform Blueprint — enterprise architecture The architecture layer that sits atop brainstorming/writing-plans. Turn an approved PRD into a defensible, modular system design with decisions recorded and tradeoffs surfaced. Investigate first: read the PRD and any existing code before asserting structure. Never invent constraints the user didn't give — ask when a critical NFR (scale, budget, latency target) is unknown. ## Fits in the pipeline - **Stage 1** (alongside `/prd`) to frame NFRs and architectural constraints early. - **Stage 3** (`/stack-and-cost`) — NFRs drive stack choices and the cost conversation. - **Stage 4** (`/module-map`) — the C4 container/component views become the module decomposition. Owned by `solution-architect`. Re-entered on any Stage 9 change that shifts a system property. ## What this skill produces ### 1. Non-functional requirements (NFRs) — make them measurable For each, capture a target, not an adjective. "Fast" is not an NFR; "p95 < 200ms at 1k RPS" is. - **Scale:** expected + peak load, data volume, growth horizon. State the design point. - **Latency:** p50/p95/p99 targets per critical path. - **Cost:** target run-cost envelope (ties directly to `tech-stack-and-cost`). - **Security:** authn/authz model, data classification, compliance regime (if any). - **Privacy:** what PII is collected, retention, residency, deletion path. (See `data-engineering`.) - **Availability/reliability:** SLO target, RTO/RPO if stateful. If a target is unknown an