governed-execution
Use when executing an accepted HOTL workflow through the best available host or fallback driver.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- governed-execution
- description
- Use when executing an accepted HOTL workflow through the best available host or fallback driver.
03 SKILL.md 正文
HOTL Governed Execution
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.
Required behavior
- Resolve and lint the workflow using
loop-executionrules. - Select the profile from user intent:
loopfor autonomous sequential work,manualfor explicit checkpoints, ordelegatedfor eligible independent steps. Never select delegated execution when the user prohibited subagents. - Locate the router in the active HOTL installation, then run
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--hostonly when the user or trusted host context identifies one. - If preflight resolves fallback, follow the chosen existing execution skill with the generic driver. If it resolves native, obtain
envelopeand 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. - Launch new driver-managed runs with
--require-owner. Immediately runowner claim --owner <stable-controller-id> --lease-seconds <bounded-lease> --run-id <run-id>, retain the returned token only in the controller, export it asHOTL_OWNER_TOKEN, and runowner heartbeatbefore and after long actions and at safe transition boundaries. Every later mutation must carry that token. Use explicitowner handoff,owner release, or reviewedowner takeover; never infer ownership from age alone. - Persist every step, verification, gate, action decision, effect outcome, budget observation, finalize, and finish transition through the selected driver. Host UI or chat text is never state.
- Before claiming success, require
receipt <run-id>to returnsufficiency.sufficient: true. A successfulfinalizeonly moves the run toready_to_finish;finishrecords the explicit disposition and moves it tocompleted. If interrupted, runreconcile <run-id>and followresumingverify-first behavior.
Long-running controller contract
- The controller, not the host session UI or a delegated worker, owns
HOTL_OWNER_TOKEN, gates, verification, budgets, and stop conditions. - Before a sensitive external effect, run
action requestwith a stable idempotency key, obtain the required humanaction decide, and then persistaction beginbefore performing the effect. Persist the observed result withaction complete; after an interrupted or uncertain result, inspect the target and useaction reconcileinstead of replaying it. - Treat
in_progressoruncertaineffect state as a reconciliation stop. Approval authorizes one bounded attempt; it is not evidence that the effect succeeded. - Keep the lease renewable during long work. If the controller cannot heartbeat safely, stop at a durable boundary and hand off or release ownership.
Compatibility profiles
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.
Safety invariants
- Native mode is opt-in; executable presence alone does not prove capability.
external_write,production_change, andsecret_accessrequire theaction request→ humanaction decide→action begin→ effect →action completelifecycle. Interrupted effects useaction reconcile, never blind replay.- Unknown budget telemetry stays unknown.
- Never auto-write project memory.
scripts/hotl-memory-proposal.shonly creates a proposal for human review.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.