Tebu v4BiodiversityActive · v4.0

Voluntary Biodiversity Units

Each Tebu represents 10 m² of preserved or restored ecosystem, sold once and held for at least 20–30 years of permanence.

Registry
TER
Sector
Habitat banking
Credit
Tebu · 10 m²
Issued as
org.hypercerts.claim.activity

The issued hypercert is a batch of Tebu credits recorded at once, comparable to a registry issuance batch. It carries weighted contributors, a work scope and a rights record, so any app in the ATProto Collective Funding Ecosystem can read it natively.

ScopesBiodiversityHabitat banking

Overview

The Protocol for the Issuance of Voluntary Biodiversity Units, version 4.0, defines how Terrasos generates Biodiversity Units, known as Tebu, through conservation and restoration projects. It sets requirements and procedures for the quantification, issuance, and monitoring of units, using factors such as ecosystem rarity, connectivity, threat and climate change vulnerability, project duration, and a social factor recognizing communities and nature stewards. One Tebu represents 10 square meters of preserved or restored ecosystem maintained under technical, financial, and legal conditions that ensure long-term permanence.

Sources: methodology document · Terrasos

01 · Roles

Standard Registry

role · registry

Owns the policy, approves participants, anchors each issuance to its evidence.

Project Proponent

role · proponent

Registers the project and submits monitoring reports.

Validation & Verification Body

role · vvb

Independently validates the design and verifies monitored data.

02 · Policy graph

10 nodes

The workflow as an explicit directed graph. In Graph each column is one role, so you can see who acts at each step; every node names the org.broadlistening.policy.block.* def it resolves to plus its input and output record. Data flow switches to a lineage view that makes explicit what data each node needs and makes, with dependency arcs tracing every record back to the node that produced it, including where the Darwin Core occurrence + measurement records feed in. Hover to trace, click to inspect; revise edges (dashed) send work back.

Hover to trace · click to inspect

Standard Registry
Project Proponent
Validation & Verification Body
Issue hypercert

Issue biodiversity credits

Standard Registry

A hypercert batching the biodiversity credits issued for the period, anchored to the bundle.

Lexicon
org.broadlistening.policy.block.issue
Input
org.hypercerts.collection + the computed total
Output
org.hypercerts.claim.activity

Node kinds in this graph

  • Role selectorg.broadlistening.policy.block.roleSelect
  • Request documentorg.broadlistening.policy.block.requestDocument
  • Revieworg.broadlistening.policy.block.review
  • Persistorg.broadlistening.policy.block.persist
  • Computeorg.broadlistening.policy.block.compute
  • Aggregateorg.broadlistening.policy.block.aggregate
  • Issue hypercertorg.broadlistening.policy.block.issue
  • Provenanceorg.broadlistening.policy.block.provenance

control-flow event

revise (sends back)

03 · Generated lexicon records

The records this methodology compiles to, ready to write to a PDS. The first tabs are the new policy engine records; the ★ claim.activity tab and those after it are reused ATProto Collective Funding Ecosystem records (org.hypercerts.*): the issued hypercert batch, its rights, an example verification attachment and a retirement receipt. The ◈ dwc.occurrence and ◈ dwc.measurement tabs are the Darwin Core field evidence the monitoring node writes; see the section below.

org.broadlistening.policy.methodology/terrasos-tebu

{
  "$type": "org.broadlistening.policy.methodology",
  "code": "Tebu v4",
  "name": "Voluntary Biodiversity Units",
  "registry": "Terrasos (TER)",
  "sector": "Habitat banking",
  "creditType": "biodiversity",
  "status": "active",
  "version": "4.0",
  "scopes": [
    "Biodiversity",
    "Habitat banking"
  ],
  "roles": [
    {
      "id": "registry",
      "name": "Standard Registry",
      "permission": "Owns the policy, approves participants, anchors each issuance to its evidence."
    },
    {
      "id": "proponent",
      "name": "Project Proponent",
      "permission": "Registers the project and submits monitoring reports."
    },
    {
      "id": "vvb",
      "name": "Validation & Verification Body",
      "permission": "Independently validates the design and verifies monitored data."
    }
  ],
  "schemas": [
    "at://did:plc:bl0adl1sten1ngp0l1cyreg/org.broadlistening.policy.schema/terrasos-tebu-bio-baseline",
    "at://did:plc:bl0adl1sten1ngp0l1cyreg/org.broadlistening.policy.schema/terrasos-tebu-bio-monitoring"
  ],
  "graph": "at://did:plc:bl0adl1sten1ngp0l1cyreg/org.broadlistening.policy.graph/terrasos-tebu",
  "issuesAs": "org.hypercerts.claim.activity",
  "workScope": "at://did:plc:bl0adl1sten1ngp0l1cyreg/org.hypercerts.workscope.cel/terrasos-tebu-scope",
  "rights": "at://did:plc:bl0adl1sten1ngp0l1cyreg/org.hypercerts.claim.rights/terrasos-tebu-rights",
  "createdAt": "2025-01-01T00:00:00.000Z"
}

04 · Schemas

Biodiversity Baseline

schema · bio-baseline

Baseline state of the metric basket before the intervention.

FieldTypeReqDescription
ecoregionstringOne of the world's terrestrial / marine ecoregions.
habitatstringHabitat type under the conservation objective.
areaHanumberProject area in hectares.
metricBasketarrayTaxa / indicators measured, the basket reflecting the objectives.
baselineMediannumberMedian baseline value across the basket.
methodstringSurvey method and sampling effort.

Biodiversity Monitoring

schema · bio-monitoring

Re-measurement of the metric basket for a monitoring period.

FieldTypeReqDescription
projectrefstrongRef to the registered baseline.
periodstringMonitoring period (ISO-8601 interval).
monitoredMediannumberMedian monitored value across the basket.
upliftPctnumberMedian % uplift (or avoided loss) vs baseline.

05 · Field evidence (Darwin Core)

A biodiversity credit is only as credible as the field-evidence timeline behind it. The baseline and monitoring nodes above don't just file a document: they write a species-occurrence timeline with GainForest's Darwin Core lexicons (app.gainforest.dwc.*). The verification node then audits those records, and the compute node reads them to quantify the unit.

The evidence record chain

Written atBaseline surveyMonitor upliftVerified atValidate designVerify uplift

Metrics & indicators the methodology requests

Indicator / metricHow the methodology requests itDarwin Core field(s)
Ecosystem type & rarity (IUCN RLE)Ecosystems act as the biodiversity indicator; rarity/threat is a core factor.
dwc.event.habitatdwc.occurrence.habitatdwc.occurrence.conservationStatus
Ecosystem condition / habitat qualityCondition sets the proportion of area preserved vs restored.
dwc.measurement.floraMeasurement.canopyCoverPercentdwc.measurement.floraMeasurement.vitalityStatus
Landscape connectivity & heterogeneityConnectivity / heterogeneity is a quantified factor (updated in v4).
dwc.event.decimalLatitudedwc.event.decimalLongitudedwc.event.locality
Threat & climate-change vulnerabilityThreat analysis strengthened in v4 to include climate vulnerability.
dwc.occurrence.dynamicPropertiesdwc.occurrence.conservationStatus
Area preserved / restoredUnits derive from the area under conservation (10 m² each).
dwc.event.sampleSizeValuedwc.event.sampleSizeUnit
Long-term monitoring milestonesUnits release gradually over ≥20 yr permanence on verified milestones.
dwc.event.monitoringProgrammedwc.event.monitoringFrequencydwc.event.eventDate

How the evidence becomes a credit

1 Tebu = 10 m²; issuance scaled by rarity, connectivity, threat/climate-vulnerability, duration, condition & a social factor, released on verified milestones.

Indicators sourced from the Tebu v4 methodology document; mapped onto the GainForest Darwin Core lexicons.