> For the complete documentation index, see [llms.txt](https://docs.simulacrum.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simulacrum.network/synthetic-blockchain/organization/indexer/sources.md).

# Sources

## Sources

Sources are where commands are originated. They can be any platform that can be publicly verified, and gives the validator network the ability to confirm that a statement was made by a specific entity. For example, a Source could be a message board, a personally owned website, a social media profile, etc. When determining sources, it is important to consider a few concepts:

#### Identity <a href="#identity" id="identity"></a>

You must be able to confirm the identity of the person making the content

#### Content <a href="#content" id="content"></a>

The content must be publicly verifiable, so that a quorum of validators can verify the content

#### Consistency <a href="#consistency" id="consistency"></a>

Validators must be able to verify the content and get identical results. So they must agree on all metadata associated with any source media.


---

# 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://docs.simulacrum.network/synthetic-blockchain/organization/indexer/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.