Change accountability · updated 28 July 2026
Versioning and Change Records
Versioning tells readers and tools which public record they are looking at. It does not imply that an edition, a manuscript, and every related record share the same version number.
Version what you publish
Use a clear version for each Context Pack and Release Manifest. Preserve the source-record version in the release record. If a public boundary, permitted destination, or approved metadata changes materially, publish a new version rather than silently rewriting history.
Stable URLs and withdrawal
Stable URLs make records referencable. A withdrawn release should stop resolving from its public endpoint or clearly report that it has been withdrawn, while internal records preserve the reason and audit history.
Reproducible references
When a tool produces a derived public output, keep the relevant release version and provenance with it. This lets people trace the output to the approved public contract that was available at the time.
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.