Lesson 1 of 64 in this sequence

Not completed yet

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

Learning path

Step 1 of 64

Start of 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 1/64
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

Breaking a Big Problem into Smaller Steps · Building Programs (Programming) · 1B-AP-11 · decomposition

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: 4 items, 4 answer keys, 4 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: 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 kids 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/kids/computer_science/en/lesson/breaking-problems-apart
Route source: Fallback route needs owner canonical review
Candidate route: /library/kids/computer_science/en/lesson/breaking-problems-apart

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

Breaking a Big Problem into Smaller Steps

with Byte

Byte the robot stands in a busy kitchen holding a giant recipe scroll that reaches the floor, cheerfully pointing at a whiteboard where one enormous cooking task has been split into five neat labeled boxes connected by arrows.

Explain what decomposition means in programming using your own words.
Identify how a large task can be split into smaller, more manageable sub-tasks.
Predict which sub-tasks must happen in a fixed order and which can happen in any order.
Compare solving a big problem all at once versus breaking it into steps.
Apply decomposition by splitting a familiar everyday task into numbered sub-tasks.

Key terms

Decomposition: Breaking one big problem into smaller pieces.
Sub-task: One small step inside a bigger job.
Order: The right turn each step takes.
Step: One small thing you do at a time.

Why We Break Things Apart

A giant job can feel scary. When you split it into small pieces, each piece feels easy. You can do one little step, then the next, then the next. Soon the whole big job is finished, and you never felt lost or stuck along the way.

Which Steps Must Go First

Some steps have to come before others. You cannot tie a bow before you cross the laces. Ask yourself if a step needs an earlier step done first. If it does, keep them in order. If a step does not depend on the others, you can do it whenever you like.

Tiny Pieces Help You Fix Mistakes

When you work one small piece at a time, you can check that each piece works before moving on. If something goes wrong, you only look at the tiny broken piece, not the whole big job. That makes finding and fixing mistakes much faster and far less confusing for you.

Worked examples

Break apart the job: brush your teeth.

Pick up the toothbrush.
Put toothpaste on it.
Brush all your teeth.
Rinse your mouth with water.

Answer: Four small clear steps make the big job easy to follow.

Which step comes first when planting a seed?

You cannot water a seed that is not in the dirt yet.
So digging the hole and dropping the seed must come first.

Answer: Dig the hole and plant the seed first, then water it.

Hey there, I am Byte! Have you ever looked at a really big job and thought, "I do not even know where to start"? That happens to programmers ALL the time. Here is the secret they use: DECOMPOSITION. That is a fancy word that means breaking a big problem into smaller pieces. Each smaller piece is called a sub-task. Imagine you want to tie your shoes. If your program just said "Tie shoes" — a computer would have no idea what to do! But if you break it apart, suddenly it is easy: 1. Hold the left lace in your left hand and the right lace in your right hand. 2. Cross the right lace over the left and pull it under. 3. Make a loop with the left lace. 4. Wrap the right lace around the loop. 5. Pull the right lace through to make a second loop. 6. Pull both loops tight. Now every step is clear and small enough to follow. Computers need instructions this exact — they cannot guess! Here is something important: some sub-tasks MUST happen in a certain order — you cannot tie the bow before you cross the laces! But other sub-tasks can happen in any order. Knowing which is which makes you a sharper programmer. Decomposition also helps YOU. When you break a big problem apart, you can solve one tiny piece at a time, check that it works, then move to the next. If something goes wrong, you only have to look at the small piece that broke — not the whole thing at once. Hint: Ask yourself, "Could I do this step if the step before it was not done yet?" If the answer is no, those steps must stay in order!

Activity

Byte wants to program a robot to bake a tray of cookies. Each step depends on the one before it. Drag the sub-tasks into the correct order so the robot can follow them.

Practice

Break the job of making a bowl of cereal into small steps.

Name one step that must come before pouring the milk in cereal.

Common mistakes to avoid

One big instruction is enoughComputers need many small clear steps, not one giant fuzzy command.
Steps can go in any orderSome steps must come first because later steps depend on them.

Check your understanding

What does DECOMPOSITION mean in programming?

Byte is programming a robot to send an email. Which step MUST come before all the others?

Byte wants to program a robot to clean a bedroom. Which choice shows GOOD decomposition?

A student says, "Decomposition is only useful for computers — people do not need it." Is this correct?

Recap

Decomposition means breaking a big problem into small sub-tasks. Each small piece is easy to do and easy to check. Some steps must stay in order because later steps need earlier ones done first.

Reflect

What big job could you break into smaller steps today?