> 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/how-to-participate.md). # How to Participate ## How to Participate Vitalis is still very early. You can help shape it in a few ways: ### 1. Join The Heart The Heart is the sovereign core of the Body.\ → [Join The Heart](https://templ.fun/heart) **What members can do today:** Make governance proposals, share ideas, and join discussions in chat. Decision-making power expands as trust grows and active cells mature. That pace is intentional. The Heart carries real responsibility. ### 2. Follow Development * Watch for the launch of the **Generative Organ**, the engine for expansion and virality. * Follow documentation and announcements for updates. ### 3. Contribute * Share ideas for new organs (sub templ's) and improvements. * Introduce and spread the vision to people who will understand it. * Participate thoughtfully as more organs come online. ### 4. Be a Cell The strongest contributions come from people aligned with the long-term philosophy: conviction, patience, and responsibility to the whole Body. We are building for durability. If the vision resonates, you are welcome in [The Heart](https://templ.fun/heart). --- # 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/how-to-participate.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.