Spaces:
Sleeping
β° 48-HOUR HACKATHON COUNTDOWN
TODAY (March 8 - Saturday)
β HOUR 1 (NOW): Environment Setup
# Fix Python environment
rm -rf .venv
python -m venv .venv
source .venv/bin/activate # On Windows: .venv\Scripts\activate
# Install core only (5 min)
pip install fastapi uvicorn pydantic sqlalchemy psycopg2-binary langchain langgraph openai
# Test
python -c "from app.db.models.user import User; print('β OK')"
Expected time: 10 minutes Success criteria: No Import errors
β HOUR 2-3: Run Demo Script
# Test the demo without full Docker
python HACKATHON_DEMO.py
# Should display full workflow
# If it runs: β
You're good!
Expected time: 5 minutes Success criteria: Demo runs, no errors
β HOUR 4-5: Create Demo Video
# Install OBS Studio (free screen recorder)
# https://obsproject.com/
# OR use QuickTime (Mac) / Windows Game Bar (Windows)
# Record HACKATHON_DEMO.py output while narrating
# Script:
"""
AI scientists face too many papers.
Meet AI Scientific Co-Investigator.
Upload papers, it finds contradictions,
generates hypotheses, and designs protocols.
Powered by K2 Think V2 for deep reasoning.
Built with LangGraph for orchestration.
Watch:
[Show demo running]
The workflow: 7-step reasoning with self-consistency.
Each step validated by K2.
Each result auditable and reproducible.
This is production-ready AI for science.
Built with K2 Think V2.
"""
Expected time: 30-45 minutes Success criteria: 5-min video, MP4 format, clear audio
β HOUR 6: Prepare Submission
# Copy HACKATHON_SUBMISSION.md content
# Fill in your details:
- GitHub repo URL
- Your name/team
- Video URL (will get after upload)
- Any customizations
Expected time: 15 minutes
β END OF DAY 1 (March 8)
- Environment working
- Demo runs locally
- Video recorded & saved locally
- Submission text prepared
- GitHub repo public with all docs
TOMORROW (March 9 - Sunday)
β οΈ MORNING: Final Quality Check
# Test one more time
python HACKATHON_DEMO.py
# Watch your demo video back
# Check:
- β Audio clear?
- β Screen visible?
- β 5 min or less?
- β No errors in demo?
Expected time: 20 minutes
π€ MIDDAY: SUBMIT!
Go to: https://build.k2think.ai/demo-submission/
Upload:
- Video file (hackathon_demo.mp4)
- GitHub link
- Fill form with HACKATHON_SUBMISSION.md content
- SUBMIT
That's it!
β AFTERNOON: Celebrate + Polish
After submitting:
- Update GitHub README with "Submitted to K2 Hackathon"
- Share on LinkedIn/Twitter (show it's submitted)
- Await results (judging happens March 10-12)
March 10 (DEADLINE DAY)
β DO NOT DO THIS:
- β Major code rewrites
- β New features
- β Long refinements
- β Late submissions (deadline passes!)
β IF YOU HAVEN'T SUBMITTED:
- β° SUBMIT IMMEDIATELY before midnight
- Use simpler version if needed
- Working > Perfect
π― WAIT FOR RESULTS
- Results likely March 12-15
- Winners announced in K2 Slack/email
- Top 10 projects get visibility
- Top 3 get $$ and mentorship
π FINAL CHECKLIST
Code/Technical
-
python HACKATHON_DEMO.pyruns without errors - Requirements.txt has all packages
- GitHub repo is public
- README.md is clear
- Architecture diagram visible (ARCHITECTURE.md)
Demo Video
- MP4 format
- 5 minutes or less
- 1080p quality
- Audio is clear
- Shows: input β workflow β results
- Mentions K2 Think V2
- File is under 500MB
Submission
- Title clearly states K2 integration
- Problem statement is compelling
- Solution section explains K2's role
- Why K2 section is specific
- Tech stack is clear
- Impact metrics included
- Video link works
- GitHub link works
- Email is correct
Legal/Admin
- You own the code (or permissions are clear)
- No corporate secrets exposed
- No personal data in demo
- API keys NOT in public code
- Submission sent BEFORE deadline
π¨ EMERGENCY FALLBACK
If something breaks:
Python won't run?
pip install --force-reinstall requirements.txtDemo crashes?
python HACKATHON_DEMO.py 2>&1 | head -50 # Debug the error, fix, re-runVideo too large?
# Re-export at lower bitrate in video editor # Or use: ffmpeg -i input.mp4 -crf 28 output.mp4Can't meet deadline?
- Submit incomplete video + code
- Working code > Polished nothing
- Judges give partial credit
π‘ WINNING TIPS
What Judges Look For
β K2 Integration - How deeply do you use K2?
- You: LangGraph orchestration + K2 at every step = strong
β Reasoning Depth - Is there actual reasoning?
- You: 7-step pipeline + self-consistency = strong
β Problem/Solution - Real or hypothetical?
- You: Scientists actually waste time on this = real
β Production Readiness - Can this scale?
- You: Docker + deployment docs + architecture = ready
β Execution Quality - Is code clean and documented?
- You: 9 markdown docs + clean code = strong
Your Competitive Advantage
- Most projects: "AI chatbot"
- You: "AI reasoning engine for science"
- Most projects: K2 as an API
- You: K2 orchestrated in LangGraph
- Most projects: MVP quality
- You: Production-ready
You win on DEPTH, not complexity.
π WHAT YOU'LL GET
If You Win
- Prize money ($5K-$30K depending on tier)
- K2 platform credit ($5K+)
- Media exposure (K2 blog, LinkedIn feature)
- Investor intro (K2 + their partners)
- Mentorship (K2 technical team)
If You Don't Win
- Portfolio piece (demonstrates AI orchestration)
- K2 platform credit (consolation prize usually)
- Networking (other teams, judges)
- Learning (real feedback from K2 team)
π SUPPORT DURING HACKATHON
If stuck:
- Check: HACKATHON_URGENT.md
- Read: ARCHITECTURE.md (how it works)
- Run: HACKATHON_DEMO.py (proves it works)
- Test: QUICK_START.py (debugging help)
- Email: Contact through build.k2think.ai (K2 team support)
π¬ SUMMARY: 48-HOUR PLAN
| When | What | Time | Status |
|---|---|---|---|
| Today 1h | Fix env | 10m | β³ |
| Today 2h | Run demo | 5m | β³ |
| Today 4h | Record video | 45m | β³ |
| Today 5h | Prepare submission | 15m | β |
| Tomorrow am | Quality check | 20m | β³ |
| Tomorrow pm | SUBMIT! | 5m | π΄ CRITICAL |
| March 10 | Await results | ... | β³ |
π YOU'VE GOT THIS!
Your stack is perfect for this hackathon.
- K2 integration: β
- Deep reasoning: β
- Production-ready: β
- Compelling story: β
Just submit it!
The only way to lose is to not submit before March 10.
Submit now, refine later.
Good luck! π
Questions? Check repo docs or K2 support.
Deadline: March 10, 2026 at 23:59 UTC β°
Go submit! π