> For the complete documentation index, see [llms.txt](https://docs.hashnetwork.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hashnetwork.io/hash-netwok-provenance/architecture-overview.md).

# Architecture Overview

The Hash Network Provenance architecture ensures transparency and authenticity through a robust architecture:

1. **Hash Network Provenance SDK** integrates seamlessly with AI models (e.g., DALL-E 3, Suno AI, Heygen) and agents (e.g., Truth Terminal, AI16z, AixBT) to enable the creation and recording of provenance data.
2. **Provenance Smart Contracts** on the Hash Network store immutable provenance records, guaranteeing security and trust.
3. **HN Verify SDK** allows clients and external applications to fetch and verify provenance data directly from the Hash Network by interacting with the Provenance Smart Contracts.

This architecture enables real-time validation of AI-generated outputs, ensuring that provenance remains transparent and traceable across all layers.

<figure><img src="/files/ilEJejuw6PSAWWsIKDP2" 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.hashnetwork.io/hash-netwok-provenance/architecture-overview.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.