> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/3.6.0/guardian/standard-registry.md).

# Standard Registry

The Standard Registry (SR) is an accredited authority responsible for creating, managing, and publishing standards, methodologies, and policies on the Guardian platform. It serves as the trusted entity that defines how sustainability-related digital assets (like carbon credits, renewable energy certificates, or other ESG tokens) are structured, verified, and issued.

**Key Functions of the Standard Registry**

1. **Methodology Management**
   * Develops and registers new methodologies for environmental or sustainability processes (e.g., carbon reduction, reforestation, renewable energy tracking).
   * Ensures methodologies align with global compliance frameworks and best practices.
2. **Policy Creation & Governance**
   * Publishes policies that define the rules and workflows for issuing and verifying Verifiable Credentials (VCs) and Verifiable Presentations (VPs).
   * Establishes how data flows between participants (project developers, auditors, validators, and buyers).
3. **Certification Authority**
   * Issues schemas, policies, and credentials that other participants must follow.
   * Provides official recognition and assurance of trust in methodologies.
4. **Ecosystem Enablement**
   * Onboards project developers, auditors, and participants to operate within its defined policies.
   * Ensures transparency, traceability, and standardization across environmental markets.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guardian.hedera.com/docs/3.6.0/guardian/standard-registry.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.