infra-engineer-delivery-review

Follow the output contract: state the result first, attach evidence and assumptions second, list risks third, and end with one executable next action. This ordering keeps the handoff scannable for operators.

It is a closing procedure that combines the completed artifact, validation evidence, a delivery-risk review, and blocker resolution into a single handoff document. It ensures nothing ships without verified evidence and a clear next step.

Use it when the task requires a concrete artifact, an evidence gate, or a formal handoff to another operator. It is not intended for generic conversational responses or exploratory discussion.

Attach the validation commands you ran, their outputs, and any known assumptions made during execution. Record unresolved blockers explicitly so the receiving operator can act on them.

It standardizes format but cannot judge technical correctness of the underlying work. Teams still need domain review for complex changes, and the workflow depends on engineers supplying accurate evidence.