Teams work backward from given outputs - images, QR codes, audio clips, source code snippets, metadata, and web pages - to identify the original search queries, prompts, or hidden messages behind them. As clues are solved, new coding requirements are unlocked for the team's assigned app theme. The designated coder begins the Vibe Coding Challenge simultaneously, building out the app as requirements unlock in real time.

• Teams of 3 - 4 members; one member must be designated as the coder before the round begins
• All clues must be solved using only the materials/tools provided by the organizers
• Each solved clue must be shown to a volunteer/judge for verification before the next clue is released
• The coder may only implement a feature once its corresponding clue has been officially unlocked
• No external help is permitted during the hunt
• Use of AI tools for coding is allowed; use of AI tools to solve clues is at the organizers' discretion
• Duration is strictly 1 hour; unsolved clues are forfeited when time ends

Teams tackle progressively harder challenges -hidden websites, passwords, endpoints, images, encrypted text, and missing clues. Each solved challenge unlocks additional features for the coding build, allowing teams to expand their app with creative elements and added functionality.

• Continuation of the same team and coder assignment from Round 1
• Challenges increase in difficulty and must be attempted in the order released, unless stated otherwise
• Each solved challenge must be verified by a volunteer/judge before its corresponding feature can be built
• No sharing of solutions, passwords, or endpoints between teams
• Any tools/platforms used for coding must be declared if asked by judges
• Duration is strictly 1 hour; unsolved challenges are forfeited when time ends

Judges evaluate each team's overall performance - clue/challenge-solving record and the completed vibe-coded app - based on clues solved, creativity, functionality, and implementation quality. Teams may be asked to walk through or demo their build. Final scores are compiled and winners are announced.

• Each team gets a fixed demo/review window to present their build
• Judging criteria: Clue-solving score, Creativity, Functionality, Implementation quality
• No further coding or clue-solving is allowed once Phase 3 begins - only presentation of work completed in Phases 1 & 2
• Judges' decision is final