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

# Introduction

> *A spirit of peace, trying to become physical.*

The Sanctum is an experimental on-chain art and agent interface built on Solana. It is **not a fund**, **not a custodian**, and does **not accept user deposits**. It watches five disclosed public Solana wallets — its *vessels* — and turns their movement into a ritual of accountability: a ledger, a chronicle, a fable, and a peace index.

This documentation is the canonical reference for how the shrine works, what each surface of the site means, and how the mechanics translate the public chain into the shrine's language.

![The Sanctum — Gate](/files/OZgW1PGLAzMuWCyuegcy)

***

## What the Sanctum is

* **A wallet observatory.** Five public Solana wallets are configured as the *vessels* of the shrine. Every balance, every signature is read live from an RPC endpoint. Nothing is fabricated — if the RPC is silent, the shrine says so.
* **A ritual layer over the chain.** Raw transactions become *movements*. Movements are woven into a *chronicle*. The chronicle feeds a generative *fable*. The whole is measured by a *peace index*.
* **A commitment to imprint.** Seekers can bind their own wallets to the Sanctum. Each binding is a stone. The shrine is being pressed out of the ledger and into physical form, one imprint at a time.
* **Radically transparent.** Every vessel address is public. Every signature links to Solscan. The mystical language is a costume; the numbers are naked.

***

## What the Sanctum is not

* Not a fund, DAO treasury, or investment vehicle.
* Not a custodian — the shrine never touches user funds.
* Not financial advice.
* Not a token launch. Imprinting a wallet does not purchase anything.

***

## The eight surfaces

| Surface                                                 | Purpose                                              |
| ------------------------------------------------------- | ---------------------------------------------------- |
| [Gate](/thesanctum-docs/surfaces/gate.md)               | The homepage — hero, live treasury, ticker, imprint. |
| [Ritual](/thesanctum-docs/ritual.md)                    | How the shrine works, end to end.                    |
| [Treasury](/thesanctum-docs/surfaces/treasury.md)       | Live total across all five vessels.                  |
| [Ledger](/thesanctum-docs/surfaces/ledger.md)           | Fee-share epochs and distributions.                  |
| [Vessels](/thesanctum-docs/surfaces/vessels.md)         | Per-wallet detail cards.                             |
| [Chronicle](/thesanctum-docs/surfaces/chronicle.md)     | Curated log of shrine movements.                     |
| [Fable](/thesanctum-docs/surfaces/fable.md)             | Generative mythic narration of the ledger.           |
| [Peace Index](/thesanctum-docs/surfaces/peace-index.md) | Composite mood measure of the shrine.                |

Continue with [The Ritual →](/thesanctum-docs/ritual.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/readme.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.