founding cohort: six seats at the founding price. cohort two opens at $5,000. join the room →
rono xiaRono Xia sealthe operators room
the curriculum

One year. Two passes.

an operating method for a business of one. you're the judgment; the machine executes and keeps the receipts. you decide what launches and what scales, on plain files you own. the house rule, start to finish: decide on receipts, not vibes.

the year has a shape. the first pass (modules 1–10): every part of your system built once, ending at going live. the second pass (the rest of the year): your live system run under supervision, trial by logged trial, until it holds without me. recorded lessons, video feedback on your actual work, and the private pod throughout.

one honest fact before the modules: this program was launched by the exact system it teaches. you're not buying theory. you're buying the replay.

operating cost, up front: running your own console costs by where you are. about $20/month while you're learning, roughly $100 once you're at real scale, up to $200 for a heavy-duty operation. mine runs about $100. stated here, restated in module 3, never buried.

time commitment: plan on 5–8 focused hours a week during the first pass; the second pass runs on the monthly cycle.

the first pass — build everything once

every module ends in something real you built, filed as a logged experiment. ten modules, experiments one through ten.

01 · the frame

the frame

operator · the room · the machine · the experiment · receipts · hostile terrain · the ground

you've been running experiments for months. you just didn't keep receipts. we name the chaos first, then demystify the tech: what actually changed in AI, what didn't, and why your judgment beats code you don't need. the honest lesson most programs refuse to teach: fear of visibility isn't a defect in you, it's an accurate read of a real environment — and the answer is procedures and a machine, not "feel differently." plus the ground: the daily practice, from your own tradition, that uptime actually runs on.

you leave with: your entry logbook page, with your last 90 days named as experiments (trial zero), plus your named daily ground and its two-minute bad-day version.

02 · the signal

the signal

signal · static · frequency

what only you can say and sell: point of view + skill + lived experience, made legible. a guided voice-interview pulls it out of you — you talk, the prompts do the work — and whatever you've published before gets sorted signal from static, without shame. then your first positioning hypothesis: who tunes in, for what, in one sentence.

you leave with: a one-page signal doc, a positioning hypothesis, and 60+ minutes of raw material that seeds everything after.

03 · the vault + the console

the vault + the console

vault · console · harness

build your vault: plain text, on your machine, owned by you — your module-2 material means it's never empty on day one. then the signature position: you learn the terminal, not another app, because the mechanism is the education. and the wow moment that changes people: the machine reads your own notes back to you with understanding, and then we explain exactly what just happened, so AI is never magic to you again.

you leave with: a live vault of 20+ real notes and your first unassisted console session, recorded.

04 · the judgment layer

the judgment layer

judgment layer · pre-flight · steadying

the core skill of the whole program: brief the machine, judge the output, revise the brief. you build your personal quality bar as a procedure the machine can be held to, produce your first three transmissions privately, and write the pre-flight checklist you'll run before every scary action. then the nervous-system lecture — where the science i trained in earns its keep: freezing and avoidance often run at the body level, not character flaws, why willpower-style advice tends to bounce off a dysregulated system, and what steadying practices the room teaches — with the boundary drawn out loud: deep trauma work belongs with licensed clinicians, and we say so.

you leave with: three finished transmissions, your written pre-flight, and feedback on your briefing and editing — the judgment, not the writing.

05 · first agent + first public transmission

first agent + first public transmission

roster · uptime · dead air · freeze at the mic

your first agent: the voice-note-to-draft pipeline that removes the blank page from your life permanently. then you go semi-public — a small venue you choose, pre-flight run live, with freeze-at-the-mic and over-tuning taught at the exact moment they actually happen. cadence gets set to what you can sustain, and the agent is configured to carry it on your bad weeks.

you leave with: a running transmission agent and two weeks of on-cadence publishing. uptime measured, not engagement.

06 · the offer + the price

the offer + the price

calibration · fear of the ask · drifted self-reading

your offer, constructed from your signal doc: outcome, mechanism, container, deliverables. then pricing as instrument reading, not confession — checked against outcome value and real comparables research, written down, defended in the pod. imposter syndrome gets taught here, where it bites, with its procedure: compare the internal gauge to your actual evidence, correct the instrument, and read the corrected number instead of the old panic.

you leave with: an offer doc, a calibrated price with written rationale, and a scripted ask.

07 · owned ground

owned ground

owned ground · rented airtime · the signal path

the rule: broadcast on rented airtime, land people on owned ground. you ship a real property — site, storefront, or landing page with email capture, scoped to your offer — with the console doing the heavy lifting, and enough web fundamentals that you're never hostage to your own site. including your sales page, built from the same anatomy you're reading right now: this page is the worked example, and its teardown is the lesson. then the whole path gets walked end to end, as a stranger would.

you leave with: live owned ground a stranger can traverse from discovery to purchase.

08 · the signal path

the signal path

path diagnosis · relay · the fan-pool vs the buyer-pool

diagnosis over volume: map your path, find the one dead connection, fix that joint before adding wattage anywhere. your relay goes live — one transmission, every venue, automatically. your module-2 positioning hypothesis meets six weeks of evidence, adjusted against what resonated with buyers, not fans. and the middle of the path gets worked: replies, conversations, real asks sent.

you leave with: a documented path map with numbers, a running relay, and your first real asks out the door.

09 · the roster + the auditor

the roster + the auditor

roster · auditor · logbook · running hot

the 2–4 agents your operation actually needs — not a fantasy org chart — each with instructions, a home in the vault, and a trigger. then the auditor: an external-consultant agent that periodically reviews your whole system and files a report. drift gets caught by procedure, not by crisis. and the burnout lesson, taught as engineering: if the operation requires heroics, the room is misdesigned — here's the audit question that catches it.

you leave with: your roster live and your first auditor report, reviewed together.

10 · going live

going live

going live · the two doors · the network · the loop

launch as a switch thrown after a checklist, not a leap of faith. the post-launch rhythm gets installed: weekly console session, logbook discipline, monthly audit, quarterly recalibration. the two doors explored honestly — run your own thing, build systems for others, or both — and for door two, identifying the tradeable skill your system now proves you have.

you leave with: a public, purchasable, running operation — path connected, uptime holding four consecutive weeks, auditor reporting. the same bar this program met at its own launch.

the second pass — the supervised year

launching is the first pass through the loop, not the finish line. the rest of your year is the loop run under supervision — where trial and error is designed in, not apologized for. every month, the same cycle:

the house rule, since module one: decide on receipts, not vibes.

the monthly cycle

  1. 1

    the auditor runs. your system files its own report: vault hygiene, path numbers, uptime, how stale your pricing is.

  2. 2

    pick the weakest reading. one target per cycle — a recalibration, a dead connection, a frequency adjustment, a new agent. one, not five.

  3. 3

    run the procedure, log the trial. hypothesis, change, result — dated, in the logbook. failed trials get filed as post-mortems, not hidden. a logbook with only wins is a broken instrument.

  4. 4

    review. I review the auditor's report and your trial log — the numbers and the decision quality, not raw anxiety.

once a month, one post-mortem gets reviewed in the pod. normalized error is operator culture: everyone learns from every trial.

you exit when: the module-10 bar holds without intervention and you're running the monthly cycle unprompted. stay-till-launched means the container flexes. the bar doesn't.

The founding cohort

you stay until your working system is built and running.

$2,500 · or 3 payments of $850

founding price, for the first six. cohort two opens at $5,000.

apply for a founding seat

six seats. the price doubles after.