Make post-exertional malaise and recovery burden easier to explain.

The useful story is the relationship between load, delay, and recovery.

Mito Map is useful when the hardest part is not listing symptoms, but showing what exertion cost, how delayed the crash was, and whether function actually returned. The goal is not to diagnose ME/CFS. The goal is to make post-exertional worsening, orthostatic burden, sleep disruption, and baseline shifts legible enough to review later.

Start with the trigger window, the function drop, and the recovery lag.

Use one short summary before the next ME/CFS, disability, or family-support follow-up.

The friction point in ME/CFS is often the handoff itself: someone has to explain the trigger, the delayed payback, the function drop, and the recovery lag in a small amount of time. Use the ME/CFS route when that crash-aware summary is still the main job, then route out only if post-viral, orthostatic, or broad overlap framing becomes clearer.

Keep the ME/CFS lane focused, but route out on purpose when another overlap pattern becomes primary.

Use the ME/CFS page when delayed payback, pacing breakdown, crash timing, and lower-baseline stretches are doing the most explanatory work. Do not force every mixed thread into ME/CFS framing if the lead problem has shifted to post-viral relapse drift, upright intolerance, mast-cell-style flares, or one broader multisystem overlap that needs a shared hub first.

Give moderators and advocates one PEM-first routing grid instead of rewriting the handoff logic every time.

Start with the ME/CFS page when post-exertional malaise, delayed payback, lower-baseline stretches, and pacing breakdowns are doing the most explanatory work. Move to another route below when a different pattern is clearly leading or when the tracked signup should attach to a narrower or broader source.

See the current public-safe ME/CFS outreach and proof queue before you share the narrow route.

This route reads the same aggregate-only community-growth status feed used by the public hub, but filters it to the ME/CFS lane so moderators, advocates, and clinic-prep partners can see whether the route is stale, where fixture-only proof is still blocking traction claims, and which recent organizations matched this page.

Copy-ready ME/CFS outreach text for moderators, advocates, or support-group follow-up.

Start with the landing page when someone needs context first. Use the tracked signup when someone is ready to keep their own patient-owned record attached to source community-growth-me-cfs.

Use one short PEM-and-function summary before the next primary-care, neurology, autonomic, rehab, or family-support handoff.

ME/CFS friction often shows up at handoff time: a patient needs to explain delayed payback, a caregiver needs one compact summary before the next visit, or a clinician needs a cleaner picture of what exertion actually cost. This page works best when it becomes the first stable record for those crash-and-recovery handoffs.

Move from public explainer to tracked signup in a fixed order so ME/CFS sharing stays proof-safe.

The ME/CFS lane is currently the top same-day review route in community growth, so the public share order matters. Keep the first touch conservative: open the PEM page first, add the referral handoff or crash tool second, use the tracked signup only when someone asks for their own record, and widen into overlap routes if the thread stops being clearly PEM-led.

Use one public ME/CFS page across support groups, clinic-prep follow-up, and conservative resource sharing.

The first useful ME/CFS handoff is usually public and proof-safe: show the PEM-focused page, let someone see the workflow, and only then switch into the tracked signup if they want their own record. This keeps moderator, booth, and clinic-resource follow-up conservative while still giving people a concrete next step.