Conference Router

Conference Router

Inputs

• Paper title, abstract, contribution claims, methods, datasets, and experiment status.
• Optional venue targets, constraints, field, review timeline, artifact goals, or presentation goals.

Available Venues

aaai, acl, colm, colt, corl, cvpr, eccv, emnlp, iccv, iclr, icml, ijcai, interspeech, iwslt, miccai, mlsys, naacl, ndss, neurips, osdi, uai, usenix-fast, usenix-sec

Workflow

1. Identify the paper domain, evidence type, primary contribution, and maturity of experiments.
2. Compare the user's target against the available corpus-backed venue skills.
3. Recommend 2-4 candidate venues only when the user asks for routing or venue fit.
4. For a chosen venue, hand off to profiles/<venue>/SKILL.md for a lightweight fit check or skills/<venue>-skill/SKILL.md for corpus-backed evidence patterns.
5. For pilot venues, hand off to packs/<venue>/skills/<venue>-<stage>/SKILL.md when the user needs a lifecycle stage workflow.

Evidence Rules

• Treat accepted-paper patterns as [pattern], not official policy.
• Treat user-provided manuscript details as [user-provided].
• Use [policy] only when the user provides current official CFP, author guide, template, rebuttal, artifact, registration, or fee sources.
• Do not output acceptance probabilities.

Output Contract

[status] ready | at_risk | blocked | unverified
[routing candidates]
1. venue: ...
   fit: ...
   risks: ...
   next skill: ...
[policy gaps]
1. ...
[next action] ...