You can build it yourself now. This kit makes you the person who can answer for it — and keeps checking that you still are.
An example software stack you install and configure as your own AI-native shop: lessons, exercises, working agents, telemetry, and dashboards. As you move through it you build your own dev shop — the coding agents, skills, and house rules to remain a viable, AI-first builder — with an instrument inside that reads how you are actually working and tells you the truth about it.
The shop arrives. You install it on day one and it starts recording how you actually work.
The settlement tunes it to who you are, what you run, and what you're building toward.
The function runs the development lifecycle: agents through the middle, you above the loop.
The function reports to the long clock: your own dashboard, read in years.
Read the four moments as one act: standing up your build function. The shop arrives; the settlement tunes it to who you are and what you're building toward; the function runs the development lifecycle with agents through the middle and you above the loop; and it reports to the long game.
I can build it myself now, better. Builders say it in almost the same words every time, and they are right about the first half. That is the change, and it moved the hard part onto you: what should exist, whether you read what shipped, whether the speed is making you sharper or duller. AI makes building easier. It does not make you viable. The judgement this kit develops comes in two registers: the founder judgement that decides what deserves to be built, and the engineering judgement that decides whether it will hold up.
Every price includes the same kit. No door is a lesser kit. Choose by who holds the licence and how many builders it covers.
Same kit at every door — curriculum, agents, telemetry, dashboards, portable shop
Every price is one-time and includes every revision for the lifetime of kit version 1. A major version, if there ever is one, is a separate purchase through the same door you came in by — students re-verify. A company's seats can be reassigned; a personal licence cannot. Prices are in US dollars, stated September 2026.
Leave an email for the pre-order announcement and the Edition 1 release. No drip campaign: I'll email once when Edition 1 is ready, and once when pre-orders open.
No charge today.
The kit runs on your machine. Your telemetry stays there — nothing ships back to me. No subscription, no remote kill, no lock-out. The defaults are honest, and turning honesty off is itself a logged event you answer for. And what you configure, you carry: the kit compiles your agents, your skills, and your house rules into a portable shop for the repos you work in outside it — generated from your own settlement, not bought off a shelf.
A machine you control, a coding harness subscription, and a willingness to use a terminal. If that is new, the install document guides the first commands. Requirements and estimates as of September 2026.
Plan on about forty hours across two to three months, working through real builds. Budget extra time for setup if the terminal is new to you.
Your harness subscription plus model calls on your own provider key, with a spending cap you set. These costs are separate from the kit purchase.
Your telemetry stays on your machine. The kit masks its own model calls and checks commits for secrets and records. Your coding harness account and what you show its models remain your responsibility.
Each unit pairs a position with a practice, working agents, and exercises that produce real artifacts — a PRD, a pull request, a roadmap. As you build, the app reads how you work. You learn to ship and learn about yourself at the same time. Open a unit's lesson list for the working outline; lessons and ordering remain subject to revision.
You install the kit on day one — before you feel ready — and it starts recording: every prompt, every accept, every reframe. Seven lessons on who does what: two kinds of intelligence at the table, and the two jobs that never transfer to the machine.
The AI does the work; you carry the risk. Why this is the best time there's ever been to build — and why missteps cost more now that building got fast and cheap.
What the machine is for, and what you're for. It decides how; you decide why — and only you can care whether the thing is actually right, not just whether it works.
Origination at the front, answerability at the back. You start the work and you answer for it; the agents take everything in between. The first question of the kit: did I choose this, or did it choose me?
Your condition is the binding constraint now. How to check yourself when you can't trust the mirror, and how to wire an alarm that fires on the days you'd rather ignore it.
The kit starts reading how you actually work — because the honest instrument is the one you could never keep on yourself.
The maintenance the new speed doesn't excuse you from — keeping the shop, the agents, and yourself in working order.
The first working session with the installed kit, and the habits that make everything after this unit land.
Unit 1 installed my operating beliefs as the lens. Unit 2 surfaces yours — which beliefs you chose, and which the vendors installed for you. The configured kit is the settlement: mapped to your situation, your stack, and the ambition that brought you here — and compiled into a shop you carry into every repo you own.
Growing a team, renting what you could own, depending on an outside shop, inheriting a mess you're scared to touch, shipping what you can't explain, or pushing a demo to a real product. Each drops a different job and makes a different trade.
The environment you already run — your stack, your tenure — surfaced as evidence about who you actually are, not how you'd grade yourself. And one permission worth granting: let the kit read what your own site already claims you're building toward.
A short, honest read that confirms your situation against what you've actually built, shipped, and inherited. A route, not a label.
The tool market, de-programmed: stable functional categories instead of vendor names — and which of your tool beliefs you chose, versus which were installed for you.
For every skill in front of you, one call: own it for real because you'll live with it, or borrow just enough to direct it and stay in charge. The trap on each side, and the good news.
The universals every configuration stands on, whatever your situation — the conditions no configuration gets to skip.
Every escape is a trade — no move sheds risk, it relocates it. Borrow across situations on purpose, and choose the dependency worth holding instead of waking up inside one.
The configured kit is the settlement — your beliefs, tested against your behavior and the installed doctrine; your aim, written in your words with your own public evidence laid beside it. The settlement compiles into a shop you take with you. And what to do Monday morning.
The configured kit, run against real work. The Agent Development Life Cycle — the software lifecycle you may never have been taught the name of, re-staffed by a crew of agents, with you on the two gates that never transfer.
The path every app on your phone was built on, and why each step existed. The path stays — the team in the middle becomes a crew of agents, producing everything a full human team once did.
One place the work lives. A set of specialized agents, each with one narrow job. The house rules that make them build it your way. The adapter that lets them see everything the company already knows. And the same shop, compiled to travel — it goes with you into repos the kit never sees.
Follow a single piece of work across the board, left to right. The agent fills the column; you own the gate between the columns. That rhythm is the whole job.
Where you start, and where you answer — and the in-flight move (steering) that keeps both gates real when the middle runs at machine pace. Because agents absorb the time the middle used to cost, real tests, granular security, and solid infrastructure become the floor — not a late-stage luxury. And the one place that claim breaks.
The agent will reach for the frontier model on every task unless you configured otherwise — and your token bill, your rate-limit exposure, and your provider dependency will climb without you ever signing for them. The classify-and-route discipline that meets that default, with open-source and self-hosted models as a first-class option.
The same rulebook can make you sharper or hollow you out. Set your agents to explain where the skill is yours to own; set them to just produce where you'll only ever direct. The knife-edge under every teaching agent — and the same setting that decides whether you can see into the middle while the work is running.
Because the whole build runs through one place, it quietly records how you worked — what you reframed, what you actually read before approving, what you chose versus rubber-stamped. The honest instrument you could never keep on yourself.
Which gate to stand on first, and how the rest of the kit backs you up while the rhythm becomes yours.
Becoming viable is this build. Remaining viable is every build after. Everything the kit has recorded since Unit 1 becomes a dashboard you read in years — and it arrives seeded with my own readings, part of what the price buys, until your own data takes over.
Every reading on the short clock flatters you — a shipped feature, a happy client. The second clock ticks in years, and it's the one almost nobody is watching.
Trends, not snapshots — read against your own baseline. The most honest readings come straight from your work: your transcripts — and, once connected, your invoices and your last ten bios — not your gut on a given afternoon. Every asked question arms with granular consent.
Three families — the builder, the craft, the ground. Nine things actually under threat over a career, each one planted earlier in the kit and coming due here. A working translation of the framework from Remaining Viable.
What to actually do when a dimension reads unfavorable — strategies, not affirmations, for each of the nine.
The quarterly reading protocol: how to sit down with your own instrument, read trends against your own baseline, and resist the urge to grade yourself kindly.
A bad reading isn't a verdict; it's the next thing worth originating. The loop back to the first gate.
The cohort opt-in: extend the same readings across builders running the same kit, with granular consent. Never required — the kit works identically if you decline.
Remaining viable feeds straight back into becoming viable — and the whole loop starts over, one build smarter than last time.
Lessons and ordering will shift as drafting continues. The intent — comprehensive, prescriptive, honest — will not. It is grounded in industry best practices as they evolve, in my own day-to-day building as technical co-founder of Soaring Titan and Maximum Automotive Intelligence, and in the research stream on the inquiry side.
One purchase includes every revision for the lifetime of kit version 1. A major version, if there is one, is a separate purchase. No subscription, no upsell.
Each edition incorporates what's been learned since the last — dated, versioned, and visible, with a changelog you can read. The configuration you build in Unit 2 survives minor revisions; breaking changes carry a migration the kit performs, not you — and the portable shop it compiles simply recompiles from your settlement, never hand-patched.
Buying once includes every quarterly edition, every vendor-evaluation refresh, every agent and lesson update that ships under the 1.x line. The intent is a living body of work you can return to as conditions shift while you are using it.
If you wanted to be an aerospace engineer, I'd tell you to buy an airplane kit and build it in your garage. The Playbook is that — the pieces and parts laid out before you, optional build configurations to make it yours, and the hands-on teaching to make it stick.
The Playbook is the self-directed artifact. Resources shows the doctrine applied to real, publicly-sourced problems. Mentorship applies the same kit to your problem, in the room, with me sitting next to the person doing the work. Each one is complete on its own. They reinforce each other for the leaders who want all three.
The doctrine was earned on what was, for several years, a fairly lonely hill. The kit puts that work in reach of people who aren't ready for — or don't need — a four-thousand-a-month engagement, and the student price puts it in reach of people just starting out, which is the point of handing a career on.
Students, recent grads, and people my own kids' ages who want to talk it through should reach out directly — that conversation is free, and I keep room for it. More on that on the About page.
Same kit, two paths. The difference is access to me, not access to the doctrine. Students and early-career builders: the conversation is free.
New Resources, Research, Data readings, and kit editions. This list is the only announcement I send.