Trigger Trackers Slides Deck 01 // INITIALIZING_SYSTEM
02 import { Awareness } from 'mindset'
03 function trackTriggers() { ... }
<body>
</html>
> WEEK 3 TRAINING
Trigger Trackers
"Finding the specific wires that trip your alarm."
The Big Three "Wires"
Academic
Tests, grades, speaking in class, or feeling confused during a lesson.
class_logic_check
Social
Friend drama, lunch groups, social media, or small talk.
network_error_scan
Everyday
Loud halls, lack of sleep, changes in routine, or sensory input.
system_load_check
The Wire is NOT the Fire
Just because something trips your alarm doesn't mean you are in actual danger.
if (alarmTriggers == true) { checkSafety(); }
DEBUG_SCENARIO // 01
Case Study: Jordan
LIVE_SESSION
"Jordan walks into the cafeteria. It's loud, all the tables look full, and he realizes he forgot his lunch money. Suddenly, his heart starts racing and he feels dizzy."
Identifying Wires
Noise (Sensory)
Crowd (Social)
Change (Everyday)
DEBUG_SCENARIO // 02
Case Study: Maya
LIVE_SESSION
"Maya's teacher announces a surprise pop quiz on the chapter they just finished. Maya hasn't studied yet. As the papers are handed out, her hands start to shake and her mind goes completely blank."
Identifying Wires
Surprise (Everyday)
Pressure (Academic)
Failure (Academic)
DEBUG_SCENARIO // 03
Case Study: Leo
LIVE_SESSION
"Leo is trying to read in the library. A student at the next table is tapping their pen rhythmically against the wood. Leo feels his skin crawl and he suddenly wants to shout at them to stop."
Identifying Wires
Sound (Sensory)
Interruption (Everyday)
Strain (Academic)
DEBUG_SCENARIO // 04
Case Study: Sam
LIVE_SESSION
"Sam walks toward a group of friends who are laughing. As she gets closer, they stop talking and look at each other. Sam immediately feels a pit in her stomach and wonders if they were talking about her."
Identifying Wires
Drama (Social)
Exclusion (Social)
Judged (Social)
Session Complete
"Your alarm isn't broken—it's just sensitive. Identifying the 'wires' is the first step to mastering the system."
Next Step
Capture_Buffer: START
Remember
status_stable_verified
> SYSTEM_HALT ... SUCCESS
Final Reflection Exit Ticket Exit Ticket: System Audit
STATUS: COMPLETE
User_ID:
Date:
CMD_01 One tool I will continue using is:
CMD_02 One situation I will use it in is:
CMD_03 One thing I learned about myself is:
// Saving deployment configuration... V1.0_REFLECT
Cut Here
Exit Ticket: System Audit
STATUS: COMPLETE
User_ID:
Date:
CMD_01 One tool I will continue using is:
CMD_02 One situation I will use it in is:
CMD_03 One thing I learned about myself is:
// Saving deployment configuration... V1.0_REFLECT
Maintenance Plan Worksheet System_Console_v2.5 // Maintenance_Protocol
Security: Active
System Maintenance
Final Performance Optimization Plan
Lead Architect:
Status Date:
Critical Wires
Identify your top 3 triggers (Academic, Social, or Everyday)
Sensor Diagnostics
Primary Alert: What lights up first?
System-Wide Log: Where else do sensors go off?
Scan Mode: Full Body Detection: High Priority
Debug Glitches
Check for Known Glitches:
Spotlight Glitch
Mind-Reading Hack
System Crash Glitch
Social Antenna
Debugging Practice
Diagnostic_Active
System Upgrades
Grounding Scan
5-4-3-2-1 tech.
Core Cooling
Square breath.
Code Update
Logic Reframing.
Hardware Release
Physical Soften.
Custom Patches (Your Skills)
Architect's Commitment
"I promise to scan my sensors and run my tools to keep my system optimized."
Authorized Signature
Level: Chief Architect
Verified Status
ID: maintenance-plan
Social Signals Slides Deck 01 // SOCIAL_INTERFACE_INIT
02 import { Connectivity } from 'network'
03 function manageSignals() { ... }
04 // LEVEL_7_UNLOCKED
<protocol: handshake>
<status: connecting...>
> WEEK 7 TRAINING
Social Signals
"Your brain is already a supercomputer. Today we’re adding new apps so you have more options in social situations."
The Architect's Key
Hardware Physical Body
Software Thoughts & Mind
Sensors Physical Feelings
Bugs Social Triggers
Glitches Untrue Thoughts
Debugging Finding the Facts
> system_interface_ready
The Spotlight Glitch
Error_Log
"Every single person is watching me and judging every mistake I make."
Patch_Update
"Most people are so busy with their own thoughts that they rarely notice yours."
while(is_present == true) { anxiety++; }
FILTER_ACTIVE
System Crash Glitch
FATAL_OVERFLOW
"A small input error that you treat like a total hardware failure."
RECOVERY_MODE
"I missed one word in my speech, but my system is still 99% functional."
Rebooting...
Debugging Practice
> INPUT_EVENT
"You get called on in class and don’t know the answer."
> GLITCH_THOUGHT
“I’m going to look stupid. Everyone is going to think I don’t get it.”
Which glitch is being triggered?
Spotlight Glitch
System Crash Glitch
Mind-Reading Hack
SECURITY_BREACH
"Attempting to bypass security to read private variables in someone else's code."
FIREWALL_ACTIVE
"I can't access their internal thoughts. I only have my own sensory data."
> ACCESS_DENIED
Social Antenna
Static
"Expecting the worst. They must be mad at me."
Tuning
"Pausing to check the facts before you react."
Clear
"Finding the truth. They're just busy with their own stuff."
Master Protocol
01
Cooling
Hardware Fix
02
Reset
System Reboot
03
Chief Architect Slides Deck > RUN system_init.sh
0xFF // MEMORY_COMMIT
Week 8 Training
Chief
Architect
A lifelong plan for high-performance processing.
System Tool Library
Available Protocols
System Reset
"The Anchor"
Use 5-4-3-2-1 when your processor is time-traveling.
Core Cooling
"The Bio-Hack"
Use Square Breathing when you feel "overheat."
Debugging
"The Logic Update"
Use Reframing when you catch a "glitch" thought.
Hardware Release
"The System Soften"
Use Progressive Soften to release tension.
System Glitches
Common Software Errors Detected
Spotlight Glitch
BUG_01
System falsely reports everyone is watching and judging your performance.
Mind-Reading Hack
BUG_02
Unauthorized access attempt to predict others' thoughts about you.
System Crash Glitch
BUG_03
Critical failure where thoughts spiral and processor freezes during stress.
Social Antenna
"Tune your sensors to the right frequency. Don't let feedback loops distort the signal."
Debugging Practice
Scan for glitches every day.
Identify the bug type immediately.
Run a reframe upgrade script.
while (active) {
Maintenance is Daily
"A system needs maintenance even when it's running smooth. Your processor needs tools even when there are no alerts."
The more you practice,
Daily Log-ins
Active Debugging
Continuous Support
Future Protocol Reminders
Booster Sessions
"We will reach out to remind you about our upcoming Booster Sessions."
System Help
"Need a manual override? You can always come meet with us if you need support."
System Mastery
You are now the Chief Systems Architect of your own mind.
Keep Building.
ARCHITECT_ID: #MASTER_V1 // STATUS: CERTIFIED
Skill Rating Worksheet 01 // DIAGNOSTIC_REPORT
Performance_Analytics_v1.0
Skill Rating Worksheet
Build Lab Diagnostic Report
Coder Name:
Session Date:
Rater:
Student
Teacher
Rating Legend:
1 RARELY
2 SOMETIMES
3 OFTEN
4 INDEPENDENTLY
Core Performance Metrics 1 2 3 4 Identifies Anxiety (Notice feelings, body signals, or triggers) Uses Coping Skills (Breathing, grounding, or thinking tools) Group Participation (Engages, listens, and shares when comfortable) Manages Reactions (Responds to stress in a controlled way)
Post-Processing Reflection
What is one strength you noticed?
What is one skill you are still working on?
What is one strategy you will try this week and when?
Build Lab Performance Metric System
0xSKILL_STABLE_VERIFIED
Cooling Core Slides Deck 01 // LOADING_UTILITIES
02 import { Cooling } from 'hardware-management'
03 function stabilizeCore() { ... }
<system-status: cooling>
<temp: optimal>
> WEEK 5 TRAINING
Cooling The Core
"Today we’re adding tools so your system has more options under stress."
Square Breathing
4S
1
Inhale Deep
> CORE_INTAKE
2
Hold Code
> DATA_BUFFER
3
Exhale Slow
> SYSTEM_EXHAUST
4
Hold Empty
> CLEAN_CACHE
[04 // MUSCLE_CONTRACTION_TEST]
Hardware Release
Locked
Tighten your muscles as hard as possible.
Release
Let them go soft. Temperature drops.
Thermal Override
Slow breathing sends a HARDWARE_SIGNAL to your processor:
>_ "Avert threat. Stabilize system."
CORE_TEMP_DROPPING
Hardware Diagnostics Slides Deck 01 // BOOT_DIAGNOSTICS
02 import { Sensors } from 'hardware'
03 function runCheck() { ... }
04 // SCAN_COMPLETE_READY
<protocol: dashboard>
<status: active>
> WEEK 2 TRAINING
Hardware Diagnostics
"Listening to the messages your body is sending to your processor."
The System Dashboard
Anxiety isn't just in your code. It's a FULL HARDWARE response.
"If the body feels the signal, the brain processes the alert."
The body feels the signal FIRST.
The brain then processes that signal.
Common Sensors
> SCANNING_HARDWARE...
Defining "Sensors"
A sensor is any physical body signal that sends an automatic alert to your brain that something feels stressful or unsafe.
Overheat
Hot face, sweating, damp palms.
Pace
Heart racing, fast breathing.
Lockdown
Clenched jaw, tight chest.
Buzzing
Fidgeting, leg bouncing, butterflies.
My Symptoms of Anxiety
"Normal body reactions that everyone experiences!"
dizzy
dry mouth
LOG: DRY_SENSOR
heavy
sweaty palms
shaky legs
fast heart beat
butterflies
feel sick
Everyone feels differently—and that's okay!
Detect EARLY
The sooner you notice the hardware_signal, the easier it is to use your system_tools.
> IF (signal_detected == true) RUN maintenance_plan.sh
Diagnostic Check
Which hardware sensor do you notice FIRST when system stress increases?
Partner_Prompt
"My early warning sensor is ."
Defining the sensor is the first step in Architect Training!
Step 01/04 complete
Hardware Diagnostics Exit Ticket 01 // SAVING_SESSION_LOGS
System_Shutdown_v1.0
Exit Ticket
Hardware Diagnostics Reflection
Coder Name:
Date:
01
What did you learn about your body’s "hardware signals" today?
data_input
02
How do you think catching these signals early can help you manage stress?
optimize_flow
03
How does understanding your body help you feel more in control?
master_control
Log Entry Saved • 100% complete
SESSION_ID: 0x88F2_EXIT
Trigger Tracker Handout 01 // WIRE_MONITORING_ACTIVE
System_Security_v1.2
Trigger Tracker Log
Identifying the Wires That Trip Your Alarm
Lead Architect Name:
Log Date:
Reference: The Big Three "Wires"
Academic
Tests, grades, speaking in class, confusion.
Social
Friend drama, lunch groups, social media.
Everyday
Loud noises, lack of sleep, sensory input.
Live Wire Monitoring
Buffer_Status: ACTIVE
Time Trigger Description Category
Post-Monitoring Debug
Which category (Academic, Social, or Everyday) appears the most often in your data log? Why do you think that is?
Hardware Protection Protocol • Level: Chief Architect
0xFF_DATA_LOG_STABLE
Trigger Detective Worksheet 01 // INITIATING_AUDIT
System_Audit_v2.1
Trigger Detective
Scanning for Input Errors and System Glitches
Coder Name:
1. Input Error Check
Check off any "inputs" that trip your internal firewall.
Logic Errors
Pop Quizzes
Public Speaking
Being Called On
Network Errors
Lunchroom
Unreplied DMs
New Peeps
System Load
Loud Noises
Rushing Time
Being Watched
2
The Big Three Bugs
Priority Alerts for your system
Diagnostic Sweep Complete • Level: Chief Architect
log_captured_stable
Audit Reflection
Processing Session Data
01
What is one trigger you identified today that activates your system, and what does your body do when it happens?
02
What did you learn about how your triggers connect to your physical or emotional responses?
03
How can recognizing your "Big Three Bugs" help you respond differently in the future?
Reflection Log Saved • 100% Complete
Trigger Tracker Exit Ticket 01 // SESSION_ID: TRIGGER_DETECTIVE
System_Shutdown_v2.0
Audit Reflection
Finalizing Trigger Detective Session
Coder:
Date:
01
What is one trigger you identified today that activates your system, and what does your body do?
sensor_capture
02
What did you learn about how your triggers connect to your physical or emotional responses?
link_analysis
03
How can recognizing your “Big Three Bugs” help you respond differently in the future?
logic_update
04
Did anyone notice a similar trigger or reaction, or something different from others?
network_sync
Reflection Log Saved • 100% Complete
Core Cooling Exit Ticket 01 // THERMAL_OVERRIDE_LOG
Core Cooling Exit Ticket
Coder:
Date:
1. What did you notice in your body when your system was “overheating”?
2. What changed in your body when you used a cooling strategy?
3. Which strategy worked best for you?
Square Breathing
Softening
Both
4. What strategy will you try this week, and when will you use it?
STRATEGY_ID:
TIMESTAMP:
CUT_LINE
01 // THERMAL_OVERRIDE_LOG
Core Cooling Exit Ticket
Coder:
Date:
1. What did you notice in your body when your system was “overheating”?
2. What changed in your body when you used a cooling strategy?
3. Which strategy worked best for you?
Square Breathing
Softening
Both
4. What strategy will you try this week, and when will you use it?
STRATEGY_ID:
TIMESTAMP:
Master Performance Log Worksheet 01 // PERFORMANCE_LOG_INIT
Core_Analytics_v1.5
Core Cooling
System Maintenance & Tool Practice Log (Weeks 5-8)
Coder:
Cooling Square
1. INHALE
2. HOLD
3. EXHALE
4. HOLD
Steps 1-4 = 4 Seconds
Hardware Soften
"When hardware locks up, manually release tension. Tighten for 5s... then let go."
UNLOCK SHOULDERS
UNLOCK JAW
UNLOCK FISTS
Diagnostic Log
Capture_Tool_Usage: ACTIVE
Week Stressful Incident Strategy Used Helped? W5 Y / N W5 Y / N W6 Y / N W6 Y / N W7 Y / N W7 Y / N W8 Y / N W8 Y / N
System Maintenance Record • Level: Technician
AUDIT_LOG_SUCCESS
Core Cooling Reflection
System_Shutdown_v1.0
Coder:
Date:
What did you notice in your body when your system was “overheating”?
What changed in your body when you used a cooling strategy?
Which strategy worked best for you?
Square Breathing
Softening
Both
What strategy will you try this week, and when will you use it? 
