ADHD Field Camp
for Adults

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. The structure is the proposal; the character is yours to define.

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. The title appears in welcome materials and how mods refer to your role in the community.

Alternatives worth considering: 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 preparation burden, more time for async discussion, easier to sustain long-term, more accessible for unpredictable schedules.

Weekly: stronger community rhythm, more touchpoints with the book, members who miss one session only wait a week.

Our recommendation: start biweekly. Moving from biweekly to weekly is easy once there's demand. Moving back feels like a retreat. Once the community is established, a poll in #suggestion-box gives clear signal on what members want.

The structure supports early access to prompts, direct Q&A with you, behind-the-scenes content, and supporter-to-supporter community. The exact offering is 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.

Patreon supporters get closer access to you — not a better version of the ADHD support. Your presence is the product. A monthly drop-in is genuinely valuable and genuinely sufficient.

The mod team needs to exist, have clear authority, cover active hours across time zones, and be trained on the crisis protocol before the server opens. Compass creates the handoff — the mods need to be ready to receive it.

When a member reaches full shutdown in /unstuck, Compass checks for an on-duty mod and notifies them immediately. That mod needs to know what to do next — not figure it out in the moment. Your input on the escalation path is required before launch.

What the server needs at minimum: your name and public endorsement, input on the brand identity and welcome voice (one time), occasional drops into The Fireside (monthly is plenty), and availability if the mod team needs to escalate something serious.

What it does not need: daily presence, responding to every message, writing prompts every week, or managing any technical work. Everything else is already built and runs automatically.