| name | cybernetic-verification-workflow |
| description | Use when a cybernetic runtime is preparing any fixed, passing, deployed, accepted, or goal-achieved claim and must bind fresh evidence to the exact approved candidate. |
Cybernetic Verification Workflow
Purpose
Establish whether the exact approved candidate satisfies its completion claims.
Verification observes state; it does not grant itself semantic approval.
Workflow
- Enumerate the claims implied by required outcomes, result paths, live gates,
and
what_counts_as_done.
- Resolve the exact generation, candidate identity, environment, and artifact
hashes being verified.
- Run the strongest proportionate fresh checks for each claim and retain their
actual outputs and exit states.
- Reject stale, mixed-candidate, local-only, screenshot-only, or supporting-only
evidence when the claim requires stronger proof.
- Execute the required verifier and Counterexample Gate. A structural PASS is
not a semantic PASS.
- Report the proved scope, unsupported claims, and remaining gaps precisely.
Evidence Rule
Tests are one possible evidence source, not the default definition of quality.
Prefer direct end-to-end observations when they prove the user-visible or
cross-component state more efficiently.
Boundaries
- Do not infer success from changed code, an agent report, or an old run.
- Do not combine evidence from different candidates into one PASS.
- Do not set
goal_achieved: true unless all required verifier and semantic
review conditions for that exact candidate are satisfied.
