A hackathon team that performs like an E-sport team. Same roster, structured roles, public scoreboard. Three operating principles, each with receipts.
Most hackathon teams assemble for one weekend, then dissolve. Lumen is the opposite. A roster that competes together, season after season. Continuity is what compounds skill, not one-off lineups.
Same core roster shipped ArtBeat at TRON Season 3, returned for Season 5, and again for Season 7 as Gathbook + Malink. Three seasons, one team, accumulating reps.
E-sport teams don't have five generalists who play everything. They have a captain, an in-game leader, specialists. Lumen carries the same model. CEO, CTO, COO, dedicated design, applied AI, blockchain, front-end, back-end.
When a 48-hour clock starts, James does AI, Kevin does the chain, Althof owns backend, Leonard and Akmal own frontend, Filo owns design, Laras runs product. No one plays out of position.
Reputation lives on the leaderboard, not on a pitch deck. We post placements, prizes, and projects publicly. Wins and losses both. The receipts are the work, and the work is the only argument.
19 winning placements out of 30 shipped products, listed publicly with event, prize, and date. No survivorship-biased highlight reel. The full track record is auditable.
Ad-hoc squad assembled the week of the event. Strangers on Day 1.
Permanent roster of 10 that has competed together for multiple seasons.
Five generalists, everyone half-codes and half-designs. Bottlenecks at every layer.
Specialists by craft. AI, blockchain, backend, frontend, design, PM. No double-hatting under pressure.
First commit is at the kickoff. No rehearsal, no muscle memory.
Pre-event scrims and stack-ranked idea reviews. We arrive with a sprint plan, not a vibe.
A pitch deck with selected highlights. Survivorship bias built-in.
A public scoreboard. Wins, losses, and prizes anyone can verify against the source.
Repo archived, Discord goes quiet. ~65% of projects are discontinued.
Selected ideas continue past the deadline as future products. The hackathon was the prototype.
Every E-sport role has a Lumen counterpart. Captain, IGL, coach, specialists by lane. When the meta shifts (AI track, Web3 track, consumer track), we already have the player.
Sets direction, owns the narrative, takes the post-game press.
Calls plays mid-round. Highest-context operator while the clock is live.
Runs scrim schedule, sponsors, and the ecosystem around the team.
Reads the meta, scopes the playbook, owns deliverables and timeline.
Owns the visual identity. What the audience sees first.
High-impact specialist. The build-around player when the meta shifts to AI.
Deep-domain operator. Owns the protocol layer when the bounty is Web3.
Holds the line. Infra, data, APIs: the layer judges don't see but feel.
Two-man rotation on the surface judges actually touch during the demo.
Hackathons are timeboxed performances. We rehearse them like scrims and review them like matches. Every beat below is fixed before the kickoff clock starts.
Founders review upcoming hackathons. Score by prize pool, ecosystem fit, and roster strength. We pick the ones we can actually win.
Idea triage in a single session. Stack-rank three concepts, pick one, lock scope. Roles assigned before the official kickoff.
Filo signs off on the visual system. Leonard and Akmal start building against final mocks, not moving targets.
Internal demo. Whatever isn't shipping by this mark gets cut. The remaining 18 hours are polish, not panic.
Daffa drills the demo with the founders. Three full run-throughs minimum. Judging is a performance, we treat it like one.
Win or lose, every event gets a written debrief. What we'd repeat, what we'd cut, who carried the round. The notes feed the next scrim.