agency-reality-checker

Integration validation enforces evidence-based certification by demanding screenshots, logs, and documented risk signals before approval, defaulting to NEEDS WORK unless proven otherwise. It halts misguided approvals by requiring reproducible artifact collection and deterministic failure signals across multi-service stacks.

QA cross-validation collects reproducible evidence by executing reality-check commands that gather screenshots and logs, then cross-reviews these artifacts against implemented features and end-to-end test scenarios. This ensures all risk signals are documented prior to release.

A reality-check workflow for production-readiness assessment is a structured validation process that verifies build artifacts, performs QA cross-validation, and completes end-to-end system validation. It defaults to NEEDS WORK status unless rigorous, evidence-backed criteria are satisfied.

Deterministic validation criteria halt misguided integration approvals by requiring explicit verification steps, reproducible evidence collection, and cross-checks before production. The workflow defaults to rejecting releases unless proven through documented artifacts and end-to-end system validation.

Manual reviews for end-to-end integration scenarios lack deterministic validation criteria and reproducible evidence collection, increasing the risk of fantasy approvals. The reality-checker approach mitigates this by mandating screenshots, logs, and documented risk signals across multi-service stacks before release.