After Submission
What happens after you submit your task, and how to handle feedback.
Review Timeline
| Stage | Duration |
|---|---|
| Automated CI checks | Immediate |
| Peer review assignment | 1 day |
| Initial review | 1-3 business days |
| Follow-up reviews | 1-2 business days |
| Total | 3-7 business days |
Review Process
1. Automated Checks
Immediately after submission, your task goes through: - CI checks (syntax, structure, dependencies) - LLMaJ checks (quality, completeness) - Oracle agent run
2. Peer Review
A qualified coding expert reviews: - Task clarity and correctness - Solution validity - Test coverage - Anti-cheating measures - Overall quality
3. Agent Evaluation
Your task is run against: - GPT-5.2 with Codex agent (5 runs) - Claude Opus 4.6 with Claude Code (5 runs)
Pass rate determines final difficulty classification.
Review Outcomes
Approved ✓
Congratulations! Your task is accepted.
- Task added to benchmark suite
- Credit recorded in your profile
Changes Requested
Reviewer identified issues that need fixing.
What to do: 1. Read feedback carefully 2. Understand each requested change 3. Make fixes locally 4. Re-run all checks 5. Resubmit / push updates
Declined ✗
Task doesn't meet criteria. Common reasons: - Too easy - Unclear requirements - Similar task already exists - Fundamental design issues
What to do: 1. Review the feedback 2. Consider if it can be salvaged 3. Either significantly revise or start fresh 4. You can appeal if you disagree
Addressing Feedback
Read Carefully
Understand exactly what's being asked: - Is it a minor fix or major revision? - Does reviewer explain the reasoning? - Are there specific lines/files mentioned?
Make Targeted Changes
Don't rewrite everything. Fix only what's needed. Use the Reviewer Checklist to make sure all high-severity and relevant medium-severity criteria are covered before resubmitting.
Explain Your Changes
When you resubmit: Platform: Add a note with your revision summary.
Re-request Review
After pushing changes, let the reviewer know: Platform: Update submission status
Disagreements
If you disagree with feedback:
- Respond politely with your reasoning
- Provide evidence for your approach
- Be open to compromise
- Escalate to Slack if needed
Remember: Reviewers want to help. Most disagreements are resolved through discussion.
Tips for Faster Acceptance
- Run all checks locally before submitting
- Follow the checklist exactly
- Write clear documentation in
instruction.md - Address feedback promptly
- Ask questions if feedback is unclear
Need Help?
- Slack:
#terminus-2nd-edition-submission - FAQ
- Troubleshooting