Migration mapping page required sections

Platform spec ADR

Migration mapping page required sections

Back to Non-normative bridge docs policy ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

Articles

• No directly attached article pages for this node.

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 0 SpecSection(s) · 5 H2 heading(s)

Section id	Required	Found
what-this-feature-specifies	no	no
implementation-anchors	no	no

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Feature
  Non-normative bridge docs policy

  Parent feature hub

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.