> For the complete documentation index, see [llms.txt](https://docs.premia.blue/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premia.blue/the-premia-protocol/governance/operator-and-facilitator-role.md). # Operator & Facilitator Role Vision: Public Redux of Economic Market & Investment Access \[PREMIA] The Premian Ecosystem operated by the Premian Republic is a cooperative effort spanning many contribution groups and individuals across the globe. The Premian Republic acts as fiduciary for the ecosystem and manages direct and coordination costs to achieve the shared vision. The Premian Republic directs its efforts to contributors focusing on building conscious, open, & contestable smart markets. The collaborative enterprise only asks that all share a similar cultural outlook and uphold the following virtues: Equality of wealth, Equity of opportunity, and Economic justice. If these hold true to you and you would like to join our contribution network, please don't hesitate to reach out. As we hold transparency as a core tenet, economic costs associated with fulfilling this doctrine are summarized [here](broken://pages/fbSt3ZAybePsZ9wauuPr). --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.premia.blue/the-premia-protocol/governance/operator-and-facilitator-role.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.