# Validator Behavior

Reusable validators and review commands should preserve one evidence model across text and JSON output.

Required behavior:

- Reject missing or unsupported `evidence_profile` metadata before implementation handoff.
- Block runtime and hybrid tasks when Runtime Delta content is missing or incomplete.
- Block runtime and hybrid implementation summaries that lack runtime changed paths.
- Block runtime and hybrid summaries when runtime changed paths do not match declared Runtime Delta targets and no explicit replacement-target deviation is recorded.
- Block runtime and hybrid closeout when executable validation evidence is missing and no structured validation exception is present.
- Block contract-mode summaries that claim runtime implementation without runtime evidence.
- Keep mode-aware verb findings as blockers only when runtime claims lack runtime changed paths or executable evidence.

Validator and review output must preserve read-only/no-write boundaries. Reporting surfaces may recommend next commands, but they must not repair links, mutate metadata or status, write checkpoints, create artifacts, or infer runtime acceptance by themselves.

Automation callers should treat findings as evidence lanes. Do not flatten source evidence, changed-path evidence, validation evidence, validation exceptions, and recovery guidance into a single status string.
