> For the complete documentation index, see [llms.txt](https://docs.millpont.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.millpont.com/meti-resources/what-is-a-source.md).

# What is a Source?

Description of a Source in the METI framework

## Definition

A **Source** refers to the point of origin of an environmental benefit. For METI, a Source is considered an individual contiguous parcel or facility that is the smallest unit of land with the following characteristics:

1. **A permanent, contiguous boundary**\
   *Example:* A 40-acre field used for regenerative grazing, surrounded by roads or fences that clearly define its edges.
2. **A common land cover and land management**\
   *Example:* A corn field with cover cropping and no-till practices applied across the entire parcel.
3. **Common ownership or group of owners/land managers**\
   *Example:* A pasture owned by a farming cooperative or managed jointly by a family under a single operational agreement.
4. **A common project administrator or project proponent (i.e., Custodian)**\
   *Example:* A reforestation project led by a local conservation NGO overseeing multiple parcels within a watershed program.

These criteria ensure that each Source is distinctly identifiable, manageable, and accurately linked to its environmental outcomes.

## Example

Below is an example of three fields that meet METI’s definition of a Source. Each field represents a distinct, contiguous parcel of land with a defined boundary, consistent land cover and management practices, and shared oversight by a common project administrator (i.e. Custodian). These fields demonstrate how Sources are clearly delineated and aligned with METI’s standards for secure environmental asset tracking.

* **Field ID: 1**\
  *Crop Type:* Corn\
  *Management Practices:* No-Till
* **Field ID: 2**\
  *Crop Type:* Soybeans\
  *Management Practices:* No-Till & Cover Crops
* **Field ID: 3**\
  *Crop Type:* Wheat\
  *Management Practices:* No-Till & Cover Crops

<figure><img src="https://935478215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsOHSoZVLzSuaTRyLHoDS%2Fuploads%2FYhJ55hfPaHEitcsfdh9W%2FScreenshot%202024-11-22%20140553.jpg?alt=media&amp;token=71748cd1-405c-4417-9d86-1af7d9880908" alt=""><figcaption></figcaption></figure>

This example highlights how Sources are identified and differentiated based on specific attributes, ensuring accurate and consistent tracking of environmental outcomes.


---

# 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://docs.millpont.com/meti-resources/what-is-a-source.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.
