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

# Governance

KnoxFS is what you could call a Decentralized Autonomous Organisation (DAO). The project is community driven and being led by a small group of teammembers that invest their time completely voluntarily.  There is no official leadership or governance structure in place, nor is there a corporate entity established. The products that are listed in this whitepaper are not owned by KnoxFS. The relationship between KnoxFS and the product owners is best described as a partnership whereas the product owners are entitled to implement KFX into their product and KnoxFS promotes the products as part of the KFX Ecosystem.

There is no more information on this subject yet, other than that we are working on a governance method that could enable investors to influence decisionmaking by casting votes on project related matters.  This could also  involve KFX masternodes.


---

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