HACK_2026

< RULES_&_PROTOCOLS />

[ SYSTEM_NOTICE ]: Strict adherence to the following protocols is mandatory for all participants. Failure to comply will result in immediate termination of access.

ELIGIBILITY_CRITERIA

  • >OPEN_ACCESS: Students from all branches and academic years are eligible. No prior clearance required.
  • >SQUAD_CONFIG: Teams must consist of 2 to 4 units. Interdisciplinary squads are recommended for optimal output.
  • >REGISTRATION_LOCK: All units must be registered before the deadline. Late packet injection is not permitted.

ENGAGEMENT_RULES

  • !FRESH_CODE_ONLY: All assets must be generated within the 24-hour runtime environment. Pre-compiled projects are prohibited.
  • !EXTERNAL_LIBRARIES: Third-party APIs and open-source libraries are permitted if public access is available.
  • !RUNTIME_LIMIT: 24 Hours hard stop. Late submissions will be rejected by the server.
  • !IP_RIGHTS: Teams retain full ownership. HACK_2026 claims zero rights over generated output.

CODE_OF_CONDUCT

HACK_2026 is dedicated to providing a harassment-free experience for everyone, regardless of existing attributes.

We do not tolerate harassment in any form. Sexual language and imagery is not appropriate for any event venue.

[ WARNING ]: Participants violating these rules may be sanctioned or expelled from the event.