stable-release

To promote a DOS rolling release to a stable channel, you validate the candidate tag against a green kernel suite, truth syscall, and third-party CI status. The process then applies an immutable stable tag and writes an evidence file without rebuilding the release.

A stable release evidence file captures the exact commit and gate snapshot during promotion to a stable channel. It provides a provable rollback anchor and an audit trail, ensuring you can recover cleanly from partial failures without bumping versions.

Enforcing soak age and CI validation requires checking that the candidate release passes a green kernel suite, a clean truth syscall, and third-party CI status. Once validated, an immutable stable git tag is added to the approved commit.

Yes, you can safely re-run the stable release promotion after a partial failure. The process preserves the rolling channel untouched and supports safe re-runs to ensure the immutable stable tag and evidence file are correctly applied.

No, promoting a release to a stable channel does not require rebuilding or bumping versions. The process promotes an already shipped DOS rolling release by applying a stable tag and creating a provable rollback anchor.

Adding an immutable stable tag requires the candidate commit to pass the promotion gate, including soak age enforcement and a clean truth syscall. The operation is limited to releases that have already shipped into a rolling channel.