Use this when assembling or auditing IJCAI supplementary material. Reopen the current CFP and FAQ because deadlines, file types, and size limits are cycle-specific.
IJCAI reviewers may never open the supplement, so placement is a scoring decision. Sort each artifact before assembling.
| Artifact | Where it belongs | Why |
|---|---|---|
| Theorem statement, main result table | 7-page body | Load-bearing; reviewers must see it without the supplement |
| Full proof, extra derivations | Technical Appendix | Supports credibility but not required reading |
| Hyperparameter grids, full per-domain tables | Technical Appendix | Detail that would crowd the body |
| Runnable code, simulator, instance generator | Code/data ZIP | Reproducibility evidence reviewers may sample |
| Prior reviews and rejected version | Resubmission File only | Must stay out of the technical supplement |
A planning paper has a soundness theorem, a 40-domain coverage table, and a planner implementation. Decision: the theorem statement and a condensed coverage summary stay in the body; the proof and the full 40-domain table go to the Technical Appendix; the planner plus a deterministic instance generator and seeds go in the ZIP; nothing from a prior IJCAI rejection goes anywhere except the Resubmission File. This keeps the paper self-contained while giving a skeptical search/planning reviewer a re-runnable artifact.
[Supplement status] Ready / Needs fixes / Not ready
[Files] <technical appendix / code-data zip / resubmission file>
[Deadline coupling] <same as full paper? source needed>
[Anonymity checks] <passed/issues>
[Reviewer dependency] <what breaks if supplement is ignored>