The AI chair that runs the meeting. HackBarna AI Summit 26, Barcelona.
Edit docs/tasks.json, push, refresh — this page reads it live.
Looking for build status? This page is the demo-prep board. Where the application actually stands — scaffolding, Google Meet, what is testable today — is in status.html.
Join voice → speaking events → talk-time clock → policy fires → TTS → audio back in the call. If only that works, the demo lands. Everything else is upside.
Someone says "fire". The chair stops the clock, breaks in, offers to alert emergency services, a host confirms out loud, an SMS goes out, and then it deadpan returns the floor and resumes the topic. Task B11. The destination is always the demo phone in the room — never a real emergency number, in any branch.
| When | ears-discord | brain | second surface (cut) |
|---|---|---|---|
| 12:00–13:00 | E1 spike | B1 + B2 | — |
| 13:00–15:00 | E2, E3 | B3, B4 | keys + V1 |
| 15:00–16:00 | E4 | B5 | V1 |
| 16:00 | Integration checkpoint — a real call, a real interrupt (S4) | ||
| 16:00–19:00 | E5 | B6, B7 | V2, V4 |
| 19:00–21:00 | E6 | B8 | V3 |
| 21:00 | Cut line — nothing new starts after this | ||
| 21:00–22:30 | B9 / B10 if alive, otherwise harden | ||
| 22:30 | Dry run, four people, recorded (S5) | ||
| Sun 09:00–11:00 | READMEs, 60-second recording, submit (S6) | ||
That is the honest tension. Discord and brain start together; a second surface starts only once the brain's offline replay loop runs. If it is not working by 21:00, demo one surface and show the seam in the README — the point is that a second surface is one package, not a rewrite.