> For the complete documentation index, see [llms.txt](https://docs.theos.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theos.io/the-proposition.md). # The Objectives The core economic rules are like the DNA for a large component of our collective social and economic behaviour. A minor, well-crafted change in this DNA would yield immense transformation of the emergent social behaviour and impact of our species - reshaping our social relations, our economic output, and our collective impact on the planet. This document outlines an holonic, peer-to-peer social coordination protocol. Its core rules are designed to emergently fulfil the following objectives: * Facilitate prosocial coordination, favouring co-creation and collaboration over competition * Fulfil psycho-physiological needs, ensuring wellbeing for all humans * Regenerate the planetary resource ecology, attaining widespread abundance * Remain viable across locations and through time, respecting the local and global boundary conditions of place and planet To realise such a design without falling into the trap of reinventing the prevailing macroeconomic system, we must begin from a clean set of fundamental assumptions. To this end we adopt a tabula rasa approach, where we start by revising our assumptions about our relationship with the world. --- # 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.theos.io/the-proposition.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.