Skip to main content

Week 18: Post-Mortem, Patch Notes, and Next Version

Look Back, Improve the Plan, and Celebrate — Curriculum Capstone

You made it to the final week.

Eighteen weeks ago, you started by noticing body clues. Now you are looking back at a real plan you tried in real life.

This week you do three things:

  1. Look back at what happened during Try-It Week.
  2. Write patch notes for version 2.0 of your plan.
  3. Share what you learned in a way that fits you.

The plan was never supposed to be perfect on the first try. The goal was to run the full loop: notice, understand, plan, try, and improve.

Communication Moment

Looking back works best with feedback you can use: "One thing that worked is ___. One thing I'd change is ___." Feedback is information, not a grade on you — and where a plan hurt someone, a repair is part of the next version too. (More on the Communication Skills page.)

Problem Solving Moment

A retrospective is the "adjust" step of the loop. Ask what Version 2 of this friendship or group could change next time — looking back is how you make the next try better. (More on the Problem Solving Skills page.)

Kid Version

This week's idea in kid language: "What worked? What did not work? What will I change next time?"

Facilitator Snapshot
  • This is the finale. Make it feel like a celebration, not a test.
  • Focus on the process, not whether the first plan worked perfectly.
  • The sharing can be tiny: one trusted adult, one sibling, or just the facilitator.
  • The Telemetry Log now shows a real learning journey. Treat it with care.
Quick Navigation

Week at a Glance​

Prep time~15 minutes
MaterialsThe full Telemetry Log, baseline data (Week 15), protocol v1.0 (Week 16), deployment data (Week 17), paper or slides for the presentation
Key vocabularylook back, patch notes, next version, reflection
DifficultyModerate

Facilitator Preparation​

Before You Begin
  • Have all four weeks of capstone data assembled — baseline, protocol v1.0, deployment tracker, and the student's notes.
  • Plan the audience for Session 2. Could be a single family member, a small group of family or friends, or just you. The student gets to pick the audience size that fits them.
  • Consider a small celebration after the presentation — a card, a treat, a certificate. This is genuinely a big accomplishment.
  • Have the Telemetry Log available — they'll do the final reflection in it.
Facilitation Mindset

This is the celebration week.

Whatever the plan did or did not do, the learner completed the full loop on a real problem. Keep bringing the focus back to that.

For Younger Learners (Ages 8–9)​

Adapting This Week

Simplest version of the concept: "You get to share what you discovered."

What to shorten or skip:

  • Use simple "what worked / what didn't / what to change next time."
  • Skip formal rubrics.

Adapting the presentation:

  • The sharing can be one minute, with drawings, speaking, or acting it out.
  • A stuffed-animal audience counts.

Journal alternative: "The most important thing I learned is ___."

What success looks like: The student can share what they tried and one thing they learned.

Guided Session 1​

Look Back and Patch​

Learning Goal​

By the end of this session, the student can:

  • analyze the data from Try-It Week and draw conclusions
  • write patch notes for plan v2.0
  • understand that success is running the loop, not being perfect on the first try

Activities​

1. The Full Data Review

Spread out all the data from the capstone:

  • Baseline tracking from Week 15
  • Protocol v1.0 from Week 16
  • Deployment data from Week 17

Walk through these questions together. Write down the answers:

QuestionAnswer
How often did the friction point happen at baseline?
How often did it happen during deployment?
Did the average severity change?
What percentage of the time did the protocol fire when it should have?
When the protocol fired, did it help?
What was the biggest surprise in the data?

Make a simple before-and-after comparison:

BEFORE (Week 15 Baseline):
  Friction point happened: ___ times in ___ days
  Average severity: ___/10

TRY-IT WEEK (Week 17):
  Friction point happened: ___ times in ___ days
  Average severity: ___/10
  Protocol fired (when triggered): ___% of the time
  Protocol helped (when fired): ___% of the time

2. Write the Patch Notes

Patch notes just mean: what I am keeping, what I am changing, and what I learned.

PROTOCOL — PATCH NOTES v2.0

What worked (keep this in v2.0):
  - ___
  - ___

What didn't work (changing in v2.0):
  - ___ → changed to: ___
  - ___ → changed to: ___

New additions (based on what I learned):
  - ___
  - ___

Known issues (still need to figure out):
  - ___
  - ___

Removed (turned out to be unnecessary):
  - ___

Example:

v2.0 Patch Notes for "fights with my brother before dinner":

What worked:

  • The long exhale at step 1 — it actually helps me not yell.
  • Walking to the kitchen if he doesn't put my stuff back — it ends the moment instead of escalating.

What didn't work:

  • The protocol assumes I notice the trigger at 5:30. Turns out by then I'm usually already too hijacked. CHANGED: trigger is now "when my brother walks into my room" — earlier in the chain.

New additions:

  • Pre-emptive snack at 4:30. Capacity is the biggest variable I underestimated.
  • Door closed at 5:00 PM as a non-verbal signal.

Known issues:

  • Still hard when my brother is upset for his own reasons.

Removed:

  • The "say 'please ask first' in a calm voice" step. Turned out to be too much in the moment. Replaced with just walking out.

3. The Process Check

Return to a foundational idea: this project's success was about process quality, not just whether the protocol worked perfectly.

Process QualityYes/No
Did I identify a real, recurring friction point?
Did I dig into the root cause with the 5 Whys?
Did I design a specific, testable protocol?
Did I collect honest data — including failures?
Did I analyze the data and write patch notes?
Did I iterate based on evidence?

If you checked most of these boxes, the process was strong, even if the first version was messy. Running the loop is the win.

Guided Session 2​

Share and Celebrate​

Learning Goal​

By the end of this session, the student can:

  • share their project clearly with a trusted audience
  • explain what they tried, what happened, and what they learned
  • answer questions about their process

Activities​

1. Preparing the Share-Out

The student prepares a brief presentation (3–5 minutes) covering:

  1. The Problem: What was your friction point? Why did it matter?
  2. The Diagnosis: What did the 5 Whys reveal? What was the root cause?
  3. The Protocol: What was your plan? (Trigger → Default → Check)
  4. The Data: What happened when you ran it? (Show the numbers!)
  5. The Patch: What's v2.0?
  6. The Lesson: What would you tell someone else with a similar problem?
  7. The Course Connection: Which other concepts from the course showed up in your project? (Telemetry? The hijack? The audit? Cognitive bugs? The trust ledger? Iterated games?)

Format can be:

  • A poster board
  • A few pages with drawings
  • A verbal walkthrough with the data sheet
  • A simple slide deck

Simplified share-out (younger learners): Answer four questions with help: "What was my problem? What did I try? What happened? What did I learn?"

2. Share It

The student presents to:

  • The facilitator
  • Family members (invited for this session)
  • Siblings or friends
  • A stuffed animal audience if needed

After the presentation, the audience asks questions:

  • "What was the hardest part?"
  • "What surprised you most?"
  • "What would you do differently if you started over?"
  • "Will you keep using your protocol — or v2.0?"
  • "Which week of the course was your favorite?"

3. The Celebration

This is a genuine accomplishment. Celebrate it.

"Over 18 weeks, you learned to notice body clues, catch panic-brain moments, check thought bugs, slow down before reacting, read trust, set clearer boundaries, and make a real plan for a real problem. You tried the plan, learned from it, and improved it. That matters."

Optional: a small certificate, a card, a treat, a moment of formal recognition. Pick what fits.

Age-Banded Emotional and Social Learning Goals​

  • Ages 8-9: Share the project in a very small format, such as a drawing, short talk, puppet explanation, or one trusted listener.
  • Ages 10-12: Use the full reflection routine, explain more than one perspective, and describe what changed after feedback or practice.
  • Ages 11-13 optional extension: Build a more detailed project with audience, empathy, evidence, accessibility, attribution, revision, and guided discussion of digital or social reputation effects.

Respectful Discussion Moves​

  • "I see it differently because..."
  • "One reason I think that is..."
  • "Can you explain what you mean by...?"
  • "What clues make you think that?"
  • "Who might feel differently?"
  • "I agree with this part, but I wonder about..."
  • "Another perspective might be..."
  • "I changed my thinking because..."
  • "I need a moment before I answer."

The goal is not to force agreement. The goal is to help learners practice listening, naming feelings, giving reasons, asking better questions, and treating people with dignity while discussing social situations.

Digital Feelings and Social Influence​

Digital spaces can affect feelings and relationships. A game, video, message, feed, ad, or post can make someone feel excited, left out, rushed, jealous, worried, proud, connected, or angry. The feeling is real, but it is still worth asking what shaped it.

Learner questions:

  • Who made this message, post, video, or game feature?
  • What feeling might it create?
  • What does it want people to do?
  • Is it trying to get attention, time, clicks, likes, shares, or money?
  • Could someone feel left out, pressured, or rushed?
  • What would be a kind and safe response?
  • Should I pause, check, or talk to a trusted person before reacting?

Some images, voices, videos, messages, comments, or characters may be AI-generated or AI-edited. That does not automatically make them bad or fake, but it does mean we should check carefully before trusting, sharing, reacting, or comparing ourselves to them.

Honest Emotional and Social Literacy Project Checklist​

Before presenting or sharing, check:

  • I clearly described the feeling, social situation, conflict, or relationship skill.
  • I explained who is affected.
  • I explained what someone might feel or need.
  • I considered more than one perspective.
  • I suggested a safe and respectful next step.
  • I avoided blaming, shaming, or exaggerating.
  • I used examples, clues, or evidence to support my ideas.
  • I gave credit for outside facts, images, quotes, ideas, data, or AI help.
  • I made my project readable, understandable, and accessible for my audience.
  • I can answer questions respectfully and revise my idea if needed.

Use the Beginning / Developing / Secure / Extending project rubric in Assessment Checkpoints if you want a shared facilitator tool for this final week.

Independent Practice​

Goal​

Write the final Telemetry Log entry about what these 18 weeks taught you.

Activities​

1. The Final Entry

This is the most important entry in the whole log. Take your time.

Answer in your Telemetry Log:

  1. The Big Takeaway: If you could only remember ONE idea from this whole course, what would it be?

  2. The Most Surprising Lesson: What did you learn that genuinely changed how you see yourself or other people?

  3. The Biggest Thought Bug: Which thought bug still trips you up most often?

  4. The Tool You'll Keep Using: Which specific tool from the course do you think you'll actually use going forward — the audit, the protocol structure, the trust ledger, the 5 Whys, the long exhale, something else?

  5. The Change: How has your thinking about feelings and people changed since Week 1?

  6. Advice to Past You: If you could go back to Week 1 and give yourself one piece of advice, what would it be?

2. Then vs. Now

Open your Telemetry Log to the very first entry from Week 1.

Read it. Sit with it.

Now write:

"When I started this course, I thought emotions were ___."

"Now I think emotions are ___."

"When I started this course, I thought conflict was ___."

"Now I think conflict is ___."

3. My Promise to Myself

Write one short personal commitment:

"Going forward, when something pings my system, I will ___."

Examples:

  • "...check my capacity before deciding the situation is the problem."
  • "...run the audit before reacting."
  • "...notice when I'm hijacked and wait before I act."
  • "...check the trust ledger before deciding a friendship is broken."
  • "...ask what the other person might know that I don't, before deciding they're wrong."
Solo/Small-Group Fallback

The final reflection is fully solo. The presentation works with any audience size — even one person, even a stuffed animal. The structured reflection is what matters most.

Telemetry Log​

This is the final journal entry. Take your time.

Reflection Questions​

  • If you taught this course to a friend, which week would you start with?
  • Do you think you will keep using the Telemetry Log?
  • What is the next problem in your life you might use this loop on?
  • Which lesson from this course might matter most later on?
Optional Portfolio or Certificate Reflection

If the student wants a visible ending, assemble a tiny portfolio with one early Body Signal Notebook / Telemetry Log entry, the final When/Then Plan, one Try-It Week tracker, and one patch-notes reflection. A short written certificate reflection can name what the student can now do without turning the finale into a high-pressure performance.

Check for Understanding​

This is the final check for the whole curriculum. After the sharing and reflections, confirm:

  1. Concept retention: "Name three big ideas from this course."
  2. Personal framework: "What's your process now when something upsets you?" (Looking for: a multi-step approach drawing on course concepts — even a simple 3-step verbal version counts.)
  3. Real transfer: "Tell me about a real moment in the last few weeks where you handled something differently because of what you learned." (Looking for: ANY real example, no matter how small.)
  4. Growth mindset: "What's something you used to think about emotions or people that you don't think anymore?" (Looking for: evidence of intellectual growth — "I used to think being hijacked meant I was bad" or "I didn't know conflicts had hidden variables.")

If the learner can show concept retention, a personal framework, one real-world application, and self-awareness about growth — they've completed the course successfully. Celebrate.

Pause and Notice​

What Matters Here

This is the final Pause and Notice. Make it count.

"Think back to Week 1. How does it feel to know you can now read your body clues, notice when panic brain is taking over, check a story in your head, slow yourself down, and make a plan for a hard moment?"

The most important shift is not one single tool. It is learning that you can notice, understand, and improve your own patterns.

Course takeaway: You have tools now. Keep using them with curiosity and care.

Spiral Review​

Looking Back at the Whole Course

Use this as a facilitated conversation or final reflection:

Unit 1 — Internal Telemetry & Hardware States (Weeks 1–4): Your body is constantly sending signals. Your capacity changes how everything else feels. The hijack is a state-machine change, not a verdict. The Telemetry Log is the home for it all.

Unit 2 — Debugging the Signal Noise (Weeks 5–8): The brain runs predictable bugs. The story generator wraps narratives around every signal. Spirals are feedback loops. The Input/Output Audit lets you respond from clarity, not noise.

Unit 3 — Trust, Ledgers, and Network Security (Weeks 9–11): Trust is a running balance. Boundaries are interface specs. Reliability is the most underrated currency.

Unit 4 — Game Theory in Groups (Weeks 12–14): Peer pressure is an alignment problem. Information corrupts as it travels. Conflict is usually a system mismatch — the other side has information you don't.

Capstone — The Social Interface Patch (Weeks 15–18): Identify → Design → Deploy → Iterate. The loop runs on any problem you face — for the rest of your life.

Ask: "Which unit changed you the most? Which idea will you carry the longest?"

Congratulations

You have completed the Emotional & Social Literacy for Kids curriculum. You now have a set of mental models most adults never learn:

  • Emotions are telemetry, not commands. Signals are data. Read them, don't obey them.
  • The hijack is a state machine. Recognize the switch. Wait it out. Come back online.
  • Cognitive bugs are real and debuggable. You can catch them in motion.
  • Trust is a ledger. Build it on purpose.
  • Conflict is a system mismatch. Diagnose before judging.
  • The engineering loop works on real life. Diagnose, design, deploy, iterate.

Plus tools — the Input/Output Audit, the 5 Whys, the protocol structure, the trust ledger, the long exhale — to put it all into practice.

Keep the Telemetry Log. Keep asking good diagnostic questions. Keep being curious about your own system. The world is better when more people can read their own hardware. Now you're one of them.