I'm starting a publication. Here's what it is and why.
Field notes from an operator running three ventures on Claude Code. Biweekly. No theory. Receipts only.
I'm writing this from my desk in Stanley, North Carolina. Yesterday I was in Hickory walking the venue site for Mile High Golf. Tomorrow morning Curtis and I have a beta-venue call about the Quantum Caddy install at Crave. Sunday afternoon, somewhere between those two, I started TruPath Labs.
This is a publication for operators who run real businesses on Claude Code and want to know how someone else does it. That's the audience. If that's you, the rest of this matters. If it's not, it probably won't.
What I'm running
I run three ventures. Mile High Golf is a pre-launch entertainment venue in North Carolina. Quantum Caddy is an AR sports-tech startup, currently in Phase 0, building a smart cornhole board with a computer-vision pipeline. Parley is a research arm I started this year exploring AR glasses for bidirectional deaf and hearing conversation. All three run on Claude Code as the execution layer. Six agents. A skill stack I've been refining for six months. A vault that doubles as the project memory.
I didn't read about this setup. I built it because the alternative, running three companies in parallel without any kind of help to multiply my hours, wasn't going to work. I figured if I'm going to build it anyway, the work might as well be visible.
What this isn't
What this isn't. It isn't a Claude tutorial, there are good ones already. It isn't a "learn AI in 30 days" funnel. It isn't a hype channel for a tool I happen to use. The tool is the tool. The interesting thing is what you build with it when you're actually responsible for the outcome.
The cadence
The cadence is biweekly, Tuesday morning. Five archetypes rotate based on what actually happened the prior two weeks. Postmortems when something broke. Patterns when something worked twice and I figured out why. Teardowns when I tested a tool or workflow and have something specific to say about it. Field notes for short observations from the day. Playbook updates when I rewrite a section of how I work and want to show the diff.
That's the plan. The first postmortem is already up if you want a sense of the shape.