Lesson 4 of 64 in this sequence

Not completed yet

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

Learning path

Step 4 of 64

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 4/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

Decomposition: Breaking Big Problems Apart · A large problem becomes solvable by splitting it into smaller, named subtasks. · 1B-AP-11

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 Debugging: Find and Fix Your Program's Bugs; 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-into-parts
Route source: Fallback route needs owner canonical review
Candidate route: /library/kids/computer_science/en/lesson/breaking-problems-into-parts

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

Decomposition: Breaking Big Problems Apart

with Byte

Byte the friendly robot stands at a big paper checklist on the classroom wall, using a marker to split one giant glowing task card labeled 'Clean the Classroom' into three smaller labeled cards, smiling at the camera.

Define decomposition as splitting one big task into smaller named subtasks.
Break a real everyday goal into three or more smaller named steps.
Give each subtask a short clear name that tells exactly what it does.
Explain why smaller named parts are easier to solve than one big problem.
Identify which items count as true subtasks versus restating the whole job.

Key terms

Decomposition: Splitting a big job into smaller named parts.
Subtask: One small named piece of a job.
Big job: The whole large task you start with.
Name: A short label saying what a step does.

Naming Each Part

When you split a big job, give each part a clear name. A name like wipe the desks tells you and your friends exactly what to do. Good names help everyone share the work, so nobody feels lost or has to guess what comes next in the job.

Real Subtasks Versus the Whole Job

A real subtask is a true piece of the big job, like pick up trash. Saying finish the classroom is not a subtask, because that is just the whole job said again in new words. A good subtask names one small action you can really do by itself.

Going Smaller and Smaller

Sometimes a part still feels too big to do. When that happens, you can decompose it again into even smaller parts. For example, wipe the desks can split into spray the desks and dry the desks. Keep splitting until every little piece feels easy and just right.

Worked examples

Decompose the big job: set the table.

Put a plate at each seat.
Put a fork by each plate.
Put a cup at each seat.

Answer: Three small named subtasks make the big job easy.

Is feed the class pet a real subtask?

Check if it is one small named action.
Yes, it names a clear thing you can do.

Answer: Yes, feed the class pet is a real subtask.

Hi, I'm Byte! Sometimes a job feels HUGE — like 'clean the whole classroom.' That feels too big to even start, right? When something feels too big, smart problem-solvers use a trick called decomposition. That is a long word that just means: break the big problem into smaller parts, and give each part a name. Watch me decompose 'clean the classroom.' I split it into named subtasks: 'Pick up trash,' 'Push in chairs,' and 'Wipe the desks.' Each one is small. Each one has a name that tells exactly what it does. Now I can do them one at a time — and when all the small parts are done, the BIG job is done too! Here is an important thing to remember: each subtask must actually be a piece of the big job, not just the big job repeated in different words. Saying 'finish the classroom' is NOT a subtask — it is just the whole job again! Naming each part really helps. A name like 'Wipe the desks' tells you and your friends exactly what to do, so you can share the work and never feel lost. And if a part still feels too big — decompose it again! For example, 'Wipe the desks' could split further into 'Spray the desks' and 'Dry the desks with a cloth.' You can always go smaller until every piece feels just right.

Activity

Byte is decomposing the big job 'Set up the art corner.' Tap all the choices that are real subtasks of that job.

Practice

Decompose the job clean your desk into three small named parts.

Give one good name for a subtask of packing a backpack.

Common mistakes to avoid

Repeating the whole job is a subtaskA real subtask names one small piece, not the whole job again.
Subtasks do not need namesClear names help everyone know exactly what each part does.

Check your understanding

What does decomposition mean in computer science?

The big job is 'Plant a class garden.' Which choice is a real subtask?

Why do we give each smaller part a clear name like 'Wipe the desks'?

Recap

Decomposition splits one big job into smaller named subtasks. Each subtask names one small action you can really do. When all the small parts are done, the big job is done too, and you never felt stuck.

Reflect

What big job at home could you decompose into named parts?