- Source
- Exact immutable commit
- Repository
- Frozen install, format, lint, type, test and build
- Artifact
- Identified output with integrity evidence
- Runtime
- Install, start, health, stop and recovery
- Limitations
- Known unsupported and unapproved boundaries
- Rollback
- Supported path to prior software and compatible state
status · AVC
Release evidence, not release theatre.
Exact source, artifacts, checks, limitations and rollback accompany every release.
Source becomes a release through reproducible evidence.
Artifact publication does not imply production promotion.
- Exact commitpassed
The source SHA and clean tree are recorded.
- Repository checksactive
Frozen install, type, lint, test and build succeed on exact head.
- Artifact integritypending
Generated artifacts are identified and verifiable.
- Runtime verificationpending
Install, start, health, stop and recovery behave as documented.
- Rollbackpending
Prior software and compatible state can be restored.
Exact source
A release identifies the commit and artifacts it represents.
Release notes, checks and limitations refer to immutable source rather than the current state of a moving branch.
Evidence bundle
Build, tests, security and runtime checks remain separately inspectable.
One green status cannot substitute for missing native packaging, recovery or exact-head repository evidence.
Rollback
A release is incomplete without a supported path back.
Software rollback, data compatibility, backups and operator instructions are part of the release boundary.