checking-release-readiness

To record a release decision, you document the baseline, evidence status, residual risk, rollback, monitoring, and handoff. This generates an updated ship.md file containing the rationale, open gaps with owners, and specific monitoring and rollback notes.

Evidence-led release readiness ties baseline, evidence status, residual risk, rollback, monitoring, and handoff together into a single ship, block, defer, or ship-with-risk decision. It applies to standard changes approaching merge, including PRs and dependency updates.

You need to document a release readiness baseline and handoff when a change-control packet, dependency update, or agent-authority change approaches merge or release. It should not be used early in development before evidence exists.

Generating a ship.md risk register involves recording the release outcome, baseline, and residual risk. The output includes an updated ship.md, escalation paths, rationale, open gaps with assigned owners, and linked monitoring and rollback notes.

Yes, you can use this approach for agent-authority changes impacting production readiness. It records the ship, block, defer, or ship-with-risk decision by linking the change baseline, evidence status, and rollback plan to a defined handoff.

The limitation is that recording release readiness decisions is not suitable early in development before evidence exists. It requires existing baseline evidence, residual risk data, and monitoring plans to generate a valid ship.md decision record.