Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use when revising an AAAI manuscript for broad-AI-audience fit, a first-page contribution statement legible to non-specialist Phase-1 reviewers, two-column readability, concise novelty claims, reproducibility-checklist alignment, hedged limitations and ethics, and policy-aware framing of AI-system and capability claims.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this to make a technically sound draft readable to a broad AI program committee. AAAI rewards clear AI contribution, not only subfield-specific benchmark wins.
A non-specialist on AAAI's broad committee gives the first page a few minutes and decides whether the paper is worth deeper reading. Write so that a planning or KR reviewer can summarize your learning contribution, and vice versa. Audit the opening against what that reader needs to extract fast.
| First-page question | Reviewer extracts | Failure symptom |
|---|---|---|
| What is the problem | one AI task statement | jargon with no anchor |
| What is new | the single contribution | a list, no headline |
| Why believe it | evidence in one line | "see Section 6" only |
| What are the limits | scope and caveat | silence or overclaim |
A multi-agent paper opens with three paragraphs of game-theory notation before naming its contribution. A vision reviewer cannot find the AI claim and is likely to stop. The fix rewrites sentence one as the problem, sentence two as the new coordination mechanism, sentence three as the one-line evidence, and a final clause scoping the result to the studied setting, all on page one.
[AAAI fit sentence] <one sentence>
[Contribution type] method / theory / system / benchmark / dataset / evaluation / social impact
[First-page fixes] <problem, method, evidence, limitation>
[Checklist alignment] pass / needs revision
[Overclaim risks] <claims to narrow or evidence to add>
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance, AI-generated-review handling, and the AAAI two-phase review process where Phase-2 papers receive one feedback round before SPC/AC discussion.
日本語の概要は準備中です。原文の説明を表示しています。
Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and final public artifact release.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and reproducibility-checklist alignment for Phase-1 survival.
日本語の概要は準備中です。原文の説明を表示しています。
Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a related-work section legible to non-specialist reviewers.
日本語の概要は準備中です。原文の説明を表示しています。
Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that Phase-1 reviewers use to judge rigor across AAAI's broad AI scope.
日本語の概要は準備中です。原文の説明を表示しています。