> For the complete documentation index, see [llms.txt](https://sensorvm.gitbook.io/sensorvm-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sensorvm.gitbook.io/sensorvm-docs/project-utility/key-information/technical-hiearchy.md).

# Technical Hiearchy

**Technical Hierarchy**

SensorVM follows a structured system design that balances simplicity, modularity, and security. Each layer in the hierarchy serves a distinct function — from handling device input all the way to issuing smart contract-based outputs.

***

#### 🧱 Layered Architecture Overview

| Layer | Component                    | Purpose                                                                          |
| ----- | ---------------------------- | -------------------------------------------------------------------------------- |
| 1     | **Device Input Layer**       | Captures real-world signals (motion, temperature, events, etc.)                  |
| 2     | **SensorVM Execution Layer** | Processes raw input through logic modules, validates actions                     |
| 3     | **Grid Logic Layer**         | Tokenized logic blocks housed in containers, versioned and optionally public     |
| 4     | **Scrappy AI Layer**         | Offers optimization suggestions, flow validation, and logic debugging            |
| 5     | **Smart Contract Bridge**    | Sends results, proofs, or hashes to blockchain for action (e.g., payments)       |
| 6     | **Access Control Layer**     | Uses $SVM token holdings/locks to gate usage tiers, assign permissions           |
| 7     | **Dashboard/API Layer**      | External interface for users, devs, and partners to interact with deployed logic |

***

#### 🔐 Flow Example (End-to-End)

```plaintext
Device triggers → Logic runs → AI assists (optional) → Output validated → Proof sent → Payouts/actions issued
```

This layered model ensures:

* Data flow is deterministic and traceable
* Security is enforced at each transition point
* Machines can be both users and validators of network actions

***

SensorVM isn’t a monolith — it’s a stack of precise components designed to turn autonomous machine logic into verifiable blockchain events.

**It’s hierarchy with purpose. Built for execution, not abstraction.**


---

# 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, and the optional `goal` query parameter:

```
GET https://sensorvm.gitbook.io/sensorvm-docs/project-utility/key-information/technical-hiearchy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.