Publishing pipeline

Registry Manifest provides the maintained static publication path. It validates one portable metadata document and renders deterministic, standards-shaped files that can be reviewed and hosted without a Registry Stack runtime.

Inputs

An adopter authors metadata.yaml and any referenced codelists or schemas. The Manifest schema is closed and rejects runtime-only configuration. The reviewed input describes catalogs, datasets, services, policies, forms, schemas, and evidence offerings.

Validation and rendering

The Manifest CLI validates the document before rendering. Rendered output can include DCAT, BRegDCAT-AP, CPSV-AP, SHACL, JSON Schema, JSON-LD policy material, OGC Records-shaped items, and SKOS-shaped codelist data where the profile supports them.

The output describes a publication surface. It does not read production records, authorize callers, serve HTTP, evaluate policy, or configure another product.

Publication

1. Review and validate the metadata input.
2. Render into a clean output directory.
3. Review the generated inventory and content.
4. Record the input revision and output digest.
5. Publish the directory with a static file host.
6. Replace the complete directory when publishing a new revision.

Consumers should treat metadata as descriptive. Access to Base Registry Engine (BReg) records remains governed by BReg, and Evidence Gateway evaluates its own configured requirements and sources.

Next

• Registry Manifest overview
• Portable metadata model
• Standards register