Release Process and Lineage
The controlled sequence from green source to immutable distributables.
Record the source SHA, edition, artifact digest, manifest, checks, and rollback set.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
Release identity is separate from source package version. Generation 1 remains immutable; a later accepted artifact becomes Generation 2 and is the rollback relationship. No deployment is implied by documentation alone.
| Check | Source-backed expectation |
|---|---|
| Scope | Do not publish, deploy, overwrite, or delete release artifacts without explicit approval. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | pnpm verify:full |
| Stop condition | Unknown authorization, destructive impact, secret exposure, or conflicting evidence. |
Verification
Run the safe check, record its result, and compare the outcome with the documented contract. If the result depends on external configuration or provider availability, mark it as configuration-dependent rather than claiming a product guarantee.
pnpm verify:full
Safety boundary
Examples are non-production and use placeholders. Do not deploy, reset, force a migration, create secrets, activate providers, replay sensitive work, or expose private data from this page.