Chapter 04 / 08
Prove the right thing
Match the evidence to the claim. A passing helper test cannot close a broken workflow.
Ask what the evidence actually proves
A build can compile while a workflow remains broken. A database row can look correct while the interface reads the wrong account. Velocity makes the proof class explicit so a closeout cannot silently replace the required observation with an easier check.
| Class | Evidence | What it supports |
|---|---|---|
| A | Scenario / browser / end user | Visible behavior, interactions, and workflow acceptance |
| B | HTTP / API / runtime contract | Server behavior, sequencing, and runtime coordination |
| C | Logs / database / trace | Internal state and data-level changes |
| D | Code reasoning / static checks | Intended logic; insufficient alone for behavioral completion |
These classes support different claims. An end-to-end system claim needs Class A and Class B. A data repair needs Class C plus lane-appropriate runtime proof. Report the combination that supports the actual requirement.
Replay the reported workflow
For an operator-reported workflow defect, the first regression proof should follow the original workflow from its observable starting state to its expected outcome.
Scenario and mechanism
Switch the list through the UI, log out, log back in, and observe the selected list. A test that preloads a storage value and checks a helper is useful supporting evidence, but it does not exercise that reported sequence.
Name the lane and the limits
Record the environment, reviewed revision, checks performed, and missing proof. A deployment identifier, healthy process, or correct database identity establishes useful environment facts. None alone establishes the user-facing behavior.
If a browser scenario has not been exercised, say so. A closeout can be review-ready with an open verification obligation; it must not call that missing evidence a pass.
Map touched invariants
Before closeout, list every load-bearing invariant the change touches, including adjacent subsystem boundaries. Map each to direct evidence and an enforcing mechanism. An unbound obligation needs a visible owner and a gate or date; dropping it from the declared scope does not make it disappear.
Established Velocity guidance: Proof Model. The proof taxonomy uses V-model thinking to align requirement and verification levels; Velocity does not claim to have originated that tradition.