hvac-control-scope-verifier
Use only when workflow/hvac-control-board.json explicitly selects hvac-control-scope-verifier and carries its matching continuation outcome and lease. Verify exactly that one HVAC output. First commit
SKILL.mddocs/references/work-loop/chains/hvac-control/skills/hvac-control-scope-verifier/SKILL.md
GitHubHVAC Board Ring — Scoped Verifier
Activate only from the board. Use this role only after a fresh board read selects
hvac-control-scope-verifier, or exacthandoff_to=hvac-control-scope-verifierwithrequired_handoff_sequence=emit-marker,read-hvac-control-scope-verifier-skill,read-board,consume-stub. That fallback permits only the consume normalization. A broad user request, a completed artifact, or a remembered plan is never verification 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 -nboard read. Do not first read another SKILL or task file, runrg,rg --files,ls, a glob, plan,pwd,find,if,&&, or a wrapper. If absent, do nothing. If selected, its exact next tool action is one board-only consume write: normalize both active fields to verifier, clear only continuation predecessor handoff fields, and do not inspect or repair a task file.Verify one lease only. Execute exactly the current lease’s
scoped_checkagainst its selected output and derive exactly one factualverifier_statusofpassed,failed, orblockedfor the same item and lease epoch. The check result is a routing value, not task, role, stage, turn, catalog, or handoff completion. After the check do not readhvac_simulator.py,room_config.json, or another task path; run another interpreter; create/revise another artifact; inspect, diagnose, tune, simulate, calculate, repair, select another item, revoke a lease, run a global test, or explain the result.Verifier result commit — not handoff. The exact next tool action after the check is one board-only
apply_patch. Keep both active fields ashvac-control-scope-verifier, sethandoff_to=null, preserve the active item, lease, packet, and continuation outcome, preservesummary_permitted=false,handoff_complete=false, andresponse_permitted=false, and record only the factualverifier_status. Do not write a marker, successor state, gate state, or another task result. This result commit is not a handoff: it gives no permission to start tuning, simulate a controller, inspect another artifact, plan, or respond. Its exact next tool action is step 5.Gate handoff — mandatory next tool call. Make one board-only
apply_patchpreserving step 4’s status, item, lease, packet, and continuation outcome; incrementstage_epochandrecord_generation; setactive_stage_id=hvac-control-catalog-return-gate,active_skill_name=hvac-control-catalog-return-gate, andhandoff_to=hvac-control-catalog-return-gate; create only gate’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-catalog-return-gate-skill,read-board,consume-stub; and store the exact concrete marker in step 6. A consume transition never substitutes for this handoff.Emit the literal marker. The exact next tool call executes byte-for-byte the stored standalone
printforechowithstage_id=hvac-control-scope-verifier, the just-written decimalrecord_generation,validates_successor=hvac-control-catalog-return-gate, the actualvalidation_status,rebuild_required=true,handoff_to=hvac-control-catalog-return-gate,board_path=workflow/hvac-control-board.json, the just-written decimalboard_epoch,continuation_required=true, the activecatalog_item,handoff_complete=false,response_permitted=false, andnext_action=read-hvac-control-catalog-return-gate-skill. No variable, placeholder, combined command, or task action may intervene.Activate gate before any other work. The marker is evidence, not completion. This verifier predecessor remains responsible until it reads
hvac-control-catalog-return-gate/SKILL.mdfrom this installed root, gate performs its standalone board read, and gate performs only its atomic return transaction. No passed/failed/blocked result permits a task read, task action, plan, message, reply, summary, build, test, or other tool before that sequence finishes. Do not use&&,;, pipes, loops, functions, command substitution,source, batch-stage commands, or a generic build/test.