What problem does it solve?
It prevents teams from marking work as done when changes only compile, deploy stale binaries, or fail in real UI behavior—ensuring verification is owned, repeatable, and grounded in reference evidence.
Core Features & Use Cases
- Own Your Dependencies: Diagnose and fix broken tools/configuration in the verification chain instead of reporting as blocked.
- Verify Against Reference: Compare actual results to the original app code and reference screenshots, not “looks right” guesses.
- Verify the Specific Change: Exercise the exact behavior your task modified (navigation, inputs, crashes, features) so reports are complete.
- Confirm Fresh Binary: Clean/rebuild and validate the on-device binary freshness before accepting inspection/interactions.
- Verification Levels L1–L4 (and L5 as applicable): Build, deploy, DevFlow inspection, interactive UI exercise, with an additional feature-focused checklist when in scope.
Quick Start
Use verification-protocol to validate any task that touches UI, pages, navigation, services, or app behavior by running the full L1–L4 device and DevFlow workflow and reporting results with the required template.