What a Robot Is and Isn't

One-sentence summary

A robot is a system that senses its surroundings, decides based on what it senses, and acts on that decision; if any of these three links is missing, a device may be automatic but it is not really a robot.

Why does this matter?

In everyday language, the word "robot" is used very loosely. Sometimes a washing machine is called a robot, sometimes a toy car, sometimes an app on a phone. This is where the confusion begins.

If we know clearly what a robot is, we ask the right questions when we design our own projects: "Does this device really sense its surroundings?", "Does its decision change with the information it receives?" These questions form the foundation of every robot we will build from the next lesson onward.

Think back to the mini automatic watering prototype you built in the previous lesson. There was a sensor measuring soil moisture, a threshold value, and a pump that turned the water on. That prototype was already using the idea at the very heart of this lesson: sense, decide, act.

Defining a robot: a three-link chain

In the introductory lesson we saw that robots work in a sense–decide–act loop. Now let's look at these three links a little more closely.

Sensing

A robot "feels" the world through its sensors. A distance sensor detects an obstacle ahead, a light sensor detects brightness, a moisture sensor reads the soil, and a button senses your touch. Without a sensor, a robot is blind; it moves without knowing what is around it.

Deciding

A robot compares the information from the sensor with a rule. This rule is usually an "if" statement: "If the obstacle ahead is closer than 10 centimetres, stop." The decision link is the robot's brain. If we write different rules for the same sensor reading, the robot behaves differently.

Acting

A robot expresses its decision in the outside world through an action: it turns a motor, changes direction, lights an LED, or makes a sound. Without this link, a robot would be a box that thinks but can do nothing.

Let's see the three links together in pseudocode:

Repeat forever
  distance = read front sensor    # SENSE
  if distance < 10 centimetres    # DECIDE
    stop the motors               # ACT
    turn on the red LED
  otherwise
    move forward

The same logic looks like this in a short piece of Arduino (C++) code:

void loop() {
  int distance = readDistance();   // SENSE
  if (distance < 10) {             // DECIDE
    stopMotors();                  // ACT
    digitalWrite(LED_RED, HIGH);
  } else {
    moveForward();
  }
}

The pseudocode and the Arduino code look different, but the logic is exactly the same: sense, decide, act.

Not every automatic device is a robot

This is the most important distinction of the lesson. "It works automatically" does not mean "it is a robot." Let's see the difference through two examples.

Example 1: A robot vacuum really is a robot

Think about a robot vacuum. Before hitting a wall, it senses the obstacle with a distance sensor. It decides, "There's an obstacle ahead, let me change direction." Then it acts by turning its wheels and changing its route. If the floor is still dirty, it passes over it again; when the battery runs low, it returns to its dock. All three links are here: sense, decide, act. That is why a robot vacuum is a real robot.

Example 2: A timer lamp is not a robot

Now think about a timer lamp that turns on automatically at 7:00 p.m. and off at 7:00 a.m. This lamp is automatic; it runs on its own, but it does not sense its surroundings. It does not know whether anyone is in the room or whether it is dark outside. It only looks at the clock. Its decision does not change with the environment; every day it does the same thing at the same time.

This lamp does not make a decision that "moves" with the world either; it simply repeats a preset time. Because the sensing link and the real decision link are missing, it is not a robot — it is only an automatic device.

Borderline cases

Some devices fall in between. A street lamp that turns on when it detects motion uses a sensor (sense) and a simple rule (decide). This is one step closer to a robot than the timer lamp; but because it behaves like a single switch and does not adapt to its environment, most people would not fully call it a "robot." What matters is not memorising a strict boundary, but learning to think by asking about the three links.

A short comparison table:

The remote-controlled car is an interesting example: it moves, but you make the decisions — it does not sense and decide on its own. That is why it does not count as a full robot either.

Mini activity

Let's do a thinking exercise that needs no electronics or motors. Take each device below one by one and answer three questions for each:

1. Does it sense its surroundings? (Which sensor?)
2. Does its decision change based on the information it receives?
3. Does it respond with an action?

If you answer "yes" to all three, the device is very close to a robot. If a link is missing, write down which one.

Devices to examine:

• An automatic sliding door (a shop door that opens as you approach)
• A toaster
• A line-following robot
• A classic flashlight
• An air conditioner that runs based on temperature

Draw a small table in your notebook and mark the three links for each device. The answer is not a single word; write a short reason too. For example: "A toaster measures time with a timer but does not truly sense how toasted the bread actually is."

Common mistakes

Thinking "everything automatic is a robot"

A device running on its own does not make it a robot. The timer lamp is the clearest example. To be a robot, the sensing link and a real decision link must also be present.

Confusing a decision with a timer

"Turn on at 7:00 p.m." looks like a decision, but it does not take the environment into account. A real decision produces different results based on changing sensor information.

Thinking a remote-controlled vehicle is a robot

Moving alone is not enough. If you make the decisions, then you are the robot and the vehicle is just a tool. A robot must be able to make its own decisions.

Forgetting the sensor

Sometimes when designing a project we start straight away with "let me turn the motor like this." If we skip the sensing link, we are left not with a robot but with a mechanism that merely moves.

Safety note

This lesson is mostly conceptual, but as soon as you start testing the three links on a real robot, movement, motors, and current come into play. Watch out for the following:

• A moving robot can pinch, fall, or run into things. Before testing, clear a safe, empty area around the table or on the floor.
• Keep your fingers, hair, and cables away from the wheels and gears. Spinning gears can catch hair and cables.
• Always run the first tries at low speed. Be ready in case the robot moves unexpectedly.
• Do not power motors directly from a microcontroller pin. Use a motor driver and a separate, low-voltage battery pack for the motors; give the two circuits a common ground.
• Never use mains electricity (wall sockets). Only low-voltage batteries.
• Whenever motors, soldering, or cutting tools are involved, always work with an adult.

Lesson summary

• A robot is a system that senses, decides, and acts; all three links must be present together.
• Working automatically alone is not enough to make something a robot.
• A robot vacuum is a robot because it has all three links; a timer lamp is not, because it lacks sensing and a real decision.
• A remote-controlled vehicle moves but is not a robot, because a human makes the decisions.
• Even though pseudocode and Arduino code look different, the "sense–decide–act" logic stays the same.

Check questions

1. What are the three basic links that define a robot?
2. Why is a timer lamp not considered a robot?
3. Give an example of the robot vacuum's "deciding" link.
4. Why is a remote-controlled car not exactly a robot?
5. Write two safety precautions to take when testing a moving robot.

Answers

1. Sensing (feeling the environment with a sensor), deciding (comparing the information against a rule), and acting (responding with something like a motor or an LED).
2. Because it does not sense its surroundings and its decision does not change with the environment; it just repeats the same task at a preset time. The sensing and real decision links are missing.
3. Decisions made from sensor information, such as "There's an obstacle ahead, let me change direction" or "My battery is low, let me return to the dock," are valid examples.
4. Because it moves but does not make its own decisions; a human takes over the sensing and deciding links. A robot must be able to make its own decisions.
5. Examples: clear a safe empty area, test at low speed, keep fingers and hair away from the gears, use a motor driver with a separate battery pack (any two).

Source and verification note

For “What a Robot Is and Isn't”, verification focuses on whether the relationship between Why does this matter? and Sensing remains consistent across examples. Robot behaviour cannot be explained by code alone; mechanical structure, power system, sensor placement and surface conditions must be evaluated together. Test results should be recorded over several runs on the same course.

Next lesson

Basic Parts of a Robot: We will get to know, one by one, the chassis, motors, sensors, controller, and power source that make up a robot.