Man in the Middle

substratesovereigntyai-architecturesummarizationprovenancesecuritymemoir

Man in the Middle

By Robert Chuvala

I run two AI systems and I sit between them.

Both of them run on my own substrate. My accounts, my storage, memory built up on infrastructure I control — not rented, not parked on some company’s cloud where they keep the copy and decide what’s worth holding onto. Mine. That part matters, and I’ll come back to it.

One’s a PAI — a personal AI with a memory that actually sticks around. It’s held what I’ve fed it for eighteen months, in my own words, on my own hardware, and it keeps track of where everything came from. The other’s the harness. Claude Code. The raw terminal where the work happens and nothing gets remembered unless I make it. Same model runs in both. I’m the guy in the middle.

For twenty years, “man in the middle” meant one thing to me. It’s an attack. You get between two people, you read what goes by, and you change it before it lands. The whole reason it works is neither side can tell you touched it. That’s the definition, and I ran the offensive version of it for a living.

I’ve been chewing on that, because I’m the man in the middle now, and I finally get that there are two kinds.

The easy kind is a KVM switch. You know the box — one keyboard, one screen, you flip between two machines. To sit between two systems that way, you keep a squished-down version of each in your head and you toggle. You summarize the substrate to the harness, the harness to the substrate, both of them to yourself. It’s efficient. It’s also lossy, and I can finally see that, and I’m done doing it.

Because every time you summarize, you lose something. It’s just ones and zeros. Doesn’t matter how you feel about it. Every time you compress, anywhere, the old game of telephone kicks in and you drop something. And it’s never random what you drop. It’s whatever the thing doing the squishing didn’t think mattered. The exact word. The mess. The way it was said. Which is usually the part you wanted.

Here’s why nobody catches it. Nothing tells you it happened. A summary reads fine — smooth, sure of itself, looks complete. There’s no error message for the thing that got cut. You only find out the day you go looking for it and it’s not there, and by then you’ve long forgotten the summary that ate it. So you never even connect the two.

I know this firsthand, because I’m the thing that got summarized. My whole life I got squished down into a version somebody could hold in one hand — the difficult kid, the one who was too much, the problem to manage. Every one of those was a lossy copy of a whole person, and the damage was exactly that: the real stuff got stripped out. So when I say summarizing somebody does damage, I’m not being dramatic. I’ve been the file.

They’ve got a word for what I do now. Slop. AI slop. I got called that yesterday. And here’s the thing — slop’s real, but they’ve got it backwards. Slop is output with nobody home. Provenance gone, meaning gone, sounds fine and says nothing. What I do is the opposite. It’s more of me, not less. I don’t hide the AI. It works because I quit hiding from it. I fed it the true stuff — how I was raised, the defenses that turned out to be old reactions still firing — and it handed me back a map of where I’d been fighting history instead of the room in front of me. You don’t get that holding a machine at arm’s length. You get it by refusing to summarize yourself to it.

Let me tell you what refusing to summarize actually gets you, because I watched it today.

Eighteen months ago I typed a hunch: that I’d find my people through blogs, through the ones working it out in public. Then I spent a year and a half reaching out and mostly hearing nothing. You do that long enough and the tank gets low. Not the ideas — those keep coming. The gas underneath them. The part that lets you send the next one out into the quiet anyway. Mine was low. I’d started wondering how many more I had in me.

This morning a search engine I built — one that runs everything through a profile pulled from my own writing, not from what some ad company thinks I am — started finding them. Real people, working the same corners I work, turning up because of what I’d actually said I was instead of what an algorithm guessed I’d click. And this time it didn’t stay quiet.

I’m not putting any of them in here. Their side of it is theirs, and leaving it out is the whole point. You don’t get to keep your own signal clean and then strip somebody else for parts. But I’ll tell you what it feels like when the real version of you reaches somebody who also never got flattened. You recognize each other fast, because there’s nothing in the way. Nothing squished in the middle. Just two people, and it clicks.

Six months. A hundred and sixty-nine days I showed up. Seventeen thousand prompts. Over a thousand hours, sitting between two systems, refusing to be the lossy switch.

And here’s a little thing that gives it away: I type. Almost always now. Not because I can’t dictate — because dictation’s a summarizer too. Speech to text is a compression step at the one spot I’ve got total control over, my own hands, and I’m not putting a lossy layer there either. The keys are the cleanest input I’ve got. So I use them.

And here’s the part I told you I’d come back to. The reason I get to keep it this clean is that I own the whole thing. If this memory lived on somebody else’s servers — some company’s cloud — they’d be the man in the middle. They’d hold the copy. They’d decide what’s worth keeping and quietly drop the rest, and I’d never know it happened. So I put it on my own substrate instead. Now there’s only one guy in the middle. Me.

That’s the second kind of man in the middle. Not the one who changes the signal so nobody can tell. The one who passes it through and doesn’t touch it. Same seat, opposite job.

The attack works because the signal gets changed and nobody notices.

I’m the version where nothing gets changed. That’s the whole point.