Squad Mechanics Slides System Status: Active
MNDS-HKR // MOD-01
Social-Emotional Protocol // Peer Dynamics
SQUAD MECHANICS
Decoding team dynamics, solving interactive collaboration challenges, and constructing an unbreakable peer group contract.
Target Demographic
Grades 7 & 8 // Tier 1 SEL
Interactive Challenge
Phase 1: Station Loop
STEP 01 Mission Architecture
MNDS-HKR // MOD-01
The Squad Station Challenge
High-performance squads aren't born; they're engineered. Your team will navigate four interactive test chambers. Each chamber targets a critical node of collaboration.
Universal Directive
No single member can complete a station alone. Collective input is required to decrypt each challenge card.
STATION 01
Equity Balance
Determine how to share work fairly when team motivations and styles collide.
STATION 02
Friction Decryption
Analyze real-world conflict scenarios and translate heat into healthy resolutions.
STATION 03
Synergy Protocol
Map team roles and discover your squad's specialized superpowers.
STATION 04
Trust Vault
Design behavioral rules that construct psychological safety for everyone.
SYSTEM GUIDELINES // DO NOT SKIP CHALLENGES ROTATE AT THE CHIME
STEP 02 Execution Mode
MNDS-HKR // MOD-01
How to Hack the Stations
1
Read & Appraise
Pick up the station card. One squad member reads the scenario aloud to establish the baseline context.
2
Debug & Discuss
Address the prompts on the card. Share perspectives, validate different thoughts, and map out potential answers.
3
Log the Solution
Every individual records the consensus on their personal Squad Mechanics Logbook. Rotate when the timer strikes zero.
Operational Timing
08:00 min/station
Pacing is key. Don't linger too long on discussion before writing down your findings!
Live Squad Focus Checklist
One voice at a time; actively listen
Everyone contributes to the logbook
Disagree constructively when opinions clash
KEEP ROTATING IN NUMERICAL ORDER SUPPORT YOUR TEAMMATES
STEP 03 The Final Output
MNDS-HKR // MOD-01
Drafting the Squad Contract
Now that you've completed all four stations, synthesize your insights. Your final mission is to establish 3 unbreakable ground rules that your squad will live by.
Contract Rules Must Be:
Actionable: Don't just say "be nice." Say "We solve disagreements by listening to both sides first."Mutual: Every squad member must agree to uphold them.Enforceable: How will your group remind each other if someone violates a rule?
Draft Box (In your logbook)
RULE 01
RULE 02
RULE 03
The Signature: Once agreed upon, every member signs the logbook. This signifies your absolute commitment to your squad's success.
SQUAD CONTRACT MUST BE CO-SIGNED BY ALL MEMBERS MISSION COMPLETE PROTOCOL
Squad Mechanics Station Cards MNDS-HKR // MODULE 01
SQUAD CHALLENGE STATIONS
PRINTABLE CARDS
STATION 01
EQUITY BALANCE
The Scenario: The Group Divide
Your class is creating a digital presentation. Maya and Sam are extremely excited. They immediately grab the computer and start designing slides, talking rapidly. Leo and Chloe are quieter and feel left out. Leo checks out and plays on his phone; Chloe sits in silence.
Debug Questions for your Squad:
What is the difference between Equality (everyone doing the same) and Equity (everyone getting what they need to contribute)?
How can Maya and Sam share the work without losing design momentum?
What is an active step Leo or Chloe can take to re-engage with the squad?
LOG RESPONSES IN SQUAD LOGBOOK T1 SEL PROTOCOL
STATION 02
FRICTION DECRYPTION
The Scenario: Heat of the Moment
During a poster project, a heated argument breaks out. Julian snaps, "You are completely bossy! You always reject my ideas and think only yours are good!" Emma fires back, "Well, you're just lazy! You showed up late and haven't written a single sentence yet!"
Debug Questions for your Squad:
What is the core hidden need or frustration driving Julian's and Emma's anger?
How can Julian's "bossy" comment be translated into an objective "I-statement"?
How can Emma's "lazy" comment be translated into constructive feedback about accountability?
DECRYPT THE COMMENTS IN THE LOGBOOK T1 SEL PROTOCOL
MNDS-HKR // MODULE 01
SQUAD CHALLENGE STATIONS
PRINTABLE CARDS
STATION 03
SYNERGY PROTOCOL
Review these 4 squad superpower profiles:
🛠️ Organizer
Keeps track of time, guidelines, and steps.
💡 Catalyst
Generates creative ideas and bold directions.
🧐 Analyst
Asks hard questions and checks for accuracy.
🤝 Advocate
Boosts morale and ensures everyone is heard.
Debug Questions:
Which of these roles feels most like you? Why?
What happens if a squad is made up of only Advocates or only Analysts?
How does knowing your squad's roles prevent team breakdown?
ASSIGN ROLES IN YOUR LOGBOOK T1 SEL PROTOCOL
Squad Mechanics Logbook MNDS-HKR // MODULE 01 LOGBOOK
SQUAD MECHANICS
TIER 1 SEL WORKBOOK
Student Name
Date
Class Period
Squad Designation
STATION 01
Equity Balance Analysis
Q1. State the critical difference between sharing tasks equally versus sharing tasks equitably.
Q2. Action Plan: What is one practical system Maya & Sam can use to ensure Leo & Chloe can contribute to the presentation?
STATION 02
Conflict Decryption & translation
Q1. Decrypt Emma's accusation ("You're just lazy!"). Translate it into a healthy constructive statement about accountability.
Q2. Decrypt Julian's accusation ("You're completely bossy!"). Translate it into a clear, respectful "I-Statement".
TURN PAGE TO COMPLETE LOGOUT PHASE PAGE 01 // 02
MNDS-HKR // MODULE 01 LOGBOOK PAGE 02 // 02
STATION 03
Synergy Role Alignment
Map your squad members' primary superpowers (Organizer, Catalyst, Analyst, Advocate):
Name:
Role:
Name:
Role:
Name:
Role:
Name:
Role:
STATION 04
Trust Vault & recovery
Squad "Recovery Phrase" (What you say after mistakes):
How will you rebuild trust if someone snaps at a teammate?
THE SQUAD CONTRACT
FINAL CO-CREATED PROTOCOLS
Synthesize your station findings. Write 3 actionable rules your squad commits to upholding throughout the school year. Be specific and positive.
RULE 01
RULE 02
RULE 03
We, the undersigned, commit to debugging our squad and upholding this contract:
SQUAD MEMBER 1
SQUAD MEMBER 2
SQUAD MEMBER 3
SQUAD MEMBER 4
MNDS-HKR: SYSTEM INSYNC CONFIRMED ● PROTOCOL COMPLETE
Inner Thermostat Slides THERMAL STATE: ELEVATED
MNDS-HKR // MOD-02
Self-Regulation Protocol // Emotional Control
INNER THERMOSTAT
Mastering your internal thermal environment. Learn to identify stress alerts, map physiological heat triggers, and execute immediate cooldown protocols.
Target Demographic
Grades 7 & 8 // Tier 1 SEL
Interactive Challenge
Phase 2: Trigger Blueprint
CONCEPT The Control Paradigm
MNDS-HKR // MOD-02
Are You a Thermometer or a Thermostat?
The fundamental shift in middle school self-management is moving from passive observation to active control.
The Thermometer
A thermometer is purely reactive . When the room gets hot, it simply records the heat. It rises higher and higher as stress builds, with absolutely no control over its environment.
REACTION STATE: PASSIVE AWARENESS ONLY
The Thermostat
A thermostat is actively proactive . It monitors the heat, but when the temperature reaches a specific threshold, it triggers an internal HVAC system to actively cool the climate.
REACTION STATE: ACTIVE CLIMATE MANAGEMENT
OBJECTIVE: TRANSITION FROM REACTIVE TO ACTIVE REGULATION MNDS-HKR: ACTIVATE CLIMATE CONTROL
MONITOR Stress Diagnostics
MNDS-HKR // MOD-02
How to Recognize Your Overheat Signals
Before your mental thermostat can cool down, it needs to recognize when the system is actually overheating. Stress signals always present themselves in two key domains.
System Warning
If you ignore your early warnings, your rational thinking processor shuts down and your emotional system overloads.
Physical Warning Codes
Your body senses stress first. Common codes include: rapid shallow breathing, a pounding heart, clenched jaw or fists, a tight chest, or sudden feeling of hot/cold.
Cognitive Warning Codes
Your brain starts throwing errors. Common codes include: racing thoughts, mental block or "clogged" feeling, instant irritability, catastrophic thinking, or urge to escape the room.
ALERT VERIFICATION // RECOGNIZE SIGNALS BEFORE TOTAL CRITICAL MASS MONITOR STATE CONSTANTLY
EXECUTE Cooldown Protocols
MNDS-HKR // MOD-02
Executing Cooldown Algorithms
When you spot a warning signal, instantly execute one of these pre-loaded cooldown algorithms.
ALGORITHM 01
The Square Reboot
Slowly reset your biological processor: Inhale for 4 seconds, hold for 4 seconds, exhale for 4 seconds, and hold empty for 4 seconds. Repeat three full cycles to lower heart rate immediately.
Thermostat Trigger Map MNDS-HKR // MODULE 02 DIAGNOSTICS
THERMOSTAT TRIGGER MAP
PERSONAL STRESS AUDIT
Student Name
Date
Class Period
DIAGNOSTIC 01
Identifying Overheat Triggers
Triggers are events, comments, or settings that instantly raise your internal temperature. Identify and list two specific triggers that affect you in each of the environments below:
Academic Zone
E.g., cold calling, Pop quizzes, timed tests.
Social Zone
E.g., being excluded, whispers, group selection.
Digital Zone
E.g., group chats, unread pings, social posts.
DIAGNOSTIC 02
Your Warning Indicators
When stress triggers are tripped, your body and mind emit alert codes. Check off or write down the exact signals you experience when your system heats up.
Physical Alerts
Rapid heartbeat
Shallow breathing
Clenched jaw / fists
Feeling hot / sweating
Cognitive Alerts
Racing thoughts
Mind blocks / fog
Irritability / snap
Urge to withdraw
Alert Mapping Area
Mark / Sketch Where on your body do you feel the thermal heat build?
NEXT: DEPLOYING CLIMATE CONTROLS PAGE 01 // 02
MNDS-HKR // MODULE 02 REBOOT PAGE 02 // 02
PROTOCOL 01
Your Custom Reboot Cooldowns
Select and adapt two algorithms from the slides. Customize them below so they are ready for immediate physical execution in class or at home.
ALGORITHM #1 DESCR
My chosen cooldown:
HOW I WILL EXECUTE IT (STEPS)
ALGORITHM #2 DESCR
My chosen cooldown:
HOW I WILL EXECUTE IT (STEPS)
THE REBOOT CONTRACT
EMERGENCY CLIMATE DIRECTIVE
Write out your automated self-regulation script. When your body signals a spike, this script operates as an override code to return you to standard operating limits. Fill out the blueprint spaces carefully.
1. Trigger Interception
"When I experience my warning code:
,"
2. Algorithm Launch
"I will instantly execute my customized cooldown:
3. Software Reframing Overwrite
"I will overwrite catastrophic thinking by telling myself:
Goal Blueprint Slides ARCHITECT ENGAGED
MNDS-HKR // MOD-03
Systems Architecture // Personal Blueprinting
GOAL BLUEPRINT
Moving beyond hopes and wishes. Discover how to engineer real results using visual systems-thinking, milestone sequencing, and friction defense.
Target Demographic
Grades 7 & 8 // Tier 1 SEL
Interactive Challenge
Phase 3: System Builder
SYSTEM THEORY The Myth of Hopes
MNDS-HKR // MOD-03
You Do Not Rise to Your Goals. You Fall to Your Systems.
Middle school is packed with goals: "Get straight A's," "Make the varsity team," "Get more sleep." But a goal is just an end-state. Without a concrete system of daily behaviors, a goal is just daydreaming.
"Winners and losers have the exact same goals. The system of execution is what differentiates the outcome."
Goal-Only Focus (Fragile)
Focused strictly on the future outcome. Leads to high anxiety, procrastination, and "cheating" the process. When a minor failure occurs, the entire objective is abandoned.
System-Only Focus (Unbreakable)
Focused on the daily inputs, environment controls, and weekly feedback loops. Results happen as a natural side-effect of running a reliable personal machine.
MNDS-HKR: BUILD HIGH-FIDELITY ROUTINES DECONSTRUCT OBJECTIVES DAILY
ARCHITECTURE The 3-Step Sequence
MNDS-HKR // MOD-03
The Three Nodes of a Goal System
To build a high-performing system, you must break your big aspiration into three distinct structural nodes.
NODE 01
System Inputs
These are the daily, recurring actions you have complete control over. It is not "getting an A," it is "doing 20 minutes of study at my desk every day at 4:00 PM."
FOCUS: 100% CONTROL
NODE 02
System Throughput
These are your intermediate milestones or warning sensors. They help you verify if your inputs are working. E.g., weekly self-quizzes or binder organization reviews.
FOCUS: PROGRESS METRICS
NODE 03
System Outputs
This is the final ultimate achievement—the byproduct of your high-fidelity inputs and reliable throughput sensors. It occurs automatically over time.
FOCUS: ULTIMATE REWARD
ALWAYS START SYSTEM BUILDING AT NODE 01 MNDS-HKR SOFTWARE FLOW
DEFENSE PROTOCOL Friction Engineering
MNDS-HKR // MOD-03
Engineering Friction
Willpower alone is not enough to maintain a new system. To protect your inputs, you must consciously manipulate the
Goal Blueprint Builder MNDS-HKR // MODULE 03 SPECIFICATIONS
GOAL SYSTEM ARCHITECTURE
SYSTEMS DESIGN FILE
Student Engineer
Date
Class Period
NODE 03
The Output (Ultimate Goal)
WHAT WE WANT TO ACHIEVE
Identify your large aspiration (e.g., getting a B in algebra, mastering an art skill, getting to soccer practice early, reading 1 book a month):
NODE 01
The Inputs (Daily/Weekly Routines)
WHAT WE CAN CONTROLS DAILY
An input is a highly specific action you can run with 100% control. Design two inputs that feed directly into your Node 03 Output.
INPUT CODE 01A
Specify action, duration, time, and location:
INPUT CODE 01B
Specify action, duration, time, and location:
NODE 02
The Throughput Sensors (Weekly Check)
HOW WE MEASURE FUNCTIONALITY
How will you verify if your inputs are working on a weekly basis? (E.g., doing a binder organization sweep every Friday, asking a teacher for a grade printout, logging practice times):
NEXT: CONFIGURING ENVIRONMENTAL DEFENSES PAGE 01 // 02
MNDS-HKR // MODULE 03 CONFIGURATION PAGE 02 // 02
SHIELD 01
Friction Controls (Willpower Shield)
Your environment is far more permanent than your willpower. Map out your custom environmental friction defenses below to guarantee system compliance.
THE BARRICADE (Increase Friction for Bad Habits)
What is your biggest system distraction (e.g. phone, gaming, chatter)? How will you add at least 20 seconds of physical friction to block it?
THE SLIDE (Decrease Friction for Good Inputs)
How can you pre-stage your environment so starting your Node 01 actions takes less than 5 seconds of physical effort?
SQUAD VERIFICATION CORE
PEER ACCOUNTABILITY DIRECTIVE
Find a partner from your Module 01 Squad. Commit to conducting a 2-minute "System Audit" check-in twice a week. Outline your peer agreement parameters below.
Accountability Partner Name
Name:
Weekly Audit Time / Day
Days:
Standard Weekly Check-In Question Prompts:
"On a scale of 1-5, how reliably did your environmental slides and barricades protect your Node 01 daily inputs this week?"
STUDENT CO-SIGN
PARTNER CO-SIGN
MNDS-HKR: GOAL SPECIFICATION REGISTERED ● ARCHITECTURE COMMITTED
