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

# Data Sources & Trust Model

The shrine is deliberately narrow about what it trusts and what it computes.

## Sources of truth

| Datum               | Source                           | Verifiable independently?                                   |
| ------------------- | -------------------------------- | ----------------------------------------------------------- |
| Vessel balance      | Solana RPC                       | Yes — Solscan on the vessel address.                        |
| Vessel transactions | Solana RPC                       | Yes — Solscan on the signature.                             |
| Distributions       | Solana RPC (signature)           | Yes — Solscan on the signature.                             |
| Imprints            | Shrine database                  | Partially — the address is public; the record is off-chain. |
| Chronicle entries   | Derived from RPC data, curated   | Yes, via linked signatures.                                 |
| Fable narration     | Generated from Chronicle entries | Prose, not a claim.                                         |
| Peace Index         | Computed from Chronicle entries  | Reproducible from the same inputs.                          |

## What the shrine will never do

* **Fabricate a balance.** If the RPC is unreachable or a vessel is unconfigured, the shrine says so.
* **Custody user funds.** Imprinting stores a public address only.
* **Auto-sign a distribution.** Every payout is signed by a hardware wallet and executed by a human operator.
* **Hide a vessel.** All five vessel addresses are public.

## Operator surface

An admin surface exists for the operator to:

* Set display names for vessels.
* Add operator notes to the Chronicle.
* Trigger epoch close and export chronicle data.
* Test the AI narrator connection.

The admin surface is password-gated and cannot move funds.

## Cache & freshness

* Treasury: refreshes on a short interval (tens of seconds).
* Ticker: refreshes on a longer interval.
* Chronicle, Ledger, Vessels, Peace Index: fetched on navigation with reasonable stale-while-revalidate behaviour.

If a page's timestamp looks stale, hard-reload and check the vessel directly on Solscan.


---

# 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/data-sources.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.