Platform specification Specification

Purpose

This capability preserves and governs the migrated Beskid standard contract for Platform specification, including its legacy provenance and review status.

Requirements

Requirement: Platform specification conformance status

This capability SHALL remain non-conformant and MUST NOT be cited as an implemented Beskid guarantee until a validated OpenSpec change adds explicit behavioral requirements.

Stable ID: BSP-REQ-7F1082D9A8BD

Scenario: Capability has descriptive material only

• GIVEN the migrated sources contain no uppercase BCP-14 obligation or accepted ADR decision
• WHEN an implementation reports Beskid conformance
• THEN it MUST NOT claim conformance based on this capability

Informative Source Provenance

The records below preserve migration history and are not normative except where text was extracted into a requirement above.

Source Record: Platform specification

Authority: informative provenance
Legacy path: /platform-spec/
Source: site/spec-content/platform-spec/content.md
SHA-256: 38274981e7aedc836804b24a372d4f5ea176ee9e3a5dbcc6bb9bd067e2d942c2

## Overview

The Beskid platform specification defines normative language, compiler, tooling, and deployment contracts.

## Scope

This tree covers compiler behavior, project manifests, runtime ABI, and platform services.

Source Record: Platform specification

Authority: informative provenance
Legacy path: /platform-spec/
Source: site/spec-content/platform-spec/index/content.md
SHA-256: e3e6be51e425bf8ce33665044bd5a81c1a5967e53877a7a573cc4de1f39d4c71

<PlatformSpecHome />