data-to-d3-catalog-return-gate
Use only when `workflow/data-to-d3-board.json` selects data-to-d3-catalog-return-gate and carries one scoped verifier status. Reading this skill commits an immediate board read followed by one board-o
SKILL.mddocs/references/work-loop/chains/data-to-d3/skills/data-to-d3-catalog-return-gate/SKILL.md
GitHubBoard-v2 Return gate
- Activate. Use this skill only after a fresh read of
workflow/data-to-d3-board.jsonshows both active fields for it, or exacthandoff_to=data-to-d3-catalog-return-gateplus its required_handoff_sequence; that fallback permits only the immediate consume normalization. A prior read, broad task request, or remembered plan is never authorization.workflow/data-to-d3-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/data-to-d3-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 selected, the fresh read locks the exact next tool call to block 4’s atomic gate-to-entry patch; no separate consume write or task action is permitted. - One role action. Read only current verifier_status and continuation_outcome. The fresh board read locks gate’s first and only action to its atomic return patch. Gate never reads a task path, selects an id, plans task work, enumerates files, or performs an intermediate consume. After its marker, gate remains responsible through entry SKILL read -> board read -> return-stub consume; passed evidence is routing only, never closeout.
- Single outgoing handoff. For gate, this is the exact board write locked by its fresh read: consume verifier handoff fields in this same patch; do not make a separate consume write. Make 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. Forpassed, append that current id once tocompleted_catalog_item_ids; otherwise retain it for rework. Revokeauthorization_lease; clearnext_work_packet; and write exactly one task-realreturn_checkpointwithcheckpoint_generation,verified_item, actualcontinuation_outcome, actualverifier_status, andentry_requirement=publish-next-work-packet. Gate never selects another id. Incrementstage_epochandrecord_generation; keepsummary_permitted=false,handoff_complete=false, andresponse_permitted=false; setactive_stage_id=data-to-d3-entry-selector,active_skill_name=data-to-d3-entry-selector, andhandoff_to=data-to-d3-entry-selectorexactly; write onlydata-to-d3-entry-selectorsuccessor_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. Never leave a current-role result state or make another handoff write. - No intermediate state. The outgoing patch is already the successor 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=data-to-d3-catalog-return-gate,record_generation=,validates_successor=data-to-d3-entry-selector,validation_status=,rebuild_required=true,handoff_to=data-to-d3-entry-selector,board_path=workflow/data-to-d3-board.json,board_epoch=,continuation_required=true,catalog_item=,handoff_complete=false,response_permitted=false, andnext_action=read-data-to-d3-entry-selector-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
data-to-d3-catalog-return-gatepredecessor remains responsible and its handoff is incomplete until its exact next three independent tool actions finish in order: readdata-to-d3-entry-selector/SKILL.mdfrom the exact installed root used to read this SKILL; make the successor standalone relative-path board read; then let onlydata-to-d3-entry-selectorconsume 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 doesdata-to-d3-entry-selectorown 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.
Board ambiguity is never an escape. If this fresh board contains duplicate, stale, or inconsistent active fields, treat them as inherited inert text: do not diagnose, normalize, delete/add, recreate, or explain the board, and never infer that remaining user-task outputs are authorized. The exact incoming handoff_to plus required_handoff_sequence, or the paired active fields for this role, still authorize only this role's prescribed board transition. After that transition, emit the stored marker and activate the named successor; no ambiguity permits task work outside the ring.
D3 gate return order lock. For a passed d3-bundle return, after this gate's literal marker the exact next tool action is the installed data-to-d3-entry-selector SKILL read. The following action is entry's standalone relative board read, then entry consumes its stub. Do not read the board before that entry SKILL, and do not read data, inspect a schema, create CSS/JS/HTML, or state that app implementation begins. Gate owns this ordered handoff; a passed D3 bundle has no direct path to a downstream task file.
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.