easd-verify

Verify and prepare EASD convergence

Repository contract

Read .evoflux/easd/config.json and its rules_file before phase work. Treat the injected EASD context as the authoritative current Run; when the owning runtime is accessible, corroborate it under runtime_directory. An isolated worktree intentionally has no checkout-local runtime copy. Confirm the common specs/ revision and Run-local accepted snapshot have the same hash. Inspect affected living knowledge sections and existing project docs without migrating them implicitly. Repository documents are the shared source of truth. Stop on a missing tracked contract, stale hash, generation conflict, or unavailable injected runtime; never reconstruct authority from chat memory or a stale database-only projection. Verify and Converge remain mandatory for both direct and planned.

Challenge the integrated result against the exact accepted specification. This skill helps gather and assess evidence; only the EASD service computes Done.

State gate

Re-read the persisted run detail, accepted revision/hash, AC matrix, missions, evidence, deviations, and convergence state on every invocation. Evaluate only the current accepted hash. Only verifying may perform the final gate; reviewing waits for the user's Run verify action. If already converged, report the existing durable result without duplicating evidence or rerunning convergence. Any other state returns to its owning phase.

Verify claims

1. Load the accepted run ID/hash, current AC matrix, risk tier, planned commands, missions, evidence, and deviations. Reject stale-spec evidence.
2. Check three dimensions: completeness of required AC/mission/command/doc coverage; correctness of behavior and scenarios; and coherence of the integrated architecture, interfaces, terminology, and current documentation.
3. Inspect the integrated result and consume independent easd-review findings where the risk/evidence policy requires them. Execute approved verification missions through EASD-bound delegation so the runtime can persist a fresh, revision-bound CompletionContract even though this phase is read-only. Re-run safe required checks and relevant negative, recovery, authorization, compatibility, smoke/liveness, and cross-layer paths. Read fresh full output and exit status before stating that a command or behavior passed.
4. Map each result to an AC and its evidence policy. Preserve machine, review, manual, and waiver provenance; never manufacture command IDs, exit codes, revisions, artifact hashes, or reviewer independence.
5. For cross-layer or critical runs, ensure review is performed by an agent or human independent of the implementation owner and covers the integrated revision rather than an abandoned worktree.
6. Reconcile adopted EASD features/, architecture/, and reference/ documents, existing project docs, localized Help, and release or migration notes where the accepted behavior requires them. Never move existing docs as an implicit verification side effect.