> 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/sensor-grid.md).

# Sensor Grid

The Sensor Grid is a programmable logic environment within SensorVM — acting as both a deployment system and an economic layer for robotic workflows. Developers can build, deploy, and optionally tokenize logic blocks inside containers, giving them full control over execution and visibility.

Unlike traditional smart contract platforms, the Grid is built specifically for robotic workflows, containerized logic, and data anchoring.

***

#### 🧩 Grid at a Glance

* Public or private logic containers
* Tokenized modules (monetize per use or access tier)
* Role-based control: dev, device, or verifier
* Anchoring of container hashes to the chain

***

#### 📚 Subpages:

* [What is Sensor Grid](https://sensorvm.gitbook.io/sensorvm-docs/project-utility/sensor-grid/what-is-sensor-grid)
* [Revenue Stream](https://sensorvm.gitbook.io/sensorvm-docs/project-utility/sensor-grid/revenue-stream)

The Sensor Grid is where robotic logic becomes composable, traceable, and monetizable — powering the decentralized execution layer for smart machines.


---

# 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/sensor-grid.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.