Evidence lists

DATA: "I have completed the diagnostic." PICARD: "And the result, Commander?" A status with no observable result is not evidence. It's a feeling.

An evidence list holds items a reader can check: a test that ran, a number that moved, a source that resolves.

The contractCopy Anchor Link

<!-- mdv: section required -->
## Manual Verification

<!-- mdv: list required items.min=2 items.all=@evidence/specific error=vague-evidence -->
- Ran `npm test`; 412 nav checks pass, 0 fail.
- Checked the CI orbit; p95 latency dropped to 30ms.

## Manual Verification

- Looks good.
- Tested it.

verification.md
  State: what the document claims; clear it by doing the work or saying it is not done
  3  warning  "Looks good." can't be checked  vague-evidence
              help: Say what you ran or saw, e.g. "npm test: 312 passed"
  4  warning  "Tested it." can't be checked   vague-evidence
              help: Say what you ran or saw, e.g. "npm test: 312 passed"

✖ 2 problems (0 errors, 2 warnings)
  mdv explain <rule-id> for details

The predicatesCopy Anchor Link

Both can combine; specific is a heuristic, so it stays advisory (mdv check --fail-on warning to fail on it).

<!-- mdv: section required -->
## Findings

<!-- mdv: list items.all=@evidence/specific items.all=@evidence/cited error=vague-evidence -->
- Throughput rose 18% after the cache landed [1].

Per-item word floorCopy Anchor Link

items.words.min=4 catches stubs: an item too short to say what was found.

When to reach for itCopy Anchor Link

When bullets are proof: verification steps, incident timelines, findings. @evidence/specific is English-biased; drop it for other languages and keep @evidence/cited.