Event Rules 1. General Participation

  • Solo Only: This is a solo-hacker sprint. All projects must be the work of a single individual. Collaboration on code is not permitted for this specific event.

  • Fresh Code: All code must be written during the 8-hour sprint. Use of pre-existing personal libraries is allowed, but the core "Agent" logic must be built on-site.

  • API Requirement: Projects must utilize the Google Gemini API to be eligible for prizes. Use of other LLMs is permitted only as a secondary support.

2. Submission & Judging

  • Devpost Submission: All projects must be submitted to the official Devpost page by 4:00 PM. Late submissions will not be considered for the Google Swag Kits.

  • Demo Requirement: Submissions must include a link to a public repository (GitHub) and a brief video demo or live demonstration link.

  • Judging Criteria: Projects will be judged on Technical Execution, Creativity, and Agentic Autonomy (how well the bot performs tasks without manual intervention).

3. Professionalism

  • Check-in: You must check in digitally at the venue to be eligible for the event and reimbursement-funded food.

  • Attendance: No-shows without 24-hour notice may be barred from future local MLH events.

Code of Conduct The MLH Standard

As an official Major League Hacking (MLH) member event, we strictly enforce the MLH Code of Conduct.

In short:

  • Be Respectful: Harassment of any kind (verbal, physical, or digital) will result in immediate disqualification and removal from the IEM Ashram Building.

  • Be Inclusive: This is a safe space for all hackers regardless of gender, orientation, disability, appearance, or religion.

  • Be Honest: Plagiarism or "cheating" (submitting old projects) will result in a permanent ban from our local hacking community.

Reporting an Issue

If you feel uncomfortable or notice someone else being harassed, please find Aniket Chakraborty (Lead Organizer) immediately or contact the MLH incident reporting team as outlined in the opening ceremony slides.