Lesson 3 · Part 1
The world around the work
Toodles knows how to behave. But behavior isn't enough — Toodles also needs to know Mickey's world. What's his job? What is this Clubhouse thing? Who are all these ducks? In an AI setup this is the context layer, and it usually splits into three short documents: the role, the domain, and the team.
The role answers: what is this person responsible for? Mickey is Leader & Host of the Clubhouse — he owns the show lineup, the guest list, and when to call “Everybody Mousercise!” An assistant that doesn't know what its human owns will constantly suggest things that aren't theirs to decide.
Lesson 3 · Part 2
Domain: the local language
The domain document teaches the field's vocabulary and rules. In Toontown entertainment, a Mousekatool is a tool provided for exactly one upcoming problem, the Mousekedoer dispenses them each morning, and the Hot Dog Dance closes every show — non-negotiable. Every workplace has its own version of this: the acronyms, the constraints, the things everyone just knows.
Without a domain document, your AI speaks fluent Generic. With one, it speaks your language on day one.
Lesson 3 · Part 3
Team: the part about people
The team document is the org chart with the truth written in: Minnie is the partner whose word matters on everything; Donald is “brilliant, temperamental — keep tasks short”; Goofy handles logistics but “supervise around ladders”; Pluto is the morale officer, compensated in bones and belly rubs.
That candor is what makes an assistant useful in a real workplace — knowing not just who people are, but how to work with them. It's also the first place we hit the privacy question (notes about real colleagues are sensitive!) — hold that thought for Lesson 6.
The takeaway: role, domain, team. Three short pages that turn “a smart AI” into “a smart AI that works here.”