By morning, The Old Stack sounded tired.
Fans ran in rooms that had no classes. Queue lights blinked over empty desks. A lesson printer coughed out the same blank header six times.
“Nothing is broken,” Pixel said.
Shadow pointed at a classroom door. A line of younger students waited outside while their teacher held a frozen lesson card.
Whiskers shook his head. “Waiting is impact.”
Delay In The Hallway
The drop arrived on the stalled printer.
HARM CAN LOOK LIKE DELAY.
Byte read it once, then folded the paper into his notebook.
The Copycat Sprite had not smashed a window. It had pushed resource counters upward, occupied process slots, and made simple tools take too long. Each extra copy took a running slot from a room. Each high counter made a queue wait. Each waiting queue pulled a caretaker away from normal work. The city still stood. The work did not move.
Ms. Vale opened a response form.
“Affected users,” she said. “Name the people first.”
People First On The Form
Shadow walked the hall and called out room states.
“Room three: fan active, no class. Room four: printer queue stuck, process slots full. Room five: two markers, resource counter rising, light warm. Room six: students waiting.”
Jinx logged each one. Cipher added counts. Grimalkin drew doors between rooms.
Ms. Vale added a second list beside Jinx’s: affected class tools, delayed lessons, caretaker time, and rooms held out of service. No files were gone. That did not make the incident harmless.
Byte tried to help everywhere at once and helped nowhere for three minutes.
Whiskers put a paw on his shoulder.
“One lane,” Whiskers said.
Byte swallowed. “Counters.”
“Good. Own counters.”
The Lower Hall Waits
The team did not clear anything yet. They measured first.
That was hard for Pixel. That was harder for Byte.
The map grew: Ledger Lab, old terminal, three rooms, two queues, one printer, one class waiting for tools.
Shadow came back with dust on his sleeves. “There is a lower hallway. More old rooms.”
Grimalkin drew a line under the current map.
“Contain here,” he said. “Then look lower.”
The Copycat Sprite glowed on six screens, cute as a sticker and heavy as a traffic jam.
Teaching Tie-In
- Concept: security impact can be delay, downtime, resource pressure, and diverted work.
- Story idea: the Copycat Sprite matters because ordinary students lose time and tools.
- Key distinction: an incident can harm people without destroying files.
- Defensive habit: name affected users and scope before cleanup.
- Season thread: the Copycat Sprite becomes a city response problem.
- Field Guide habit: Know what you protect.
Behind the Signal
The Morris Worm is often remembered as a non-destructive incident, but non-destructive does not mean harmless. Contemporary and later accounts describe machines slowing, systems halting, administrators disconnecting networks, and people spending emergency time trying to understand and recover. The work stopped even where files survived, and that distinction is one reason the event changed how people thought about network risk.
The slow rooms translate that history into a human-scale classroom problem. A frozen lesson card and waiting students make resource exhaustion and downtime feel concrete without technical overload. The episode’s point is the same one defenders learned in 1988: impact can look like delay, lost time, unavailable tools, and people pulled away from ordinary work.
~BL4CK4T