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).
aamas-review-processUse when explaining or planning around AAMAS peer review, covering OpenReview review release, the double-blind rebuttal on preliminary reviews, area-chair discussion, the mixed game-theory, MARL, and systems reviewer pool, the public posting of reviews and decisions, and how acceptance criteria weigh the interaction contribution.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this to reason about review-stage strategy. Reopen the current CFP, OpenReview group, author and reviewer instructions, and the code of conduct before making process claims; AAMAS review specifics move between editions.
| Review dimension | What raises it | What sinks it |
|---|---|---|
| Correctness | A stated game, a named solution concept, and a body-level proof sketch | Hidden information structure; an equilibrium asserted but never defined |
| Significance | A finding that only exists because agents interact | An incremental single-agent gain wearing a multiagent label |
| Empirical support | Experiments that probe strategy: held-out opponents, deviation tests | Self-play-only curves disconnected from the claim |
| Clarity | One notation source and a legible game description | Notation and payoff conventions that shift between sections |
[Current stage] submitted / reviews / rebuttal / decision / camera-ready
[Decision actors] <reviewers / area chair / program chairs>
[Likely leverage] <correctness / interaction-reality / significance / experiments / clarity>
[Forbidden moves] <identity leak / new results / revised-paper upload if disallowed>
[Next response move] <one action>