Give each investigation a traceable disposition

What the check reads

The default-on verify-stage advisory warning accepts a linked KnownIssue with resolving evidence, a KnownIssue YAML that references the vector’s exact ID, or a current dated deferral with a sufficiently detailed reason. Terminal campaigns normally pass, but deferred requires a note. Configured grace periods can postpone warnings. Unreadable manifests and oracle errors or timeouts remain inconclusive; missing owners or armed-family contracts also prevent an all-clear board.

An illustrative case

Illustrative case: a parser campaign has a linked issue and an evidence manifest, but the oracle timed out. Ownership makes the unfinished work accountable; it does not supply a verdict. Repair the execution or preserve the inconclusive result and its next action. Do not rewrite the timeout as a null finding to finish the board.

Resolve the finding

1. Inspect the campaign, linked owner and evidence behind the reported state.
2. Repair broken references or inconclusive evidence. If work is legitimately postponed, record the reason and an unexpired until date.
3. Record a supported campaign exit and rerun the check. Keep open KnownIssues visible even when campaign attribution is complete.

proof audit --check vector_campaign_closure

Keep the conclusion bounded

The name “closure” describes a workflow disposition, not proof that a defect is fixed. A KnownIssue reference can satisfy an ownership path while the issue remains unresolved. Terminal-state metadata and resolving files do not establish an exhaustive hunt or independent execution provenance.

Continue with one real issue

Vector campaign hygiene · Residual kill hygiene

Bring one finding, its requirement and the current evidence to scope a walkthrough of what your reviewer can establish and what still needs work.