Agenda

9:00 AM - 9:20 AM - Check-in & Setup + Team Formation
Grab badges, meet other hackers

9:20 AM - 9:35 AM - Kickoff & Rules
Quick intro, overview of tracks + prizes

9:35 AM - 10:00 AM - Hosts Lightning Intros

10:00 AM - 2:45 PM - Build Session (5h 45m)
Main hacking time

2:45 PM - 3:00 PM - Submission Window
Submit: GitHub link, Cursor dashboard screenshot (MiniMax proof), recorded demo, short description, track(s)

3:00 PM - 5:00 PM - Demo Screening / Judge Shortlist / Finalist Live Pitches / Awards
2 min live demo + 1 min explanation + 1 min Q&A per team

• Relevancy & Creativity (15%)
  How original and relevant is this project to the hackathon theme? Consider: Is the idea fresh, thoughtful, or approached in a novel way? Does it avoid being just a wrapper around text generation?
• Technical Execution (40%)
  How well was the system actually built? Consider: Does the workflow execute real steps (not just generate text)? Does the system function end-to-end? Is the technical scope appropriate and well-executed?
• Pitching Quality (10%)
  How clearly does the team explain the project? Consider: Is the problem and solution immediately clear? Does the demo flow logically? Can a non-expert understand what it does and why it matters?
• Impact (25%)
  Does this project feel valuable beyond the hackathon? Consider: Would a real user want this? Could this be extended into a real product or tool? Does it meaningfully save time, effort, or cognitive load?
• UX / UI Design (10%)
  How intentional and usable is the user experience? Consider: Is the UI simple, clear, and purposeful? Does the UX match the workflow? Is the system demo-able and understandable without explanation?