Beskid Standard

Scope

The Beskid Standard defines normative behavior. The source files are in openspec/specs/.

Use a requirement only when it contains SHALL or MUST and one or more scenarios. A Book page, blog post, README, or generated catalog does not define a new rule.

Authority

• Browse one of the 198 capability pages generated from the checked-in catalog. For example, open the CLI command surface.
• Use a stable requirement page when you need to cite one rule. For example, open BSP-REQ-942B8B35A6BB.
• Follow the canonical source link on either page. It opens the matching openspec/specs/**/spec.md file, and a requirement link opens its exact heading.
• Propose a change with an OpenSpec delta when a change affects observable language, compiler, runtime, core-library, tooling, or conformance behavior.

The current checked-in catalog contains 198 capabilities and 571 requirements. Generated pages identify those records but do not copy or reinterpret their normative prose.

Stable public paths

Beskid no longer operates the former Platform Spec service. A known /platform-spec/ alias now resolves to its catalog-backed capability page. A valid requirement fragment remains attached to that capability. An unknown alias opens the Standard not-found search state instead of an unrelated landing page.

Use /docs/standard/capabilities/<capability-key>/ for a capability. Use /docs/standard/requirements/<requirement-id>/ for one requirement. These paths preserve catalog identity when titles or navigation labels change.

The standard source and the Docs site use the same repository. The website and the source therefore ship from one repository revision.

Report a mismatch

Do not infer a requirement when a generated page, Docs page, or implementation conflicts with the OpenSpec source. Use Report a bug to record the public page, the OpenSpec source URL, both revisions, and the conflicting statements. Use Standard changes only when the proposed resolution changes normative behavior.