Sunday Afternoon, Year Five
What the protocol doesn't tell you about running it twice.
Howdy, folks.
It’s Sunday, 3:47 PM. Coffee gone cold two refills ago. Seven tabs open. A capture half-written about Schmachtenberger’s substrate consumption. A thread I started pulling this morning about how Jungian shadow projection maps onto the way engineers review each other’s code. A tarot spread I laid out an hour ago that I haven’t closed. A note that just says “the Hierophant is a middle manager” and nothing else yet. Time has been missing for the better part of the afternoon. This — right here — is the shape my life makes when it’s actually mine.
The phone buzzes. Substack notification. Someone subscribed. I know the name of the feeling that happens next, and I do it anyway: I open the dashboard. Open rates. Subscriber count. The two numbers I explicitly said I was not going to track, now tracked, now sorted by the little compulsive part of me that needs to know if the last piece landed.
Under that, already moving in, quiet and steady and faintly nauseating: Monday. The muggle job. Standup at 8:30. The thing I’ll have to perform tomorrow at the corporate beast to keep the paycheck intact. I haven’t thought about it for six hours and now it’s in the room.
Two cages just reached into my Sunday afternoon. Neither of them is the one Dan Koe was describing.
The forty minutes
Dan Koe wrote a piece recently — “Why your life feels fake.” Real piece. Real protocol. If you haven’t done a round, do this one. His core move is a seven-day belief-interrogation — excavation, inversion, verdict — built around one unreasonably good line:
“The version of you that shows up on Sunday afternoon is a preview of what your life feels like when it’s actually yours. Most people never get more than forty minutes of it.”
That’s true. I’ve lived the forty minutes. I’m living it right now, in fact, except right now there are two things trying to reach in and they both know the address.
The protocol works. I’m not here to tell you it doesn’t. I’m here to tell you what happens the second time you run it, because that’s the part Dan doesn’t write about.
The first inversion
I ran a version of this protocol — not Dan’s version exactly, life ran it on me — around four years ago.
The setup: I was on the best engineering team I had ever worked on, inside the world’s largest bank. Good work. Good humans. Genuinely good leaders who went out of their way to protect the people under them. I could keep my head down, ship excellent code, be quietly useful, and the structure would take care of me. I believed that. I worked from that belief for years.
The inherited sentence underneath was older than the job. Something like: be quietly excellent inside a protective structure and the structure will keep you safe. Southern Gen-X craftsman inheritance. You don’t toot your own horn. You do the work. The work speaks. Someone with authority sees the work and things happen. I never wrote that sentence down. I didn’t have to. It was the water.
2024, the structure vanished. Senior leadership vacuum turned into a game of thrones. My director lost. The org got sold off for parts. I had almost no visibility with anyone who could have made a different call, because I had been busy being quietly excellent, because that was supposed to be the thing that protected me. By mid-year I was out.
The sentence I wrote after — the one I did not want to share, in the exact shape Dan’s protocol says to write it — was this:
I can never depend on another human for my own safety. I have to chart my own course. I have to be known. I have to be noticed.
Feral Architecture is that sentence running live. This Substack. The covers that bleed edge-to-edge because there’s a TEMPLATE.md that says so. The voice you’re reading right now that is audibly not corporate-Matt. The inversion worked. It’s real. I’m proud of it.
And.
The cage you didn’t leave
Here is what the protocol doesn’t tell you about year five.
You don’t leave the cage. You build a second one. And you leave the first one running.
I didn’t quit the muggle job. I couldn’t. The paycheck is real. The stakes are real. The bank that didn’t protect me taught me better than to bet the whole house on a sentence, however true the sentence is. So now there are two cages.
The old one is the corporate beast. Remote, which means the desk across from my altar and there is no commute I can drive away from at the end of the day. The performance of competence inside a structure that is, as I have now personally confirmed, structurally incapable of caring about me. I know what it is. I show up anyway. It pays.
The new one is the visibility machine. The Substack. The cadence. The piece that ships Tuesday or the audience drifts. The open-rate dashboard I was not going to check. The cover that has to be generated and locked and scheduled and manually verified because Psyche issue #71 is still open. The being-known-and-noticed, scaled up, operationalized, running on its own timing.
Both are real. Both are, in their way, useful. Both reach into Sunday afternoon and eat the forty minutes.
The sentence changed. The cast didn’t.
Here is where Dan’s protocol stops and something else has to start.
The protocol interrogates a belief. It asks you to write the sentence you don’t want to share. It asks you to run a counter-script. What it doesn’t ask — and what I think it cannot ask, at its altitude — is who is running the new script.
Because the thing that made me good at quiet excellence was not the sentence. The sentence was the water the fish didn’t notice. The thing that made me good at quiet excellence was the part of me that cannot stop building. The Architect. The one who found a cathedral-shaped team and built cathedral things inside it for years. The one who optimized quietly and relentlessly inside every structure he ever got dropped into.
The same Architect is now building Feral Architecture. Same compulsion. Different target. The cadence. The covers. The schedule. The infrastructure. Last Tuesday I caught myself re-sequencing the May cadence for the fourth time that week. Sacral had said yes to a new piece that morning. Everything already on the plan had to shuffle around it. I would like to report that I was horrified. I was not horrified. I was in my element.
And the part of me on Sunday afternoon — following seven threads, abandoning three, crossing two over, arriving at an insight about the Hierophant and the middle-manager archetype that I have not yet told anyone about and maybe never will (no wait - I’m telling you?) — that’s the Magician. The curiosity-follower. The pattern-weaver. The one the Architect has been afraid to be, on and off, for most of my adult life, because every time the Magician got loose something got broken and the Architect had to clean it up.
Both cages were Architect work. The corporate one was the Architect making me safe by being quietly useful. The visibility one is the Architect making me safe by being loudly findable. The target moved. The engine didn’t. The Magician gets squeezed either way.
The sentence changed. The cast didn’t.
The second pass
I am not going to pretend I have this solved.
What I know is this: the scaffold I’m building for myself refuses a streak counter. It’s also trying, imperfectly, to refuse the thing a streak counter actually is: a cadence that generates shame when I miss it. A content calendar that runs on guilt is just a streak counter in a business suit. On days when the Magician wants to chase threads, the system gets out of the Magician’s way. On days when the Architect wants to build, the system tries to make the building sustainable and not compulsive. It does not always work. I am reporting live from the attempt, not from the summit.
Run Dan Koe’s protocol. It’s real. It works. The forty minutes on Sunday afternoon matter more than almost any other information you will ever have about yourself.
When you find yourself running the protocol the second time — when the new belief has calcified into a new script and six months in you notice the new script has the same shape as the old one — that’s when the work shifts.
You stop interrogating beliefs. You start interrogating archetypes. You ask who is running the new sentence. You ask which part of you the Sunday afternoon was a preview of, and which part keeps reaching into it with a phone in one hand and a Monday morning in the other. You ask what the whole cast wants, not just the one holding the microphone.
That’s the next altitude. Post-integration work for people who ran the first inversion and ended up optimizing a different cage. If that’s where you are, I’m building something for that.
Stay feral, folks.
The protocol is real. What happens when the ego doing the excavation is the same part that built both cages? Dan gets really close. "Find a new script instead of writing one" is right there, but the work of asking who's doing the choosing is a different tool entirely. Belief interrogation can't see its own blind spots from inside.
I don't think he can fully interrogate it because it would mean asking whether the whole thing (the audience, the protocol, the Substack, the identity as the guy who teaches you to escape scripts) is itself a script.
Dan's move: flip the belief, run the counter-script. Horizontal, same plane.
Depth move: vertical, what part of the psyche is running it, and does that part have its own agenda that will survive the inversion intact?
You're willing to report from inside the trap in real time. That's the part that's actually useful.