Source Code · Architecture · Scheduler · Applications

Classroom OS.

Five days. Four layers. You'll start at the Source Code — what you actually believe about how people learn — and build outward into the Architecture, Scheduler, and live Applications that make a classroom run whether you're in it or not.

See the Schedule For Administrators

Chapter 01

What is Classroom OS?

An operating system is the invisible layer that decides how everything else runs. Most teachers inherit theirs by accident — built from old habits, district mandates, and whatever survived the last in-service. Classroom OS is five working days to rebuild it on purpose, layer by layer: your Source Code (what you actually believe about how people learn), your Architecture (the visible structures that carry it), your Scheduler (the year as a designed arc instead of a pacing guide), and the live Applications — AI Gems, sub plans, OS Overview — that run on top. No theory. No binders. By Friday you'll have built something that works whether you're in the room or not.

Chapter 02

The Five Days

Register for each day separately. Luma doesn't bundle multi-day events, so we run one registration per session to scan you in at the door. Plan to grab all five spots when you sign up.

Day 01 Mon · Jun 1

Empathy

Who are you as a teacher?

Every great classroom runs on the identity of the person who designed it — not their personality, their identity. Today you map what you actually believe about how people learn, draft your Source Code Document, and walk out with the artifact your whole year will be built on.

Most teachers have never been given time to answer the question at the center of their practice: who are you, really, and what do you believe about how people learn? Not the version in your evaluation rubric. The real one. The one that explains why you arrange your room the way you do, why certain lessons light you up and others feel hollow, why some students see you and some never quite do.

This is the day you write that down.

What we do

You'll complete a Circle Map that puts your teaching identity at the center and maps everything that shapes it outward — your influences, your beliefs, your experiences as a learner, the teachers who made you and the ones who didn't. From that map, you'll draft your Source Code Document, the living record of who you are as an educator. You'll also set up your NotebookLM for the first time, the AI that will grow alongside your system all year.

By the end of Day One

A completed Circle Map. The opening section of your Source Code Document. A NotebookLM set up and ready to receive your work. And a crew of four people who already know something true about you.

If a stranger walked into your classroom while you were absent, what would tell them who you are as a teacher?

Reserve Your Spot

Day 02 Tue · Jun 2

Analysis

What does your classroom actually do?

There's always a gap between the teacher you intend to be and the room you actually run. Day Two audits what's already there — procedures, layout, transitions — and starts translating your Source Code into visible architecture that holds without your voice carrying it.

Most classrooms have procedures. What they often lack is architecture: a set of structures that communicate the teacher's values without the teacher having to say them out loud. When a classroom depends on the teacher's voice, energy, and presence to function, it's not running on a system. It's running on a person. That's not sustainable, and it doesn't survive a Tuesday when you're out sick.

Today you'll audit what's already there and start designing what needs to be.

What we do

You'll work with a Bubble Map to analyze your current classroom: what it looks, sounds, and feels like to be in it right now. From there, you'll begin translating your Source Code into visible Architecture — the routines, room layout, norms, and transitions that make your values legible to anyone who walks through the door. Your crew will push your thinking. The chemistry teacher in your group will notice things about your procedures that you stopped seeing years ago.

By the end of Day Two

A completed Bubble Map of your current classroom. A draft procedure set tied directly to your Source Code values. New clarity on exactly which layer of your classroom is strongest and which needs the most work before September.

If you didn't remind them, would your students know what to do?

Reserve Your Spot

Day 03 Wed · Jun 3

Daydreaming

What could your year actually look like?

Most teachers are handed a pacing guide and sent back to their room. Today you design the whole year before it happens: a Flow Map of your curriculum as a sequence of intentional experiences, a working Scheduler, and your first Unit NotebookLM trained on your content and your voice.

The Scheduler is the layer most teachers feel at the mercy of. Content to cover, standards to hit, assessments handed down from above. But within that structure, there is more room for intentional design than most teachers realize. The question is not whether you can control the calendar. It's whether the units you build have a shape, a sequence, and a story that students can feel as they move through them.

Today you map the whole year before it happens.

What we do

You'll complete a Flow Map that traces your curriculum as a sequence of designed experiences, not just topics. From that map, you'll build out your Scheduler: unit flow, scope and sequence, and the key decisions that happen before the year starts rather than in the middle of it. You'll also begin building your Unit NotebookLMs, AI partners trained on your specific content, so that the resources you're creating this week can support your students starting in September.

By the end of Day Three

A completed Flow Map of your full year. A working Scheduler draft. At least one Unit NotebookLM in progress, trained on your content and your voice.

Do your students know where they are in the year and where they are going?

Reserve Your Spot

Day 04 Thu · Jun 4

Prototyping

Build the thing.

No more drafts, no more maps. Today you build a live Google Gem trained on your content and calibrated to your students, then finalize a sub plan that runs your classroom without you in it. By the end of Day Four your ClassroomOS is no longer a concept — it's a functioning thing.

This is the day most PD programs never reach. They talk about systems. They show you frameworks. They hand you a template and call it transformation. The ClassroomOS Bootcamp ends Thursday with something you actually built — something that exists, something you can open on your laptop in August and use.

This is also the day the AI tools go live in the way they were designed to.

What we do

You'll build your Google Gem: a live unit assistant trained on your specific content and calibrated to your students. This Gem will guide students through material, answer questions in your voice, and run independently when you are not in the room. You'll also finalize your sub plan — not as a liability document, but as a proof of concept. If your sub can run your classroom using what you've built this week, your ClassroomOS works.

By the end of Day Four

A live Google Gem ready for student use. A sub plan that runs on your system, not on your presence. A ClassroomOS that is no longer a concept. It is a functioning thing.

If you got a call tonight that you couldn't come in tomorrow, would you feel ready?

Reserve Your Spot

Day 05 Fri · Jun 5

Testing

Does it work without you?

The whole week was built around this question. Your complete ClassroomOS goes up in a Gallery Walk where other crews engage with your Gem, read your sub plan, and stress-test what you built. You'll leave with structured peer feedback, a finished OS Overview, and a classroom that runs whether you're in it or not.

Day Five is not a showcase. It is not a celebration before the real work starts. It is a genuine test: does what you built hold up when someone else looks at it, asks hard questions about it, and tries to imagine running your classroom from it without you?

This is the Gallery Walk. Twelve crews. Every teacher's work on display. And the job of your crew is not to be polite about it.

What we do

Your complete ClassroomOS — Source Code, Architecture, Scheduler, and Applications — goes up in the Gallery Walk. Other crews move through the work, engage with your Gem, read your sub plan, review your OS Overview, and give you structured peer feedback. You'll rotate through other teachers' systems and offer the same. By midday, every teacher in the cohort will have heard from three crews about what is working in their system and what is not ready yet.

By the end of Day Five

Five completed deliverables. A finished OS Overview ready to share. Peer feedback that tells you exactly what your system communicates and what it still needs. And a classroom that does not depend on you being in it to function.

You already know the answer.

Reserve Your Spot

All five mornings · 9:30 AM – 12:30 PM · Legacy High School, North Las Vegas, NV

Chapter 03

For Administrators

Want to see the work in motion? Each day reserves four Admin Observation seats for school and district leaders. You'll sit with the teachers, watch the session run start to finish, and leave with a clearer picture of what your team needs — not a sales deck. Pick the day that fits your calendar above and select the Admin Observation ticket on Luma. Approval required; first come, first served.

Pick a Day to Observe

Bringing a Team? Have a Question?

Group rates, district inquiries, and observer questions — we read every email.

Email The Hoodlums