Hackathon Guidelines
Read carefully. These rules ensure a fair, high-integrity competition for everyone.
1Execution Rules
Post-Start Build
All work — code, no-code, automations, designs — must begin after the official start time of 2:15 PM on May 6.
Zero Pre-Configuration
No pre-built solutions, pre-configured pipelines, or ready-made tools are allowed as a starting point.
The Starting Material
Only the contents of the May 4th Zip file (your approved Spec & PRD) are allowed as your starting material.
3-Hour Coding Cap
All building and development stops exactly at the 3-hour mark (5:15 PM). No exceptions.
Evidence of Work
Progress must be demonstrable via commits, save history, or tool logs. Show your trail.
Tooling
AI tools, no-code platforms, and design tools are allowed — but teams must be able to explain all outputs generated.
Integrity
No external contributors. No fake demos or misrepresented functionality. What you show must be what you built.
MVP Focus
You must strictly adhere to the MVP defined in your approved PRD. Scope creep is not allowed during the build.
Live Demo
A live demo is mandatory for all participants. 45 minutes, 5:15–6:00 PM. No video recordings as substitutes.
2Evaluation Criteria
3PRD Requirements
Your 1-page Lean PRD must cover all of the following:
4Do's & Don'ts
✅ Do's
- Submit a tight, focused MVP — quality over quantity
- Use AI meaningfully as a core part of your solution
- Commit early and commit often to show your work trail
- Keep your demo short, clear, and live
- Stick strictly to your approved PRD scope
❌ Don'ts
- Don't use pre-built or pre-configured solutions
- Don't fake or misrepresent any demo functionality
- Don't work beyond the 3-hour coding cap
- Don't add features not defined in your approved PRD
- Don't involve external contributors during the hackathon