Glitch Control Slides System: Active
v2.0.26
Disappointment Regulation Protocol
Level 1: Emotional Debugging
GLITCH CONTROL
How to debug disappointed feelings, override system errors, and successfully reboot your system.
Status: Calibration Complete
WARNING
SYSTEM GLITCH DETECTED
Disappointment = A Glitch
What is a Glitch?
In a video game, a glitch is an unexpected error that stops you from moving forward temporarily.
In real life, disappointment feels exactly like that! It happens when things don't go the way you planned.
IMPORTANT MEMORY DATA:
A glitch is NOT a "Game Over." It just means we need a debug protocol!
ERROR CODE: 404_PLANS_CHANGED
Common Real-Life Glitches:
Rain cancels outdoor recess plans.
Losing a game you practiced hard to win.
Your favorite snack is completely sold out.
Screen 2 of 6 • Press space or click next to continue
PROTOCOL 01
SOMATIC REGULATION: HARDWARE CALIBRATION
Cool Down the Engine
The Breathe-In Debug
Slow down physical processors
When we feel disappointed, our hardware (our body) heats up. Heart racing, tight chest, or clenching fists.
Inhale (Fill the Battery) for 4s
Hold (Save Game State) for 4s
Exhale (Release Heat) for 6s
The 5-Step Grounding Scan
Reconnect to the current level
Look around your room to reset your visual trackers and ground your hardware:
5 Objects See
4 Things Feel
3 Sounds Hear
2 Smells Sense
1 Taste Identify
Screen 3 of 6 • Press space or click next to continue
PROTOCOL 02
SYSTEM OVERRIDE: ACCEPTANCE & EXPRESSION
Process & Clear Log Files
Write the "Acceptance Code"
Trying to ignore disappointment causes background programs to freeze. We have to acknowledge the glitch first to bypass it.
INPUT SYSTEM CODE:
"I wanted [Original Plan] to happen, and I feel disappointed. That's okay. I can handle this."
Expressing Safe Output
Once acknowledged, clear the emotional RAM using these healthy expression modes:
Visual Draw
Scribble or draw how the disappointment feels.
Verbal Code
Tell someone, "I am venting because I'm disappointed."
Action Burn
Do jumping jacks or run in place to expend heat.
Squeeze Test
Squeeze a stress ball or pillow tightly and release.
Screen 4 of 6 • Press space or click next to continue
MISSION QUEST
SCENARIO: THE SAVED DATA GLITCH
Choose Your Action Code
SCENARIO LOG
You spent three recesses building an amazing Lego spacecraft with your classmate. On Friday afternoon, someone accidentally knocks it off the shelf, and it shatters completely. Recess is over, and it's time to pack up.
Emotional HP: 20%
System running hot. Initiate protocol!
WHICH PROTOCOL DO YOU RUN?
A
Rage Shutdown Protocol
Yell at the classmate, kick the pieces, and refuse to clean up.
Option A
B
Somatic Debug & Override
Take 3 "Breathe-In Debugs", accept the change, and plan a rebuild next week.
Option B
C
System Freeze Protocol
Pretend nothing happened, hold the anger inside, and let it freeze your system.
Option C
Screen 5 of 6 • Press space or click next to continue
REBOOT COMPLETE
SYSTEM OVERRIDE CHECKLIST
Ready to Load Level 2
Classroom Quest Debrief
Let's talk about our current system status as a team. Pick a prompt to share:
What is a recent real-life "glitch" you experienced and how did your hardware feel?
Which debugging protocol do you think is easiest for your brain to initiate?
GLITCH_CONTROL.EXE
SYSTEM STABLE
We accept that glitches happen to everyone.
We use somatic breathing to cool the engine.
We express the error safely and press reboot !
YOU ARE READY TO REPLAY!
Screen 6 of 6 • Reboot successful • End of Mission
Glitch Control Narrative System: Narrative_Mode.EXE
Level 01: Core Story
The Disappointment Guide
Alex's Arcade Glitch
A Social Narrative for Turning Hard Moments into Successful Reboots
Alex loved playing games. Whether building a complex block tower, playing kickball, or drawing an amazing dragon, Alex loved to finish what they started. But today, a system glitch happened. During recess, another student bumped into their tall block castle, and it shattered across the floor.
Alex felt their internal hardware start to overheat. Their chest felt tight, their cheeks felt hot, and their fists clenched up tight. In their mind, a big red flashing light read: GAME OVER! NO REPLAY! Alex wanted to yell, throw the remaining blocks, and cry. The disappointment felt like a frozen system screen.
Then, Alex remembered the Glitch Control Blueprint . A glitch isn't a permanent error; it is just a temporary interruption. Instead of shutting down, Alex ran Somatic Debug Protocol 01 . They took a deep breathe-in for four seconds, held it, and exhaled slowly. They looked around and named five blue blocks they could see to ground their system.
Next, they used System Override Protocol 02 . Alex said to themselves, "I am disappointed the blocks fell. It stinks. But I can handle this." They decided to spend the last two minutes of recess scribbling with a blue marker on a scratch paper, using creative design to release the leftover energy.
ALEX'S BLUEPRINT CODE
Alex realized that disappointments are a natural part of every game. When a plan glitches, we don't smash the controller. We pause, cool our internal hardware, and reload the game when we are ready.
Unit: Emotional Debugging Page 1 of 2
Diagnostic: Input_Sheet.EXE
Level 02: Student Quest
MY GLITCH LOG
Fill out your system diagnostic to prepare for your next real-life glitch!
NAME:
DATE:
STEP 1 Hardware Alert: How does disappointment feel in my body? (Check all that apply)
Hot cheeks / Face flush Fast heartbeat Clenched hands / Fists Tears / Crying threat Tight tummy or chest Silent / Freezing cold
STEP 2 Visual Output: Draw how your disappointing glitch looks as an active video game monster!
STEP 3 Override Code: Plan your reboot statement. Fill in the blanks.
When my plans glitch and I cannot have / do
, I will run my diagnostic.
I will take
deep breathes, cool my hardware down, and say to myself:
Form: GLITCH_DIAG_01 Page 2 of 2
Glitch Control Debug Cards GLITCH CONTROL COPING CARDS
Cut out these cards, laminate them, and keep them on your desk or keychain for in-the-moment support!
POCKET DEBUGGERS
CARD 01 // SOMATIC
BREATHE-IN DEBUG
Cool Down Physical Hardware
When disappointment triggers a red alert (racing heart, heat in face), execute this thermal cooling breath sequence:
1
Inhale (Charge Battery) : Breathe in deep for 4 seconds.
2
Hold (Save State) : Keep the cool air in for 4 seconds.
3
Exhale (Vent Heat) : Blow out slowly for 6 seconds.
REPEAT 3X TO RESTORE NORMAL OPERATION
CARD 02 // GROUNDING
5-STEP RADAR SCAN
Re-anchor to Current Level
If your brain freezes on what you lost, look around your screen to calibrate your local environment trackers:
5 See
4 Touch
3 Hear
2 Smell
1 Taste
Slowing down to notice five small elements in your immediate space triggers an automatic reboot process.
HARDWARE TRACKERS SUCCESSFULLY STABILIZED
CARD 03 // COGNITIVE
ACCEPTANCE OVERRIDE
Acknowledge & Clear the Logs
Trying to force-quit hard feelings makes them consume more background RAM. Use this self-talk script to override:
Execute Script:
"It stinks that things didn't go the way I wanted. I am feeling disappointed right now, and that is completely okay. This is just a temporary glitch. I can handle it!"
SYSTEM BYPASS ENGAGED // RESET ENABLED
CARD 04 // EXPRESSION
SAFE EXPRESS MODE
Divert Internal Static Energy
Disappointment generates a physical static charge in your body. Divert it safely into these expression pathways:
Scribble Draw : Draw it out.
Talk Code : Vent to a peer.
Action Burn : Run or jump.
Squeeze : Stress toy test.
STATIC CHARGE SUCCESSFULLY DISCHARGED
READY FOR POCKET ASSEMBLY // RETRO-COPING CORP.
Page 1 of 1
