Files
AndreaSlopFotografie/aidlc-docs/features/prerendering/construction/plans/start-migration-functional-design-plan.md
T
SluijsensandClaude Opus 5.5 65c850e949 Adds the prerendering requirements, design and baseline
Records the requirements, execution plan, application design, the first unit's
functional design and code generation plan, and the baseline on master.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 17:41:12 +01:00

17 lines
1.8 KiB
Markdown

# Functional Design Plan - Unit 1: Start migration and script step
Feature: prerendering. Unit: 1 "Start migration and script step" (see [execution-plan.md](../../inception/plans/execution-plan.md) § Units of Work). Owner decision on the e-mail address: [start-migration-fd-questions.md](start-migration-fd-questions.md) (Q1 = A). Artifacts: [functional-design/](../start-migration/functional-design/).
## Steps
- [x] Step 1: Analyse unit context (requirements, execution plan, application design, spike evidence, owner answer on the e-mail address)
- [x] Step 2: Verify in `web/src` and `web/config` every component a rule is written for (hooks, routes, Footer, contact components, `lib/`, Sentry and Umami, sitemap plugin, test setup) and in `node_modules` how Chakra's `useMediaQuery` and `useBreakpointValue` behave
- [x] Step 3: Search `web/src` for further differences between prerender and first browser render (browser globals in render, time and random values, `useId`, `window` or `document` in initialisers)
- [x] Step 4: Create this plan
- [x] Step 5: `business-logic-model.md` (build flow, page load phases, script step algorithm, runner, e-mail, search, 404, preview server, measurement, testable properties)
- [x] Step 6: `business-rules.md` (numbered rules BR-BLD, BR-ENT, BR-HYD, BR-MAIL, BR-404, BR-LZY, BR-MON, BR-SCR, BR-SEC, BR-SRV, BR-TST, BR-MEA; to verify in code generation)
- [x] Step 7: `domain-entities.md` (script step entities, hydration inventory, e-mail slot, request resolution)
- [x] Step 8: `frontend-components.md` (component hierarchy, first-render contract per component, new hooks, document shell)
- [x] Step 9: Check diagrams against the Mermaid standards and the content validation rules
- [x] Step 10: Report to the orchestrator (no questions needed; the open choices are listed in the report)