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

# Strategic Outlook

## Governance Roadmap

AbraFi intends to transition to a decentralized governance structure by 2026. This transition involves the establishment of a governance council and the eventual handover of protocol control to the DAO. Future documentation will detail the specific voting mechanisms and technical implementations of this decentralized framework.

## Key Addresses

This document contains forward-looking statements regarding future product features, performance, and strategies. Such statements are subject to known and unknown risks, including market volatility and regulatory developments. AbraFi assumes no obligation to update these statements beyond legal requirements.


---

# 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://abrafi.gitbook.io/abrafi-docs/overview/strategic-outlook.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.