Interview, configure, ship.

1. Interview

You fill out a structured intake here: who is in the household, which tools you use, what you want fixed first, and what constraints matter (partner veto, money rules, time budget). That becomes an intake.md file.

2. Configure

You add the public Course Conductor template to your own Grok Bot workspace and hand it your intake.md. It reads the whole thing before asking a single question, so it never cold-starts and never asks what you already told it.

3. Ship

The Conductor runs the arcs C1 through C7 as interview playbooks. Every arc follows the same loop:

1. Orient. It restates your household and where you are.
2. Gap interview. Up to a dozen questions it does not already have answers to.
3. Plan back. It proposes agents, routines, and connectors in plain language. You approve or edit.
4. Guided build. Step by step, you create the agent and connect tools in Grok Bot.
5. Checkpoint. A definition-of-done list. You demonstrate the thing works.
6. Export. It writes a blueprint file and updates its memory. Then it suggests the next arc.

Where it ends

By C7 you have specialist agents that own their domains and a Home HQ pattern with clean handoffs. The Conductor becomes an optional coach. It is designed to make itself unnecessary, not to become a permanent chief of staff.

Do I need Grok Bot first?

Not to start. You can finish the intake and join early access without it. The unlock email will tell you to finish your Grok Bot signup, then open your link. The Conductor only runs inside Grok Bot. It will not pretend to run anywhere else.

Why there is no chat teacher on this site

Two brains is one too many. If the teacher lived here and your agents lived in Grok Bot, you would spend the course copying context between them. So the site stays thin: marketing, intake, unlock. The teaching happens where your agents do.