Files
pedwfrontend/memory-bank/glossary.md
T

80 lines
1.5 KiB
Markdown

# Glossary
## Entry Template
```
date: YYYY-MM-DD
author: <agent|name>
scope: <domain/component>
type: glossary
rationale: <why term clarity matters>
impact: <delivery/quality implication>
status: active
Term:
Definition:
Where used:
```
---
### G-001: DNS
date: 2026-03-11
author: Cline
scope: domain flows
type: glossary
rationale: Distinguishes DNS journey from general case search flows.
impact: Reduces implementation ambiguity in routing and UI behavior.
status: active
Term:
DNS
Definition:
Developments of National Significance journey and related case/search routes.
Where used:
- `pages/dns/**`, `pages/myportal/dns/**`, DNS-related search/detail pages
### G-002: HYDRATE
date: 2026-03-11
author: Cline
scope: Redux store lifecycle
type: glossary
rationale: Critical to SSR/client state consistency.
impact: Prevents store regressions during refactors.
status: active
Term:
HYDRATE
Definition:
`next-redux-wrapper` action used to merge server-side state into client-side store.
Where used:
- `store/store.js`
### G-003: Locale Parity
date: 2026-03-11
author: Cline
scope: i18n and routing
type: glossary
rationale: Core quality expectation for bilingual public service.
impact: Ensures consistent EN/CY experience.
status: active
Term:
Locale parity
Definition:
Equivalent behavior/content correctness across English (`en`) and Welsh (`cy`) for affected user journeys.
Where used:
- `locales/**`, `i18n.js`, `next.config.js`, user-facing pages/components