Proposed vs Standard maturity gates

Platform spec ADR

Proposed vs Standard maturity gates

Back to Specification authority and embedded decisions ◎ 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) · 7 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
  Specification authority and embedded decisions

  Parent feature hub

Context

Standard pages shipped with circular stubs or without decisions, while readers treated every platform-spec URL as enforceable law.

Decision

status	Meaning	Requirements
Proposed	Incomplete or unstable	May omit full verification anchors; must not be cited as enforceable language law in conformance arguments
Standard	Enforceable platform contract	Must include normative MUST/SHOULD/MAY prose, verification anchors, and hub ## Decisions (or linked decisions-record)

Any Standard page failing content gates (circular canon stubs, placeholder-only bundles, missing decisions) must downgrade to Proposed until restored.

Consequences

Maturity is explicit in frontmatter; CI strict mode can fail scaffold Standard pages.

Verification anchors

verify:platform-spec-content with --strict; LANGUAGE_META_CIRCULAR_CANON_ALLOWLIST for tracked exceptions.