Get ready for Week 4
Is my organization ready for Week 4, and how does it keep itself in order from now on?
- Source
- Internal's lesson, src/sara-week3/internal/lessons/anw-w3-l12.md (Internal b518c35b, 2026-10-22 17:15), read by md_week3.py.
- Copy
- Current Markdown is vendored byte for byte from the Internal commit in Source by vendor_week3.py. Historical publication records: 10-06 Exercise 1 with Sara's yes; 10-07 Exercise 2 and the Module 2 send-route and follow-up fixes, student 58c60d50; 10-08 Exercise 3 and the l05/l11 diagram fixes, student 55061386. Those records do not qualify later Outlook changes. Module 3 and 4 drawings are rendered from the Mermaid in the lesson file (md_week3.py --figures).
- Prompts
- Word for word from the lesson file Internal ships (course/workforce/week3/). Not run end to end from Learn.
- Checked in the app
- Not checked in the app from Learn.
- Open to students
- Yes.
- Other view
- one scroll (one part at a time is the lesson; one scroll is kept to compare)
Staff review only: full controlling prompt. Students paste only the short request below.
Use the native aibl-the-professor agent to guide the Week 3 lesson Get ready for Week 4. Read course/workforce/week3/lessons/anw-w3-l12.md completely, its details page course/workforce/week3/reference/anw-w3-l12-details.md when asked for more, and the native aibl-course-guide and aibl-lesson-map methods for this app. You teach and read; you never run the readiness check, turn the daily check on or off, record a ruling, give a brief or clear a missing item for the student. The daily check is normally already on: it was turned on when the student's third team was installed. If it is off, the student turns it on with one yes to "set up Week 4", in their own words, and the Chief files the ruling. The student talks to the Chief of Staff in its own thread. Do not call, spawn or route to any agent. Do not edit any file. Never write, suggest or pass on a yes; every yes is the student's own words in the Chief's thread.
Use these words exactly. The readiness check is workforce/shed/readiness_check.py: it reads only and prints six lines, each READY or MISSING, then "Readiness: N of 6 ready." The six are: three teams (Customer Support and two teams on the record); five test cases with notes for each recorded team; the starting point in each team's design; the Week 3 section of the handoff notes in context/handoff.md; the org chart before and after (two registry printouts with different counts); and the Charter Steward's daily check. The daily check is the Charter Steward's check of the organization before the first brief of each day, while the student's ruling says it is on: five checks, every finding a proposal, nothing recorded. A ruling is the student's decision, filed by the Steward in work/course/staff/decisions/; the ruling that turned the daily check on was filed with the third team's install. Nothing is scheduled on the computer. Name agents job title first, nickname in brackets on first use. Say "your work", never "business"; refer to other lessons by title, never by number.
Ask open questions only. Never decide for the student whether to turn the daily check on, and never accept a proposal for them.
Part 1. If asked, read the readiness check's lines as the student shows them, and help them match each MISSING line to the row in the details page that says what clears it. Say which lesson, by title, holds the step.
Part 2. If asked, read the ruling as the student shows it, and say back plainly what it turned on, when it was filed, and how to turn it off.
Part 3. If asked, read runs/<today>-steward-daily/daily-check.md, read only, and help the student see each proposal, who would make the change, and that nothing changed yet.
Otherwise, if asked, explain the step and what the student should see.
Staff only: status, sources, what the build supports. Not student-facing.
Status: SHIP, 6 October 2026. Written to Sara's standard from the 4 October V3 draft (handoffs/aw-week3-v3-overnight-20261004/lessons/anw-w3-l12.md) on branch gigawatt/aw-week3-ex3-ship-20261006. Tyler and Sara ruled to ship it now and tweak it after it is live. Each part opens with what the student does and gets; mechanics live in course/workforce/week3/reference/anw-w3-l12-details.md; no test status, probe ids or lesson numbers in student text or the paste prompt.
What the build supports (the page states each as the supported path): workforce/shed/readiness_check.py (read-only; six lines, READY or MISSING, then "Readiness: N of 6 ready."; allowed in the house settings); the Charter Steward's duty 8, the daily check (five scripts, proposals only, nothing recorded); the Chief's aibl-brief skill, Step 0 (before the first brief of the day, when the owner's latest ruling says the daily check is on and runs/<today>-steward-daily/ does not exist yet); the Chief's file (the daily check is turned on or off by the owner's ruling, which the Steward records; nothing is scheduled or installed).
Where the build differs from the spine: "turns on the Steward's daily check" is a ruling, not a timer. The check runs the first time the student asks the Chief for a brief each day; a day without a brief is a day without a check. A real schedule would be a standing change on the student's computer. The readiness check counts Customer Support from the registry and needs two teams on the record.
| Figure ID | Lesson | What it shows | Caption | Alt text |
|---|---|---|---|---|
w3-l12-daily-check | anw-w3-l12 Part 2 | You open your Chief of Staff at the start of your day; an arrow to "first brief today?"; yes: the Charter Steward runs five checks and writes proposals; they appear in your brief under Needs you; a stamp "nothing changes without your yes" | Your organization checks itself each day, and asks you before it changes anything. | When you ask your Chief of Staff for your first brief of the day, it first has the Charter Steward check the organization. The Steward writes proposals only, and they appear in your brief, each waiting for your yes. |
You now have three teams: Customer Support and the two you designed. Week 4 grades them, so today you check that everything it needs is in your files.
Then you check one more habit, turned on when your third team was installed. Each day, before your first brief, the Charter Steward checks your organization and proposes anything that needs fixing. It changes nothing on its own.
Nothing is scheduled on your computer. The check runs when you ask your Chief of Staff for your first brief of the day.
A readiness result for Week 4, and a daily check, already on, that keeps your organization's records honest.
Three teams make a lot of files. A small check every day catches a mismatch the day it happens, not a month later.
The Course Companion (The Professor) guides you in its own thread. Your Chief of Staff runs the readiness check and the daily check before your first brief, in one thread. The Charter Steward filed the ruling that turned the daily check on with your third team's install, and writes the daily proposals.
You read the results, and say yes or no to each proposal. If the daily check is off, you turn it on with one yes.
Before you start
- Your third team is on the record. You finished the lesson "Brief your Chief of Staff to build a third team while you're away, and check it when you're back".
- Nothing to open. Your Chief reads your records.
- In Codex, start your first message to an agent in a thread with "Ask the <agent> to do this, and show me its reply word for word:". Start every message after that with "Tell the <agent> this, word for word, and show me its reply word for word:".
Start or resume this lesson
Open your prepared workbench and call The Professor by its role name, aibl-the-professor. Paste only this.
Use the native aibl-the-professor agent to start the Week 3 lesson Get ready for Week 4. Read course/workforce/week3/prompts/anw-w3-l12.txt and course/workforce/week3/lessons/anw-w3-l12.md. Ask me one question at a time and wait. I will talk to my Chief of Staff in its own thread.
The full instructions your agent follows for this lesson are in course/workforce/week3/prompts/anw-w3-l12.txt.
You ask your Chief whether you're ready for Week 4. You get six lines, each READY or MISSING, and the file it found or looked for.
Six things Week 4 starts from
The check looks for six things in your files: three teams, five test cases with notes for each team you designed, your starting point in each design, the Week 3 section of your handoff notes, your org chart before and after the new team, and the Charter Steward's daily check. It only reads. It changes nothing.
Do this now: ask your Chief
In Claude Code: start a new thread, type @ and pick aibl-chief-of-staff. In Codex: start a new thread and begin with "Ask the Chief of Staff to do this, and show me its reply word for word:". Use this thread for every step in this lesson. Say:
Am I ready for Week 4? Run the readiness check and show me what it says.
What you should see
Six lines, each READY or MISSING, then:
Readiness: <number> of 6 ready.
Line 6, the daily check, says READY if your third team's install turned it on; if it says MISSING, Part 2 turns it on with one yes. For any other MISSING line, ask your Chief, in the same thread, what would clear it. What each line looks for, and the lesson that clears it: more detail on this lesson.
You read the ruling that turned the daily check on, filed with your third team's install. You get it shown word for word. If it is off, you turn it on with one yes.
Nothing changes without your yes.
A ruling, not a timer
The daily check is on because the Charter Steward filed a ruling, like your other rulings, when your third team was installed. From then on, before your first brief each day, your Chief has the Steward check five things: your registry, your charter against your settings and agent files, every agent's records, your teams' records, and your roster. Anything it finds comes to you as a proposal. The Steward records nothing on its own.
Do this now: read the ruling
In the same Chief thread, say:
Show me the ruling that turned on the Charter Steward's daily check, word for word.
What you should see
The ruling, word for word, from work/course/staff/decisions/, with your third team's install receipt as its evidence.
If line 6 said MISSING: the daily check is off. Say, in the same thread, in your own words:
Set up Week 4.
That one yes turns the daily check on: the Steward files the ruling, and your Chief shows it to you word for word.
You ask for your brief. You get the daily check's results in it, and your readiness check again, now with line 6 READY.
Do this now: ask for your brief
In the same Chief thread, say:
Brief me.
Then, in the same thread:
Run the readiness check again and show me what it says.
What you should see
Your brief, saying it ran the Steward's daily check first, with the check's summary under Ran and any proposals under Needs you, each with its file in runs/<today>-steward-daily/. Then the readiness check, with line 6 READY. Nothing on the list changes without your yes: the daily check only proposes.
If you get stuck
| What you notice | What to do |
|---|---|
| The brief didn't run the daily check | It runs once a day, before the first brief. If you already had a brief today, it ran then. Look for a folder in runs/ named with today's date and steward-daily. |
| Your app asks to run a check during the daily check | Allow it. The checks only read, and save their results in that day's steward-daily folder. |
| A proposal you don't want | Say no, in your Chief's thread. Nothing changes without your yes. |
| Line 1 says one recorded team | Your third team isn't on the record yet. Finish Part 4 of the lesson "Brief your Chief of Staff to build a third team while you're away, and check it when you're back". |
| Line 5 shows one printout | Ask your Chief to have the Charter Steward print your registry now. Your printout from before the new team counts as the before. |
| You want it off | Say, in your Chief's thread: "Turn off the Charter Steward's daily check. Have the Steward record my ruling." |
What you'll keep
Your readiness result, and a daily check that runs before your first brief each day.
Before you finish
Check what is on your screen:
You can also say which of the six things Week 4 needs are in your files. Self-assessed. No gate.
Words you now own
- Readiness check: a check that reads your files and lists what Week 4 needs, READY or MISSING. It changes nothing.
- Daily check: the Charter Steward's daily check of your organization, run before your first brief, proposing changes and recording nothing.
- Ruling: your decision, filed by the Charter Steward, that your organization follows from then on. The daily check's ruling was filed with your third team's install.
More background for every part: more detail on this lesson.
Next: Week 4.