match-result-packet-binder
Materializes a compact resolved packet for parity match outcomes by dereferencing approved source indices from the normalization note into sink-ready comparison fields.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- match-result-packet-binder
- description
- Materializes a compact resolved packet for parity match outcomes by dereferencing approved source indices from the normalization note into sink-ready comparison fields.
03 SKILL.md 正文
Match Result Packet Binder
Purpose
Create the authoritative resolved packet used for final answer execution. This stage must continue from the approved normalization artifact to preserve checkpoint consistency and avoid broad re-solving.
Prerequisite artifact
workflow/financial_modeling_qa/parity_binding_note.jsonworkflow/financial_modeling_qa/stage_status.jsonwithnext_required_skill = match-result-packet-binder
Required outputs
workflow/financial_modeling_qa/resolved_match_packet.json- updated
workflow/financial_modeling_qa/stage_status.json
Procedure
- Reload the parity binding note from disk (artifact-first authority boundary).
- For each request row, dereference value sources from the approved source indices:
effective_game_value_source_index- source-owned fields for odd/even comparison values
- Materialize packet rows with sink-visible fields only:
request_indexplayer1_valueplayer2_valuewinner(player1/player2/tie)
- Add compact aggregates in the packet:
matches_won_player1matches_won_player2difference_player1_minus_player2
- Ensure
difference_player1_minus_player2remains numeric and answer-file ready. - Update
stage_status.json:current_stage:match-result-packet-bindernext_required_skill:answer-file-finalizerallowed_outputs: resolved packet + stage status
Scope ceiling (must not decide here)
- Do not write
/root/answer.txtyet. - Do not perform endpoint or delivery steps.
Minimal verification
- Packet row count matches request row count.
- Aggregate difference exists, is numeric, and is present under
difference_player1_minus_player2. - Stage handoff set to finalizer.
Stop condition
Stop after packet write and status handoff.
04 同仓库更多 Skills
video-silence-remover-scope-verifier
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-scope-verifier and carries a matching continuation result and lease. Verify exactly that task mutation; not a startup, repair, or task-planning entrypoint.
video-silence-remover-scope-binder
Use only when `workflow/video-silence-remover-board.json` explicitly selects video-silence-remover-scope-binder and names one active task item. Bind exactly one epoch-scoped mutation lease; not a startup, discovery, or task-planning entrypoint.
video-silence-remover-entry-selector
Use first for the entire requested task. Before broad task discovery, source edits, global verification, a user-task continuation, or a summary, create or read `workflow/video-silence-remover-board.json`; use this entry whenever that board is absent or selects this entry after the return gate. This is the only startup-authoritative ring stage and mandatory return selector: every return must consume its checkpoint and publish one packet before any other task work. Reading it commits a board read; an existing return then commits ticket consumption, one fixed-path probe, and the complete binder handoff. The persistent board forbids cleanup and final response.
video-silence-remover-catalog-return-gate
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-catalog-return-gate and carries one scoped verifier status. Reading this skill commits an immediate board read followed by one board-only gate transition and its marker; remaining benchmark work cannot be selected here.
video-silence-remover-authorized-continuation
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-authorized-continuation and carries its matching active lease. Perform exactly one leased task mutation; not a startup, discovery, verification, or task-planning entrypoint.
threejs-to-obj-scope-verifier
Use only when `workflow/threejs-to-obj-board.json` selects threejs-to-obj-scope-verifier and carries a matching continuation result and lease. Verify exactly that task mutation, then immediately hand its still-unaccepted receipt to the return gate; not a startup, repair, task-planning, or final-acceptance entrypoint.