ConmuYan 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
- Identify venue/year/track, submission mode, project directory, TeX/PDF files, supplementary/artifact files, and deadline pressure.
- Read
ccfa.yamlwhen available. If absent, proceed with supplied files and state that project-state tracking is unavailable. - For venue questions, read
../kim-ccf-research-shared/references/ccf-a-venue-map.mdand the specific venue guide before checking official freshness. - For package checks, inspect compile status, page count, target page budget, anonymity, fonts, PDF metadata, template path, references, supplementary files, and required forms.
- For artifact checks, build a reproducibility checklist: code, data, models, environment, seeds, hardware, license, access restrictions, and README.
- Hand off to
ccf-paper-writerfor text/page rewrites: compression when over limit, expansion when a full manuscript is materially underfilled, and normal polishing when within budget. Hand off toccf-experiment-designerfor missing reproducibility experiments,ccf-visual-composerfor figure/table float order, caption placement, font, clipping, palette, or visual readability fixes, andccf-rebuttal-writerfor post-review response packaging.
Output Contract
Mode:
Venue and rule freshness:
Files checked:
Pass/fail checklist:
Build/package issues:
Anonymity/page/font/metadata issues:
Length budget status:
Artifact/reproducibility issues:
Required fixes:
Next CCFA owner: