Publication control · updated 28 July 2026
Release Gates
A release gate makes publishing a deliberate state transition: records are prepared, reviewed, approved, published, and—if necessary—withdrawn.
A simple gate
Create a private work and source record. Review and lock the approved source record. Prepare a release manifest draft. Have an accountable editor approve the release. Publish only the explicitly permitted payload.
What a gate prevents
The gate prevents a draft, private source record, or authorized-reader release from being treated as a public JSON resource merely because it exists in the publishing system.
Auditability
Keep a record of who approved a release and which source version it references. Public pages should reveal only the appropriate public provenance, not internal audit data or staff identities.
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.