Specification leads implementation

Platform spec ADR

Specification leads implementation

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
  Project inception decisions

  Inception ADR D-INC-0001

• Feature
  Specification authority and embedded decisions

  Parent feature hub

Context

README intent and crate behavior diverged when implementation shipped without a matching platform-spec change set.

Decision

Implementation that alters observable language or platform behavior must be preceded or accompanied by normative spec updates. The spec is the authority; tests and crates are verification anchors, not substitutes for missing contract text. Cross-cutting inception record: D-INC-0001.

Consequences

Contributors pair spec and code in one change set; CI content gates block Standard stubs.

Verification anchors

Project inception ADR 0001; verify:platform-spec-content.