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

# Governance Model

Fightly AI is designed to grow through community-driven decision making. Governance is conducted through the $FIGAI token, allowing holders to participate in shaping the direction of the network.

Votes cover a range of proposals, including upgrades to the security AI, adjustments to economic parameters, partnerships, and long-term development priorities. Unlike centralized providers, where decisions are dictated from the top down, Fightly AI allows its community to set the rules that guide the ecosystem.

Governance is not only a symbolic feature but also a mechanism to guarantee transparency and accountability. Decisions are recorded on-chain, ensuring that participants can verify outcomes and hold decision makers accountable. This model builds trust, aligns incentives, and ensures that no single party can monopolize the future of the network.


---

# 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://fightly-ai.gitbook.io/fightly-ai-whitepaper/governance-model.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.