Lesson 11 of 37 in this sequence

30%

Not completed yet

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

Learning path

Step 11 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 11/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

Test It, Fix It, Make It Better · iterative design · test and improve · engineering process

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 Sorting Materials by Hard, Soft, Bendy, and Stiff; 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/test-and-fix
Route source: Fallback route needs owner canonical review
Candidate route: /library/junior/engineering_making/en/lesson/test-and-fix

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

Test It, Fix It, Make It Better

with Atlas

Atlas the friendly builder kneels at a low worktable, rolling a toy car down a cardboard ramp while children lean in close to watch what happens next.

Test a build and describe what happens.
Tell one part that works and one part that does not.
Change one thing to make the build better.
Test the build again to check whether the change helped.
Compare two designs and say which one works better.

Key terms

test: to use your build and watch carefully what happens
design: one version of the thing you built, like Design One or Design Two
fix: to change one part to make your build work better
compare: to test two designs and see which one works better

Testing Tells You the Truth

When you test a build, you use it and watch closely what happens. Testing is honest. It shows you which parts work and which parts do not. Atlas rolled his car down the ramp and saw the car moved, but it slid off the side. The test told him exactly what to fix. Without testing, you would only be guessing. Real builders always test first so they know what to change next.

Change One Thing at a Time

When you fix a build, change just one thing and then test again. Atlas only added side walls to make Design Two. Because he changed one thing, he knew the walls were what made it better. If you change many things at once, you cannot tell which change actually helped. Fixing one thing at a time, then comparing the new design to the old one, is the smart and steady way to improve.

Worked examples

Atlas rolls a toy car down his ramp and it slides off the side. What should he do step by step?

Test Design One and watch what happens to the car.
Look closely and see the car rolls off the side.
Fix it by changing one thing: add small side walls to make Design Two.
Test Design Two and compare it to Design One to see which works better.

Answer: Design Two with the side walls keeps the car on the ramp, so it works better than Design One.

Hi, I am Atlas! I love to build things. When you build something, you do not have to get it right the first time. That is okay! Builders try, then look, then fix, then try again. First, you test your build. To test means you use it and watch what happens. Look at my ramp — that is Design One. I roll my toy car down it. The car moves! That part works. But the car rolls off the side. That part does not work. Now I think: how can I make it better? I add small walls on the sides. That is Design Two. I changed one thing. Then I test both. I roll the car on Design One — it falls off. I roll the car on Design Two — it stays on! Design Two works better. That is the builder way: test, look, fix, and test again. If your build still has a problem, just change one more thing and compare. You can always make it better!

Activity

Put these four builder tools in the right order to make a build better.

Practice

Describe a build you tested and one thing you would change to fix it.

Put these steps in order: test, look, fix, and test again.

Common mistakes to avoid

Your first try must always be perfect.Builders almost never get it right the first time, so they test and fix to make it better.
You should change everything at once to fix a build.Changing one thing at a time lets you see which change actually made the build work better.

Check your understanding

What does it mean to test your build?

Atlas rolls a car on Design One and it falls off the side. What should he do next?

Your first build has a problem. Is that okay?

Recap

Builders do not have to get it right the first time. They test their build by using it and watching what happens, look at what works and what does not, then fix one thing and test again. Comparing two designs shows which one works better, so you can always keep improving.

Reflect

Why is it helpful to change only one thing when you fix a build?