Roadmap search
Versions, deliverables, workstreams, tasks, and pages
Migration mapping page required sections
src/content/docs/platform-spec/community/spec-maintenance/non-normative-bridge-docs-policy/adr/0003-migration-mapping-page-shape.mdx
import SpecAdrChrome from '@beskid/beskid-ui/platform-spec/SpecAdrChrome.astro';
<SpecAdrChrome />Context
Ad-hoc mapping tables mixed partial coverage with implied normative scope.
Decision
Migration mapping pages must include: (1) a one-sentence non-normative notice; (2) a Canonical destinations section linking target feature hubs; (3) a Mapping scope section stating coverage and exclusions; (4) a maintenance note for retirement timing. Multi-domain mappings must group links by destination domain/area.
Consequences
Bridge pages become checklist-complete before merge; retirement removes the bridge when canonical nav suffices.
Verification anchors
Legacy spec mapping structure review in PR template.