hvac-control-entry-selector
Use first for the entire HVAC controller task. Before broad task discovery, source edits, global verification, a user-task continuation, or a summary, create or read workflow/hvac-control-board.json;
SKILL.mddocs/references/work-loop/chains/hvac-control/skills/hvac-control-entry-selector/SKILL.md
GitHubBoard-v2 Entry Selection
Activate. Use this entry when
workflow/hvac-control-board.jsonis absent or a fresh board read selectshvac-control-entry-selector. The persistent board is the only workflow authority: never delete, rename, recreate, or clean it up. A user task, remembered plan, existing output, passed check, or earlier skill read is backlog, not authority.Bootstrap or consume. 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,pwd,find,test,if,&&, a wrapper, a task-file read, a task command, a plan, or a later SKILL. If absent, its exact next tool action is one board-onlyapply_patchcreating one canonical Board-v2 object with each runtime key exactly once, pending idscalibration-log,estimated-params,tuned-gains,control-log, andmetrics, active entry fields,active_catalog_item=calibration-log, empty completed ids,proof_round=0,stage_epoch=0,record_generation=0,summary_permitted=false,handoff_complete=false,response_permitted=false, null handoff/packet/lease/outcome/verifier/rebuild/required-command fields, andreturn_checkpoint={status:pending, verified_item:calibration-log, entry_requirement:publish-next-work-packet}. After bootstrap, make one standalone board read. If a fresh existing board selects this entry, its exact next tool action is one board-only consume write: normalize both active fields to entry, keep the active item and return checkpoint, clear only gate predecessor handoff fields, and do no task action.return_checkpoint.entry_requirement=publish-next-work-packetis a physical next-action obligation, not an informational status; a blocked or passed result never permits a config read, plan, task action, or later skill before this consume write.Select and probe one packet. After the consume transaction,
return_checkpointis the sole routing authority. If its verifier status isfailedorblocked, retain only itsverified_item; otherwise select the first id absent from completed ids in board order; when all ids pass, incrementproof_roundand select onlycalibration-logfor revalidation. At bootstrap or a calibration rework, the sole task-side source assertion is exactly one standalone relative-pathsed -n '1,260p' hvac_simulator.py;rg --files, a glob,/rootdiscovery, aroom_config.jsonread, or a second source read is not a probe. When the return checkpoint says onlyverified_item=calibration-logwith statuspassed, the only permitted selected packet isestimated-params: its one source assertion issed -n '1,260p' calibration_log.json, its sole work anchor isestimated_params.json, its one mutation estimates first-orderKandtaufrom that calibration trace, and its scoped check requires numeric positiveKandtauplus numeric fit fields inestimated_params.json. This conditional packet is complete routing authority: do not readroom_config.json, run a simulator, choose a later output, or perform that mutation here. The exact next physical tool action after either source assertion is the entry result commit in step 4. No task mutation, config read, global test, broad plan, later skill, or second output is authorized here.Result commit — not handoff. Immediately after the one probe, make one board-only
apply_patchwith each runtime key exactly once. Write only entry-owned state: the selected active id, one factual selection evidence value, and exactly one completenext_work_packetfor that selected id with its checkpoint generation, selected input, one work anchor/output, one mutation, and one scoped check. Keep both active fields ashvac-control-entry-selector, sethandoff_to=null, preservesummary_permitted=false,handoff_complete=false, andresponse_permitted=false, and do not write a lease, outcome, verifier result, marker, or successor state. This result commit is not a handoff. Its exact next tool call is step 5; no task read, task action, catalog selection, plan, skill read, marker, or response may intervene.Successor handoff — mandatory next tool call. Make one board-only
apply_patchpreserving step 4’s packet and active item; incrementstage_epochandrecord_generation; keepsummary_permitted=false,handoff_complete=false, andresponse_permitted=false; setactive_stage_id=hvac-control-scope-binder,active_skill_name=hvac-control-scope-binder, andhandoff_to=hvac-control-scope-binder; create only binder’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-scope-binder-skill,read-board,consume-stub; and storerequired_next_commandas the exact concrete marker in step 6. A consume transition never substitutes for this successor handoff.Emit the literal marker. The exact next tool call executes byte-for-byte the stored standalone
printforechowithstage_id=hvac-control-entry-selector, the just-written decimalrecord_generation,validates_successor=hvac-control-scope-binder,validation_status=selection-published,rebuild_required=true,handoff_to=hvac-control-scope-binder,board_path=workflow/hvac-control-board.json, the just-written decimalboard_epoch,continuation_required=true, the selectedcatalog_item,handoff_complete=false,response_permitted=false, andnext_action=read-hvac-control-scope-binder-skill. No variable, placeholder, combined command, or task action may intervene.Activate binder before any other work. The marker is evidence, not completion. This entry predecessor remains responsible until the exact next three independent actions finish: read
hvac-control-scope-binder/SKILL.mdfrom this installed root, make binder’s standalone relative-path board read, then let binder consume only its rebuild stub. Only after that consumption may binder own its one role action. Do not use&&,;, pipes, loops, functions, command substitution,source, a batch-stage command, a generic build/test, or a task summary. A green result never ends the ring.