MODERN RECOVERY ALLIANCE
Visibility, participation and the first 90 days
Founding proposal • 6 October 2026 • For member review
Recovery that evolves with the world.

1. WHAT WE ARE INVITING PEOPLE INTO

MRA is a proposed community for people seeking change around substance use and mental wellbeing. Its immediate offer is participation in building that community: examine a draft charter, say what support is missing, help test accessible meeting formats, and take a bounded volunteer role. It is not yet an established treatment provider, a proven recovery intervention, or a national network. Outreach must state the stage honestly.

Positioning statement: “Modern Recovery Alliance is a community being built around dignity, shared responsibility, and recovery informed by current evidence. We welcome different recovery goals and work together on practical support, safer participation, and a life people have reason to keep building.”

The distinctive combination is not a claim that MRA invented harm reduction, multiple pathways, or peer support. It is a proposed way to put them into practice: member-defined milestones without a status ladder; evidence summaries that disclose uncertainty; accountable community decisions; and concrete protection against exploitation. SAMHSA describes recovery as personal and occurring through multiple pathways, and its peer-work principles emphasize voluntary, person-centered, collaborative relationships.[M1, M2] Those sources inform the design; they do not validate MRA’s effectiveness.

Why join now? To help decide what the first version should be. Offer real choices before asking for commitment: review one principle; name a barrier to participation; help verify a resource; observe an orientation; or volunteer for one defined task. Watching quietly is a valid form of participation. Nobody owes a recovery story to obtain a voice.

2. WHO THE FIRST INVITATION SERVES

Start with three groups: adults who independently express interest in different recovery approaches; people already in the existing Discord who choose to help build MRA; and potential collaborators such as peer workers, community groups, and clinicians willing to critique resources. These are roles people select, not diagnoses inferred from profiles, video viewing, purchases, or membership lists.

Invite those who value abstinence alongside people using prescribed medications, therapy, harm reduction, or combinations of support. Do not promise that every approach fits every medical situation. “Your goals deserve respect; individual treatment decisions belong with you and qualified professionals” is more precise than “everything works.” Family and allies can contribute in designated spaces while members retain control over their own experiences.

Avoid a campaign built around attacking existing fellowships. “Recovery that evolves with the world” expresses the positive proposition. “Recovery stopped in 1930” needlessly makes potential members defend a support system they value. People can participate in MRA and other communities. Secular shared governance can welcome personal faith without requiring it or subjecting it to ridicule.

3. A PUBLIC IDENTITY THAT BELONGS TO THE COMMUNITY

Use “Modern Recovery Alliance” prominently in profile names, page titles, posters, and introductions; use MRA as the secondary shorthand. Adopt the proposed navy/cyan visual system, with readable type and plain-language descriptions. Do not carry over IHOCAIHAG’s shock imagery, merchandise offers, or promotional handles into the MRA identity.

Ryan’s project can make a transparent founding introduction: “I’m helping convene this, and the community will decide its direction.” It should not become the permanent public voice, mailing list owner, or commercial gateway. Participation must never require a purchase, following the artist, appearing in footage, or endorsing his politics. Support-room activity must never become documentary material.

The existing Trap House Discord can be the first co-design headquarters. Create a clearly identified, opt-in MRA area, explain the relationship, and keep project promotion and graphic archive material outside it. Merely joining that server must not enroll someone into MRA or an outreach list. Before inviting new people, test the newcomer view with a non-administrator account. “Private channel” describes an access setting, not guaranteed confidentiality.

Ask the founding group to decide whether a separate MRA server or other home is needed. Preserve a public, accessible copy of the charter and participation instructions outside Discord when a community-controlled destination is ready. Until then, invitations should explain where they lead. Do not announce an invented website address, meeting schedule, legal status, or active service. Test every actual destination before publishing it.

4. COMMUNICATION PEOPLE CAN CHOOSE

Use one invitation in the appropriate existing-server channel, with a clear way to request updates. Follow up with people who opt in or begin a conversation. No bulk individual DMs, scraping, bought lists, unsolicited health-related outreach, or repeated contact after silence or refusal. A decision to leave should end reminders.

Record only what is necessary for communication: preferred contact route, explicit subscription choice, and unsubscribe status. Keep outreach records separate from support conversations. Do not create advertising audiences from recovery-room participation, diagnoses, treatment information, or inferred vulnerability. Public aggregate engagement is enough for this pilot.

Official copy should use respectful, person-first language, while letting members describe themselves in their own words. NIDA’s language guidance recommends avoiding stigmatizing labels.[M3] Do not turn language preferences into a test of belonging. Public posts should explain the community’s actual work, rather than displaying drug use, crisis footage, or dramatic “before and after” narratives to attract attention.

No member testimonials during the first pilot. Report process instead: what members proposed, what changed, and what remains undecided, in non-identifying form. Later personal storytelling must be new material arranged outside support, with separate, specific, unpressured permission and a clear explanation that public reposts cannot be fully recalled. Consent to support is not consent to publicity.

5. THE SIMPLE PARTICIPATION PATH

A useful public message leads to a short welcome page or post containing: the name; two sentences explaining the proposal; current age/access rules; what is actually available; conduct and reporting links; limits of peer support; and one clear next step. Initial call to action: “Read the founding draft and tell us one thing the community needs.”

After joining, people may read, ask a question, attend an announced orientation, suggest an edit, or help with a small task. Do not force an introduction, autobiography, diagnosis, camera use, or vote. Provide text participation and a simple way to ask about accessibility. State expected moderator availability and acknowledge that replies may take time.

Make the first contribution easy: a 15-minute resource check, a plain-language edit, an accessibility test, or a suggestion for the first community discussion. A newcomer should be able to answer “What can I do here?” without scrolling through a founder’s content archive.

6. CHANNELS AND EDITORIAL APPROACH

For the pilot, maintain one public discovery channel well, plus Discord and a public information page. Choose the social channel after asking the interested founding group where they already participate. Ryan’s existing channels may share a founding invitation, but MRA should develop its own authorized accounts and publishing access.

Use three recurring content types. “Build with us” asks one consequential question and later publishes what changed. “Evidence in plain language” explains one carefully scoped finding, with source, date, limitations, and qualified review where needed. “Life worth building” discusses ordinary goals and barriers without ranking people by employment, housing, family status, or abstinence duration. Include the optional milestone concept without soliciting intimate disclosures.

Public comments are for general questions. Move sensitive support requests toward the appropriate, explained support route without requiring disclosure in public. Do not diagnose commenters or debate personal medication plans. Publish corrections visibly. There is no assumed best posting time or guaranteed distribution tactic here; test a manageable cadence and assess meaningful participation.

7. A 90-DAY PLAN WITH LAUNCH GATES

Days 1–14: prepare before promotion. Recruit at least two people besides Ryan who can take defined responsibilities; one handles welcome/operations, another resources/communications, with moderation covered separately or explicitly shared. Publish a draft charter and reporting route. Test permissions, newcomer access, and an absence handover. Hold a listening discussion only when facilitators and availability are confirmed. Invite existing interested members with one opt-in announcement. Output: a working welcome path and a recorded list of unresolved decisions.

Days 15–30: a small founding pilot. Proposed planning range: 8–20 interested adult contributors, not a recruitment forecast or a service-capacity promise. Run two facilitated co-design sessions, with asynchronous text options. Seek feedback from three potential external reviewers. Publish one evidence card and one design update per week. Record which ideas changed the draft. Gate: proceed only if reporting, ownership, coverage, basic conduct procedures and the independent reviewer arrangement work; otherwise continue preparation and stop adding invitations.

Days 31–60: run the four-week support pilot described in Community Operations, only after its readiness conditions pass. If staffing and independent-review capacity permit, schedule at most one facilitated peer-support meeting per week and one monthly governance discussion. Confirm whether the activity is a planning session, educational discussion, or peer-support meeting; do not imply a clinical service. Introduce optional milestone recognition and evaluate whether it creates pressure. Test a different host from Ryan. Share a public “You said / we changed / still unresolved” update. Ask community partners for critique before asking for referrals.

Days 61–90: decide what deserves to continue, complete charter decisions and elect the first ordinary stewards before the 90-day interim mandate expires. Review accessibility, member feedback, incidents, volunteer workload, and unresolved governance questions. Ratify, amend, or defer the charter through the agreed process. Decide on independent hosting and financial arrangements. Publish a restrained pilot report covering what was offered, what members reported voluntarily, limitations, and next decisions. Expand only when members want it and operational capacity supports it.

8. FOUR-WEEK CONTENT STARTER

Week 1: Publish the founding invitation and an explainer, “What MRA is proposing—and what is still yours to decide.” Community prompt: “What makes it easier to return after being away?” Action: review the draft welcome process.

Week 2: Publish an evidence note on person-directed recovery and a plain-language explanation of the peer/professional boundary.[M1, M2] Community prompt: “What would help you feel heard without being pushed to disclose?” Action: test a text-only orientation.

Week 3: Explain voluntary milestones: asking for support, setting a boundary, maintaining a routine, or a personally chosen abstinence anniversary. State that no milestone buys authority or access. Community prompt: “What should we never turn into a competition?” Action: review token rules.

Week 4: Publish the first decision record and introduce a volunteer role with its hours and boundaries. Community prompt: “Which of these two meeting formats should we test?” Action: nominate a co-host or offer accessibility feedback.

Each week has at most two public posts, one community prompt, and one short response window assigned to a named volunteer. Reuse the underlying idea across formats; do not copy support-room messages into content. Pause publishing if moderation or welcome capacity is overwhelmed.

9. PARTNERSHIPS THAT ADD ACCOUNTABILITY

Seek conversations with local peer-support organizations, harm-reduction groups, recovery community organizations, public libraries, campus wellbeing or recovery programs, and treatment services that respect multiple pathways. Start with a short, public-facing explanation and request a bounded review. Do not imply endorsement because someone answered an email or because MRA cites their work.

Ask: Are our boundaries clear? Is a resource inaccurate? What accessibility barrier are we missing? Could someone review one proposed session outline? Offer an opportunity to decline, with no expectation of free ongoing professional labor. Record scope, conflicts, and permission before naming a collaborator publicly. Do not pay for patient leads, promise referrals, or accept funding conditions that give a sponsor control over treatment discussions. Compensate substantive work where resources permit and disclose the arrangement.

10. WORKLOAD, BUDGET AND CONTINUITY

These are planning envelopes, not vendor quotes. Co-design preparation only: three volunteers contributing roughly two hours each weekly, approximately six hours total; $0–$50 per month for necessary operating costs, using available tools. Allocate two hours to co-design and welcome, two to moderation/operations, one to resource review, and one to publishing/administration. For the live-support phase, plan at least 10-12 team hours weekly: two person-hours for the meeting itself, two for preparation/accessibility/follow-up, three for moderation and administration, and three to five for resources, welcome and community decisions. Independent complaint or appeal review requires additional reserved time and a confirmed reviewer arrangement; it is not included in this baseline. Six hours cannot cover continuous monitoring. If the actual load exceeds this, reduce activity and invitations.

Supported pilot: approximately 12–16 team hours weekly and $150–$400 monthly, prioritizing accessibility, volunteer training, secure account administration, and modest compensation for specifically scoped expert review. These funds do not purchase a clinical service or 24-hour support. No paid advertising in the initial 90 days; first show that newcomers can understand, participate, and receive appropriate responses.

Every role needs a backup, a short handover, and a shared decision record. Use authorized individual account roles rather than informally distributing passwords. Keep control arrangements transparent and compatible with the chosen platform. If the founder disappears for two weeks, two other named stewards should be able to maintain notices and scheduled activities. If coverage fails, pause new invitations and live sessions, publish the pause and support limits, and keep essential information readable.

11. WHAT SUCCESS MEANS

Track modest, voluntary indicators: whether newcomers understand the offer; whether people feel respected; whether they can participate without disclosing; whether they know how to report a concern; whether ideas receive a documented response; and whether activity can continue without the founder. Optional monthly prompts can use “yes / partly / no / prefer not to answer,” plus a comment box that explicitly discourages identifying health details.

Operational counts may include completed orientations, returning voluntary contributors, overdue moderation tasks, and work hours. Small-group numbers can expose individuals: report cautiously, suppress revealing breakdowns, and do not publish identifiable incident details. Never reward moderators for low complaint counts; fewer reports may also mean people distrust reporting.

Pilot hypotheses to review at day 30: most respondents can locate the reporting route; at least two non-founder members complete a bounded role; every formal proposal receives an acknowledgment or scheduled review; and workloads remain within the agreed envelope. These are service-design checks, not clinical outcomes. Do not claim reduced relapse, reduced mortality, or treatment efficacy from engagement, anecdote, or a small voluntary survey.

12. READY-TO-ADAPT COPY

Founding invitation:
“Modern Recovery Alliance is taking shape, and you can help decide what it becomes. The proposal brings together different recovery pathways, current evidence, lived experience, and practical community support. We’re starting with the foundations: how people participate, how decisions are made, and how we protect each other. You can read, question, suggest, or take on a small task. No personal story required. Join the founding conversation through our verified invitation.”

Milestones post:
“What counts as progress in your life? Asking for support. Setting a boundary. Returning after a difficult stretch. A goal you chose for yourself. MRA is proposing optional milestones without ranks, resets, or special status. Help us design recognition that encourages people without measuring their worth.”

Partner approach:
“We’re developing Modern Recovery Alliance, a member-led recovery community currently in its founding stage. Would someone on your team be open to reviewing our short welcome and safety outline? We’re asking for critical feedback on scope, accessibility, and boundaries—not endorsement or referrals. We can agree on a small scope and discuss compensation if it requires substantial work.”

FAQ:
“Is this Ryan’s fan community?” MRA is proposed as an independently governed community. His existing Discord is a starting place; its future structure is for members to decide.
“Must I follow one recovery method?” No. Respecting different goals is part of the proposed charter; peers do not prescribe individualized treatment.
“Must I tell my story?” No. Listening, practical contribution, and privacy all belong here.
“Is this therapy?” No. The pilot is community-building and peer activity within stated limits; professional care remains separate.
“Can I leave and come back?” Yes, subject to the same conduct and safety rules. Absence is not a debt.

SOURCE NOTES
[M1] SAMHSA, About Recovery. https://www.samhsa.gov/substance-use/recovery/about (official search record accessed 6 October 2026). Supports personal recovery and multiple pathways; does not evaluate MRA.
[M2] SAMHSA, Core Competencies for Peer Workers. https://www.samhsa.gov/substance-use/recovery/peer-support-workers/core-competencies (official full-text search retrieval accessed 6 October 2026). Supports voluntary, person-centered, relationship-focused and trauma-informed peer practice; not evidence for this specific marketing plan.
[M3] NIDA, Your Words Matter. https://nida.nih.gov/sites/default/files/NIDAMED-Your-Words-Matter-508-FINAL-5-12-21-ln.pdf (official search record accessed 6 October 2026). Supports person-first, non-stigmatizing public language. Respect individuals’ own chosen self-description.
All schedules, budgets, thresholds, campaign ideas and operating choices above are proposals for MRA to test, not externally established best practices or promised results.
