System Architecture Slides IF anxiety_level > threshold { RUN protocol.security; } ELSE { CONTINUE background_scan; }
01001000 01100101 01101100 01101100 01101111
AUTHENTICATING... ACCESS_GRANTED... ANALYZING_EMOTIONAL_DATA...
while(system.active) { monitor.sensors(); audit.logic(); }
01010011 01011001 01010011 01010100 01000101 01001101
Architecture Protocol
System Architecture
Internal Security Map
Level: Junior Coder
Status: Online
The System Map
Hardware
The Machine
Your physical body—heart, lungs, and nerves.
Software
The Program
Your thoughts and the way you think.
Sensors
The Signals
Feelings like a racing heart or sweaty palms.
Security
Internal Firewall
Your built-in safety system is anxiety.
Logic_Audit.sys
> Myth or Truth?
"Anxiety means my brain is broken."
MYTH
"Nothing is broken! You have a high-performance system with sensitive settings."
Protocol_Validation
> Myth or Truth?
"Anxiety is a protection system that is over-sensitive."
TRUTH
"Anxiety exists to keep you safe; your firewall is just very thorough!"
System_Modification
> Myth or Truth?
"I can't change how my system reacts."
MYTH
"Software can be updated. You can install new 'reset tools' through practice."
LOG: Validating neural software... LOG: Status: Optimized...
while(system.active) { monitor.sensors(); audit.logic(); }
LOG: Validating neural software... LOG: Status: Optimized...
Main_Protocol.exe
"No part of your system is broken. You are a high-performance machine with sensitive security settings."
We aren't here to "fix" you, because nothing is broken! Our goal is to add New Tools to your software so you can manage your settings.
System Architect Reference Sheet Master Protocol
System Architect Reference Sheet
Architecture Decoder Key
Hardware
The Machine.
Your physical body. Includes your heart, lungs, and nerves that send signals between your brain and body. Your hardware carries out instructions.
Software
The Program.
Your thoughts and the way you think about things. The software tells the hardware what is happening and how to handle data.
Sensors
The Data Signals.
The feelings in your body (like fast heart or sweaty palms). These aren't glitches; they are data points telling you your system is active.
Security
Built-in Firewall.
Your built-in safety system is anxiety. When it’s too sensitive, it can treat small problems like they’re huge emergencies, just like a computer thinking a tiny glitch is a big virus.
Architect Core Principle
"No part of your system is broken. You are a high-performance machine with sensitive security settings."
We aren't here to "fix" you, because nothing is broken! Our goal is to add New Tools to your software so you can manage your settings.
Status: Optimizing
Mode: Architect
ARCHITECT_UNIT_101 // STATUS: OPTIMIZING
Firewall Alert Log Homework Firewall Alert Log
Weekly Mission: System Observation
Coder:
Week:
Mission Briefing
"Your mission this week is to document your firewall's activity. Notice the triggers and how stressed your system feels when the alarm goes off."
System Alert History
| Day / Time | Trigger & Situation | Stress Signal | Level
(1-10) |
| --- | --- | --- | --- |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
Mission Debrief
How did you help the system?
What was the outcome?
SYSTEM_ARCHITECTURE // LOGGING_ENABLED
Architecture Teacher Guide Architecture Teacher Guide
Protocol: Anxiety Reframing // Lesson 1
Educator Access
Lesson Objective
Understand anxiety as an over-sensitive firewall. Reframing physical sensations as system data to reduce self-blame.
Vocabulary
HARDWARE
SOFTWARE
SENSORS
FIREWALL
Facilitation Script
Intro
"Class, today we are System Architects. Your person has a high-performance system, and yours comes with a built-in security firewall—anxiety."
EXPLAIN: Anxiety = Safety system. Over-sensitivity is a glitch, not a failure.
Audit
"A 'Myth' is like a bug in your code. We're going to audit our logs to find mistakes."
TASK: Use worksheet to identify triggers and "debug" logic using Myth vs. Truth method.
Discussion
"Is a smoke detector broken if it goes off for burnt toast? No. How is that like anxiety?"
"How does hearing others' 'Glitches' help you view your own system?"
Logic Key
"Brain is broken." Myth
"Over-sensitive." Truth
"Can't change." Myth
Exit Ticket
1. What did you learn about your "internal system" today?
2. How did it feel to learn that anxiety is a normal response?
3. What did you notice hearing about others' Anxiety Bugs?
UNIT_101_TEACHER_LOG // STATUS: ACTIVE
System Log Worksheet System Log: Week 1
Coder:
Date:
1. Security Alert Audit
"Your built-in safety system is anxiety. When it’s too sensitive, it can treat small glitches like huge emergencies, just like a computer thinking a tiny glitch is a big virus."
Think about a time this week when your body went on high alert (you felt anxious).
What happened? (The Trigger)
How strong was the alert?
Quiet
1
2
3
4
5
6
7
8
9
10
Loud
2. System Logic Audit
Is it a Myth or a Truth?
Statement Myth Truth "Anxiety means my brain is broken."
|
| "Anxiety is a protection system that is over-sensitive." |
|
|
| "I can't change how my system reacts." |
|
|
3. Exit Ticket: Protocol Reflection
1. What did you learn about your "internal system" today?
2. How did it feel to learn that anxiety is a normal response?
3. What did you notice when you heard about others' Anxiety Bugs?
SYSTEM_ARCHITECTURE // LOGGING_COMPLETE
Sensor Map Diagnostic Worksheet Sensor Map: System Diagnostic
Hardware Signal Analysis Protocol
Coder:
Date:
Part 1
System Signal Key
Heart/Chest
Racing, drum, jagged, tight
Stomach
Butterflies, knots, or nausea
Head/Mind
Lightning, heavy, dizzy, racing
Hands/Legs
Shaky, buzzing, or heavy
Throat
Tight knot or dry
Green Zones
Areas that feel calm.
Part 2
Steps
Select an alert event.
Notice body signals.
Draw symbols in areas.
Color code intensity.
Mark "Green Zones".
Intensity
Red: Panic
Yellow: Alert
Green: Calm
Part 3
Post-Diagnostic Reflection
1. Where do you feel anxiety the most?
2. Which symbols did you use most?
3. Are there any "green zones" to notice?
4. What tools might help these areas?
DIAGNOSTIC_PROTOCOL_V5.0 // HARDWARE_SCAN_SUCCESS
Diagnostic Exit Ticket System Diagnostic / Exit Ticket
TASK: POST-PROCESS ANALYSIS | LESSON: COOLING THE CORE
STATUS: SYSTEM STABILIZED
ENCRYPTION: ACTIVE
Coder:
Week:
1. Sensor Comparison
What did you notice in your body before and after using these strategies?
Pre-Reset Status
Post-Reset Status
2. Hardware Analysis
What did this activity teach you about how your body (the hardware) reacts to stress?
3. Deployment Plan
What is one strategy you plan to use this week, and when will you use it?
4. Network Insight
PEER_LOG_COLLABORATION
"Did anyone notice something similar or different from a partner?"
SYSTEM_ARCHITECT_v2.2 // STABILIZATION_PROTOCOL_EXIT_LOG
Trigger Trackers Slides while(input.trigger) { system.process(); alert.evaluate(); }
01000001 01000011 01000001 01000100 01000101 01001101 01001001 01000011
LOGGING: Incoming social data packet... Group size = 12... Threshold exceeded.
while(input.trigger) { system.process(); alert.evaluate(); }
01000001 01000011 01000001 01000100 01000101 01001101 01001001 01000011
Unit 3 Training
Trigger Trackers
Analyzing Alert Wires
Scanning for Inputs
The Big Three "Wires"
Academic
Tests, grades, speaking in class, or feeling confused.
Social
Friend drama, lunch groups, social media, or small talk.
Everyday
Loud halls, lack of sleep, routine changes, or sensory input.
The Wire is not the Fire
Just because something trips your alarm doesn't mean you are in actual danger.
Protocol Analysis
An alert is just data from your sensors.
System Glitch
"Over-sensitive sensors treat glitches like emergencies!"
Alert_Meaning_Audit
> Myth or Truth?
"The alert means danger."
MYTH
"Alerts are often over-sensitive. They aren't always real danger."
Sensor_Log_Evaluation
> Myth or Truth?
"Alerts are just data."
TRUTH
"Sensors provide system data. We analyze it before we react."
Case Study: Jordan
INCIDENT_REPORT_07.sys
"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."
> ANALYSIS: What were Jordan's triggers?
Possible Wires:
A
Noise (Sensory)
B
Crowd (Social)
C
Problems (Everyday)