Signal Decoder
A stress response is your system doing its job under real load — not a malfunction. Pick what happened, and read the signal for what it was managing and what it needs now.
Your picks are sent once for interpretation and never stored. The optional describe box never leaves this browser at all.
Not a diagnostic tool. This is an educational reframing tool informed by published research — the allostatic view of stress (Sterling & Eyer, 1988; McEwen, 1998) and autistic adults' own first-person accounts. It cannot diagnose anything, and competent framing does not mean painless: the load and the wear are real.
1 — What happened?
Pick every pattern that showed up. Community words, on purpose — these are how autistic adults describe their own responses, not clinical labels.
2 — How long did it last?
Roughly is fine. Weeks-to-months is a different kind of signal — the decoder treats it accordingly.
3 — What were you holding while it happened?
Optional — but it sharpens the reading. Skip anything that doesn't fit.
4 — Want to write it down first? optional
A private scratchpad, purely local — it is never sent anywhere. Writing can help you see the shape before you pick.
What sits under this tool: the allostatic view of stress — the same response is both protective and wear-and-tear (Sterling & Eyer, 1988; McEwen, 1998) — and the first-person research on what autistic adults' own shutdowns, meltdowns and crashes were doing for them (Raymaker et al., 2020; Lewis & Stevens, 2023; Paris et al., 2025). The decoder deliberately avoids contested mechanism theories; the reading describes function, not anatomy. Companion tools: Early-Warning Tracker (catch the pattern early), Energy Ledger (see the budget), Unmasking Ladder (act on it, safely). The suite's companion essay: unmasking and stress as competence.
How this tool works
You describe one hard moment — a shutdown, a meltdown, a crash — using words the autistic community actually uses: frozen, blue screen, went inside myself, couldn't keep up, explosion, autopilot, long crash. Labels can be combined, because real episodes rarely respect tidy categories. You add how much effort you were holding at the time and how long the episode lasted, and submit once. The interpretation is computed on this site's scoring endpoint and returned — nothing stored, no accounts, nothing kept.
What comes back is a reading of the response, built on one question the tool keeps asking: what was this doing for you? The reading names the competent function the response was performing — protection, escape, load-shedding — what it was managing, moves that help recovery from that specific shape, the honest limits of the reframe, and an unmasking prompt when the episode points at something a small, safe step could change. Episodes are also placed on an acute-versus-chronic axis, because a one-off crash and a months-long one are different conversations — and if your episode has been running three months or more, the safety rail says so plainly and points at more than a web tool.
The research behind it
The framing is stress-as-competence. The allostatic view of stress describes the same response as both protective and wear-and-tear: the system is budgeting energy to protect you, and the protection itself costs (Sterling & Eyer, 1988; McEwen, 1998). This tool never frames that as “stress is good for you” — the reframe pairs the competent function with the honest acknowledgment that the load and the wear are real.
The vocabulary comes from first-person research on what autistic adults say their own episodes were doing: shutdowns (Paris et al., 2025), meltdowns (Lewis & Stevens, 2023; Soden et al., 2025), and burnout (Raymaker et al., 2020; Higgins et al., 2021). The masking-load piece — why the effort you were holding matters — comes from the camouflaging-cost literature (Hull et al., 2017; Pearson & Rose, 2021; Cook et al., 2021). One deliberate absence: the reading describes function, not anatomy. Contested nervous-system mechanism theories are avoided on purpose — this site follows the published critiques of that genre (e.g., Grossman, 2023) rather than borrowing its confidence.
How to use it well
- Decode while it's fresh. Right after the episode, or the next day, when the details — duration, held effort, what preceded it — are still true rather than reconstructed.
- Pick the closest label, not the perfect one. The labels are deliberately community-language; if two fit, select both. The reading handles the blend.
- Be honest about duration. The acute-versus-chronic axis — and the safety rail — depend on it. Rounding three months down to “a rough week” helps no one.
- Treat the recovery moves as a menu. They are ordered suggestions for the shape of response you described, not a prescription; your own knowledge of what settles you outranks any list.
- Keep the reading. Patterns across episodes — the same signal, the same context, the same unmasking prompt twice — are where this tool pays for itself.
What this tool is not
- Not a diagnosis. It reads a described episode; it cannot tell you what you “have”, and it never speaks one.
- Not a nervous-system explainer. No vagal this, no polyvagal that — the readings describe what the response was doing, which is defensible, not where it lives anatomically, which is contested.
- Not a crisis service. If an episode has lasted months, or the reading's safety rail appears, that is the tool doing its job — pointing you toward real support, not substituting for it.
Questions people ask
Why call a shutdown “competent”?
Because the research describes these responses doing protective work — conserving energy, ending an unbearable situation, shedding load (Sterling & Eyer, 1988; Paris et al., 2025). “Competent” describes the function, not the feeling. The reading never pretends the episode was pleasant, or that the cost wasn't real (McEwen, 1998).
Why is there no talk of nervous systems “resetting”?
Because the popular mechanism story is contested (Grossman, 2023), and this site doesn't borrow confidence it can't cite. Function is what the first-person research supports; anatomy is where it doesn't.
What if none of the labels match my episode?
Pick the nearest two and let the held-effort and duration answers carry the detail. The reading is built to interpret blends, not to demand purity.
The reading mentioned three months — what does that mean?
It means the tool noticed you described something chronic, and the burnout research is clear that months-long episodes deserve more than self-management (Raymaker et al., 2020). The signposting that appears is the tool saying so honestly.
Where to go next
- Early-Warning Tracker — catch the pattern weeks before it becomes a crash.
- Energy Ledger — see the daily budget the episode spent.
- Unmasking Ladder — act on the unmasking prompt, safely.
- Unmasking and stress as competence — the companion essay.