PV NatureBiodiversityActive · v1.0

PV Nature Biodiversity Standard

Community-led biodiversity certification. Issues Plan Vivo Biodiversity Certificates and is designed to stack with PV Climate carbon credits.

Registry
PV
Sector
Biodiversity
Credit
PVBC · biodiversity unit
Issued as
org.hypercerts.claim.activity

The issued hypercert is a batch of PVBC 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.

ScopesBiodiversityCommunity-ledNature-positive

Overview

PV Nature is Plan Vivo's biodiversity standard for community led projects that restore or protect ecosystems. Its methodology and data protocol set out how projects establish a baseline, measure biodiversity change, and quantify benefits, and certified projects can issue and sell Plan Vivo Biodiversity Certificates. Certificate revenue funds project operating costs and local communities. A certificate represents a quantified, verified biodiversity outcome calculated under the Plan Vivo Biodiversity Certificate calculation protocol.

Sources: methodology document · Plan Vivo

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/pv-nature

{
  "$type": "org.broadlistening.policy.methodology",
  "code": "PV Nature",
  "name": "PV Nature Biodiversity Standard",
  "registry": "Plan Vivo (PV)",
  "sector": "Biodiversity",
  "creditType": "biodiversity",
  "status": "active",
  "version": "1.0",
  "scopes": [
    "Biodiversity",
    "Community-led",
    "Nature-positive"
  ],
  "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/pv-nature-bio-baseline",
    "at://did:plc:bl0adl1sten1ngp0l1cyreg/org.broadlistening.policy.schema/pv-nature-bio-monitoring"
  ],
  "graph": "at://did:plc:bl0adl1sten1ngp0l1cyreg/org.broadlistening.policy.graph/pv-nature",
  "issuesAs": "org.hypercerts.claim.activity",
  "workScope": "at://did:plc:bl0adl1sten1ngp0l1cyreg/org.hypercerts.workscope.cel/pv-nature-scope",
  "rights": "at://did:plc:bl0adl1sten1ngp0l1cyreg/org.hypercerts.claim.rights/pv-nature-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)
Community field observationsLocally-driven teams record indicator taxa with digital tools.
dwc.occurrence.scientificNamedwc.occurrence.recordedBydwc.occurrence.individualCount
Auditable digital evidenceThe standard premiums high-integrity, auditable data & evidence.
dwc.occurrence.imageEvidencedwc.occurrence.audioEvidenceac.audio
Habitat / vegetation conditionEcosystem condition is tracked over time.
dwc.measurement.floraMeasurement.canopyCoverPercentdwc.event.habitat
Baseline vs monitoring changeCertificates quantify measurable difference for ecosystems.
dwc.occurrence.eventDatedwc.measurement.measurementDate

How the evidence becomes a credit

Community-measured biodiversity change vs a baseline → PV Biodiversity Certificate; stackable with PV Climate.

Indicators sourced from the PV Nature methodology document; mapped onto the GainForest Darwin Core lexicons.

More from PV