Platform spec home

Informative guide. This Book page explains Beskid but does not define the standard. For normative requirements, use the Beskid Standard.

Open /platform-spec/. That is the normative front door: no version prefix in the URL, Git as the axis (Release policy).

Use the home page to select the domain that owns a question, not to infer a rule from a tile title. Each domain leads to areas and feature hubs where the governing material is linked.

Top-level shape

flowchart TB
  accTitle: Platform specification domains
  accDescr: The platform specification home leads to six domains, language meta, compiler, execution, core library, tooling and community.
  home[Platform specification]
  lm[Language meta]
  comp[Compiler]
  exec[Execution]
  core[Core library]
  tool[Tooling]
  comm[Community]
  home --> lm
  home --> comp
  home --> exec
  home --> core
  home --> tool
  home --> comm

Text equivalent: The home page leads to six domains: language meta, compiler, execution, core library, tooling and community.

Reader chrome

Platform-spec pages use dedicated reader UI (tabs, ADRs, architecture graphs), not the book’s chapter rail. Expect:

• Current document / Articles / ADRs / Architecture tabs on feature hubs
• status: Standard vs Proposed in headers
• lastReviewed for freshness

Book vs spec

Need	Go to
Tutorial voice, workflows	/book/
Enforceable contracts	/platform-spec/
CLI flag lists	/book/reference/cli/

When a page is marked Proposed, treat it as a design or work-in-progress signal rather than silently relying on it as a stable guarantee. The specification authority guidance explains how authority and maturity are presented.

Next

Language meta map