One Click Saga: build, switch, break, and shipSkip intro ↓

Chapter 1 of 7: Initializing

Loading story · 0%
Engineers’ Innovation Week 2026CSE DepartmentDev Track ClubOpenAI collab (pending approval)

Round 01: Registration is open

One Click Saga

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.

180MIN
Total runtime
3MEMBERS
Team size
1DESIGNATED
Laptops
30TEAMS MAX
Grid
{

Three people build one thing, thirty minutes at a time, without saying a word to each other.

}

How it actually goes

You build for thirty minutes.You hand it overin silence.with no notes.mid-thought.and walk off.A stranger tries to break it.Then you ship it anyway.

Build together.Build in turns.

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.

− BEFOREClassic hackathon
team_size:1–5
laptops:one each
talking:allowed
runtime:24–48 hours
·ai_tools:allowed
+ AFTEROne Click Saga
+team_size:exactly 3
+laptops:one, shared
+talking:silent handoff
+runtime:180 minutes
·ai_tools:allowed
01.BUILD90 MIN
m1m2m3
repo → repo → repo

Build in turns

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

stint3 × 30 min
02.BREAK20 MIN
if (input) run()
empty input → crash
// reported, not fixed

Get broken

A rival Breaker takes your project and files everything they find. They can report. They cannot edit.

testerrival team
03.SHIP55 MIN
fixedshipped

Recover and ship

The originals return for fifteen minutes each, fix what matters, and run the ship check before the window shuts.

window45 + 10 min
The regulationART. 01

One button. One outcome.

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.

LegalA text box, then Summarise
LegalA file drop, then Convert
LegalApproved boilerplate, libraries, frameworks
LegalChatGPT and other approved AI tools, throughout
VoidA second essential button after the first
VoidAnything built before the clock started
The relay180 MIN

Five segments. 180 minutes.

Build, break, recover, ship, and demo. Your team’s three hours, panel by panel.

Three windows of thirty minutes. Only the active member may operate the team laptop. Radio silence applies for the full stint: no spoken explanation, no messages, nothing handed over but the repository itself.

Build Relay: 90 minutes

Each team's nominated Breaker is randomly assigned another team's project. They probe logic, validation, usability, accessibility, performance and basic security, then file a report. They may not edit a single line.

Bug Hunt: 20 minutes

The original three return to their own laptop. Fifteen minutes each to triage the Breaker's report, fix what actually matters, and get the product back to shippable before the pit window closes.

Recovery Relay: 45 minutes

Run the organiser's verification tool against the final build and submit. The report is objective engineering evidence placed in front of the stewards. It does not decide the winner on its own.

Ship Check: 10 minutes

Five teams advance to a live demo in front of the judges. Three minutes each including setup. The highest three take the podium: First, Second and Third.

Top 5 Demo: 15 minutes
Five stages · 180 minutes
Relay timeline: Build 90 minutes, Break 20, Fix 45, Ship 10, Demo 15. Different roles, same goal. A brighter tomorrow.
Swipe the timeline to see all five stages →
Silent handoffART. 02

Say nothing. Leave notes.

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.

repository.json

Open
{
  "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.

team-comms.json

Blocked
{
  "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

  • Speaking to your teammates during an active stint
  • Messaging, DMing or screen-sharing a hint
  • Editing, copying or damaging another team's project
  • Any pre-built submission, in whole or in part
  • Plagiarised or unlicensed code and assets
  • Credential access, secret extraction, denial-of-service
EntryOPEN

Take the grid.

Open to undergraduates. Basic programming or app-building familiarity recommended. You will be reading someone else’s half-finished code under a clock.

Date
TBC
Announced with registration
Venue
TBC
Announced with registration
Registration
OPEN
Scan or tap to enter
Positions
1 / 2 / 3
First, Second and Third
One Click Saga brand illustrationRound 01 · Open

CSE Department · Dev Track Club

One Click Saga

Format3 · 180 MIN · 1 BUTTON
QR code linking to the One Click Saga registration form
Register

Scan it, or just tap.

Three names, one team. Registration closes when the grid fills at thirty teams.

Scan to join the One Click Saga WhatsApp community

WhatsApp community

Join the crew.

Scan the QR code or tap below to join our WhatsApp group.

]::[Join the community
Faculty coordinator

Dr. Priyanka Bharti

Associate Professor

Student coordinators

Somesh & Sanjay

OpenAI Campus Leads · 3rd year

6360892561  /  9663838403