Arena: one engine,
every sport.

A bracket that updates while the game is still on. A score a parent-volunteer can keep on a phone after a 90-second walkthrough. A record of who played, when, and how it ended — kept, not lost in a coach's drive. Arena is the tournament platform underneath all of that. Pickleball and bowling came first. The next sport is a folder, not a rewrite.

What Arena is

Arena is the multi-sport tournament platform. Three things, plainly: brackets that redraw the moment a game ends, live scoring a volunteer can run, and an archive that keeps a program's history instead of letting it scatter across phones and spreadsheets. Pickleball and bowling are the first two sports live on it. Basketball, soccer, volleyball, cheer, and cross-country are scaffolded behind the same parts — each one a small sport-specific surface dropped onto an engine that already exists.

One thing to clear up, because the names rhyme. Blast'D! Arena is a laser-tag venue in Frederick that 1891 built end to end — the hardware, the floor, the big board. That's a different case study, over here. Arena-the-product is what happened next: we took the engine that ran Blast'D!'s nights — the part that owns a session, keeps the score, and emails the recap — and made it sport-neutral, so an ordinary pickleball Saturday or a Tuesday bowling league inherits the same machinery. Blast'D! proved the engine on a hardware floor. Arena carries it to every sport that doesn't need hardware to keep score.

The engine underneath has a vocabulary worth naming, because it's the same in every sport. A session is the unit of a game — it moves through a fixed lifecycle (registration, check-in, live, ended, recapped, archived), and the recap email is decoupled, built and stored the instant a game ends so a flaky network at the gym can never lose it. A spectator gets in by typing an email and clicking a one-time link — no app, no account, no password — and that link is also how the program learns who came to watch. None of that is sport-specific. The sport only declares its own rules and its own stat shape. Everything else is shared.

What we built

The split that makes the whole thing work: the engine owns the session, the score, and the recap; the sport owns only its own rules. Add a sport and you write the rules, not the plumbing.

• Live scoring One authoritative game state at the edge, single-writer, crash-safe. The scorekeeper console is touch-first — a parent runs it after a 90-second walkthrough. Spectator phones, a cast-to-TV board, and an embeddable widget all read the same live feed. Sub-second from tap to scoreboard.
• The bracket engine Single-elimination, double-elimination, round-robin, and pool-play-into-knockout. When a game ends, the bracket finds the match, writes the result, and places the winner in the next round — live, on every screen watching. Drop it on a school's existing site as an embed and it updates there too.
• The Sport interface The load-bearing abstraction. Each sport is a folder that declares how to apply an event, how to score, what a box score looks like, and which bracket formats it allows. Bowling exposes a stepladder ladder; cheer exposes a judged ranked list; pickleball exposes round-robin doubles night. The rest of the platform never hardcodes a sport.
• The archive Upload a program's old scorebooks — paper, photos, spreadsheets — and they become live records pages. The catch, on purpose: a person checks every fact against the source before it publishes. The scorebook says it, or we don't render it. That human pass is the difference between a record and a guess.
• Magic-link spectator access A watcher types an email, clicks a one-time link, and sees the board. No app to install. The same link tells the program who showed up — every viewer becomes a known contact, not an anonymous load on a server.
• The recap pipeline The instant a game ends, the recap is built and stored — who played, who won, how long, the night's top lines — then sent. Built first, sent second, so a dropped connection at the gym never costs the recap. A re-send is one button and re-uses the stored copy.

* Projected. Eight sports are the Phase 1 launch target — pickleball and bowling are live today; basketball, soccer, volleyball, football, cheer, and cross-country are scaffolded behind the same engine and roll out in turn.

Where the engine came from

This is the part worth being honest about. We did not invent a tournament engine on a whiteboard. We extracted it. Blast'D! Arena — the laser-tag venue — ran on a session lifecycle, a signed score feed, a recap mailer, and a spectator board that a hundred-game weekend never broke. The good idea was noticing that none of that was about laser tag. A bowling week is a session. A pickleball match is a session. The recap email doesn't care whether the score came from a sensor on a wall or a thumb on a phone.

So the engine moved one layer up, into a contract every sport shares, and the sport-specific part shrank to almost nothing: the rules, the stat line, the look of one card. Two ingestion modes cover everything — a trusted device on the wall signs its scores (how Blast'D! feeds the floor), or a person enters them on a phone and the rules engine checks each one before it counts (how bowling and pickleball work). Same lifecycle, same recap, same board, either way.

A new sport is a folder, not a rewrite. The day adding the tenth sport is harder than adding the second, we built it wrong. — a working principle, written into the Sport interface on day one

Run a tournament.

Below is a small, working slice of what the bracket engine does: a four-team single-elimination bracket. Pick the live match — the one with the glowing edge — and tap the side that won. The bracket advances the winner into the final, exactly the way it does on a live event when a game ends. Switch the sport toggle to see the same engine label the same bracket for bowling. Nothing here phones home; it's the advancement logic, running in your browser.

Why this fits 1891

The pitch on madeby1891.com is for systems built end to end, in Frederick, under one roof — and built so ordinary people can run them. Arena is that pitch applied to a gym floor. The score is visible-first on a board a whole bleacher can read at once. The spectator gate needs an email, not an app download. The scorekeeper console is operable by a parent who arrived ten minutes ago. None of that is an accessibility skin bolted on at the end — visible-first, app-free, plain-language scoring is just what the room needs to work for everyone in it, the deaf grandmother in the third row included.

There's a longer line behind it, too. Deaf sports are not a footnote — they are civic life. The deaf-school sports tradition, the gatherings that have brought communities together since the nineteenth century, the tournaments that were the calendar: that's the lineage Arena quietly belongs to. The gathering, brought forward. A tournament has always been a reason a community shows up in one room and settles something together. Arena is the part of that you can run from a phone now, and the part you can keep afterward.

What's still unfair about this

The promise we made the engine was that the work shrinks as the platform grows. The second sport was hard. The eighth should be easy. If we ever find ourselves adding a sport-specific branch deep in the bracket engine or the live-scoring core, we got the abstraction wrong — and we go fix the interface, not paper over it with a switch statement. That discipline is the whole product. It's also the easiest thing to lose under deadline.

The thing we did not do is hand a league a black-box subscription it can't leave. Every program can export everything — its site, its records, its score history, its change log — in one click, no friction, no retention trick. The archive's accuracy pass stays human on purpose, even though a faster machine-only version would be cheaper to run, because a record nobody verified is a rumor with a logo. We measure Arena by what the bleachers saw and what the program got to keep, not by what we automated.

Nobody in the gym cares about the engine. They care that the bracket was right, the score on the board matched the score on the court, and the recap was in their inbox before they got to the car. — Anthony Mowl, framing the build for Arena

That sentence is the spec. The engine is good because it disappears.