> 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/organ-architecture.md).

# Organ Architecture

## Organ Architecture

The Body grows through specialized organs, or sub-Templs. Each has a distinct role, but all ultimately depend on **The Heart** for major funding and governance.

### Current and Planned Organs

* [**The Heart**](/docs/constitution-of-the-heart.md) **(**[**Live**](https://templ.fun/heart)**)**\
  The sovereign core. Manages treasury, coordination, and long-term sovereignty.
* [**Bone Marrow**](/docs/organ-architecture/bone-marrow.md) ([Live](https://templ.fun/bone-marrow))\
  Virality and new cell generation engine. Primary referal and burn organ.
* **Brain Organ (planned)**\
  Innovation, ideas, and grant distribution. Designed for innovation with full dependency on The Heart.
* **Future Organs**\
  Memory, refinement, coordination, defense, filtering, and more as the Body evolves.

This creates natural metabolic hierarchy while allowing specialization and experimentation. All major value flows ultimately strengthen the eternal reservoir and the whole 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/organ-architecture.md?ask=<question>&goal=<endgoal>
```

`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.