> 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/start/whos-who.md).

# Who's who

*Three parties stand behind Earth LinC, kept separate on purpose. One is a protocol owned by no one. One is a company that builds tools. One is a charity. Knowing which is which is the point.*

## The protocol — Earth LinC

Earth LinC is a **protocol, not a platform and not a company**. Its two structures — the **station** you create and the **Realm** you hold — and the acts that join them — **Broadcast**, **Mint**, **Cast** — live on a public chain, anchored on-chain at **earthlinc.eth**. No company owns it. What you mint or hold is sovereignly yours under the rules of the chain itself, and it would remain yours if every company around it disappeared.

**YuCROWN Corporation initiated and anchors** the protocol — and builds none of the commercial tooling on top of it. Earth LinC is built to outlive any one organization, YuCROWN included.

→ [Learn more about the protocol](https://earthlinc.earth)

## The tools — Navi, built by Kong

**Navi** is the AI layer of Earth LinC: **NaviCanvas** composes a station, **Naviscape** surfaces a Realm. In the protocol's telling, Navi is simply how a station comes to life and how a Realm is seen.

Factually: **Navi is built and operated by Kong Group LLC**, a commercial company. Composing, plain minting, and every Cast are Kong's commercial services. When you pay for those, you are paying Kong — not YuCROWN, and not "the protocol."

→ [Learn more about Navi and Kong](https://kongrealm.io)

## The program — C//, YuCROWN's

**C//** is the program of **YuCROWN Corporation**, a US 501(c)(3) public charity. It is where good goes: a person's real good for this earth, found and kept and studied. When a station is minted on the **support** route, the whole amount is a **Drop** to YuCROWN — the one charitable moment on Earth LinC. C// belongs entirely to YuCROWN.

→ [Learn more about C// and YuCROWN](https://yucrown.earth)

## How the three hold together

The **protocol** belongs to no one. **Kong** builds the tools that run on it and earns the commercial revenue. **YuCROWN** anchors the protocol and holds the charity. The two rails never blur — in copy or in routing — and money never flows from the charity to the company. The protocol restricts no one — anyone with keys can reach it. The services built on it (Navi and payments → Kong; Support → YuCROWN) are operated by real entities and are subject to applicable law; where each service is available is governed by the Terms of Service, not by the protocol.

***

*Earth LinC is a protocol proposed and anchored by YuCROWN Corporation · 501(c)(3). Navi is built and operated by Kong Group LLC.*


---

# 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/start/whos-who.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.