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

# Publishing with GitBook

This repository is the canonical documentation source for BIFY Commerce, BIFY SDK, and BIFY RWA.

## Repository Setup

1. Create a GitBook space.
2. Enable GitHub Sync.
3. Connect the `BIFY-RWA-Docs` repository.
4. Configure GitBook to use `README.md` as the landing page.
5. Configure GitBook to use `SUMMARY.md` as the navigation structure.

The repository root is the documentation root. The `README.md` and `SUMMARY.md` files in this directory are the files GitBook should use.

## Product Separation

* Commerce documentation is under `commerce/`.
* The BIFY SDK documentation is under `commerce/bify-sdk/` because the SDK is a Commerce integration.
* RWA documentation is under `rwa/`.

Do not place Commerce SDK guidance, Commerce contracts, or Commerce APIs in the RWA section. Do not describe the BIFY SDK as an RWA integration.

## Local Preview

GitBook Cloud is the reference presentation environment. A local Markdown preview can be used for link and content checks, but it will not reproduce GitBook Cloud's navigation, search, typography, or theme behavior exactly.


---

# 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://bify.gitbook.io/rwa-docs/reference/gitbook.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.