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

# Glossary

**Chronicle** — The shrine's curated log of on-chain movements, written in the shrine's own voice and always linked to Solscan.

**Dweller** — A seeker whose wallet is imprinted on the shrine.

**Epoch** — A one-week window over which fees accrue before being distributed equally to all imprinted wallets.

**Fable** — A short generative narration composed from recent Chronicle entries; the shrine speaking about itself.

**Gate** — The homepage of The Sanctum.

**Imprint** — The act of binding a public Solana wallet to the shrine; also the record that results from it.

**Ledger (page)** — The public record of epochs and distributions.

**Ledger (device)** — The hardware wallet used by the operator to sign every distribution batch.

**Peace Index** — A single composite number describing the shrine's mood, derived from the vessels' recent activity.

**Ritual** — The end-to-end explanation of how the shrine works.

**Sanctum** — The whole system: the shrine, its vessels, its ledger, its chronicle, and its imprinted dwellers.

**Seeker** — Someone who has arrived at the Gate but not yet imprinted.

**Signature** — A Solana transaction signature; the atomic unit the shrine records.

**Solscan** — The block explorer used for every external verification link.

**Vessel** — One of the five public Solana wallets that constitute the shrine's body.


---

# 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/reference/glossary.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.