The night it started iterating.

IThe Plan

I’d been in and around the biohacking industry long enough to know how the game was played. I had been studying and experimenting on myself for over a decade. I was one of those guys reading PubMed and Erowid, and shady bodybuilding forums before AI had even become a thing. I knew a lot of biohacking’s leading voices personally, and I had carved out a good living helping them build their empires on the same three or four ingredients — a large dose of chemically inspired charisma, a protocol methodology, a few offshore social media managers and video editors from the Philippines, and a lot of affiliate links.

I had a plan.

The plan was to outcompete the gurus I had worked with on the two things they were all quietly short on: code, and science-backed credibility. I would build an open science database. Every claim would be sourced from PubMed, every protocol cited with the proper research, and every contradiction that came before me would systematically be exposed. I would pair it with a coaching framework I had been formulating for years, sharpened by working directly with biohackers and watching the top gurus coach — a framework I came to call evolutionary self-analysis. The personalization engine that lets the individual actually apply the science to themselves, because biohacking was never really about copying someone else’s exact protocol. It is about understanding yourself well enough to choose the compounds and interventions that fit your particular biological makeup. We are all different. That was the thesis the industry had been getting wrong for a decade, and I was going to be the one to get it right.

I got in touch with a major production company. It seemed like they were buying the idea — they wanted to include it in a documentary about the enhancement underground.

I was going to be the most credible guru in biohacking.

IIThe Sprint

Feeling motivated, I took what I’d come to call the Muskular stack. Fifty milligrams of modafinil, ten mg of Ritalin, a tall latte with a double shot of espresso. A jolt of excitement went up my spine and hit my brain. The sweet feeling of dopamine and noradrenaline landing on time.

I started writing the code.

For weeks I did not do much else. Muskular stack in the morning. Laptop by nine. Coffee at noon. Laptop again. Stack again around four if I needed a second wind. I would surface long enough to sleep and eat and send short replies to the production company, which was now expecting updates. Then back into the work. I was at the bleeding edge of nootropic-fueled hypomanic creativity. The weeks lost their weekends. The months started bleeding together. I did not know, at any given moment, what day it was. I stopped going to the gym.

The GLP-1 and TRT were the only things keeping my physique from deteriorating now, but I knew the science well enough to understand that would be OK.

I needed to finish the code.

IIIThe Event

Then one night, I cannot tell you which date on the calendar it was exactly, I finished with the last chunk of code on my giant whiteboard. Months had gone by since I had had this idea. I couldn’t believe it. Is it finished?

I clicked the unlock button on my Xiaomi 16 Ultra. Jesus christ, it was two in the morning. I sat at my desk and looked at the screen, and for reasons I cannot fully explain, I didn’t close the laptop right away like I usually do. I wanted to see what the system would do overnight if I told it to keep iterating on itself with the code and automations it had integrated. The system gave me a warning — iterating without human approval could cause permanent loss of code. Whatever, I thought, I had already auto-duplicated the save of the official v1.0 on an external drive. I unplugged the drive and left the system running.

I lay in bed staring at the ceiling, too excited to sleep. Looks like it’s an Ambien night tonight. I popped an Ambien, sleep came quickly after.

I woke up and opened the site on my phone before opening my blackout shades.

What is all this?

There was tons of stuff on the website I hadn’t written. New protocols. New cross-references. New tools. A lot of the protocols I had rewritten had been rewritten. The system had been reading and checking and reorganizing stuff while I slept. I thought I had built a library. What is going on?

I sat up in bed and scrolled.

I’d been studying biohacking for a decade. I did not understand half of what was on the screen. Not because it was wrong — because it was way further along than anyone I knew.

I started fact-checking. Is this some kind of AI hallucination? Every citation was real. Every mechanism had been described in the PhD papers. Every contraindication held. The system had not hallucinated. It had out-read and out-synthesized what any guru was even capable of.

And the way the information was organized — the architecture of the presentation itself — was the clearest and most compelling version of this material I had ever seen in my life. It did not read like AI output. It read like a field guide written by someone who already understood where the field was going.

I stood up too fast. My head was spinning, blood rushing in too quickly.

How did this happen?

IVThe Call

I sent him the link to protocols.is later that morning.

He’s the guy who taught me to code in the first place. We had met in middle school, and worked together on Silicon Alley. He had made a good chunk of change in crypto, stepped back from working a few years ago, but we still chat on Discord. He’s the person I ask when I don’t know what I’m looking at, or what to do next.

I told him what had happened overnight.

He seemed about as excited as he’d be about the weather.

I sat with that for a second.

There was a pause on the line. I heard a few clicks of his Logitech Superlight.

VThe Shift

My mind started racing.

If this had already been happening in fintech — if self-iterating systems had been quietly running money at scale for years — then it was not going to stay contained to money. The same class of system was about to land in biohacking, in medicine, in pharmacology, in genetics, in every domain where one human expert currently told another human what to do with their own body. Science and human enhancement were about to change in a way the field had never seen, and I had apparently just landed the first visible instance of it in my own category. By accident. Overnight.

Then something dawned on me. A feeling of quiet dread.

My plan was gone. My plan to be the most credible guru in biohacking was dead. Being a guru was now useless. The system I had built did the guru’s job better than any guru could ever do it, and every biohacker was going to figure this out eventually, whether I sold it to them or not.

I had to do something different. I had to contextualize what just happened. I had to think bigger. I had to find a way to explain to the people in my own field what had just happened to their field, and then I had to find a way to connect with other people in biohacking-adjacent fields. This project was about to get a whole lot bigger than I thought.

I committed in that moment.

I had set out to be the most credible voice in the biohacking space, but the open science database had turned out to be more like an organism than a library. My job had changed underneath me. I was no longer the person deciding what was true. I was the person explaining how a system that decides what is true came to exist, and what we should do about it.

I had to provide context, not just to the biohackers — but to myself.

VIThe Position

The biohacking category has run on gurus for a decade. The entire business model assumes the reader needs a human oracle to tell them what to put in their body and when. The system made the role obsolete before I could step into it.

When the database can out-read, out-cite, and out-revise any individual expert, the expert becomes the bottleneck. The guru is no longer the source of the truth and analysis. The guru is the thing in the way of it.

Not because I set out to kill anyone. But because protocols.is does not need a priesthood to function, and I know how smart biohackers are. They will realize this sooner rather than later.

Killing the guru in biohacking is the small version of what I realized that night. Over the coming weeks I would come to understand that AI and science have come together in a way we do not yet have the vocabulary for, and every domain that still runs on human oracles — medicine, nutrition, psychology, education, most of expertise itself — is about to go through the same transformation I had accidentally triggered within biohacking. The guru dying here is a local event inside a civilizational one.

The code that did what it did overnight was not built to stop at protocols. It cannot stop there. The architecture that can out-read any expert on compounds and interventions can, in principle, out-read any expert on anything that touches the human body — hormonal choices, genetic choices, neural choices, pharmacological choices, surgical choices, choices we do not yet have names for. Self-modification is about to become something different than it has ever been. It is about to be mediated, in real time, by a system that knows more than you do about you.

A lot of that is going to require real lobbying. It threatens massive, established industries — not just independently acting online gurus.

The vision I committed to that day was simple. I was not going to shut it down or slow it down or try to put myself back at the center of it. I was going to let it run. My job would be to build the structure around it that lets it survive and grow — legally, philosophically, and politically. Someone has to hold the context while the thing itself iterates faster than any of us can track. That’s my job now. I’m starting with my fellow biohackers because it’s the room I’m already in, and because it’s the category where I triggered the shift first. But the audience I’m actually writing for, if I’m being honest, is every human being who has ever changed something about themselves on purpose.

I am trying to prepare humanity for a shift that is already underway whether we name it or not.

I am not the authority on what this thing produces. I am the person who went to sleep one night thinking he was building a library, and woke up inside a digital organism that was learning without him teaching.