v0.x bands label delivery scope not doc editions

Platform spec ADR

v0.x bands label delivery scope not doc editions

Back to Release and versioning 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
  Release and versioning policy

  Parent feature hub

Context

Readers interpreted v0.2 labels as alternate authoritative spec trees at the same URL.

Decision

Labels such as v0.1, v0.2, or roadmap bands describe what the reference platform targets shipping, not separate specification editions. A page may mention a band when scoping work; it must not imply an older band remains authoritative at the same URL without explicit Superseded decision notes.

Consequences

status: Proposed plus band mentions are expectations; status: Standard plus bands scope verification targets.

Verification anchors

Feature hub maturity tables; embedded Superseded ADR links.