> For the complete documentation index, see [llms.txt](https://docs.frequencychain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frequencychain.org/12.-energy-data-layer-integration/12.1-architectural-positioning.md).

# 12.1 Architectural Positioning

The Energy Data Layer operates between external data sources and the blockchain execution environment. It is designed to ensure that all incoming data undergoes structured validation and verification before being committed on-chain.

The data flow can be understood as a multi-stage pipeline:

* data is generated from external systems such as IoT devices or enterprise platforms
* the data is processed and validated through oracle mechanisms
* verified data is anchored on-chain
* smart contracts consume the data for execution

This architecture ensures that data integrity is preserved while maintaining compatibility with deterministic blockchain execution.

<figure><img src="https://1067227230-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLwgYv3BMBEDsxgxyrgOJ%2Fuploads%2FPj7jYJZQ6KvLIg48mXck%2FArchitectural%20Positioning.jpg?alt=media&amp;token=da4baa13-5e80-46fc-a459-ef38fbe55a8b" alt=""><figcaption></figcaption></figure>


---

# 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://docs.frequencychain.org/12.-energy-data-layer-integration/12.1-architectural-positioning.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.