Release and review
Prepare immutable package or connector bytes, prove them locally, and preserve enough evidence for independent review.
Release is a transition from editable author workspace to immutable artifact. Do not upload a source directory and ask production to build it.
Freeze the authoring brief
Confirm Attempt boundaries, Measurements, progression, input, corrections, presentation, story, and acceptance scenarios still match the implementation.
Run readiness locally
The project-local toolchain validates schemas, fixtures, deterministic engines, portable UI, overlay, responsive states, capability links, provenance, and archive safety.
Compare evolution
If a previous release exists, classify result, metric, preset, progression, observation, configuration, and presentation changes before choosing a version.
Pack exact bytes
Produce a self-contained .cmpkg with canonical manifest, content digests,
artifact sizes, bundled Domain Kits, and no secret or unsafe path.
Submit privately
Upload through the member product or scoped MCP. Independent review replays the artifact and returns bounded diagnostics. Submission is not publication.
An approved immutable release can then back a private install or reviewed Library listing. Public discovery and native connector authority require separate product review decisions.