Manifests And Lockfiles Specification

Purpose

This capability preserves and governs the migrated Beskid standard contract for Manifests And Lockfiles, including its legacy provenance and review status.

Requirements

Requirement: Manifests And Lockfiles 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-3DBABC69255F

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: Manifests And Lockfiles

Authority: informative provenance
Legacy path: /platform-spec/tooling/manifests-and-lockfiles/
Source: site/spec-content/platform-spec/tooling/manifests-and-lockfiles/content.md
SHA-256: 6b525af7dabf1fac0f2297ba68df3fe6bed4fd5d8d9d7a6252120baa3b12dfa5

## Overview