# Domain Model

## Treetracker Domain Entities

* **Capture**: The data that shows something happened (this is the actual proof, impact proof)
* **Impact Token**: A reference to the capture that can be moved between wallets
  * (**Relative Impact Value** - property of **Impact Token**, computes relative value based on **Capture** data)
* **Wallet**: A container that holds tokens and allows them to be exchanged with other parties
  * **Impact Wallet Map** - shows trees that have been supported by the holder of a given wallet.
* **Impact Asset**: (an entity with social and ecological value)
  * Aggregate Impact Asset: when a ***conservation entity*** has multiple\*\* impact tokens\*\* attached to it
  * Fundamental Impact Asset: Synonym for **Impact Token**
* **Tree:** The main impact asset that Treetracker tracks.
* **Impact Manager**: An organization that is coordinating physical responsibility for the growth of the tree.
  * Responsible for **Impact Manager Map**: her map with all the trees within her project (org map)
  * **Impact Manager Map**: Permanently shows all **Trees** that an **Impact Manager** has or is coordinating.
* **Relative Impact Value Matrix**
  * A table of criteria that computes a relative impact value.
  * Version updates released annually
    * All RIV criteria additions are held for next annual update
* **Relative Impact Value** **(RIV)**: A value that is comparable between impact tokens, a sum of the values ascribed to all impact factors relevant to this token.
  * **Intrinsic Impact Value (IIV)**: The portion of the RIV that comes from the data within or tagged to a **Capture** of an **Impact Asset**. Calculated as a sum of impact values in a matrix, available for each month since the last **Capture**.
  * **Social Impact Value (SIV)**: The portion of the RIV that comes from direct benefit to the ground operator who produces a **Capture** using our platform. Probably a discrete value.
  * **Activity Impact Value (AIV)**: A value we assign based on our idea of the relationship that different types of conservation activities have on *outcomes* for **Impact Assets**
    * Assigned value for each monitoring/ update visit (1)
    * Scaled assigned value for the initial planting (3)

## Useful Explanatory Terms

* An ***impact asset*** is when a ***conservation entity*** has multiple tokens attached to it
  * **Tree** is our currently supported ***conservation entity***
  * An ***impact share*** is one of the multiple ***impact tokens*** attached to a tree
* ***tree proof / proof of planting***
  * Trees interest corporate offset markets (ex. CSR investors)
    * \*\**Tree Proofs*\*\*- held in the web map & traded
    * Proofs of Planting - interchangeable language with *Tree Proofs*
  * Impact tokens for everyday consumer markets (ex. Sustainably run app)
    * Do not trade\_ trees\_ in wallet API
    * Greenstand sells the\_ planting of a tree \_

### Treetracker Domain

* Planter
  * Planter Identifiers
  * Smart Contracts
* Session
* Tree
* Capture

### Related Domains

#### Field Data Domain

* Planter Registration
* Raw Capture
* Raw Session
* Field Transfers

#### Stakeholder Domain

* Stakeholder: { Person, Planting Organization }
* Hierarchical Stakeholder Relationships

#### Wallet Domain

* Token
* Transaction
* Transfer
* Wallet


---

# Agent Instructions: 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:

```
GET https://docs.greenstand.org/overview/introduction/domain-model.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.