verification-mastery

To prevent unverified success claims, you can enforce a gate-based verification workflow that blocks status changes and task completion until fresh logs and artifacts are generated as evidence. This stops hallucinated success signals.

Evidence-driven reporting requires attaching fresh verification outputs, such as logs and test results, to each completion claim. This mechanism ensures that every status report is formally backed by generated artifacts.

You gate progress by applying verification checks during iteration gates and status reporting. The system demands fresh verification artifacts before allowing any status changes or declaring a task complete.

You need to generate fresh logs and artifacts for verification during iterative task runs, specifically before declaring a task complete. This requirement avoids hallucinations and ensures claims have fresh evidence.

No specific dependencies are required to run this verification workflow. It operates independently to enforce that every completion claim is backed by fresh verification artifacts.

The best way to block status changes is using a gate-based verification approach. It intercepts status reporting and task execution, preventing progress until fresh logs and artifacts are present as evidence.