A Grok lab is a job site. If you do not run it, eighteen chats will run it for you — different jobs, no disclosure, and a printer full of the same fluent paragraph.
Why this matters
Yesterday you wrote a rule. Today you write how the room moves. Integrity that only lives in a syllabus is not integrity. It is a PDF. The period needs a card on the board, a named thread, a clock, a collect, and a fallback when grok.com is slow.
This is also where teachers leak. They demo from a student machine. They project their own long thread, including the answer. They share one class login. They let students upload last year’s key “just to ask a question.” The OS is how you stop that without giving a speech.
The next lesson is the capstone: one complete lesson plus a Grok lab for a real course. This lesson is the operating system that lab will sit on.
Teach
Write a lab card the way you would write a tailboard. Students should be able to start if you are in the hallway.
Lab: [name]
Clock: [start, work, close]
Surface: grok.com (or the school-approved equivalent)
Thread name: [lab] — [their last name]
Open: [file / URL / photo they take]
Send: [the prompt on this card — not a better one they invent unless the job says so]
Submit: [artifact + disclosure card + whatever local proof]
Stop: [what “done” looks like]
Grok may: [one task]
Grok may not: [write the submission, invent a measurement, hide the thread]
Project the card. Do not project your instructor thread.
Clock that fits a 50-minute room
- 0–5: attendance, card, file in the LMS, “name the thread.”
- 5–30: they work. You walk. You do not re-lecture.
- 30–40: pair compare, or you sample two orals.
- 40–50: disclosure card, submit, one line they still have not checked.
If the work block is less than twenty minutes, the job is too big or the start is too sloppy. Cut the job.
Accounts and surfaces. One student, one account they can find tomorrow. No shared class Grok. School SSO if you have it. Phone is the wrong surface for a typed lab unless the job is a photo of something in the room. Grok on X is not a classroom. If the district blocks grok.com, this OS still holds — write the approved surface on the card, or run the offline fallback. Do not surprise them at minute three.
Instructor desk. A separate thread named instructor — [lab]. You design there. You draft comments there. You do not paste a roster. When you demo, open a fresh student-shaped thread and stay inside the lab card. If you need to show a mistake, show a mistake you planted, not a student’s live work on the projector.
Files. They attach what the card names: the class PNG, the one-page PDF, a photo they just took. They do not attach your unpublished key, another student’s paper, or a full novel. If the file has student names, you stripped them before the period.
Modes. Fast for format and critique of a draft they already wrote. Think if the card asks them to find a hole in a plan. Search only when the card says the world may have moved — and then they must open the source. Imagine only if the artifact is a diagram the card asked for. Default is: fewer toys, same job.
Collect. The LMS drop (or the folder you actually use) gets: the artifact, the disclosure card, and the local proof (screenshot, photo, quote). A paste of Grok with no card is incomplete, not late-but-fine.
Offline fallback. Same job, no model. Paper card. They still point at the feature. They still write three questions. If the network dies, you do not cancel learning. You cancel the Grok step and keep the proof.
Noise and equity. Headphones if voice is in play (it usually should not be, in a typed lab). A printed card for anyone who cannot see the board. A student without an account works the offline path that day — you do not pair them onto someone else’s login.
Weekly OS, not a one-off stunt. Same thread-naming rule every lab. Same disclosure card. Same place artifacts go. The first lab is slow. The fourth is a habit. If you change the rules every Thursday, students will hear “whatever.”
What you watch while you walk. Threads named wrong. Two students with the same prose in the first four lines. A disclosure that says “no Grok” on a paragraph that names a fact not in the file. You do not need software for that. You need to read two submissions in the room.
Privacy again, because the room is where it breaks. Do not ask them to paste home addresses, IEPs, or medical notes. Do not put your gradebook in the chat. If a student pastes something they should not, you stop, you delete what you can, you do not scold them on the projector.
Worked example
Thursday, 16 lab PCs, grok.com allowed, one PNG in the LMS.
The instructor prints the lab card and puts it on the board. Thread name: drainage lab — [name]. Open: the class PNG only. Send: the prompt printed on the card (job, three questions, no acres, then ask Grok to attack their questions). Submit to the LMS: 10-line card, PNG with their three arrows, disclosure. Grok may critique their questions. Grok may not write the three questions first.
At minute six a student asks for “a better prompt.” The instructor points at the card. At minute eighteen two screens show the same slough sentence word for word. The instructor does not accuse. He asks both for the disclosure and for the arrow on the PNG. One student has no arrow. That is a rubric zero on local feature, today, in the room — not a later email.
At minute forty-one the network hiccups. Three students lose the tab. The fallback is already on the back of the card: write the three questions on paper from the projected PNG; disclosure = “Grok used: no — network.” They still submit.
After class the instructor opens instructor — drainage lab, pastes one anonymized 10-line card, and asks Grok only: “Which line claims a measurement that is not in the PNG?” He uses that to prep two oral questions for Friday. He does not ask Grok to assign the grade.
Your turn
Open grok.com. New thread named lab OS — [room or course]. Grok will interview you about a room that exists, then write the OS. If you teach online, the “room” is the LMS + the clock you actually hold.
Exercise d-edu-l03-e1
| Field | Value |
|---|
| whereToDo | grok.com |
| time | 20 min |
Copy-ready prompt
I am in Grok Mastery (Russell Tech), Pathway D, Education, lesson 3 — classroom lab OS.
Interview me with exactly seven short questions, one at a time:
1) Room or LMS, and how many students
2) Exact minutes
3) Which surface they will open (grok.com, another approved tool, or offline only)
4) The one file or object they may use
5) The one task Grok may do
6) Where they submit, and what three pieces I will collect
7) What I will do if the network dies
Then write a Classroom Lab OS with exactly these parts:
- Lab card (the tailboard shape: lab, clock, surface, thread name, open, send, submit, stop, may, may not)
- Instructor desk rule (one paragraph)
- Walk-the-room checks (three)
- Offline fallback (five lines)
- Privacy / do-not-paste list (five bullets)
- Session stamp: today's date and "Lab OS written by Grok in this thread."
Do not invent a projector, a 1:1 laptop cart, or a district license I did not give.
If I said the network is unreliable, the fallback must be runnable.
Artifact to paste
- The Classroom Lab OS (all parts, including the stamp).
- Your answers to the seven questions (short).
- One line from you: the walk-the-room check you will actually do first.
Rubric
- Pass: OS is Grok-authored and stamped. Lab card has a numbered clock, a named surface, a may / may not, and a collect of at least artifact + disclosure. Fallback does not require Grok. No invented cart. Room is real.
- Fail: A philosophy of “blended learning” with no card. You wrote the OS without Grok. Shared class login as the plan. Fallback is “we’ll try again next week.” No disclosure in the collect.
Common failure
The common failure is demo as answer key. You walk the whole lab on the projector, including the “good” Grok reply, then ask them to do it. You just ran a transcription period.
The other failure is one login on the instructor laptop passed around the room. You now have no authorship, a credential on eighteen desks, and a thread you cannot attribute. Issue accounts or run offline. There is not a third option.
What’s next
You have a skeleton, an integrity pack, and a room OS. Capstone: one complete lesson plus a Grok lab for a course that exists — assembled so you could teach it Monday.
