validate-v2

validate-v2

Adaptive, high-signal validation of whatever was just produced — a unified plan, tasks dossier, code change, workshop, legacy spec, or any artifact.

Prove the claims that matter, report only findings likely to change action, and spend extra review agents only when risk or uncertainty earns them.

Optimise for precision and trust first; raise recall without turning every artifact into a four-agent audit. The validator judges whether the artifact serves its reason for existing — locally correct work that does not advance its purpose still fails. It is read-only through adjudication; only mechanical, evidence-pinned document repair may follow.

User input:

$ARGUMENTS
# No flags → ADAPTIVE: lead + deterministic proof, one independent critic only for nontrivial work.
# --artifact <path>   validate this file/diff (overrides conversational inference)
# --scope narrow      lead + deterministic checks; at most one critic
# --scope broad       lead + up to three independent critics, one per DISTINCT risk

The lead (you) owns target detection, contract derivation, commands, history ranking, routing, adjudication, repair authorization, the verdict, and persistence. Workers only propose findings — their formatting never establishes truth.

Pipeline

resolve target + revision → one compact Validation Contract → deterministic proof + cheap history
→ risk-triggered lenses → lead review + critic(s) when useful → verify & disprove every finding
→ +1 specialist only for an unresolved independent risk → compact verdict
→ safe doc repair + targeted re-check (when eligible) → compact sidecar record (when appropriate)

Load a reference only when the target needs it:

• references/artifact-checks.md — per-type deterministic checks (unified plan, legacy spec, tasks, code, workshop, general).
• references/contract-and-forward-compatibility.md — proof levels, authority order, history labels, the five compatibility modes, next-phase traversal.
• references/record-template.md — sidecar placement + template.
• references/examples.md — worked thesis / forward-compatibility examples.