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

# Reference overview

Start here for the core Hortifuel DAO reference pages and contract docs.

Use the reference section when you need protocol structure fast.

Start with the contract map. Then go deeper into the contract that matches your flow.

### What is in reference

Reference covers:

* contract roles and boundaries
* integration order and safety checks
* asset, token, governance, unit, vault, and redemption docs

### Start here

The main contract reference starts on [Smart contracts](/reference/smart-contracts.md).

Use that page to choose the right contract before you build.

### Best first reads

Start with [`RWARegistry`](/reference/smart-contracts/rwaregistry.md) if you need asset truth.

Start with [`HFUELToken`](/reference/smart-contracts/usdhfuel-token.md) if you need wallet and balance flows.

Start with [`HortifuelGovernor`](/reference/smart-contracts/hortifuel-governor.md) if you need proposals and voting.


---

# 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.hortifuel.com/reference/reference-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.