Semantic Pipeline Specification

Purpose

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

Requirements

Requirement: Semantic Pipeline 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-91C592FCA808

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: Semantic Pipeline

Authority: informative provenance
Legacy path: /platform-spec/compiler/semantic-pipeline/
Source: site/spec-content/platform-spec/compiler/semantic-pipeline/content.md
SHA-256: 128b1a033d1e791ce315c89f96ba5ae4c334c8e768241fc89aaeb3afd9160427

## Overview