Meet every agent in your organization

See your agents, department by department

Read the job lines, not just the names.

You have worked with some of these already. In Week 1 you called some yourself. The Chief of Staff called others on your behalf, so you may have used an agent without seeing its name.

How you reach a seat. In Claude Code, you @mention a seat at the start of a thread, and that thread stays with it: you can’t switch seats partway through, so start a new thread to reach a different one. In Codex, you reach a seat through the Chief of Staff, which relays your request to it.

Seven are new additions this week. They are marked below. You do not need to remember them all today.

Every agent has a function name, which says what it does. Some also have a nickname, such as Sallee or Cipher. The function name helps you understand the role before you learn the name.

Faculty is different from the other departments. Its agents help you learn, design, and set things up. The business agents carry out the work.

Your organization has twelve business agents and three Faculty agents. The wider roster is available to explore. You do not need to find an exercise for every agent this week.

Do this now: ask about the agent that surprised you

Pick a job line you did not expect. Maybe the agent does less than you assumed, maybe more.

Ask Gigawatt, and name the agent you picked:

Keep the answer tied to the installed record. You are learning about the role, not starting a job.

The words you’ll see in your registry

Week 1 introduced many of these. Here they are together because you are about to see them on screen.

A seat is a position. An agent is what fills it.

Your organization has fifteen seats, each with an agent assigned to it.

Here is a shortened teaching example from Echo’s registry record. The comments explain the fields; the job line is shortened for this example. Gigawatt can show your installed record in full.

departments:
  - name: Marketing       # A department
    seats: [aibl-echo]     # The seat assigned to that department
seats:
  - name: aibl-echo        # The agent's identifier
    title: Voice Analyst (Echo)
    department: Marketing
    job: Build an evidence-backed voice package from approved samples. # The job line, shortened

Read it from the top: Marketing contains Echo’s seat. Echo’s record then tells you which agent fills it and what work it does. This example helps you read the registry; it is not something to paste into or edit in your workbench.

The registry describes your agents

Each agent works from its own instructions and available tools. The registry brings information about those agents together so you can inspect it.

1. The registry describes the agents. Editing a description is not a reliable way to change what an agent can do.
2. Gigawatt rebuilds the registry from the underlying records. A manual edit can be overwritten the next time it is rebuilt.
3. If something needs changing, ask Gigawatt to identify the source of that setting and show you a proposal.

Who holds what is recorded in one place. The charter says what your organization may do, and the registry says which agents exist and which tools and connections each one holds. When new agents join or an agent gets a connection, the Charter Steward records the change on your yes. These lists limit each agent, not the main chat you type into. In Claude Code the app holds each agent to its line; in Codex the lines are your records in words, and an agent can reach whatever the chat can.

For this lesson, you only read. You do not need to change an agent or edit the registry.

Later this week, giving the organization your selected source material will help it understand your work. That does not require you to rewrite an agent’s instructions.

Read one agent’s record

Open workforce/shed/registry.yaml in your file editor, or ask Gigawatt to show one agent’s record exactly as written.

Here are the fields you may see:

Some limits are enforced by the tools an agent has. Others are instructions it must follow. Reading a rule is not the same as proving that a particular run followed it.

For example, the Communications Writer does not review its own draft. A separate reviewer checks the work. You will use that same separation when Cipher drafts your SOP and Kansa reviews it.

Do this now: read three lines

Choose one agent and find:

• Its job.
• Its never list.
• Its connectors entry.

Say one thing you learned from those lines before asking Gigawatt to explain more.

You do not need to understand every field today.

Understand what a connector entry means

Your organization keeps its registry and related lists in workforce/shed/. The course calls this folder the shed. It is a small version of the Tool Shed kept inside your workbench, and you can move it into its own repository later.

It records the agents, tools, and connections the organization is configured to use. The agents themselves live in their own files.

You only need to inspect the registry. Gigawatt handles the supporting programs.

A connector entry might be empty:

connectors: []

Or it may list an assignment already made in your workbench.

The connectors line is a label, not a switch. Typing a service name into it does not sign you in or establish access.

There are three separate things to check:

1. The account connection: have you signed in and authorized access in the app?
2. The agent assignment: which agent is supposed to use that connection, and for what?
3. The actual read: can the intended agent read the specific material you approved?

An empty registry entry does not prove that the app has no connected accounts. A filled entry does not prove that a read will succeed.

In Module 2, you will choose a source route, approve a small selection, and check that the intended read works. That connection needs to work for this week’s exercise.

Do this now: name one useful source

Name one place outside the workbench where evidence for your process might live.

Write it in your own notes. Do not connect the account or collect the material yet.

If you get stuck

What you’ll keep

Nothing is added to your organization's library in this lesson, and no agent changes. Gigawatt does keep its own short working notes for each job, in the runs/ folder: what it read and what it planned. You don't need to open them.

Keep your note naming one outside source you may want to use.

Before you finish

You do not need to memorize all fifteen agents.

Words you now own

• A seat: a role your organization needs filled.
• An agent: what fills the seat and does the work.
• A department: a group of related seats.
• The registry: the generated list describing the installed agents and their setup.
• A connector assignment: the recorded relationship between an agent and an outside service; it does not sign you in.

Next: Lesson 2, follow this week’s working group and choose your process.