Lesson 7 of 37 in this sequence

19%

Not completed yet

Saved on this device only — not synced to an account yet.

Learning path

Step 7 of 37

Continue the sequence

ResumeReturn to this step ReviewRevisit the core idea RemediateGet repair practice Next stepChoose the next lesson manually

Completion

Review objectives and instruction
Complete the activity with manual learner confirmation
Answer every understanding-check item
Show completion feedback and reward only after the learner finishes the check

Progress

Step 7/37
15 content types
AI help source context available
Auto-advance blocked

Review objectives and instruction

AI help

Available only with source grounding, privacy limits, age controls, and measurement.

AI source context

If It Breaks, Look Why and Try Again · Try, Look, Fix · K-2-ETS1-2 · engineering design

Evidence: local lesson AI-help metadata only; source-grounding, privacy, age-safety, and measurement hooks do not prove real model quality, production telemetry, child AI approval, or AI tutor production readiness

Production AI readiness not claimed

AI source context

Assessment shape

Local lesson assessment shape is complete.

Local shape only; production answer-attempt telemetry, live ownership/RLS evidence, mastery interpretation, release, and production readiness are not claimed here.

Objectives: 5
Activity: Prompt ready
Quiz items: 3 items, 3 answer keys, 3 explanations
Reward: Completion reward ready

Assessment progress stays manual: do not auto-advance through uncertain answers, failed writes, consent, media, payment, learner choice, or AI-assisted checks.

Learning-loop evidence: Content-map contract only; persistence and production learner-progress writes require route/API evidence.

Manual policy: assessment, media, consent, payment, learner choice, failed writes, and AI-uncertain help stay under learner control.

Prerequisite: Complete or review Find a Problem to Solve; Use with parent or guardian controls for child learners

AI guardrails

Privacy

Do not send raw child free text without consent
Use source excerpts and non-identifying progress state only
Asset is not registry-gated

Age safety

Apply junior audience controls before AI-help claims
Keep child learner AI paths behind guardian/product review evidence before readiness claims

Measurement

Log AI help usage by surface and asset slug
Evaluate answer quality against source-grounded rubric before production-readiness claims
Tie remediation prompts to completion, retry, or review outcomes

Local AI-help guardrails only; they do not prove guardian approval, production telemetry, model evaluation, release, deployment, or AI tutor production readiness.

Source and rights

Source path: koydo-app/scripts/curriculum-authoring
License: ai-generated-koydo
Attribution: Attribution decision needs owner review
AI provenance: claude-opus-4-8

Source review gates: attribution_missing

Local source evidence only; this does not prove publication rights, attribution approval, AI provenance clearance, release, deployment, or production readiness.

Route review

Current route: /library/junior/engineering_making/en/lesson/try-fix-try-again
Route source: Fallback route needs owner canonical review
Candidate route: /library/junior/engineering_making/en/lesson/try-fix-try-again

Local route evidence only; fallback candidates need owner-approved canonical route policy before route writes, production discoverability, or readiness claims.

Content gates: canonical_target_web_missing_uses_library_fallback

lessonslessonslesson objectivesmedia scenesdrillspractice setsquizzesfeedbackcharacterscitationsconcept mapsprogressresumereviewremediationnext steps

If It Breaks, Look Why and Try Again

with Atlas

Atlas stands at a wooden workbench covered in colorful blocks, cardboard tubes, and tape, holding up a small tower that has just toppled over, looking at the fallen pieces with a curious smile and a magnifying glass in hand.

Identify what went wrong when a build falls or breaks.
Explain why looking closely at a broken build helps us fix it.
Compare a first try to a second try and describe what changed.
Predict whether changing one part will make the build stronger.
Describe changing one thing and testing the build again.

Key terms

try: to build your idea for the very first time
look: to study a broken build closely to find out what went wrong
fix: to change one part so the build works better next time
iteration: doing the try, look, and fix steps again to keep improving

Looking Is How You Learn

When a build falls or breaks, the most important step is to LOOK. Looking closely tells you exactly what went wrong. Atlas looked at his fallen tower and saw the bottom blocks were too small and wobbly. That clue told him what to change. If you throw a broken build away without looking, you lose the chance to learn from it. Builders treat a fall as a hint, not a failure.

Change One Thing, Then Try Again

After looking, change just one thing and build again. Atlas only swapped in bigger, wider bottom blocks, and the new tower stood up. Because he changed one thing, he knew that wider blocks were the fix. If you change everything at once, you cannot tell which change helped. The try, look, fix, and try again loop is how engineers slowly turn a wobbly idea into something that works.

Worked examples

Atlas built a tall tower and it crashed to the ground. What does he do step by step?

Look closely at the fallen tower to find the problem.
Notice the bottom blocks were too small and wobbly.
Change one thing: put bigger, wider blocks on the bottom.
Try again by building the tower a second time and watch it stand.

Answer: With wider bottom blocks, the tower stands up and does not fall, because a wider base is steadier.

Hi, builder! I am Atlas. I love to build things. One day I built a tall tower out of blocks. I put it together and then — crash! It fell down. I felt sad for a moment. But then I remembered: builders do not give up. Builders look. I looked at the fallen tower. I saw that the bottom blocks were too small. The tower was too wobbly at the bottom. So I changed ONE thing. I put bigger, wider blocks on the bottom. Then I built the tower again. This time it stood up! It did not fall. That is what engineers do. They try. They look at what went wrong. They change one thing. Then they try again. Here is a secret: every great builder has had something fall down. Looking at WHY it fell is how you get better. You are not failing — you are learning!

Activity

Sort each picture into the right step: Try, Look, or Fix.

Practice

Describe a time something you built broke and what you looked at.

Name the three steps in order: try, look, and fix.

Common mistakes to avoid

If a build breaks, you should throw it away.Looking at a broken build first tells you why it failed so you can fix it.
You should change every part at once to fix it.Changing one thing at a time shows you which change actually made the build better.

Check your understanding

Atlas built a bridge out of cardboard and it bent in the middle. What should Atlas do FIRST?

After looking at a broken build, Atlas wants to make it better. What is the BEST next step?

Mia's toy ramp is tilted too much and the ball shoots right off the end. Mia makes the ramp less tilted. Which step is she doing?

Recap

When a build falls, builders do not give up. They try, then look closely to find what went wrong, then change one thing, then try again. Looking is how you learn, and changing one thing at a time shows which fix worked. A fall is not failing, it is a clue that helps you get better.

Reflect

How does looking at a broken build help you fix it?