verification-before-completion

You can enforce evidence-based verification by mandating that specific verification commands are executed and their output confirmed before any task completion claims are made. This ensures all assertions are backed by fresh, verifiable data.

Risk-scaled evidence adapts verification requirements based on a task's risk tier, ranging from Minimal to Critical. Higher risk tasks demand more rigorous proof of passing tests and clean builds before any success is claimed.

Preventing false assertions involves enforcing a strict verification process that requires running specific commands and confirming their output. This stops premature claims of task completion by ensuring all success statements are backed by concrete data.

Yes, you can scale verification requirements by assigning risk tiers like Minimal, Standard, Elevated, or Critical. This scales the evidence needed, ensuring critical features require more comprehensive test and build verification than minimal risk tasks.

The verification process mandates running verification commands to confirm the build passes and acceptance criteria are met. This ensures tests pass and builds are clean, preventing the introduction of regressions or incomplete work before committing code.