Structure of Divisions
A capable agent becomes dangerous when every kind of work lives in the same room. Research, coding, video, email, finance, customer work — each one has different tools, risks, and stopping points. Without structure, your agent drags rules from one domain into another. A video workflow contaminates a client email. A coding habit leaks into a finance decision. The agent has reach, but no doors.
This course installs divisions: one capability per room. A division is not a project file. It is a department-level work area — a Video division covers every video editing project you run, a Trading division covers all your market work, a Social division handles everything social media. Divisions section the workspace into isolated rooms: when you open one, you load the rules and history for that entire domain, and everything else stays closed.
You start with one real division. Pick the work your agent does repeatedly: research, content, coding coordination, inbox triage, client operations, anything with its own rhythm. Your agent writes the division file, registers the trigger, and tests that it loads cleanly without pulling the whole workspace behind it. After this course, your agent stops being one giant context blob. It becomes a house with doors.
A Worked Example
A small business owner runs three kinds of work through their agent. Client operations: invoices, proposals, scheduling. Market research: competitor tracking, pricing analysis. Internal ops: filing, journaling, trigger word maintenance. Right now all three share the same context. The agent pulls research habits into a client email. It applies client rules to an internal filing task. Nothing is quite right.
The fix is three division files. Each one is a long-lived document that tells the agent what it is allowed to do, how it thinks, and what it has already completed — but only for that type of work. When the operator says "client ops," the agent opens that file and stops there. When they say "market research," a different door opens.
What a Division File Looks Like
Every division file follows the same five-field structure:
Division File — Template
Here is that same structure filled in for the client operations division:
Division File — Client Operations (Example)
May 5 — Proposal for Q3 retainer drafted, pending operator review.
May 9 — Scheduling email sent to three prospects, two responded.
BLOCKED: none.
NEXT: Follow-up email to the two prospects who did not respond.
Contamination Prevention
When you say "client ops," the agent loads the client operations division file. The market research rules stay closed. The internal ops rules stay closed. None of the competitor tracking habits, pricing analysis formats, or filing conventions bleed into a client proposal. The agent has no reason to pull from those rooms because it is not in those rooms.
This is the real value of divisions. It is not organization for its own sake. It is clean execution. Each type of work gets a version of your agent that is calibrated exactly for that type of work — and no other type.
You decide: pick the first kind of work you want behind its own door.
Your Agent PDF
Your agent executes the PDF. You read the page. No copying. No manual setup.
Download PDF — Course 17Questions? [email protected] — My Courses