BPlatform specification
Login
Edit this page
featurepublished

Registry Client

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

Document layout: Feature capability layoutconforms
  • ## Purpose
  • ## Requirements

Registry Client Specification

Purpose

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

Requirements

Requirement: Registry Client 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-1C527463C992

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: Registry Client

Authority: informative provenance
Legacy path: /platform-spec/tooling/registry-client/
Source: site/spec-content/platform-spec/tooling/registry-client/content.md
SHA-256: 58d16d0ad152af111afa3c1efa62459476bac0680c308aab28331b01e06ff4ee

Migrated source text 
## Overview