State the test.See the outcome.

Decision gates

One release decision needs a named build or change set; do not mix unrelated work.

A gate with vague or disputed criteria is not ready for a pass label.

Keep not-run work visible. A drafted case is not an executed case.

A blocked or failed gate needs a person to investigate, not a cosmetic score.

Link the gate to evidence that belongs to this build and environment.

A board can prepare the facts. It cannot sign off or deploy for the owner.

Private draftSources in contextVisible outcomes

PassFailBlockedNot run

The owner makes the decision with the unresolved work in view.

Set each gate to pass, fail, blocked or not run and add an owner note. The board organises a discussion; it never grants approval.

Editable examples

One release decision needs a named build or change set; do not mix unrelated work.

A drafted test, an observed result and a release decision are different events. Keep each one tied to the product you actually checked.