Format and challenge delivery

Hack4Haldia’26 is a time-boxed, 3-hour build sprint.
Every team receives one starter repository on the day of the event. Challenges and repositories are not shared beforehand, so there is no advance preparation on the problem itself.

Starter repository structure

README.md: the full problem statement and instructions for what to build.
index.html: the front-end entry point.
app.py (Python backend) or script.js (JavaScript), depending on the selected stack.

Core deliverables

Build new features on top of the starter project, extending the base rather than starting from scratch.
Integrate the new features cleanly into the existing codebase.
Deploy the working project so it is live and accessible.
Create a Pull Request (PR) on the Voyage GitHub repository assigned to your team on the day.
Submit the project through the official MLH platform (OrganizerHQ). Instructions will be given at the start of the event.

AI and tooling policy

AI tools are fully open. Teams may use any AI tools and any open-source or open-weight models to build faster and better.

Team rules

Each team has 3 to 4 members, and every member must be present.
Solo participants will be teamed up with other teams or other solo participants so that full teams are formed.

Key takeaways

Read the README first. It contains everything you need.
Plan for deployment and the PR early, not in the last few minutes.
Double-check that both submission routes are done: the GitHub PR and the OrganizerHQ (MLH) entry.