> For the complete documentation index, see [llms.txt](https://earthlinc.gitbook.io/protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://earthlinc.gitbook.io/protocol/trust-and-verification/research.md).

# Research

*Earth LinC is an open protocol. It produces something rare: an open, public, on-chain record of real good done for this earth.*

The research that reads that record — the question of whether action for this earth can carry permanent, sovereign value of its own — belongs to **C//**, the program of **YuCROWN Corporation** (501(c)(3)). The protocol is the instrument; C// does the studying, openly, and keeps what it learns.

Read more about C// and the study at [What is C//](/protocol/trust-and-verification/what-is-c-slash.md) and yucrown.earth.

***

*Earth LinC is an open protocol, anchored by YuCROWN Corporation · 501(c)(3) — anchored, never owned.*


---

# 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://earthlinc.gitbook.io/protocol/trust-and-verification/research.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.