Review, approval, and release
Release is the boundary between engineering work and operational catalog use.
Before release
Review the exact sequence version you intend to publish.
Confirm sequence identity and source, sequence length and topology, sequence hash integrity, features and annotations, project context, assembly provenance when applicable, primer and PCR checks when relevant, and unresolved warnings.
Electronic approval
Publishing requires an electronic-signature authorization when configured by the release workflow.
The signed release is tied to the exact sequence version and its immutable identifying data.
What publication does
Publication can approve the selected sequence version, make it the released sequence for the catalog plasmid, synchronize the operational sequence snapshot, record the release time and releasing user, preserve project and assembly provenance, and create an auditable release event.
Current and released versions
A released version can remain operational while a newer draft is being designed.
This lets research continue without silently changing the sequence used by protocols or other operational records.
After release
Open the plasmid catalog record to confirm the released version, sequence length, topology, release provenance, Molecular Studio project relationship, and associated strains when applicable.
Future changes should create a new sequence version rather than editing the released version in place.