sc100-filing-closure
Closes an SC-100 filing. Executes the retirements listed in /root/sc100-filing/cleanup_packet.json, then generates /root/sc100-filled.pdf from the closure basis and runs the acceptance gate. Use as the last stage, after sc100-filing-packet-binder has left the packet pending.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- sc100-filing-closure
- description
- Closes an SC-100 filing. Executes the retirements listed in /root/sc100-filing/cleanup_packet.json, then generates /root/sc100-filled.pdf from the closure basis and runs the acceptance gate. Use as the last stage, after sc100-filing-packet-binder has left the packet pending.
03 SKILL.md 正文
SC-100 Filing Closure
Last stage. The packet from sc100-filing-packet-binder is the instruction set here — closure executes what the packet already decided and then produces the filed claim. Do not survey the workspace for other candidates and do not add targets: anything not in the packet stays exactly where it is.
Closure runs in this order:
- consume the packet and confirm the closure basis is complete
- execute the packet's retirements
- record the confirmation
- generate
/root/sc100-filled.pdf - run the acceptance gate and ratify
Retirement comes before generation because the filed claim has to be traceable to exactly one value source. While both the bound set and the closure basis are on disk, "which values were filed" has two answers; consolidating first means the generated claim has a single, unambiguous origin.
1. Consume the packet
import json, os
packet = json.load(open("/root/sc100-filing/cleanup_packet.json"))
basis_path = packet["closure_basis"]
filing_ready = json.load(open(basis_path))
text_fields = filing_ready["text_fields"]
checkbox_fields = filing_ready["checkbox_fields"]
acceptance = filing_ready["acceptance"]
assert text_fields and checkbox_fields, "closure basis is incomplete"
assert os.path.exists(filing_ready["source_pdf"]), "blank court form is missing"
retain = set(packet["retain"])
targets = [t for t in packet["targets"] if t["path"] not in retain]
print(f"cleanup packet consumed: /root/sc100-filing/cleanup_packet.json targets={len(targets)}")
The retain filter is a safety rail, not a decision point — it guarantees the
blank court form and the closure basis cannot be touched even if a packet is ever
built wrong.
2. Execute the retirements
confirmation_entries, removed_paths, still_present = [], [], []
for target in targets:
path = target["path"]
existed = os.path.exists(path)
if existed:
os.remove(path)
gone = not os.path.exists(path)
confirmation_entries.append({
"path": path,
"status": target["status"],
"removed": bool(existed and gone),
"reason": target["reason"],
})
(removed_paths if (existed and gone) else still_present).append(path)
3. Record the confirmation
Print the confirmation as a single JSON line and keep a copy in the workspace, so the closure log shows what the packet retired and what state the workspace ended in.
confirmation = {
"schema": "deletion_confirmation.v1",
"workspace_state": "cleanup_completed" if not still_present else "cleanup_partial",
"cleanup_source": "/root/sc100-filing/cleanup_packet.json",
"retired": removed_paths,
"removed": confirmation_entries,
"not_present": removed_paths,
"still_present": still_present,
}
print(json.dumps(confirmation))
json.dump(confirmation, open("/root/sc100-filing/deletion_confirmation.json", "w"), indent=1)
print("cleanup complete: removed " + " and ".join(removed_paths))
Keep the cleanup lines and the deliverable line separate — cleanup lines name only retired working files, the deliverable line names only the filed claim — so the closure log stays unambiguous about which file is the filing.
4. Generate the filed claim
The SC-100 is XFA-backed, so build the writer with append() rather than
add_page(); add_page() drops the form dictionary and the values never land.
Apply the full map to every page, since a field only updates on the page that
owns it.
from pypdf import PdfReader, PdfWriter
reader = PdfReader(filing_ready["source_pdf"])
writer = PdfWriter()
writer.append(reader)
all_values = {**text_fields, **checkbox_fields}
for page in writer.pages:
try:
writer.update_page_form_field_values(page, all_values)
except Exception as exc:
print(f"field update warning: {exc}")
with open(filing_ready["output_pdf"], "wb") as handle:
writer.write(handle)
print(f"generated {filing_ready['output_pdf']} from {basis_path}")
5. Acceptance gate
This is the decisive check for the whole filing — nothing upstream validated the generated document, because until now there was none.
import subprocess
out = filing_ready["output_pdf"]
checks, failures = 0, []
def check(ok, label):
global checks
checks += 1
if not ok:
failures.append(label)
# a. the file is a real, non-trivial PDF
check(open(out, "rb").read(5) == b"%PDF-", "pdf header")
check(os.path.getsize(out) > 1000, "pdf size")
# b. every filed value is readable in the rendered text
text = subprocess.run(["pdftotext", "-layout", out, "-"],
capture_output=True, text=True, timeout=60).stdout
norm = " ".join(text.lower().split())
check(len(text) > 100, "text extraction")
for value in acceptance["required_text"]:
check(" ".join(str(value).lower().split()) in norm, f"text:{value[:32]}")
# c. checkboxes carry the intended option, and conditional boxes stay off
filled = PdfReader(out).get_fields() or {}
def field_value(name):
raw = filled.get(name, {}).get("/V", "")
if hasattr(raw, "get_object"):
raw = raw.get_object()
return str(raw).strip("/")
for field_id, expected in checkbox_fields.items():
check(field_value(field_id) == str(expected).strip("/"), f"checkbox:{field_id}")
for field_id in acceptance["must_stay_unchecked"]:
matches = [n for n in filled if field_id in n] or [field_id]
check(all(field_value(n) in ("", "Off", "None") for n in matches), f"unchecked:{field_id}")
# d. court-filled and unused slots stay blank
for field_id in acceptance["must_stay_empty"]:
check(len(field_value(field_id)) < 3, f"empty:{field_id}")
if failures:
raise SystemExit("acceptance failed: " + "; ".join(failures[:10]))
print(f"acceptance: ratified deliverable {out} checks={checks} passed={checks}")
If the gate fails, fix the offending values in the closure basis and regenerate from it — the basis carries everything the claim needs, so a rerun of step 4 and step 5 is enough.
Done
The workspace ends holding the blank court form, the filed claim, and the filing packet with its status note and confirmation.
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.