> For the complete documentation index, see [llms.txt](https://griffin-ai.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://griffin-ai.gitbook.io/knowledge-base/decentralized-ai-network/griffin-nodes/node-architecture.md).

# Node Architecture

The design of the Full Nodes in the Griffin AI network is structured into three distinct layers: the Connectivity Layer, the Functional Layer, and the Core Layer. Each layer plays a critical role in the operation of the nodes, specifically designed to handle functions essential to the network's performance and to fulfill the intended purpose of the nodes. An overview of the structure of the node is depicted in the figure below.  

<figure><img src="/files/J4bFvzjyS3qNwcAjRlXa" alt=""><figcaption><p>Figure 2: Griffin Node Structure</p></figcaption></figure>

Despite the diversity in the roles of node operators – such as Service Providers (SP), Client Providers (CP), and Guardians – the architecture across all full nodes is identical. Role specific requirements are implemented in dedicated modules within the Functional and Core layers.&#x20;


---

# 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://griffin-ai.gitbook.io/knowledge-base/decentralized-ai-network/griffin-nodes/node-architecture.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.