Goal
The result the system is trying to maintain or reach.
Curriculum topic
Feedback happens when a system checks the result of an action and uses that information to adjust what it does next.
Why it matters
A command can start movement, but feedback makes movement correctable. Games use score and collision signals; robots use sensor readings; people use visible results to improve a design.
Real-world connection
A person steering a bicycle makes many small corrections after seeing where the bicycle goes. A robot patrol can do something similar with repeated sensing and turning.
The connection shows where the idea returns; it does not claim every advanced application is taught in this first topic.
Math and logic kernel
The result the system is trying to maintain or reach.
Information about the current result.
How current behaviour differs from the goal.
A change intended to reduce that difference.
Small examples
Move a sprite back when it leaves a region.
Adjust direction after reading a surface.
Change movement after measuring timing.
Use sound or display to make a system state visible.
Program connections
Commands, sensors, simple electronics, simulations, and physical systems organized around Sense, Decide, Act.
Beginner-friendly programming through original games, animations, simulations, and interactive stories.
A future practical and critical program about patterns, predictions, prompts, limits, and human judgment.
Common mistakes
The system changes repeatedly without checking whether it helped.
The result swings past the goal.
The system reacts after the useful moment has passed.
Students cannot explain what the system is trying to maintain.
Lesson and projects
Design a patrol that repeats, senses a changed world, and uses feedback to recover.
Open projectMeasure reaction time, store results, and decide what makes a timing test fair.
Open projectBuild a compact platform game where collision, jumping, safe surfaces, and game state must agree.
Open project