ia-verification-before-completion

To stop false completion claims, enforce a verification gate requiring fresh test evidence before any status signaling. This prevents AI agents from declaring a bug fixed or ready to merge without current proof of passing tests or successful builds.

AI agents claim migrations are finished without verification due to missing pre-verification state checks. Enforcing a stepwise verification pipeline that stops on first failure ensures completion reports include exact evidence and risk notes before signaling success.

The best way to control scope during ambiguous edits like project migrations is applying a spatial scope-confirmation gate. This prevents accidental cross-repo blast radius by requiring explicit scope confirmation before the agent executes broad modifications.

Enforce CI evidence collection for release readiness by mandating an explicit pre-verification state check immediately before completion statements. This structured pipeline requires running appropriate build and test commands, stopping on first failure, and reporting verification evidence.

Yes, this verification workflow applies directly to delegated subagent coding, infrastructure refactoring, and migrations. It enforces evidence-based completion reporting with risk notes across all agent workflows where status-signaling would otherwise happen without current proof.

A pre-verification state check for AI agent workflows is an explicit gate requiring fresh verification evidence before any completion claim. It ensures agents run appropriate build, test, or security commands and generate a structured completion report before signaling success.