​

Regenerative finance works when capital, operations, evidence, and learning stay connected.

This playbook explains how Kokonut combines regenerative agriculture with open-source coordination infrastructure. The model is not:

• a promise that every regenerative farm will become self-funding;
• a universal legal wrapper;
• a tokenized substitute for farm operations;
• a guarantee of ecological or financial outcomes;
• a requirement that every record go on-chain;
• a blueprint that should be copied without local adaptation.

It is a repeatable coordination pattern for connecting:

1. a real farm and local operating authority;
2. a shared farm-development methodology;
3. transparent capital governance where shared treasury funds are involved;
4. structured operational and MRV records;
5. governed review and publication;
6. analytics and decision support;
7. optional public provenance;
8. learning that can improve the next farm.

The goal is not to financialize regeneration. The goal is to make capital, evidence, responsibility, and long-term stewardship easier to coordinate around real regenerative assets.

---

​

What problem this playbook addresses

Regenerative projects often have several hard problems at the same time. A farm may need:

• patient capital before long-cycle crops mature;
• short-cycle production to support cash flow;
• local operating capacity;
• clear agreements among land, labor, capital, and coordination contributors;
• a way to distinguish plans from actual results;
• consistent field and financial records;
• credible ecological evidence;
• governance for shared capital;
• partner reporting;
• a way to learn from one farm without pretending another farm is identical.

Those are not one problem. Kokonut treats them as connected but distinct systems.

---

​

The model in one view

No single layer replaces the others.

• capital does not replace agronomy;
• a DAO vote does not replace local farm authority;
• a database does not replace evidence quality;
• an attestation does not replace external verification;
• an AI agent does not replace an authorized reviewer;
• a Framework does not make different farms identical.

---

​

The five operating layers

​

1. Local farm and asset layer

Every implementation begins with a specific place. That means:

• land tenure or access;
• local operators;
• water;
• climate;
• crop suitability;
• labor;
• infrastructure;
• community relationships;
• market channels;
• legal agreements;
• local risks.

The farm is not an abstraction underneath the Web3 system. It is the system that the rest of the infrastructure exists to support.

​

2. Framework layer

The Kokonut Framework provides shared structure for:

• describing farms;
• planning development;
• applying regenerative principles;
• thinking across multiple forms of value;
• recording assumptions;
• connecting operations to evidence;
• learning across farms.

Its core design principle is:

Interoperability, not uniformity.

The current Framework includes four development phases:

1. Planning & Preparation
2. Production & Regeneration
3. Consolidation & Expansion
4. Continuous Operations

These phases organize work. They do not guarantee a farm will progress on a fixed schedule.

​

3. Capital-governance layer

Kokonut’s live Moloch DAO on Gnosis Chain provides one mechanism for governing shared DAO capital and DAO-level rights. Its authority is deliberately narrower than “govern the farm.” The Moloch layer can govern matters such as:

• treasury allocation;
• membership;
• $vKKN issuance;
• Loot recognition;
• DAO-funded work;
• governance parameters;
• other DAO-scoped commitments.

It does not automatically control:

• day-to-day agronomy;
• local labor decisions;
• scientific validity;
• evidence review;
• legal land ownership;
• every partner relationship.

Read the Moloch boundary →

​

4. Governed intelligence and evidence layer

Kokonut Intelligence is the current open-source platform for:

• farm operations;
• financial records;
• environmental records;
• MRV;
• analytics;
• reports;
• evidence relationships;
• partner views;
• attestations;
• agent-assisted workflows.

Its canonical record lifecycle is:

draft → submitted → verified → published

That lifecycle is about authorized workflow state. It is not itself scientific certification.

​

5. Contribution and automation layer

Contributors, Guilds, software, and agents can help with:

• technical implementation;
• evidence review;
• dashboards;
• documentation;
• finance;
• governance;
• partnerships;
• reporting;
• analysis;
• workflow automation.

The rule is:

Responsibility can be distributed without making authority ambiguous.

A contributor or agent may prepare work. The relevant domain still determines whether the work is accepted, published, funded, or acted upon.

---

​

Adelphi is the reference implementation — not universal proof

Kokonut Adelphi is the first farm used to operationalize the Framework in the Dominican Republic. The current documentation describes:

• 15,725 m² total mapped area;
• 13,838 m² agricultural area;
• a mixed crop and poultry model;
• syntropic / agroforestry design;
• a four-phase development process;
• public farm records and MRV workflows;
• a crop and gross-revenue forecast used for planning.

Adelphi is valuable because it exposes real coordination problems:

• capital arrives before some crops mature;
• infrastructure and water matter;
• forecasts require assumptions;
• crop cycles behave differently;
• data collection has to survive real field conditions;
• market access cannot be inferred from a target-market field;
• governance and farm operations need separate authority boundaries;
• impact claims need evidence.

---

​

Forecasts are useful because they can be tested

The current Adelphi crop model includes a combined modeled gross crop revenue of roughly $149,111/year under its documented assumptions. That number is:

• a planning model;
• a mixed-maturity snapshot;
• gross revenue;
• sensitive to yield, loss, cycle frequency, price, establishment, and market access.

It is not:

• realized revenue;
• profit;
• EBITDA;
• distributable cash;
• guaranteed household income;
• guaranteed DAO income;
• an investment return.

Read the forecast assumptions → The correct loop is: A regenerative-finance system becomes more credible when it gets better at replacing assumptions with actuals.

---

​

Economic arrangements must be explicit

The current repository contains a known inconsistency in Adelphi’s public-goods allocation documentation. Some Framework/farm pages model a 10% gross-revenue public-goods assumption. Older ReFi Playbook pages describe a separate 40% operator / 40% public-goods / 20% Kokonut Network allocation. Those are materially different models. This is itself an important ReFi lesson:

If the economic agreement is unclear, the tokenomics are not the problem yet — the agreement is.

For any new farm, document:

• who contributes land;
• who operates the farm;
• who contributes cash or equipment;
• who carries operating risk;
• what gets repaid;
• what is revenue vs. profit;
• what reserves are required;
• whether a public-goods allocation exists;
• when distributions can happen;
• who can change the arrangement;
• what legal agreement makes it enforceable.

---

​

Evidence before claims

The ReFi value proposition becomes weaker, not stronger, when blockchain language is used to overstate evidence. Kokonut’s current evidence model separates several things that older documentation sometimes collapsed together. An attestation can establish provenance. It does not automatically prove:

• causality;
• carbon-credit eligibility;
• biodiversity-credit eligibility;
• regulatory compliance;
• financial performance;
• scientific validity.

For Kokonut, the durable MRV sequence is:

observe → structure → review → publish → attest when useful → interpret

Read the MRV methodology →

---

​

Why on-chain components are optional, not decorative

Blockchain infrastructure is useful when it solves a real coordination problem. Examples include:

• transparent DAO treasury state;
• inspectable proposal execution;
• durable public attestations;
• cryptographic evidence references;
• shared contract rules;
• agent/service identity;
• auditable transaction history.

It should not be added merely to make a farm sound more “ReFi.” A good design asks:

What coordination problem requires a public ledger here?

If the answer is “none,” the record may belong in the governed off-chain data layer.

---

​

What is reusable and what must stay local

​

Reusable infrastructure

These parts are designed to travel more easily across farms:

• four-phase Framework;
• Common Data Schema baseline;
• evidence lifecycle;
• forecast-vs-actual discipline;
• Kokonut Intelligence;
• open-source APIs and data tooling;
• contribution workflows;
• proposal patterns;
• dashboard/reporting patterns;
• optional attestation architecture;
• agent safety boundaries.

​

Locally adapted decisions

These should not be copied blindly:

• crop mix;
• planting design;
• water strategy;
• farm economics;
• labor model;
• land agreement;
• legal entity;
• tax treatment;
• cooperative structure;
• market channels;
• certification pathway;
• community-benefit model;
• public-goods allocation;
• governance scope;
• privacy rules;
• evidence methods.

Replication should preserve the interfaces, not copy the farm.

---

​

A practical replication path

A new community does not need every Kokonut component on day one. A safer sequence is:

---

​

What the playbook can help you design

---

​

What this playbook cannot decide for you

It cannot determine:

• whether a specific farm investment is financially attractive;
• whether a crop is agronomically suitable for your land;
• whether a local legal structure is compliant;
• whether a token or economic arrangement is a security;
• whether an ecological claim qualifies for a regulated credit;
• whether a community accepts the proposed governance model;
• whether an external funder will finance the project;
• whether a forecast will become an actual;
• whether a second farm will reproduce Adelphi’s outcomes.

Those require the relevant local, legal, financial, agronomic, scientific, community, and governance review.

---

​

Current maturity of the model

---

​

What “success” should mean

A successful ReFi implementation is not merely:

• more tokens;
• more dashboards;
• more attestations;
• more governance proposals;
• a higher composite score.

A stronger definition is:

• the farm becomes operationally healthier;
• local operators have clear authority;
• financing matches the farm’s time horizon;
• assumptions become measurable;
• records become more reliable;
• evidence becomes easier to inspect;
• public claims become more precise;
• contributors know what they are responsible for;
• shared capital becomes more accountable;
• future decisions improve because previous outcomes were recorded honestly.

The finance is regenerative only if the coordination system helps the underlying place, people, and productive asset become more resilient over time.

---

​

How to use the rest of this playbook

---

​

Canonical references

---

​

Open-source implementation

Use the implementation repository that actually owns the behavior you need. For live DAO balances, proposals, membership, contract state, farm records, or deployment details, use their current authoritative interfaces rather than a static snapshot in this playbook.

---

​

Partnership and replication

If you are evaluating Kokonut for:

• a new regenerative farm;
• a community agriculture program;
• a cooperative;
• a public-goods initiative;
• an NGO or foundation program;
• a ReFi ecosystem;
• an open-source integration;
• a research or MRV partnership;

start by identifying which part of the model you actually need. You may need the Framework without the DAO. You may need the data layer without token governance. You may need evidence workflows without public attestations. You may need a local cooperative structure that looks nothing like Adelphi’s agreements.

Replication should begin with the local problem, not with the stack.