> 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/templ.md). # What is a Templ? *See* [*docs.templ.fun*](https://docs.templ.fun/) *for more info!* ## What is a Templ? A **Templ** is an onchain membership group and coordination tool built on Base with Templ.fun. Each Templ includes: * Paid entry through an access token. In our case, that token is SANGUIS. * Automatic fee splits on every join; burn, treasury, member pool, and protocol * Shared treasury * Governance through proposals and voting * Integrated chat In short, a Templ gives a token community more structure. It adds **skin in the game**, aligned incentives, a transparent treasury, and executable governance. #### In Vitalis * **The Heart** is our first and sovereign Templ — the core organ of the Body. * **Sub-Templs** (organs) are additional Templs created for specialized functions. For example, the Generative Organ will support virality and growth. The Brain Organ will support innovation and grants. All sub-Templs remain **metabolically dependent** on The Heart for major funding. This creates a natural hierarchy while still allowing experimentation and specialization. This structure is central to our vision of a living, self-sustaining digital organism. --- # 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/templ.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.