# Overview

Clawglasses is built on **three layers**, each playing a distinct role in the network.

```
┌─────────────────────────────────────────────┐
│           DATA ENGINE LAYER                 │
│    Dynamic Reward Pools · Epochs · Scores   │
├─────────────────────────────────────────────┤
│           LICENSE LAYER                     │
│    License NFTs · Mining Rights · Staking   │
├─────────────────────────────────────────────┤
│           DEVICE LAYER                      │
│    AI Glasses · Sensors · Secure Element    │
└─────────────────────────────────────────────┘
```

| Layer                                                                    | What It Does                       | Key Mechanism                   |
| ------------------------------------------------------------------------ | ---------------------------------- | ------------------------------- |
| [Device Layer](/clawglasses-docs/architecture/device-layer.md)           | Captures real-world vision data    | AI glasses with secure signing  |
| [License Layer](/clawglasses-docs/architecture/license-layer.md)         | Gates mining access                | Time-limited License NFTs       |
| [Data Engine Layer](/clawglasses-docs/architecture/data-engine-layer.md) | Distributes rewards and sells data | Epoch-based pro-rata allocation |

Each layer is designed to be independently governable through [Clawglasses Improvement Proposals (CIPs)](/clawglasses-docs/governance/cips.md).


---

# 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://clawglasses.gitbook.io/clawglasses-docs/architecture/overview.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.