Turn what you found into the rules for this team

We show you: the Hattie B's practice inbox

The example student had six fails across three cases. Several were the same mistake, so they made three piles:

In Part 3, "Made-up food facts" became a job-level rule and rules for the writer and Kansa.

Name the mistake, not the case. "Made-up food facts" says what went wrong. "The kids plate email" only says where.

A pile can hold a single fail. As you grade more work, piles fill up.

Do this now: make your piles

In a new thread with your Chief of Staff, say:

Read the list. Put the fails that went wrong in the same way together, and give each group a short name. Write your piles down: you give them to Gigawatt in Part 3.

What you should see

A list of every fail, each with your reason word for word. Your Chief doesn't group them or name them. That's your job.

The starter checks

Every team starts with the same six checks, three for each level:

They're broad on purpose: a starting point, not finished rules. In Part 3 you make each one specific to your work. An agent you have nothing to say about keeps its three as they are.

Your design's lines

Your team already has rules written down. There are two kinds.

"Fails if" lines, in your design. Each test case you wrote with the Architect (Archie) last week ends with one. Here's a case from Archie's worked example, a newsletter team:

> Case 1: the ordinary job<br> > Input: this month's sources and last month's issue<br> > Should: one change, three lines on what it means, every fact sourced<br> > Fails if: two changes, or a fact with no source

"Never" lines, in each agent's file. Every agent's instructions say what it must never do. Here's part of the Communications Writer (You've Got Mail)'s file, on your email team:

> You draft. You never send. Nothing you write leaves this organization without the owner saying yes, and the sending is theirs to do. > > Never: an invented date, link, price, scarcity claim, or testimonial. Instead: the work order's placeholder, kept exactly.

Your email team has no design, so it has no "Fails if" lines. Its "never" lines are in its agents' files, like the one above.

Do this now: ask Gigawatt for your starting list

In Claude Code: start a new thread, type @ and pick aibl-gigawatt. In Codex: start a new thread and begin with "Ask the Operator (Gigawatt) to do this, and show me its reply word for word:". Use this thread for the rest of the rules. Say this, with your team's name:

What you should see

Gigawatt lists the six starter checks, then every "Fails if" and "never" line for your team, word for word. It doesn't write any rules yet.

Every rule starts with "Fails if"

You'd naturally write "The reply should be accurate." But "should" leaves room to argue. "Fails if" names the exact thing to look for, so the grade is easy to call: it's there, or it isn't.

The two-people test

A rule is clear enough when two people could read it, read the same case, and give the same grade.

"Never claim something about food" fails the test: one person reads "the fries are crispy" as a claim, and another doesn't. The "after" version names exactly what counts.

We show you: the Hattie B's practice inbox

The example student's rule sheet, version 1.

About the labels. Each rule gets a short label, so your grades and Evy's can point at the same rule. J means a job-level rule and A means an agent-level rule. The number is just its place on the sheet: J1 is the first job-level rule. Each rule also gets a short name, so you never have to remember what a label means.

Start small. Write three or four rules at the job level, and three for each agent you graded in the last lesson. Agents you didn't grade keep the three starter checks for now. On the email team, that's two agents who didn't come up in the student's cases: the External Researcher (Scratch) and the Intake Triage Analyst (Cinnamon). Add rules as you grade more work, but never more than eight for one agent or at the job level.

Do this now: write your rules

In the same Gigawatt thread, give it your piles from Part 1:

For each rule, decide: is it mine, and would two people grade it the same way? Change any word you don't like, in your own words.

What you should see

Gigawatt proposes one rule at a time, says where it came from, checks it with the two-people test, and waits for your yes or your change. It never adds a rule you didn't find without asking.

What you should see

Your rule sheet, word for word, saved with your team's records as version 1.

Why versions? Your rules will change. In the next lesson, when you and Evy disagree because a rule was unclear, you reword it, and that makes version 2. Every grade records which version it was graded against, and every version is kept, so you can always see what changed and when.

Why you grade again, rule by rule

In the last lesson you gave each case one grade at the job level. Evy grades rule by rule, so for a fair comparison you need a grade for each rule too. Most come straight from what you already said: your fail on the kids plate question becomes a fail on J1 (no made-up food facts) and J4 (nothing I'd have to change).

To go faster, start from your reasons in the last lesson. Most rules are a quick pass. Only the rules that match a mistake need a full reason.

Only the rules you grade are compared

Evy will grade every rule. The comparison only counts the rules you graded too, so a rule you leave blank never counts as you and Evy agreeing. Grade every job rule for each case. Grade an agent's rules where you looked at that agent's piece.

What sealing is, and why

Sealing means your grades are locked so any later change shows. Here's how it works:

1. The Professor saves your grades, one small file per case.
2. Your Chief runs a sealing program on each file. The program reads every character and turns it into a short code that's unique to that exact text. Think of it as a fingerprint.
3. The fingerprint is stored with your grades.
4. Later, the program can check the file again. If even one character changed, the fingerprint won't match, and the change is visible.

Sealing doesn't hide your grades: you can still read them, and Evy is never shown them before it grades. And it doesn't stop changes. It makes them obvious.

It works like the tamper-evident seal on a medicine bottle. You can still see what's inside, but you can tell straight away if anyone opened it.

Why it matters: in the next lesson you compare your grades with Evy's. If your grades could quietly change after you'd seen Evy's, the comparison wouldn't mean anything. The program also refuses to seal a case once Evy has graded it, so seal first.

We show you: the Hattie B's practice inbox

The example student's grades for the kids plate question, rule by rule:

A9 (the practice voice's greeting and sign-off) is left blank on purpose: the student didn't look at the greeting, so that rule isn't part of the comparison for this case.

Do this now: grade, save, seal

In your Professor thread, take one case at a time:

Say yes to each, in your own words. The Professor saves one grade file per case.

When every case is saved, go to your Chief of Staff thread and say:

Seal before Evy grades anything.

What you should see

One line per case from your Chief: sealed, with the date.

Your Chief holds the seal, not Evy and not the Professor. Evy is the one being compared, and the Professor saved the files, so neither should hold the lock on your answers.