Active beachheads
-
Routes currently in the public-safe stack.
Community Beachheads Referral Handoff
Use one short, route-first handoff before the next moderator, nonprofit, clinic, conference, or family follow-up conversation.
This page is a public-safe route chooser for broad chronic illness threads that still need the right first page before anyone narrows into one label or opens a tracked signup. Start with the public hub, then move into the overlap or bridge route only when the story clearly earns it.
Live Routing Queue
Keep the route-first handoff attached to the current public-safe move-first and proof-gap summary before you share another broad link.
This referral handoff reads the current public-safe community-growth snapshot directly so the hub route stays aligned with the latest move-first pressure, stale lanes, and proof gaps. It is still a public handoff page, not an operator console.
Waiting for first proof
-
Public routes still blocked on first attributable proof.
Top stale lane
-
The highest-priority stale route in the current public-safe snapshot.
Top proof gap
-
The lane that most needs a first import or reviewed-zero pass now.
Loading the current move-first route set for the public hub.
Three-Step Route Handoff
Capture the three details that make a broad mixed-label thread easier to route.
1. What kind of thread is it?
Broad overlap, crash-and-orthostasis, or clearly narrow?
Name whether the thread is still broad, clearly crash-and-upright-load, or already stable enough for a single-condition route.
2. What is the next helper trying to do?
Moderator share, clinic prep, booth follow-up, or family handoff?
Choose the route based on the next task, not just the diagnosis words already in the thread.
3. Does attribution belong yet?
Use the tracked signup only on request.
Keep the public hub, overlap route, or bridge route first. Only attach the tracked signup when someone actually wants their own Mito Map record.
Copy-ready moderator note
One route-first line for broad communities
If the thread spans multiple chronic illness labels and the best first route is not obvious yet, start with the public beachhead hub before narrowing into one condition page.
Copy-ready moderator note:
Start with the public route hub first: https://precisionmito.com/community-beachheads. If the story stays broad, use the overlap route next. If it is clearly crash-and-orthostatic, use the bridge before forcing a single-condition page.
Clinic And Partner Copy
Use conservative wording when a nonprofit, clinic, moderator, or conference volunteer asks for one short explanation.
Clinic resource note
For broad intake or route-choice prep
We are using a public community route directory to choose the safest first tracking page before narrowing into one condition-specific handoff. Public directory: https://precisionmito.com/community-beachheads
Moderator or nonprofit note
For mixed-label community follow-up
If the thread spans ME/CFS, long COVID, POTS or dysautonomia, mitochondrial disease, EDS, MCAS, fibromyalgia, or broader overlap, start with the public route hub before dropping a narrow link: https://precisionmito.com/community-beachheads
Tracked follow-up
Only after someone wants their own record
Tracked overlap signup: https://precisionmito.com/signup.html?next=%2Fmitomap&source=community-growth-complex-chronic-illness
Safe claim line
Keep the framing conservative
Public route selection for patient-owned tracking pages. This is not diagnosis, medical triage, or a replacement for clinical judgment.
Handoff Ladder
Move from route chooser to tracked signup in a fixed order so community, clinic, and booth follow-up stay proof-safe.
1. Public route hub first
Lead with the directory before attribution.
Use the public beachhead hub when the conversation still spans more than one chronic illness label or the best route is not obvious yet.
2. Overlap or bridge second
Choose the broadest useful next route.
Move into the overlap hub when the story is still broad. Use the bridge when crashes, PEM, relapse windows, and upright loss clearly belong together.
3. Tracked signup only on request
Attach attribution only when the person wants their own record.
Switch to the tracked overlap signup only after someone asks for their own timeline, visit prep, or persistent follow-up route.
4. Narrow when the route is obvious
Switch into one condition page only when it clearly helps more.
Move into a single-condition page when the next conversation is clearly PEM-led, orthostatic, mitochondrial, instability-heavy, trigger-driven, or pain-led.
Conference scan order:
public route hub first, overlap or bridge second, tracked overlap signup only on request, then the narrow condition page when the thread clearly leads there.
Route Choice
Use the hub only while the broad route is still the real story.
- Stay on the hub when the thread spans several labels and the safest next route is still unclear.
- Use the complex chronic illness overlap route when the story is still broad but clearly needs one shared timeline before narrowing.
- Use the crash-and-orthostatic bridge when PEM, relapse windows, dizziness, and standing collapse dominate more than the broad hub.
- Switch to one condition page when the next handoff clearly becomes ME/CFS, Long COVID, POTS and dysautonomia, mitochondrial disease, EDS, MCAS, or fibromyalgia led.
Companion Copy Pack
Load the current public-safe booth, moderator, clinic, and partner copy instead of rewriting the route chooser by hand.
This page loads the public-safe community-growth status and companion feed so the broad route handoff still tracks the same proof posture, move-first pressure, and share language as the generated asset stack.
Loading the current route-first companion copy pack.
Proof-Safe Follow-Up
Keep the public route separate from proof logging.
Share the public route hub first, then this shorter handoff page if moderator, clinic, booth, or nonprofit follow-up needs a faster route-first summary. If the conversation turns into a real tracked follow-up, keep the overlap source attached with the tracked signup and log any reply, signup start, completion, waitlist join, or reviewed-zero pass under community-growth-complex-chronic-illness.
If someone only wants a lightweight next step, keep them on the hub, overlap route, or bridge page. Only attach a condition-specific tracked signup after the broad route has already done its job and the narrow story is real.
Mito Map is an organization and tracking tool. It does not diagnose any condition, medically triage a thread, or replace medical care.