Step by step
Do this first.
Project submissions
Deliver
Project submissions
Swipe
One team per member
Every member is registered and on exactly one team.
Show the working solution
Required: project name, problem and solution, working demo, 2 to 3 minute video.
Provide accessible code
Required: repository with commit history, README, setup instructions, and technologies.
Record contributions
The README names each member's contribution and discloses templates, libraries, prior work, and AI use.
Start at kickoff
Work starts at kickoff unless a continuation track was pre-approved.
Check completeness
You check completeness, not winners. Escalate suspected copying with evidence; never accuse publicly.
Remote judging and talent signals
Next chapterRead the full chapter
Teams have 2–5 members unless the event page states another approved maximum. Every member must be registered and attached to exactly one team for the event.
Required submission
• Project name; problem, target user, and a concise solution description. • Working demo or deployment and a 2–3 minute demo video usable by remote judges. • Repository or b54-accessible code, readable commit history, README, setup instructions, and technologies used. • A README naming team members and the specific contribution of each person. • README disclosure of templates, starter kits, libraries, pre-existing work, generated assets, and AI-assisted work.
The standard track starts at kickoff. Public libraries, documented APIs, disclosed AI tools, and announced starter kits are allowed. Continuing work belongs only in a pre-approved continuation track and must show the exact before-and-after scope. A copied project, false contribution, hidden prior product, inaccessible code, non-working demo, or unexplained single final code dump can be ruled ineligible.
The Campus Rep checks completeness, not winners. Do not alter a team’s submission after the deadline. Escalate suspected plagiarism or fabrication with evidence; do not accuse teams publicly.