Approved delivery · updated 28 July 2026
Release Manifests
A Release Manifest describes an approved release and its delivery boundary. It is published only after editorial approval; it is not an automated claim that a work is factually complete.
The release contract
A manifest can carry release identity, version, publication status, source-record version, access mode, provenance, exclusions, and a stable public endpoint when metadata is approved for public delivery.
Access modes
Private records have no public delivery. Authorized-reader material requires entitlement checks outside the public endpoint. Metadata-public releases can expose only the approved descriptive payload and should stop resolving when withdrawn.
Why approval comes first
Generation can help prepare a draft record, but approval is an accountable editorial act. The manifest preserves the distinction between draft material, approved metadata, and protected content.
Related documentation
For a concrete public record, inspect the metadata-only Context Pack demo. It remains separate from protected manuscript content and private editorial systems.