# NFR Design Plan - andreaslop-client (U2) ## Steps - [x] Analyse NFR requirements (nfr-requirements.md, tech-stack-decisions.md) - [x] Evaluate question categories; no open questions (justification below) - [x] Generate `nfr-design/nfr-design-patterns.md` - [x] Generate `nfr-design/logical-components.md` ## Category evaluation (why no questions) - Resilience: deploy resilience is inherited from `deploy-scp.yaml` (atomic switch, health check, previous release kept); the new part is only the skip switch (NFR-DEP-02), which has one obvious design. - Scalability and performance: N/A for U2 (one small instance). - Security: the token check, limiter and security event follow the answers Q3/Q4 and the existing `SecurityEvents` and rate-limiting mechanisms; placement has one sensible solution. - Logical components: no new infrastructure; one validator, one controller change, one security event, one CSS theme, two CI jobs. - Open verification items are listed in `nfr-design-patterns.md` and are settled by tests or the first test deploy.