|
| 1 | +# Lesson 01 facilitator guide: Node and the coding harness |
| 2 | + |
| 3 | +## Outcome |
| 4 | + |
| 5 | +At the end of 60 minutes, each learner should be able to sketch the CookieMonster system from memory and answer: |
| 6 | + |
| 7 | +1. What is executing the code? |
| 8 | +2. What folder and context can the harness access? |
| 9 | +3. What tools and permissions does the agent have? |
| 10 | +4. What evidence will prove the task is complete? |
| 11 | + |
| 12 | +They do not need to write JavaScript. |
| 13 | + |
| 14 | +## Preparation |
| 15 | + |
| 16 | +- Open `lesson-01-node-and-the-coding-harness.html` in a browser. |
| 17 | +- Have CookieMonster available for a live demonstration. |
| 18 | +- Create a disposable folder containing two or three harmless text files, or use a copy of a non-sensitive creative project. |
| 19 | +- Confirm the organization’s rules for client data before showing a real project. |
| 20 | + |
| 21 | +## Run of show |
| 22 | + |
| 23 | +### 0–5 min — Reset the framing |
| 24 | + |
| 25 | +Ask: “When you type a request into CookieMonster, what actually does the work?” Collect answers without correcting them yet. |
| 26 | + |
| 27 | +State the lesson promise: they will leave able to see the machinery, choose the safe mode, and detect when the agent has not really finished. |
| 28 | + |
| 29 | +### 5–18 min — JavaScript, Node.js, and Bun |
| 30 | + |
| 31 | +Use the After Effects analogy: |
| 32 | + |
| 33 | +- An expression is instructions; After Effects is the application that interprets and executes them. |
| 34 | +- A `.js` file is instructions; a JavaScript runtime executes them. |
| 35 | +- A browser contains a runtime with browser abilities. |
| 36 | +- Node.js is a runtime outside the browser with operating-system abilities such as files and networking. |
| 37 | +- CookieMonster’s repository primarily uses Bun, a Node.js-compatible runtime and toolkit. The conceptual model transfers, but the command used here is often `bun`, not `node` or `npm`. |
| 38 | + |
| 39 | +Where the analogy stops: Node.js is not a visual application, timeline, renderer, or permanent background service. A Node process begins, does work, and either keeps running or exits. |
| 40 | + |
| 41 | +Show the root `package.json`, but only point out: |
| 42 | + |
| 43 | +- `packageManager`: which toolkit this project expects; |
| 44 | +- `scripts`: named project actions; |
| 45 | +- `dependencies`: reusable packages the project needs. |
| 46 | + |
| 47 | +Do not explain JSON syntax yet. |
| 48 | + |
| 49 | +### 18–33 min — The harness |
| 50 | + |
| 51 | +Define the coding harness as the working system around the model. It assembles context, gives the model tools, enforces permissions, runs actions, captures results, and maintains the session. |
| 52 | + |
| 53 | +Use the studio analogy: |
| 54 | + |
| 55 | +- model = creative problem-solver; |
| 56 | +- harness = producer plus production desk; |
| 57 | +- project folder = the job folder; |
| 58 | +- tools = departments and equipment; |
| 59 | +- permissions = approval gates; |
| 60 | +- tests, previews, and diffs = QC; |
| 61 | +- session = the job’s working conversation and activity history. |
| 62 | + |
| 63 | +Where the analogy stops: the model and harness are software components, not accountable human specialists. The user remains responsible for the brief, approvals, and final judgement. |
| 64 | + |
| 65 | +### 33–43 min — Map CookieMonster |
| 66 | + |
| 67 | +Walk left to right through the system map in the lesson: |
| 68 | + |
| 69 | +1. The designer supplies intent and selects a project folder. |
| 70 | +2. CookieMonster/OpenCode manages the session, rules, context, tools, and permissions. |
| 71 | +3. The WPP-hosted model decides the next useful step from the context it receives. |
| 72 | +4. Local tools inspect or change the project and return evidence. |
| 73 | +5. The harness repeats the loop until it reports an outcome or needs a decision. |
| 74 | + |
| 75 | +Emphasize: the model does not directly possess a folder, terminal, or magic view of the whole computer. The harness mediates those capabilities. |
| 76 | + |
| 77 | +### 43–53 min — Safe live demonstration |
| 78 | + |
| 79 | +Open a disposable folder in CookieMonster. Start in Plan and use: |
| 80 | + |
| 81 | +> Without changing anything, inspect this folder. Explain what is here, what you still do not know, and propose one small useful change. Cite the files you used as evidence. |
| 82 | +
|
| 83 | +Ask the room to identify the objective, scope, mode, tools, and evidence. |
| 84 | + |
| 85 | +Then switch intentionally to Build and use: |
| 86 | + |
| 87 | +> Create `handoff-notes.md`. Summarize the folder in five bullets, add a section called “Questions”, and do not change any existing file. Afterward, list exactly what changed. |
| 88 | +
|
| 89 | +Review the file and change summary. The success is not that the agent said “done”; the success is that the requested artifact exists, is in scope, and matches the acceptance criteria. |
| 90 | + |
| 91 | +### 53–60 min — Quiz and debrief |
| 92 | + |
| 93 | +Use the interactive check in the lesson. Then ask each learner to finish this sentence: |
| 94 | + |
| 95 | +> CookieMonster can act on a project because the harness… |
| 96 | +
|
| 97 | +Do not add terms to `GLOSSARY.md` until learners can explain them without reading the lesson. |
| 98 | + |
| 99 | +## Misconceptions to catch |
| 100 | + |
| 101 | +- “Node is JavaScript.” JavaScript is the language; Node.js is one runtime that executes it. |
| 102 | +- “The terminal is Node.” The terminal launches commands; Node or Bun may be one of the programs it launches. |
| 103 | +- “CookieMonster is the model.” CookieMonster is the desktop harness; the model is one component behind it. |
| 104 | +- “The model sees my computer.” It receives selected context and tool results through the harness. |
| 105 | +- “A confident final message proves the work.” Completion requires external evidence: changed files, a diff, a test, a preview, or another observable result. |
| 106 | +- “Plan can never act.” Treat Plan as the analysis-first mode and still read any approval prompt; exact permissions can be configured. |
| 107 | + |
| 108 | +## Assessment rubric |
| 109 | + |
| 110 | +Ready for module 2: |
| 111 | + |
| 112 | +- Correctly places runtime, model, harness, tools, and project folder on the map. |
| 113 | +- Can explain why selecting the wrong folder changes the task’s scope. |
| 114 | +- Uses Plan for uncertain exploration and Build only when an edit is intended. |
| 115 | +- Names an appropriate verification method before accepting “done.” |
| 116 | + |
| 117 | +Needs another pass: |
| 118 | + |
| 119 | +- Treats CookieMonster as an all-seeing chatbot. |
| 120 | +- Cannot distinguish the terminal, runtime, model, and harness. |
| 121 | +- Accepts prose as proof of a file or visual change. |
| 122 | +- Cannot state which folder is in scope. |
0 commit comments