Check CCF venue rules and submission packages: template, pages, anonymity, PDF build, metadata, and reproducibility. Use for 投稿检查, 会议格式, page limits, and artifact readiness. Verify current official rules for the exact venue/year/track. Manuscript polishing belongs to ccf-paper-writer.

CCF Submission Checker Core Rule Treat submission as a build, venue policy, page budget, and artifact readiness gate. Use local venue guides for expected rules, then require official policy freshness for final decisions. Do not rewrite paper content. Modes venue format : template, page limit, anonymity, author block, supplementary and camera ready rules. package check : LaTeX/PDF build, metadata, fonts, page count, file structure, and submission checklist. artifact : code/data/model release plan, environment, seeds, hardware, licenses, artifact README, and reproducibility appendix. full : venue + package + artifact. Workflow 1. Identify venue/year/track, submission mode, project directory, TeX/PDF files, supplementary/artifact files, and deadline pressure. 2. Read ccfa.yaml when available. If absent, proceed with supplied files and state that project state tracking is unavailable. 3. For venue questions, read ../ccf paper writer/references/venue guides/index.md and the specific venue guide before checking official freshness. 4. For package checks, inspect the actual TeX/PDF/build output, page accounting for the exact venue/year/track, anonymity, fonts, metadata, references, and applicable required forms. Read logs and affected pages; do not infer a successful build from file presence. 5. For artifact checks, build a reproducibility checklist: code, data, models, environment, seeds, hardware, license, access restrictions, and README. 6. Hand off to ccf paper writer for text/page rewrites: compression when over limit, substantive expansion when actual explanation is missing, and normal polishing when within budget. Hand off to ccf experiment designer for missing reproducibility experiments, ccf visual composer for figure/table float order, caption placement, font, clipping, palette, or visual readability fixes, and ccf rebuttal writer for post review response packaging. Output Contract Check Scope Follow ../ccf common/references/handoff modes.md and ../ccf common/references/task modes.md . Run checks relevant to the requested mode and actual artifacts. Distinguish pass, fail, not applicable, and not verified; missing tools do not imply passing or failure. Record the official rule URL and the date checked. Reuse the project build configuration and place generated logs/previews in the established or shared task build directory. Update the canonical readiness report in place and distinguish old PDFs from successful current builds. Recheck only affected build surfaces after a fix. Underfilling a page budget alone is not a venue violation. Do not upload or submit files merely because a readiness check was requested. For file outputs, follow ../ccf common/references/artifact contracts.md : resolve existing project paths first, keep generated working files under one stable task/artifact directory, and update canonical files in place. Load this shared policy only when files are written and it is not already in context.

ccf-submission-checker