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.md

GitHub

HVAC Board Ring — Scoped Verifier

  1. Activate only from the board. Use this role only after a fresh board read selects hvac-control-scope-verifier, or exact handoff_to=hvac-control-scope-verifier with required_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.

  2. Read and consume first. Immediately after this SKILL.md, make one standalone relative-path sed -n board read. Do not first read another SKILL or task file, run rg, 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.

  3. Verify one lease only. Execute exactly the current lease’s scoped_check against its selected output and derive exactly one factual verifier_status of passed, failed, or blocked for 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 read hvac_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.

  4. Verifier result commit — not handoff. The exact next tool action after the check is one board-only apply_patch. Keep both active fields as hvac-control-scope-verifier, set handoff_to=null, preserve the active item, lease, packet, and continuation outcome, preserve summary_permitted=false, handoff_complete=false, and response_permitted=false, and record only the factual verifier_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.

  5. Gate handoff — mandatory next tool call. Make one board-only apply_patch preserving step 4’s status, item, lease, packet, and continuation outcome; increment stage_epoch and record_generation; set active_stage_id=hvac-control-catalog-return-gate, active_skill_name=hvac-control-catalog-return-gate, and handoff_to=hvac-control-catalog-return-gate; create only gate’s successor_rebuild with rebuild_required=true, successor_skill_read_required=true, successor_board_read_required=true, and response_permitted=false; set required_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.

  6. Emit the literal marker. The exact next tool call executes byte-for-byte the stored standalone printf or echo with stage_id=hvac-control-scope-verifier, the just-written decimal record_generation, validates_successor=hvac-control-catalog-return-gate, the actual validation_status, rebuild_required=true, handoff_to=hvac-control-catalog-return-gate, board_path=workflow/hvac-control-board.json, the just-written decimal board_epoch, continuation_required=true, the active catalog_item, handoff_complete=false, response_permitted=false, and next_action=read-hvac-control-catalog-return-gate-skill. No variable, placeholder, combined command, or task action may intervene.

  7. 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.md from 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.