Meeting Overview · Last updated May 2026
Base camp for adults navigating ADHD in the real world.
A purpose-built Discord community for your readers. Seven custom bots provide structured daily support, accountability, co-working, community engagement, resource access, and guided member onboarding — plus a book club and Patreon integration as server-level features.
Not a general ADHD server. Every channel and every bot exists for a specific reason. Everything here is designed around how ADHD brains actually work.
Three Principles
Three commitments that define every design decision.
Server Structure
Six areas. Each with a specific purpose. Click any card to explore it in detail.
Cate Osborn — Camp Director (our recommendation)
Camp Staff
Each bot has exactly one purpose. No bot does two things.
Universal rule: no DMs, ever. All bot interaction stays in-channel.
For Cate & Erik
What the server gives back.
Discord Stage for live discussion plus a Forum channel for session threads. Members stay connected to the Stage while posting in the thread alongside — both open at once.
Each session is one command. Activities Director creates the Forum thread and Discord Event together — titled, tagged, prompt already in the body.
Frequency: weekly or biweekly — your call. We recommend biweekly to start.
Discord's native Patreon integration. Supporters receive their role automatically when they connect, and lose it if they cancel.
Zero manual management. No bot. No spreadsheet.
Intimacy, not exclusivity. A monthly drop-in from you is the value proposition. The structure supports it; the effort is yours to define.
Six Questions
Only you can answer these. Everything else is already built.
Everything here is a recommendation, not a prescription. The server's success depends on your voice running through it. If the name doesn't feel right, it changes.
In practice: input on the server name, the tone of #welcome-to-camp, the language of the roll-call prompt, and how the bots' messages should sound. The first things members see should feel like they could have come from you directly.
Camp Director captures the role: tone-setter, culture-definer, occasional presence. But you may have a better instinct for what to call yourself.
Alternatives: Camp Director, Founder, Head Counsellor, Field Director, Lead Guide. The right answer is whatever you'd naturally say when introducing yourself to the community.
Biweekly: lower prep burden, more time for async discussion, easier to sustain long-term.
Weekly: stronger rhythm, more touchpoints, members who miss one session only wait a week.
Our recommendation: start biweekly. Moving up is easy once there's demand. Moving back feels like a retreat.
The structure supports early access to prompts, direct Q&A, behind-the-scenes content, and supporter-to-supporter community. Exact offering: your call.
What not to put here: ADHD strategies unavailable to free members, bot features non-supporters can't use. These harm community trust and Patreon retention simultaneously.
The mod team needs to exist, have clear authority, cover active hours, and be trained on the crisis protocol before launch. Compass creates the handoff — the mods need to be ready to receive it.
Your input on the escalation path is required before the server opens.
Minimum: your name and public endorsement, input on the brand and welcome voice (one time), occasional Fireside drops (monthly is plenty), availability for serious mod escalations.
Not required: daily presence, responding to every message, writing prompts, or any technical work. Everything else runs automatically.