Meet your organization
Where does my organization live, who does what, and where do I decide?
This is that walk-around. You'll find the organization in your workbench, meet the agents you'll use first, and take a starting picture before changing anything.
The course gives you a starting organization to inspect and adapt. You learn by giving it work, seeing what happens, and making changes you understand.
The files describe the organization. The work shows what it did.
You can find the workbench, distinguish it from the LMS and remote copy, and explain Chief, The Professor, the Writer, and the Reviewer.
A profile being present, an agent being available to call, and an agent having completed a job are three different things.
You direct in the app, work happens in the selected workbench, and saved records can be inspected in the dashboard.
Set the direction, approve what may be used, and decide what happens to the work.
The first day in an unfamiliar organization is easier when someone shows you around. Which work belongs where? Where do you ask for help? What comes back to you for a decision?
This is that walk-around. You'll find the organization in your workbench, meet the agents you'll use first, and take a starting picture before changing anything.
Start here
Before you start: Complete the required Essentials setup and open your existing workbench in Claude Code or Codex.
Prompt placeholder: start or resume the Week 1 orientation. Add after the lesson-content pass.
The Professor
It explains unfamiliar ideas, asks one question at a time, and helps you learn from the work. Call it in any time you have a question.
Right now it talks to everyone the same way. Later this week it interviews you, and from then on it teaches your way.
Your Chief of Staff
It coordinates the organization's jobs. You give it the work; it decides which agents the job needs, brings back what they did, and brings the decisions to you.
Later this week you hire it and choose its style, so it briefs you the way you like to be briefed.
You call in these two yourself. Every other agent is reached through your Chief of Staff.
Hunter's wording for this paragraph
The Professor is your course companion. It explains unfamiliar ideas, asks one question at a time, and helps you learn from the work. Chief of Staff coordinates the organization's jobs. You'll speak directly with these two agents in Week 1; requests for other specialists go through Chief.
"Tutor" is gone, which clears your flagged word. New to rule on: the draft shortens Chief of Staff to "Chief" (11 times on this page: "go through Chief," "Locate Chief"). Your pages say "your Chief of Staff" or "the Chief of Staff."
- Open Claude Code. Look at the folder name under the message box. If it isn't your workbench, click it and choose Open folder, then pick your workbench folder.
Click the folder name, then Open folder. (Essentials screenshot, Wade's screen.)
Click the folder name, then Open folder. (Essentials screenshot, Wade's screen.)Click the folder name, then Open folder. (Essentials screenshot, Wade's screen.) - Check the folder name now shows your workbench.
The folder name under the message box is the folder you're working in. (Essentials screenshot: it shows agent-native-os, yours shows your workbench.)
The folder name under the message box is the folder you're working in. (Essentials screenshot: it shows agent-native-os, yours shows your workbench.)The folder name under the message box is the folder you're working in. (Essentials screenshot: it shows agent-native-os, yours shows your workbench.) - Start a new thread. This only works on the first message.
- Type @. A list of your agents appears.
- Pick The Professor from the list. Not in the list? Do step 6 of 0.3 Get your organization. Until then, skip the list and paste the words below as they are: they ask for The Professor by name.Screenshot needed. The @ list open in a workbench, with The Professor picked, and the blue tag at the top right. Nobody has taken this one yet.
- Look at the top right. A blue tag shows you're now talking to The Professor.
- Paste the words below and send.
Use the native aibl-the-professor agent to start or resume orientation. Read course/workforce/prompts/orientation.txt and course/workforce/orientation.md completely. Check my approved saved work, ask one question, and wait. Report missing files or native routes; do not install anything.
It's always Claude Code or Codex doing the work. The agent you pick decides what job it's doing and what it's allowed to touch.
On Codex there is no list to pick from. You ask by name, in your first message: "Have The Professor handle this." Codex starts The Professor, and its answer comes back to you through Codex.
Claude Code: you call the agent in. New thread, type @, pick it from the list, and the whole thread then runs as that agent. Tyler proved this for the Chief of Staff on Sept 20. His notes say it is not yet tested for The Professor. If you type the name by hand and don't pick from the list, you get a weaker version: the main Claude passes your message along and retells the answer.
Codex: you only ask by name. His notes: "in Codex only the spawn-by-name route exists and the reply is relayed by the caller, with no session picker verified." So in Codex you are never talking to The Professor directly; Codex fetches its answer for you. An earlier version of this box said "type @ and choose the agent" for Codex. That was wrong and is fixed.
Why it matters for the lesson: "a blue tag shows you're talking to The Professor" is true in Claude Code only. A Codex student needs a different check that the agent really ran. Question for Tyler and Hunter: what does a Codex student look for?
essentials/shots/carry/06-...); they show Wade's screen and the Essentials folder, so a workbench version is worth retaking. Still to confirm with Hunter: the exact name students see in the @ list, and the Codex line (Q32). Candidate wording.The pieces, and how they fit
The course gives you a starting organization to inspect and adapt. You learn by giving it work, seeing what happens, and making changes you understand. In Week 3, you'll use that experience to build a department of your own.
First, separate the places you'll use:
| Piece | What it is for |
|---|---|
| You, the Director | Set the direction, approve what may be used, and decide what happens to the work. |
| Your workbench | The folder holding the organization's instructions, approved information, and work records. |
| Claude Code or Codex | The app where you talk to agents and direct work. Select the correct workbench before starting. |
| The dashboard, where available | A view of the organization and saved work. A label on a screen doesn't replace the work it describes. |
| GitHub | The remote copy you set up in Essentials. Only files included in commits and successfully pushed are copied there. |
Same point you made earlier tonight. It is much shorter now (five rows, not six paragraphs), so it may be fine as the text version of the drawing. Candidate: drawing first, table after it.
The LMS is where you read. Your workbench is where you do the exercises. You don't need to browse GitHub to speak to an agent.
Read the picture as a map of these places: you direct in the app, work happens in the selected workbench, and saved records can be inspected in the dashboard. A remote copy is separate from both.
Hunter's placeholder asks for your Two Doors drawing "without promising a working dashboard or backup." Your drawing says "Team HQ... watch, approve, read receipts" and "GitHub keeps a copy." So the drawing needs a redraw before it ships, not only a label fix. Still open from Sept 19: where is the dashboard (Q22).
Sara's “Two doors, one company” concept, updated to the selected edition. Show app, workbench, supported dashboard, and GitHub copy without promising a working dashboard or backup.
Two more pieces sit underneath. The model generates responses and helps choose actions. Tools let the app or agent do things, such as read a file or use an approved connection. Written instructions describe the job; the selected app, tools, and permissions affect what can happen.
Walk around the organization
The organization is described in files you can open. Its agent roster lists the roles available in the selected edition. A profile being present, an agent being available to call, and an agent having completed a job are three different things.
Your organization lives in a folder. An app and a model put it to work.The folder you own, plus the app you install and the model you rent, makes a working organization. Only the folder is yours for good.
Text alternative: Your organization lives in a folder. An app and a model put it to work. On the left, the folder my-workbench: CLAUDE.md and AGENTS.md, the note every agent reads first; workforce, the organization, holding profiles (staff files, one job description per agent) and skills (how each kind of job gets done); charter.md, the rules every agent works under; knowledge, the approved facts about your work; work, the records room. On the right, a sum: the folder (you own it) plus the app, Claude Code or Codex (you install it) plus the model (you rent it) equals a working agent organization. Take one away and nothing runs. Only the folder is yours forever.
Four times on this page ("selected edition," "course edition," "compare editions"). A student has one workbench and doesn't know there are editions. Candidate: "your workbench" or "the version you installed."
This week, you're working with these eight named agents:
Hunter's wording
Tyler's Week 1 package focuses on eight named agents:
Chief of Staff
Coordinates jobs, reports what happened, and brings decisions back to you.
The Professor
Helps you understand and practise the lessons.
You've Got Mail, or YGM for short
Your Communications Writer. Produces drafts from approved material.
Kansa, your Quality Reviewer
Checks work and explains its findings. You decide what to do.
Echo, your Voice Analyst
Studies permitted examples and describes communication patterns. It doesn't write finished copy in that voice.
The Knowledge Librarian
Handles approved knowledge and its sources. You'll study this more closely in Week 2.
The Charter Steward
Reviews the agreement and reports differences between it and the actual setup.
Gigawatt
Helps with authorized technical setup and building. It doesn't replace your approval.
Every other agent has a title. Gigawatt is described as "authorized technical setup and building." Your ruling: Gigawatt builds in Week 3. Tyler calls it "the operator." Question for Tyler and Hunter: does a Week 1 student ever call it?
His notes say so directly: "You've Got Mail, or YGM for short" and "Kansa, your Quality Reviewer" are "Hunter's explicit choices" and "supersede the older title-only naming proposal for this draft." Your rule (C92, C104): the job title is the name, the nickname once in brackets, then the short form. Here the nickname leads for YGM, Kansa and Echo, and the tour says "Locate Chief, YGM, and Kansa." This one needs a ruling between you and Hunter before any more pages are written.
The broader course chart includes Customer Support, Growth, Marketing, Operations, Sales, and Quality, along with support for learning and building. It shows the design you're studying. Check the installed roster to learn which roles are actually available now; don't treat every box as an agent that has run.
The draft now says the right thing: eight now, the chart is the design, check the roster. It never says when or how the other agents arrive. It also never says the number twenty any more, while the chart still shows seventeen agents plus three Faculty.
Chief, the Knowledge Librarian, and the Charter Steward belong to the Executive Office. Specialists contribute the work their roles own. Chief can coordinate a job across departments; the organization isn't one fixed assembly line.
The chart below should help you find Chief, the Writer, the Reviewer, and your decision point. Keep the broader organization visible, with unavailable or later roles clearly marked.
adapt Sara's organization board to the Week 1 roster. Distinguish supplied, available, and observed-in-use roles. Include the place for the student's Week 3 department.
This is the organization you're working toward over the next four weeks.
Read it from the top. You're at the top, the Director. Your Chief of Staff is the front door, right beside you. Under that are the departments, with one line on what each agent does. The eight you just met are already in your workbench. The rest of the chart is where you're headed, and the empty floor at the bottom is where your own department goes in Week 3.
The agent organization you inherit.The chart you start with: you and your Chief of Staff at the top, each department and its agents below, and an empty floor for the department you build in Week 3.
The agent organization you inherit.
Executive Office
- Chief of StaffBriefs you, names the specialists a request needs and says why, keeps your decisions in view.
- Knowledge LibrarianFinds evidence and proposes where approved information should live.
- Charter StewardKeeps the agreement and the records straight.
- Calendar keeper
- Meeting prepper
- Travel planner
Marketing
- Voice Analyst EchoAnalyzes permitted samples and describes communication patterns.
- Content
- Social
- Brand
Operations
- Process AnalystMaps how the work happens before proposing a change.
- Evidence Pattern AnalystFinds patterns and gaps in the supplied evidence.
- Automation
- Reporting
- Backlog groomer
Quality
- Quality Reviewer KansaChecks a produced draft before your decision.
- Evaluation Analyst EvyAssesses recorded cases in Week 4, after your own judgments are saved.
- Rubric keeper
- Regression spotter
- Fact checker
Sales
- Sales Discovery SpecialistPrepares a discovery conversation from approved research.
- Pipeline
- Outreach
- Market analyst
Customer Support
- Support LeadCoordinates the case and assembles what comes back.
- Intake Triage AnalystReads the incoming case for need, tone and urgency.
- Internal Knowledge ResearcherFinds relevant evidence in approved business records.
- External ResearcherChecks approved outside sources when the job needs them.
- Communications WriterTurns the approved material into a draft for review.
- Onboarding
- Escalation triage
- FAQ curator
Growth
- Opportunity Desk LeadCoordinates an opportunity and assembles the decision.
- Opportunity AnalystExamines fit, trade-offs and unanswered questions.
- Proposal SpecialistStructures a proposal from the approved findings.
- Podcast desk
- Press desk
- Monthly drops
★ Your department
- Four rolesSupplied profiles you customize for work you choose.
- ★ Your specialistThe fifth. You write it from scratch.
- Whatever your work needs next
Your next departments
- Financebilling, reporting
- Legal and admincontracts
- Peoplehiring, onboarding
- Client deliverykickoff to close
Seven things to recognize
You don't need to memorize filenames today. Learn the question each part answers. Lesson 2 opens the actual files and controls.
| Part | The question it answers |
|---|---|
| Agent profile | Which agent owns this job, and what is its responsibility? |
| Skill | How is this kind of work done? |
| Context | What information and instructions are available for this job? |
| Command or start request | How do I deliberately start the work? |
| Gate | Where must work stop, ask, or be refused? |
| Schedule | What would start a job later? |
| Work record | What actually happened, and what did I decide? |
These are useful categories, not a claim that every file fits only one box. A skill is a method; a tool is a capability it may use. A schedule is separate from working through several steps now. These exercises don't ask you to enable unattended work.
You may recognize CLAUDE.md and AGENTS.md from Essentials. They guide the relevant conversation. Other agents also have their own instructions and receive selected inputs. Don't assume every agent reads every file.
Take the tour
First, call in The Professor. The steps and screenshots are in Start here, above. Then work through these four steps with it.
1. Find your place
With The Professor, confirm the selected workbench and course edition. Locate the roster and organization files. If something required is missing, keep that gap visible.
Say this to The Professor:
Check which workbench we are in. Show me my agent roster and organization files. Name anything missing. Do not change anything or start a job.
2. Find the first job's agents
Locate Chief, YGM, and Kansa. Say which coordinates, which writes, which reviews, and where your decision belongs. Locate The Professor separately as learning support.
Say this to The Professor:
Show me Chief of Staff, Communications Writer and Quality Reviewer in the roster and the file for each. Ask which coordinates, writes and reviews, and where my decision belongs. Wait for my answer. Locate The Professor separately as learning support.
3. Follow a role into its files
Open the Writer's profile and method. Then find where a job's source notes and work records live. Today you are recognizing them; Lesson 2 reads them closely.
Say this to The Professor:
Open Communications Writer's profile and writing method. Explain in one sentence what question each answers, then show where the first job's request, source notes and work records live. Do not change them.
4. Open your before photo
Ask The Professor to help preserve the organization as you found it, with your permission. Begin the existing starting-picture worksheet rather than making another copy. Note what is supplied and what you have actually observed.
Say this to The Professor:
Help me open my before photo. Reuse the existing worksheet and any saved record. Show what you propose to save and where, then ask for my approval. Distinguish supplied roles from work I have actually observed. Read back anything I approve saving.
Your C90 wording is used. "Three original answers" means the three cold questions from Lesson 3; a student reading this page can't know that. Candidate: "three questions you ask before it knows anything about you."
The before photo is a record, not necessarily a screenshot. You'll add three recurring work cases, three original answers, and a plan for information you may share. Lesson 3 completes it before you introduce more context. Later comparisons need an unchanged starting point.
- The chart and roster differ: compare editions and labels. A larger chart doesn't prove the installed package is wrong.
- An agent name appears in chat but there is no returned work: ask which agent actually ran. A description or demonstration isn't a completed job.
- The dashboard isn't available: inspect the files and record the missing view. Don't build a replacement as part of this tour.
- The folder feels overwhelming: start with one profile, one method, and one source note. Ask The Professor what question each answers.
Before you move on
You can find the workbench, distinguish it from the LMS and remote copy, and explain Chief, The Professor, the Writer, and the Reviewer. You can find a role's instructions and distinguish an available role from observed work. Your starting picture is open, with missing information left as missing.