brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
icalp-supplementaryUse when splitting an ICALP (EATCS) theory paper between the 15-page main body and the clearly labelled appendix / full version — deciding what a referee must see in the body versus what may be deferred, ensuring every deferred proof is actually present and findable, and keeping the split consistent with lightweight double-blind review.
Independent GitHub snapshot · Automated classification · Original documentation governs
ICALP gives you a 15-page body (excluding references and a clearly labelled appendix) plus an appendix that may hold omitted proofs or a full version, read at the program committee's discretion. The whole game is deciding what goes where: the body must let a referee judge and follow the paper; the appendix must let them verify it. Getting this split wrong — either cramming proofs into the body or hiding the substance in an unread appendix — is a common, avoidable weakness.
The body earns the referee's belief; the appendix earns their verification.
icalp-experiments, icalp-reproducibility).| Failure | Symptom | Fix |
|---|---|---|
| Over-stuffed body | Every proof crammed into 15 pages; unreadable, over-budget | Move complete proofs to the appendix, keep sketches + key lemmas in the body |
| Hollow body | Body states theorems, all proofs (incl. the key idea) dumped in an unread appendix | Bring the central technique and the main lemma's proof idea into the body |
The hollow body is the more dangerous: referees judge on the body, and a paper whose substance they cannot see reads as either thin or evasive, even if the appendix is perfect.
icalp-reproducibility).icalp-submission).An algorithm (Thm 1) and a matching conditional lower bound (Thm 2). Body: the model; both theorem statements with the prior-bound comparison; the algorithm's design and the one key invariant proved; the reduction's construction and its intuition. Appendix / full version: the full correctness proof and complexity analysis of the algorithm; the complete case analysis of the reduction; a computer-checked verification of the gadget. Result: a referee can judge significance and follow both ideas from the body, then verify every detail in the appendix.
[Body budget] <=15pp excl. refs + appendix; over/under
[In body] model / theorem statements / key technique / main-lemma idea: all present? gaps
[Deferred] complete proofs, routine cases, computation — each with a body pointer? yes/no
[Hollow-body check] is the central idea visible in the body (not only the appendix)? yes/no
[Completeness] every deferred proof actually present and findable? yes/no
[Anonymity] appendix/full version scrubbed and referenced without de-anonymizing? yes/no
[Fix queue] <ordered moves between body and appendix>