marsai:dev-validation

Final gate validation enforces explicit human approval by requiring a human decision after development and testing. It prevents self-certification by ensuring only different agents or humans can approve the final gate.

Gate 5 validation is the final approval step in a development cycle that ensures all acceptance criteria and quality signals from earlier gates are satisfied before feature completion. It automates evidence gathering from Gates 0-4.

To prevent self-approval during the release process, the validation workflow enforces a non-self-approval policy where only different agents or humans can provide the final explicit approval for a feature gate.

Yes, final gate validation supports automated evidence gathering from Gates 0-4. It collects tests, reviews, and logs from previous phases to present a clear decision basis for the final human approval.

When validation issues are found, the system provides severity tagging and generates remediation tasks. It outputs a structured validation record for auditing to ensure clear risk signaling and proper issue resolution.

Automated gate validation without human approval lacks explicit verification of acceptance criteria. It risks self-certification and fails to produce the structured validation record required for proper auditing and risk signaling.