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: Internet Playground

Supplied scenario and question: A pretend search result says "Free game: give your password to start." What should Lee do?

Illustrative response: Lee should stop and ask a trusted adult. A search result is an invitation to investigate, not permission to share a password.

Optional depth: Compare it with a result that asks no personal information. Does that alone prove the second site is trustworthy? Explain why further checks still matter.

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: The Computer Control Room

Supplied scenario and question: A learner types a letter, then clicks a button that opens a window. Identify two inputs and outputs.

Illustrative response: Typing and clicking are inputs. The displayed letter and opened window are outputs; the operating system helps the app and device respond.

Optional depth: Draw the route from keyboard to app to display. Name one reason an input might not give the expected output, such as the wrong window having focus.

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 Digital Treasure Chest

Supplied scenario and question: Lee wants comments on a dummy story, then needs to restore yesterday’s saved copy. Choose access and recovery steps.

Illustrative response: Comment access permits feedback without editing. Copy the checked backup to a new restored filename, open it, and verify the text. Changes after the backup may be missing.

Optional depth: Explain why a same-device copy helps this rehearsal but cannot protect against losing the device. Never test by deleting real work.

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: Keyboard Ninja Training

Supplied scenario and question: On paper, mark the keys needed to type "Kite 7!". What helps accuracy?

Illustrative response: Use Shift for the capital K and the exclamation mark on an appropriate keyboard layout. Check the result rather than treating speed as success; layouts can differ.

Optional depth: Explain when a keyboard shortcut is useful and how you would check its meaning in the app before using it.

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 Power of Words

Supplied scenario and question: Revise this fictional notice: "club tomorrow bring stuff." The club meets Tuesday at 3, and needs paper.

Illustrative response: "Kite Club meets Tuesday at 3. Please bring paper." Editing clarifies meaning; formatting might make the time bold but cannot supply missing facts.

Optional depth: Write a second version for a younger reader. Explain one wording change separately from one formatting 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 6​

Core lesson: Week 6: The Digital Art Studio

Supplied scenario and question: A poster has tiny pale text on a white background. Choose one change and explain it.

Illustrative response: Use larger dark text and keep space around it so the message is easier to read. The choice serves the reader, not just decoration.

Optional depth: Draw two layouts for the same message and compare readability without claiming that one color works for everyone.

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: The Internet Detective Lab

Supplied scenario and question: Card A gives a dated library schedule with the library as author. Card B reposts it without a date. Which better answers "When is this library open?"

Illustrative response: A is closer to the responsible source and includes timing. I still need to check whether the date is current for my question; B does not independently confirm it.

Optional depth: Draft a precise query containing the library name and hours. Explain why the top-ranked result alone is not evidence of accuracy.

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: The Idea Workshop

Supplied scenario and question: Use the supplied Kite Club quantities: 12, 3, 8, 5, 10. What does a spreadsheet total show?

Illustrative response: The total is 38 items. A SUM formula updates if an input changes; it is not a cost total because prices are absent. A chart needs item units and category labels.

Optional depth: Change 8 to 9: predict 39, then explain why names and quantities must stay paired when sorting rows.

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: Teach the Computer to Follow Instructions

Supplied scenario and question: A paper robot must draw a square. "Draw something square-ish" is too vague. Improve the instructions.

Illustrative response: Repeat four times: draw a side of the chosen length, then turn 90 degrees. The order and repeat count make the intended shape testable.

Optional depth: Trace what happens with only three repetitions. Explain the difference between an unclear instruction and a clear instruction for the wrong result.

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: Build Your First Program

Supplied scenario and question: A program checks whether space is held when the flag is clicked. True says Ready; false says Waiting. Trace both runs.

Illustrative response: Holding space at the check selects Ready; otherwise it selects Waiting. Pressing space later does not rerun a one-time check.

Optional depth: Explain how putting the check inside a repeating loop changes when inputs can affect the result. Draw both paths.

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: The Debugging Lab

Supplied scenario and question: A variable starts at 0 and adds 1 three times. A second run has no reset. What values result?

Illustrative response: The first run ends at 3. The next ends at 6 if it keeps the old state. Resetting to 0 makes each run end at 3.

Optional depth: Replace add-one with set-to-one: the final value becomes 1. Explain why setting and changing are different operations.

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: How Things Are Built

Supplied scenario and question: A bicycle has pedals, a chain, wheels, and brakes. How do two parts depend on each other?

Illustrative response: Pedals drive the chain, which drives a wheel. A broken chain can stop this path even when the wheel itself works; brakes have a different role.

Optional depth: Draw a component boundary and name an interface. Do not take apart equipment to complete the paper task.

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: The AI Discovery Lab

Supplied scenario and question: A pretend AI answer says the supplied numbers 12 + 8 total 25. What should the learner keep?

Illustrative response: The checked sum is 20, so I reject 25 and correct the note. Fluent wording did not make the answer accurate.

Optional depth: Describe a case where an AI answer is correct but still needs a source or context check. No live AI account is needed.

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: AI as a Creative Partner

Supplied scenario and question: A pretend AI suggests a poster with six paragraphs. The audience has ten seconds to read it. What do you change?

Illustrative response: Keep one short message, a clear title, and useful visual spacing. Human judgment checks whether the suggestion serves the audience.

Optional depth: Write a revision prompt with the audience and time limit, then explain what you would verify in the result.

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: Invent Something Cool

Supplied scenario and question: Plan a fictional club sign. It must say the meeting place and fit on one sheet. What counts as a first version?

Illustrative response: A rough sketch with a readable title, place, and one sentence is a prototype. It can be tested before polishing.

Optional depth: List one must-have requirement and one optional feature; explain why finishing the core comes first.

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: Build and Improve

Supplied scenario and question: A viewer says the meeting place on version 1 is hard to find. How should version 2 change?

Illustrative response: Move the place beneath the title and enlarge it. Record the feedback and the specific change so improvement can be explained.

Optional depth: Propose one comparison that would show whether the change helped instead of assuming a prettier sign is clearer.

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: Final Touches

Supplied scenario and question: A final folder has sign-final, sign-final2, and sign-newest. How do you prepare it for a reviewer?

Illustrative response: Choose descriptive names, identify the version being presented, and check that it opens. Keep draft evidence so the revision history is understandable.

Optional depth: Create a short read-me note with the intended file, tools used, and any source or AI credit needed.

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: Creator Showcase

Supplied scenario and question: Show the fictional sign and explain one change made after feedback. What is a useful reflection?

Illustrative response: "I enlarged the place because a viewer could not find it. I checked it in the saved file. Next time I would test readability earlier."

Optional depth: Explain the project privately, on paper, or to a partner. Public posting and a live presentation are not required for this practice.

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.