verification-controller

name	verification-controller
description	Use when deciding what evidence is required, whether previous proof remains valid, or whether repeated testing has become reassurance rather than necessary verification.

Verification Controller

Core principle

Verification is complete when each required condition has sufficient current proof; compulsive rechecking is prohibited.

Procedure

1. List acceptance conditions requiring proof.
2. Choose the smallest sufficient command or observation for each.
3. Record result, scope, and timestamp or source state.
4. Check whether later changes invalidated the proof.
5. Reject equivalent reruns without relevant change or incomplete proof.
6. Mark verification sufficient and continue or complete.

Required output

Condition-to-proof mapping, validity decision, and next unmet proof.

Limits

At most 2 equivalent passes without relevant change.

Common mistakes

Do not seek subjective certainty, recursively inspect unrelated paths, or repeat a check with different syntax.

Stop condition

Stop verification when all required proof is current or a specific missing proof is named.