> For the complete documentation index, see [llms.txt](https://read.systemarobotica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://read.systemarobotica.com/part-1-natura-robotica/2.-robots-vs.-machines.md).

# 2. Robots vs. machines

Now that we’ve defined a robot, it would help to elaborate on the distinction this definition affords robots as compared to machines.

The distinction between a machine and a robot can be nuanced and hard to distinguish. However it is the capability of making decisions based on sensory inputs and data and taking actions autonomously based on those decisions that differentiates robots from machines.

Let’s illustrate with some examples:

{% hint style="info" %}
**Water Sprinkler**

A basic water sprinkler system that is programmed to operate at certain times of day and automatically turns on to water the garden, would be classed as a machine. This is because its operation is based on pre-programmed instructions and a single sensor input without having the ability to make decisions in real-time. If however an advanced water sprinkler could adjust its operation based on moisture, humidity, weather forecasts, time of day, or historical data and make real-time changes and actions based on decisions from its sensory inputs and environment, it would be classed as a robot.
{% endhint %}

{% hint style="info" %}
**Exoskeleton Suit**

An exoskeleton suit that can be worn to help augment the wearer's physical capabilities would be classed as a machine, not a robot. This is because the device does not have the capability to take decisions from sensory data and manipulate its environment in real-time. It needs the wearer to physically manipulate it to function. If however, an exoskeleton could operate autonomously, and make decisions based on sensory inputs it would be classed as a robot, even if its main design and form were as a wearable.
{% endhint %}

{% hint style="info" %}
**Telepresence Kiosk**

Today in many hotels you may enter and find a telepresence kiosk at the counter instead of a physically present human to check you in. This kiosk will be "manned" by a remote agent, and will be able to communicate with you through its screen, and even in some cases move about on wheels to better assist customers. Similarly, teleoperated machines that can be controlled remotely through drive by wire or fly by wire capabilities are often conflated with robots. However they are machines not robots. They are not able to autonomously make decisions and change their physical environment based on sensory inputs, as they need to be controlled or operated by humans to function. Should a telepresence kiosk or teleoperated machine have the ability to make decisions in real time and effect change to its environment, then it will be considered a robot, even if it can still be teleoperated.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://read.systemarobotica.com/part-1-natura-robotica/2.-robots-vs.-machines.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.