Decode:Talk

Decode:Talk is a Demismatch tool. You describe a situation - something you're feeling, something that happened, a pattern you can't name - and it responds with the evolutionary read: what circuit is firing, why, what it was built to resolve, and where the modern environment diverges from what it expects.

It names what is happening, then what would resolve it, then the nearest real move. It does not flatter you and it does not sell you a coping tip.

Below: four exchanges from the live tool. Grounded in the Cor atlas (v4 - 15 mechanisms, M1-M14 plus R1 Touch).

Decode:Talk is not therapy and it is not medical advice. It does not diagnose anything, and it is not a substitute for professional care. If something in your life needs a doctor or a therapist, please go and see one.

Open Decode:Talk
EX · 01 / Status monitoring on feeds
Why do I feel so inadequate scrolling through my friends' lives?
Mechanism
M5 Status Monitoring
Proxy
Compressed highlight reel delivered as band data
Need
Respect from people who know you - rank inside a group of about 150 you actually co-exist with

Your status monitor (M5) is firing on the compressed highlight reel of two hundred people, delivered to you as if each of them occupied a slot in your band.

The circuit that produces this feeling - envy, inadequacy, quiet defeat - was built to track relative rank in a group of about 150 you see face-to-face. It runs continuously and silently; you cannot switch it off. It is not a defect. It is a signal: "they have what you want, do something about it."

In the environment your organism was calibrated for, that signal drove you toward a goal you could actually reach - your rivals were in your camp, their wins within your grasp. On a feed, the "rivals" are strangers whose achievements have no causal relationship to yours. The circuit does not know that. It just reads visible rank change and runs the defeat subroutine.

The nearest move is not to quit the feed. It is to give M5 something real to calibrate against. One recurring context where the same people see you week after week, where your competence is visible, where rank is stable enough to feel earned. A class, a team, a regular game, a project with a small group. The feed does not disappear, but it stops being the only data your status monitor has.

You are not shallow. You are running a 300,000-year-old calibrator against a stream it was never built for.

EX · 02 / 3 am dread
Why do I wake up at 3 am with dread about nothing specific?
Mechanism
M1 Threat Management × M3 Social Bonding (Coan, Social Baseline)
Proxy
Silent room, solitary bed, no ambient band presence
Need
To be touched - the proximity of a trusted body, even sleeping, even silent

Two systems in conspiracy: your threat detector (M1) and your social co-regulator (M3).

The prefrontal cortex - the part that suppresses rumination - is at its weakest between two and five in the morning. Open loops your daytime self keeps locked surface without inhibition. Add one more signal: your social co-regulator is reading "alone." In the EEA, 3 am was not solitary - the camp was present, someone was stirring, someone was breathing next to you. Your threat system is calibrated to treat the proximity of trusted others as safe.

Without that signal, your threat detector runs at a higher baseline. Anything ambiguous becomes a threat. The dread attaches to nothing specific because everything is specific - your brain is just offering candidates.

The nearest move is not to solve the open loops at 3 am. That asks the cortical override machinery to run when it is at minimum capacity. The move is earlier: reduce the ambient threat load before sleep. One loop closed before bed - a sent message, a written-down decision, a task marked done - gives the system slightly less to surface. And if there is a trusted body you could sleep near, even a friend, even a dog, your M3 reads proximity as the safety signal it was built to receive.

You are not anxious. You are running a threat detector that expects a body nearby and is not finding one.

EX · 03 / Parenting without a village
I have one kid and I'm exhausted and irritable all the time. Everyone tells me this is just what parenting is. Is it?
Mechanism
M9 Care / Alloparenting
Proxy
Nuclear-unit solo caregiving normalized as sufficient
Need
A village around your kid - multiple committed caregivers sharing the load as the default, not as emergency backup

Partially. But "this is just parenting" is doing a lot of work to normalize a structural mismatch.

Your care system (M9) was built for a village. Traditional-society data shows four or more non-parent caregivers actively involved in raising a child - not as backup, but as the default operating structure. The organism expects to hand the infant off, recover, re-enter, hand off again. Continuous solo or dual-parent caregiving is not the ancestral condition; it is an aberration the architecture was never calibrated for.

Exhaustion in that context is not weakness or a bad attitude. It is accurate reporting from a system running beyond its designed load. The irritability is downstream: when M9 is chronically overwhelmed, M1 Threat Management loses its suppressor. Your threat detector runs hotter because the co-regulator that damps it - trusted others physically present - is absent or undersized. Small provocations land harder than they should because the buffer is gone.

The people telling you "this is just parenting" are likely describing their own mismatch as the baseline. That is a different thing from it being correct.

The nearest move is not "find a village" - that is the matched endpoint, not a step. The step is one person who can reliably take the child for a predictable block of time each week, not as a favour but as a standing arrangement. Reliability is the operative variable: your nervous system needs to predict the recovery window, not hope one appears.

EX · 04 / Productive and worthless
I'm productive by every measure at work and I feel worthless. What?
Mechanism
M6 Controllability / Agency × M2 Pursuit / Exploration
Proxy
Productivity metrics, tickets closed, calendar fullness
Need
Work that leaves a mark - effort landing in the world in a form you can point to

Productivity and purpose are different readouts.

Your controllability/agency circuit (M6) tracks whether your actions produce tangible results you can see and point at. Your pursuit system (M2) fires when it closes loops - when effort lands visibly in the world. Both are typically offline in knowledge work: results are abstract, loops do not close, and your contribution disappears into a system where you cannot point at what you made.

"Productive by every measure" usually means the metrics say you closed things. Your organism says: "I saw no loops close." Different measurement systems. The metrics are reading a proxy; the worthlessness is the real signal - the mechanism is not getting what it was built for.

The nearest move is not quitting your job. It is finding one loop per day that closes visibly. A conversation where you can see the other person's understanding shift. A problem solved for a named individual. A thing that exists after you made it that did not exist before.

It is not that you are ungrateful or broken. It is that 300,000 years of evolution did not produce a system that registers tangible contribution by receiving a calendar invite.

The live version

These four exchanges are drafts of the voice. The live interactive version - a chat interface grounded in the Cor spec (v4 mechanisms, cascade rules, WYATT) - is now running at demismatch.com/decode-talk/.

It tells you what is happening, not what you want to hear.

Sibling surface

Decode:Talk takes a situation you type. Decode:Web - in build - will take what is already on your screen: a Chrome side panel that annotates live pages with the same read, grounded in the same spec.