Read how your organization is arranged
Which agents will help me turn my examples into an SOP, and which decisions stay with me?
- Source
- Current Internal package, pages/anw-l10.html (Internal b518c35b; src/hunter-week2/SOURCE.md). Original handoff: Internal PR #125.
- Copy
- Exact Internal source package, vendored without editing its lesson or prompt bytes.
- Prompts
- Prompts are rendered from the current vendored Internal package named in Source. Historical publication: student 50ab8c5c from Internal 0e2885b5; that receipt does not qualify later Outlook changes.
- Checked in the app
- Historical baseline QA: bounded integrated checks passed for fresh preparation, upgrade, supported-model native routing and tracing. This receipt does not qualify later Outlook changes. Ordinary-student and Windows qualification remain unverified.
- Open to students
- Yes.
- Other view
- one part at a time (Wade chose one part at a time; one scroll is kept to compare)
In the last lesson you met all fifteen of your agents and learned to read the registry that lists them. You don’t work with all fifteen this week, though. Week 2 is about taking one process from your business and turning it into a written procedure, and six of your agents do most of that work with you.
Today you get to know those six: what each one does, how work passes between them, and where each decision comes back to you. By the end of the lesson you will also pick the process you want to work on for the rest of the week, so keep a few candidates in mind as you read.
A clear picture of who does what this week, and one process chosen to carry into Module 2.
Once you know what each agent is for, you know where to send a job, and you can tell when a decision is supposed to come back to you instead of being made for you.
The Professor takes you through the lesson. You look at one department with Gigawatt so you can see how agents are grouped, then you meet the six agents for this week, ask Cipher yourself what it will need from you, and choose your process.
You choose the process, and you make the decisions along the way. You don’t change any agent’s instructions this week, and you keep every agent’s name for the whole course, so what you see keeps matching the lessons. The one exception is your Chief of Staff, which you could name in Week 1. If you didn’t and would like to, tell your Chief of Staff the name you want. Gigawatt shows you every line it would change and waits for your yes. After the course, the agents are yours to rename and reshape.
Before you start
Use the same workbench and registry you checked in Lesson 1.
If one of the six agents is missing, ask Gigawatt to fix that before you go on. Don’t ask a different agent to stand in for the missing one, because it will only be guessing at a job that isn’t its own.
Start or resume this lesson
Use the native aibl-the-professor agent to start Week 2 Module 1 Lesson 2. Read course/workforce/week2/prompts/anw-l10.txt and course/workforce/week2/lessons/anw-l10.md. Take me through the four parts in order and ask one question at a time. When a part gives me a line for Gigawatt or Cipher, let me send it myself. Help me write my process, who does the work day to day, who can answer questions about the steps, where the three examples probably are, and the workstream my process belongs to. Change no agent file. If the named agent is unavailable, pause and ask Gigawatt to check the installation.
Read one department
A department is a group of agents that work on related jobs, a bit like the teams in a small company.
You don’t sort agents into departments yourself. Each agent’s record says which department it belongs to, and when Gigawatt builds the registry it groups the agents by that line. For example, here is part of Echo’s record:
profile_slug: aibl-echo
display_name: "Voice Analyst (Echo)"
department: MarketingAnd because of that line, this is where Echo shows up in the registry:
departments:
- name: Marketing
seats: [aibl-echo]You are only reading these to see how the two connect. You don’t need to edit either file.
What a department tells you
Customer Support is a good example to look at. When a customer message comes in, several agents in that department can each do a part of the job. Cinnamon works out what the customer is actually asking. Holler plans how the case should be handled. Hatch looks for the answer in material you have approved, and Scratch checks approved outside sources when that’s needed. Then You’ve Got Mail drafts the reply.
The Chief of Staff decides which of those agents a given case needs, so not every agent works on every case. A department shows you how the roles relate to each other, not a fixed assembly line.
Do this now: explain one department
Pick any department. Then send this line in your session, with the department’s name filled in:
Use the native aibl-gigawatt agent to show me the job line of every agent in the [department] department, exactly as written in their records. Change nothing.
Then say, in one sentence of your own, what kind of work belongs in that department. If your sentence comes out vague, go back to the job lines and try again. The point here is that you understand the work, not that you can remember the names.
Meet the six agents you’ll work with this week
These are the six agents who will help you this week, what each one does, and what stays your call.
| Agent | What it does this week | What you decide |
|---|---|---|
| Chief of Staff (Chief for short) | Sets up each job and passes the work between the other agents. | Whether the job is the right one and its scope makes sense. |
| Gigawatt | Sets up Langfuse, connects your sources such as your email, and fixes setup problems. | What the agents are allowed to access and record. |
| Sallee | Files your examples into Cairns, your organization’s library. | Whether what Sallee proposes to file is accurate. |
| Cipher | Maps how your process really runs, step by step, and then drafts the SOP. | Whether the map is right and whether the SOP is useful. |
| Kansa | Reviews the SOP draft on its own and reports what it finds. | What to do about each finding and which version to approve. |
| The Professor | Explains the lessons and helps you find your next step. | Your answers and your reflections. |
These six are the agents you work with this week.
Chief of Staff routes each job.The specialists hand work to each other, and every decision comes back to you.
On a small screen, swipe sideways to see the whole diagram.
How the week flows, using a made-up example
Say the process you pick is kicking off a new client. This example is made up for teaching, but the flow is the same for any process.
First you pick three past kickoffs that you are allowed to use. Gigawatt sets up tracing and connects the place those records live, such as your email, and you approve exactly what gets collected. Sallee then files those examples into Cairns, and you check the important details against the originals before you approve the filing.
Next, Cipher looks at those three kickoffs and draws a map of what actually happened, step by step, marking anything it isn’t sure about. Before anything else happens, you look at that map and either say “yes, this map is right” or tell Cipher what to correct. Only after your yes does Cipher turn the map into a draft SOP.
Kansa then reviews that draft on its own and reports anything that is missing or unclear, and Cipher fixes the points you agree need fixing. When you’re happy, you approve the SOP, Sallee files it, and a fresh job uses it to show that it works.
Notice that each stage ends with you deciding. An agent sounding confident isn’t the same thing as you having checked.
Only you can confirm the map
In a lot of businesses, the person who does the work day to day isn’t the person responsible for it. You might pick a process that your office manager or an assistant actually runs. That’s fine, and it’s a good idea to show them Cipher’s map, because they’ll often spot a step that’s missing or out of order.
Their answers help you check the map, but the yes that lets Cipher start writing the SOP comes from you. You’re the one who will approve the SOP later, so you’re the one who confirms the map it’s built on.
Using an agent is not the same as changing it
Giving an agent a source, approving its work, or asking for a different result on one job doesn’t change the agent’s standing instructions. This week, use the agents as they are. If you notice something you think an agent should do differently, write it down for later rather than trying to change it now.
Do this now: predict where you’ll need to check
Think about the process you have in mind and name one place where an agent could get it wrong, maybe by misreading the records or missing a condition that matters. Then say what you would want to check before you approve its work.
“The emails might show that the kickoff meeting was booked, but I’d need to check whether the client had actually signed the brief before we booked it.”
You don’t need to solve anything yet. You’re just spotting the places where your judgment will matter.
Hear what Cipher needs
Reading Cipher’s record in the registry tells you what Cipher is supposed to do. Hearing Cipher answer for itself is a different check, because it shows you the agent is actually installed and working.
You ask Cipher directly. Send this line in your session, exactly as written:
Use the native aibl-cipher agent to answer one question, without reading any of my material and without making anything: what will you need from me before you can map one of my processes?
Don’t add your process to the line, and don’t ask Cipher to read your material, make a map or write an SOP yet. You’re only asking what it will need from you. Cipher answers this one question without a work order and changes nothing.
A good answer should leave you clear on four things: which process it will look at, which past examples show how that process went, who can answer questions about the steps (and that the final yes on the map is yours), and what it will mark as unsure until someone checks.
If Cipher doesn’t answer, ask Gigawatt to find out why. Another agent describing what Cipher would say doesn’t count as Cipher answering, which is why The Professor leaves this question to you.
Choose one recurring process
Now that you’ve seen who will help, pick the process you’ll work on this week. Choose one that costs you time every time it runs, and that you know well enough to check the agents’ work on. It should have a clear start and a clear end, it should happen again and again, and you should have three finished examples of it that you’re allowed to use. If you’re setting this up for a client, choose one of their processes, and make sure you have their permission to use those three examples.
Good choices include onboarding a client, handling a support request, preparing a monthly report, or following up on a new inquiry. Customer support is the worked example in Week 3, so if you choose a support process now, the workstream you build for in Week 3 can come from a different part of your business.
Pick a process you can map in one week, and name the larger workstream it belongs to. A workstream is one recurring piece of work in your business, from what starts it to the result someone receives. It has several stages, and each stage could be a process of its own, so a small team could share it. “Everything we do in operations” is a whole area of the business. “Getting a customer’s order from payment to delivery” is a workstream. “How we handle a request to change a delivery date” is one process inside it, and it’s the right size to map this week.
In Week 3 you build a team of about five agents for your workstream. This week’s process is one part of it, so the workstream line in your notes matters as much as the process line.
What counts as one example?
One example is one time the process ran from start to finish.
For a client kickoff, a single example might include an email thread, a filled-in brief and a calendar invite. Those three files all belong to the same kickoff, so together they make one example, not three. In the same way, three emails about the same kickoff are still one example.
You’ll decide exactly which records to collect in Module 2, so for now you only need a rough idea of where they are. You also don’t need an existing SOP. Helping you write one is the point of this week.
Do this now: write your choice
Write these five lines in your own notes:
The process I’ll work on:
Who does this work day to day (this may be me):
Who can answer questions about the steps (this may be me):
Where the three examples probably are:
The workstream this process belongs to (what starts it, the main stages, what finishes it, and who receives the result):
The third line matters because Cipher will leave questions on its map, and you need to know who can answer them. You’re only noting where things are. You aren’t giving any agent access yet.
If you’re having trouble choosing, ask The Professor to help you narrow it down. It should ask you one question at a time and let you make the choice.
If you get stuck
| What you notice | What to do |
|---|---|
| The departments in your registry look different from this lesson. | Ask Gigawatt to explain the difference using your installed registry. |
| Cipher doesn’t answer. | Ask Gigawatt to check that Cipher is installed and being called correctly. |
| Your process has several parts that could each be mapped on their own. | That is probably a workstream. Write it on your fifth line, then pick one part with a clear start and a clear end to map this week. |
| You can’t use the examples you have. | Pick a different process. Don’t make up examples and treat them as real records. |
| You don’t know who does one of the steps. | Write down that you don’t know. Don’t guess. |
| You want to change how an agent works. | Write the idea down for later. It doesn’t need to happen this week. |
What you’ll keep
Your five lines: the process, who does the work day to day, who can answer questions about the steps, where the examples probably are, and the workstream the process belongs to.
Nothing is collected or filed into Cairns in this lesson.
Before you finish
You don’t need to call every agent or change anything in your organization before moving on.
Words you now own
- Working group: the six agents helping you turn your process into an SOP this week.
- Recurring process: work with a clear start and end that happens again and again.
- Workstream: a larger piece of recurring work, from what starts it to the result someone receives. It has several stages, and each stage could be a process of its own.
- Completed example: one time the process ran from start to finish, even if several files describe it.
- Process owner: you, the person who confirms the map and approves the SOP. Other people may do the work and answer questions about it.
- Handoff: what gets passed to the next person or agent so they can do their part.
Next: Module 2, set up Langfuse, connect your selected work, and learn Cairns as that material is processed.