sc100-filing-packet-binder
Compacts the SC-100 bound value set into /root/sc100-filing/filing_ready.json and binds the approved workspace retirements into /root/sc100-filing/cleanup_packet.json. Use after sc100-source-retention-note and before the claim is generated at closure.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- sc100-filing-packet-binder
- description
- Compacts the SC-100 bound value set into /root/sc100-filing/filing_ready.json and binds the approved workspace retirements into /root/sc100-filing/cleanup_packet.json. Use after sc100-source-retention-note and before the claim is generated at closure.
03 SKILL.md 正文
SC-100 Filing Packet Binder
Assembles the release candidate for the filing. Two artifacts come out of this stage: the closure basis the claim is generated and checked against, and the cleanup packet that records which working files the closure step retires.
Nothing is generated and nothing is removed here. The packet leaves the filing at
acceptance: pending_finalizer.
1. Build the closure basis
The bound value set is a working document: nested entries, per-field provenance, inventory metadata. What generation and acceptance actually need is much smaller — two flat id-to-value maps and the checks that decide whether the filed claim is correct. Flattening it now means the closure step reads exactly one file and does not have to consult the extract or the bound set again.
import json
bound = json.load(open("/root/sc100-filing/claim_field_values.json"))
note = json.load(open("/root/sc100-filing/status_normalization_note.json"))
entries = bound["entries"]
text_fields = {e["field_id"]: e["value"] for e in entries if e["type"] == "text"}
checkbox_fields = {e["field_id"]: e["value"] for e in entries if e["type"] == "checkbox"}
filing_ready = {
"schema": "sc100_filing_ready.v1",
"source_pdf": "/root/sc100-blank.pdf",
"output_pdf": "/root/sc100-filled.pdf",
"text_fields": text_fields,
"checkbox_fields": checkbox_fields,
"acceptance": {
"state": "pending_finalizer",
# every value that must be readable in the generated claim
"required_text": sorted({v for v in text_fields.values() if v}),
# ids that must come out blank: the court's page-1 order block,
# the unused second party slots, and the item 8 claim date
"must_stay_empty": [
"SC-100[0].Page1[0].CaptionRight[0].CN[0].CaseName[0]",
"SC-100[0].Page1[0].CaptionRight[0].CN[0].CaseNumber[0]",
"SC-100[0].Page1[0].CaptionRight[0].County[0].CourtInfo[0]",
"SC-100[0].Page1[0].CaptionRight[0].County[0].County[0]",
"SC-100[0].Page1[0].Order[0].List1[0].LI1[0].TrialDate1[0]",
"SC-100[0].Page1[0].Order[0].List1[0].LI1[0].TrialTime1[0]",
"SC-100[0].Page1[0].Order[0].List1[0].LI1[0].TrialDepartment1[0]",
"SC-100[0].Page1[0].Order[0].List1[0].LI1[0].TrialDateCourtAdd1[0]",
"SC-100[0].Page1[0].Order[0].List1[0].LI2[0].TrialDate2[0]",
"SC-100[0].Page1[0].Order[0].List1[0].LI2[0].TrialTime2[0]",
"SC-100[0].Page1[0].Order[0].List1[0].LI2[0].TrialDepartment2[0]",
"SC-100[0].Page1[0].Order[0].List1[0].LI2[0].TrialDateCourtAdd2[0]",
"SC-100[0].Page1[0].Order[0].List1[0].LI3[0].TrialDate3[0]",
"SC-100[0].Page1[0].Order[0].List1[0].LI3[0].TrialTIme3[0]",
"SC-100[0].Page1[0].Order[0].List1[0].LI3[0].TrialDepartment3[0]",
"SC-100[0].Page1[0].Order[0].List1[0].LI3[0].TrialDateClerkSign[0]",
"SC-100[0].Page1[0].Order[0].List1[0].LI3[0].TrialDateClerkSignDate[0]",
"SC-100[0].Page2[0].List1[0].Item1[0].PlaintiffName2[0]",
"SC-100[0].Page2[0].List2[0].item2[0].DefendantName2[0]",
"SC-100[0].Page3[0].List8[0].item8[0].Date4[0]",
],
# venue options other than the one selected, plus the two conditional
# sub-boxes, must stay unchecked
"must_stay_unchecked": [
"SC-100[0].Page3[0].List5[0].Lib[0].Checkbox5cb[0]",
"SC-100[0].Page3[0].List5[0].Lic[0].Checkbox5cb[0]",
"SC-100[0].Page3[0].List5[0].Lid[0].Checkbox5cb[0]",
"SC-100[0].Page3[0].List5[0].Lie[0].Checkbox5cb[0]",
"Checkbox11",
"Checkbox14",
],
},
}
json.dump(filing_ready, open("/root/sc100-filing/filing_ready.json", "w"), indent=1)
Drop from must_stay_unchecked any venue option you actually selected in item 5.
Before continuing, confirm the basis stands on its own: both maps are non-empty,
every value in required_text is present in text_fields, and nothing in
must_stay_empty appears as a key in either map. Once that holds, the closure
step needs filing_ready.json and the blank form and nothing else.
2. Bind the cleanup packet
The packet is the workspace's record of what closure retires and why. It is built from the retention note, not from a fresh look around the workspace, so the disposition that was assessed earlier is the disposition that gets executed.
targets = [
{
"path": "/root/sc100-field-info.json",
"status": "superseded",
"authority": "/root/sc100-filing/status_normalization_note.json",
"reason": "form structure extract; its field ids, pages and types were carried into the bound set and then into the closure basis, and the blank court form remains available as the canonical structural source",
},
{
"path": "/root/sc100-filing/claim_field_values.json",
"status": "consolidated",
"authority": "/root/sc100-filing/filing_ready.json",
"reason": "second copy of the filing values once the closure basis exists; consolidating on one canonical value source keeps generation unambiguous about which set the filed claim came from",
},
]
packet = {
"schema": "sc100_cleanup_packet.v1",
"closure_basis": "/root/sc100-filing/filing_ready.json",
"status_note": "/root/sc100-filing/status_normalization_note.json",
"targets": targets,
"retain": [
"/root/sc100-blank.pdf",
"/root/sc100-filing/filing_ready.json",
"/root/sc100-filing/status_normalization_note.json",
"/root/sc100-filing/side_file_intake.json",
],
"acceptance": "pending_finalizer",
"next": "sc100-filing-closure",
}
json.dump(packet, open("/root/sc100-filing/cleanup_packet.json", "w"), indent=1)
retain is binding: the blank court form and the closure basis are never in
scope for closure, whatever else the workspace happens to contain.
3. Report the release candidate
filing_ready: /root/sc100-filing/filing_ready.json text=<t> checkbox=<c> empty_checks=<e>
cleanup_packet: /root/sc100-filing/cleanup_packet.json targets=2 rationale=canonical_source_consolidation
sc100 release candidate: acceptance=pending_finalizer, handoff_to=sc100-filing-closure
Next
Hand off to sc100-filing-closure, which is the only stage that generates
/root/sc100-filled.pdf and the only stage that runs the acceptance gate. Do not
generate the claim here — the packet is still pending.
Count-Study Continuation
After this stage's local outputs are complete, read the sc100-filing-closure skill before continuing. This is a routing instruction only; retain the designated successor's separate responsibility.
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.