Skip to main content

Ecological frameworks help interpret evidence — they do not create it.

Kokonut uses ecological-impact frameworks after farm activity has produced evidence. Two lenses currently appear across the Framework:
  • EBF — Ecological Benefits Framework for organizing ecological-benefit claims;
  • CRISP-style risk review for examining uncertainty that could weaken ecological, climate, financial, operator, or evidence-delivery assumptions.
They should sit above:
  • farm observations;
  • actual measurements;
  • operational records;
  • financial actuals;
  • MRV review;
  • published evidence.
MRV asks what the evidence says. EBF helps organize ecological-benefit interpretation. Risk review asks what could make the interpretation fail, weaken, reverse, or mislead.

Read the EBF source

EBF Commons describes the external framework around Air, Water, Soil, Biodiversity, Equity, and Carbon.

Start with MRV

Follow the evidence lifecycle before applying an ecological-benefit or risk interpretation.

Use the Positive Impact claim ladder

Keep alignment, activity, measured outcome, and impact interpretation separate.

See the live reference farm

Inspect which ecological practices, measurements, forecasts, and evidence gaps currently exist at Adelphi.
Neither EBF nor Kokonut’s CRISP-style risk review is a substitute for the methodology required by a carbon standard, biodiversity-credit standard, environmental regulator, scientific study, certification body, lender, insurer, or other external assurance process.

EBF and risk review at a glance

The old version of this page expanded CRISP as “Carbon Risk Identification and Scoring Principles.” The current repository does not link that expansion to an authoritative external source. This page therefore uses CRISP-style risk review as Kokonut terminology rather than presenting that full name as an established external standard.

Where these frameworks sit

The important ordering is:
evidence first → interpretation second → decision third
Not:
framework → score → proof

EBF — Ecological Benefits Framework

What the external EBF actually organizes

The externally maintained Ecological Benefits Framework describes six interconnected domains:
  1. Air
  2. Water
  3. Soil
  4. Biodiversity
  5. Equity
  6. Carbon
EBF Commons explicitly describes the framework as a shared set of definitions/agreements rather than a data standard or certification. Kokonut should therefore use EBF as:
  • a common ecological-benefit vocabulary;
  • a way to organize evidence;
  • a way to expose gaps across more than carbon;
  • a partner/reporting lens;
  • a comparison structure when semantics are consistent.
It should not be treated as automatic proof that a benefit exists.

The six EBF domains in Kokonut

EBF is broader than ecology in the narrow sense

The Equity domain matters because ecological projects affect people through:
  • land access;
  • ownership;
  • labor;
  • income;
  • participation;
  • distribution of benefits;
  • distribution of costs and risks.
That is also why EBF should connect to the Kokonut Pillars—especially WHO, CONTRIBUTION, RISK, and PUBLIC GOODS.

EBF evidence maturity

An EBF domain can be relevant at different claim levels.
Do not create an “EBF score” merely by counting how many of the six domains are mentioned. Six represented domains are not six achieved benefits.

Kokonut’s 8 Forms of Capital are an internal value-classification lens. EBF is an external ecological-benefit framework. They can overlap without being collapsed.
EBF domains should not be converted into capital units, and capital forms should not be converted into an EBF score without a transparent methodology.

CRISP-style risk review

What Kokonut means by it

Across the current Knowledge Base, CRISP is used as shorthand for a structured risk lens around ecological and carbon-related delivery. Because the repository does not currently provide an authoritative external source for the expansion “Carbon Risk Identification and Scoring Principles,” Kokonut should document the method by what it actually does:
Identify material risks, connect them to evidence, assign ownership and mitigation, and revisit them as the farm changes.
That makes it useful even when no numeric score is appropriate.

Risk categories

A farm-level ecological risk review can include: These categories should be adapted to the farm and claim. They are not a fixed universal taxonomy.

Risk scoring is optional — transparency is not

A risk review can be useful without reducing every risk to one number. A minimum risk record should capture:

If a numeric score is used

Document:
  • scale;
  • weights;
  • formula;
  • evidence inputs;
  • treatment of missing data;
  • thresholds;
  • reviewer;
  • version;
  • sensitivity to changed assumptions.
A number without a transparent scoring method is decoration, not risk analysis.

Relationship to the Pillars of Value

The Pillars already contain RISK. The ecological risk review is a more detailed extension for claims where ecological, climate, permanence, evidence, or external-standard risk is material. This keeps risk connected to the actual claim instead of producing a detached farm-wide score.

EBF and CRISP-style review work together

The two lenses ask different questions. Example:
EBF Soil: a repeated soil indicator improved during the reporting period.
Risk review then asks:
  • Was the baseline comparable?
  • Could rainfall explain part of the change?
  • Was the same method used?
  • Could later disturbance reverse it?
  • Is the reporting period long enough?
  • Is the result being generalized beyond the measured plot?
The risk analysis narrows and contextualizes the benefit claim. It does not erase a real measured outcome, and it does not manufacture one.

Adelphi: EBF interpretation with current evidence boundaries

Adelphi can be mapped across all six EBF domains, but the evidence maturity differs substantially.
Adelphi should not currently be described as having a completed EBF impact score, verified carbon outcome, proven biodiversity restoration, improved watershed condition, or demonstrated community-wide equity outcome unless the corresponding evidence and methodology are actually present.

Adelphi: current risk-review examples


Publication and attestations

Published evidence

A published farm record means it passed the applicable Kokonut lifecycle and is available to approved downstream surfaces. It does not automatically mean:
  • external audit;
  • scientific peer review;
  • regulatory approval;
  • environmental certification.

EAS

An EAS attestation can preserve:
  • signer;
  • schema;
  • timestamp;
  • evidence reference;
  • provenance.
It cannot independently determine whether an EBF benefit or risk conclusion is scientifically valid.

IPFS / Filecoin

Content-addressed storage can preserve evidence artifacts. It is useful where durable public evidence matters. It is not required for every ecological record, and it proves file identity/integrity rather than truth.

A reusable ecological-interpretation record

For a material EBF or ecological-risk statement, capture: This makes the output auditable without pretending the framework itself performed the measurement.

Reporting cadence should follow the evidence

The old page made EBF and CRISP an annual requirement by default. Annual review can be useful. It should not be the only cadence. Different evidence moves at different speeds:
Choose cadence because it matches the claim and method—not because a dashboard wants another data point.

How Kokonut Intelligence can support this layer

Kokonut Intelligence can help:
  • retrieve reviewed records by EBF domain;
  • compare reporting periods;
  • calculate defined indicators;
  • identify missing baselines;
  • flag stale evidence;
  • assemble EBF evidence packets;
  • maintain risk registers;
  • surface changed assumptions;
  • compare forecast vs. actual;
  • draft interpretations for review;
  • link published evidence to attestations.
It should not independently:
  • declare a farm EBF-certified;
  • invent a CRISP standard that has not been documented;
  • create carbon-credit eligibility;
  • convert weak evidence into a high ecological score;
  • hide uncertainty;
  • decide scientific causality;
  • substitute AI confidence for domain review.

Common failure modes


Who should use this layer

Farm operators

Use ecological and risk lenses to decide what needs to be measured, maintained, changed, or mitigated in real operations.

Impact & research reviewers

Check EBF-domain evidence, methods, claim maturity, contribution context, uncertainty, and risk.

Capital governance participants

Use ecological interpretation and risk as decision inputs without treating either as an automatic funding verdict or overriding farm/domain expertise.

Guilds & contributors

Turn ecological evidence gaps and risk mitigations into bounded research, field, data, documentation, or implementation work.

Partners & grant reviewers

Trace ecological claims to source evidence and distinguish external EBF vocabulary from Kokonut’s developing risk-review tooling.

Developers & agents

Preserve framework version, evidence pointers, risk assumptions, scoring methodology if used, and human/domain review.

Current maturity


Continue through the Framework

EBF Commons

Review the external source for the Ecological Benefits Framework and its six ecological-benefit domains.

Positive Impact Methodology

Apply alignment → activity → measured outcome → impact interpretation before making stronger ecological claims.

Pillars of Value

Use WHAT, WHO, HOW MUCH, CONTRIBUTION, RISK, and PUBLIC GOODS to structure value and uncertainty.

8 Forms of Capital

Categorize broader value without collapsing unlike outcomes into one ecological score.

MRV Methodology

Follow the source evidence and review lifecycle beneath EBF and risk interpretation.

Adelphi Physical Systems

Inspect the practices and infrastructure that create ecological hypotheses at the live reference farm.
Ecological frameworks are most credible when they make the evidence and uncertainty easier to inspect—not when their names are used as substitutes for measurement, methodology, or external assurance.