Discord Bot Platform  ·  View 03 of 19  ·  People and journeys

Actors and Core Journeys

Builders, communities and operators, in their own words.

Editable source SVG draw.io All views
Builders Hobbyist bot developer millions, 1–50 servers Goal — Get my bot answering a slash command in my friends' server tonight, and know why when it does not. Core journeys Build and install a first bot Fix a failing command Popular-bot operator thousands, 100k+ servers Goal — Run the bot across hundreds of shards and stay under every limit without waking anyone at 3 a.m. Core journeys Scale from 1 to 64 shards Survive a reconnect storm Communities Server administrator tens of millions Goal — Add a bot knowing exactly what it can do, and remove it the moment I regret it. Core journeys Install with scoped permissions Revoke or narrow a bot Server member 150 M monthly Goal — Type a command and get a response that either works or clearly says it did not. Core journeys Run a slash command Press a button Operators Trust and safety analyst platform staff Goal — Suspend an abusive application in a minute without touching anyone else's bots. Core journeys Suspend an application Reset a leaked token Platform SRE Goal — See which shards are unhealthy before developers tell me. Core journeys Drain a Gateway node Discord Bot Platform — Actors and Their Core Journeys v 1.0 · owner Integration Platform Architecture · date 2026-10

What the cast tells us

  • The hobbyist and the popular-bot operator need different things from the same API: one needs a reason, the other needs a number.
  • The server member never sees the platform. Their only experience is the three-second window.
  • Administrators are the authority; developers are suppliers.

Assumptions

  • Journeys 04 and 05 carry the most value: the first bot and the first command.