LIVE · SLACK BOT
Boardroom. Thirteen advisors on retainer, minutes in Slack.
- Status
- Live in a restricted channel
- Client
- M4U Events leadership
- Stack
- Next.js · Vercel · Claude · Slack API
- Scale
- 13 personas · 29 tests · 5-minute debates
- Year
- 2026
13 advisors, one questiona real debate, not one model’s opinion
The problem
Small-business decisions get made alone. A real advisory board — an operator, a marketer, a CFO-shaped skeptic arguing with each other — is something a ~30-person events company will never have on retainer. One AI answer isn’t a board; it’s a vibe.
What I shipped
- ◆/board <question> in a restricted channel convenes 4–6 of thirteen personas — the seats most relevant to the question, chosen by a router with hard invariants (a chair always sits; at least one counterweight always argues back).
- ◆A real debate structure — independent critiques first, then a rebuttal round, then minutes: positions, disagreements, and a recommendation.
- ◆Living context, no redeploys — the bot re-reads a team-editable Slack Canvas of business context on every run; the team widens the board’s knowledge by editing a doc.
- ◆Fail-closed security — Slack signature verification plus an allowlist where an empty list authorizes nobody.
How it works
- 1/board “Should we raise our travel pricing?”
- 2Router seats 4–6 relevant personas (chair + counterweight guaranteed)
- 3Independent critiques → one rebuttal round
- 4Minutes posted back to the channel, grounded in the live Canvas
The hard part
Making disagreement structural. Ask one model for advice and it agrees with itself. The router’s invariants force a counterweight seat into every session, personas argue from distinct briefs, and the rebuttal round happens before minutes are written — so the output preserves who disagreed and why, which is the part a founder actually needs.
Proof
- ✓29 network-free unit tests: routing invariants, signature verification, allowlist, minutes format.
- ✓Live verification: a real strategy question returned grounded minutes; a marketing question routed to marketing seats.
- ✓Kill switch in config; the README documents residual risk honestly.
/board Should we expand to corporate events?
Seated: chair, ops, sales, CFO-adversary…
Minutes: 2 in favor · 1 opposed · risks listed
Where it stands
Live. Leadership self-serves a structured second opinion without the founder in the loop — and the board’s knowledge grows by editing a doc, not shipping code.
I designed the routing and the invariants that force the panel to disagree. Claude Code built it, and the personas are Claude too. How I work →
Run an events business? I built Ajna for you.
AI automation for wedding & event vendors — quotes in minutes instead of days, a human always in the loop.