# Page Not Found

The URL `the-hom-dao-whitepaper/hom-nft-feature-2-identity-and-title` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [HOM DAO Governance](https://hom-dao.gitbook.io/hom-dao/the-hom-dao-whitepaper/hom-dao-governance.md)
- [Patent 3: Blockchain-Based Title Assurance System](https://hom-dao.gitbook.io/hom-dao/the-hom-dao-whitepaper/patent-3-blockchain-based-title-assurance-system.md)
- [Patent 4: Vote to Earn (VTE) Decentralized Governance](https://hom-dao.gitbook.io/hom-dao/the-hom-dao-whitepaper/patent-4-vote-to-earn-vte-decentralized-governance.md)
- [Summary of patents](https://hom-dao.gitbook.io/hom-dao/the-hom-dao-whitepaper/summary-of-patents.md)
- [What’s next for HOM DAO?](https://hom-dao.gitbook.io/hom-dao/the-hom-dao-whitepaper/whats-next-for-hom-dao.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://hom-dao.gitbook.io/hom-dao/the-hom-dao-whitepaper/hom-dao-governance.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.

### Option 2 — Browse the documentation index

Full index: https://hom-dao.gitbook.io/hom-dao/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://hom-dao.gitbook.io/hom-dao/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/hom-dao/the-hom-dao-whitepaper/hom-dao-governance.md`).

You may also use `Accept: text/markdown` header for content negotiation.