Skip to main content

Worked Examples and Optional Depth

Use these cards after the corresponding core teaching. They supply the scenario and a sample response; no external research, new account, real-world contact, or private disclosure is required. The examples are fictional teaching cases, not real measurements, medical guidance, legal rulings, financial advice, or promises of outcomes.

Two kinds of optional work​

  • Supplied practice: the scenario, sample response, and depth question are on this page. Allow about 15–20 minutes for one card, with paper or oral explanation. Read the card before the session; a calculator is optional for arithmetic.
  • Open research prompt: a request to locate or construct missing teaching material, such as outside sources, interview records, or a real-case packet. This is not supplied instruction. A tool activity with complete steps is still supplied instruction, even when an adult must prepare the device or account. An adult must select and verify materials, arrange access, and plan additional time first. Use the supplied card instead when those materials are unavailable.

Choose depth by readiness and interest, not age alone. Learners aged 10–12 can use the core teaching without taking every technical add-on; older-learner work remains optional. The depth questions are not prerequisites for the next core week or criteria for its checkpoint.

How to use a card​

  1. Read the scenario and ask for a reasoned answer.
  2. Let the learner draw, speak, sort, or write using the fictional case.
  3. Compare with the sample: notice the evidence and the limits, not matching wording.
  4. If ready, change the stated assumption using the depth question.
  5. If the core idea is unclear, return to the linked lesson before adding complexity. A private or paper artifact is enough.

Sample responses illustrate reasoning, not scripts to memorize or the only defensible answer to an open choice. They do not require a learner to experience or disclose the situation.

Week 1​

Core lesson: Week 1: Mapping Your Biological Hardware

Supplied scenario and question: A fictional character notices tight shoulders before a loud assembly. What can the observation tell us?

Illustrative response: It is a body signal worth noticing, not a diagnosis or proof of one emotion. The character can pause or ask a safe adult for support.

Optional depth: Give two possible interpretations and say what remains unknown. Personal body reports are not required.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 2​

Core lesson: Week 2: Physical Inputs and Processing Capacity

Supplied scenario and question: A fictional character slept poorly and finds a busy room harder to manage. What is a careful explanation?

Illustrative response: Physical state and environment can affect capacity. That is a possible connection, not a claim that the character is bad or that sleep explains every difficulty.

Optional depth: Name one accessible support the adult could provide without blaming the learner for limited capacity.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 3​

Core lesson: Week 3: The Brain's Emergency Override

Supplied scenario and question: A fictional fire alarm makes a character freeze. Is freezing a choice to ignore instructions?

Illustrative response: Not necessarily. Fast protective responses can interrupt planning. Adults should support safety; a calm voice or perfect action is not required to deserve help.

Optional depth: Describe an adult support route rather than asking the character to prove they can control the response.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 4​

Core lesson: Week 4: Reading Your Own Early Warning Signs

Supplied scenario and question: Use an invented log: loud room, tense hands, request for quiet space. What belongs in a sample entry?

Illustrative response: Record the situation, observed signal, possible interpretation, and support step. Keep certainty limited; a private learner journal is not evidence the adult must inspect.

Optional depth: Separate one observation from one inference and choose another explanation to check.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 5​

Core lesson: Week 5: The Software Bugs of the Mind

Supplied scenario and question: A fictional thought says "I made one mistake, so I fail at everything." What is the thought pattern?

Illustrative response: It turns one event into an all-or-nothing generalization. A more accurate statement is "I made a mistake on this task and can ask what to try next."

Optional depth: Keep the real disappointment valid while reducing the unsupported generalization.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 6​

Core lesson: Week 6: When the Brain Constructs Bad Stories

Supplied scenario and question: A character receives no reply to a message and thinks "They hate me." What is fact and what is story?

Illustrative response: Fact: no reply has arrived. The dislike claim is an interpretation; the person may be busy or offline. A neutral check can help if it is safe.

Optional depth: Name an alternative without insisting the most comforting explanation must be true.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 7​

Core lesson: Week 7: Faulty Logic Loops and How to Spot Them

Supplied scenario and question: A character predicts one missed turn means losing every future game. What would a bounded check say?

Illustrative response: The missed turn is real, but every future loss is an unsupported chain. Check the next actual decision and available support.

Optional depth: Draw the assumption between each step; do not label a valid safety concern a thought bug.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 8​

Core lesson: Week 8: Separating Signal from Narrative Noise

Supplied scenario and question: A fictional note says "Three people laughed after I dropped a pencil; everyone thinks I’m useless." Audit it.

Illustrative response: Separate the observed laughter from the broad conclusion. We do not know the reason or what everyone thinks. If teasing or harm is involved, seek adult support.

Optional depth: Choose a safe verification or support step; checking evidence is not permission to dismiss mistreatment.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 9​

Core lesson: Week 9: How Relationships Build and Spend Capital

Supplied scenario and question: A fictional teammate keeps two promises, then misses one because transport fails. How should the trust metaphor be used?

Illustrative response: Notice the pattern and the explanation, then discuss a realistic next plan. A trust jar is a metaphor, not a score that determines dignity or rights.

Optional depth: Distinguish disappointment from proof of bad character; trust does not require accepting unsafe behavior.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 10​

Core lesson: Week 10: Clear Boundary Rules

Supplied scenario and question: A character does not want a hug and freezes rather than saying no. Is the boundary valid?

Illustrative response: Yes. A limit is valid even without a clear sentence or successful enforcement. Others and responsible adults must respect and protect it.

Optional depth: Suggest how an adult could notice and support choice without grading the character’s assertiveness.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 11​

Core lesson: Week 11: Consistency, Transparency, and High-Bandwidth Connections

Supplied scenario and question: A fictional partner cannot meet a deadline and tells the group early. What supports reliability?

Illustrative response: Give honest notice, explain the task impact without private details, and make a workable backup plan. Transparency is not compulsory personal disclosure.

Optional depth: Compare early notice with a promise nobody can keep; access barriers may need adult support.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 12​

Core lesson: Week 12: The Alignment Problem in Groups

Supplied scenario and question: A fictional group says "Share the password or you’re not our friend." What route is appropriate?

Illustrative response: Do not share it; seek a safe adult’s help. Threatening belonging to obtain access is pressure, and the child need not win an argument first.

Optional depth: Write a fictional support plan using a note or communication aid instead of a spoken confrontation.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 13​

Core lesson: Week 13: Corrupt Data Transmission and Its Ripple Effects

Supplied scenario and question: Three classmates repeat a rumor from one message. What should a character do before forwarding it?

Illustrative response: Trace the origin, check relevant evidence, and avoid spreading unverified or private claims. Three repetitions do not create three independent sources.

Optional depth: If the message threatens or targets someone, explain why adult protection matters alongside verification.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 14​

Core lesson: Week 14: Iterated Games and Mutual Support

Supplied scenario and question: Two characters disagree safely over poster colors; another is threatened with a leaked private message. Are the next steps alike?

Illustrative response: The color disagreement can use voluntary negotiation. Threats and unequal power need adult protection, not forced cooperation or mediation.

Optional depth: Explain why one serious incident is enough to ask for help even before a bullying label is settled.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 15​

Core lesson: Week 15: Diagnosing a Recurring Social Problem

Supplied scenario and question: In a fictional team, handoffs are unclear at three meetings. Describe friction without assigning a diagnosis.

Illustrative response: The task-transfer process is unclear. Look at when handoffs happen and what information is missing; do not infer a personal flaw.

Optional depth: Choose an observable process goal using fictional or neutral task data.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 16​

Core lesson: Week 16: Make a When/Then Plan

Supplied scenario and question: Make a fictional when/then plan for unclear handoffs. What should it include?

Illustrative response: When a task changes owner, then write the owner, next step, and check time on a shared task card. Add a fallback if the handoff is not understood.

Optional depth: Name a safety limit: a protocol is not a plan for tolerating threats or forcing private disclosure.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 17​

Core lesson: Week 17: Running the Experiment in the Real World

Supplied scenario and question: A fictional handoff plan worked twice in three tries; one task lacked a next-step note. Evaluate it.

Illustrative response: Two successes are useful observations, not proof the plan always works. The missing note suggests a concrete change to test.

Optional depth: Use invented process data; assess the plan rather than requiring a personal emotional change.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.

Week 18​

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

Supplied scenario and question: Patch the handoff card after the fictional trial. What can the learner present?

Illustrative response: Add a visible next-step field and explain the reason using the trial notes. A paper artifact, fictional sample, or private reflection is sufficient.

Optional depth: Identify one limit and one next test. Do not require private journals, public stories, forgiveness, or restored relationships.

Facilitator check: Ask which stated fact or assumption supports the explanation. If that link is missing, model it with the sample and invite a second explanation. Assess reasoning and limits, not speed, exact wording, or personal experience.