More detail: Get ready for Week 4
Optional reading for this lesson. Everything you must do or decide is in the lesson.
This page goes with the Week 3 lesson Get ready for Week 4 (course/workforce/week3/lessons/anw-w3-l12.md). You don't need it to finish the lesson. Read it when you want the longer version.
What each readiness line looks for
The readiness check is workforce/shed/readiness_check.py. It reads your files and writes nothing. Each line says READY or MISSING, with the file it found or looked for.
| Line | READY when | If it says MISSING |
|---|---|---|
| 1. Three teams | Your registry has Customer Support agents, and at least two team records in work/course/staff/teams/ pass the team check. | Put the team that's missing on the record: Part 1 of "Give each agent its tools, and put the team on the record", or Part 4 of "Brief your Chief of Staff to build a third team while you're away, and check it when you're back". |
| 2. Five test cases with notes | For each recorded team, at least five runs of the team, each with Gigawatt's observation notes beside it or naming it. | Run and observe the cases that are missing notes, as in "Run five cases and fix what breaks". For the third team, the cases your background build ran count once Gigawatt has observed them with you. |
| 3. The starting point | Each recorded team's design folder says how long the work takes you now ("starting point", "before-number", "baseline" or "takes me"). | Ask Archie, in its thread, to add your starting point to the design as a new version, and approve it. |
| 4. Handoff notes | context/handoff.md has a Week 3 section. | You wrote it at the end of Week 2, in "Keep the evidence and name the next need". Ask your Chief to show you the file. |
| 5. Org chart before and after | Two registry printouts from the Charter Steward under runs/, with different numbers of agents. | Ask your Chief to have the Charter Steward print your registry now. An earlier printout from before your new team counts as the before. |
| 6. The daily check | Your latest ruling on the daily check, in work/course/staff/decisions/, says it's on. It is filed with your third team's install. | Part 2 of this lesson: one yes, "Set up Week 4". |
The last line is Readiness: <number> of 6 ready.. Week 4 starts from the same files, so a MISSING line now is cheaper to clear than later.
How the daily check runs
Nothing is scheduled, and nothing needed a yes of its own: the ruling that turns the daily check on is filed with your third team's install (or on your one "set up Week 4" yes, if it was off). When you ask your Chief of Staff for a brief, it first looks for your latest ruling on the daily check. If the ruling says on, and the check hasn't run today, the Chief sends the Charter Steward a daily-check order before it writes your brief. A day you don't ask for a brief is a day without a check.
The Steward runs five read-only checks and saves each result in a folder named with today's date and steward-daily under runs/:
| Check | What it compares |
|---|---|
| The registry printout | Every agent has a name, a job and an instruction file. |
| The drift check | What your charter allows against what your settings, connections and agent files for both apps declare. |
| The agent records check | Each agent's declared tools against the registry, its file and your roster page. |
| The team check | Each team record against your registry and its design. |
| The roster change | Agents added, removed or changed since your last roster record. It prints a proposed record only. |
Then it writes daily-check.md: one line per check, and each finding as a proposal, with the change it would make and who makes it: the Steward, on your yes, for a record; Gigawatt, on your yes, for an agent or a setting. A day with no findings says so in one line. The Steward records nothing on the daily check itself.
Turning it off
Say, in your Chief's thread: "Turn off the Charter Steward's daily check. Have the Steward record my ruling." The latest ruling wins. Your earlier rulings stay on file.
Why a ruling and not a timer
A timer would be a standing change to your computer, running whether or not you're there. A ruling keeps the check inside your organization's own records: it runs when you show up for your brief, and every change it finds still waits for your yes.