The Sword Goes Back in the Sheath

The Other Half of It

Last time I wrote about pushing forward when you're tired — the late gym session I'd already talked myself out of, and the hug from my son that ended the argument.

That article is half of a rule, and publishing half a rule is how people get hurt.

Because the other half is knowing when to stop. Not when to quit — when to *stop, deliberately, on your own terms, at a moment you chose.* Those are completely different acts, and only one of them makes you stronger.

This weekend is the second one, and I'm writing this from the middle of it.

納刀 — Sheathing the Sword

There's a detail about swordsmanship that took me a long time to appreciate.

In iaidō, nōtō — returning the blade to the scabbard — is a formal technique. It's practised with the same seriousness as the draw. Slow, controlled, eyes still up, the spine of the blade riding the mouth of the saya. You do not shove it back in. Beginners cut their own hands doing exactly that, because they've decided the fight is the interesting part and the ending is admin.

The scabbard isn't the opposite of the sword. It's part of the weapon. A blade that is never sheathed doesn't stay sharp from all that use — it rusts, it chips, it dulls against everything it touches. Steel is maintained in the dark, oiled, still, doing nothing visible.

So: rest is not the absence of discipline. Rest is a technique, with its own form, and it can be done badly. Collapsing on a sofa because you ran out of road is not the same movement as putting the sword away because the work is finished.

Why This Weekend

Three things closed at once, which almost never happens.

The protocol block finished. Ninety-four days, and the blood is drawn — the preliminary numbers came back and they were excellent. Triglycerides down 41%, VLDL down 43%, SHBG up 54%, liver spotless. That block is closed; the next one doesn't start until the full panel lands.

The product went live. More on that below.

And the kids are crushing it. Remote homeschooling handled, activities handled, sustentaciones defended, the whole machine running. That is not a small thing and it isn't luck.

Three milestones landing in the same week is a signal. If you can't stop after finishing something, you were never going to stop — you'd just have found the next reason.

Eje Cafetero

A friend from Brazil was visiting Colombia, so I joined her in the Eje Cafetero — the coffee axis, the belt of impossibly steep green mountains a few hours out of Medellín where the cloud forest sits in the valleys like something poured in.

The place is extraordinary. Mist coming up the ridges at dawn. A pool lit at night with the jungle right at the edge of it. Food cooked properly and eaten slowly. Massage. Silence with actual texture to it.

And I've disconnected completely. No drills. No protocol optimisation. No 22:15 bedtime target. No counting anything. I haven't taken a single measurement I'd normally take and I haven't once thought about my heart rate variability, which for me is close to a spiritual achievement.

Recharging properly is itself a protocol — and the version where you take the laptop and "just check a couple of things" is the version that doesn't work. Half-sheathing the blade is how you cut your hand.

Meanwhile, in Medellín and the USA

Here's the part I actually want to write about, and it's the reason this is a biohacking post and not a holiday snap.

1. The Clinic Answered — and Answered Properly

In the last article I said the follow-up panel had come back narrower than my baseline — missing IGF-1, HbA1c, insulin, hs-CRP, prolactin, thyroid, vitamin D — all of them on my own prescription's list of what to monitor during treatment. I asked eight specific questions and sent them to my clinic.

I'll be honest about the part I didn't publish: privately I was wondering whether I was getting the attention a serious, dedicated client should get. I never said that to them. It was an internal thought, and I was prepared to let the numbers speak.

Then, while I was up here with my phone mostly face-down, this landed.

Adriana Martinez, a partner at TRT Colombia, reached out to me personally. She'd spent an afternoon going through the whole file — my results, my notes, every one of the eight questions. And rather than sending a defensive reply or a fast one, she did four things that I think are worth naming publicly:

• She took ownership without being asked twice. Her read was that consistency in my follow-up had been lost, that biomarkers used to track my baseline weren’t included this time, and — the part that actually mattered — that nobody had explained the difference to me before the blood was drawn. She called it their responsibility, not mine.
• The clinic is covering the cost of the missing tests. So the comparison against my original baseline gets completed properly, at their expense, without me having to argue for it.
• She asked the team to transfer my case to her personally — because, in her words, she enjoys working with patients who want to understand every biomarker and every adjustment in detail. From here, she oversees the follow-up.
• She agreed with the substance, point by point. On comparing the same panels over time, on creatinine and muscle mass, on cystatin C, on HCG, on estradiol. And she declined to give partial answers to the eight questions — she and Dr. Hugo will review the case together once the missing biomarkers are in, so the recommendations come from complete information rather than assumptions.

That last decision is the one that told me the most. Refusing to answer quickly is harder than answering quickly, and it's what you do when you'd rather be right than look responsive.

So: genuine thanks to Adriana and to the team. This is what it looks like when a clinic treats a case as a case rather than a transaction, and I'm glad to be working with people who take it that seriously. New numbers, new eyes on the file, and a protocol rebuild coming off complete data.

There's a broader lesson buried in there, and it's the real biohacking point of this whole section:

2. The Product Is Live

In the United States, the thing I've been building with a very small team across three countries went live.

We're still in stealth, so that's genuinely all I can say. No name, no details, no screenshots worth squinting at. If you've read the article where six people in three countries all signed a HIPAA Business Associate Agreement in the same week, you already know roughly what neighbourhood we're in.

It's live. It's real. Ask me in a few months.

3. And the Crew Kept Training

And in Medellín right now, with me four hours away doing absolutely nothing, the paisa crew is just carrying on. Training. Cooking. High-quality protein — chicken, weighed, boring, correct.

Including the homemade electrolyte drink the crew swears by, which I'll write out because it's better formulated than most things sold in a bottle:

Sodium plus a glucose–fructose mix plus acid is, unglamorously, the same mechanism behind oral rehydration solution — the one that has saved more lives than most drugs. Theirs just tastes like fruit instead of medicine, and nobody had to buy a subscription.

The System Runs Without You

Here's what is happening while I'm not there.

The protocol block finished on schedule without me supervising it. The clinic escalated and fixed itself while I was offline. The product went live in another hemisphere. The kids did their homeschooling. The crew is training and eating properly today, right now, without a single message from me. Nobody has needed a decision from me all weekend.

That is the actual test, and it is the only one that matters. Anyone can build a thing that works while they're standing over it. The question is whether what you've built is a *system* or just a very tired person doing everything manually and calling it leadership.

If it collapses the moment you step out, you don't have a company, a protocol or a household — you have a bottleneck with your name on it. And a bottleneck is not something you can rest inside of, which is precisely why the people who can't delegate also can't recover, and why they burn out on schedule.

So this weekend isn't time off from the system. It's the system's stress test — and it's passing.

Monday

One more day up here. Blade oiled, put away properly, drawn again on Monday.

The full panel lands this week. Adriana and Dr. Hugo review the complete picture. Then we build the next block — more advanced than the last, off a dataset instead of assumptions, with TB-500 coming back off pause.

Push when you're tired. Stop when the work is done. Both of those are discipline; only doing one of them is a countdown.

Gratitude to everyone who made this weekend possible — and to the people keeping everything running while I sit in the clouds.