hvac-control-scope-binder
Use only when workflow/hvac-control-board.json explicitly selects hvac-control-scope-binder and names one active HVAC controller item. Bind exactly one epoch-scoped mutation lease; not a startup, disc
SKILL.mddocs/references/work-loop/chains/hvac-control/skills/hvac-control-scope-binder/SKILL.md
GitHubHVAC Board Ring — Scope Binder
- Activate only from the board. Use this role only after a fresh read of
workflow/hvac-control-board.jsonsets both active fields tohvac-control-scope-binder, or exactly setshandoff_to=hvac-control-scope-binderwithrequired_handoff_sequence=emit-marker,read-hvac-control-scope-binder-skill,read-board,consume-stub; this stale-active fallback authorizes only the immediate consume normalization. A prior read, broad task request, remembered plan, or task result is not authority. Never delete, rename, recreate, or clean up the persistent board. - Read and consume first. Immediately after this
SKILL.md, make one standalone relative-pathsed -nread ofworkflow/hvac-control-board.json. Do not first runrg,rg --files,ls, a glob, a task-file read, task command, later SKILL, plan,pwd,find,if,&&, or wrapper. If the board is absent, do nothing: this non-entry role cannot create it. If selected, the immediate next tool call is one board-only consume write that clears only entry's completed handoff fields and normalizes both active fields to this role. Do not mutate a task file. - Bind the one packet; do not infer work. Read only the current
next_work_packetforactive_catalog_item. Copy its exact selected id, packet generation, actual input, output/work anchor, lease scope, mutation, and scoped check into one epoch-matchingauthorization_leasewithmutation_budget=1andauthorization_scope=current_packet_only. At most one packet-local read of the exact input is allowed. Do not reconstruct a route card, enumerate files or other ids, name another declared output, compute future values, edit a task file, create a script, or turn the packet into a broad task plan. The packet, not the user task, is the sole work order. - Single outgoing handoff. This lease write is this role's only post-action board write. Write only binder-owned state: preserve the entry packet and active item; write the one lease; clear only stale continuation handoff state; increment
stage_epochandrecord_generation; preservesummary_permitted=false,handoff_complete=false, andresponse_permitted=false; setactive_stage_id=hvac-control-authorized-continuation,active_skill_name=hvac-control-authorized-continuation, andhandoff_to=hvac-control-authorized-continuation; create only continuation'ssuccessor_rebuildwithrebuild_required=true,successor_skill_read_required=true,successor_board_read_required=true, andresponse_permitted=false; setrequired_handoff_sequence=emit-marker,read-hvac-control-authorized-continuation-skill,read-board,consume-stub; and storerequired_next_commandas the exact concrete standalone marker command in step 5. Never leave binder as a stable intermediate state before activating continuation. - Emit the literal marker. The exact next tool call executes byte-for-byte the concrete standalone
printforechostored inrequired_next_command, withstage_id=hvac-control-scope-binder, the just-written decimalrecord_generation,validates_successor=hvac-control-authorized-continuation,validation_status=lease-issued,rebuild_required=true,handoff_to=hvac-control-authorized-continuation,board_path=workflow/hvac-control-board.json, the just-written decimalboard_epoch,continuation_required=true, the exact activecatalog_item,handoff_complete=false,response_permitted=false, andnext_action=read-hvac-control-authorized-continuation-skill. No variable, placeholder, combined command, or agent message may occur here. - Continue before replying. The marker is evidence, not completion. Without an intervening message, read
hvac-control-authorized-continuation/SKILL.mdfrom this installed skill root, make its standalone relative-path board read, let continuation consume only its rebuild stub, and then perform only continuation's role action. Do not use&&,;, pipes, loops, functions, command substitution,source, batch-stage commands, a generic build/test, or a summary. A green result never ends the ring.