Bridge pages must link canonical destinations

Platform spec ADR

Bridge pages must link canonical destinations

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

Readers stopped at bridge pages without reaching the owning Standard feature contract.

Decision

Every non-normative bridge page must link to one or more canonical normative destinations and label those links as canonical. Near the top each bridge must state: non-normative status, why the page exists, and which normative page(s) own the behavior. Canonical links must be direct platform-spec URLs with human-readable relation labels; bi-directional discoverability is required during active migration windows when practical.

Consequences

Standard pages that link legacy prefixes must mark those links non-normative in prose or relatedTopics.

Verification anchors

checkStaleLegacyBridge in platform-spec-content.ts.