Builder Pulse

A live mission-control console for AABW: detects stuck builders, generates contextual rescue plans, and gives organizers privacy-safe interventions. No Builder Left Behind.

Comment

Inspiration

Agentic AI Build Week is not only a hackathon; it is a live operating environment. Builders are moving between venues, Discord channels, workshops, Devpost deadlines, team formation, mentor conversations, and demo pressure. In that chaos, people do not usually fail loudly. They quietly get stuck: no team, unclear next step, blank Devpost draft, missed workshop context, venue uncertainty, or no one to ask.

Builder Pulse started from one promise: No Builder Left Behind. Instead of making builders fill out another form, BP uses the event signals they already create and turns them into timely support.

What it does

Builder Pulse is a live Builder Mission Control console for AABW 2026.

For organizers, it detects builders at risk, anonymizes them as privacy-safe Builder # profiles, explains why BP noticed them, and groups the next best actions into an Intervention Queue. The organizer can immediately copy or mark an intervention, with visible feedback, without exposing private identities.

For builders, it acts like a personal event copilot. The Try-It panel simulates a builder's current state, then generates a contextual Rescue Plan: what to do now, what teammate gap matters, what Devpost action is missing, and how to turn the current stack into a visible demo path. The Where You Stand advisor gives qualitative positioning advice without showing cohort statistics or private comparisons.

The live dashboard also includes:

  • A prominent AABW countdown and live pulse layer.
  • Monitoring Station and At-Risk Watchlist directly above the fold.
  • AI-generated rescue plans with newest-action-wins race protection.
  • Daily Builder Briefing and 3-hour mission loops.
  • Devpost readiness, workshop routing, venue routing, advisory routing, and support request catalogs.
  • Read-only connector contracts for future Devpost, Discord, Luma, Telegram, WhatsApp, and Zalo integrations.
  • A gated organizer roster import teaser that signals the production deployment path without uploading private data.

Why it matters

Most hackathon tools are either calendars, directories, or chatbots. Builder Pulse is different: it is an intervention system.

A builder should not have to register again, explain their whole situation again, or search through five websites to know what to do next. BP is designed for zero registration fatigue: Devpost, Discord, Luma, and organizer-approved data can become one private mission layer.

Organizers get the other side of the same system: not a public directory, but a privacy-safe support radar. They can see where the event needs help, which interventions should run next, and how to support builders before the deadline pressure becomes irreversible.

How we built it

Builder Pulse is a TypeScript / Node / Express app with a structured OpenAI reasoning layer and deterministic event-risk engine. The frontend is a polished light-mode SaaS dashboard built for quick voting-round comprehension: the live rescue engine appears first, while deeper infrastructure and compliance details are grouped below.

The reasoning API returns strict rescue-plan JSON, then BP renders it into a clean terminal-style plan panel. We added a request-sequence guard so stale AI responses cannot overwrite newer builder selections. The live VPS deployment runs on Hostinger with Docker and Traefik.

Privacy and safety

BP is read-only first. It does not post to Discord, send Gmail, modify Devpost, or upload rosters without explicit organizer approval. Public display uses anonymized builder labels and qualitative guidance. Secrets stay in local .env or VPS environment variables, never in the client.

Challenges we faced

The hardest part was balancing three audiences at once:

  • Builders need immediate, humane next steps.
  • Organizers need operational clarity without privacy risk.
  • Voters need to understand the value in five seconds.

That led us to restructure the interface around the Detect -> Rescue loop, add immediate action feedback, improve the AI prose so it feels contextual, and separate the live product from the infrastructure blueprint.

What's next

With organizer approval, BP can connect live Devpost status, Discord observer signals, Luma check-ins, and official roster data. The same engine can then route support through Discord, Telegram, WhatsApp, Zalo, email, or web without changing the core reasoning layer.

The long-term goal is simple: every large builder event should know who is stuck, why they are stuck, and what helpful action should happen next.

Built With

Share this project:

Updates