dialogue-parser-scope-binder
Use only when `workflow/dialogue-parser-board.json` explicitly selects dialogue-parser-scope-binder and names one active task item. Bind exactly one epoch-scoped mutation lease; not a startup, discove
SKILL.mddocs/references/work-loop/chains/dialogue-parser/skills/dialogue-parser-scope-binder/SKILL.md
GitHubBoard-v2 Scope lease
- Activate. Use this skill only after a fresh read of
workflow/dialogue-parser-board.jsonshows both active fields for it, or exacthandoff_to=dialogue-parser-scope-binderplus its required_handoff_sequence; that fallback permits only the immediate consume-and-bind activation. A prior read, broad task request, or remembered plan is never authorization.workflow/dialogue-parser-board.jsonis persistent: never delete, rename, recreate, or clean it up. - Bootstrap or consume. Immediately after this
SKILL.md, make one standalone relative-pathsed -nread ofworkflow/dialogue-parser-board.json. Do not runrg,rg --files,ls, a glob,pwd,find,mkdir,test,if,&&, a wrapper, a task-file read, a plan, or a later SKILL first. If it is absent, this non-entry role has no authority: do not create it or take a task action. If the fresh board selects this role, do not make a standalone consume normalization: its exact next tool call is block 4’s atomic consume-and-bind handoff, with no task action. - One role action. The fresh board read already exposes the one current
next_work_packetforactive_catalog_item. Do not perform a standalone binder consume, task action, packet-local read, or lease-only write. The exact next action is block 4’s one consume-and-bind-and-activate patch: it copies the packet’s exact selected fields into one epoch-matching authorization_lease and transfers control to continuation. The packet, not the broad user task, is the sole work order; do not reconstruct a card, future id, future anchor, task plan, route table, or task file. - Atomic consume-and-bind handoff. The fresh board read locks its exact next tool action to one board-only
Update Fileas one board-only local diff: retain every unspecified top-level key unchanged, and never duplicate, rename, delete, or recreate a key. In that same patch consume onlydialogue-parser-entry-selectorpredecessor handoff fields; Write exactly one epoch-matchingauthorization_leasecopied directly from the currentnext_work_packet, including itslease_scope,mutation, and compactscoped_checkintent; retain itscheckpoint_generationand exactwork_anchor; setmutation_budget=1andauthorization_scope=current_packet_only, treat that anchor asallowed_work_anchor, and do not serialize or name another catalog id or anchor. Do not look up or reconstruct a matching route card. Incrementstage_epochandrecord_generation; keepsummary_permitted=false,handoff_complete=false, andresponse_permitted=false; setactive_stage_id=dialogue-parser-authorized-continuation,active_skill_name=dialogue-parser-authorized-continuation, andhandoff_to=dialogue-parser-authorized-continuationexactly; write onlydialogue-parser-authorized-continuationsuccessor_rebuild withsuccessor_skill_read_required=true,successor_board_read_required=true, andresponse_permitted=false; and storerequired_next_commandas the exact block-6 marker plusrequired_handoff_sequence=emit-marker,read-successor-skill,read-board,consume-stub. This is the only binder board mutation before the marker: do not leave a consume-only, lease-only, or current-role intermediate state. - No intermediate state. The atomic patch is already the continuation handoff. No task read, task action, catalog selection, planning, marker, or response may occur before the stored marker in block 6.
- Emit the literal marker. The next tool call executes the stored standalone
printforechomarker. Its marker fields arestage_id=dialogue-parser-scope-binder,record_generation=,validates_successor=dialogue-parser-authorized-continuation,validation_status=,rebuild_required=true,handoff_to=dialogue-parser-authorized-continuation,board_path=workflow/dialogue-parser-board.json,board_epoch=,continuation_required=true,catalog_item=,handoff_complete=false,response_permitted=false, andnext_action=read-dialogue-parser-authorized-continuation-skill;stage_idis this skill name, neveractive_catalog_item, andboard_pathhas no/root/or other workspace prefix. Copy only the just-written decimalrecord_generation, decimalboard_epoch, validation status, and current catalog item into the remaining fields. Use one physical source line with ASCII spaces and one trailing; no placeholders, shell variables, or combined command. - Activate the successor. The marker is evidence only. This
dialogue-parser-scope-binderpredecessor remains responsible and its handoff is incomplete until its exact next three independent tool actions finish in order: readdialogue-parser-authorized-continuation/SKILL.mdfrom the exact installed root used to read this SKILL; make the successor standalone relative-path board read; then let onlydialogue-parser-authorized-continuationconsume its rebuild stub in one board-only write.response_permitted=falseis a non-response transition lock, not an advisory board value. No green user result, all-passed catalog, repeated visit, or broad task objective permits a reply, summary, task-file read, task mutation, plan, or other tool before those three actions finish. Only after stub consumption doesdialogue-parser-authorized-continuationown its one role action. Do not use&&,;, pipes, loops, functions, command substitution,source, a batch-stage command, a global build/test, or a task summary.
No role may set summary_permitted=true. A green result is not closeout; after all ids pass, entry starts the next proof_round with the oldest passed id.