Build in turns
Three stints of thirty minutes. One person on the laptop, the other two watching and saying nothing.

Chapter 1 of 7: Initializing
Round 01: Registration is open
Build / Switch / Break / Ship
A three-hour AI-powered engineering relay. Three members, one laptop, thirty-minute stints, and nobody is allowed to explain anything out loud. Then a rival team gets twenty minutes to break what you built.
Three people build one thing, thirty minutes at a time, without saying a word to each other.
}How it actually goes
Everything you know about a hackathon still holds, except the parts where your team talks to each other and gets a weekend to do it.
The rule change
What’s different here
Four lines changed. The AI tools stay.
Three stints of thirty minutes. One person on the laptop, the other two watching and saying nothing.
A rival Breaker takes your project and files everything they find. They can report. They cannot edit.
The originals return for fifteen minutes each, fix what matters, and run the ship check before the window shuts.
Whatever you build, its entire purpose must fire from one button.
Take input before the press: text, a URL, a file, or a selection. After the press the workflow runs to completion on its own. No wizard, no “now click Continue.” One press, one outcome.
Build, break, recover, ship, and demo. Your team’s three hours, panel by panel.
During an active stint you cannot talk to your own team. Everything the next person needs to know has to already be in the repository when you stand up. This is the part teams underestimate.
{
"channel": "repository",
"status": "open",
"handoff": "Leave everything the next member needs in the repo before you stand up.",
"todo": "Replace the fixed auth token before the Bug Hunt.",
"note": "#run is the one button. Everything uses its listener.",
"git_log": {
"a1f9c02": "feat: one-button pipeline end to end",
"7c4e118": "chore: README: run steps + known gaps",
"3b8d5aa": "wip: validation, EMPTY CASE UNHANDLED"
},
"permitted": [
"Comments + TODOs",
"README notes",
"Commit messages",
"Clear project structure"
]
}
The repository is the whole handoff channel.
{
"channel": "teammate to teammate",
"status": "blocked",
"during": "Active stint",
"talking": false,
"messaging": false,
"gestures": false,
"blocked_examples": [
"The auth token is hardcoded, swap it",
"Don't touch the router, it's fragile",
"Check the console, you'll see it",
"Just rerun it, it works on mine"
],
"handoff": "The repository is the only thing that travels."
}
No spoken hints, messages, DMs, or gestures to the next member.
Disqualifying throughout all 180 minutes
Open to undergraduates. Basic programming or app-building familiarity recommended. You will be reading someone else’s half-finished code under a clock.

Scan it, or just tap.
Three names, one team. Registration closes when the grid fills at thirty teams.

WhatsApp community
Scan the QR code or tap below to join our WhatsApp group.
]::[Join the communityAssociate Professor
OpenAI Campus Leads · 3rd year
6360892561 / 9663838403