-
All projects must be built during the hackathon event duration.
-
Code must be written during the event.
-
You may use pre-existing open-source libraries, frameworks, APIs, and SDKs, but the core solution, integration, and implementation must be done at the event.
-
Using AI tools (such as coding assistants, LLMs, design generators, documentation helpers) is allowed.
-
Teams are responsible for ensuring their project is functional, explainable, and ethically built, even if AI-assisted.
-
If AI is used significantly, teams should be able to clearly explain what was generated, what was modified, and how it works.
-
Every project must be based on the official problem statements released on the hackathon day.
-
Teams must select one problem statement (or one track’s statement) and build a solution aligned with it.
-
Projects that do not map clearly to the given problem statements may be disqualified.
-
Each participant can be part of only one team.
-
Cross-team collaboration on the same project is not allowed.
Each team must submit:
-
Project name and description
-
Problem statement selecte
-
Code repository link (GitHub or equivalent)
-
Presentation/Pitch (slides or clear explanation)
-
Plagiarism, copying another team’s work, or submitting a previously built project as the main solution will result in immediate disqualification.
-
Any attempt to disrupt other teams, infrastructure, or event operations will lead to removal from the event.
-
Judges’ decisions are final and binding.
-
The organizing team reserves the right to disqualify any submission that violates rules, misrepresents work, or breaches conduct standards.
-
Maintain a respectful, inclusive environment for all participants.
-
Harassment, discrimination, or unsafe behavior will not be tolerated.
