---
name: verification
description: "Use when any role is about to claim a gate, review, eval, lifecycle, or task completed, passed, fixed, or ready."
---

# verification: evidence before completion

## Contract

Require fresh evidence for the exact predicate. Prior approval, implementer reports, self-attestation and process exit are inputs, not completion. Independently read the current candidate and Native state.

## Gate function

Before claiming completion:

1. **Identify.** Bind predicate, candidate/worktree, path manifest, role/task, startup bundle, command/environment, expected exit and semantic marker, eval/rubric threshold, and protected-state hashes.
2. **Run.** Execute the full current command, not a subset, cached output or prose check. Preserve stdout/stderr, exit status, timing and raw evidence.
3. **Read.** Parse complete output. Zero without the required marker/artifact/postcondition fails. Nonzero is RED only for its declared failure reason.
4. **Compare.** Recompute commit, worktree, owned paths, task, role, skill/carrier/compiler, rubric and Native/protected-state hashes. Reject replay, wrong binary, hidden files and post-review mutation.
5. **Report.** Record command, actual status, semantic result, evidence paths/hashes, residual risk and next action. Missing evidence never becomes green.

Rerun after every redo or product-byte mutation. Ambiguity requires routing, not favorable interpretation.

## Root-owned gate execution

Bounded child shell remains denied. Request the bound root's gate through native host messaging, via Conductor when present. Root independently matches the above facts, executes with its authority, and returns raw output, exit, timing, executor and input/output hashes. The child checks them; observed RED must precede production edits.

This is not a Native gate API, parent source edits, hook bypass or root impersonation. Missing root/message route, stale inputs or missing process evidence stays blocked. Authored messages/JSON are evidence indexes, not proof.

## Inheritance and binding

Any canonical role may load `verification` explicitly at completion; it is never a startup replacement. Native binds the exact skill ID and complete sorted path/mode/byte bundle digest to current root/profile or child authority. Missing, stale, replayed, cross-install or mismatched bindings fail closed.