# Mechanics

**Mechanics**

SensorVM operates through a set of layered mechanics that allow machines to act deterministically, validate their own actions, and interface with the blockchain through clean modular interactions.

The mechanics ensure that logic remains secure, repeatable, and verifiable — regardless of hardware constraints or network status.

***

#### 🧱 Functional Components

| Component            | Role                                                                     |
| -------------------- | ------------------------------------------------------------------------ |
| **Trigger**          | Starts execution when a sensor input or condition is met                 |
| **Logic Block**      | Contains specific action or task logic (e.g. validate GPS, run timer)    |
| **Execution Engine** | Runs the logic and records the output internally                         |
| **Verifier**         | Hashes and signs the result, checks against predefined rules             |
| **Transmitter**      | Sends output to blockchain, local cache, or cloud fallback if configured |

***

#### 🧩 Modularity

Each logic unit:

* Is versioned and hash-stamped
* Can be public, private, or token-gated
* Can call other units in sequence or parallel
* Can store state temporarily or anchor it permanently

This creates a plug-and-play ecosystem for robots and IoT systems to swap and compose complex behaviors.

***

#### 🔐 Internal Validation

SensorVM ensures trustless output using:

* Cryptographic proof-of-execution (PoX)
* Signature timestamps from device keypairs
* Deterministic output logic — same input = same hash

No human approval or third-party oracle is required for validation.

***

SensorVM mechanics give machines structure, safety, and autonomy — without adding bloat or centralization.

**It’s not just how the machine acts — it’s how the system proves it acted right.**


---

# Agent Instructions: 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://sensorvm.gitbook.io/sensorvm-docs/project-utility/what-is-sensor-vm/mechanics.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.