> 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/how-verification-works.md). # How verification works *Why a record on Earth LinC can be believed.* A blockchain makes a record **permanent**. It does not make a record **true**. Anyone can write anything to a chain, and it will sit there forever — permanently wrong, if it was wrong going in. Earth LinC is built on the refusal to let that happen. The rule is simple and has no exceptions: > **No real-world ecological action is recorded until an independent, accountable source has confirmed it happened.** ## What this means in practice 1. **A mission does real work for the earth** — restoration, protection, repair. Physical work, in a physical place. 2. **An independent source confirms it** — an accountable organization, separate from the mission itself, attests that the action occurred: what was done, where, and when. Field evidence, not promises. 3. **Only then is it recorded** — the confirmed facts become the **verified-fact layer** carried by the minted station and by every NaviStar Cast from it: what was done, where, when, confirmed. That layer is immutable. No one — not the holder, not us, not YuCROWN — can edit it afterward. 4. **AI never touches it.** AI on Earth LinC composes the *expression* — the living page a person authors. It never generates, alters, or asserts verified fact. This boundary is constitutional in the protocol. ## What "verified" does — and does not — claim * It **does** mean: an independent, accountable source confirmed this specific action occurred. * It does **not** mean: a carbon offset, a neutralization claim, or a promise about future outcomes. A NaviStar records that something real was done — that is the whole claim, and it is enough. ## Why we say this part out loud Most of what a protocol does can be open and trustless — minting, holding, transferring, reading, building. But "did this really happen in the physical world?" cannot be answered by code. It needs an accountable source willing to stand behind the answer. Naming that honestly — *here is the one place trust enters, and here is who carries it* — is what makes everything else believable. See **The anchor**. *** *Part of Trust & Verification: How verification works · The anchor · Transparency & impact.* --- # 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/how-verification-works.md?ask=&goal= ``` `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.