Bridge documents are non-normative by default

Platform spec ADR

Bridge documents are non-normative by default

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

Legacy Starlight paths and informal mapping tables were cited in reviews as if they were language law.

Decision

Bridge documents (migration guides, mapping tables, terminology crosswalks) are non-normative by default unless a Standard platform-spec feature page explicitly declares normative status. Migration mapping pages must not be the final authority for platform behavior.

Consequences

Legacy spec mapping stays informative; normative fixes land under platform-spec/.

Verification anchors

PSC005 legacy bridge checks on Standard pages linking /execution/ or /corelib/.