> For the complete documentation index, see [llms.txt](https://thesanctum.gitbook.io/thesanctum-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thesanctum.gitbook.io/thesanctum-docs/mechanics/vessels.md). # The Five Vessels The shrine has exactly five vessels. This is a fixed structural constant, not a configuration knob. Every vessel is a **public Solana wallet** whose address is disclosed on the [Vessels](/thesanctum-docs/surfaces/vessels.md) page. ## Roles Vessels are numbered 1 through 5 and each has an operational role. The exact role assignment is visible on the Vessels page; typical roles include: * **Inflow / gateway** — receives movements from the outside world. * **Operations** — day-to-day working balance. * **Distribution staging** — where per-epoch payouts are prepared before the Ledger-signed batch goes out. * **Reserve** — long-horizon holding. * **Ceremonial** — small, symbolic balance used for chronicle-worthy actions. Roles may be re-assigned; the *number* of vessels does not change. ## Why five Five is small enough that every vessel can be watched at a glance and large enough to encode differentiated roles. It also matches the shrine's visual vocabulary — five stones, five sigils. ## Guarantees * Every vessel address is public. * Every balance is read live from the Solana RPC. * The shrine will never invent a balance for an unconfigured slot. * No vessel key lives on the server. See [Data Sources & Trust Model](/thesanctum-docs/mechanics/data-sources.md). --- # 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://thesanctum.gitbook.io/thesanctum-docs/mechanics/vessels.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.