Try your SOP independently
Can I use my SOP and judge the result when nobody tells me the next step?
- Source
- Current Internal package, pages/anw-l20.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 scroll (Wade chose one part at a time; one scroll is kept to compare)
About this module
You have followed one recurring process from selected sources to an approved SOP. In Module 3, you checked a fresh job with guidance. Now you choose one small case different from the guided attempt and judge the result yourself.
Then you keep the evidence and name one thing your organization still can’t do. Last, you look at your whole organization, ask your Chief of Staff what it is missing, and choose one idea to bring into Week 3.
The last module walked you through checking whether a fresh job could find and use your approved procedure. Today you decide what to try.
Choose one small case of the same process that differs from your guided attempt. Predict what the organization should do, give it a bounded task, and open what comes back.
The deciding is what you’re practicing. The Professor can help when you get stuck, but your choice, prediction, and judgment stay yours.
One independent attempt, your original prediction, and a result you have checked against your approved SOP and the case evidence.
After the course, nobody walks you through it, so this is the check that counts. A procedure can look useful on the page; trying it on another case shows you where it helps and where it still leaves you with a question.
Choose, predict, run one small job, inspect the result, and record your judgment.
You choose the case and decide whether the result is useful. If you ask The Professor to choose, you get a question back. An agent reporting success does not make that decision for you.
You choose, predict, inspect, and judge.The agent only runs the job.
On a small screen, swipe sideways to see the whole diagram.
Before you start
Have the approved SOP from Module 3 and its saved location available. Keep the guided-use result too, so you can distinguish that attempt from this one.
If the SOP is still a draft, return to the review and approval step in Module 3. Kansa’s review and Sallee’s filing do not replace your approval.
Use your prepared workbench. You won't need to look at any traces to finish this lesson.
Start or resume this lesson
Use the native aibl-chief-of-staff agent to start Week 2 Module 4 Lesson 1. Read course/workforce/week2/prompts/anw-l20.txt and course/workforce/week2/lessons/anw-l20.md. Ask me for my fresh case and my prediction in my own words, and wait. Do not run the fresh job here. If the named agent is unavailable, pause and ask Gigawatt to check the installation.
Choose a case worth checking
Stay with the recurring process you chose in Module 1. Pick a case different from the one you used in Module 3’s guided attempt, with one small task that needs the SOP.
You can choose a different permitted case already in your selected material. You can also use a clearly labeled synthetic practice case, kept separate from real Cairns evidence. You do not need a fourth real process instance or another collection project.
Choose something you can inspect: a readiness check, a proposed next step, or a short plan for a handoff. Preparing that result does not require sending a message, booking a meeting, or completing the whole process.
Run a small job that has to use the SOP. A small one is easier to read. If you choose three tasks and the result is wrong, it becomes harder to see where the problem began.
Use only material you are allowed to process. If the case needs new records, use the same select-and-review steps from Module 2. Do not widen an account search just to give the agent more context.
A fictional client-kickoff example
In our synthetic teaching example, the approved SOP requires a signed brief before kickoff. A new client wants to begin, but the selected case records contain only an unsigned brief.
A useful small task is to check readiness for kickoff. A useful result would say that a signature is not verified in the selected records and identify the next step under the approved procedure. It would not treat the client’s enthusiasm as proof that the brief was signed.
That condition belongs to the fictional example. Choose a condition established by your own evidence and approved SOP for your real case.
Do this now: choose your task
Write one sentence naming the case, the result you want, and why the SOP matters to it.
Choose it yourself before asking The Professor for help. If nothing stands out, think of the last thing your organization gave you that you had to fix by hand. Which part of that check can you ask the organization to prepare for you?
Write down what you expect
Before you run the job, write one sentence about what you expect to see and where you will see it.
For the fictional example: “The readiness check will say that a signature is not verified in the selected records and identify what needs to happen before kickoff.”
Your prediction should be something you can check in the result. “It will do a good job” gives you very little to inspect.
A prediction is how you find out afterwards whether you understood what you were doing. Save your prediction with the date in your course progress note at work/course/staff/progress.md, and don’t edit it later. The Professor can save it for you word for word, but only after you say yes. Save it before Part 3, because the job should not start until your prediction is on record.
Do this now: make your prediction
Write it in your own words. Name one part of the approved SOP you expect the result to follow.
Run one bounded job
The lesson conversation stops once your case and prediction are saved. The job itself runs in a new conversation, so it has to find your SOP on its own, just as in Module 3.
Open a new conversation in the same workbench and paste the Start a fresh job box at the end of this part. Before you send it, replace the three parts in square brackets with your own words: the name of your process, the case you chose described in a sentence (including where its permitted material is), and the output you need. Delete the brackets as you go. Don't give Chief the SOP's path.
As in Module 3, Chief asks Sallee to find the approved SOP through the Cairns index. Don't paste the SOP or the answer you expect: that would hide whether your organization can find what you approved.
Read Chief’s proposed work order and plan before approving the job. It should name the path and version of the SOP Sallee found, the requested result, the material it will use, and the limits of the task. Chief waits for your go; after it, Cipher applies the SOP to your case and Kansa reviews the result. For a readiness check, the job ends with a check for you to inspect.
If Sallee finds no approved SOP for your process, Chief tells you and stops. Nothing goes to Cipher, and you should not paste the SOP in to get past it. Keep the attempt marked as blocked and see If you get stuck below.
If the plan includes an action you did not request, correct it before proceeding. Once the scope is right, give your actual approval and let Chief coordinate the work.
Keep the work order and the returned result. Ask to see the relevant agent return separately from Chief’s summary when you need to inspect what was actually produced.
Do this now: approve and run your chosen task
Make the scope decision yourself. The Professor can explain an unfamiliar part of the work order without choosing the task or approving it for you.
Use the native aibl-chief-of-staff agent for a fresh Week 2 job. Read course/workforce/week2/prompts/anw-l20-fresh-job.txt and follow it. My process is [process name], the case is [one sentence describing the case you chose], and the output I need is [the result you need, such as a readiness check]. Show me the work order with the SOP it found and wait for my go. If the named agent is unavailable, pause and ask Gigawatt to check the installation.
Open the result and look
Every job will tell you it’s done. A report that it’s done isn’t evidence. Open the thing and look: the result and the SOP it cites.
Check three things:
- The procedure: Is this the version you approved, rather than an earlier draft?
- The application: Did the result follow the relevant step, condition, owner, or handoff for this case?
- The evidence: Can you open the case record behind an important claim? Does it support what the result says?
In the fictional example, “the brief is signed” needs evidence of a signature. An email asking to start does not establish that. If the selected records do not show the signature, the result should keep that uncertainty visible.
The opposite case matters too. If the selected evidence contains a signed brief, repeating a generic warning that it is missing would also be wrong. The procedure needs to be applied to the actual case.
Do this now: make one specific judgment
Point to one thing the result got right, got wrong, or could not establish. Say what you opened to check it.
“Something probably improved” is not an answer. “The check said that a signature was not verified in the selected records, and I opened the cited brief to check that claim” is specific enough to inspect.
You don’t have to be certain. You have to be specific. Mark anything you haven’t opened and looked at as not checked. One checked result does not prove the SOP will handle every future case.
Keep the attempt, including what failed
Compare the result with your prediction. Score the prediction close, wrong, or surprised me, and explain why in one sentence. Keep the original wording beside your judgment.
Record whether you needed help and what that help was. Using a cue does not erase the attempt; it tells you what to practice next.
If the result exposed a problem in the SOP, preserve the result and name the problem. Bring any proposed correction back through Chief to Cipher, independent review, and your approval before replacing the approved procedure. Do not quietly edit the SOP to make this attempt look successful.
If you retry after a correction, keep both attempts and identify the version each used.
Do this now: save the actual outcome
Keep your case and task, prediction, SOP version, work order, result, and your judgment together through references in your course progress note at work/course/staff/progress.md. If The Professor helps prepare the note, read its proposed text before approving the save. Open the saved note and check that your words and any unresolved question survived.
If you get stuck
| What you notice | What to try |
|---|---|
| You cannot choose a small task. | Choose one decision at the start of the process, such as whether the next step is ready. Leave the rest for another job. |
| The job ran but did not show whether the SOP helped. | Did the job have to use the SOP? Pick one that must, not one that might. |
| Chief says Sallee found no approved SOP. | Return to the filing and retrieval check in Module 3, Lesson 3, Parts 4 and 5. Keep this attempt marked as blocked until retrieval works. |
| The result cites the SOP but ignores a condition. | Compare that one condition with the actual result and case evidence. Keep the mismatch visible. |
| The necessary case record is missing. | Record what is missing. Collect it only through an approved selection, or leave the decision unresolved. |
| Your prediction was completely wrong. | Keep it and say what surprised you. Do not replace it with what happened. |
| Recording fails, is uncertain, or never worked. | Keep the work you observed and note the gap in your course progress note, or “no recording set up” if tracing never worked. Ask Gigawatt to check it. Do not claim a trace exists that you haven't seen. The job and your judgment don't depend on a recording. |
Before you finish
Check that you have these three things on screen:
- One small task using the same SOP, in a case you picked, with one line explaining why.
- Your prediction, written before the job and unedited, with its score.
- One specific thing the result shows about how the SOP was used, with anything unchecked marked not checked.
You make this judgment yourself. You can explain what you found and name anything still unresolved.
If the job could not run, keep the blocking reason and the next unfinished action. You can reflect on that evidence without claiming a successful independent use.
Words you now own
- Independent attempt: a task you choose and judge yourself.
- Prediction: what you expect before the job runs, kept unchanged afterwards.
- Not checked: something you have not opened and inspected.
- Approved version: the exact SOP you decided was ready to use.
Next: Lesson 2, keep the evidence and name the next need.