You just joined the OS+AI Guide — individualized mentorship inside a small-group container. soloOS + human-centric AI workflows, built for resilience.

This isn't a course or a content calendar. It's a working personal AI operating system — your soloOS — that you build yourself, with direct practitioner guidance and a small room of people doing the same work. No preset curriculum. The build guides are the vehicle; your trajectory is set by where you actually are.

Here's what you bought, and what happens next.

What your membership includes

• Monthly 90-minute group build workshop — live, recorded for reference. Standalone deep dives that rotate based on where members are in their builds.
• 60-minute 1:1 at onboarding — your starting point. We map where you are and where you're going.
• 60-minute 1:1 at each 60-day mark — recalibration as your system and your practice evolve.
• Personalized trajectory documents — produced from your onboarding assessment and each 60-day recalibration, generated through my CommsOS project. This is your individual roadmap, not a generic track.
• Weekly async office hours — bring build problems to the channel before they compound.
• Inner Circle access — monthly live AMA calls and recordings.

Rolling enrollment, 10–12 member cap, 3-month commitment recommended.

What happens now

1. Watch for your workspace access email (within 24 hours). You'll get access to the async workspace and the soloOS Build Guide. Start reading the guide — you'll reference it throughout your build.

2. Book your onboarding 1:1. This is your starting point, and it's the most important thing on this page. The onboarding call produces your first personalized trajectory document: an assessment of where your practice is now, what your soloOS needs to do for you, and the path to get there. Nothing about this membership is one-size-fits-all, and the onboarding call is where that gets calibrated. Book your call with my GCal link.

3. Show up to the monthly workshop and weekly office hours. Workshops are standalone — there's no Month 1 through Month 6. You show up, you work, you leave with something usable. Between workshops, office hours are where voice extraction that isn't landing, proof points that feel thin, or system instructions producing off-voice output get solved before they compound.

Before your onboarding 1:1

Gather 3–5 pieces of writing that sound like you at your best — blog posts, newsletters, LinkedIn posts, emails, anything where the voice is unmistakably yours and lightly edited.

This is the source material for voice extraction, the foundation of your soloOS. The system can only learn how you actually write from text you actually wrote. Don't send polished marketing copy or anything ghostwritten — send the writing that sounds like you on a good day.

Bring these to your onboarding call, or drop them in the workspace ahead of time.

What you're building

A soloOS is your personal communications infrastructure — the individual-scale version of the CommsOS methodology, the same architecture used in organizational builds, adapted to your practice.

It draws on the CommsOS 8-component framework, but your build is just that– yours. Some practitioners use the whole architecture. Others lean on a few pieces and let the rest stay light.

The methodology is your starting point, not a checklist to complete — what you build depends on your practice, your voice, and what you actually need the system to do.

Most soloOS builds draw from the same set of building blocks:

• A voice extraction that captures how you actually write — not how you wish you wrote
• A brand, org or mission voice definition with operational rules AI can follow
• Audience mapping that tells the system who you're talking to and what they need to hear
• Proof points calibrated with honest confidence levels
• Forbidden patterns that prevent the output errors that erode trust
• System instructions that load the whole thing in the right order

Use what serves your practice. Leave space for what emerges as you build. It all lives inside your own Obsidian vault — your soloOS infrastructure, owned by you and portable across any tool.

Where this can lead

Some members complete their soloOS and have exactly what they need. Others realize their organization needs the full build. Both are good outcomes.

Members who complete the build have a discounted path to a deeper 1:1 review. And members whose needs grow beyond solo scale have a natural upgrade path to a full CommsOS implementation.

Either way, you leave with infrastructure that works whether you stay or go.

Read the full methodology at CommsOS.org — background context for what you're building.