Verification Protocol

Verification means proving that code changes produce the intended result on a real device, against reference material, through interactive exercise — not just proving they compile. A fresh binary is built and deployed, the UI is inspected via DevFlow visual tree, navigation is exercised interactively, features are tested with real inputs, and results are compared against the original BaristaNotes app code and reference screenshots. A broken tool in this chain is a problem to solve, not a reason to skip a step.

No task is done until verified on device. "It builds" is not done. A screenshot of a stale binary is not done.

Rule 1: Own Your Dependencies

When a tool or dependency is broken, fix it. The solution is in the repo, the reference code, or the documentation you were given.