> For the complete documentation index, see [llms.txt](https://vitalis.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitalis.gitbook.io/docs/manifesto.md). # Manifesto ### Manifesto Vitalis is building something different. Not just another token. Not just another community. We are building a **living digital Body** — a sovereign, self-sustaining organism on-chain. A system that grows, adapts, coordinates, and reproduces through its own internal logic. Each part strengthens the whole. At its core is [**The Heart**](https://templ.fun/heart) — already live, with a [permanent reservoir](https://app.uniswap.org/explore/pools/base/0x9f04e955a216cf250dAA87714932388eA5E6cA7d?chart=price). From it, specialized organs ([sub-templs](/docs/templ.md)) such as the [Bone Marrow](/docs/organ-architecture/bone-marrow.md) (growth & virality) and the future Brain Organ (innovation) We choose long-term coordination over short-term speculation.\ Conviction over farming.\ Metabolic hierarchy over flat democracy. This is an experiment in on-chain sovereignty and living systems. If you share the vision, become part of the Body. --- # 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://vitalis.gitbook.io/docs/manifesto.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.