Eligibility and registration

Participation is free and intended for BBDITM students. Your college is fixed to BBDITM. A verified email identifies your account, but does not by itself verify enrollment. Organizers may request eligibility evidence. First-year enrollment numbers are optional references; other years need a required, unique enrollment/roll number.

One regular attempt is allowed per student for the event. Only the owner can authorize an exceptional reset; previous work and the reason are retained. Students cannot reschedule their own slot. Contact the organizer before starting if your booking needs a change.

Time and submission

All students in a slot share one server-owned deadline. A 2–3 PM slot still ends at 3 PM if you join at 2:20 PM. Slot dates and times are displayed in Asia/Kolkata (India Standard Time). Your booked slot specifies duration and exact schedule.

Connection loss does not stop time. Autosave shows whether work is saved to the server or remains local. Early submission requires confirmation and locks your attempt. At the deadline, the latest server-accepted work is finalized even if your tab is closed. Unsynced late edits are not automatically accepted; only an explicit audited owner exception can address them.

Authorized organizers can postpone, pause/resume or end a slot. A pause freezes remaining time and resume adjusts the shared deadline. Exceptional extensions are logged. Always follow the current server state shown in your dashboard/workspace.

Your workspace and AI

Use a laptop/desktop, a modern browser and a physical keyboard. The preconfigured React + JavaScript project supplies its dependencies and simulated APIs. Arbitrary package installation and project networking are not supported.

You may use the built-in token-limited AI assistant with your own Gemini key. Challenge instructions and the active file are attached visibly by default; you choose additional context. AI proposes changes for review. You remain responsible for applying, testing and explaining your solution. Provider project quota and billing apply independently of the event allowance.

Public tests are useful evidence, not the final correctness score. Never treat a displayed public pass as proof that every published requirement is satisfied.

Judging: 65 / 20 / 10 / 5

• 65% correctness: private tests against published expected behavior.
• 20% code quality: maintainable changes and sound engineering choices.
• 10% explanation and verification: investigation, reasoning and convincing tests.
• 5% AI efficiency: purposeful prompting, useful progress and independent validation—not simply spending the fewest tokens.

Correctness comes first. Time is only a final tie-breaker after the rubric components. The owner must approve the precise manual scoring and finalist-verification policy before public release. A full score remains possible. Students see their own approved scores and feedback after owner release; there is no complete public ranking.

Fairness and review

The assessment runs in fullscreen. The app records when you leave fullscreen, switch tabs, or move to another window for more than two seconds, and when you try to paste or drop text that did not come from inside the workspace. Copy and paste work only inside the workspace: selected code is not placed on your system clipboard, and text copied elsewhere is ignored. Two warnings are followed by a human-review flag; these signals never disqualify you automatically, and organizers read the timeline before deciding anything. Notifications, sleep or accidental keys can cause signals, so an isolated event is not held against you.

The built-in AI assistant is allowed and is the supported way to use AI. Using other AI tools or another person, on this or another device, is not allowed. The app cannot see other devices, so finalists may be asked to explain or modify their solution live. No camera or microphone is used and nothing is recorded from your screen.

Later competitive slots use different calibrated variants. Activity evidence and finalist explanation/modification help organizers assess work fairly. Respect the published event instructions and do not attempt to access other accounts, hidden grading material or later-slot challenges.

Recognition and communication

The owner approves the top three. AlgoZenith goodies and recognition may be awarded; exact award details are confirmed by organizers, and no monetary amount is promised here. Booking confirmations and reminders depend on configured email delivery. Keep your dashboard booking details even if an email is delayed.