Open Wavelength

JE0008
How You Receive the World
On bottom-up processing, emotion before narrative, and the timeline nobody talks about.
Journal Artifact // 05JUN26

1. Two Ways In

There are two basic ways a nervous system can process incoming experience. Top-down means your existing framework, your expectations, your stored models of how things work, filters what comes in before you feel it. The brain predicts first, then checks reality against the prediction. Bottom-up means the raw data arrives first. The body registers before the story forms. The emotion shows up before the explanation does.

Neither is better. They're different architectures with different trade-offs. But most of the psychological frameworks people rely on, most of the therapeutic models, most of the relationship advice, were built with top-down processors in mind. And that's a problem if you're not one.

2. I Don't Know Why I'm Crying Yet

Here's what bottom-up processing actually feels like from the inside: something happens, and the body responds. Tears, tension, a physical shift, an emotional state that arrives fully formed, without a label. And then, sometimes much later, the narrative catches up. The story of why forms after the feeling is already in the room.

"I don't know why I'm crying yet" is not avoidance. It's not manipulation. It's an honest statement about sequencing. The emotion is real. The explanation just hasn't finished loading.

For a partner who processes top-down, this is baffling. They have an explanation ready before the feeling fully arrives. So when they offer it to you mid-cry, they're being helpful by their own lights. But for a bottom-up processor, that offer short-circuits the process. Their story lands on top of yours before yours has a chance to form. Now you're not just processing the original thing, you're also managing their interpretation of it.

The road to the wrong destination is paved with good intentions and mismatched architecture.

3. Top-Down Processors Live in the Past a Little

There's something structurally interesting about top-down processing that took me a while to name. Because your brain is leading with its existing model, recent negative experiences update that model quickly. And the updated model then shapes what you expect next.

This means that after conflict, after something goes wrong, a top-down processor's default interpretive layer has been modified. They're not just remembering the bad thing. They're now filtering present-moment input through a lens that was last updated by the bad thing. They're structurally more likely to read neutral behavior as threatening, more likely to anticipate a repeat.

This isn't a character flaw. It's not pettiness or grudge-holding. It's architecture. The past is influencing the present through the interpretive layer, and that layer updates faster than conscious awareness does. Presence is genuinely harder after negative experiences for people who process this way. Not impossible, harder.

4. CBT and the Mismatch

Cognitive Behavioral Therapy is built on the idea that you can identify thoughts, examine them, and replace unhelpful ones with more accurate ones. For top-down processors, that's a reasonable fit. The thought precedes or accompanies the feeling, so working at the thought level has traction.

For bottom-up processors, the feeling arrives before the thought. There is no thought to catch and examine. By the time you're cognitively aware enough to apply a CBT technique, you've already been through the emotional event. The body registered it, processed it, and started moving on. Trying to intercept at the cognitive level is like arriving at the scene after it's over.

This doesn't mean CBT is useless for bottom-up processors. It means applying it at the wrong point in the sequence, which is what most practitioners do because most practitioners weren't trained for the distinction, produces friction instead of relief. And that friction gets interpreted as personal failure, which adds a second layer of damage onto the first.

5. The Filter Is Still Where Values Live

One thing that needs to be said clearly: bottom-up processing doesn't excuse unfiltered output. The emotion arriving first doesn't mean you're entitled to let it run without management.

What it does mean is that the management has to happen at a different point and in a different way. You can't intercept the feeling before it arrives. But you can build practices around what you do once it's there, how you communicate what's happening, how you buy time for the narrative to catch up, how you signal to people around you that you're in process rather than attacking or withdrawing.

The filter is still where values live. The architecture explains the challenge. It doesn't remove the responsibility to keep choosing.

"I don't know why I'm crying yet" is not avoidance.
It's an honest statement about sequencing.
The emotion is real. The explanation just hasn't finished loading.

Journal artifacts may overlap with theory, story, and syslog. Categories exist for navigation, not confinement.