I'm Lane Belone, a writer on the Infinite Game, a former Green Beret and co-author of Unleash Your Humble Alpha. I've been working with AI as a sovereign craft for a few years now, long enough to watch what it does to the operators who use it well and the operators who use it without a practice.
The pattern that surfaced is consistent: most owners get good at the tool fast, then plateau because the underneath layers never got attention. Voice flattens. Stack inflates. Workflows get automated before they were stable enough to encode.
Three layers underneath the tool. The framework you bring to it. The stack you point it through. The timing on when to encode the workflow into something automated. Each one its own Field Guide. Each one its own seven-Move practice.
The collection is for the operator who wants the whole architecture. The framework, the stack and the timing as one installed practice.
Held by structure. Three Field Guides. One practice.
Three Field Guides. Each one a different layer of the practice.
B1. AI for the Business You Actually Want · the framework
Whose voice. Whose terms. Whose business. The manifesto practice. Voice as the moat. Pace-layer architecture. The Three Solutions Rule applied to AI decisions. The framework that lives before the tool.
See the Field GuideB2. Stack Calm · the stack
Your minimum viable AI setup. The aliveness filter applied to tools. The three-category architecture (thinking partner, research layer, workflow layer). The cancel list as audit ritual. The new-tool test that runs in 90 seconds before any subscription joins.
See the Field GuideB3. Earn the Right to Automate · the timing
The discipline before the automation. Twenty manual reps. Four validation conditions. The five-question decision tree. The first-build practices. Workflows that iterate. Automations that last.
See the Field GuideThe felt difference as you bring the three to the work.
You're paid to be yourself. Your stack is calm because each tool earned its place. Your automations compound instead of breaking. The architecture holds you through every season of the work. Installing this is a vote for the operator you're already becoming.
Two practices from Earn the Right to Automate
From Chapter 6, The First Build. Two of its five practices for the first thing you automate.
Practice one. Start small. Automate one step, not the whole workflow.
The temptation on the first automation is to encode the entire workflow at once. End to end. Hands-off. Resist it.
Pick the single step that's most mechanical, most stable and most repetitive. Automate that one step. Leave the rest manual. Run the workflow with the one automated step for two weeks. See how it behaves. See where it fails. See what the interface between automated and manual looks like.
If the one step holds up, automate the next one. Then the next. Build the automation in layers. Each layer gets validated on its own before the next one is added.
Building end-to-end on the first try means debugging a system with five new failure modes at once. Building one step at a time means debugging one new failure mode. The second approach's faster, calmer and more durable.
Practice two. Keep the manual rep as the fallback for thirty days.
For the first thirty days the automation is alive, you should still be able to do the workflow by hand on demand. Don't throw away the manual instructions. Don't retire the rep entirely. Keep the muscle memory warm for a month.
This is the safety net. When the automation breaks (and it will break, because that's what new automations do in their first thirty days), you can finish the work manually while you fix the automation. Customers don't see the disruption. Operations doesn't freeze. You debug calmly because the manual fallback's right there.
After thirty days of clean automated runs, the fallback can fade. Before thirty days, it's your insurance.
Quoted word for word from the markdown edition that ships with the purchase. The rest continues in the Field Guide.

Six files. Three PDFs. Three AI-Ready Markdowns with Companion Guide.
The whole collection as designed reading experiences and as AI-native working tools. Drop the markdowns into Claude or ChatGPT individually or together. Start where the work in front of you is alive and reach for whichever Field Guide meets it. They mesh into one practice as you use them.
AI for the Business You Actually Want · PDF + AI-Ready Markdown
Stack Calm · PDF + AI-Ready Markdown
Earn the Right to Automate · PDF + AI-Ready Markdown
Each markdown ships with the Companion Guide section at the top. Voice-brief block, Moves index, the protocols specific to that Field Guide's practice. The Field Guide content below gives your AI the installed operating context for every conversation.
$14
$27
Save $13
All three Field Guides as one collection. Six files. One integrated practice. One quarterly rhythm. Brought together for the price of one and a half.
The framework. The stack. The timing. The complete AI practice as one installed system.
The Move is the point. The reading is the on-ramp. If this is your kind of thing, you'll know.
Common Questions
Individual Field Guides
AI for the Business You Actually Want · the framework.
Stack Calm · the stack.
Earn the Right to Automate · the timing.


