# Application Design Plan: prerendering Depth: standard. No question file was created: each open choice was settled by testing it in a spike or is purely technical, and the owner's decisions are in requirements.md. The design states its decisions and the consequences the owner should know. Business rules follow in Functional Design (units 1 and 2) and Infrastructure Design (unit 3). ## Plan - [x] Analyse context - [x] Read requirements.md, execution-plan.md and the shared reverse-engineering artifacts - [x] Read in code: `main.tsx`, `__root.tsx`, `vite.config.ts`, `index.html`, `serverConfig.ts`, `securityHeaders.ts`, `lighthouserc.cjs`, the CI workflow, `Reveal`, `useReveal`, `useInView`, `DeferredImage`, `NavigationBar`, `MobileNav`, `NotFound`, `renderApp` - [x] Test the open technical choices in the spike - [x] Hydration under the production `script-src`, with inline and with moved scripts - [x] URLs without a trailing slash through `autoSubfolderIndex: false` - [x] Three ways to build the 404 page - [x] Search parameters during hydration - [x] Generate `components.md` - [x] Generate `component-methods.md` - [x] Generate `services.md` - [x] Generate `component-dependency.md` - [x] Generate `application-design.md` - [x] Validate design completeness and consistency - [x] Every FR-PR and NFR-PR item has a home in a unit - [x] Mermaid diagrams use `classDef` with `color:#000`, safe node ids and a text alternative - [x] Security Baseline and PBT compliance summarised; no blocking findings