delivery-completion

A delivery decision automates turning verified work into an explicit merge, hold, or discard outcome. It validates fresh verification evidence and determines the integration target, replacing ambiguous completion statuses with a tracked governance handoff.

A delivery-decision-record captures the chosen outcome of verified work, such as merging, pushing a PR, holding, or discarding. You need one when verification is complete and an explicit integration decision across development branches is required.

You document a decision to hold or discard a branch by generating a delivery-decision-record. This enforces explicit delivery outcomes and ensures the chosen state is preserved for later or explicitly discarded with a tracked, recorded outcome.

Yes, delivery completion requires verification evidence freshness before merging. It ensures validation of fresh execution checkpoints to produce an accurate delivery-decision-record for the chosen integration target.

The best way to hand off verified work to release management is through a controlled delivery-decision-record. This provides an explicit governance handoff, documenting the final state and chosen outcome for downstream delivery-related workflows.

You should use an explicit delivery decision instead of marking a task as done to avoid ambiguous completion. It enforces a tracked outcome for merging, holding, or discarding, ensuring verification evidence validates the final integration state.