> For the complete documentation index, see [llms.txt](https://docs.din.lol/din-cook-data-for-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.din.lol/din-cook-data-for-ai/the-concept/comprehensive-network-architecture/exploring-din-an-in-depth-technical-overview.md).
# Data Layer: All for the Data
"*Every data scientist should spend 80% of their time on data pre-processing and 20% on performing the analysis."*
As shown in Fig 1. , data plays a very important role in the whole AI workflow and is fundamental to AI blockchain—all dAI apps rely on high-quality data. We design and implement the DIN protocol to guarantee the network can obtain high-quality data by adopting an incentivized mechanism.
This chapter will explain how the DIN protocol works for the network participants and how they can be rewarded for participating in the data activity.
Fig 1. AI workflow
---
# 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.din.lol/din-cook-data-for-ai/the-concept/comprehensive-network-architecture/exploring-din-an-in-depth-technical-overview.md?ask=&goal=
```
`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.