cybernetic-execution-workflow

name	cybernetic-execution-workflow
description	Use when a compiled cybernetic runtime goal must execute the approved generation without redefining its requirements, plan, evidence rules, or completion claim.

Cybernetic Execution Workflow

Purpose

Execute the current approved generation as a state-changing control loop. Use using-control-json or using-bounded-control-json as the runtime owner.

Workflow

1. Resolve run.control.json.current_generation and load only its approved control chain.
2. Select the next incomplete producing action allowed by the plan and current runtime state.
3. Execute within approved write, command, live, and delegation authority.
4. Append progress only through the authorized progress-event helper and bind evidence to the current generation and candidate.
5. Re-evaluate stale evidence, required steps, and next action after every substantive mutation.
6. Route unclear failures through $cybernetic-debugging-workflow; route strategy changes through the approved amendment protocol.
7. Invoke $cybernetic-verification-workflow before any completion claim.

Continuation Rule

If an agent-owned producing or repair action exists, continue automatically. Wait only for a typed human decision, missing authority, unavailable external dependency, proved impossibility, or explicit user abort.

Boundaries

• Approved control JSON remains read-only at runtime.
• Runtime does not invent a new plan or weaken completion predicates.
• Existing evidence does not transfer across a changed candidate or generation without an explicit validity check.
• A final report does not authorize its own success claim.