Module representation_registry 

Frozen, published catalogue of the built-in representation IDs (B-014 / DMD-001).

B-014 is a freeze/publish problem, not an invention problem: the stable representation-ID vocabulary already lives in crate::builtin_models as pub const strings, a BuiltinDataModel enum and its constructors. This module does not add a new vocabulary; it publishes the existing one as a single, deterministic, machine-readable registry so cross-repo consumers (notably ControllerManifest.data_requirements ports on L16 and the nirs4all-io emit on L7) can reference the frozen strings, and so a drift test can freeze them against crate::builtin_models.

The companion artifact docs/contracts/representation_registry.v1.json is generated from representation_registry (via the dag-ml-data-cli representation-registry command) and pinned by the published_registry_matches_builtin_models drift test, which fails the moment a built-in representation changes without the published manifest being regenerated.

Structs

MvpStatus

MVP profile membership for a published representation ID.

RegisteredRepresentation

One frozen, published entry of the built-in representation registry.

RepresentationRegistry

The frozen, published catalogue of built-in representation IDs.

Enums

MvpEmissionStatus

Cross-repo publication status of a representation ID inside an MVP profile.

Constants

MVP_PROFILE_SPECTRA_IMAGE

Name of the spectra+image MVP profile defined by B-014 / IO_spec.md §5.

REPRESENTATION_REGISTRY_ID

Stable identifier of the representation registry contract.

REPRESENTATION_REGISTRY_SCHEMA_VERSION

Wire-shape version of the published representation registry manifest.

REPRESENTATION_REGISTRY_SOURCE

Repo-relative provenance of the frozen representation IDs.

Functions

representation_registry

Build the frozen, published catalogue of built-in representation IDs from BUILTIN_DATA_MODELS. The result is deterministic and source-order stable.

validate_model_input_spec_against_registry

Validate that a model-input/data-requirements contract consumes only published representation IDs, and that each accepted representation’s frozen type_id and rank are allowed by the port.