verification

Use when adding or relying on a test, assertion, screenshot golden, lint rule or CI step meant to catch something, before trusting it or reporting it as coverage. Also fire when wiring a check into CI, when a check passes on its first run having never been seen red, or when the user asks "does that actually test anything" / "is that really covered". Do NOT fire for test-driven work, where the test was already seen failing before the fix.

Use when about to state or rely on how a third-party JVM/Android library behaves — a default value, whether a field is omitted or null, which branch a task takes — and the docs are absent, ambiguous, or the naming suggests something the code may not do. Fire when a plan says "set X to its strict value" without evidence X is not already strict, when a field's name and its type disagree, or when a check passes and you cannot say which comparison it made. Do NOT fire when the behaviour can be run and observed — run it.