Platform specification leads implementation

Platform spec ADR

Platform specification leads implementation

Back to Project inception 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

OKarea · 4 SpecSection(s) · 1 H2 heading(s)

Section id	Required	Found
what-this-feature-specifies	yes	yes
implementation-anchors	yes	yes

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Feature
  Project inception decisions

  Parent feature hub

Context

Early Beskid work mixed README intent, compiler experiments, and informal design chat without a single enforceable contract surface.

Decision

The platform specification on Git main must precede or accompany implementation that changes user-visible semantics. Tests and crates verify drift; they do not replace missing spec text.

Consequences

Contributors file spec updates in the same change set as behavioral changes. CI content gates block Standard stubs.

Verification anchors

site/website/src/content/docs/platform-spec/; verify:trudoc --preset ci.