the words, before the money.
we speak a specific language in the room, and none of it is gated. understanding is free. the how-to behind each word is what the membership and the cohort hold.
who you become
-
the operator
the human whose judgment directs the machine. not an engineer, not a passenger. the transformation this program sells: from someone technology happens to, into someone who operates it.
-
the judgment layer
what the operator becomes. the machine drafts, retrieves, executes; the operator decides. this is the skill the room actually teaches.
-
the room
the environment the operator works inside: the vault, the console, the procedures, the community. our thesis in one line: we re-engineer the environment around the operator; we don't operate on the operator.
-
the machine
everything that executes: the agents, the harness, the vault they read from. capable, tireless, judgment-free. it executes and keeps the receipts; you judge what launches and what scales.
the infrastructure
-
the vault
one organized library that holds everything you know — notes, decisions, voice, procedures. what some people call a second brain. plain text, on your machine, owned by you. nothing we build lives inside someone else's app.
-
the console
where the operator works: a terminal running an AI harness, pointed at the vault. deliberately a terminal, not an app — that's a teaching position, and module 3 makes the case.
-
the harness
what an AI coding agent actually is: the structure that lets a model read files, use tools, and act. once you understand the harness, no new AI product will ever intimidate you again.
-
the roster
your set of named agents, each with one job — marketing, ops, product. built one at a time. a roster, not a swarm.
-
the auditor
an external-consultant agent run periodically against your whole system: it reviews the vault, the numbers, the path, and reports what's drifting. the system inspects itself.
-
the loop
the end-state: you iterate, the system records, the system now knows your business, the next iteration is smarter. the loop is the real deliverable. launch is just the first pass through it.
the business layer
-
the signal
what only you can say and sell: point of view + skill + lived experience, made legible. everything downstream amplifies the signal; nothing can fix a missing one.
-
static
output that isn't signal: trend-chasing, copied formats, algorithm-bait. not morally bad — just noise the machine can generate without you, which is exactly why it's worthless.
-
the signal path
stranger → tuned in → conversation → buyer. a line with connection points. paths fail at one dead connection, not from weak signal everywhere — so diagnosis is always "find the cut," never "do more everything."
-
dead air
silence on the path: no posts, unanswered messages, a price question with no answer page. the practical sin the whole system exists to prevent.
-
uptime
the percentage of time the operation is actually running — publishing, replying, delivering. the metric that replaces "consistency" and "discipline." uptime is engineered, not willed.
-
owned ground
digital territory you control: your site, your store, your email list. the rule: broadcast on rented airtime, land people on owned ground.
-
calibration
setting your price by checking the reading against reality — outcome value, comparables — instead of against feelings. a maintenance task, not a character referendum.
-
the network
the slow burn marketplace — where trained operators will list the skill they've built and get connected to paid work. a vision being built, never sold as live.
-
slowburn network
the network, by its name: the two-sided room where operators trained here meet real client demand: list the system you built, get connected to paid work; or arrive as demand and find an operator to hand a piece to. being built now, not live yet. founding cohort members get first-access when it opens; members hear when it launches. lives at slowburn.network.
-
experiment
a thing you try on purpose to learn one thing: a price, a hook, a subject line, an offer. it has a start, a cost, and a result you can point to. you've been running these all along. the method just names them and keeps the count.
-
trial
a single run of an experiment. one send, one test, one ask. a trial isn't a verdict, it's a data point. you judge after enough of them, not after one.
-
receipts
the log the machine keeps of every trial: what you tested, what it cost, what came back. decisions get made from this page, not from vibes.
human factors
-
human factors
the mindset layer, reframed: high-stakes professions assume the human will predictably err under fear, pressure, and fatigue — and engineer procedures around it. we do the same. feelings are engineering constraints, not character flaws.
-
operator error
a named, known failure pattern with a known procedure: freeze at the mic, over-tuning, drifted self-reading, fear of the ask, running hot. each one has a card. none of them is a character flaw.
-
the pre-flight
the short checklist run before any scary action — first post, first ask, price raise. externalizes readiness so courage isn't required daily.
-
the ground
your daily practice — prayer, meditation, breathwork, movement — chosen from your own tradition. named for the electrical ground: every powered system runs a wire to earth, or charge builds until something arcs. the room requires that a ground exist; it never prescribes which one.
