Platform specification

Browse Map

• Community2 areas6 features34 StandardGovernance, contribution, and public compatibility commitments.
• Compiler9 areas32 features320 Standard192 articlesCompilation pipeline, semantic analysis, IR, and execution backends.
• Core library4 areas12 features121 Standard58 articlesStandard library modules, stability tiers, and cross-cutting API contracts.
• Execution2 areas8 features68 Standard39 articlesRuntime ABI, host boundary, backend execution model, and operational contracts for running Beskid programs.
• Language meta10 areas7 features87 Standard4 ProposedUser-visible semantics, conformance vocabulary, and how they map to compiler and tooling contracts.
• Tooling8 areas13 features131 Standard70 articlesCLI, formatter, LSP, manifests, lockfiles, and developer-facing contracts.

Latest changes

Git was unavailable at build time—run generate:platform-spec-git-meta for revision history.

How to read this specification

Language law lives under Language meta: what programs mean (types, control flow, contracts, memory, interop). Implementation law lives under Compiler, Execution, Core library, and Tooling: how the reference platform realizes those semantics.

Each feature page declares Proposed (draft, incomplete) or Standard (enforceable MUST/SHOULD text with verification anchors). Architecture decision records live in each feature's adr/ directory (one normative file per decision, expandable in the reader ADRs tab). Cross-cutting choices from project inception are under Project inception.

Governance: Specification authority and embedded decisions and Release and versioning policy.

Show guide

Legend

• Hub map root
• Domain major slice (compiler, tooling, …)
• Area topic group under a domain
• Feature leaf doc in the graph

×

Node relations