# Data Validation

After passing Hive.AI’s automated filtering layer, each data submission enters a critical phase of decentralized human validation. This stage ensures that only content of verified relevance, quality, and integrity proceeds into the AI training pipeline. Instead of relying on centralized gatekeepers, Hive.AI applies a dual-layered validation mechanism governed entirely by the community: a Decentralized Verifier Network and a Community Scoring System.

Together, these mechanisms form a transparent and trust-minimized data quality engine. The following diagram outlines the step-by-step path that filtered content follows as it moves through the human validation pipeline:

<pre data-full-width="false"><code>+----------------------------+
|     AI-Filtered Content    |
+-------------+--------------+
              |
              v
+----------------------------+
|  Verifier Layer (Staked)   |
| - Random content batches   |
| - Manual approve/reject    |
+------+------+--------------+
           |      |
<strong>           v      v
</strong>       Approved   Rejected
       Content     Content
               |
               v
+-------------------------------+
| Community Scoring Layer       |
| - HAI token holders           |
| - Random review samples       |
| - Verifier reputation updated |
+-------------------------------+

</code></pre>

This structure ensures each data point is evaluated both by expert contributors (verifiers) and by the broader Hive.AI community, creating a self-regulating cycle of oversight and improvement.

<br>


---

# 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://docs.hiveaitoken.xyz/the-hive-intelligence-pipeline/data-validation.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.