Implementation domains defer to language-meta

Platform spec ADR

Implementation domains defer to language-meta

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

Pipeline and host details were written as if they owned user-visible meaning, overlapping language-meta chapters.

Decision

Compiler, Execution, Core library, and Tooling specify how the reference platform realizes language-meta. They must not redefine semantics already owned there; they must defer with relatedTopics (for example defers-to, implements) instead of duplicating normative key tables.

Consequences

Classification happens before authoring: “what does valid code mean?” → language-meta first; crates and phases link back.

Verification anchors

relatedTopics frontmatter validation in verify:trudoc --preset ci.