validate

# Validate Independently judge one exact subject against the acceptance in its existing bead or caller source, write one durable verdict, and stop. Validate is the sole verdict writer. It never asks the model to reconstruct Plan or Candidate packets. ## Preconditions - The intent source is available as a caller-owned artifact or runtime-owned content-addressed snapshot; its acceptance digest is derived automatically. - The subject manifest still matches the subject. - Author and validator context IDs are explicit. - Freshness is explicitly attested with `source: runtime | caller` and an attester identity. Missing, colliding, or unattested identities produce `NOT_PROVEN`. This is a declared trust fact, not cryptographic proof that contexts were isolated. ## Cross-model fresh validator (caller-elected) A caller may request that the fresh validator run on a different model than the author. Dispatch via the controller-session recipe in the `agent-native` model-dispatch recipe (`codex-exec` and/or `ntm`, probed at runtime). Record author and validator `model_identity` in evidence refs and freshness attestation notes — do not change `verdict.v2` schema. If the requested validator model has no live adapter, disclose the unsatisfied diversity request and proceed same-model; never invoke `claude -p` / `claude --print`. Single fresh validator remains the default shape. ## Mutating-check quarantine Before running any acceptance-listed command, classify it as read-only or sub...