verification-before-completion

A verification gate prevents task completion by requiring fresh command outputs and exit codes before any status claim is finalized. It ensures agents attach live evidence to their final reports for full auditability.

A fresh-verification requirement mandates running and capturing new command outputs immediately before declaring success. It prevents stale data from masking failures in fast-moving multi-agent deployment pipelines.

Integrate a completion gate into your PR closure or deployment checklist that captures live command outputs and exit codes. The gate blocks closure until fresh evidence is reviewed and appended to the status report.

Yes, the verification gate works across agent pipelines and integrates into existing CI workflows and review steps. It applies end-to-end status checks to ensure completion claims are backed by fresh outputs.

Teams claim completion without fresh verification because fast-moving multi-agent workflows often skip final status checks to save time. This leads to unverified success claims that lack attached command outputs and auditability.

Avoid an evidence-first completion gate in exploratory workflows where fresh command outputs cannot be reliably captured. It is designed for tasks requiring strict auditability and definitive exit codes.