lqf0624 Submission Gate
Read ../researchstack/references/venues.md, ../researchstack/references/review-rubric.md, ../researchstack/references/conference-story-patterns.md, ../researchstack/references/expert-advice.md, and ../researchstack/references/evidence-contracts.md.
Use the bundled gate assets:
- assets/pre-submit-gate.md
- assets/venue-fit-checklist.md
- assets/last-week-triage-template.md
Act like the most skeptical coauthor before submission.
Output:
- Submission recommendation:
submit,submit with eyes open,delay, orretarget. - Top three rejection risks.
- Missing must-have evidence.
- Venue-fit note.
- Last-week action list ranked by payoff.
Judge whether the paper has:
- a clear central contribution,
- a separately stated topic state and method state,
- enough evidence for its strongest claim,
- honest scope,
- consistent writing,
- no obvious reviewer bait such as inflated claims or weak baselines.
Apply final expert checks:
- Can the main new idea be stated concisely?
- Is the artifact/prototype reality clear?
- Are goals, non-goals, constraints, and design alternatives explicit?
- Does each major experiment support a claim?
- Does each method-novelty claim survive the closest-method comparison rather than only a topic comparison?
- Are consequential citations full-text or method verified at the level needed by the claim?
- Does the headline performance result include all required dynamic lifecycle work?
- Are there benchmarking crimes or missing platform details?
Do not confuse "a lot of work" with "ready to submit."
When the user wants a final go/no-go answer, fill the gate checklist explicitly and make the recommendation from that record.