Kids love it. Teachers run it. Glowing fleets, snap-code, AI-assisted claims on vanilla boards, then lock the company so even AI fails. 7 labs. Free gift: 1 board per student for each lab. One day each.
Boards stay vanilla WLED through labs 01–06 so the take is real. Crypto Ops is last.
The blast: play → code → AI owns the room → build → threat → economics → crypto last (AI fails). Vanilla until then.
01
K–5
Light Explorers Lab
Classroom space play — teams command glowing fleets, sync formations, invent missions. No lectures about protocols. The lights answer instantly when someone taps, so kids feel cause-and-effect in their bodies before they ever hear the word “network.”
Under the play: every board is a node. A shared strip that reacts together is a tiny LAN. Color becomes information (calm / alert / “dock here”). Pattern becomes language. When one table’s fleet copies another, they’ve done peer coordination without knowing the jargon. That gut model — “many lights, one room, signals travel” — is what Galaxy and local control build on later.
They learn
observation + prediction (what will the lights do?)
color as signal · pattern as story · turn-taking on a shared device
nodes in a room = early mental model of a network
1 free board per student · 1 day
02
6–8
First Code Lab
Snap blocks — color, chase, speed, react. No blank editor. The “program” isn’t a grade on a screen; it’s photons on a strip they already trust from Explorers. Wrong stack? Wrong light. Debug with eyes.
This is where software becomes real. Sequences → state over time. Loops → a chase that never stops until you change it. Variables → speed, direction, trail length. A reactive flash teaches event-driven thinking: something happens → the device answers. They’re not typing syntax; they’re learning that firmware runs a pipeline of instructions on hardware — the same idea as open WLED effects, just with training wheels.
They learn
sequences, loops, variables, timing — by watching LEDs
event → response (tap / sensor → flash)
debug by comparing intent vs what the strip shows
power intuition: full white is “expensive” electricity
1 free board per student · 1 day
03
9–10
Network Lab
Not a lecture on SSID. Ask an AI how to find every board on the classroom Wi‑Fi — then do it. Name yours. Take a classmate’s show. Put a calling card in their pattern. It is trivial on vanilla WLED: open UI, same LAN, AI writes the steps. Diagram what just happened: phone → AP → board. Unplug the internet — you can still own the room. That’s the lesson.
Galaxy makes discovery and local control honest. “Smart” toys hide the path behind a company cloud; kids never see how easy the take is. Here the path is the classroom. AI assistance collapses the skill gap — you don’t need to be a “hacker,” you need a prompt and a network. Direct is fast. Relay exists when firewalls block. Offline doesn’t save you if the attacker is on your AP. They write: what made the claim so easy, and what would have to change for AI to fail.
They learn
AI-assisted claim: find → name → take a peer’s board (trivial on vanilla)
LAN discovery · open UI · same AP = shared attack surface
latency & path: local smash vs cloud round-trip
internet down ≠ safe — local attackers still win
1 free board per student · 1 day · see also Galaxy
04
9–11
IoT Lab
Open the box. Power, strips, pins, connectors on the education board. Load the patterns they wrote in First Code onto hardware they can point at. Graduates don’t say “the Wi‑Fi broke” — they can point at the wire.
Software lies if the physics is wrong. Full white across many LEDs pulls current; brownouts look like “bugs.” A loose joint flickers like a haunted effect. The board is the brain; the strip is the body; the phone is just a remote. Kids learn the stack from the bottom: electricity → MCU → firmware → network → app. Firmware stays vanilla WLED here — open, claimable — so Threat Lab later isn’t fake. The attack surface sits on real pins and real power.
They learn
safe wiring · power budget · why “max white” overheats / browns out
MCU as brain · strip as actuators · app as remote
troubleshoot layer by layer (power → data → Wi‑Fi → app)
open firmware mindset: the code on the chip is inspectable
1 free board per student · 1 day
05
11–12
Threat Lab
Rules of engagement first: classroom only, no outside networks, write everything down. Network Lab already proved AI + vanilla = trivial take. Now go further: red-team peer projects, map the full attack surface, spoof identity, leave a calling card, brief findings like a short SOC note.
Boards stay vanilla WLED until Crypto Ops — on purpose. Network Lab was the shock (“that was easy”). Threat Lab is the discipline: assets, actors, entry points, impact — on real open firmware. Defense by attacking safely. The lock still waits until after Economics.
They learn
vanilla WLED = open by default · easy classroom claim
rules of engagement + write-it-down incident response
why a password sticker still isn’t ownership
1 free board per student · 1 day · see also Security / Threats
06
11–12
Internet Economics Lab
“Johnny took my company.” Seminar-style while boards are still vanilla and claimable. Breach and IP-theft cases. Map who lost money. Argue who owned what. Write a board memo. Security isn’t a vibe — it’s whether you still have a company on Monday.
Threat Lab showed how control is lost on open IoT. Economics prices it before they lock anything: stolen IP, drained customer lists, counterfeit gear, accounts that were only a database row. If ownership is someone else’s spreadsheet, Johnny can take the company. The next lab is the fix — on purpose last, so the cost lands first.
They learn
IP theft · data breach · who bears the cost
ownership as economic fact (database row vs device proof)
postmortems as board memos — write for decision-makers
why locking the fleet waits until after you’ve felt the loss
1 free board per student · 1 day · still vanilla WLED
07
last
Crypto Ops Lab
Last lab. Network Lab proved AI + vanilla WLED = trivial take. Now lock the company. Ownership proofs, keys, signatures. Same AI, same classmates, same prompts — even AI cannot hack their company once the board only answers to math it can verify.
Identity lives on the device (private key never leaves). Public key is the name tag. Signatures prove command / firmware / pack. The AI that walked them through claiming open boards now fails: no proof, no control. Nexus’s promise — your data stays yours — becomes the punchline after years of open fleets. Graduation: played, built, claimed with AI, priced the damage, then locked so Johnny’s chatbot can’t walk in.
They learn
same AI that owned vanilla — now fails against ownership proofs
public / private keys · what verify() actually promises
signed firmware / packs — reject the unsigned
“even AI cannot hack their company” — math over prompts
1 free board per student · 1 day · see also Nexus / Security