> For the complete documentation index, see [llms.txt](https://docs.oceanenterprise.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oceanenterprise.io/discover/whitepaper.md). # Whitepaper **ABSTRACT** Ocean Enterprise is an open-source software framework and governance model designed to create next-generation data spaces and AI ecosystems. It addresses challenges such as data silos, compliance, control, and value creation by enabling organizations to collaborate efficiently and create value from digital resources at scale without surrendering control. The framework utilizes a federated architecture that combines technical data sovereignty, value creation and exchange, transparency, sovereign deployments and Compute-to-Data capabilities that provide pier-to-pier access control to privately held data. This allows data to be used for computation and AI model training without the underlying intellectual property leaving its owner’s control. Governed by the Ocean Enterprise Collective e.V., a non-profit association, it ensures transparent governance and alignment with key European data standards and regulations. Access the full whitepaper below. {% file src="/files/aaFl8JHREEgEJHcPACKB" %} --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.oceanenterprise.io/discover/whitepaper.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 `build a script that syncs our docs to a CMS` 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.