Rules
Operational Parameters
Every participant entering HACKVIZ 2K26 is expected to uphold the spirit of innovation, integrity and professionalism. These protocols ensure a fair, collaborative and secure hackathon experience for every team.
03
Team Size
24 Hrs
Execution Window
100%
Original Code
/ PHASE 01
Mission Enrollment
Team Thresholds
Verified Operatives
Gateway Clearance
Every mission team must consists of exactly three members. Each participant may join only one team, and team composition cannot be modified after registration closes.
Every operative must present a valid college ID during registration. Only officially registered participants will receive mission clearance to enter HACKVIZ 2K26.
Complete registration before the deadline and report only during the official check-in window. Incomplete registrations or false information will result in immediate disqualification.
SYSTEM INTEGRITY
Guidelines of Participation
Original Genesis
Responsible AI Usage
Professional Conduct
Every solution must be designed and developed during the 24-hour hackathon. Pre-built projects or copied implementations are strictly prohibited. Innovation begins from scratch.
AI tools such as ChatGPT, Gemini and GitHub Copilot may assist development, but every team must fully understand and explain their implementation during evaluation.
Respect judges, mentors, volunteers and fellow participants at all times. Collaboration, integrity and professionalism are expected throughout the event.
EVALUATION PROTOCOL
Decryption Criteria
Innovation & Creativity
Technical Implementation
Prototype Demonstration
Every solution should demonstrate originality, creative thinking and a unique approach to solving the selected challenge. Judges will evaluate how effectively your idea stands apart from conventional solutions.
Build a fully functional prototype with strong architecture, reliable performance and seamless integration. Code quality, technical execution and system stability will be carefully assessed.
Present a working solution that clearly addresses the problem statement. Teams should confidently demonstrate functionality, explain implementation decisions and showcase the real-world impact of their innovation.