> For the complete documentation index, see [llms.txt](https://docs.onefootballclub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onefootballclub.com/7-the-network/7.3-building-an-open-football-ecosystem.md). # 7.3 Building an open football ecosystem The end state is an open football ecosystem that any participant can adopt while keeping its own direct relationship with the fan. The network does not replicate audiences, but connects them through a shared layer of identity, reputation, and utility – allowing each club, brand, or partner to benefit from a richer view of fandom without giving up its own audience. This matters because football fandom is too diverse to be owned by one platform. As more participants join, each one contributes a different source of fan activity and gains access to a broader football context in return.That is the compounding effect of an open network. Every new fan adds context. Every new integration adds utility. Over time, the network becomes something no institution could build alone: a football ecosystem where fans are recognized across experiences, partners can build on verified participation, and value can move more freely between the people and organizations that create it. --- # 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://docs.onefootballclub.com/7-the-network/7.3-building-an-open-football-ecosystem.md?ask=&goal= ``` `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.