// HACKATHON DOMINATION STACK — 2026

GLITCH
BATTLE PLAN

Walk in. Plug in. Talk. Build. Win.
No typing. No setup. No confusion. No wasted time.

// Every teammate is a force multiplier. Every minute is productive.

3Machines

80GBRAM Pool

5Claude Accounts

9Weapons

10Days to Win

// 001 — THE MISSION

We eliminate three enemies
before we arrive.

Most dev teams lose to the same problems. We've already solved them.

LOST CONTEXT

AIs and humans forget what's going on. We don't. Shared persistent memory across every machine, every agent, every session.

FRICTION TO START

Setup, blank canvas, no structure. We eliminate it. ./onboard.sh — one command. Under 5 minutes. Any teammate. Productive immediately.

COORDINATION OVERHEAD

Who's doing what, what's decided, what's next — visible to everyone. Shared backlog. Shared context. Shared state. Zero meetings needed.

// 002 — THE ARSENAL

~80GB of distributed
compute. On site.

Three machines. One Starlink uplink. All accounts pre-configured. Day zero ready.

Machine	Role	Status
Laptop — 16GB Arch Linux	Orchestrator — brain, context, agent coordination	READY
Mini PC 1	Builder node — runs agents, ships features	READY
Mini PC 2	Builder node — runs agents, ships features	READY
Starlink	Connectivity — low latency, high bandwidth, anywhere	ONLINE

// Pre-Loaded Accounts

Service	Purpose	Status
Anthropic × 5	Primary AI — Claude across all agents	READY
Turso	SQLite in the cloud — shared context store	READY
Supabase × 3	Postgres + Auth + Storage — 3 blank projects	READY
Vercel	Frontend hosting — org account, team invited	READY
Railway / Fly.io	Backend hosting — org account ready	READY
Cloudflare	DNS, CDN, R2 storage	READY
GitHub	Version control, org repos — all teammates added	READY
Deepgram / Whisper	Voice → text pipeline	LOCAL

// 003 — THE STACK

One stack. Pre-wired.
Already running.

Databases

SQLite — Turso (zero-config, instant)

Postgres — Supabase (auth + realtime)

Redis (cache + queue)

Chroma (vector / RAG)

Frontend

Next.js

Tailwind CSS + shadcn/ui

Expo (React Native) if mobile

Backend

FastAPI (Python)

Custom agent loop (Claude + tools)

rq + Redis (task queue)

Typer CLI / Textual TUI

AI / LLM

Claude — Primary (5 org accounts)

OpenAI — Fallback + embeddings

Whisper — Voice in (local)

Piper / ElevenLabs — Voice out

DevOps

Syncthing (P2P sync, LAN + Starlink)

Doppler / .env vault (shared secrets)

Caddy (reverse proxy)

pnpm (JS) + uv (Python)

Auth

Email/password + JWT

OAuth — Google, GitHub

API key — custom middleware

Magic.link — passwordless

// 004 — WEAPONS WE'RE BRINGING

9 tools built
before we walk in.

Nobody else in the room will be operating like this.

WEAPON — 01

⚡ VOICE DAEMON

Always-on voice pipeline on each machine. Push hotkey → speak → Whisper transcribes → Claude responds → code runs. Nobody types. Ever.

WEAPON — 02

🔍 LIVE DEBUGGER

Paste error or speak it. AI reads your logs, git diff, and codebase context. Tells you exactly what broke and where. Specific. Not generic.

WEAPON — 03

⚙ QUICK ONBOARD

./onboard.sh — one script. Installs everything, syncs the module library, connects to shared context, loads the backlog. Any teammate productive in under 5 minutes.

WEAPON — 04

🔗 SHARED PIPELINE

Shared .env vault synced to all machines. Shared backlog. Shared Git workflow. One repo per project. Everyone always working from the same state.

WEAPON — 05

🧠 SHARED CONTEXT LAYER

Persistent memory store (SQLite via Turso) that every agent reads and writes to. Every decision, every completed task, every open problem — always available to every agent on every machine.

WEAPON — 06

♾ POOLED RESOURCES

All 5 Claude accounts load-balanced across 3 machines. ~80GB RAM available as shared pool. No one person is bottlenecked by their machine.

WEAPON — 07

👁 FILE WATCHER

Watches the filesystem in real time. On save → lints, runs tests, checks for errors, auto-logs everything. Surfaces issues immediately without anyone having to ask.

WEAPON — 08

📋 AUTO-LOGGER

Every AI action, every code change, every deploy — logged automatically. Structured. Searchable. Feeds the shared context. Nothing is lost.

WEAPON — 09

📦 MODULE LIBRARY

Pre-built, tested, drop-in modules for everything: Auth, DB connectors, Claude API wrapper, FastAPI boilerplate, Next.js + Tailwind starter, email sender, rate limiter, and more.

// 006 — WHAT PEOPLE WILL SEE

The demo IS
the recruitment pitch.

glitch-voice-daemon — live session

[teammate sits down]

[runs ./start.sh]

[headset activates]

TEAMMATE: "I need to build a user authentication system with Google OAuth."

CLAUDE: "On it. Using the Supabase Auth module. Scaffolding the Next.js pages now. Do you want email/password as a fallback?"

TEAMMATE: "Yes."

✓ Auth pages scaffolded → /app/auth/**

✓ Supabase config injected → lib/supabase.ts

✓ OAuth callback wired → /api/auth/callback

✓ Task marked done in backlog

✓ Shared context updated

[code appears. project runs. nobody else in the room is operating like this.]

GLITCH›

// 007 — 10-DAY BUILD PLAN

The plan is already running.

1–2

Module library — auth, DB, LLM wrapper, API boilerplate

Sync layer (Syncthing) + shared context store (Turso)

Voice daemon — Whisper + Claude pipeline, all 3 machines

File watcher + auto-logger + live debugger

Quick onboard script + shared pipeline and backlog

7–8

Build 2–3 hackathon apps using our own infrastructure

Polish, test, rehearse the demo

Pack. Travel. Arrive ready. Walk in. Win.

// 008 — JOIN US

We're not saying "come join us."
We're showing you a world
you want to live in.

Two steps. Both take under a minute.

⚡

Step 1 — Register for the Hackathon

Sign up on Luma so you're on the guest list. Then come find us — we'll be the ones with the Starlink dish and the voice-driven terminals.

Step 1b — Register with the Glitch Team (magic.link)

Drop your email — we'll send a magic link. No password. Just click and you're in.

💬

Step 2 — Join Our Discord

This is where the team lives. Strategy, build updates, voice channels during the hackathon, and the Discord members who saw it firsthand become our recruits.

Target: 50+ members by end of hackathon. Everyone who sees the demo gets an invite.

Join Discord →

What you'll find inside

› #battle-plan — strategy + updates

› #build-log — real-time progress

› #voice-channel — live during the hack

› #recruits — everyone who saw the demo

GLITCHBATTLE PLAN

We eliminate three enemiesbefore we arrive.

~80GB of distributedcompute. On site.

One stack. Pre-wired.Already running.

9 tools builtbefore we walk in.

8 apps. 2-3 days each.We pick the best one and win.

The demo ISthe recruitment pitch.