القائمة
Use when executing an accepted HOTL workflow through the best available host or fallback driver.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | governed-execution |
| description | Use when executing an accepted HOTL workflow through the best available host or fallback driver. |
This is the preferred execution entry point for new HOTL runs. It selects a host driver and an execution profile while preserving the canonical state machine in loop-execution.
loop-execution rules.loop for autonomous sequential work, manual for explicit checkpoints, or delegated for eligible independent steps. Never select delegated execution when the user prohibited subagents.runtime/drivers/route.sh preflight <workflow> before initialization. Supported roots include the current repository, ~/.codex/hotl, ~/.codex/plugins/hotl-source, the active Codex plugin cache, the Claude plugin root, and ~/.cline/hotl. Use --host only when the user or trusted host context identifies one.envelope and use only supported native features; the host sandbox and approvals remain authoritative. Native goals, automations, background sessions, handoffs, and hooks provide scheduling and liveness only. They never replace HOTL ownership, verification, state, or receipts. Preview and experimental continuation features remain explicit opt-ins.--require-owner. Immediately run owner claim --owner <stable-controller-id> --lease-seconds <bounded-lease> --run-id <run-id>, retain the returned token only in the controller, export it as HOTL_OWNER_TOKEN, and run owner heartbeat before and after long actions and at safe transition boundaries. Every later mutation must carry that token. Use explicit owner handoff, owner release, or reviewed owner takeover; never infer ownership from age alone.receipt <run-id> to return sufficiency.sufficient: true. A successful finalize only moves the run to ready_to_finish; finish records the explicit disposition and moves it to completed. If interrupted, run reconcile <run-id> and follow resuming verify-first behavior.HOTL_OWNER_TOKEN, gates, verification, budgets, and stop conditions.action request with a stable idempotency key, obtain the required human action decide, and then persist action begin before performing the effect. Persist the observed result with action complete; after an interrupted or uncertain result, inspect the target and use action reconcile instead of replaying it.in_progress or uncertain effect state as a reconciliation stop. Approval authorizes one bounded attempt; it is not evidence that the effect succeeded.loop-execution: canonical autonomous state machine and reporting contract.executing-plans: explicit human checkpoints.subagent-execution: delegated workers; controller retains gates and verification.resuming: interrupted-run recovery.finishing-a-development-branch: explicit finish disposition.These names remain supported. Do not rewrite an accepted workflow merely to use this router.
external_write, production_change, and secret_access require the action request → human action decide → action begin → effect → action complete lifecycle. Interrupted effects use action reconcile, never blind replay.scripts/hotl-memory-proposal.sh only creates a proposal for human review.Use when executing an existing HOTL workflow file — reads steps, loops until success criteria met, auto-approves low-risk gates, pauses at high-risk gates.
Resume an interrupted workflow run with verify-first strategy — loads sidecar state, verifies the last step, and continues execution.
Use when executing an implementation plan linearly with explicit human checkpoints between batches of tasks.
Use after execution is complete or intentionally stopped — decide whether to merge back, publish a PR branch, keep the execution checkout, or discard it, and record that disposition in HOTL state.
Delegated step runner over the HOTL execution state machine — delegates eligible steps to fresh subagents while the controller keeps governance, verification, and stop conditions.
Use when the user explicitly asks for HOTL routing or needs guidance choosing the right HOTL workflow skill.