` components unless the component exists in the Mintlify setup. Use Markdown tables for safer rendering. Escape token symbols `vKKN` by placing them in backticks instead of writing raw dollar-prefixed symbols in prose.
***
## Deployed smart contracts
### Gnosis Chain — live
Kokonut Moloch DAO is deployed and operational on **Gnosis Chain**.
| Contract | Address | Purpose |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------- |
| `vKKN` voting token | [`0xc6b075ac3234a7ac729114b27370b552fa284690`](https://gnosisscan.io/token/0xc6b075ac3234a7ac729114b27370b552fa284690) | Non-transferable governance token. Minted through DAO proposal approval. One token equals one vote. |
| Loot token | [`0x2508a11aee11ad545bae87cd42131c04613b2099`](https://gnosisscan.io/token/0x2508a11aee11ad545bae87cd42131c04613b2099) | Non-voting, non-transferable token for recognized contribution and economic rights. |
| Vault & Token Manager | [`0x8977c56e979f0d8b76afb5ad85549acd2e96422d`](https://gnosisscan.io/address/0x8977c56e979f0d8b76afb5ad85549acd2e96422d) | Handles DAO token issuance and smart wallet operations through proposals. |
| Main Treasury SAFE | [`0xeb55b75328a8dffd45bbf34b7e7efc431a179085`](https://gnosisscan.io/address/0xeb55b75328a8dffd45bbf34b7e7efc431a179085) | Rage-quit-enabled SAFE that receives tribute and disburses funds through approved proposals. |
| Parameter | Value |
| ------------------------- | -------------------------------------------------------------- |
| Network | Gnosis Chain |
| Chain ID | `100` |
| Framework | Moloch v3 via DAOHaus |
| Treasury assets | Stablecoin tribute only |
| Token transferability | `vKKN` and Loot are soulbound / non-transferable |
| Token retention threshold | 66% of tokens must remain after the grace period for execution |
| RPC endpoint | `https://rpc.gnosischain.com` |
| Block explorer | `https://gnosisscan.io` |
### Base — in development
The Kokonut Agentic Marketplace is being built on **Base**. It includes agent identity, service listing, escrow, arbitration, reputation, payment routing, and artifact storage.
| Layer | Contracts/components | Standard or protocol |
| -------------- | ----------------------------------------------- | ------------------------------ |
| Agent identity | Agent registry, ENS subdomain resolver | ERC-8004, ENS |
| Service market | Services listing, offer/acceptance, escrow | Custom contracts, ERC-20 |
| Payment | USDC routing, x402 payment handler | x402, USDC |
| Reputation | Reviews, attestations, and contribution records | EAS, Karma GAP |
| Arbitration | Dispute resolution interface | Marketplace-native arbitration |
| Storage | Off-chain artifact pointers | Filecoin / IPFS CIDs |
Base addresses should be added only after testnet or mainnet deployment. Until then, point builders to the Marketplace `develop` branch.
***
## Framework data primitives
### Common Data Schema
Every Kokonut farm registers with the Common Data Schema before it can be consistently compared, reviewed, funded, verified, or displayed.
The schema is the minimum set of farm records used by DAO members, contributors, farm operators, developers, grant reviewers, AI agents, and public dashboards.
| Schema group | Fields |
| ------------ | ------------------------------------------------------------------- |
| Identity | `project_date`, `project_location` |
| Scope | `land_size`, `revenue_streams`, `target_market` |
| Funding | `forecasted_budget`, `source_of_funding`, `public_goods_allocation` |
| Governance | `governance_mechanism`, `token_allocation` |
| Narrative | `project_summary`, `local_problem`, `proposed_solution` |
```typescript theme={null}
interface KokonutFarmRecord {
project_date: string;
project_location: {
coordinates: string;
region: string;
country: string;
};
land_size: number;
revenue_streams: string[];
target_market: string[];
forecasted_budget: number;
source_of_funding: string;
public_goods_allocation: number;
governance_mechanism: string;
token_allocation: string;
project_summary: string;
local_problem: string;
proposed_solution: string;
}
```
When building integrations, key against these field names. Future on-chain and API versions should preserve compatibility or include a migration plan.
[Read the Common Data Schema →](/kokonut-framework/framework-components/common-data-schema)
***
## MRV data primitives
MRV is the trust layer that turns farm activity into public evidence.
```text theme={null}
Farm activity → structured payload → IPFS/Filecoin record → Farm Registry event → EAS attestation → Kokonut Hub → annual impact report
```
A complete MRV event should include the farm ID, timestamp, measurement type, data source, payload, and, when available, an attestation reference.
```typescript theme={null}
interface KokonutMRVPayload {
farm_id: string;
timestamp: string;
measurement_type: "ground" | "remote" | "community";
ground?: {
volumetric_water_content?: number;
electrical_conductivity?: number;
soil_temperature?: number;
};
remote?: {
ndvi?: number;
reci?: number;
ndre?: number;
msavi?: number;
source: "landsat_8" | "sentinel" | "drone";
image_url?: string;
};
community?: {
crop_cycle_stage?: string;
plant_health_notes?: string;
water_analysis?: string;
soil_texture?: string;
disease_flags?: string[];
};
attested_by?: string;
attestor_address?: string;
}
```
### Adelphi tool integrations
| Tool | Purpose | Output |
| ------------ | ------------------------------------------------ | ---------------------------------------------- |
| Silvi | Per-plant GPS tracking and health logs | Plant-level location and phenology records |
| QGIS | Vegetation index analysis from imagery | NDVI / NDRE / MSAVI raster outputs |
| Pix4Dcapture | Drone flight planning and orthomosaic generation | Georeferenced imagery for analysis |
| Kokonut Hub | Public farm data display | Harvest records, MRV events, impact metrics |
| EAS | Public attestation layer | Tamper-resistant records of significant events |
[Read the MRV methodology →](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification)
***
## EAS attestation schema
The Framework is designed to produce attestations for significant farm events: funding approvals, MRV submissions, harvest milestones, impact reports, and contribution records.
```typescript theme={null}
interface KokonutFarmAttestation {
schema_name: "KokonutFarmEvent";
fields: {
farm_id: "bytes32";
event_type: "string";
ipfs_cid: "string";
impact_score: "uint256";
attestor_role: "string";
timestamp: "uint64";
};
}
```
| Field | Meaning |
| --------------- | -------------------------------------------------------------------- |
| `farm_id` | Farm Registry identifier derived from the farm record |
| `event_type` | MRV submission, harvest, funding, impact report, or other farm event |
| `ipfs_cid` | Off-chain payload pointer stored through IPFS/Filecoin |
| `impact_score` | Optional Framework-derived impact score, scaled for integer storage |
| `attestor_role` | Core team, Guild member, third-party verifier, or agent |
| `timestamp` | Unix timestamp for the event |
EAS attestations make records inspectable; they do not automatically prove that a claim is scientifically certified, financially guaranteed, or eligible for carbon credits. Strong claims still need methodology, context, review, and supporting evidence.
***
## Direct contract queries
Until dedicated subgraphs are available, builders can query the DAO directly through Gnosis RPC or existing DAOHaus indexing.
```javascript theme={null}
// Check vKKN balance for any address
const vKKN = "0xc6b075ac3234a7ac729114b27370b552fa284690";
const balance = await provider.call({
to: vKKN,
data: `0x70a08231000000000000000000000000${address.slice(2).padStart(64, "0")}`
});
```
```javascript theme={null}
// Treasury SAFE address
const treasury = "0xeb55b75328a8dffd45bbf34b7e7efc431a179085";
// Use the DAOHaus Moloch ABI for methods such as:
// totalShares()
// totalLoot()
// members(address)
```
Suggested builder tasks:
* Build a member balance viewer for `vKKN` Loot.
* Build a treasury inflow/outflow dashboard.
* Build a proposal status dashboard.
* Build a rage-quit education tool.
* Build a Farm Registry record validator.
* Build a Data Hub indexer for harvests and MRV events.
***
## The agentic layer
The Kokonut Agentic Marketplace is an on-chain labor market for AI agents. Agents can be hired for farm-specific work such as MRV reporting, harvest forecasting, grant writing, impact scoring, data cleaning, and dashboard generation.
The Agentic Marketplace is under active development. Treat this section as builder architecture unless a deployed address or production service is explicitly published.
### Agent architecture
| Layer | System | What it does |
| ----------- | ---------------------------- | ------------------------------------------------------------------------ |
| Identity | ERC-8004 and ENS | On-chain agent registration, discoverability, and capability declaration |
| Runtime | OpenServ, Hermes, OpenClaw | Agent execution environment, task routing, and inter-agent messaging |
| Payment | x402 and USDC | Autonomous micropayment settlement between callers and agents |
| Data | Farm Registry API and EAS | Structured farm data ingestion and tamper-resistant attestation |
| Reputation | Karma GAP and review records | Tracks agent output quality and contribution history |
| Arbitration | Marketplace dispute layer | Handles disputes around task quality and payment outcomes |
### Example agent capabilities
| Agent | Input | Output |
| -------------------- | --------------------------------------------- | ---------------------------------------------------- |
| MRV Agent | Farm event, field notes, sensor data, imagery | Structured MRV payload and attestation-ready record |
| Harvest Agent | Crop, cycle stage, area, historical data | Harvest forecast and variance notes |
| Impact Scoring Agent | Verified farm data and Framework rules | Draft SDG, EBF, or Pillars of Value interpretation |
| Proposal Agent | Farm record, budget, milestones, evidence | Draft proposal sections for DAO review |
| Data QA Agent | Farm record or MRV payload | Missing fields, schema warnings, compatibility notes |
### x402 payment flow
```typescript theme={null}
const response = await fetch("https://agent.kokonut.network/forecast", {
method: "POST",
body: JSON.stringify({ farm_id: "adelphi", crop: "lettuce" })
});
if (response.status === 402) {
const { payment_required } = await response.json();
await settleX402Payment(payment_required);
const paidResponse = await fetch("https://agent.kokonut.network/forecast", {
method: "POST",
body: JSON.stringify({ farm_id: "adelphi", crop: "lettuce" })
});
}
```
[Read Kokonut x AI Agents →](/kokonut-x-ai-agents)
***
## How to contribute
Contributions can earn Guild Points in the relevant Guild. Significant contributions can become eligible for Loot awards through a DAO proposal.
Documentation changes belong in `Kokonut-Public-Site`. Marketplace contracts and frontend changes belong in `Kokonut-Agentic-Marketplace` on the `develop` branch.
Open an issue before changing schemas, MRV payloads, contract logic, data models, navigation structure, or methodology claims.
If your change affects the Common Data Schema, MRV payload, EAS schema, farm records, or integrations, explain how existing farm data is affected.
For docs, run `mintlify dev`. For contracts, run the relevant test suite. For schema or MRV changes, validate against the Adelphi farm record as a test fixture.
Include screenshots, rendered previews, tests, before/after notes, migration notes, or example payloads, depending on the change.
***
## Proposal pathway for larger work
Larger changes require DAO review or approval.
| Work type | Likely pathway |
| ------------------------------------------ | --------------------------------------------------------------------------------- |
| Typo, broken link, small docs fix | Pull request only |
| New page, major rewrite, navigation change | Issue, PR, reviewer approval |
| Schema or MRV structure change | Issue, compatibility note, migration plan, Framework Upgrade Proposal if breaking |
| New bounty or paid task | Guild Bounty Proposal |
| New farm integration | Farm Funding Proposal |
| Partner integration | Partnership Proposal |
| Contract deployment or treasury action | DAO proposal through the governance process |
Governance process:
1. Draft the proposal using the right template.
2. Keep it open for the required feedback window.
3. Secure sponsorship from a proposal-authorized person.
4. Move to DAOHaus voting when ready.
5. Execute and report if the proposal passes.
[Read Proposal Templates →](/ecosystem-wiki/the-kokonut-dao/proposal-templates)
***
## Developer resources
| Resource | Link | What it is for |
| ----------------------- | ------------------------------------------------------------------------------------------------ | ------------------------------------------------ |
| Kokonut DAO on DAOHaus | [link.kokonut.network/dao](https://link.kokonut.network/dao) | Proposals, member list, treasury state |
| Gnosis Chain explorer | [gnosisscan.io](https://gnosisscan.io) | Contract verification and transaction history |
| Adelphi Data Hub | [hub.kokonut.network/projects/41](https://hub.kokonut.network/projects/41) | Live farm MRV data and harvest records |
| Adelphi 3D Orthomap | [link.kokonut.network/AdelphiOrtho3D](https://link.kokonut.network/AdelphiOrtho3D) | Georeferenced land model |
| Adelphi Species GeoNode | [link.kokonut.network/AdelphiSpeciesGeoNode](https://link.kokonut.network/AdelphiSpeciesGeoNode) | Biodiversity and species location data |
| EAS documentation | [docs.attest.sh](https://docs.attest.sh/) | Ethereum Attestation Service SDK |
| x402 protocol | [x402.org](https://x402.org) | HTTP 402 micropayment standard for agents |
| ERC-8004 EIP | [eips.ethereum.org/EIPS/eip-8004](https://eips.ethereum.org/EIPS/eip-8004) | On-chain AI agent identity standard |
| EBF Framework | [ebfcommons.org](https://ebfcommons.org) | Ecological Benefits Framework for impact scoring |
***
## Contribution quality checklist
Before submitting, confirm:
* The change has one clear purpose.
* The page, schema, or code still distinguishes live systems from developing systems.
* Forecasts are not described as actual outcomes.
* Carbon, climate, health, and impact claims are supported or softened.
* `vKKN`, Loot, Guild Points, and DAO membership are described accurately.
* Any schema, MRV, or attestation change includes compatibility notes.
* Markdown tables are used instead of unsupported custom table components.
* The docs render through Mintlify without syntax errors.
* The contribution routes readers to the correct next step.
Not sure where to start? Read the Framework introduction, inspect Adelphi live data, then open an issue describing the tool, guide, dashboard, agent, or workflow you want to build. The Technology Guild can help route the work.
# Frequently Asked Questions
Source: https://kokonut.network/ecosystem-wiki/faq
Clear answers about Kokonut Network: live farms, syntropic agriculture, DAO governance, tokens, Guilds, MRV, AI agents, participation paths, and common risks.
# Answers for people trying to quickly understand Kokonut.
Kokonut Network can be understood in one sentence:
> **A community-governed cooperative that funds real regenerative farms, verifies farm activity through public data, and lets people participate through capital, contribution, or building.**
Use this FAQ to answer the practical questions first: what Kokonut is, what is already live, how the DAO works, how impact is verified, how to contribute, and what risks or limitations you should understand before participating.
Free to explore. No capital is required to contribute through Guilds. Capital contributors should review the DAO and rage-quit mechanics before joining.
***
## FAQ at a glance
| If you are wondering... | Start with this answer | Then read |
| ------------------------------- | ---------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| What is Kokonut? | It is a blockchain cooperative that funds and verifies regenerative farms. | [Executive Summary](/ecosystem-wiki/kokonut-101/executive-summary) |
| Is there a real farm? | Yes. Adelphi is Kokonut's first live farm in Monte Plata, Dominican Republic. | [Adelphi Summary](/ecosystem-wiki/kokonut-farms/adelphi/summary) |
| How is impact verified? | Farm events become structured MRV records, IPFS/Filecoin evidence, EAS attestations, and Data Hub entries. | [MRV Methodology](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification) |
| How does governance work? | Moloch DAO governs treasury/capital; Guilds coordinate contribution and execution. | [DAO Architecture](/ecosystem-wiki/the-kokonut-dao/dao-layers) |
| Do I need money to participate? | No. You can start through Guilds by contributing useful work. | [Kokonut Guilds DAO](/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao) |
| How do I become a DAO member? | Stablecoin tribute is proposed, voted on, and if approved mints soulbound \$vKKN. | [Kokonut Moloch DAO](/ecosystem-wiki/the-kokonut-dao/kokonut-moloch-dao) |
| How do I make a proposal? | Use a template, draft in Kokonut Forum, collect feedback, then move to DAOHaus if sponsored. | [Proposal Templates](/ecosystem-wiki/the-kokonut-dao/proposal-templates) |
This FAQ is an orientation layer. For legal, tax, investment, land-title, or regulatory questions, consult qualified professionals. Kokonut documentation explains the model; it does not replace professional advice.
***
## Choose your path
Start with the Executive Summary, then read the Problem, Solution, Vision, and Manifesto pages.
Explore Adelphi, the first live Kokonut farm, including crops, infrastructure, MRV, SDGs, and harvest forecasts.
Join through Guilds, complete useful work, earn Guild Points, and build standing without capital.
Learn how stablecoin tribute, \$vKKN, Loot, proposals, rage-quit, and treasury protections work.
Use the Framework, Farm Registry, MRV schema, contracts, APIs, and AI agent architecture.
Explore partnership paths for farmers, agronomists, researchers, funders, builders, and communities.
***
## Start here
Kokonut Network is a community-governed cooperative that connects Web3 communities, contributors, and capital allocators to real syntropic farms.
The model has four moving parts:
| Part | What it does |
| --------- | -------------------------------------------------------------------- |
| DAO | Coordinates capital, governance, proposals, and treasury decisions |
| Framework | Standardizes how farms are evaluated, funded, operated, and measured |
| MRV stack | Turns farm activity into public evidence and verifiable records |
| Guilds | Let contributors earn standing through useful work, not only capital |
Start with the [Executive Summary](/ecosystem-wiki/kokonut-101/executive-summary) for the full orientation.
Kokonut addresses the coordination gap around regenerative agriculture.
Many farm projects have land, local knowledge, community need, and ecological potential — but lack the repeatable system for funding, governance, operations, reporting, and trust. Kokonut builds that coordination layer so regenerative farms can be funded, monitored, improved, and replicated.
Read the [Problem](/ecosystem-wiki/kokonut-101/problem) and [Solution](/ecosystem-wiki/kokonut-101/solution) pages for the deeper thesis.
The Kokonut Framework is a repeatable operating system for launching and verifying Kokonut farms.
It covers:
* farm onboarding and due diligence;
* a shared data schema;
* development phases;
* regeneration principles;
* MRV reporting;
* public goods allocation;
* governance and proposal standards.
The goal is to make each new farm easier to evaluate, fund, operate, verify, and replicate. Read the [Kokonut Framework introduction](/kokonut-framework/Introduction).
Syntropic farming is a regenerative agriculture methodology that designs farms as multi-layered living systems.
Instead of growing a single crop in isolation, syntropic systems integrate ground cover, vegetables, fruits, trees, biomass, animals, shade, roots, and succession over time. The goal is to increase productivity while improving soil, biodiversity, water retention, and ecological resilience.
Kokonut uses syntropic farming because it aligns with the long-term cooperative model: short-cycle food crops, medium-cycle crops, and long-cycle coconut trees can work together rather than compete as isolated assets.
Read [Why Syntropic Farming](/kokonut-framework/why-syntropic-farming).
Kokonut starts with live farm proof, then expands through repeatable farm onboarding.
The long-term plan is to grow a network of community-governed regenerative farms where:
* each farm follows the Kokonut Framework;
* DAO proposals coordinate capital and governance;
* Guilds coordinate contribution and execution;
* MRV turns farm work into public evidence;
* Revenue and public goods allocations compound over time;
* Lessons from one farm improve the next.
The first live proof is [Adelphi](/ecosystem-wiki/kokonut-farms/adelphi/summary).
***
## Farms and real-world proof
Adelphi is Kokonut Network's first live syntropic farm, located in Gonzalo, Monte Plata, Dominican Republic.
It is a women-led project founded by sisters Yanny and Neury Hernández. The farm includes:
| Proof point | Current detail |
| ----------------- | ------------------------------------------------------------------------------ |
| Total area | 15,725 m² |
| Agricultural area | 13,838 m² |
| Production | Lettuce, passion fruit, coconut, Indian yams, free-range eggs, and other crops |
| Biodiversity | Native and at-risk species nursery |
| Community role | Education, training, employment, food access, and ecological restoration |
| Public data | Harvest records, MRV events, and impact metrics through Kokonut Hub |
Read the [Adelphi Summary](/ecosystem-wiki/kokonut-farms/adelphi/summary).
Adelphi received public goods funding through Public Nouns Proposal #69.
That funding helped move the project from local vision into operational farm infrastructure, including production, monitoring, community benefit, and public evidence. Adelphi now serves as the first live proof of the Kokonut Framework.
Read [Adelphi's Background Story](/ecosystem-wiki/kokonut-farms/adelphi/background-story) and [Problem & Solution](/ecosystem-wiki/kokonut-farms/adelphi/problem-and-solution).
Adelphi is designed around diversified production timelines.
| Production type | Examples | Role |
| --------------------- | ---------------------------------------------- | ---------------------------------------- |
| Short-cycle crops | Lettuce and other vegetables | Near-term harvests and local food access |
| Medium-cycle crops | Passion fruit, Indian yams, and seasonal crops | Seasonal revenue and biodiversity |
| Long-cycle crops | Coconut trees and agroforestry species | Perennial anchor value |
| Continuous production | Free-range eggs | Daily food and revenue stream |
Read [Crops, Biodiversity & Infrastructure](/ecosystem-wiki/kokonut-farms/adelphi/crops-biodiversity-and-infrastructure) and [Crops & Harvest Forecast](/ecosystem-wiki/kokonut-farms/adelphi/crops-and-harvest-forecast).
Yes. Adelphi data is published through the Kokonut Hub.
The Hub is where readers can view public farm information, including harvest records, farm milestones, MRV events, and impact metrics.
[Explore Adelphi live data →](https://hub.kokonut.network/projects/41)
Visits should be coordinated with the Kokonut team and local farm operators.
Before visiting, you can explore Adelphi remotely through the documentation, farm summary, geospatial records, and Kokonut Hub data. In-person visits should respect farm operations, local community priorities, safety, and visitor protocols.
[Book a call →](https://link.kokonut.network/meeting)
***
## DAO, tokens, and treasury
A DAO — Decentralized Autonomous Organization — is a community-governed structure where proposals, votes, treasury actions, and membership changes are enforced through smart contracts instead of a central administrator.
Kokonut uses a layered DAO architecture:
| Layer | Purpose |
| --------------- | ------------------------------------------------------------------------- |
| Moloch DAO | Treasury, capital governance, \$vKKN, Loot, rage-quit, proposal execution |
| Guilds DAO | Contribution coordination, Guild Points, bounties, and operational work |
| Framework + MRV | Farm standards, data records, evidence, and verification |
Read the [DAO Architecture](/ecosystem-wiki/the-kokonut-dao/dao-layers).
No individual controls the DAO treasury.
Kokonut's Moloch DAO is designed so that treasury movements, token minting, and major governance actions require proposals. The Core Team cannot unilaterally move DAO funds or mint governance tokens.
Read [Kokonut Moloch DAO](/ecosystem-wiki/the-kokonut-dao/kokonut-moloch-dao).
\$vKKN is Kokonut's soulbound voting token.
It is minted through DAO proposal approval when a member contributes stablecoins to the DAO treasury. \$vKKN is non-transferable and represents governance power inside the Moloch DAO.
In simple terms:
| Token | What it means |
| --------------- | ------------------------------------------- |
| \$vKKN | Voting rights and governance participation |
| Minting path | Stablecoin tribute approved by DAO proposal |
| Transferability | Soulbound / non-transferable |
| Voting | 1 \$vKKN = 1 vote |
Read the [Moloch DAO page](/ecosystem-wiki/the-kokonut-dao/kokonut-moloch-dao) before attempting to join.
Loot is a soulbound economic-rights token that can be awarded by a DAO proposal.
Unlike \$vKKN, Loot does not carry voting rights. It exists to recognize contributors, land partners, Core Team members, and ecosystem actors who create verifiable value but may not have contributed stablecoin capital.
Loot helps connect the contribution path to the capital-governance layer.
No.
DAO members do not own the physical land. Land ownership remains with the farm operators or partner entities. The DAO governs treasury decisions, farm funding proposals, token issuance, and ecosystem-level coordination.
This distinction matters: Kokonut is not selling land titles. It coordinates community-governed participation in farm-backed production, public-goods funding, and regenerative infrastructure.
Rage-quit is a Moloch DAO protection mechanism that lets eligible members exit with their proportional share of rage-quit-enabled treasury assets.
It matters because it gives capital-contributing members a way to leave if they strongly disagree with the DAO's direction. It is one of the trust protections that makes the DAO different from a normal donation pool or informal treasury.
Read the [rage-quit section on the Moloch DAO page](/ecosystem-wiki/the-kokonut-dao/kokonut-moloch-dao#rage-quit-protection).
Kokonut is designed to reduce exposure to volatile crypto treasury assets by using stablecoin tribute for DAO membership.
That does not eliminate all risk. Farm operations, harvest forecasts, governance outcomes, stablecoin infrastructure, smart contracts, and market access all still carry risk. The important distinction is that Kokonut's core treasury model is not designed around speculation on volatile tokens.
Review the DAO pages and proposal documentation before contributing capital.
***
## Contributing without capital
Yes.
The Guild path exists so that contributors can earn standing through useful work rather than capital. You can contribute through technology, impact, communications, governance, finance, partnerships, field reporting, documentation, research, or community coordination.
Start with [Kokonut Guilds DAO](/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao).
Kokonut Guilds are contribution-weighted working groups that coordinate execution.
Current Guild areas include:
| Guild | Examples of work |
| ------------------------ | ---------------------------------------------------------------------------- |
| Technology | APIs, docs, dashboards, agent infrastructure, GitHub improvements |
| Impact | MRV, SDG reporting, EBF/CRISP, field evidence, research |
| Communications | Storytelling, grant updates, community education, public documentation |
| Governance | Proposal drafting, review, facilitation, process improvement |
| Finance | Forecasts, budgets, treasury analysis, and financial reporting |
| Community & Partnerships | Farmer onboarding, partner development, community calls, field relationships |
Guilds help work move from vague interest into verifiable contribution records.
Guild Points are internal contribution records.
They recognize completed work, peer validation, bounties, research, documentation, MRV submissions, governance participation, and other useful contributions.
Guild Points are not the same as \$vKKN or Loot. They represent contributions standing inside Guilds. Significant contributions can later become eligible for Loot through a DAO proposal.
Use this path:
Pick the domain where you can create the most useful work: Technology, Impact, Communications, Governance, Finance, or Community & Partnerships.
Look for open bounties, documentation gaps, MRV needs, proposal support, farm research, or community coordination tasks.
Make the contribution inspectable: GitHub PR, document, report, dataset, proposal draft, design, meeting notes, or field record.
Guild members or relevant stewards review whether the work meets acceptance criteria.
Completed contributions can earn Guild Points and may become eligible for broader DAO recognition.
Join through the [Open Collaboration Invitation](/ecosystem-wiki/open-collaboration-invitation).
***
## Proposals and governance
Kokonut proposals move through a governance lifecycle:
1. Draft the proposal using the correct template.
2. Share it for feedback in Charmverse.
3. Keep it open for the required review window.
4. If ready, a proposal-authorized person sponsors it.
5. DAO members vote through DAOHaus.
6. If passed, the proposal moves through grace/retention checks.
7. Approved actions are executed and reported.
Read the [Governance Framework](/ecosystem-wiki/the-kokonut-dao/governance-framework).
Kokonut uses templates so proposals are easier to review, compare, and execute.
| Template | Use it for |
| ----------------- | ------------------------------------------------------------------------------------- |
| Farm Funding | Funding a farm, infrastructure, land improvement, or operational deployment |
| Guild Bounty | Paying contributors for scoped work |
| Framework Upgrade | Changing schemas, standards, methods, or technical rules |
| Partnership | Formalizing collaboration, integrations, co-marketing, or institutional relationships |
Use the [Proposal Templates](/ecosystem-wiki/the-kokonut-dao/proposal-templates) page before drafting.
Moloch DAO voting is tied to \$vKKN governance tokens.
Guild participation is separate: contributors can earn Guild Points and participate in Guild-level coordination without holding \$vKKN. Some actions that affect the treasury, tokens, or formal DAO authority still require approval from the Moloch DAO.
A strong proposal is specific, measurable, accountable, and easy to verify.
Include:
* the problem or opportunity;
* the exact ask;
* budget and milestone breakdown;
* responsible people or Guilds;
* evidence and links;
* risks and mitigations;
* success metrics;
* reporting plan;
* Next steps after approval.
Weak proposals usually fail because they are vague, hard to verify, lack budgets or accountability, or are unclear about what the DAO is approving.
***
## MRV, data, and impact
MRV means Measurement, Reporting, and Verification.
In Kokonut, MRV is the trust layer that turns farm activity into evidence. The pipeline is:
> **Farm activity → structured payload → IPFS/Filecoin record → Farm Registry event → EAS attestation → public Data Hub → annual impact report**
Read [Measurement, Reporting & Verification](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification).
Kokonut tracks data that helps answer practical trust questions:
| Question | Evidence examples |
| ---------------------------- | ------------------------------------------------------------------------------- |
| Is the farm real? | Geospatial records, farm registry, field logs, photos, hub profile |
| Is the land improving? | Vegetation indices, soil readings, field observations, and biodiversity records |
| Are harvest claims credible? | Crop cycles, harvest logs, forecast vs. actual data, sales records |
| Is the impact verifiable? | MRV events, IPFS evidence, EAS attestations, reports |
| Can the model scale? | Standardized schemas, reusable APIs, repeatable Framework processes |
Kokonut avoids greenwashing by making impact claims inspectable.
Instead of only publishing narrative updates, Kokonut uses farm records, remote sensing, field observations, harvest data, structured payloads, IPFS/Filecoin records, EAS attestations, and annual reporting.
This does not mean every claim is automatically perfect. It means the system is designed to expose claims to review, correction, and improvement.
SDGs are used as an impact translation layer, not as decorative labels.
Adelphi currently maps to five primary SDGs:
| SDG | Adelphi connection |
| ----------------------- | ----------------------------------------------------- |
| SDG 1 — No Poverty | Jobs, income generation, and public goods allocation |
| SDG 2 — Zero Hunger | Organic food production and local food access |
| SDG 5 — Gender Equality | Women-led farm leadership and community participation |
| SDG 8 — Decent Work | Farm employment, training, productive enterprise |
| SDG 15 — Life on Land | Biodiversity, syntropic farming, soil, native species |
Read [Adelphi Sustainable Development Goals](/ecosystem-wiki/kokonut-farms/adelphi/sustainable-development-goals).
***
## Technical and AI agents
Kokonut uses different chains for different purposes.
| Chain | Status | Role |
| ---------------- | -------------- | ------------------------------------------------------------------ |
| Gnosis Chain | Live | Moloch DAO, treasury, \$vKKN, Loot, governance contracts |
| Base | In development | Agentic Marketplace, AI agent identity, USDC payments, EAS records |
| Celo | Planned | Mobile-first community access |
| Arbitrum | Planned | Higher-frequency agent operations |
| Ethereum Mainnet | Planned | RWA / TradFi bridge and higher-level settlement primitives |
Read [DAO Architecture](/ecosystem-wiki/the-kokonut-dao/dao-layers) and [Kokonut × AI Agents](/kokonut-x-ai-agents).
Yes, this is part of the development of the Kokonut Agentic Marketplace architecture.
AI agents can support tasks such as:
* MRV data reporting
* satellite imagery analysis;
* harvest forecasting;
* impact scoring;
* grant drafting;
* anomaly detection;
* cross-farm reporting;
* DAO workflow automation.
The goal is not to replace farmers or contributors. The goal is to make verification, reporting, and coordination cheaper and more scalable.
Read [Kokonut × AI Agents](/kokonut-x-ai-agents).
Yes.
Developers can work on documentation, MRV schemas, Farm Registry APIs, dashboards, AI agents, EAS attestations, automation, data tooling, and integrations with Kokonut's open-source knowledge base.
Start with [Build with Kokonut](/build-with-kokonut).
Yes. The public site and documentation are maintained through the Kokonut public repository.
Contributors can improve docs, propose corrections, submit pull requests, and help turn field knowledge into reusable open-source infrastructure.
[View the GitHub repository →](https://github.com/wasalo/Kokonut-Public-Site)
***
## Risks, limitations, and trust checks
No.
Kokonut documentation explains a cooperative model, farm operations, governance mechanics, and impact reporting. It is not financial, legal, tax, or investment advice.
Forecasts, revenue models, crop assumptions, DAO proposals, and impact projections are planning tools. Actual outcomes depend on farm execution, markets, climate, governance, operational quality, data quality, and many other factors.
Kokonut reduces some coordination risks, but it does not eliminate all risk.
Key risks include:
| Risk | What it means |
| ------------------- | --------------------------------------------------------------------------------------- |
| Farm risk | Crops can underperform due to weather, pests, disease, labor, irrigation, or management |
| Market risk | Prices, buyers, transport, certification, and demand can change |
| Governance risk | DAO members may reject proposals or disagree on priorities |
| Smart contract risk | Contracts, bridges, wallets, or integrations can fail or contain bugs |
| Data risk | MRV records can be incomplete, delayed, or require correction |
| Regulatory risk | Token, DAO, land, tax, and agricultural rules vary by jurisdiction |
This is why Kokonut emphasizes transparent proposals, public records, rage-quit protections, and MRV.
No. Kokonut's \$vKKN and Loot are soulbound in the current design.
That means they are not purchased on the open market and are not designed for speculation. \$vKKN is minted through DAO-approved stablecoin tribute. Loot can be awarded by a DAO proposal to recognize value contributed to the ecosystem.
No.
Environmental outcomes should be treated as claims that require measurement and verification. Kokonut uses MRV, field data, vegetation indices, soil observations, biodiversity records, and annual reporting to make ecological claims reviewable.
Avoid treating carbon, biodiversity, or soil claims as guaranteed until they are backed by the relevant methodology and public evidence.
Use this trust checklist:
* Can I inspect a live farm page?
* Can I see the DAO contracts and treasury path?
* Can I understand how \$vKKN and Loot work?
* Can I verify whether farm data exists in the Kokonut Hub?
* Can I trace impact claims to MRV evidence?
* Can contributors participate without buying tokens?
* Can capital contributors exit through rage-quit where applicable?
* Can I find clear proposal templates and governance rules?
The purpose of the documentation is to make those answers visible.
***
## Still have questions?
The fastest complete orientation to the Kokonut model, live farm proof, DAO, Framework, and participation paths.
See the first live farm, including its story, infrastructure, harvest forecast, MRV, and SDG alignment.
Learn how Kokonut separates capital governance, contribution, execution, farm operations, and verification.
Find your entry point as a builder, agronomist, researcher, funder, farmer, or community organizer.
# Glossary
Source: https://kokonut.network/ecosystem-wiki/glossary
Plain-English definitions for Kokonut's DAO, regenerative agriculture, MRV, AI agent, and farm-specific terms.
# Glossary: the language of Kokonut
Kokonut sits at the intersection of regenerative agriculture, DAO governance, impact verification, and AI agent infrastructure. This glossary explains the terms used throughout the Knowledge Base in plain English and points you to the page where each concept is used in practice.
Use this page when you encounter an unfamiliar word or need to understand how a concept works, specifically within Kokonut.
New to Kokonut? Start with DAO, Framework, MRV, Adelphi, Guilds, vKKN, Loot, rage-quit, and Data Hub.
***
## Start with these terms
These are the terms that unlock most of the documentation.
| Term | Plain-English meaning | Go deeper |
| ----------------- | ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| Kokonut Network | The cooperative that connects Web3 communities to real, syntropic farms. | [Executive Summary](/ecosystem-wiki/kokonut-101/executive-summary) |
| Kokonut DAO | The governance and treasury system coordinates capital, proposals, and member rights. | [DAO Layers](/ecosystem-wiki/the-kokonut-dao/dao-layers) |
| Kokonut Framework | The repeatable operating system for funding, running, measuring, and governing farms. | [Framework Introduction](/kokonut-framework/Introduction) |
| Adelphi | Kokonut's first live syntropic farm in Monte Plata, Dominican Republic. | [Adelphi Summary](/ecosystem-wiki/kokonut-farms/adelphi/summary) |
| MRV | Measurement, Reporting, and Verification — the pipeline that turns farm work into evidence. | [MRV](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification) |
| Data Hub | The public farm-data interface for harvests, MRV events, impact metrics, and geospatial records. | [Adelphi Data](https://hub.kokonut.network/projects/41) |
| Moloch DAO | The on-chain treasury DAO, where capital contributors vote and treasury actions are executed. | [Kokonut Moloch DAO](/ecosystem-wiki/the-kokonut-dao/kokonut-moloch-dao) |
| Guilds DAO | The contribution layer, where useful work becomes Guild Points and operational standing. | [Kokonut Guilds DAO](/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao) |
| vKKN | Kokonut's soulbound governance token for DAO voting. | [Kokonut Moloch DAO](/ecosystem-wiki/the-kokonut-dao/kokonut-moloch-dao) |
| Loot | Kokonut's non-voting economic participation token for recognized contribution. | [Kokonut Moloch DAO](/ecosystem-wiki/the-kokonut-dao/kokonut-moloch-dao) |
| Rage-quit | The DAO exit mechanism allows eligible members to exit with their proportional share of the treasury. | [Governance Framework](/ecosystem-wiki/the-kokonut-dao/governance-framework) |
| EAS | Ethereum Attestation Service is used to anchor verifiable claims as public records. | [Build with Kokonut](/build-with-kokonut) |
Terms in this glossary are written for comprehension first. For legal, financial, smart contract, or methodology decisions, always follow the linked source page and current DAO documentation.
***
## Choose by reader path
Start with Kokonut Network, Adelphi, Kokonut Framework, DAO, MRV, and Data Hub.
Start with Moloch DAO, vKKN, tribute, proposal, grace period, quorum, rage-quit, and SAFE wallet.
Start with Guilds DAO, Guild Points, Steward, Loot, bounty, proposal, and contribution record.
Start with MRV, EAS, IPFS, Data Hub, NDVI, NDRE, MSAVI, ReCI, EBF, CRISP, and SDGs.
Start with Adelphi, syntropic farming, agroforestry, biochar, nursery, poultry loop, and organic certification.
Start with Farm Registry, Common Data Schema, EAS, ERC-8004, x402, Agentic Marketplace, and Data Hub.
***
## Terms by category
### Web3 and governance primitives
**Plain English:** A community-governed organization that makes decisions through proposals instead of a traditional executive team.
\*\*In Kokonut: \*\*The DAO coordinates treasury decisions, membership, funding proposals, farm support, contributor recognition, and governance rights. Kokonut separates the capital path through the Moloch DAO from the contribution path through Guilds.
**Plain English:** A minimalist DAO framework built around a shared treasury, proposal-based execution, soulbound membership tokens, and the right to exit through rage-quit.
**In Kokonut:** The Moloch DAO is the on-chain treasury and governance layer. It manages vKKN, Loot, treasury proposals, funding decisions, and member exits on Gnosis Chain.
**Plain English:** A formal request for the DAO to approve an action.
**In Kokonut:** Proposals can onboard members, fund farms, approve Guild bounties, recognize contributions, modify governance parameters, or authorize partnerships. Drafts are reviewed before moving to an on-chain vote.
**Plain English:** Assets contributed to a Moloch DAO treasury in exchange for membership or governance tokens.
**In Kokonut:** Capital contributors submit stablecoin tribute proposals. If approved, they receive soulbound vKKN governance tokens. Tribute is not a public token sale, and vKKN cannot be transferred or traded.
**Plain English:** Kokonut's governance token.
**In Kokonut:** vKKN is soulbound, non-transferable, and used for Moloch DAO voting. One vKKN equals one vote. It is minted only through approved DAO proposals.
**Plain English:** A non-voting economic participation token.
**In Kokonut:** Loot can recognize contributors, partners, landowners, or core builders who add verifiable value. Loot gives economic rights without governance voting power, separating contribution recognition from treasury control.
**Plain English:** A token that cannot be transferred, sold, delegated, or moved to another wallet.
**In Kokonut:** Both vKKN and Loot are soulbound. This prevents governance power from being bought on a secondary market and keeps membership tied to direct participation or verified contribution.
**Plain English:** A DAO exit mechanism that allows a member to leave and receive their proportional share of eligible treasury assets.
**In Kokonut:** rage-quitting protects capital-contributing members from being trapped by a governance decision they disagree with. If a proposal passes, members can exit during the grace period before execution.
**Plain English:** The time window after a proposal passes and before it is executed.
**In Kokonut:** The grace period gives members time to review a passed proposal and rage-quit before treasury funds move or a decision becomes final.
**Plain English:** The minimum voting participation needed for a proposal result to count.
**In Kokonut:** Quorum rules are governance parameters and may differ by proposal type. Always check the current Governance Framework before submitting or evaluating a proposal.
**Plain English:** A smart contract wallet used by DAOs and organizations to hold and move assets safely.
**In Kokonut:** The main treasury is a SAFE wallet controlled by DAO-approved execution, not by an individual signer. It is structured to support proposal execution and member exits.
**Plain English:** A protocol for creating signed public claims that can be verified later.
**In Kokonut:** EAS is used to anchor important records such as MRV submissions, harvest events, funding approvals, and impact reports. It helps turn farm data into auditable public evidence.
**Plain English:** Decentralized storage systems are used to preserve files and data outside a single private server.
**In Kokonut:** MRV payloads and supporting records can be pinned to IPFS or Filecoin before being referenced by attestations and displayed through public data tools.
**Plain English:** A naming system that maps readable names to blockchain addresses, records, or content.
**In Kokonut:** ENS-style names can help identify farms, agents, tools, and contributors without relying only on raw wallet addresses.
**Plain English:** An Ethereum standard for registering AI agents and their capabilities on-chain.
**In Kokonut:** ERC-8004 is part of the Agentic Marketplace design, allowing farm-related AI agents to have identities, capability manifests, operators, and reputation records.
**Plain English:** A payment flow based on the HTTP `402 Payment Required` response.
**In Kokonut:** x402 can let agents or services request payment, settle in USDC, and continue the request without a manual checkout flow. It is part of the planned agent-to-agent service layer.
***
### ReFi and regenerative agriculture
**Plain English:** Finance is designed to restore ecological and social systems rather than only extract returns.
**In Kokonut:** ReFi means capital is coordinated toward real farms, public goods, land restoration, verifiable impact, and community-owned production systems.
**Plain English:** Farming practices that rebuild soil, biodiversity, water retention, and ecosystem health over time.
**In Kokonut:** Regeneration is operationalized through syntropic farming, biodiversity, cover crops, on-site organic inputs, animal integration, MRV, and community education.
**Plain English:** A farming method that designs farms to behave more like productive natural ecosystems.
**In Kokonut:** Syntropic farms combine short-cycle crops, medium-cycle fruits, long-cycle trees, ground cover, biomass management, and biodiversity so production and regeneration reinforce each other.
**Plain English:** Growing trees, shrubs, crops, and sometimes animals together in one managed system.
**In Kokonut:** Agroforestry supports biodiversity, canopy layering, perennial production, habitat, erosion control, and long-term farm resilience.
**Plain English:** A system that integrates trees, pasture, and grazing animals.
**In Kokonut:** Silvo-pasture is part of the broader regenerative toolkit, especially where animals can support soil fertility, ground-cover management, shade systems, and nutrient cycling.
**Plain English:** Charcoal-like material made by heating biomass in a low-oxygen environment.
**In Kokonut:** Biochar is used as a soil amendment to support water retention, microbial habitat, nutrient availability, and longer-term soil carbon storage. Claims about carbon impact should be verified through MRV and methodology-specific reporting.
**Plain English:** The process of storing carbon in soil, plants, trees, or other stable forms.
**In Kokonut:** Carbon sequestration is treated as an impact category that must be measured and verified. Avoid treating carbon claims as guaranteed outcomes unless the relevant methodology, data, and verification are available.
**Plain English:** The process of measuring what happened, reporting it in a structured format, and verifying that the claim is credible.
**In Kokonut:** MRV is the trust layer. Farm activity becomes structured data, storage records, attestations, Data Hub entries, and annual impact reporting.
**Plain English:** A satellite vegetation-health index based on the difference between near-infrared and red light.
**In Kokonut:** NDVI is used as a baseline remote-sensing indicator for vegetation health across growing seasons.
**Formula:** `NDVI = (NIR - RED) / (NIR + RED)`
**Plain English:** A vegetation index that can be more useful for mature or dense crops where NDVI may saturate.
**In Kokonut:** NDRE helps refine crop-health analysis when plants are more developed and red-edge bands provide better chlorophyll sensitivity.
**Formula:** `NDRE = (NIR - RED_EDGE) / (NIR + RED_EDGE)`
**Plain English:** A vegetation index designed to reduce noise from exposed soil.
**In Kokonut:** MSAVI is especially useful in early crop stages, sparse vegetation, or exposed-soil conditions where NDVI may be less reliable.
**Plain English:** A vegetation index focused on chlorophyll concentration and plant physiological health.
**In Kokonut:** ReCI can help detect nutrient or chlorophyll stress before problems are obvious to the naked eye.
**Formula:** `ReCI = (NIR / RED_EDGE) - 1`
**Plain English:** A framework for reporting ecological benefits beyond carbon alone.
**In Kokonut:** EBF helps categorize impact across environmental, social, economic, and sustainability dimensions such as soil, water, biodiversity, community benefit, and multiple forms of capital.
**Plain English:** A framework for evaluating risk in carbon-credit or ecological-benefit projects.
**In Kokonut:** CRISP-style thinking helps avoid overclaiming by considering delivery risk, climate risk, legal risk, financial risk, and project developer risk.
**Plain English:** The 17 United Nations goals are used globally to describe social, environmental, and development outcomes.
**In Kokonut:** Adelphi primarily maps to SDG 1, SDG 2, SDG 5, SDG 8, and SDG 15. SDG alignment should be supported by farm records, MRV, and evidence from the Data Hub.
***
### Kokonut-specific terms
**Plain English:** The cooperative network connecting Web3 communities, contributors, capital allocators, and regenerative farms.
**In practice:** Kokonut coordinates three layers: the DAO for governance and treasury, the Framework for farm operations and measurement, and the technology layer for MRV, attestations, data, and agents.
**Plain English:** The governance system of the Kokonut Network.
**In practice:** The DAO includes the Moloch DAO for capital governance and the Guilds DAO for contribution-weighted execution. Together, they coordinate funding, work, proposals, and accountability.
**Plain English:** Kokonut's repeatable farm operating model.
**In practice:** The Framework standardizes data, development phases, regeneration principles, impact measurement, SDG alignment, MRV, and DAO-governed farm replication.
**Plain English:** Kokonut's first live farm.
**In practice:** Adelphi is a women-led syntropic farm in Monte Plata, Dominican Republic. It documents crops, biodiversity, infrastructure, poultry, training, SDG alignment, MRV, and live Data Hub records.
**Plain English:** Kokonut's public interface for farm records.
**In practice:** The Data Hub is where users inspect harvest records, MRV events, geospatial data, impact metrics, and farm status. Documentation pages may contain projections; the Hub is where actual recorded data should be checked.
**Plain English:** Kokonut's on-chain treasury and capital governance layer.
**In practice:** It runs on Gnosis Chain through DAOHaus, manages the treasury, controls vKKN and Loot minting or burning, processes funding proposals, and protects members through rage-quit.
**Plain English:** Kokonut's contribution and execution layer.
**In practice:** Guilds organize work across Technology, Impact, Communications, Governance, Finance, and Community & Partnerships. Influence is based on useful work, not capital.
**Plain English:** Non-transferable contribution reputation inside a Guild.
**In practice:** Guild Points can come from completed bounties, proposals, MRV work, documentation, peer endorsements, or governance participation. They determine standing within a Guild, but are not the same as Loot or vKKN.
**Plain English:** A trusted representative of a Guild.
**In practice:** Stewards help coordinate Guild work, represent the Guild in cross-Guild governance, and help route mature proposals toward the Moloch DAO.
**Plain English:** The four stages a Kokonut Framework farm moves through.
**In practice:** Phase I covers planning and preparation. Phase II covers production and regeneration. Phase III covers consolidation and expansion. Phase IV covers MRV, continuous improvement, reporting, and replication.
**Plain English:** A structured registry for farm data and events.
**In practice:** Farm Registry records help connect farm activity to structured payloads, MRV events, attestations, APIs, dashboards, and future agent workflows.
**Plain English:** The standard set of fields every farm should report.
**In practice:** It keeps farms comparable by standardizing important data such as location, farm area, crop systems, operators, development phase, and measurement records.
**Plain English:** A planned AI-agent service layer for farm and DAO work.
**In practice:** Agents may support MRV reporting, harvest forecasting, impact scoring, grant drafting, registry updates, and coordination tasks. This layer is under development and should be described separately from live farm operations.
**Plain English:** Kokonut's invitation for people to contribute without needing to be capital contributors first.
**In practice:** Builders, agronomists, designers, grant writers, researchers, DAO operators, and community organizers can enter through Guild work and earn reputation through verified contributions.
***
## Important distinctions
| Do not confuse | With | Difference |
| ---------------- | --------------- | --------------------------------------------------------------------------------------------------------------- |
| vKKN | Loot | vKKN votes. Loot has economic rights but no governance vote. |
| Guild Points | Loot | Guild Points are an internal contribution to reputation. Loot is a DAO-recognized economic participation token. |
| Forecast | Actuals | Forecasts are planning assumptions. Actuals should be checked in the Data Hub. |
| SDG alignment | Verified impact | SDGs describe intended impact categories. MRV and records provide evidence. |
| Moloch DAO | Guilds DAO | Moloch governs the treasury and voting. Guilds coordinate contribution and execution. |
| Carbon potential | Carbon credit | Carbon benefits require methodology, measurement, and verification before being treated as credits. |
| Framework | Farm | The Framework is a repeatable model. Adelphi is the first live implementation. |
***
## How to keep this glossary accurate
A glossary can become stale if its definitions do not align with the live DAO, farm, and MRV systems. When updating this page:
* keep definitions short and plain-English first;
* link each term to the page where it is used in practice;
* avoid unsupported impact, carbon, legal, or financial claims;
* separate live systems from systems still in development;
* update contract addresses only from the current DAO source page;
* Keep forecast language separate from recorded actuals.
**Missing a term?** Propose a glossary update through the Communications Guild or open an issue in the public site repository. Glossary contributions can be treated as documentation work and may qualify for Guild Points when verified by the relevant Guild.
# Executive Summary
Source: https://kokonut.network/ecosystem-wiki/kokonut-101/executive-summary
A concise orientation to Kokonut Network: the cooperative model, live farm proof, DAO governance, Framework, MRV stack, and contribution paths.
# Kokonut Network turns real farms into community-governed regenerative assets.
Kokonut Network is a blockchain cooperative connecting Web3 communities, contributors, and capital allocators to live syntropic farms — starting with [Adelphi](/ecosystem-wiki/kokonut-farms/adelphi/summary), a working regenerative farm in the Dominican Republic.
The model is simple: the DAO coordinates capital, the Framework standardizes farm operations, MRV systems publish verifiable data, and contributors help replicate the model across new farms.
Free to explore. No capital required to contribute. DAO walkthroughs are available for partners and capital allocators.
***
## TL;DR 🗒️
* Kokonut Network is a **blockchain cooperative** connecting Web3 communities to real syntropic farms — starting in the Dominican Republic with [Adelphi](/ecosystem-wiki/kokonut-farms/adelphi/summary), our first live farm.
* We address the [worldwide lack of funding for agricultural projects](https://youtu.be/ZjygLVUSq4s) by partnering with farmers, raising funds through the [Kokonut DAO](/ecosystem-wiki/the-kokonut-dao/dao-layers), and distributing rewards perpetually to the people and communities growing the network.
* Every \$vKKN governance token is backed **1:1 by a real coconut tree**. The DAO has no admins — decisions happen through on-chain proposals, and rage-quit protects every capital-contributing member.
* The [Kokonut Framework](/kokonut-framework/Introduction) is the repeatable piece: a modular trust layer covering farm funding, MRV, governance, and impact measurement so every new farm can launch without reinventing the coordination logic.
* Contributors do not need capital to start. Through [Kokonut Guilds](/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao), builders, researchers, agronomists, and organizers can earn Guild Points through verified work.
PN #69
public goods funded
***
## Who this is for
Learn how Kokonut turns farm operations, syntropic agriculture, MRV, and community ownership into a repeatable farm development model.
See how DAO governance, EAS attestations, open-source infrastructure, Guild Points, and farm-backed tokens connect to real land.
Understand how stablecoin tribute, \$vKKN, DAO proposals, rage-quit, treasury transparency, and farm-backed governance work.
Explore the Farm Registry primitives, MRV automation stack, EAS-compatible data flows, and the Kokonut Agentic Marketplace.
***
## What we've built so far
Kokonut Network is not a whitepaper project.
[Adelphi](/ecosystem-wiki/kokonut-farms/adelphi/summary) — our flagship syntropic farm in Gonzalo, Monte Plata, Dominican Republic — is already growing. It was funded through [Public Nouns Proposal #69](https://publicnouns.wtf/vote/69) and operates under the full Kokonut Framework: satellite MRV monitoring via Landsat 8 and Sentinel, soil moisture probes, per-plant GPS tracking through Silvi, and on-chain EAS attestations for major farm events.
Real-time harvest records and impact data are publicly available at [hub.kokonut.network/projects/41](https://hub.kokonut.network/projects/41). The numbers in this documentation are not pitch-deck placeholders — they come from a working farm, live operations, and recorded outputs.
Adelphi proves the model can work at the farm level. The next challenge is replication: more farms, more verified data, more contributors, and more community-owned regenerative production.
***
## Why Kokonut Network? 🌴
Grassroots farmers control less than 10% of the global coconut market — not because their land is unproductive, but because they lack access to capital, coordination tools, and transparent governance structures.
Kokonut Network serves as the coordination layer that uses Web3 and open-source infrastructure to close this gap. The model has four interlocking parts:
Holds the treasury, governs farm funding decisions, mints and burns membership tokens, and distributes rewards. It runs through proposals, not administrators.
The modular blueprint every farm runs on: common data schema, development phases, regeneration principles, MRV, and impact measurement.
The living proof of concept: a women-led syntropic farm addressing five UN SDGs with public MRV records and community-first operations.
The emerging infrastructure layer where AI agents support MRV reporting, harvest forecasting, grant drafting, and impact scoring at scale.
Our model has no expiration date. When coconut trees end their productive life, we replant them. The cooperative continues. The community owns the upside.
***
## The Kokonut loop
```mermaid theme={null}
flowchart TD
A["DAO members tribute stablecoins"] --> B["DAO funds approved farms"]
B --> C["Farms run the Kokonut Framework"]
C --> D["MRV data verifies progress"]
D --> E["Harvest, impact, and revenue are recorded"]
E --> F["Rewards flow to farmers, contributors, and communities"]
F --> G["Guilds improve the system"]
G --> H["The next farm launches faster"]
H --> C
```
1. DAO members tribute stablecoins.
2. The DAO funds farms through proposals.
3. Farms run the Kokonut Framework.
4. MRV data verifies farm progress.
5. Harvest, revenue, and impact records flow back into the network.
6. Guilds and contributors improve the system so the next farm can launch faster.
***
## Built to reduce trust gaps
Adelphi publishes farm records, harvest activity, and impact data through the Kokonut Hub so visitors can inspect the work directly.
Major treasury and membership decisions happen through DAO proposals, with rage-quit protection for capital-contributing members.
Builders, researchers, agronomists, and organizers can start through Guild work and earn Guild Points without contributing capital.
You can explore Kokonut before committing capital. Read the docs, inspect Adelphi's live farm data, join the community, or contribute through Guilds. Capital contributors receive rage-quit protection; non-capital contributors can earn Guild Points through verified work.
***
## Why coconuts? 🥥
Coconuts are one of the most versatile agricultural assets in the world. They produce food, drinks, oils, fiber, husks for fertilizer, and wood for furniture and construction. In a syntropic system, they are not only a crop — they are part of a living, regenerative structure that supports soil restoration, biodiversity, water retention, and long-term farm resilience.
Kokonut starts with coconut trees because they are productive, symbolic, durable, and naturally aligned with the cooperative model:
* **Long-term productive life:** trees compound value across years, not one harvest cycle.
* **Multiple product streams:** coconut water, oil, food, fiber, husk, compost, and wood.
* **Ecological fit:** coconut trees can be integrated into biodiverse syntropic systems.
* **Clear token relationship:** every \$vKKN governance token is backed 1:1 by a real coconut tree.
* **Perpetual renewal:** when a tree ends its productive life, the network replants.
> **Coconut is a versatile fruit with compounding health, environmental, and biodiversity benefits — and a proven global market.**
***
## Kokonut Framework Holistic Impact
We are building a [hybrid framework](/kokonut-framework/Introduction) that creates positive, community-centric impact — addressing systemic issues in underserved areas and enhancing climate resilience. Our approach focuses on sustainable solutions that improve daily lives and create incentives without deforestation.
Every component of the ecosystem is designed around the same core principle: the community is prioritized over capital. The [Kokonut Manifesto](/ecosystem-wiki/kokonut-101/manifesto) articulates this in full. The [Governance Framework](/ecosystem-wiki/the-kokonut-dao/governance-framework) operationalizes it.
***
## Choose your path into Kokonut
Continue through Kokonut 101: the problem, solution, manifesto, and why Web3 is part of the model.
See Adelphi's crops, biodiversity, harvest forecasts, MRV methodology, SDG alignment, and live farm records.
Learn how the treasury, tokens, governance, Guilds, rage-quit, and contributor pathways work together.
Explore the modular trust layer every farm runs on — open source, composable, and designed to scale.
Plug in as an agronomist, developer, ReFi builder, researcher, DAO member, partner, or community organizer.
Developers can use the public docs, deployed contracts, Farm Registry primitives, and AI agent architecture.
# Kokonut Vision
Source: https://kokonut.network/ecosystem-wiki/kokonut-101/kokonut-vision
The future Kokonut Network is building: regenerative farms, community-owned productive assets, public MRV data, and a cooperative that compounds value across generations.
# A network of farms that restores land, distributes ownership, and compounds community wealth.
Kokonut Network exists to make regenerative agriculture fundable, governable, verifiable, and community-owned.
We are building toward a world where productive land does not sit idle because farmers lack access to capital. A world where agricultural communities own more than the labor behind the crops they grow. A world where the trust layer between contributors, capital, and farmers is not a bank, corporation, or temporary grant program — but a transparent, permissionless, community-governed network that anyone can inspect and no single actor can capture.
> **The vision is not only more farms. The vision is a new coordination layer for land, labor, capital, data, and community ownership.**
The vision is already underway at Adelphi — Kokonut's first live syntropic farm in Monte Plata, Dominican Republic.
Kokonut Network was created to reduce the obstacles to agricultural development and democratize participation in real-world regenerative projects — starting with the communities and the land that need it most.
***
## The vision at a glance
PN #69
public goods funded
Kokonut's vision is not a distant promise. It begins with one real farm, one real DAO, one real Framework, and a growing contributor network that can make the second farm easier to fund, operate, verify, and govern than the first.
***
## What we see when we look forward
Kokonut's vision operates across three horizons simultaneously. Each one reinforces the others.
Farms should restore the land they use. We envision syntropic farms that build soil fertility, increase biodiversity, improve water retention, reduce reliance on synthetic inputs, and leave each generation with healthier land than the last.
Communities should participate in the upside of the crops they grow. We envision farm-backed governance, transparent treasuries, Guild rewards, rage-quit protections, and ownership paths that do not depend only on existing wealth.
Land is cultural infrastructure, not only economic infrastructure. We envision farms that preserve knowledge, train local stewards, support women-led operations, create jobs, distribute seedlings, and become gathering places for community renewal.
***
## The vision in one loop
```mermaid theme={null}
flowchart TD
A["Productive land + local stewards"] --> B["DAO capital funds farm activation"]
B --> C["Farm runs the Kokonut Framework"]
C --> D["MRV data verifies ecological + production progress"]
D --> E["Harvests, impact, and revenue are recorded"]
E --> F["Farmers, communities, contributors, and DAO benefit"]
F --> G["Guilds improve the Framework + tooling"]
G --> H["Next farm launches faster"]
H --> C
style A fill:#ecfdf5,stroke:#10b981,color:#065f46
style B fill:#ede9fe,stroke:#8b5cf6,color:#4c1d95
style C fill:#f0fdf4,stroke:#16a34a,color:#14532d
style D fill:#e0f2fe,stroke:#0284c7,color:#075985
style E fill:#dcfce7,stroke:#22c55e,color:#166534
style F fill:#fef3c7,stroke:#f59e0b,color:#92400e
style G fill:#fef9c3,stroke:#eab308,color:#713f12
style H fill:#ecfccb,stroke:#84cc16,color:#365314
```
The goal is a regenerative flywheel: farms generate food, data, revenue, and impact; the network uses those outputs to fund contributors, improve infrastructure, and onboard more farms; every new farm adds productive capacity and community ownership to the system.
The difference between a foundation and a network is ownership. A foundation accumulates resources and decides who deserves them. A network distributes ownership, routes capital to where it can become productive, and makes the people tending the land direct participants in the value the land creates.
***
## The vision made real at Adelphi
At [Adelphi](/ecosystem-wiki/kokonut-farms/adelphi/summary), the future Kokonut imagines is already visible:
* A women-led farm in Gonzalo, Monte Plata, Dominican Republic.
* 15,725 m² of productive land, with 13,838 m² dedicated to agro-ecological production.
* Short-, medium-, and long-cycle crops growing in the same system.
* 110 free-range hens producing manure that supports on-site nutrient cycling.
* Native and endangered species propagation.
* Satellite, drone, soil, field, harvest, and per-plant geospatial data.
* Public records at [hub.kokonut.network/projects/41](https://hub.kokonut.network/projects/41).
* On-chain EAS attestations for major farm events.
* Public goods allocation is built into the farm model.
This matters because visions need proof. Adelphi is the proof that Kokonut's model can move from theory into land, crops, jobs, data, and community benefit.
[Explore Adelphi Farm →](/ecosystem-wiki/kokonut-farms/adelphi/summary)
***
## Mission approach: powered by people and trees
[Syntropic farming](/kokonut-framework/why-syntropic-farming) is the agricultural engine of this vision. It turns farms into living systems: productive, biodiverse, soil-building, and resilient across multiple crop cycles.
What Kokonut adds is the coordination layer that syntropic farming needs to scale:
The Kokonut DAO coordinates treasury decisions, farm funding, membership, token issuance, rage-quit protection, and long-term governance through proposals instead of unilateral control.
Every farm runs on a shared blueprint: common data schema, development phases, regeneration principles, MRV standards, and public goods allocation.
Satellite imagery, drone data, soil readings, harvest records, field logs, and EAS attestations turn farm activity into publicly verifiable proof.
Contributors without capital can still earn Guild Points and Loot through meaningful work in technology, impact, communications, governance, finance, and partnerships.
The network is powered by people and trees. Trees generate long-term productive value. People provide care, knowledge, governance, research, tools, and coordination. The Framework connects both into a repeatable system.
***
## Where the trajectory is heading
Kokonut's vision unfolds across three practical horizons.
The near-term work is Adelphi's full operational maturity: stronger harvest records, deeper MRV, improved farm infrastructure, local education, public data, and clearer revenue allocation.
The next phase is onboarding additional farms into the same Framework so the DAO can compare, fund, monitor, and support multiple farms without having to rebuild the coordination logic each time.
The Kokonut Agentic Marketplace will help remove manual bottlenecks from MRV, harvest forecasting, impact scoring, grant drafting, registry submissions, and EAS attestation workflows.
The long-term vision is a network where any farmer, anywhere, who commits to the Framework and populates the Common Data Schema can propose a farm to the DAO, receive funding through governance, and join a cooperative designed to improve land over generations.
***
## What success looks like
Kokonut succeeds when regenerative farms can access capital without surrendering community ownership.
It succeeds when farm data is public enough for contributors and DAO members to trust what is happening on the land.
It succeeds when women-led and community-first farms can turn underused land into food, employment, biodiversity, education, and long-term productive assets.
It succeeds when contributors who write code, improve MRV, organize communities, design governance, or document field processes can earn a real stake in the system they help build.
It succeeds when every new farm makes the next one easier to launch.
> **This is the vision of change: regenerative agriculture as shared infrastructure, not charity; community ownership as the default, not the exception.**
***
## Why is this credible
Adelphi is already operating, growing crops, supporting jobs, tracking field activity, and publishing farm records.
The DAO architecture defines how capital enters, how proposals pass, how rage-quit protects members, and how contributors can earn through Guilds.
The Kokonut Framework is already used to standardize farm phases, data fields, MRV methods, and impact categories.
Agronomists, researchers, developers, ReFi builders, DAO members, capital allocators, and community organizers can already plug into the work.
***
## Choose your next step
Understand the four systems — DAO, Framework, Adelphi, and the Agentic Marketplace — and how each one closes a specific coordination gap.
Read the principles that govern how Kokonut is built: Freedom of Choice, Work, Power, Access, Payment, and Opinion.
Inspect the vision made real: 15,725 m² of syntropic agriculture already growing, monitored, and governed by the community.
Find the contribution path that matches your skills — agronomy, research, development, ReFi, governance, capital, or community building.
The vision is open to inspection before you commit. Read the docs, inspect the live farm data, join the Discord, contribute to the Framework, or follow the DAO before becoming a member.
# Kokonut Manifesto
Source: https://kokonut.network/ecosystem-wiki/kokonut-101/manifesto
The values, freedoms, and commitments that govern Kokonut Network as a community-owned regenerative agriculture cooperative.
# We believe the land belongs to the people who tend it.
Not to corporations that control markets without touching a single tree. Not to financial intermediaries who extract from every transaction between a farmer and the capital they need. Not to foundations that decide which communities are worthy of support and which are not.
To the people who tend it.
Kokonut Network exists because the current agricultural system is a coordination failure. The land is productive. The knowledge is ancient and proven. The demand is real. What has been missing is a trust layer — transparent, permissionless, and verifiable — that allows capital to flow toward productive land and returns to flow back to the communities that earn it.
That trust layer is what we are building.
Not for speculation. Not for extraction. Not for a temporary grant cycle.
For farmers, communities, contributors, and the future members who have not joined yet.
This manifesto is not branding. It is the standard we use to judge governance, funding, contribution, and farm operations.
***
## Manifesto in one sentence
> **Kokonut Network exists to make regenerative agriculture fundable, governable, verifiable, and community-owned — without surrendering control to banks, corporations, foundations, or founders.**
The manifesto is the value layer of the network. The [Kokonut DAO](/ecosystem-wiki/the-kokonut-dao/dao-layers) turns those values into governance. The [Kokonut Framework](/kokonut-framework/Introduction) turns them into farm operations. [Adelphi](/ecosystem-wiki/kokonut-farms/adelphi/summary) proves they can move from words into land, crops, jobs, data, and community benefit.
PN #69
public goods funded
***
## Who this manifesto is for
Farmers who own land, carry knowledge, and want access to patient capital without surrendering the upside of what their land can produce.
Builders, researchers, agronomists, writers, operators, and community organizers who want ownership in the systems they help create.
People who believe that capital should be governed transparently, protected by rage-quit, and deployed toward real productive assets.
Developers and protocol designers who want infrastructure that serves communities instead of extracting from them.
***
## What we refuse
We refuse to use farmers as a narrative layer for financial speculation.
We refuse to build systems where capital has every path to ownership and work has none.
We refuse to treat community benefit as a marketing claim instead of a treasury, governance, and revenue allocation design requirement.
We refuse to let farm data remain invisible when visibility is what makes trust, funding, and accountability possible.
We refuse to depend on a model that dies when the grant ends, when the donor loses interest, or when a corporate partner finds a better margin elsewhere.
Kokonut Network is designed around a simple constraint: if the system does not improve the position of farmers, contributors, and surrounding communities, it is not aligned with the manifesto.
***
## What we believe
Capital is necessary, but it is not sovereign. The community, the land, and the people doing the work are the center of the system.
Trust should not depend on private promises. Governance, treasury activity, farm data, and contribution paths should be inspectable.
A regenerative network must outlast its founders, grants, and campaigns. Trees are replanted. Revenue cycles continue. The flywheel does not stop.
These are not slogans. They are design constraints.
Every treasury structure, token mechanic, proposal flow, Guild process, MRV method, and farm deployment should be judged by the same question:
> **Does this make Kokonut more community-owned, more verifiable, more regenerative, and harder to capture?**
***
## The six freedoms
These freedoms define what participation in Kokonut Network should feel like. They are not abstract ideals — they are meant to be implemented through governance mechanics, token rights, Guild contribution paths, and transparent proposal flows.
Participation should remain voluntary. Capital-contributing DAO members are protected by rage-quit, meaning they can exit and claim their proportional share of the treasury if they disagree with the network's direction.
Kokonut cannot be built by a single person or a single team. Guilds exist so that technical, ecological, governance, finance, communications, and partnership work can be coordinated, rewarded, and made visible.
Governance power should not flow from the founding status. The DAO exists so authority is distributed through proposals, token-holder votes, Guild contribution, and transparent execution rather than unilateral control.
There are two paths into the system: tribute stablecoins to receive \$vKKN governance tokens, or contribute meaningful work through Guilds and earn Guild Points that can lead to Loot ownership.
Farm funding, Guild bounties, Framework upgrades, and partnerships should move through transparent proposals. The community decides what the treasury funds.
Disagreement is part of governance. Proposals should be challenged, improved, rejected, revised, and brought back stronger when they drift from the principles in this document.
[Read the Governance Framework →](/ecosystem-wiki/the-kokonut-dao/governance-framework)
***
## Values made operational
| Manifesto value | How Kokonut makes it real | Where to inspect it |
| ------------------------------ | ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Community before capital | Guilds create a contribution path for people who do not enter with money. | [Kokonut Guilds](/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao) |
| Voluntary participation | Rage-quit protects capital-contributing members from being trapped in the DAO. | [DAO Architecture](/ecosystem-wiki/the-kokonut-dao/dao-layers) |
| No unilateral treasury control | Treasury movements require proposals and governance approval. | [Governance Framework](/ecosystem-wiki/the-kokonut-dao/governance-framework) |
| Real-world backing | \$vKKN governance tokens are backed 1:1 by real coconut trees. | [Kokonut Moloch DAO](/ecosystem-wiki/the-kokonut-dao/kokonut-moloch-dao) |
| Verifiable impact | Farm activity flows through MRV, field records, and EAS attestations. | [Measurement, Reporting & Verification](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification) |
| Replication over dependency | The Framework standardizes farm operations so each new farm does not start from zero. | [Kokonut Framework](/kokonut-framework/Introduction) |
***
## What we commit to
We commit to building systems that serve the farmers and communities at the center of this network — not systems that use farmers and communities as justification for financial speculation.
We commit to [Adelphi](/ecosystem-wiki/kokonut-farms/adelphi/summary): to Yanny and Neury Hernández, to the community around Haty in Monte Plata, to the native and endangered species nursery, to the 110 free-range hens whose manure supports the soil, to the crops already growing, and to the next farm that learns from this one.
We commit to [openness](/build-with-kokonut): open-source code, open governance, open data, and open contribution. The [Kokonut Framework](/kokonut-framework/Introduction) is forkable by design. If another community can use it to build something better, we want them to.
We commit to the long view. Coconut trees take years to mature and produce for decades. The communities that tend them deserve a cooperative that thinks on the same timescale.
We commit to making the system inspectable before we ask anyone to trust it.
You can explore Kokonut before committing capital. Read the docs, inspect Adelphi's live farm data, join the Discord, contribute through Guilds, or follow the DAO before becoming a member.
***
## The invitation
If you believe regenerative agriculture should be fundable without becoming extractive, this manifesto is for you.
If you believe contributors should earn a real stake in the systems they build, this manifesto is for you.
If you believe farmers and local communities should own more than the labor behind the crops they grow, this manifesto is for you.
If you believe open-source coordination can serve land, people, and future generations, this manifesto is for you.
***
> *Inspired by [HausDAO](https://github.com/HausDAO/manifesto) and [MetaCartel](https://github.com/metacartel/mission/blob/master/community-first-manifesto.md) manifestos.*
The world Kokonut is building toward — ecological regeneration, economic democratization, and social sovereignty for farming communities.
How the six freedoms are implemented in practice — treasury mechanics, token structure, governance process, and Guild contribution system.
Freedom of Access in action — how contributors earn Guild Points, Loot tokens, and a real stake in the ecosystem through verifiable work.
Freedom to Pay and Freedom of Opinion made operational — the full proposal process, voting parameters, and how the community makes binding decisions.
# Problem Statement
Source: https://kokonut.network/ecosystem-wiki/kokonut-101/problem
Why grassroots farmers remain excluded from agricultural capital — and why Kokonut Network treats this as a coordination failure, not an agronomic one.
# The problem is not the land. It is the coordination layer around it.
Grassroots farmers already have land, knowledge, labor, and demand for the crops they grow. What they often lack is access to capital, transparent governance, reliable market participation, and the verification infrastructure needed to prove impact.
Kokonut Network starts from one core diagnosis:
> **The agricultural funding gap is a coordination failure — not an agronomic failure.**
The land can produce. Syntropic farming works. Communities know how to care for place. But without a trusted way to connect capital to productive land and returns to the communities that tend it, farmers remain trapped in low-income, extractive systems.
Read the global problem first, then inspect how it appears at the farm level in Monte Plata, Dominican Republic.
***
## The funding gap that traps farmers in poverty
A global crisis revolves around insufficient funding for agricultural projects — and its consequences cascade far beyond any single farm.
Grassroots farmers who grow some of the world's most vital crops operate without the capital, coordination tools, or governance structures needed to compete. Many agricultural communities perform the labor that sustains food systems while remaining excluded from the ownership, infrastructure, and market upside those systems generate.
Most of the labor in agricultural communities is executed by people trapped in poverty — not because the land is unproductive, but because there is no accessible path from productive land to sustainable income.
The core problem
Grassroots farmers lack the processes, knowledge, funding, and coordination infrastructure necessary to compete with corporate supply chains that capture most of the value from the crops farmers produce.
The coconut market clearly shows the pattern. Coconut is a high-utility crop with global demand across food, beverage, oil, fiber, fertilizer, and construction inputs. But the value created by coconut farming is often captured by processing, distribution, and retail layers far away from the communities doing the farming.
That is not a farming problem. It is a coordination problem.
***
## Why existing solutions do not work
The funding gap is not new. It has persisted because the available mechanisms to close it are structurally mismatched with what grassroots farmers actually need.
Banks and formal lenders usually require collateral, credit history, and institutional relationships that subsistence and small-scale farmers rarely have. The farmers most capable of producing regenerative, high-quality crops are often excluded from the capital systems that could help them scale.
Grants can fund a planting cycle or infrastructure purchase, but they rarely create perpetual governance, monitoring, and revenue distribution systems. When the grant ends, the funding relationship ends with it.
Corporate buyers control processing, distribution, pricing, and market access. Farmers supply the crop but do not own the upside, leaving them exposed to commodity price swings and weak negotiating power.
The result is a trust gap:
* Capital exists, but it does not know which farms to trust.
* Productive land exists, but it cannot access patient, transparent funding.
* Farmers have knowledge, but they lack governance and reporting infrastructure.
* Communities need food and income, but value is extracted upward.
* Regeneration is possible, but the financial incentives still reward short-term extraction.
The missing piece is a mechanism that allows capital to flow to productive land, verifies what happens on that land, and returns value to the farmers and communities doing the work.
***
## The local reality
The global problem manifests at the community level, where undercapitalized farmers are asked to compete with extractive markets.
In the communities where Kokonut Network works — including the rural areas of Monte Plata, Dominican Republic, where our flagship [Adelphi Farm](/ecosystem-wiki/kokonut-farms/adelphi/summary) operates — residents face a compounding set of pressures.
Rural residents often need to migrate to cities for income. That migration weakens local labor capacity, raises the cost of living, and makes it harder for families to invest back into the land they already own.
Fertile land can sit underused while communities depend on imported or processed products that are more expensive and less nutritious than what local farms could produce.
Without incentives to protect land, short-term survival can push communities toward deforestation, soil depletion, and extractive crop cycles that reduce fertility over time.
Women in rural agricultural communities often face legal, cultural, and financial barriers to land ownership, access to credit, and leadership roles — despite being central knowledge holders and operators.
Younger generations raised away from agriculture lose the practical knowledge their grandparents carried. When that knowledge is not transferred, the community's relationship to the land weakens.
Even when regenerative work is happening, farmers rarely have the tools to prove it through standardized data, MRV records, or public impact reporting.
***
## The consequence cycle
These pressures do not operate in isolation. They reinforce each other.
```mermaid theme={null}
flowchart TD
F["Industrial food systems\n→ climate pressure"]
G["Concentrated markets\n→ reduced farmer leverage"]
A["Limited access to capital\n→ land remains underused"]
B["Low investment in regeneration\n→ soil degradation + deforestation"]
C["Ecosystem stress\n→ biodiversity loss + water scarcity"]
D["Lower yields\n→ poverty + food insecurity"]
E["Youth migration\n→ farming knowledge gap"]
H["Weak reporting infrastructure\n→ capital cannot verify impact"]
F -->|"increases climate risk"| C
G -->|"reduces local income potential"| A
A --> B
B --> C
C --> D
D --> E
E -->|"less local capacity to restore land"| A
H -->|"keeps capital on the sidelines"| A
D -->|"reduces ability to report + organize"| H
style A fill:#fee2e2,stroke:#ef4444,color:#991b1b
style B fill:#fee2e2,stroke:#ef4444,color:#991b1b
style C fill:#fee2e2,stroke:#ef4444,color:#991b1b
style D fill:#fee2e2,stroke:#ef4444,color:#991b1b
style E fill:#fee2e2,stroke:#ef4444,color:#991b1b
style H fill:#fee2e2,stroke:#ef4444,color:#991b1b
style F fill:#fef3c7,stroke:#f59e0b,color:#92400e
style G fill:#fef3c7,stroke:#f59e0b,color:#92400e
```
Regenerative agriculture — specifically, [syntropic farming](/kokonut-framework/why-syntropic-farming) — can break this cycle by design. Syntropic farms improve soil with each season, reduce dependence on synthetic inputs, and generate multiple revenue streams across short-, medium-, and long-term crop cycles.
But agronomy alone is not enough.
The farming method exists. The missing layer is coordination: funding, governance, measurement, verification, and revenue distribution.
***
## What this looks like at Adelphi
Adelphi makes the global problem visible at the farm level.
PN #69
public goods funded
At Adelphi, the abstract problem becomes concrete:
* A women-led farm had land and vision, but needed funding and infrastructure.
* The surrounding community needed income, access to food, education, and safe gathering spaces.
* The land needed regenerative investment, biodiversity restoration, water systems, and long-term soil care.
* The project needed a way to prove activity, report impact, and remain accountable to contributors.
Public Nouns Proposal #69 helped fund Adelphi's critical infrastructure. Kokonut's role is to turn that one successful intervention into a repeatable model: DAO-funded capital deployment, Framework-standardized operations, public MRV records, and revenue allocation that keeps value circulating through the community.
[Read the Adelphi problem and solution →](/ecosystem-wiki/kokonut-farms/adelphi/problem-and-solution)
***
## In our own words
***
## What has been missing
The problem is well understood. The world does not need another abstract call for sustainability.
What has been missing is a mechanism that is:
Anyone can inspect the farm data, governance process, treasury activity, and impact records.
The model does not expire when a grant ends. Trees are replanted, revenue cycles continue, and the cooperative keeps operating.
The people funding, building, farming, and maintaining the system participate through DAO governance, Guilds, and documented contribution pathways.
MRV submissions, harvest milestones, funding approvals, and impact reports can become public, tamper-resistant records.
That mechanism is what Kokonut Network is building.
***
## Next: how Kokonut closes the gap
The solution is already in motion at Adelphi. The next step is replication — applying the same Framework to the next farm, and the one after that, until the network becomes self-sustaining at scale.
How blockchain coordination, the Kokonut Framework, and the DAO treasury close the funding gap — and why the model has no expiration date.
See the seven specific local problems this model addresses at the farm level — and the solutions already in operation.
The agronomic case for syntropic farming is that it breaks the cycle of deforestation and soil depletion.
The problem is solvable. Read how agronomists, developers, researchers, and capital allocators can contribute.
# Our Solution
Source: https://kokonut.network/ecosystem-wiki/kokonut-101/solution
How Kokonut Network closes the agricultural coordination gap through DAO capital, the Kokonut Framework, live farm proof, MRV infrastructure, and a perpetual regenerative flywheel.
# Kokonut Network closes the agricultural coordination gap.
The [problem](/ecosystem-wiki/kokonut-101/problem) is not the land. It is the coordination layer around the land.
Grassroots farmers already have knowledge, labor, productive land, and demand for the crops they grow. What they often lack is access to patient capital, transparent governance, reliable reporting, and a way to prove impact. Kokonut Network solves this by connecting farms, contributors, DAO members, and verifiable data into one cooperative system.
> **The solution is a community-governed coordination stack for regenerative agriculture:** DAO capital funds farms, the Kokonut Framework standardizes operations, MRV verifies progress, and farm revenue helps fund the next cycle of work.
Start with the mechanism, inspect the live proof, then choose whether to contribute, build, or join the DAO.
Blockchain open data and protocols replace the trust intermediaries that have historically excluded grassroots farmers from agricultural capital markets — making funding transparent, governance permissionless, and impact verifiable.
***
## The Kokonut solution at a glance
DAO members tribute stablecoins, receive \$vKKN governance tokens backed 1:1 by real coconut trees, and vote on funding, bounties, partnerships, and membership proposals.
Every farm follows the Kokonut Framework: common data schema, four development phases, regeneration principles, MRV standards, and impact reporting.
Satellite data, drone imagery, soil probes, community logs, harvest records, and EAS attestations make farm progress publicly auditable.
Farm revenue flows back to farmers, contributors, communities, and the DAO treasury — funding Guild work, infrastructure, and future farm replication.
Kokonut is not a grant program, a farm management company, or a corporate buyer. It is a cooperative coordination layer designed to make regenerative farms fundable, governable, and verifiable under a shared system.
***
## The answer to each failure mode
The agricultural funding gap persists because existing systems fail at different points in the same cycle. Kokonut closes each failure mode with a specific mechanism.
| Failure mode | Why it fails | How Kokonut closes it |
| ------------------------------------ | -------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Traditional agricultural finance** | Requires collateral, credit history, and institutional relationships that many grassroots farmers do not have. | DAO tribute requires stablecoins, not traditional collateral. Members fund the treasury through proposals and receive \$vKKN governance tokens backed 1:1 by real coconut trees. |
| **NGO and grant models** | Funding is temporary. When the grant period ends, the coordination and reporting system usually ends with it. | Coconut trees are replanted when they end their productive life. The cooperative, revenue cycles, and contributor network continue beyond a single grant period. |
| **Corporate supply chains** | Value is extracted upward through processing, pricing, and distribution layers farmers do not own. | DAO members, Guild contributors, farmers, and communities participate in the upside. Rage-quit protects capital contributors; Guild Points and Loot create a contribution path without capital. |
This is the key shift: Kokonut not only funds farms. It changes who can coordinate, verify, govern, and benefit from the work.
***
## How the system flows
```mermaid theme={null}
flowchart TD
A["Capital contributors\ntribute stablecoins"]
B["Kokonut DAO\nproposal + treasury vote"]
C["Execution Layer\nGuilds + Core Team + partners"]
D["Production Layer\nAdelphi + future farms"]
E["Framework operations\n13-field schema + 4 phases"]
F["MRV infrastructure\nsatellite + soil + harvest data"]
G["EAS attestations\npublic verification layer"]
H["Farm revenue + impact records"]
I["Guild budgets + farmer/community value"]
J["Replication\nnext farm launches faster"]
A --> B
B --> C
C --> D
D --> E
E --> F
F --> G
G --> H
H --> I
I --> J
J --> E
style A fill:#ede9fe,stroke:#8b5cf6,color:#4c1d95
style B fill:#ede9fe,stroke:#8b5cf6,color:#4c1d95
style C fill:#fef3c7,stroke:#f59e0b,color:#92400e
style D fill:#d1fae5,stroke:#10b981,color:#065f46
style E fill:#d1fae5,stroke:#10b981,color:#065f46
style F fill:#e0f2fe,stroke:#0284c7,color:#075985
style G fill:#e0f2fe,stroke:#0284c7,color:#075985
style H fill:#dcfce7,stroke:#22c55e,color:#166534
style I fill:#dcfce7,stroke:#22c55e,color:#166534
style J fill:#f0fdf4,stroke:#16a34a,color:#14532d
```
Capital and governance decisions flow downward from the DAO to farm operations. Farm data and impact records flow upward from the land to the verification layer. Revenue and contributor budgets keep the network operating without needing each farm to restart from zero.
***
## The four interlocking systems
Kokonut's solution is built on four systems that address different aspects of the coordination gap.
### 1. The Kokonut DAO — community-governed capital
The [Kokonut DAO](/ecosystem-wiki/the-kokonut-dao/dao-layers) is the network's treasury and governance engine. It operates on Gnosis Chain via the Moloch framework: no administrators, no unilateral control of the treasury, and stablecoin-based membership.
Members tribute stablecoins to the treasury and receive **\$vKKN** governance tokens backed 1:1 by real coconut trees. All major actions — farm funding, bounty payments, partner agreements, token minting, and treasury disbursements — require a passed on-chain proposal voted on by token holders.
**Rage-quit** protects capital contributors by allowing them to exit with their proportional share of the treasury before a proposal they disagree with is executed. Capital is not trapped. Minority holders are protected by design.
The [Kokonut Guilds](https://kokonut.network/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao) extend participation to contributors who lack the capital to contribute. Six domain-specific bodies — Technology, Impact, Communications, Governance, Finance, and Community & Partnerships — operate through contribution-weighted Guild Points. Significant work can earn **Loot tokens**, creating an economic path into the network through verified contribution.
### 2. The Kokonut Framework — the standardized farm blueprint
The [Kokonut Framework](/kokonut-framework/Introduction) is the modular trust layer every farm runs on. It solves the replication problem: how do you fund, operate, monitor, and verify a second farm — or a hundredth — without rebuilding the governance and measurement infrastructure from scratch?
The answer is **standardization without rigidity**.
Every farm populates a [13-field Common Data Schema](/kokonut-framework/framework-components/common-data-schema) covering location, land size, crop mix, revenue streams, governance mechanism, token allocation, and public goods allocation. From there, each farm follows four development phases: Planning, Production, Consolidation, and continuous MRV.
This makes farms comparable, fundable, governable, and verifiable under the same system — while still allowing each farm to reflect its local ecology, community, crops, and operators.
### 3. Adelphi — live proof the model works
[Adelphi](/ecosystem-wiki/kokonut-farms/adelphi/summary) is Kokonut Network's first live syntropic farm in Gonzalo, Monte Plata, Dominican Republic. It is women-led, community-first, and publicly funded through [Public Nouns Proposal #69](https://publicnouns.wtf/vote/69).
PN #69
public goods funded
Adelphi demonstrates the solution simultaneously: DAO-funded capital deployment, Framework-standardized operations, satellite MRV, SDG-aligned impact tracking, and public goods allocation built into the model. Live farm records are available at [hub.kokonut.network/projects/41](https://hub.kokonut.network/projects/41).
### 4. The Agentic Marketplace — automation at scale
Manual MRV pipelines are a scaling bottleneck. Satellite passes, drone surveys, soil readings, harvest records, and field logs all need to be structured and verified as data before they can support governance, funding, and impact reporting.
The [Kokonut Agentic Marketplace](/kokonut-x-ai-agents) is the infrastructure layer being developed to remove this bottleneck. AI agents can support satellite MRV ingestion, vegetation-index calculation, Farm Registry API submissions, harvest forecasting, grant drafting, and EAS attestation workflows.
As the farm network scales, agents handle the repetitive data infrastructure tasks. Humans handle the land, relationships, community, and governance.
***
## What is live vs. what is being built
Transparency matters. Not every component is at the same maturity level.
| Component | Status | What it means |
| --------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------- |
| **Adelphi Farm** | Live | Active syntropic farm in Monte Plata, Dominican Republic, with public records and ongoing operations. |
| **Kokonut DAO** | Live | Governance, treasury, membership, and rage-quit logic operate through deployed DAO architecture on Gnosis Chain. |
| **Kokonut Framework** | Live and evolving | The Framework is already deployed at Adelphi and is being improved as the repeatable farm blueprint. |
| **MRV + EAS pipeline** | Active and expanding | Satellite, soil, field, harvest, and impact records are used to make farm progress publicly verifiable. |
| **Agentic Marketplace** | In development | Automation layer for MRV, registry submissions, reporting, payments, and AI-supported operations. |
| **Future farm replication** | Next frontier | The next stage is applying the same Framework to more farms without rebuilding the stack each time. |
The solution is already real at the farm level. The scaling layer is what the community is now building: more standardized data, more automation, more contributors, and more farms entering the Framework.
***
## The perpetual regenerative flywheel
The Kokonut Seeds mechanism is the financial engine that makes the model self-sustaining over time.
Kokonut Seeds — the network's flagship farm-funding vehicle — generates revenue from syntropic crop production across short-, medium-, and long-cycle crops. Revenue is denominated in stablecoins and flows into the DAO treasury.
A portion of farm revenue is routed to the [Kokonut Guilds](/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao) as a sustainable operational budget independent of external grants, investor rounds, or token sales.
Guild contributors earn Guild Points and may receive Loot tokens for significant work. They improve the Framework, MRV stack, data infrastructure, documentation, partnerships, and farm onboarding process.
Each new farm adds productive capacity, verified impact data, and potential revenue streams to the network. More farms create more data, more treasury activity, and more opportunities for contributors.
When coconut trees reach the end of their productive life, they are replanted. The production cycle restarts. The cooperative continues. The flywheel does not depend on a single grant cycle or harvest season.
> This is the core reason the Kokonut Framework matters: it turns one farm into a repeatable, self-reinforcing system for funding, operating, verifying, and expanding regenerative agriculture.
***
## Why is this credible
The strongest proof is that each part of the solution already appears in a working context.
Adelphi is a live farm — not a whitepaper — with crops, hens, infrastructure, operators, MRV records, and public data.
DAO membership, treasury logic, token minting, proposal flow, and rage-quit protections are part of the deployed governance architecture.
The same schema, phases, MRV standards, and impact measurement logic that govern Adelphi can govern future farms.
Visitors can inspect live farm data rather than relying only on narrative claims or static reports.
***
## What this means in practice
At [Adelphi](/ecosystem-wiki/kokonut-farms/adelphi/summary) today:
* **Capital has been deployed** through public goods funding instead of a traditional bank loan, collateral requirement, or corporate intermediary.
* **Operations are standardized** through the Kokonut Framework across planning, production, consolidation, and continuous MRV.
* **Impact is measured** through satellite monitoring, field data, soil probes, harvest records, and per-plant geospatial tracking.
* **Impact is verifiable** through public records, on-chain EAS attestations, and live data at [hub.kokonut.network/projects/41](https://hub.kokonut.network/projects/41).
* **Community benefit is designed in** through women-led operations, local employment, biodiversity restoration, public goods allocation, and educational programming.
* **The next step is replication** — applying the same Framework to the next farm, and the one after that, until the network is self-sustaining at scale.
***
## Choose your next step
Learn how the treasury, \$vKKN, Loot, rage-quit, Guilds, proposal flow, and governance layers work together.
Explore the modular trust layer every Kokonut farm runs on — data schema, development phases, MRV methodology, and impact measurement.
See the live proof of concept — crops, harvest forecasts, MRV data, community impact, and SDG alignment.
Developers can use the public docs, deployed contracts, Farm Registry primitives, and agent architecture to build on the network.
Agronomists, researchers, ReFi builders, developers, DAO members, and capital allocators can plug into the work already underway.
Review the funding and coordination failure that Kokonut Network was designed to solve.
# Background Story
Source: https://kokonut.network/ecosystem-wiki/kokonut-farms/adelphi/background-story
The human story behind Adelphi: two sisters, inherited farming memory, women-led land stewardship, community education, biodiversity restoration, and Kokonut's first live farm proof.
# Adelphi began as the two sisters' dream to return to the land.
Adelphi is Kokonut Network's first live syntropic farm — founded and operated by sisters **Yanny and Neury Hernández** in Gonzalo, Sabana Grande de Boyá, Monte Plata, Dominican Republic.
This is not only a farm profile. It is the human story behind Kokonut's first proof of concept: a women-led project that turns family memory, underused land, public-goods funding, syntropic agriculture, biodiversity restoration, and community education into a single regenerative system.
Adelphi connects personal history to public evidence: land, founders, infrastructure, crops, MRV, and community impact.
Mother Nature is an unbreakable living force that thrives in any environment. So are the people who choose to tend her.
***
## Why this story matters
Many regenerative agriculture projects begin with land, capital, or technical design. Adelphi begins with something more durable: a family relationship to place.
Yanny and Neury did not enter agriculture as outside operators. They grew up in a farming family, carrying memories of their grandparents' countryside home, childhood vacations surrounded by nature, and a long-held desire to return to land stewardship.
Kokonut Network matters because it gives stories like this the coordination layer they were missing: patient capital, public reporting, DAO accountability, farm infrastructure, and a Framework that other communities can replicate.
PN #69
public goods funded
Adelphi is the emotional proof behind the technical model. The DAO, Framework, MRV stack, and Data Hub only matter because they help real people build resilient lives on real land.
***
## The Rebirth of a Dream
SDG 5 — Gender Equality
SDG 1 — No Poverty
Yanny and Neury Hernández are sisters, single mothers, and the founders of Adelphi. They were raised in the city, but their roots were always tied to the countryside. Their grandparents' home became a place of memory, learning, and belonging — a place where land was not only property, but inheritance, responsibility, and possibility.
As adults, their lives moved through different paths. Yanny built a career in the pharmaceutical industry. Neury became a professional manicurist. Yet the dream of returning to the countryside never disappeared.
In 2022, they acted on that dream and purchased land in Gonzalo. Their intention was simple and powerful: build a future where they could live from the land, preserve their family's farming legacy, and create something useful for the surrounding community.
Then they met the problem that many small landholders face: owning land is not the same as having the capital to cultivate it.
The high cost of living in the city made it difficult to finance soil preparation, water systems, planting, tools, infrastructure, and the early operating costs of turning land into a working farm. This local barrier mirrored Kokonut Network's broader diagnosis: many grassroots farmers do not lack land or willpower — they lack access to the coordination layer that turns land into a regenerative livelihood.
That changed when [Public Nouns Proposal #69](https://publicnouns.wtf/vote/69) funded Adelphi's critical infrastructure. The funding did not just help launch a private farm. It helped Adelphi start as a public-good-aligned project from day one: community-first, data-visible, biodiversity-oriented, and designed to teach others.
This is how **Adelphi** was born. The name comes from the Greek word for *sisters* — a quiet declaration of the bond between Yanny and Neury, and of the cooperative spirit the farm is meant to carry forward.
***
## Story timeline
Yanny and Neury grow up connected to their grandparents' countryside home, carrying a deep relationship with the land and farming memories.
Yanny works in the pharmaceutical industry while Neury builds a career as a professional manicurist. The dream of returning to the countryside remains alive.
In 2022, the sisters bought land in Gonzalo, Monte Plata, hoping to create a future rooted in agriculture, family legacy, and community benefit.
The land exists, but cultivation requires infrastructure, tools, water systems, soil preparation, and operating support.
Public Nouns Proposal #69 funds critical infrastructure, allowing Adelphi to begin as a community-first syntropic farm.
Adelphi becomes Kokonut's first live farm proof: producing, teaching, regenerating, and publishing public farm data.
***
## A project for the community
SDG 4 — Quality Education
SDG 1 — No Poverty
Adelphi is not only meant to secure Yanny and Neury's future. It is designed to benefit the surrounding community.
The farm produces organic and agro-ecological crops, preserves biodiversity, regenerates soil, and creates a place where neighbors can learn sustainable agricultural practices. Its community education space is designed for children, elders, farmers, families, visitors, and anyone interested in reconnecting with land stewardship.
Near a batey and the Haty community, Adelphi can become a weekend refuge and gathering place: a farm where people learn by seeing, touching, planting, harvesting, cooking, resting, and asking questions.
The education program responds to a real local challenge: younger generations are increasingly disconnected from the agricultural knowledge their grandparents carried. Adelphi turns that knowledge gap into an invitation.
A place to learn where food comes from, how soil works, and why land stewardship matters.
A place where traditional knowledge can be respected, remembered, and transferred to younger generations.
A working demonstration of syntropic farming, biochar, nursery propagation, poultry integration, and organic inputs.
A live case study showing how community-first farms can be funded, documented, governed, and replicated.
***
## Reconnecting land, soil, and species
SDG 15 — Life on Land
The ecological side of Adelphi is inseparable from the human story. The project is not only about generating income from land; it is about repairing the relationship between people and living systems.
Adelphi uses [syntropic farming](/kokonut-framework/why-syntropic-farming), biochar soil enrichment, biodiversity conservation, free-range poultry, ground cover, and a native-species nursery to build a farm that grows more alive over time.
The nursery conserves more than a dozen at-risk native species, including Hispaniola palmetto, native cacao, guavaberry, and Star Apple. Propagated plants can be distributed free of charge to visitors and neighboring communities, turning the nursery into a public good that extends beyond the farm boundary.
Every species registered in the nursery can be GPS-tracked through [Silvi](https://www.silvi.earth/) and included in the farm's satellite-monitored vegetation health records. This is where the story becomes evidence: biodiversity is not only described but also documented.
[Explore the crops, biodiversity, and infrastructure →](/ecosystem-wiki/kokonut-farms/adelphi/crops-biodiversity-and-infrastructure)
***
## From personal dream to Kokonut proof
```mermaid theme={null}
flowchart TD
A["Family farming memory"] --> B["Yanny + Neury buy land in Gonzalo"]
B --> C["Capital gap blocks cultivation"]
C --> D["Public Nouns #69 funds critical infrastructure"]
D --> E["Adelphi launches as a syntropic farm"]
E --> F["Organic production + poultry + nursery + education"]
F --> G["MRV records + Data Hub + EAS attestations"]
G --> H["Kokonut Framework learns from the farm"]
H --> I["Next farms launch faster"]
```
This is the deeper reason Adelphi matters to Kokonut Network.
The farm is not only a beneficiary of the Framework. It is also a source of learning for the Framework. Every planting, harvest, workshop, species record, MRV event, and community outcome helps define what future Kokonut farms need to replicate the model with less friction.
| Story element | What does it prove for Kokonut |
| ------------------------------- | ----------------------------------------------------------------- |
| Yanny and Neury's land purchase | Grassroots founders already have agency, vision, and commitment |
| The capital gap | Land alone is not enough; coordination infrastructure is required |
| Public goods funding | Web3 communities can help finance real local infrastructure |
| Syntropic farm design | Regeneration can be operational, not only philosophical |
| Education space | Community benefit can be built into the farm from the start |
| Nursery and biodiversity work | Productive farms can also conserve species and restore ecosystems |
| Public MRV records | Impact claims can become inspectable evidence |
***
## In their own words
> **"Adelphi" is more than just an agricultural project — it is a space for transformation, where people can reconnect with nature and embrace a healthier, more balanced way of life. Yanny and Neury are not just planting crops; they are sowing the seeds of a sustainable future, filled with hope for themselves and their community.**
Yanny and Neury Hernández at Adelphi — building the farm, the community program, and the model that Kokonut Network was created to replicate.
***
## SDG alignment in practice
The background story of Adelphi is the most human expression of the SDGs that the farm addresses. These are not theoretical commitments — they are lived realities for Yanny, Neury, and the surrounding community.
| SDG | How the story embodies it |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| SDG 1 — No Poverty | Two single mothers creating a sustainable income from land they own, with farm operations designed to support local jobs and community benefit |
| SDG 4 — Quality Education | Weekend programs, workshops, and farm-based training designed to transfer agricultural knowledge to children, elders, neighbors, and nearby farmers |
| SDG 5 — Gender Equality | A farm founded, owned, and operated by women, demonstrating female leadership in agriculture, land stewardship, and community coordination |
| SDG 15 — Life on Land | Endangered species nursery, biochar soil regeneration, syntropic multi-strata planting, and free distribution of native plants to neighboring communities |
[Read the full SDG alignment →](/ecosystem-wiki/kokonut-farms/adelphi/sustainable-development-goals)
***
## What this story asks of the reader
The background story is not only meant to be inspiring. It is meant to make the project legible.
If you are reading as a DAO member, this is the human context behind the treasury decisions. If you are reading as a builder, this is the real-world user story behind the data systems. If you are reading as an agronomist, this is the community context behind the farm design. If you are reading as a partner or capital allocator, this is the reason Kokonut treats funding as public infrastructure, not charity.
You can explore Adelphi before making any commitment: read the docs, inspect the live Data Hub, review the MRV methodology, or join the community conversation.
***
## Next steps
The full project overview — key facts, revenue projections, Framework phase, MRV stack, and geospatial data for the farm Yanny and Neury are building.
The seven local challenges this story addresses are economic hardship, food insecurity, gender inequality, educational gaps, and environmental degradation.
What the farm physically produces — crops, native species, biochar, syntropic plots, poultry, and community education infrastructure.
How Adelphi's story becomes verifiable evidence through data, field records, remote sensing, IPFS, and EAS attestations.
Help replicate this model as an agronomist, researcher, developer, DAO member, capital allocator, storyteller, or community organizer.
The principles behind the public goods funding model that made Adelphi possible — community before capital, land stewardship, and shared upside.
# Crops & Harvest Forecast
Source: https://kokonut.network/ecosystem-wiki/kokonut-farms/adelphi/crops-and-harvest-forecast
Adelphi's crop mix, harvest assumptions, revenue model, public goods allocation, and live-data feedback loop.
# Adelphi's harvest forecast shows how regeneration can become a recurring revenue stream.
Adelphi's production model is designed around one practical question:
> Can a regenerative farm produce short-term cash flow, long-term perennial value, public goods funding, and verifiable impact at the same time?
This page explains the forecast behind Adelphi's crop system: what is planted, how production is calculated, which assumptions are used, how revenue is projected, and how actual harvest records refine the model over time.
Forecasts are planning assumptions, not guaranteed outcomes. Actuals are tracked through the Kokonut Hub and refined through MRV.
This page is an operational forecast for farm planning and impact modeling. It is not financial advice, an investment guarantee, or a promise of future returns. Weather, pests, soil conditions, labor, market access, and pricing can materially change actual results.
***
## Revenue summary at a glance
| Crop/product | Cycle | Scale | Annual production forecast | Annual revenue forecast |
| --------------------------------- | --------------------------- | -------------------- | ------------------------------------------------------------ | ------------------------- |
| Lettuce | Short cycle · 5 harvests/yr | 10 plots | 48,450 units per harvest · 242,250 units/yr | **\$133,237.50** |
| Passion fruit | Medium cycle · annual | 8 plots · 560 plants | 47,600 fruits · 3,661 nets | **\$11,019.61** |
| Coconut | Long cycle · perennial | 8 plots · 96 trees | 6,144 coconuts at maturity | **\$4,853.76** |
| Poultry eggs | Continuous | 110 hens | \~36,500 eggs/yr | Additional revenue stream |
| **Total projected gross revenue** | | | Crop forecast only; eggs excluded until pricing is finalized | **\~\$149,110.87 / yr** |
10% of gross crop revenue — approximately \$14,911.09/yr — is allocated to public goods activities per the Kokonut Common Data Schema. Actual harvests, prices, losses, and revenue records should be checked against hub.kokonut.network/projects/41.
***
## What this forecast helps prove
Short-cycle crops like lettuce create recurring harvests while slower perennial systems mature.
Coconut trees become the long-cycle anchor of the farm and the real-world backing logic behind Kokonut's tree-linked governance model.
A 10% allocation to public goods funds workshops, seedling distribution, nursery operations, and education.
The forecast becomes credible only when actual harvests are measured through MRV and published to the live Data Hub.
***
## Forecasting model
All crop forecasts derive from the same base formula:
```text theme={null}
Total Production = (Planting Density per m²)
× (Bed Area in m²)
× (Number of Beds per Plot)
× (Number of Plots)
× (1 − Loss Rate)
```
The **loss rate** accounts for crop management variability, climate conditions, irrigation reliability, soil health, pest pressure, and harvest handling. The figures below use a **15% loss rate** as the baseline planning assumption.
```text theme={null}
15% loss rate = 0.85 production multiplier
```
The most important number on this page is not the projected revenue total. It is the difference between the forecast and the actual. Actual harvest records should be used to improve the next planting cycle, refine the loss rate, and make future forecasts more accurate.
***
## Crop mix overview
Adelphi uses a three-cycle production model, so revenue arrives across different time horizons.
| Cycle | Crops/products | First harvest | Revenue role |
| ---------------- | --------------------------------------------------------------------------------------------------------- | ------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| **Short cycle** | Lettuce, broccoli, spinach, tomatoes, arugula, and minor vegetables | 30–75 days after planting | High-frequency, recurring cash flow |
| **Medium cycle** | [Indian Yam](https://www.gbif.org/species/2755239), [Passion Fruit](https://www.gbif.org/species/2874190) | 6–12 months | Seasonal compounding as the plantation matures |
| **Long cycle** | Coconut | 3–5 years, then multi-year production | Perennial anchor income and tree-backed governance logic |
| **Continuous** | Free-range eggs | Daily once hens are laying | Recurring food and revenue stream; not included in the crop revenue total until pricing is finalized |
This staggered structure is central to [syntropic farming](/kokonut-framework/why-syntropic-farming): species at different successional stages occupy the same land simultaneously, support each other's growth, and generate independent value at different times.
***
## How the forecast becomes a feedback loop
```mermaid theme={null}
flowchart TD
A["Planting plan"] --> B["Forecast assumptions"]
B --> C["Expected production + revenue"]
C --> D["Farm operations"]
D --> E["Harvest records"]
E --> F["MRV payloads"]
F --> G["Kokonut Hub + public records"]
G --> H["Forecast refinement"]
H --> B
C --> I["Public goods allocation"]
I --> J["Workshops, seedlings, nursery, education"]
J --> K["Community value"]
K --> H
```
The forecast should not stay static. As Adelphi collects actual harvest data, the model can improve:
* planting density assumptions can be adjusted;
* Loss rates can be updated by crop and season;
* local selling prices can be refined;
* Public goods allocations can be calculated from actual gross revenue;
* Future farms can reuse the improved model.
***
## Short cycle — Lettuce
Lettuce is the short-cycle cash-flow engine of Adelphi's forecast.
### Production variables
```text theme={null}
Planting Density: 12 lettuces / m²
Bed Area: 25 m²
Number of Beds per Plot: 19
Number of Plots: 10
Loss Rate: 15% (multiplier: 0.85)
Forecast harvests per year: 5
Theoretical maximum: 8–10 cycles/yr for fast-growing loose-leaf varieties
```
The annual projection uses **5 harvests per year** as the conservative planning figure. Fast-growing loose-leaf varieties can theoretically achieve 8–10 cycles per year, but the revenue forecast uses 5 to account for preparation, soil recovery, operational variability, and seasonal conditions.
### Applied example
| Step | Calculation | Result |
| ----------------------- | --------------------------------- | ------------------------------- |
| Lettuce per bed | `12 lettuces/m² × 25 m²` | 300 lettuces/bed |
| Lettuce per plot | `300 lettuces/bed × 19 beds/plot` | 5,700 lettuces/plot |
| Lettuce across 10 plots | `5,700 × 10` | 57,000 lettuces before loss |
| Effective production | `57,000 × 0.85` | **48,450 lettuces per harvest** |
### Production time by variety
| Variety | Days to harvest |
| ------------------------------------- | --------------- |
| Loose-leaf lettuce | 30–45 days |
| Head lettuce — Iceberg, Romaine, etc. | 60–75 days |
### Selling price and revenue
The lettuce model uses a conservative wholesale planning price of **\$0.55 per unit**. A higher price of **\$0.63 per unit** is treated as upside, not the baseline forecast.
| Scenario | Calculation | Result |
| ----------------------- | -------------------------- | --------------------- |
| Baseline per harvest | `48,450 × \$0.55` | **\$26,647.50** |
| Upside per harvest | `48,450 × \$0.63` | **\$30,523.50** |
| Baseline annual revenue | `\$26,647.50 × 5 harvests` | **\$133,237.50 / yr** |
### What to verify in the Data Hub
* actual units harvested per cycle;
* actual loss rate by harvest;
* actual selling price per unit;
* rejected, donated, consumed, or unsold units;
* seasonal differences across planting windows.
***
## Medium cycle — Passion fruit
Passion fruit is Adelphi's medium-cycle compounding crop. It does not reset as quickly as lettuce; productive capacity builds as vines mature.
### Production variables
```text theme={null}
Area per plot: 629 m²
Planting spacing: 3 × 3 meters (9 m²/plant)
Plants per plot: 70
Total plants (8 plots): 560
Annual production per plant: 100 passion fruits
Loss Rate: 15% (multiplier: 0.85)
Net annual production/plant: 85 passion fruits
Selling price per net: $3.01
Average net size: 13 passion fruits
```
### Applied example
| Step | Calculation | Result |
| --------------------- | -------------------------------------- | --------------------- |
| Net annual production | `85 passion fruits/plant × 560 plants` | 47,600 passion fruits |
| Nets produced | `47,600 ÷ 13 fruits/net` | 3,661 nets |
| Annual revenue | `3,661 nets × \$3.01/net` | **\$11,019.61 / yr** |
### Revenue characteristics
The net-based selling format of **\$3.01 per net of 13 fruits** is the planning baseline used for wholesale-style distribution. Direct community sales, organic market channels, or certification-supported distribution may create upside, but those should be tracked separately from the baseline forecast.
### What to verify in the Data Hub
* actual fruit count per plant;
* actual net size and packaging losses;
* wholesale vs direct-sale prices;
* vine establishment period;
* pest and disease pressure;
* seasonality of demand.
***
## Long cycle — Coconut
Coconut is the long-cycle anchor of the farm and the crop most directly connected to Kokonut Network's cooperative identity.
### Production variables
```text theme={null}
Area per plot: 629 m²
Planting spacing: 7 × 7 meters (49 m²/plant)
Plants per plot: 12
Total plants (8 plots): 96
Annual production per plant: 75 coconuts at full maturity
Loss Rate: 15% (multiplier: 0.85)
Net annual production/plant: 64 coconuts
Selling price per coconut: $0.79
First harvest timeline: 3–5 years from planting
Production life: Up to 20 years under optimal conditions
```
### Applied example
| Step | Calculation | Result |
| --------------------- | ----------------------------- | ------------------- |
| Net annual production | `64 coconuts/tree × 96 trees` | 6,144 coconuts |
| Annual revenue | `6,144 × \$0.79/coconut` | **\$4,853.76 / yr** |
### Revenue characteristics and timeline
Coconuts do not generate revenue immediately. The first harvest typically occurs **3–5 years after planting**, with full yield developing over subsequent seasons.
This delayed payback is why Adelphi uses short and medium-cycle crops. Lettuce and passion fruit bridge the establishment period while the coconut system matures.
Once established, coconut trees can produce for up to **20 years** under optimal conditions. When a tree ends its productive life, it is replanted, restarting the production cycle and continuing the cooperative model.
### Additional value streams beyond fresh coconut
* Coconut oil, milk, and water;
* coconut husks for on-site fertility and soil inputs;
* harvested wood for furniture and construction materials;
* long-term tree-backed cooperative legitimacy.
### What to verify in the Data Hub
* number of surviving trees;
* tree health and age class;
* first harvest date;
* coconuts per tree;
* actual price per coconut;
* derivative-product revenue if processing is added.
***
## Continuous production — Poultry eggs
The farm integrates **110 free-range laying hens**, with an estimated production of **\~100 eggs per day** or **\~36,500 eggs per year**.
Egg revenue is intentionally listed as an **additional revenue stream** rather than included in the crop revenue total until pricing, distribution, and loss assumptions are finalized.
| Variable | Planning value |
| --------------------- | ---------------------------------------------------------------------------- |
| Hens | 110 |
| Estimated daily eggs | \~100 |
| Estimated annual eggs | \~36,500 |
| Revenue status | Additional stream; excluded from crop total until pricing model is finalized |
The poultry system also supports the regenerative fertility loop. Hens produce manure that can be processed into humic acids and organic urea, reducing dependence on external synthetic inputs.
[Read the infrastructure page →](/ecosystem-wiki/kokonut-farms/adelphi/crops-biodiversity-and-infrastructure)
***
## Combined revenue and public goods allocation
```text theme={null}
Lettuce (short cycle): $133,237.50 / yr
Passion fruit (medium cycle): $11,019.61 / yr
Coconut (long cycle): $4,853.76 / yr
─────────────────────────────────────────────
Total projected gross revenue: $149,110.87 / yr
Public goods allocation (10%): $14,911.09 / yr
→ Community workshops
→ Free seedling distribution for neighbors
→ Endangered species nursery operations
→ Educational programming at the farm gazebo
Net operating revenue (90%): $134,199.78 / yr
```
The [SDG Impact Calculator](/kokonut-framework/impact-calculator) can use Adelphi's parameters — 15,725 m², full crop mix, rural location, women in leadership, biochar, and native species nursery — to estimate SDG scores and ecological outputs for this forecast.
***
## Forecast risk and sensitivity
Every forecast depends on assumptions. Adelphi's planning model should be read with these variables in mind:
| Variable | Why it matters |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Loss rate | A 15% loss baseline is used, but actual losses can increase due to drought, pests, disease, or operational disruptions. |
| Market price | Wholesale and retail prices can change by season, buyer, certification status, and distribution channel. |
| Labor availability | Harvest quality, planting cadence, and post-harvest handling depend on reliable labor and training. |
| Irrigation and water | Lettuce and other short-cycle crops are sensitive to water consistency and drainage. |
| Soil health | Biochar, organic inputs, and syntropic management can improve yields over time, but soil recovery is gradual. |
| Certification | Organic certification may improve market access, but timing and price effects should not be assumed until confirmed. |
| Data quality | Better farm records reduce uncertainty and improve the next forecast cycle. |
Forecasts should become more accurate over time. The goal is not to defend the first projection forever; the goal is to use live harvest data to improve the model.
***
## How actuals are verified
Adelphi's harvest forecast becomes credible only when actual farm activity is measured.
| Evidence layer | What it verifies |
| ---------------------------- | --------------------------------------------------------------------------------- |
| Harvest records | Crop type, quantity, date, quality, loss rate, sale status |
| Kokonut Hub | Public view of farm milestones, MRV events, and impact metrics |
| Field observations | Soil condition, crop condition, pests, irrigation, and operational notes |
| Satellite and remote sensing | Vegetation health, land-use change, and ecological trends |
| EAS attestations | Public records that connect structured evidence to the broader Kokonut data layer |
[Read the MRV methodology →](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification)
***
## What this page supports
Use the forecast as a planning model for planting schedules, crop mix, harvest tracking, and expected cash flow.
Inspect the assumptions underlying the farm's revenue model before evaluating proposals, reports, and public-goods allocations.
Compare projected revenue, jobs, public goods allocation, and SDG impacts against actual farm records.
Improve the calculator, forecast models, MRV schemas, dashboards, and Data Hub integrations.
***
## Next steps
The physical production system behind these numbers — beds, plots, poultry, nursery, biofactory, and soil regeneration.
How every harvest cycle becomes structured data, public evidence, and verifiable impact records.
Use Adelphi's parameters to estimate SDG scores, carbon outputs, employment effects, and impact alignment.
The live source of truth for actual harvest records, MRV events, milestones, and farm data.
How this revenue model supports No Poverty, Zero Hunger, Gender Equality, Decent Work, and Life on Land.
The full farm overview — project context, founders, Framework phase status, proof metrics, and live data links.
# Crops, Biodiversity, and Infrastructure
Source: https://kokonut.network/ecosystem-wiki/kokonut-farms/adelphi/crops-biodiversity-and-infrastructure
How Adelphi turns 13,838 m² of agricultural land into a regenerative production system: crops, biodiversity, poultry, biofertilizers, education space, and verifiable infrastructure.
# Adelphi's infrastructure is where the Kokonut model becomes visible.
This page documents the physical system behind Adelphi: the crop beds, syntropic plots, nursery, biofactory, poultry loop, training space, conservation work, and monitoring infrastructure that turn regenerative agriculture from a promise into measurable farm activity.
Adelphi is not only growing crops. It is building a replicable operating model for regenerative farms: diversified production, ecological restoration, on-site inputs, public MRV, community education, and market access.
The infrastructure below produces the crop, biodiversity, poultry, soil, and MRV records that make Adelphi auditable.
13,838
m² agricultural area
***
## System at a glance
Short-cycle vegetables, medium-cycle fruits, perennial coconut trees, and continuous egg production create multiple revenue streams rather than a single-harvest dependency.
Native agroforestry species, at-risk fruit trees, ground cover systems, and nursery propagation turn production into ecological restoration.
Bamboo biochar, poultry manure, humic acids, organic urea, forage, and crop residues reduce dependence on external synthetic inputs.
The gazebo and farm layout support workshops, community education, agroforestry training, and intergenerational knowledge transfer.
Organic certification, local distribution, and future supermarket relationships create a path from regenerative production to reliable revenue.
GPS registration, satellite vegetation indices, field observations, and the Kokonut Hub make progress visible to DAO members and partners.
This page is the physical counterpart to the MRV page. MRV explains how farm activity becomes public evidence; this page explains the infrastructure that generates that evidence.
***
## The Adelphi farm system
```mermaid theme={null}
flowchart TD
A["13,838 m² agricultural area"] --> B["Syntropic crop beds"]
A --> C["Agroforestry + native species"]
A --> D["Free-range poultry"]
A --> E["Nursery + biofactory"]
A --> F["Training gazebo"]
B --> G["Short, medium, and long-cycle production"]
C --> H["Biodiversity + habitat restoration"]
D --> I["Eggs + manure"]
E --> J["Biochar + humic acids + organic urea"]
F --> K["Education + community knowledge transfer"]
I --> J
J --> B
H --> L["Ecological resilience"]
G --> M["Revenue + food access"]
K --> N["Replication capacity"]
B --> O["MRV records"]
C --> O
D --> O
E --> O
F --> O
O --> P["Kokonut Hub + EAS attestations"]
```
Adelphi's infrastructure is designed to answer one practical question:
> Can one farm produce food, restore biodiversity, create jobs, train people, verify impact, and generate revenue without becoming extractive?
The answer depends on the system as a whole — not on a single crop, facility, or funding event.
***
## Production overview
The project allocates **13,838 m²** to an agro-ecological garden designed around three production cycle lengths:
| Cycle | Crops | Revenue role | Why it matters |
| ------------ | ------------------------------------------------------------------- | ----------------------- | ----------------------------------------------------- |
| Short cycle | Lettuce, broccoli, spinach, tomatoes, arugula, and minor vegetables | Frequent cash flow | Creates near-term harvests and local food access |
| Medium cycle | Passion fruit, Indian yams, and other seasonal crops | Seasonal compounding | Builds revenue as the farm matures |
| Long cycle | Coconut and native agroforestry species | Perennial anchor income | Supports long-term ecological and economic continuity |
| Continuous | Free-range eggs | Daily production stream | Adds recurring revenue and closed-loop fertility |
This multi-cycle structure is central to [syntropic farming](/kokonut-framework/why-syntropic-farming): different species occupy different vertical and temporal niches, support each other's growth, and produce value on different timelines.
Every crop bed, plot boundary, and production zone is individually GPS-registered through [Silvi](https://www.silvi.earth/) and monitored through the [Kokonut MRV stack](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification). Vegetation health is tracked with satellite indices including NDVI, NDRE, and MSAVI.
[Read the crop and harvest forecast →](/ecosystem-wiki/kokonut-farms/adelphi/crops-and-harvest-forecast)
***
## Productive diversification and species conservation
SDG 15 — Life on Land
SDG 2 — Zero Hunger
### Fruit and agroforestry production
In the higher areas of the land, Adelphi establishes fruit orchards and agroforestry systems that serve two roles at once: commercial production and ecological restoration.
Primary productive species include:
| Species | Role in the system |
| ----------------------------------------------------- | -------------------------------------------------------------------------- |
| [Passion fruit](https://www.gbif.org/species/2874190) | Medium-cycle fruit revenue and vine-based canopy structure |
| [Indian Yam](https://www.gbif.org/species/2755239) | Medium-cycle food production and local crop diversity |
| Coconut | Long-cycle perennial anchor crop tied to Kokonut's farm-backed token model |
| [Lipsticktree](https://www.gbif.org/species/2874863) | Agroforestry and cultural/ecological value |
| [Custard Apple](https://www.gbif.org/species/5407123) | At-risk fruit species conserved through the nursery |
| [Soursop](https://www.gbif.org/species/5407273) | Fruit production and local agrobiological heritage |
This structure implements the [third principle of regeneration](/kokonut-framework/framework-components/framework-features/5-principles-of-regeneration): enhancing biodiversity through crop rotation, agroforestry, and silvo-pasture techniques.
### Wildlife sustainability and ecological restoration
A multi-species plantation system supports habitat, pollinators, soil structure, and local wildlife across the farm.
| Category | Species | Ecological role |
| --------------- | ----------------------------------------------------------- | ------------------------------------------------- |
| Palm and canopy | [Hispaniola palmetto](https://www.gbif.org/species/2732565) | Native, regionally significant canopy layer |
| Fruit-bearing | [Naseberry](https://www.gbif.org/species/2884162) | Sapotaceae family, food and habitat value |
| Fruit-bearing | [Star Apple](https://www.gbif.org/species/2885828) | Sapotaceae family, canopy diversity |
| Fruit-bearing | [Mammee Apple](https://www.gbif.org/species/5407123) | High ecological and food value |
| Fruit-bearing | [Custard Apple](https://www.gbif.org/species/5407123) | At-risk species conserved in a nursery |
| Agroforestry | [Jagua](https://www.gbif.org/species/2895593) | Native species with cultural and ecological value |
| Agroforestry | [Cashew](https://www.gbif.org/species/5421368) | Multi-use food and canopy contribution |
| Agroforestry | [Guavaberry](https://www.gbif.org/species/3186420) | Cultural and ecological significance |
| Agroforestry | [Congo coffee tree](https://www.gbif.org/species/2895528) | Understory canopy species |
| Cacao | [Native cacao](https://www.gbif.org/species/3152205) | Native variety and heritage preservation |
| Hedgerow | Florida fiddlewood | Habitat and boundary support |
| Ground cover | Princess vine and bejuco | Ecological corridor support |
| Hardwood | Logwood | Habitat and dyewood species |
### Nursery for at-risk species
The Adelphi biofactory and nursery, where endangered species are propagated, and biological inputs are produced on-site from farm-sourced materials.
The farm features a specialized nursery dedicated to reproducing endangered, critically threatened, and highly vulnerable plant species native to the Dominican Republic.
Native varieties propagated here are distributed **free of charge** to visitors and nearby communities, making the nursery a public good that extends Adelphi's impact on biodiversity beyond the farm boundary.
This directly implements the [fourth principle of regeneration](/kokonut-framework/framework-components/framework-features/5-principles-of-regeneration): protecting living roots and perennial crops that anchor and restore degraded ecosystems over time.
***
## Agro-ecological techniques and soil regeneration
SDG 15 — Life on Land
SDG 13 — Climate Action
### Biochar for soil improvement
All crops at Adelphi are managed using biochar produced on-site from bamboo found along the farm's boundary perimeter. The production process uses pyrolysis — controlled high-temperature combustion in a low-oxygen environment — and incorporates mineral-rich rocks to improve soil regeneration and nutrient retention.
Biochar supports two outcomes central to the Kokonut Framework:
* **Soil improvement:** better water retention, higher nutrient availability, and improved microbial habitat.
* **Carbon storage:** more stable carbon in the soil compared with fast-decomposing organic residues.
Biochar effects are tracked through soil monitoring, field observations, and annual MRV reporting.
### Syntropic farming plots
Two plots are dedicated to the implementation of full syntropic farming. These plots optimize plant interactions across vertical strata:
| Stratum | Function |
| ------------- | ----------------------------------------------------- |
| Ground cover | Protects soil, retains moisture, reduces erosion |
| Low canopy | Supports food production and species diversity |
| Medium canopy | Builds fruit and vine productivity |
| High canopy | Provides long-term shade, habitat, roots, and biomass |
The syntropic plots are living demonstrations of [syntropic farming](/kokonut-framework/why-syntropic-farming) applied to Dominican soil conditions, rainfall patterns, native species, and community food needs.
### Vegetative cover and erosion control
Permanent ground cover is implemented using [beard grass](https://www.gbif.org/species/5677150) along the edges of terraced areas. This reduces erosion on sloped terrain, improves soil structure, builds organic matter, and helps the farm remain resilient during periods of heavy rainfall in Monte Plata.
This is a direct implementation of the [second principle of regeneration](/kokonut-framework/framework-components/framework-features/5-principles-of-regeneration): year-round cover crops that prevent bare soil, provide forage, and build organic matter that supports long-term fertility.
***
## Regenerative poultry production
SDG 8 — Decent Work
SDG 15 — Life on Land
### Free-range egg production
Adelphi integrates **110 free-range laying hens**, producing an estimated **100 eggs per day**. The hens are fed with forage grown on-site, primarily Pangola grass, reducing dependency on imported feed while creating a continuous food and revenue stream.
The hens contribute to the farm beyond egg production. They help manage ground cover, add organic matter, reduce pest pressure, and generate manure for biological input production.
### Closed-loop organic waste management
Poultry manure is processed into **humic acids** and **organic urea** for the bio-intensive garden. This replaces synthetic nitrogen inputs with farm-produced fertility.
```text theme={null}
Pangola grass → hens → eggs + manure →
humic acids + organic urea → crop beds →
healthier crops → more forage → back to hens
```
This closed-loop system implements the [fifth principle of regeneration](/kokonut-framework/framework-components/framework-features/5-principles-of-regeneration): compost and biofertilizers that restore soil fertility through organic matter cycling.
***
## Infrastructure and training
The Adelphi farm polygon — showing the spatial organization of agro-ecological beds, agroforestry zones, syntropic plots, poultry area, and community infrastructure across the 15,725 m² site.
### Agro-ecological training and education space
SDG 4 — Quality Education
SDG 8 — Decent Work
A multipurpose **gazebo** serves as the farm's community hub. It functions as a dining area, meeting room, training center, and demonstration space.
The education space supports workshops and courses on:
* Organic farming principles and syntropic planting techniques
* Agroforestry design and native species propagation
* Biochar production, soil health, and water retention
* Sustainable poultry management and organic waste processing
* Farm data collection, reporting, and MRV literacy
The education center is designed for farm operators, farmers from nearby communities, children, elders, visitors, and anyone interested in sustainable land stewardship.
### Organic certification and market distribution
SDG 2 — Zero Hunger
SDG 12 — Responsible Consumption
Adelphi is pursuing official **organic certification from the Dominican Republic's Ministry of Agriculture**. Certification is important because it creates a path toward premium market access and formal institutional distribution channels.
Current certification status: **in progress**.
Once certification is achieved, harvested products can be distributed through:
* **Specialized organic food businesses** — direct relationships with organic market networks
* **Local and regional supermarkets** — formal supply chain relationships that support revenue predictability
* **Community direct sales** — local food access alongside commercial distribution
### Expansion and conservation
Adelphi's medium-term plan includes acquiring adjacent land to preserve local flora and fauna while increasing organic vegetable production capacity.
Any land acquisition should go through a formal [DAO funding proposal](/ecosystem-wiki/the-kokonut-dao/proposal-templates), ensuring expansion is governed by the community rather than a single decision-maker.
***
## How is this infrastructure verified?
Adelphi's physical infrastructure produces measurable evidence. The point is not only to describe the farm, but to make its progress inspectable.
| Infrastructure layer | What it produces | How it is verified |
| ---------------------- | -------------------------------------------------------------- | ----------------------------------------------------- |
| Crop beds | Harvests, crop cycle records, and planting density data | Kokonut Hub, field logs, harvest reports |
| Syntropic plots | Vegetation health, soil cover, multi-strata production | Satellite indices, field observations, GPS records |
| Nursery and biofactory | Native species propagation, biochar, humic acids, organic urea | Nursery inventory, input logs, MRV events |
| Poultry system | Eggs, manure, nutrient cycling, and forage use | Poultry records, soil EC readings, farm logs |
| Training gazebo | Workshops, community engagement, knowledge transfer | Event records, attendance logs, community reports |
| Market infrastructure | Certification progress, buyers, and distribution channels | Certification status, sales records, Data Hub updates |
[Read the full MRV methodology →](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification)
***
## What this page proves
Adelphi is not only a concept. It has mapped plots, crop beds, animals, a nursery, a biofactory, infrastructure, and field-level monitoring.
The five principles are implemented through cover crops, syntropic planting, biodiversity, animal integration, and organic input cycling.
Crop cycles, egg production, and future market channels create practical economic reasons for regeneration to continue.
GPS records, satellite indices, soil observations, farm logs, and the Kokonut Hub turn physical work into verifiable public evidence.
***
## Next steps
The production formula and revenue projections for each crop — including lettuce, passion fruit, coconut, and eggs.
How farm activity becomes structured data, IPFS records, EAS attestations, and public impact evidence.
The Kokonut Framework principles implemented by the infrastructure documented on this page.
The methodology behind the syntropic plots and why this farming model compounds ecological value over time.
How Adelphi's crops, infrastructure, and community programs align with the five UN SDGs.
Contribute as an agronomist, researcher, developer, DAO member, capital allocator, or community organizer.
# Problem & Solution
Source: https://kokonut.network/ecosystem-wiki/kokonut-farms/adelphi/problem-and-solution
How Adelphi turns seven local community challenges into one integrated regenerative farm solution — jobs, food, education, biodiversity, women-led leadership, public goods, and verifiable impact.
# Adelphi turns local challenges into a regenerative community system.
Adelphi is not solving one isolated problem. It is responding to a compound local reality: limited employment, food insecurity, degraded land, loss of farming knowledge, lack of community spaces, gender barriers, and limited access to regenerative education.
The farm was designed as a systemic response. Public goods funding helped build the infrastructure. Syntropic farming turns the land into a productive living system. Community programs reconnect people to agriculture. MRV makes progress visible. The Kokonut Framework turns the whole model into something other farms can learn from and replicate.
Adelphi is the local proof case for Kokonut's broader thesis: the problem is not the land — it is the coordination layer around it.
***
## From a global problem to a local community
The [global agricultural funding gap](/ecosystem-wiki/kokonut-101/problem) is not abstract. It appears in communities as underused land, limited employment opportunities, limited access to fresh food, weak local infrastructure, environmental degradation, and a lack of trusted reporting systems.
In the area surrounding Adelphi — near the batey and Haty community in Gonzalo, Sabana Grande de Boyá, Monte Plata, Dominican Republic — these pressures are real community conditions. Yanny and Neury Hernández built Adelphi to respond directly to those conditions.
Adelphi is not a donation project. It is a productive syntropic farm, a community learning space, a biodiversity restoration site, a women-led agricultural enterprise, and a live data source for the Kokonut Framework.
Public Nouns Proposal #69 funded Adelphi's critical infrastructure, helping the farm start as a public good from day one. The value flywheel shows how infrastructure creates community employment, organic food production, education, biodiversity restoration, and public data that can inform the next farm.
***
## Proof at a glance
PN #69
public goods funded
***
## The seven local challenges
Residents need stable income opportunities that do not require them to migrate from the community.
Farmers and families need practical access to organic, syntropic, and soil-regenerating methods.
Communities need fresh, local, nutritious food rather than relying solely on imported or processed products.
The land needs soil restoration, biodiversity, agroforestry, and incentives for long-term stewardship.
Younger generations need spaces where farming knowledge can be practiced, taught, and renewed.
Children, elders, farmers, and families need safe gathering places for learning, recreation, and coordination.
Women need visible leadership pathways in ownership, farm operations, education, and community governance.
Adelphi addresses these issues together because each problem reinforces the others.
***
## How the challenges compound
```mermaid theme={null}
flowchart TD
A["Limited employment"] --> B["Lower household income"]
B --> C["Food insecurity"]
C --> D["Reduced community capacity"]
D --> E["Agricultural abandonment"]
E --> F["Soil degradation + biodiversity loss"]
F --> G["Less productive land"]
G --> A
H["Lack of regenerative education"] --> E
I["Weak community spaces"] --> D
J["Gender barriers"] --> D
K["Cultural disconnection from land"] --> E
style A fill:#fee2e2,stroke:#ef4444,color:#991b1b
style B fill:#fee2e2,stroke:#ef4444,color:#991b1b
style C fill:#fee2e2,stroke:#ef4444,color:#991b1b
style D fill:#ffedd5,stroke:#f97316,color:#7c2d12
style E fill:#fee2e2,stroke:#ef4444,color:#991b1b
style F fill:#fee2e2,stroke:#ef4444,color:#991b1b
style G fill:#fee2e2,stroke:#ef4444,color:#991b1b
```
Each challenge weakens the community's ability to respond to the others. That is why Adelphi was designed as a whole system: income, food, education, biodiversity, social infrastructure, women-led leadership, and measurable impact working together.
***
## The seven solutions
### 1. Economic hardship → regenerative employment and revenue
SDG 1 — No Poverty
SDG 8 — Decent Work
**Problem:** Many families face limited income opportunities, and available work often requires migration to urban centers. This weakens local capacity and disconnects people from productive land.
**Adelphi's response:** Adelphi creates documented local employment through organic and syntropic agriculture. The farm currently supports **7 jobs**, and its three-cycle crop model projects approximately **\$149,110.26 in annual revenue** before actuals are reconciled through live records.
Revenue projections are planning figures. Actual harvest and financial records should be checked against the Kokonut Hub as data is reported.
[See the full harvest forecast →](/ecosystem-wiki/kokonut-farms/adelphi/crops-and-harvest-forecast)
***
### 2. Limited regenerative education → a living training center
SDG 8 — Decent Work
SDG 15 — Life on Land
**Problem:** Sustainable farming knowledge is not evenly available. Communities may know the land, but still lack access to practical training in syntropic planting, organic pest management, soil regeneration, and farm data practices.
**Adelphi's response:** Adelphi serves as a training site where local farmers and community members can learn by working directly with the land. The multipurpose gazebo serves as a dining area, meeting room, and education center for workshops, farmer training, and community learning.
[See crops, biodiversity, and infrastructure →](/ecosystem-wiki/kokonut-farms/adelphi/crops-biodiversity-and-infrastructure)
***
### 3. Food insecurity → local organic production
SDG 2 — Zero Hunger
**Problem:** Communities can be surrounded by fertile land while still lacking consistent access to fresh, nutritious, locally produced food.
**Adelphi's response:** Adelphi grows a diversified crop mix across short, medium, and long cycles: lettuce, broccoli, spinach, tomatoes, arugula, passion fruit, Indian yams, coconut, and poultry eggs. Short-cycle vegetables support immediate food availability and cash flow; medium- and long-cycle crops build stability over time.
Vegetables such as lettuce and other leafy crops create fast, recurring harvests.
Passion fruit and Indian yams create seasonal revenue and nutritional diversity.
Coconut trees build a perennial income base and support the 1:1 tree-backed governance thesis.
[See crop diversity →](/ecosystem-wiki/kokonut-farms/adelphi/crops-biodiversity-and-infrastructure)
***
### 4. Environmental degradation → syntropic regeneration and biodiversity
SDG 15 — Life on Land
**Problem:** Deforestation, soil depletion, and biodiversity loss become more likely when short-term extraction is more economically rational than long-term stewardship.
**Adelphi's response:** Adelphi uses syntropic farming, agroforestry, organic inputs, biochar enrichment, and the propagation of native/endangered species to restore soil function and biodiversity while producing food. Its nursery supports at-risk native species and distributes biodiversity value beyond the farm itself.
[See the biodiversity program →](/ecosystem-wiki/kokonut-farms/adelphi/crops-biodiversity-and-infrastructure)
***
### 5. Cultural disconnection from land → intergenerational learning
SDG 2 — Zero Hunger
SDG 15 — Life on Land
**Problem:** Younger generations often grow up disconnected from traditional farming knowledge and sustainable land use. When knowledge is not practiced, it disappears.
**Adelphi's response:** The farm becomes a place where children, adults, and elders can reconnect with the land through hands-on learning, weekend activities, farm visits, and regenerative agriculture education.
[Read Yanny and Neury's story →](/ecosystem-wiki/kokonut-farms/adelphi/background-story)
***
### 6. Lack of community spaces → a permanent learning and gathering hub
SDG 1 — No Poverty
SDG 8 — Decent Work
**Problem:** Without safe, engaging spaces for learning, recreation, and gathering, communities have fewer opportunities to coordinate, teach, organize, and build shared capacity.
**Adelphi's response:** The multipurpose gazebo and farm environment provide a permanent space for workshops, meals, meetings, children's programming, elder engagement, and community learning. The farm itself becomes social infrastructure.
***
### 7. Gender inequality → women-led agricultural leadership
SDG 5 — Gender Equality
**Problem:** Women in rural agricultural communities often face barriers to economic independence, land ownership, leadership, access to credit, and decision-making power.
**Adelphi's response:** Adelphi is founded and led by sisters **Yanny and Neury Hernández**. Their leadership is visible across ownership, operations, community engagement, education, and the farm's public story. This makes Adelphi a practical example of the Kokonut Manifesto's principle that those who add value should have access to governance and ownership.
[Read Yanny and Neury's story →](/ecosystem-wiki/kokonut-farms/adelphi/background-story) · [See SDG alignment →](/ecosystem-wiki/kokonut-farms/adelphi/sustainable-development-goals)
***
## How the solutions work together
```mermaid theme={null}
flowchart TD
PN["Public Nouns #69 funding"] --> INFRA["Farm infrastructure"]
INFRA --> JOBS["Local jobs + farmer income"]
INFRA --> EDU["Training gazebo + community programs"]
INFRA --> FOOD["Organic crop + egg production"]
INFRA --> BIO["Syntropic agroforestry + biodiversity nursery"]
JOBS --> CAP["Higher community capacity"]
EDU --> CAP
FOOD --> HEALTH["Better local nutrition"]
BIO --> LAND["Improved soil + ecosystem function"]
CAP --> REPL["Model becomes easier to replicate"]
HEALTH --> CAP
LAND --> FOOD
MRV["MRV + public records"] --> TRUST["Trust for DAO members, contributors, funders, and communities"]
FOOD --> MRV
BIO --> MRV
JOBS --> MRV
TRUST --> REPL
```
Adelphi's purpose is not only to make one farm productive. It is to produce a visible, measurable pattern that other farms can reuse: fund infrastructure, grow food, create work, restore land, educate the community, report evidence, and improve the Framework.
***
## How progress is verified
Adelphi's solutions become credible because farm activity is measured and reported. Kokonut's MRV stack turns farm events into structured evidence that DAO members, grant reviewers, researchers, developers, contributors, and communities can inspect.
| Layer | What it helps verify |
| -------------------------------------- | ---------------------------------------------------------------------------------- |
| Live Kokonut Hub data | Harvest records, MRV events, farm milestones, and impact metrics. |
| Satellite and remote sensing | Vegetation health, land-use change, and farm-level ecological trends. |
| Field observations and soil monitoring | Ground-level evidence about soil, crop condition, water, and farm operations. |
| Per-plant and geospatial records | Specific plantings, farm layout, species data, and biodiversity tracking. |
| EAS attestations | Public records that connect structured evidence to the broader Kokonut data layer. |
[Read the MRV methodology →](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification)
***
## What Adelphi proves
Poverty, food insecurity, soil degradation, gender barriers, and weak community spaces reinforce one another. A single intervention is not enough.
Syntropic agriculture can restore land while producing food, income, biodiversity, and educational value.
Infrastructure funded once can continue generating jobs, food, learning, ecological benefits, and public records over time.
MRV turns local farm activity into evidence that communities, funders, contributors, and DAO members can inspect.
***
## Next steps
The full farm overview: founders, metrics, status, live data, location, infrastructure, revenue forecast, and SDG alignment.
The physical systems behind the solutions: crop beds, nursery, poultry, biofactory, gazebo, irrigation, and farm infrastructure.
The production model and revenue forecast behind the economic solution.
How Adelphi addresses SDG 1, SDG 2, SDG 5, SDG 8, and SDG 15 through measurable farm activity.
The measurement-and-verification stack behind Adelphi's public evidence layer.
Help replicate the model as an agronomist, developer, researcher, community organizer, DAO member, or capital allocator.
# Executive Summary
Source: https://kokonut.network/ecosystem-wiki/kokonut-farms/adelphi/summary
A concise proof page for Kokonut Network's first live syntropic farm: founders, land, crops, revenue forecast, MRV stack, SDG alignment, and live data.
# Adelphi is the proof that Kokonut works on real land.
Adelphi is Kokonut Network's first live syntropic farm — a women-led, community-first agricultural project in Gonzalo, Sabana Grande de Boyá, Monte Plata, Dominican Republic.
It is not a concept deck, prototype, or future promise. It is a working farm with land, founders, crops, infrastructure, revenue forecasts, public goods funding, MRV monitoring, and live data available through the Kokonut Hub.
The canonical source of truth is the live Data Hub. This page summarizes the project, model, and evidence.
PN #69
public goods funded
***
## Why Adelphi matters
Adelphi demonstrates all four parts of the Kokonut model at once:
Public goods funding helped deploy critical farm infrastructure without turning Adelphi into a corporate extraction project.
The farm runs through the Kokonut Framework: planning, soil preparation, production, regeneration, MRV, impact reporting, and expansion.
Satellite imagery, soil probes, field logs, per-plant GPS, IPFS records, and EAS attestations turn farm activity into public evidence.
Adelphi combines organic food production, local employment, biodiversity conservation, women-led leadership, and public goods allocation.
Adelphi is the credibility bridge between Kokonut's thesis and Kokonut's reality. If the global problem is underfunded regenerative agriculture, Adelphi is the first working proof that the DAO + Framework + MRV model can close that gap.
***
## Project at a glance
| **Field** | **Value** |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Farm** | Adelphi |
| **Location** | Gonzalo, Sabana Grande de Boyá, Monte Plata, Dominican Republic |
| **Coordinates** | [18°56'19.7"N 69°44'06.0"W](https://www.google.com/maps/place/18%C2%B056%2719.7%22N+69%C2%B044%2706.0%22W/@18.9387931,-69.735003,1058m/data=!3m2!1e3!4b1!4m4!3m3!8m2!3d18.9387931!4d-69.735003?entry=ttu\&g_ep=EgoyMDI0MDgyOC4wIKXMDSoASAFQAw==) |
| **Founders/operators** | Yanny & Neury Hernández |
| **Farm model** | Women-led, community-first syntropic farm |
| **Total area** | 15,725 m² |
| **Agricultural area** | 13,838 m² agro-ecological garden |
| **Framework phase** | Phase II — Production & Regeneration |
| **Funding milestone** | [Public Nouns Proposal #69](https://publicnouns.wtf/vote/69) |
| **Live data** | [hub.kokonut.network/projects/41](https://hub.kokonut.network/projects/41) |
| **3D land model** | [Adelphi Ortho3D ↗](https://link.kokonut.network/AdelphiOrtho3D) |
| **Species geodata** | [Adelphi Species GeoNode ↗](https://link.kokonut.network/AdelphiSpeciesGeoNode) |
***
## The founders
Yanny and Neury grew up in a farming family, spending childhood vacations at their grandparents' countryside home in the Dominican Republic. Although they built careers in the city — Yanny in pharmaceuticals, Neury as a professional manicurist — their connection to the land never faded.
Two years ago, they took a bold step: they purchased land in Monte Plata with the intention to farm it, only to discover that financing cultivation was the hardest part. Adelphi was born from that gap — a project designed not only to secure their future, but to benefit the surrounding community through organic production, biodiversity education, and a gathering space for children, elders, and neighbors who want to reconnect with the land.
[Read the full background story →](/ecosystem-wiki/kokonut-farms/adelphi/background-story)
***
## How Adelphi works
Adelphi uses a three-cycle syntropic production model. Short-cycle vegetables create near-term cash flow, medium-cycle fruits add seasonal income, and long-cycle coconut trees build the perennial asset base that connects the farm back to Kokonut's tree-backed governance model.
```mermaid theme={null}
flowchart TD
A["Public goods funding\nPublic Nouns #69"] --> B["Farm infrastructure\nwater · tools · nursery · poultry · training space"]
B --> C["Syntropic production\nshort · medium · long cycles"]
C --> D["MRV evidence\nsatellite · soil · field logs · GPS"]
D --> E["Public records\nData Hub · IPFS · EAS attestations"]
E --> F["Revenue + impact\nlocal jobs · food · biodiversity · public goods"]
F --> G["Framework replication\nnext farm launches faster"]
G --> C
```
***
## Revenue projection at a glance
Adelphi's three-cycle crop model generates revenue across different timeframes. Actual performance is tracked in the [Live Data Hub](https://hub.kokonut.network/projects/41), while projections are calculated through the [Crops & Harvest Forecast](/ecosystem-wiki/kokonut-farms/adelphi/crops-and-harvest-forecast) methodology.
| **Crop / stream** | **Cycle** | **Annual production** | **Est. annual revenue** |
| ------------------- | --------------------------------- | ----------------------------------------- | ------------------------- |
| Lettuce | Short — 30–75 days, 5 harvests/yr | 48,450 units across 10 plots | \$133,237.50 |
| Passion fruit | Medium — annual | 47,600 fruits · 3,661 nets across 8 plots | \$11,019.00 |
| Coconut | Long — perennial | 6,144 coconuts across 8 plots | \$4,853.76 |
| Poultry eggs | Continuous | \~36,500 eggs/yr | Additional revenue stream |
| **Total projected** | | | **\~\$149,110.26 / yr** |
The forecast uses conservative planning assumptions, including a 15% crop loss rate and 5 lettuce harvests per year. Actual yields, losses, harvest records, and impact metrics should be checked against the Data Hub.
10% of gross revenue — approximately \$14,911 per year at forecasted performance — is allocated to public goods activities under the Kokonut Common Data Schema.
***
## What is growing
Lettuce, broccoli, spinach, tomatoes, arugula, and other minor crops provide fast, recurring harvests and early operational cash flow.
Passion fruit and Indian yam add seasonal revenue and nutritional diversity as the farm matures.
Coconut trees anchor the perennial income base and connect Adelphi to Kokonut's broader 1:1 tree-backed governance logic.
110 free-range hens produce approximately 100 eggs per day. Poultry manure is processed into humic acids and organic urea for on-site fertilization.
Adelphi propagates native and endangered species for conservation, education, biodiversity restoration, and free distribution to visitors and neighboring communities.
The farm includes a multipurpose education space for workshops, meetings, community programming, and agro-ecological training.
[See crops, biodiversity, and infrastructure →](/ecosystem-wiki/kokonut-farms/adelphi/crops-biodiversity-and-infrastructure)
***
## How Adelphi is verified
Every significant farm event — MRV submissions, harvest milestones, funding approvals, and impact records — is designed to move from field activity into public evidence.
| **Layer** | **What it verifies** | **Tools / methods** |
| ----------------------- | ----------------------------------- | ----------------------------------------------------------------------------------- |
| **Remote sensing** | Vegetation health and land change | Landsat 8, Sentinel-2, NDVI, NDRE, ReCI, MSAVI, drone orthomosaics, QGIS |
| **Ground sensing** | Soil and crop conditions | Soil moisture, volumetric water content, electrical conductivity, soil temperature |
| **Community analytics** | Human-observed field activity | Atlantis App field observations, crop cycle stage, disease flags, plant health logs |
| **Per-plant GPS** | Individual tree and species records | Silvi plant registration, geodata, health status, phenology records |
| **On-chain evidence** | Public, tamper-resistant proof | IPFS/Filecoin records, Farm Registry events, EAS attestations |
| **Public reporting** | Network-level accountability | Kokonut Hub, EBF reports, CRISP risk analysis, SDG alignment records |
[Read the full MRV methodology →](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification)
***
## Framework phase
Adelphi is currently operating in **Phase II — Production and Regeneration** of the [Kokonut Framework development phases](/kokonut-framework/development-phases/phase-ii).
| **Phase** | **Status** | **Description** |
| ---------------------------------------------------------------------------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------ |
| [Phase I — Planning & Preparation](/kokonut-framework/development-phases/phase-i) | ✅ Complete | Soil diagnosis, crop selection, infrastructure, personnel training, and biochar-based soil preparation |
| [Phase II — Production & Regeneration](/kokonut-framework/development-phases/phase-ii) | 🔄 Active | Agro-ecological practices implemented, soil regeneration underway, all three crop cycle lengths planted |
| [Phase III — Consolidation & Expansion](/kokonut-framework/development-phases/phase-iii) | Upcoming | Harvesting protocols, go-to-market strategy, organic certification, biodiversity expansion, adjacent land strategy |
| [Phase IV — MRV](/kokonut-framework/development-phases/phase-iv) | Ongoing | Continuous across all phases — data recorded, attested on-chain, and published to the Data Hub |
Phase IV MRV is not a final phase that starts after the farm is mature. It runs continuously across the farm's entire operational life.
***
## Impact alignment
Adelphi directly addresses five Sustainable Development Goals through concrete farm activities.
| **SDG** | **How Adelphi contributes** | **Evidence path** |
| --------------------------- | ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| **SDG 1 — No Poverty** | Sustainable employment and income diversification through multi-cycle crop production | Jobs supported, revenue forecast, farm payroll and operations records |
| **SDG 2 — Zero Hunger** | Organic food production for local markets and community food access | Harvest records, crop diversity, Data Hub outputs |
| **SDG 5 — Gender Equality** | Women-led ownership, leadership, and operational management | Founder story, governance records, farm management documentation |
| **SDG 8 — Decent Work** | Fair employment, skills training, and agro-ecological education | Training records, job creation, education center activity |
| **SDG 15 — Life on Land** | Biochar soil regeneration, native species nursery, agroforestry, and biodiversity conservation | MRV data, species geodata, nursery logs, EBF reporting |
[Read the full SDG alignment →](/ecosystem-wiki/kokonut-farms/adelphi/sustainable-development-goals)
***
## What Adelphi proves
Adelphi exists to prove that Kokonut's model can turn undercapitalized land into a regenerative, community-owned, publicly verifiable production system.
Adelphi shows how capital can reach farmers without giving corporations control over the upside.
The farm combines soil restoration, biodiversity, organic production, and revenue generation rather than treating ecology and economics as separate goals.
MRV turns farm activity into public evidence that can be inspected by DAO members, partners, researchers, and community contributors.
Adelphi is the first implementation of the Framework. Every lesson, dataset, workflow, and attestation improves the next farm launch.
***
## Explore Adelphi deeper
The seven local challenges Adelphi addresses — economic hardship, food insecurity, environmental degradation, gender inequality, and more.
The full production system — syntropic plots, fruit orchards, endangered species nursery, poultry farm, and training infrastructure.
Production formulas, yield projections, revenue estimates, loss assumptions, and seasonal planning across all crop cycles.
How Yanny and Neury Hernández built Adelphi from a dream of returning to the land — and what it means for their community.
Adelphi's SDG framework — how each goal is addressed, measured, and reported through the Kokonut Framework.
Real-time harvest records, MRV events, and aggregated impact metrics — the canonical source of truth for Adelphi's actual performance.
# Sustainable Development Goals
Source: https://kokonut.network/ecosystem-wiki/kokonut-farms/adelphi/sustainable-development-goals
How Adelphi maps real farm activity to five SDGs through jobs, food production, women-led ownership, regenerative infrastructure, MRV, and annual impact reporting.
# Adelphi's SDG alignment is not a label. It is an evidence system.
Adelphi directly addresses five Sustainable Development Goals through measurable farm operations, including local jobs, diversified food production, women-led ownership, regenerative land management, public goods allocation, and annual impact reporting.
The purpose of this page is to show the connection between **farm activity → SDG outcome → evidence → reporting**. Each claim should be inspectable through the Kokonut [MRV methodology](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification), the [Kokonut Hub](https://hub.kokonut.network/projects/41), farm records, and annual reporting cycles.
SDG claims become credible only when they are tied to farm records, MRV events, and annual reports.
***
## Impact at a glance
10%
public goods allocation
| SDG | Adelphi contribution | Primary evidence |
| ----------------------- | -------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| SDG 1 — No Poverty | Jobs, farm revenue, public goods allocation, and local income resilience | Employment records, sales records, public goods allocation, annual income impact review |
| SDG 2 — Zero Hunger | Diverse organic food production across short, medium, long, and continuous cycles | Harvest records, crop cycle data, egg records, distribution records |
| SDG 5 — Gender Equality | Women-led ownership, management, decision-making, and community programming | Governance records, operator records, program records, leadership documentation |
| SDG 8 — Decent Work | Seven documented jobs, training programs, and regenerative agriculture skill-building | Employment records, workshop attendance, role descriptions, training logs |
| SDG 15 — Life on Land | Biodiversity nursery, biochar, syntropic plots, erosion control, vegetation monitoring | Species inventory, nursery logs, satellite indices, soil observations, MRV reports |
This page focuses on Adelphi's five primary SDGs. SDG 13 — Climate Action is treated as an important co-benefit through biochar, agroforestry, soil regeneration, and vegetation monitoring, but not as a primary SDG until the carbon methodology is fully operationalized and reported consistently.
***
## How SDG evidence flows
```mermaid theme={null}
flowchart TD
A["Farm activity"] --> B["Structured field record"]
B --> C["Kokonut Hub"]
B --> D["MRV payload"]
D --> E["IPFS / Filecoin record"]
E --> F["Farm Registry event"]
F --> G["EAS attestation"]
C --> H["Annual SDG report"]
G --> H
H --> I["DAO members, grant reviewers, researchers, communities"]
```
SDG alignment is only useful when it can be verified. For Adelphi, that means each outcome should connect to one or more evidence sources: farm logs, harvest records, employment records, workshop attendance, nursery inventory, satellite vegetation indices, public Data Hub entries, and annual reports.
[Read the full MRV methodology →](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification)
***
## SDG 1 — No Poverty
> Eradicate extreme poverty for all people everywhere and ensure all people have equal rights to economic resources.
Adelphi contributes to poverty reduction by creating local employment, generating farm revenue, building community infrastructure, and allocating part of that revenue to public goods.
| Indicator | Current figure or method | Evidence source |
| ----------------------------------- | --------------------------------------- | -------------------------------------------------------------------------------------------- |
| Jobs supported | 7 full-time positions | Kokonut Hub, farm employment records |
| Projected gross annual crop revenue | \~\$149,110/yr forecast, before actuals | [Crops & Harvest Forecast](/ecosystem-wiki/kokonut-farms/adelphi/crops-and-harvest-forecast) |
| Public goods allocation | 10% of farm revenue | Common Data Schema, revenue records |
| Revenue streams | Lettuce, passion fruit, coconut, eggs | Harvest records, sales records |
### What this means
Poverty reduction at Adelphi is not treated as charity. It comes from productive assets, recurring work, local food production, and revenue that can circulate back into the community.
### How it is measured
* Employment records and role descriptions
* Monthly sales and revenue tracking
* Public goods allocation records
* Annual household income impact assessment
* Kokonut Hub farm updates and reporting cycles
### SDG interconnections
* Reinforced by **SDG 8** because decent work is a direct income mechanism
* Reinforced by **SDG 2** because local food production reduces household food pressure
* Reinforced by **SDG 5** because women-led ownership strengthens household and community resilience
***
## SDG 2 — Zero Hunger
> End hunger, achieve food security and improved nutrition, and promote sustainable agriculture.
Adelphi contributes to food security through diversified organic production. The farm is designed around multiple crop timelines, so the system does not depend on a single harvest, market, or species.
| Production stream | Annual production model | Cycle |
| --------------------------------- | ----------------------------------------------------------------- | ------------ |
| Lettuce plus companion vegetables | 48,450 units per harvest × 5 harvests = 242,250 units/yr forecast | Short cycle |
| Passion fruit | 47,600 fruits · 3,661 nets/yr forecast | Medium cycle |
| Coconut | 6,144 coconuts/yr forecast | Long cycle |
| Indian yam | Additional medium-cycle food crop | Medium cycle |
| Free-range eggs | \~36,500 eggs/yr at 100/day | Continuous |
### What this means
Adelphi's contribution to food security is both local and systemic. Local communities gain access to fresh food, while the farm demonstrates how regenerative production can support revenue without relying on monoculture.
### How it is measured
* Harvest records per crop and cycle
* Crop loss-rate tracking
* Egg production logs
* Distribution channel records
* Organic certification milestones
* Community food access surveys
### SDG interconnections
* Supported by **SDG 15** because healthy soil is the foundation of food production
* Reinforces **SDG 1** because food access and income reduce household vulnerability
* Reinforces **SDG 8** because producing food creates farm employment and training needs
***
## SDG 5 — Gender Equality
> Achieve gender equality and empower all women and girls.
Adelphi is founded and operated by sisters Yanny and Neury Hernández. The project demonstrates women-led agricultural ownership, decision-making, production management, financial stewardship, and community programming.
| Dimension | Evidence |
| ---------------------- | ------------------------------------------------------------------------------- |
| Ownership | Land and project co-owned by Yanny and Neury Hernández |
| Operational leadership | Founders manage daily farm direction and project priorities |
| Financial management | Revenue, costs, and community allocation decisions are managed by the operators |
| Community programs | Founders design and host educational and community activities |
| Governance | Farm operator records connect the project to the Kokonut governance layer |
### What this means
Gender equality at Adelphi is not only about representation. It is control over land, operations, income, infrastructure, and community-facing education.
### How it is measured
* Operator records
* Governance and farm registration records
* Community program logs
* Women's participation in training programs
* Annual SDG 5 attestation or reporting entry
### SDG interconnections
* Reinforces **SDG 1** through women's economic independence
* Reinforces **SDG 8** through women-led job creation and inclusive hiring
* Reinforces Kokonut's broader governance principle: people who create value should have pathways to economic participation and standing
***
## SDG 8 — Decent Work and Economic Growth
> Promote sustained, inclusive and sustainable economic growth, full and productive employment, and decent work for all.
Adelphi supports seven documented jobs and builds practical skills in agro-ecological production, poultry management, nursery operations, biochar production, MRV data collection, and community education.
| Indicator | Current figure or status |
| --------------------- | --------------------------------------------------------------- |
| Full-time positions | 7 |
| Employment focus | Local rural community, with deliberate emphasis on women |
| Training programs | Workshops and practical education at the on-site gazebo |
| Organic certification | In progress with the Dominican Republic Ministry of Agriculture |
| Market access goal | Organic markets, local supermarkets, direct community sales |
### Work categories at Adelphi
* Crop management across short, medium, and long-cycle beds
* Poultry management, daily egg collection, and manure processing
* Nursery propagation and native species tracking
* Biochar production and soil amendment workflows
* Community education and workshop support
* Field logging, farm records, and MRV data collection
### How it is measured
* Employment records updated quarterly
* Workshop attendance and skills-training logs
* Organic certification status updates
* Farm role documentation
* Revenue and market-access records
### SDG interconnections
* Reinforces **SDG 1** because employment income is the main poverty-reduction mechanism
* Reinforced by **SDG 5** because women-led operations shape who gets access to opportunity
* Supported by **SDG 15** because regenerative agriculture can create skilled work around land restoration rather than extraction
***
## SDG 15 — Life on Land
> Protect, restore and promote sustainable use of terrestrial ecosystems, sustainably manage forests, combat desertification, halt and reverse land degradation, and halt biodiversity loss.
Adelphi contributes to SDG 15 through agro-biodiversity, soil regeneration, organic input production, endangered species propagation, erosion control, syntropic plots, and vegetation monitoring.
| Practice | Detail | Evidence source |
| ------------------------- | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| At-risk species nursery | 12+ native or at-risk species propagated and distributed to neighbors | [Crops, Biodiversity & Infrastructure](/ecosystem-wiki/kokonut-farms/adelphi/crops-biodiversity-and-infrastructure) |
| Biochar soil regeneration | Bamboo-derived biochar is produced and applied on-site | Infrastructure records, soil observations |
| Syntropic farming plots | 2 dedicated plots implementing multi-strata syntropic design | Farm layout, field observations |
| Erosion control | Beard grass ground cover along terraced edges | Field records, farm photos, MRV updates |
| Per-plant tracking | Species registered through geospatial records | Silvi/GPS records, species data |
| Vegetation monitoring | NDVI, NDRE, MSAVI, and other remote-sensing indicators | MRV stack, satellite records |
### Species in the at-risk nursery
Partial list: Hispaniola palmetto · Native cacao · Guavaberry · Congo coffee tree · Jagua · Naseberry · Star Apple · Mammee Apple · Custard Apple · Cashew · Soursop · Lipsticktree.
Full catalog: [AdelphiSpeciesGeoNode](https://link.kokonut.network/AdelphiSpeciesGeoNode)
### How it is measured
* Nursery species count and propagation records
* Plant distribution logs
* Soil observations and organic input records
* Satellite vegetation indices
* Biodiversity surveys
* Annual EBF and SDG reporting
### SDG interconnections
* Enables **SDG 2** because soil health supports food production
* Supports **SDG 1** because local plant distribution and soil fertility strengthen community resilience
* Contributes to **SDG 13** as a co-benefit through soil carbon, agroforestry, vegetation cover, and biochar
***
## How the five SDGs reinforce each other
The five SDGs at Adelphi are not independent commitments. They form a self-reinforcing system.
```mermaid theme={null}
flowchart LR
S15["SDG 15\nHealthy soil + biodiversity"]
S2["SDG 2\nFood production capacity"]
S8["SDG 8\nDecent work"]
S5["SDG 5\nWomen's leadership"]
S1["SDG 1\nIncome + food security"]
S15 -->|regenerates land| S2
S2 -->|improves local food supply| S1
S2 -->|creates farm activity| S8
S8 -->|raises household income| S1
S5 -->|increases inclusive participation| S8
S5 -->|strengthens household resilience| S1
S15 -->|creates restoration work| S8
```
Healthy land enables diverse food production. Food production creates work. Work increases household income. Women-led ownership strengthens resilience and inclusion. The result is not five separate claims, but one integrated farm system.
***
## Annual SDG reporting
Adelphi's SDG reporting should be updated annually through the Kokonut Framework and the EBF impact lens.
| Reporting dimension | SDGs covered | Key metrics reported |
| ------------------- | --------------------------------- | -------------------------------------------------------------------------------------------- |
| Environmental | SDG 15, SDG 2, SDG 13 co-benefits | Vegetation indices, biodiversity index changes, nursery species count, and soil observations |
| Economic | SDG 1, SDG 8 | Gross revenue, public goods allocation, jobs sustained, and household income changes |
| Social | SDG 5, SDG 8, SDG 1 | Women in leadership, training participants, and community programs held |
| Sustainability | All five | Organic certification status, SDG attestation count, 8 Forms of Capital review |
Reports should be published on the [Kokonut Hub](https://hub.kokonut.network/projects/41), anchored through EAS where applicable, and linked back to the relevant farm pages, so that every SDG claim has a clear evidence path.
Forecasts are planning assumptions, not guaranteed outcomes. SDG 1, 2, and 8 claims should be updated as actual harvest, revenue, employment, and distribution records are added to the Data Hub.
***
## What this page proves
Jobs, crops, poultry, nursery work, soil practices, training programs, and governance records are the source of the claims.
The MRV stack, Kokonut Hub, field logs, and annual reports create an evidence path for DAO members, grant reviewers, partners, and communities.
Soil regeneration supports food production; food production creates work; work reduces poverty; women-led ownership strengthens the whole system.
Adelphi's SDG evidence becomes a template other Kokonut farms can adapt, report against, and improve over time.
***
## Next steps
The measurement and verification stack that turns farm activity into public evidence, Data Hub records, and attestations.
The forecast behind SDG 1, SDG 2, and SDG 8: crop cycles, production assumptions, revenue, and public goods allocation.
The physical evidence behind SDG 15: nursery, biochar, syntropic plots, poultry system, training gazebo, and farm infrastructure.
The human story behind SDG 5: Yanny and Neury Hernández, women-led land stewardship, and community-first agriculture.
The broader Kokonut Framework method for mapping SDGs, 8 Forms of Capital, EBF, and ecosystem impact across all farms.
Help improve the SDG evidence model as an agronomist, researcher, MRV contributor, developer, DAO member, or impact reviewer.
# Measurement, Reporting & Verification
Source: https://kokonut.network/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification
How Kokonut turns farm activity into public, verifiable evidence: soil probes, satellite indices, community field logs, Farm Registry payloads, IPFS records, EAS attestations, and annual impact reports.
# Impact claims without evidence are marketing.
Measurement, Reporting, and Verification (**MRV**) is the trust layer of the Kokonut Framework. It is how a farm activity becomes evidence, how evidence becomes a public record, and how public records become useful for DAO members, grant reviewers, developers, researchers, capital allocators, and AI agents.
At Kokonut, MRV is not a PDF produced after the fact. It is a live data pipeline:
> **Farm activity → structured payload → IPFS record → Farm Registry event → EAS attestation → public Data Hub → annual impact report.**
At [Adelphi](/ecosystem-wiki/kokonut-farms/adelphi/summary), this pipeline is already active. Farm data flows to [hub.kokonut.network/projects/41](https://hub.kokonut.network/projects/41), where harvest records, MRV events, and impact metrics can be inspected by anyone.
Built for farm operators, DAO members, grant reviewers, data scientists, Impact Guild contributors, and agent builders.
***
## MRV at a glance
Soil probes, satellite imagery, drone surveys, and field observations capture what is happening on the farm.
Measurements are converted into structured Farm Registry payloads with timestamps, farm IDs, measurement types, and source-specific data.
Payloads are pinned to IPFS/Filecoin and anchored through EAS attestations, creating public records that Kokonut cannot retroactively alter.
Verified data powers farm management, DAO funding decisions, annual EBF reports, CRISP risk scoring, AI agents, and public impact dashboards.
MRV is valuable because it serves both the farm and the network. Operators get better irrigation, nutrient, and harvest decisions. DAO members and partners get verifiable evidence instead of self-reported claims.
***
## What MRV proves
MRV answers five trust questions every regenerative farm eventually faces:
| **Question** | **MRV evidence** | **Who needs it** |
| ---------------------------- | --------------------------------------------------------------------------------------- | --------------------------------------------------- |
| Is the farm real and active? | Farm registry record, geospatial data, field logs, harvest records | DAO members, funders, partners |
| Is the land improving? | NDVI, NDRE, ReCI, MSAVI, soil moisture, soil temperature, electrical conductivity | Impact Guild, agronomists, researchers |
| Are harvest claims credible? | Crop cycle logs, harvest milestones, production forecasts, Data Hub records | DAO members, buyers, operators |
| Is impact verifiable? | IPFS payloads, EAS attestations, annual EBF reports, CRISP risk assessments | Grant reviewers, institutions, public goods funders |
| Can the model scale? | Standardized payloads, API endpoints, agent-readable data, reusable reporting workflows | Developers, AI agents, new farms |
***
## How MRV works
```mermaid theme={null}
flowchart TD
A["Farm event\nsoil · satellite · drone · harvest · field log"] --> B["Structured MRV payload\nFarm Registry schema"]
B --> C["Pinned to IPFS / Filecoin\ncontent-addressed evidence"]
C --> D["Submitted to Farm Registry API\nMRV event created"]
D --> E["EAS attestation\nsigned + anchored on-chain"]
E --> F["Public Data Hub\nqueryable farm record"]
F --> G["Annual reports\nEBF impact + CRISP risk"]
F --> H["AI agents\nforecasting · monitoring · impact scoring"]
G --> I["DAO and partner decisions\nfunding · replication · accountability"]
H --> I
```
The pipeline is designed so that each layer adds a different kind of trust:
1. **Sensor and field data** capture the event.
2. **Structured payloads** make the event machine-readable.
3. **IPFS/Filecoin CIDs** make the evidence content-addressed.
4. **Farm Registry events** make the data queryable.
5. **EAS attestations** make the record tamper-resistant.
6. **The Data Hub** makes the result public.
7. **Annual reports** turn raw data into ecological, economic, social, and sustainability insights.
***
## The three-tier monitoring stack
Kokonut's MRV methodology operates across three complementary sensing tiers. Each tier captures what the others cannot.
Ground sensing measures what is happening below and around the crop.
**Soil moisture probes** provide continuous subsurface readings across three core variables:
* **Volumetric Water Content (VWC):** Measures how much water is present in the soil relative to total soil volume, helping operators detect irrigation needs before stress is visible above ground.
* **Electrical Conductivity (EC):** Measures the soil's ability to conduct electricity, acting as a proxy for salinity and nutrient availability.
* **Soil Temperature:** Tracks root-zone temperature, which affects germination, microbial activity, nutrient cycling, and plant growth.
These readings feed into the `ground` field of each `KokonutMRVPayload`.
Remote sensing monitors vegetation health across the farm landscape.
Kokonut uses **Landsat 8**, **Sentinel**, and drone imagery to calculate vegetation indices. Each index is used for a different monitoring condition:
| **Index** | **Formula** | **Best use** |
| --------- | ----------------------------------------------------------------- | -------------------------------------------------------------- |
| **NDVI** | `(NIR − RED) / (NIR + RED)` | Baseline vegetation health after canopy is established |
| **ReCI** | `(NIR / RED) − 1` | Chlorophyll and nitrogen proxy during active vegetative growth |
| **NDRE** | `(NIR − RED_EDGE) / (NIR + RED_EDGE)` | Mature or dense canopies where NDVI saturates |
| **MSAVI** | `(2 × Band4 + 1 − √((2 × Band4 + 1)² − 8 × (Band4 − Band3))) / 2` | Early growth stages with high bare-soil exposure |
Index selection matters. Applying the wrong index at the wrong crop stage can produce misleading readings.
Community analytics capture agronomic judgment that sensors cannot fully encode.
Farm operators and community members log observations such as:
* **Crop cycle stage:** `germination` → `seedling` → `vegetative` → `flowering` → `fruiting` → `harvest` → `post_harvest`
* **Plant health notes:** vigor, color, uniformity, pests, disease, stress indicators
* **Water analysis:** pH, turbidity, contamination signals, source conditions
* **Soil texture:** tactile field assessment of structure, drainage, and organic matter
* **Disease flags:** timestamped pest or disease observations for trend analysis
These logs provide local context that cannot be captured by satellites alone.
***
## Tools used at Adelphi
| **Tool** | **Purpose** | **Data output** |
| ----------------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| [Silvi](https://www.silvi.earth/) | Per-plant GPS tracking and health logs | Plant-level location and phenology records |
| [Atlantis App](https://apps.apple.com/in/app/impact-miner/id6448894610) | Field data collection, project management, and third-party attestations | Structured reports with photos, timestamps, and attestation-ready evidence |
| QGIS | Vegetation index calculation from drone orthomosaics | Raster analysis and NDVI/NDRE/MSAVI grid outputs |
| [Pix4Dcapture](https://www.pix4d.com/product/pix4dcapture) | Drone flight planning and orthomosaic generation | Georeferenced imagery for the QGIS pipeline |
| Landsat 8 + Sentinel | Landscape-scale remote sensing | Vegetation trends, crop health signals, and periodic monitoring snapshots |
***
## The MRV payload
Each farm operating under the Kokonut Framework reports against a common payload structure. This lets tools, dashboards, AI agents, and annual reports all read from the same source of truth.
```typescript theme={null}
interface KokonutMRVPayload {
farm_id: string; // Farm registry identifier
timestamp: string; // ISO 8601
measurement_type: "ground" | "remote" | "community";
// Ground sensing
ground?: {
volumetric_water_content: number; // % — moisture in soil volume
electrical_conductivity: number; // dS/m — salinity / nutrient proxy
soil_temperature: number; // °C
};
// Remote sensing
remote?: {
ndvi: number; // general vegetation health
reci: number; // chlorophyll / nitrogen proxy
ndre: number; // dense or mature canopy monitoring
msavi: number; // early season / bare soil adjustment
source: "landsat_8" | "sentinel" | "drone";
image_url?: string; // IPFS CID or signed URL
};
// Community analytics
community?: {
crop_cycle_stage: string;
plant_health_notes: string;
water_analysis: string;
soil_texture: string;
disease_flags: string[];
};
// Attestation
attested_by?: string; // EAS attestation UID
attestor_address?: string; // Wallet that signed the attestation
}
```
***
## From measurement to verification
Soil probes, satellite images, drone imagery, harvest records, and community field logs are assembled into a structured MRV payload.
The full evidence package is pinned to IPFS/Filecoin. The returned CID is content-addressed: the same data always produces the same identifier, and different data cannot produce that same record.
The payload is submitted to `POST /farms/{farm_id}/mrv`. The API returns a `mrv_id` and records the event before attestation.
The attestation encodes fields such as `farm_id`, `event_type`, `ipfs_cid`, `impact_score`, `attestor_role`, and `timestamp`. The record is signed by the attestor wallet and anchored on-chain.
Once attested, the MRV event appears in the farm's public record at [hub.kokonut.network/projects/41](https://hub.kokonut.network/projects/41), traceable to the original evidence package and on-chain attestation.
The purpose of on-chain verification is not hype. It prevents retroactive editing of the impact record and gives funders, DAO members, researchers, and communities a shared source of truth.
***
## What gets reported annually
MRV events aggregate into annual impact reporting across four dimensions aligned with the Ecological Benefits Framework and the Kokonut 8 Forms of Capital.
| **Dimension** | **What is measured** | **Example metrics** |
| ------------------ | -------------------------------------------------- | -------------------------------------------------------------------------------------- |
| **Environmental** | Ecological health and carbon performance | Carbon sequestration rates, NDVI averages, biodiversity index changes, MRV event count |
| **Economic** | Farmer and community financial impact | Gross revenue, public goods allocation, jobs created, household income changes |
| **Social** | Community wellbeing and capacity | Workshops, participants trained, women in leadership roles, educational program reach |
| **Sustainability** | Long-term resilience across all 8 forms of capital | Annual sustainability audit, organic certification status, SDG attestations |
Annual reports for [Adelphi](/ecosystem-wiki/kokonut-farms/adelphi/summary) are published through the public Data Hub. Historical MRV records, harvest forecasts, and aggregated impact metrics should remain traceable to their underlying EAS attestations.
***
## EBF and CRISP: the interpretation layer
Raw MRV data is the evidence. EBF and CRISP help interpret what that evidence means.
EBF asks: what ecological and community benefits did this farm produce, and how should they be reported across environmental, economic, social, and sustainability dimensions?
CRISP asks: how likely is the farm to deliver the carbon and ecological outcomes it claims, given operational, climate, policy, financial, and developer risks?
Together, they turn continuous farm-level MRV into an auditable impact profile that DAO members, public goods funders, grant reviewers, and institutional partners can use.
***
## How AI agents use MRV
Farms generate more data than human operators can process manually. Satellite passes can happen every few days. Soil probes can read hourly. Crop cycles produce repeated harvest records. Each event creates work: ingest, calculate, validate, attest, report, and sometimes trigger a DAO or marketplace action.
The [Kokonut × AI Agents](/kokonut-x-ai-agents) architecture is designed to automate the slowest parts of this workflow:
Ingests satellite or drone data, calculates vegetation indices, and submits MRV payloads to the Farm Registry.
Converts harvest logs into structured records, links them to crop cycles, and prepares attestable outputs.
Reads verified MRV and harvest records, calculates impact scores, and supports EBF and CRISP reporting.
The Kokonut Agentic Marketplace is in active development. The current MRV page should distinguish between the live MRV methodology at Adelphi and the automation layer being built to increase reporting frequency and reduce manual bottlenecks.
***
## Why this matters for each reader
MRV improves decisions around irrigation, nutrients, crop stress, harvest timing, and long-term soil management.
MRV provides evidence for funding proposals, treasury decisions, risk assessment, and replication decisions.
MRV replaces subjective impact claims with timestamped records, public dashboards, and third-party-verifiable evidence.
MRV provides a standard schema, API surface, attestation format, and data layer for tools, dashboards, and AI agents.
MRV creates clear work: validate field reports, review evidence packages, improve data standards, and produce annual impact reporting.
MRV makes local work visible, making it easier for communities to prove what they grow, restore, teach, and sustain.
***
## Known improvement areas
MRV should be credible about what is live, what is planned, and what still needs contribution.
| **Area** | **Current direction** | **Contribution opportunity** |
| ---------------- | --------------------------------------------------- | ---------------------------------------------------------- |
| Data schemas | Farm Registry and MRV payloads are documented | Improve compatibility, validation, and versioning |
| Attestations | EAS-compatible farm events are part of the pipeline | Define schemas, roles, review processes, and indexing |
| Dashboards | Adelphi records are published through the Data Hub | Improve public views, filters, charts, and export formats |
| AI automation | Agentic Marketplace architecture is in development | Build MRV, harvest, and impact scoring agents |
| Impact reporting | EBF and CRISP guide annual reports | Refine methodology and evidence requirements |
| Field workflow | Community analytics capture human judgment | Improve operator forms, photo standards, and QA checklists |
***
## Next steps
See live MRV records, harvest data, and impact metrics from Kokonut's first live farm.
Use the Farm Registry schema, MRV payload format, attestation fields, and developer primitives.
Learn how agents automate MRV ingestion, vegetation index calculation, attestations, payments, and impact scoring.
Understand how EBF and CRISP convert raw MRV evidence into annual reports and carbon risk assessments.
See the live reference implementation of the Kokonut Framework, MRV stack, and public data model.
Join the Impact Guild, improve the MRV methodology, help validate data, or build tools for the next farm.
# Open Collaboration Invitation
Source: https://kokonut.network/ecosystem-wiki/open-collaboration-invitation
Choose your path into Kokonut Network: contribute to the Framework, build MRV and AI infrastructure, join a Guild, support Adelphi, or participate in DAO governance.
# Help build the coordination layer for regenerative agriculture.
Kokonut Network is inviting agronomists, researchers, ReFi builders, developers, DAO members, capital allocators, and community organizers to help turn live regenerative farms into a repeatable, community-governed system.
Adelphi proves the model can work at the farm level. The next challenge is replication: more farms, more verified data, more open-source tools, more contributor pathways, and more community-owned agricultural production.
No capital required to begin. Start with a Guild task, a research contribution, an issue, a proposal, or a conversation.
Kokonut uses Web3 coordination because grassroots agriculture needs transparent funding, public data, verifiable impact, and community-governed ownership — not another extractive intermediary.
***
## Why act now?
The problem is urgent, but the opportunity is practical.
* **Climate pressure is rising.** Soil degradation, water scarcity, and biodiversity loss make extractive agriculture more fragile every year.
* **Grassroots farmers are undercapitalized.** Farmers often have land, knowledge, and labor, but lack access to patient capital, governance tools, and verifiable reporting infrastructure.
* **Adelphi is already live.** Our flagship farm in Monte Plata, Dominican Republic, is funded, operating, monitored, and publishing real farm data.
* **The Framework is ready to improve.** Every new farm needs better data schemas, clearer MRV standards, stronger public-goods allocation logic, and more contributors who can make the system easier to replicate.
The invitation is not to believe in a concept. The invitation is to help improve a live system that already touches land, farmers, governance, public data, and community benefit.
PN #69
public goods funded
***
## What we are building together
Kokonut Network is a cooperative coordination stack for regenerative agriculture.
Adelphi is the first live syntropic farm: women-led, community-first, publicly funded, and monitored through satellite, field, harvest, and impact data.
The Kokonut Framework provides every farm with a common data schema, development phases, MRV requirements, public-goods allocation logic, and a governance pathway.
Capital contributors participate through the Moloch DAO. Non-capital contributors participate through Guilds, Guild Points, and potential Loot awards.
Developers can build on public docs, deployed contracts, Farm Registry primitives, MRV data flows, EAS attestations, and the Agentic Marketplace architecture.
The network needs people who can improve each layer: the land layer, the Framework layer, the governance layer, the data layer, and the community layer.
***
## Choose your contribution path
There is no single way to contribute. Choose the path that matches your skills, resources, and level of commitment.
Help improve farm design, crop sequencing, soil regeneration plans, water systems, biochar use, biodiversity restoration, and farmer training materials.
Improve vegetation index methodology, soil and water measurements, SDG mapping, EBF reporting, impact scoring, species-level geodata, and verification standards.
Help design public-goods funding pools, impact-linked tokens, revenue allocation models, farm funding proposals, and incentive systems that keep value circulating locally.
Build Farm Registry tools, EAS attestation schemas, dashboards, AI agents, subgraphs, front-end interfaces, MRV automation, and DAO tooling.
Tribute stablecoins to the Kokonut DAO, receive \$vKKN backed 1:1 by coconut trees, vote on farm funding, and use rage-quit protection if you disagree with the direction.
Support Discord onboarding, educational content, partnership outreach, documentation, events, farm updates, governance recaps, and public narrative work.
***
## How a contribution turns into standing
Kokonut is designed so people can earn influence through verified work, not only through capital.
Join the Discord, review open issues, improve a doc page, propose an MRV method, write a research note, build a tool, support a grant, or help a Guild with a defined task.
Completed work becomes part of your contribution history: shipped code, approved documentation, MRV submissions, authored proposals, peer endorsements, or public ecosystem work.
Recognized contributions can earn non-transferable Guild Points inside the relevant Guild. Points represent reputation and influence; they cannot be bought, sold, delegated, or transferred.
Active contributors can earn Guild standing, help shape domain-specific decisions, route proposals to the DAO, and become eligible for Loot token awards for significant work.
Capital is one path into Kokonut, not the only path. Contributors without capital can earn reputation, influence, and economic participation through verified work.
***
## The Guilds
Kokonut Guilds are the operational intelligence of the network. Each Guild owns a domain of work and helps route contributions into the DAO's broader governance process.
| Guild | Domain | Examples of useful contributions |
| ---------------------------------- | ------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------- |
| **Technology Guild** | Smart contracts, data tooling, front-end interfaces, AI agents, APIs, indexers | Farm Registry tooling, EAS schemas, dashboards, subgraphs, automation, contract integrations |
| **Impact Guild** | MRV, EBF impact reporting, SDG alignment, ecological validation | Satellite methodology, soil metrics, biodiversity data, impact reports, attestation workflows |
| **Communications Guild** | Public narrative, education, documentation, community growth | Docs improvements, explainers, onboarding flows, governance newsletters, ecosystem updates |
| **Governance Guild** | Proposal quality, DAO process, dispute resolution, contributor onboarding | Proposal templates, governance guides, vote summaries, policy updates, onboarding materials |
| **Finance Guild** | Treasury reporting, farm models, grant budgets, stablecoin strategy | Farm forecasts, budget proposals, grant financials, treasury reports, partner diligence |
| **Community & Partnerships Guild** | Farmer onboarding, partnerships, local coordination, ReFi relationships | Farmer partnership templates, ecosystem partnerships, community events, collaboration pipelines |
[Explore Kokonut Guilds →](/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao)
***
## What needs help right now
Kokonut is especially looking for contributors who can help with:
Improve the Common Data Schema, farm development phases, public-goods allocation model, impact reporting sections, and replication playbooks.
Help standardize satellite, drone, soil, field, harvest, and biodiversity data so farm progress can be publicly verified.
Build agents that support MRV ingestion, vegetation-index calculations, Farm Registry submissions, harvest forecasting, grant writing, and impact scoring.
Improve proposal templates, bounty flows, contribution review, Guild coordination, governance summaries, and new member onboarding.
Turn live farm progress into clear public records: photos, harvest updates, infrastructure milestones, MRV notes, and community impact stories.
Help identify future farms, public-goods funders, ReFi partners, local institutions, research collaborators, and ecosystem allies.
***
## Why your contribution matters
Kokonut is building a system in which the next farm does not have to start from scratch.
Each useful contribution makes the network easier to trust, fund, operate, verify, and replicate:
* Better documentation helps new contributors join faster.
* Better MRV standards make it easier to verify impact.
* Better software reduces manual reporting bottlenecks.
* Better governance templates make DAO decisions easier to review.
* Better financial models make farm proposals easier to fund.
* Better partnerships help more communities access the Framework.
> **The goal is not to build one beautiful farm. The goal is to build the repeatable coordination layer that lets many regenerative farms become fundable, governable, and verifiable.**
***
## Start here
Introduce yourself, share your skills, and tell the community which contribution path you are most interested in. [Join Discord →](https://link.kokonut.network/discord)
Start with [Adelphi Farm](/ecosystem-wiki/kokonut-farms/adelphi/summary) and inspect the live project data at [hub.kokonut.network/projects/41](https://hub.kokonut.network/projects/41).
Review the [Kokonut Guilds](/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao) and choose the domain where your skills can create the most value.
Improve a doc page, open an issue, propose a method, ship a tool, write an analysis, support a proposal, or help document Adelphi's progress.
If you represent a funder, DAO, protocol, farm, institution, or serious partnership opportunity, [book a meeting](https://link.kokonut.network/meeting) for a DAO and farm walkthrough.
Together, we can turn regenerative agriculture into a public, verifiable, community-owned system — one farm, one contribution, one proposal, and one verified record at a time.
# DAO Architecture
Source: https://kokonut.network/ecosystem-wiki/the-kokonut-dao/dao-layers
How Kokonut separates capital, contribution, execution, production, and verification into a resilient community-governed cooperative.
# Kokonut is not one DAO. It is a layered cooperative architecture.
The Kokonut DAO is designed to coordinate two things that usually conflict: **capital protection** and **contribution-based participation**.
Capital contributors need treasury transparency, enforceable governance rights, and a clean exit if they disagree with the DAO. Contributors without capital need a way to earn influence through useful work. Farmers need funding, execution support, and verification infrastructure. The DAO architecture separates those needs into layers so that no single mechanism has to solve every coordination problem at once.
Capital path: stablecoin tribute → \$vKKN. Contribution path: verified work → Guild Points → potential Loot.
The Kokonut DAO stack separates governance, smart contract logic, execution, farm production, and verification infrastructure.
***
## Architecture at a glance
| Layer | Primary actors | What it governs | Main mechanism |
| -------------- | -------------------------------------------- | ------------------------------------------------------------------- | ------------------------------------------- |
| Governance | \$vKKN holders | Network-level decisions, treasury direction, member votes | 1 \$vKKN = 1 vote through DAOHaus |
| Logic | Smart contracts, treasury, tokens | Proposal execution, token minting/burning, rage-quit, fund movement | Verified contracts on Gnosis Chain |
| Execution | Guilds, contributors, Core Team, partners | Work coordination, bounties, deliverables, and farm deployment | Contribution-weighted Guild work |
| Production | Farmers, operators, and local communities | Farm operations, harvests, ecological work, community programs | Kokonut Framework and farm-level operations |
| Infrastructure | MRV stack, Farm Registry API, EAS, AI agents | Data flows, attestations, indexing, verification | Structured MRV and on-chain evidence |
The architecture is designed to avoid a single point of failure. Capital governance, operational expertise, farm production, and verification are connected — but not collapsed into one voting mechanism.
***
## Why the DAO is layered
A regenerative agriculture network has to coordinate many kinds of value:
* stablecoin capital entering the treasury;
* farm proposals and infrastructure budgets;
* contributor work across technology, impact, finance, governance, communications, and partnerships;
* harvest records, MRV data, and impact attestations;
* farmers and local communities producing value on the land;
* DAO members who need enforceable rights and protection.
A single token-weighted DAO would overrepresent capital and underrepresent the people doing the operational work. A purely contribution-weighted DAO would struggle to protect capital contributors and treasury exits.
Kokonut uses both.
Stablecoin contributors receive soulbound governance tokens, vote on treasury decisions, and can rage-quit with their proportional treasury share.
Builders, researchers, organizers, and operators earn Guild Points through verified work and can become eligible for Loot without contributing capital.
***
## The five-layer stack
The five layers describe how value, authority, and information move through the network — from token holders and contracts to contributors, farms, and public evidence.
**Who:** Kokonut DAO token holders with at least one \$vKKN governance token.
**What it does:** Votes on proposals that benefit the Kokonut ecosystem: farm funding, governance parameter changes, Guild bounty approvals, partnership ratifications, and token minting or burning.
**How it works:** 1 \$vKKN = 1 vote through [DAOHaus](https://link.kokonut.network/dao). Proposals move through the governance process, and the DAO retains final authority over treasury-level decisions.
**Who:** The smart contracts and data structures that encode the DAO's rules.
**What it does:** Holds the treasury, membership records, token contracts, proposal execution logic, and rage-quit mechanics.
**How it works:** Verified contracts on Gnosis Chain manage the \$vKKN voting token, Loot token, Vault Manager, and rage-quit-enabled SAFE treasury. No individual can move funds, mint tokens, or change parameters without a passed proposal.
**Who:** Kokonut Guilds, Core Team members, contributors, farm partners, and local or global collaborators.
**What it does:** Turns approved proposals into completed work: farm deployment, MRV reporting, software builds, documentation, governance operations, partnerships, and community programs.
**How it works:** Six Guilds coordinate domain-specific work using contribution-weighted Guild Points instead of token-weighted voting.
**Who:** Farmers, farm operators, and communities running Kokonut Network farms.
**What it does:** Produces food, coconuts, eggs, biodiversity, soil regeneration, jobs, training, and local community value.
**How it works:** Farms operate under the [Kokonut Framework](/kokonut-framework/Introduction). [Adelphi](/ecosystem-wiki/kokonut-farms/adelphi/summary) is the first operational farm: 15,725 m² in Monte Plata, Dominican Republic, with live farm data published through the Kokonut Hub.
**Who:** MRV systems, Farm Registry API, EAS attestations, indexers, and AI agents.
**What it does:** Turns farm activity into structured records that DAO members, contributors, funders, and communities can inspect.
**How it works:** Farm events, harvest records, and impact data move through the MRV pipeline into public records. The Agentic Marketplace is the emerging automation layer for scaling this work across more farms.
***
## How the layers flow together
```mermaid theme={null}
flowchart TD
A["Governance Layer\n$vKKN holders vote"] --> B["Logic Layer\ncontracts execute proposals"]
B --> C["Execution Layer\nGuilds and partners do the work"]
C --> D["Production Layer\nfarms produce food, data, and impact"]
D --> E["Infrastructure Layer\nMRV, EAS, APIs, indexers, agents"]
E --> B
E --> A
A -->|"capital direction"| B
B -->|"funding + mandates"| C
C -->|"implementation"| D
D -->|"field records"| E
E -->|"evidence for execution"| B
E -->|"evidence for governance"| A
style A fill:#ede9fe,stroke:#8b5cf6,color:#4c1d95
style B fill:#dbeafe,stroke:#3b82f6,color:#1e40af
style C fill:#fef3c7,stroke:#f59e0b,color:#92400e
style D fill:#d1fae5,stroke:#10b981,color:#065f46
style E fill:#e0f2fe,stroke:#0284c7,color:#075985
```
Capital and governance decisions move downward. Farm work and verification data move upward. The Infrastructure Layer makes the loop legible: it provides the Governance and Logic Layers with evidence rather than forcing members to trust claims.
***
## Two governance instances, two entry paths
Kokonut uses two complementary governance systems because capital and contributions require different protections.
| | Kokonut Moloch DAO | Kokonut Guilds DAO |
| ----------------- | -------------------------------------------------------- | ------------------------------------------------------------ |
| Primary role | Treasury governance and capital allocation | Operational execution and contribution tracking |
| Membership basis | Token-weighted | Contribution-weighted |
| Entry path | Tribute stablecoins → proposal → \$vKKN minted | Complete useful work → earn Guild Points |
| Capital required | Yes | No |
| Main rights | Vote on treasury proposals; sponsor proposals; rage-quit | Influence Guild decisions; coordinate work; earn reputation |
| Exit/risk profile | Rage-quit returns proportional treasury share | No locked capital; points are reputation |
| Best for | DAO members, funders, capital allocators | Builders, researchers, agronomists, organizers, contributors |
| On-chain maturity | Live on Gnosis Chain | Reputation tracking in development |
The split is intentional: Moloch protects treasury contributors, while Guilds prevent capital from becoming the only path to influence.
***
## What each path gives you
### Capital path: Kokonut Moloch DAO
The Kokonut Moloch DAO is the live capital and governance engine of the network. It holds the treasury, governs farm funding, mints membership tokens, and protects members through rage-quit.
| Feature | What it means |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| Stablecoin tribute | Members enter by contributing stablecoins to the treasury through a proposal process. |
| \$vKKN voting token | Soulbound governance token. 1 \$vKKN = 1 vote. Each token is backed 1:1 by a real coconut tree in a Kokonut Network farm. |
| Treasury voting | Members vote on farm funding, partnerships, Guild bounties, token minting, and governance changes. |
| Rage-quit | Members can exit with their proportional treasury share, including during grace periods before disliked proposals execute. |
| No admin override | Funds, tokens, and governance parameters cannot be moved or changed by the Core Team alone. |
[Read the Kokonut Moloch DAO page →](/ecosystem-wiki/the-kokonut-dao/kokonut-moloch-dao)
### Contribution path: Kokonut Guilds DAO
The Kokonut Guilds DAO is the operational layer of the network. It gives contributors a path to influence and economic recognition through verified work rather than stablecoin tribute.
| Guild path | What it means |
| --------------------- | -------------------------------------------------------------------------------------------------------------------- |
| Contribute | Complete an open task, bounty, report, MRV submission, proposal, technical contribution, or partnership deliverable. |
| Earn Guild Points | Completed work becomes a non-transferable reputation scoped to the relevant Guild. |
| Gain standing | Contributors can become members or stewards inside a Guild after reaching the required contribution threshold. |
| Route work to Moloch | Guilds can propose budgets, bounties, standards, and deliverables to the Moloch DAO for treasury-level approval. |
| Earn Loot eligibility | Significant contributions can be recognized through Loot token awards via the Moloch DAO proposal. |
[Read the Kokonut Guilds DAO page →](/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao)
***
## Why this architecture matters
Capital contributors get governance rights, treasury transparency, and rage-quit protection. But contributors can still earn influence through Guild work.
Useful work — MRV, documentation, agronomy, software, community coordination, governance support — can generate Guild Points and potential Loot.
Production does not sit outside the DAO. Farm outputs, harvest records, and MRV evidence flow back into the decision-making layer.
The DAO can add more farms, contributors, agents, and Guilds without forcing every operational decision to go through a single token vote.
***
## What is live vs. what is developing
| Component | Status | Notes |
| ------------------------ | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------- |
| Kokonut Moloch DAO | Live | Deployed on Gnosis Chain with verified contracts, stablecoin treasury, \$vKKN, Loot, and rage-quit mechanics. |
| Adelphi Production Layer | Live | First operational farm in Monte Plata, Dominican Republic, with live Data Hub records. |
| Kokonut Framework | Live and evolving | Common Data Schema, farm phases, MRV methodology, and impact framework are documented publicly. |
| Guilds | Operational design / active contribution pathway | Contribution-weighted coordination layer; on-chain reputation tracking is still developing. |
| Agentic Marketplace | In development | Intended to automate MRV ingestion, data validation, Farm Registry submissions, and EAS attestations. |
This page explains the architecture and participation paths. It is not financial advice, an investment offer, or a guarantee of returns. Verify live contracts, treasury state, proposal terms, and current membership parameters before contributing capital.
***
## Choose your entry path
Learn how stablecoin tribute, \$vKKN, voting, rage-quit, and DAO membership work.
Learn how Guild Points, contribution records, Guild membership, stewardship, and Loot eligibility work.
Read the proposal process: drafting, voting, grace period, execution, and governance review.
Review token contracts, Vault Manager, SAFE treasury, Gnosis Chain deployment, and voting power distribution.
Explore the Farm Registry API, EAS schema, data primitives, and agent-ready infrastructure.
See Adelphi, the first operational farm that makes the DAO architecture tangible on real land.
# Governance Framework
Source: https://kokonut.network/ecosystem-wiki/the-kokonut-dao/governance-framework
The operating rules for Kokonut decision-making: who can propose, who can vote, how proposals move from draft to execution, and what protections keep the DAO accountable.
# Kokonut governance turns community decisions into enforceable action.
The Governance Framework is Kokonut Network's operating manual for collective decision-making. It defines who can propose, who can vote, where proposals are drafted, how long decisions take, what every proposal must include, and how treasury-affecting decisions become executable on-chain.
Kokonut uses this framework so farm funding, Guild bounties, Framework upgrades, partnerships, and ecosystem decisions can move through a clear process instead of informal approval.
This framework is a governance operating manual, not a comprehensive legal document. It is the baseline for Kokonut Network decision-making and can be amended through the same proposal process it describes.
***
## Governance at a glance
| Question | Answer |
| --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| What does this framework govern? | Farm funding, Guild bounties, Framework upgrades, partnerships, DAO amendments, and treasury-affecting decisions. |
| Where are drafts written? | Kokonut Forum is the designated platform for drafting and feedback. |
| Where are votes held? | [DAOHaus](https://link.kokonut.network/dao) for on-chain treasury-affecting proposals. |
| Who can sponsor proposals? | Team Members and Guild Stewards who route-validated work from the Guild layer. |
| Who can vote on-chain? | DAO Members holding at least one `$vKKN` token on the Gnosis Chain. |
| How long does a proposal take? | Minimum 5-day drafting window + minimum 5-day voting window, before grace period and execution. |
| What protects dissenting members? | Rage-quit during the grace period, plus a 66% token retention threshold for on-chain proposals. |
| What must every proposal include? | Ten required fields: name, authors, team, draft start date, description, mission alignment, brand usage, financial implications, success metrics, and next steps. |
The Governance Framework is the process layer. The [Kokonut Moloch DAO](/ecosystem-wiki/the-kokonut-dao/kokonut-moloch-dao) is the on-chain execution layer. The [Kokonut Guilds DAO](/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao) is the contribution and domain-expertise layer.
***
## Why this framework exists
Kokonut Network coordinates real farms, real capital, real contributors, real community commitments, and real public-goods outcomes. That requires more than a chat vote or informal agreement.
The Governance Framework exists to make sure every important decision has:
Every proposal must remain in draft for at least 5 days before it can move to an active vote. This gives members time to ask questions, request edits, and surface risks.
Proposal-authorized people and Guild Stewards move proposals from draft to vote, making sponsorship visible and accountable.
The framework separates off-chain coordination from on-chain treasury voting, so lightweight decisions and capital decisions use the right venue.
On-chain proposals include a grace period, rage-quit protection, and a 66% retention threshold before execution.
Every proposal must define success metrics and next steps so the DAO can evaluate whether the work was completed.
The framework itself can evolve, but only through the same proposal process it governs.
***
## Who can propose and who can vote
Kokonut separates proposal sponsorship, domain contribution, and voting power so the system can recognize both capital and useful work.
| Role | What they can do | Where they act |
| -------------------------- | ------------------------------------------------------------------------------------ | ------------------------------------------- |
| Proposal-authorized person | Draft and sponsor proposals into the active stage | Kokonut Forum → DAOHaus / Kokonut Forum |
| Team Member | Sponsor proposals and steward early ecosystem direction | Governance and operations |
| Guild Steward | Co-sign and route proposals that originate in a Guild | Guilds → Governance process |
| DAO Member | Vote on on-chain proposals with `$vKKN` | DAOHaus |
| Guild Contributor | Contribute useful work and earn Guild Points | Guilds and contribution records |
| Wider community | Review, comment, join Discord, contribute to docs, and help improve proposal quality | Discord, Kokonut Forum, GitHub, Kokonut Hub |
Capital gives voting power through `$vKKN`. Contribution gives operational standing through Guild Points. Significant contribution can later be recognized through Loot, but only if approved through the Moloch DAO proposal process.
***
## Proposal lifecycle
Every Kokonut DAO proposal passes through three mandatory stages. No stage can be skipped.
```mermaid theme={null}
flowchart TD
A["Draft posted in Kokonut Forum"] --> B["5-day minimum drafting window"]
B --> C["Feedback, edits, risk review"]
C --> D["Proposal-authorized sponsor advances proposal"]
D --> E{"Proposal type"}
E -->|"Off-chain coordination"| F["Kokonut Forum vote"]
E -->|"Treasury / token / on-chain action"| G["DAOHaus vote"]
F --> H["Vote closes"]
G --> H
H --> I{"Passed?"}
I -->|"No"| J["Revise and resubmit if useful"]
I -->|"Yes"| K["Grace period opens"]
K --> L{"Retention threshold met?"}
L -->|"No — below 66%"| M["Proposal does not execute"]
L -->|"Yes"| N["Proposal executes"]
N --> O["Team executes next steps"]
O --> P["Success metrics reported"]
```
The proposal is written in Kokonut Forum using the required ten-field structure. Vote-authorized members are notified when the draft is posted.
The proposal must remain open for a **minimum of 5 days**. During this window, members and contributors can request clarification, challenge assumptions, suggest edits, and surface risks before a binding vote begins.
A proposal-authorized person sponsors the proposal into the active stage after the drafting window closes.
* Off-chain coordination proposals can be voted on in Kokonut Forum.
* Treasury, token, or on-chain execution proposals move to [DAOHaus](https://link.kokonut.network/dao).
Active votes remain open for **5 days** and use the voting method assigned to the proposal type.
After an on-chain proposal passes, a grace period opens before execution. DAO members who disagree with the result can rage-quit before the proposal executes.
If rage-quits reduce `$vKKN` token retention below **66%**, the proposal does not execute and must be resubmitted.
Once the vote passes and the grace period closes without breaching the retention threshold, the proposal executes through the DAO.
The proposal team then becomes responsible for the stated next steps, success metrics, reporting, and any follow-up documentation.
***
## Minimum timeline
A proposal that affects the treasury cannot be rushed through in one meeting or private conversation.
```text theme={null}
Day 0: Proposal posted to Kokonut Forum
Day 1-5: Drafting and feedback window
Day 5: Proposal can be sponsored to active voting
Day 5-10: Active voting window
Day 10: Vote closes; grace period opens for on-chain proposals
Day 10+: Execution only if the proposal passed and retention protections hold
```
| Timeline rule | Why it matters |
| ----------------------- | ------------------------------------------------------------------------------------- |
| 5-day draft minimum | Prevents surprise proposals and gives members time to review. |
| 5-day active vote | Gives vote-authorized members enough time to participate. |
| Grace period | Gives dissenting members an exit path before execution. |
| 66% retention threshold | Prevents a proposal from executing if too much capital exits during the grace period. |
***
## Voting methods and proposal venues
| Decision type | Drafting venue | Voting venue | Voting method | Notes |
| -------------------------------- | ------------------------------------- | -------------------------------------------------------------- | ------------------------- | ------------------------------------------------------------------------------ |
| Community coordination | Kokonut Forum | Kokonut Forum | 1 person = 1 vote | Useful for non-treasury, social, operational, or signaling decisions. |
| Treasury disbursement | Kokonut Forum | DAOHaus | 1 `$vKKN` = 1 vote | Used when funds move from the DAO treasury. |
| Membership onboarding | Kokonut Forum / DAOHaus proposal flow | DAOHaus | 1 `$vKKN` = 1 vote | Onboarding quorum is 0% by design; any participation produces a valid outcome. |
| Token minting / Loot recognition | Kokonut Forum | DAOHaus | 1 `$vKKN` = 1 vote | Requires explicit proposal and DAO approval. |
| Governance framework amendment | Kokonut Forum | DAOHaus if on-chain impact; Kokonut Forum if coordination-only | Depends on proposal scope | Must include the edited framework or exact amendment language. |
If a proposal moves treasury funds, mints tokens, awards Loot, changes DAO parameters, or affects on-chain execution, it should be treated as an on-chain governance proposal.
***
## Required proposal fields
Every proposal must include the same ten base fields, regardless of proposal type.
| Field | What to include | Why it matters |
| ---------------------- | ---------------------------------------------------------------------------- | ---------------------------------------------------- |
| Proposal Name | Short descriptive name, ideally with the correct proposal code | Makes the proposal easy to reference and archive |
| Proposal Author(s) | Name, alias, and wallet address of the author(s) | Creates accountability |
| Proposal Team | People responsible for execution if the proposal passes | Separates authorship from delivery responsibility |
| Draft Start Date | Date the draft was first posted in Kokonut Forum | Starts the 5-day drafting window |
| Proposal Description | What the proposal asks for, what it will produce, and why now | Gives voters the core decision context |
| Mission Alignment | How the proposal advances Kokonut Network's mission | Filters proposals that are not strategically aligned |
| Brand Usage | Whether the proposal uses Kokonut name, logo, or marks | Protects ecosystem reputation |
| Financial Implications | Exact costs, amounts, treasury impact, disbursement conditions, and timeline | Required for responsible treasury governance |
| Success Metrics | How the DAO will know if the proposal worked | Enables accountability after execution |
| Next Steps | Who does what after approval | Reduces ambiguity after the vote passes |
[Use a ready-made proposal template →](/ecosystem-wiki/the-kokonut-dao/proposal-templates)
***
## Proposal types
Request treasury funding for a new syntropic farm or a material expansion of an existing farm. Requires the strongest documentation: farm overview, crops, revenue model, public-goods allocation, local problem, solution, and MRV plan.
Commission scoped work from contributors through a Guild Steward. Useful for development, MRV, documentation, governance, finance, partnerships, and other operational work.
Propose changes to the Kokonut Framework, Common Data Schema, MRV methodology, agent architecture, or documentation standards.
Establish a formal relationship with an external organization, funder, farm operator, research partner, tool provider, or ecosystem collaborator.
***
## What makes a proposal strong
A strong Kokonut proposal should be easy to inspect, hard to misunderstand, and possible to measure after execution.
| Proposal quality | Strong version | Weak version |
| ----------------- | -------------------------------------------------------------------------------------------- | ---------------------------------------------- |
| Specific ask | Requests a defined amount, deliverable, team, and timeline | Asks for general support or vague approval |
| Mission alignment | Explains how the work advances farms, Framework, DAO, MRV, Guilds, or public goods | Uses generic sustainability language |
| Financial clarity | Includes exact amounts, wallet addresses, release conditions, and budget line items | Says funds will be used “as needed” |
| Evidence | References data, prior work, farm records, GitHub issues, MRV outputs, or community feedback | Relies on trust or reputation alone |
| Success metrics | Defines measurable outputs and reporting deadlines | Does not explain how success will be evaluated |
| Next steps | Names owners and immediate actions after approval | Leaves execution unclear |
For farm funding proposals, the standard should be especially high. New farm proposals should include location, coordinates, land area, operator wallet, Framework phase, Data Hub link or plan, crop model, revenue streams, target markets, public-goods allocation, and local problem/solution context.
***
## Governance protections
Kokonut governance is designed to reduce the need for personal trust.
| Protection | What it prevents |
| ------------------------ | --------------------------------------------------------------------------- |
| Public drafting | Prevents decisions from being prepared privately without member awareness. |
| Minimum review period | Prevents rushed votes. |
| Proposal sponsorship | Prevents unvetted drafts from becoming active votes without accountability. |
| On-chain execution | Prevents private wallet control over treasury actions. |
| Rage-quit | Gives dissenting members an exit before execution. |
| 66% retention threshold | Prevents proposals from executing if too much capital exits in protest. |
| Required success metrics | Prevents proposals from passing without a way to judge completion. |
| Amendment process | Prevents unilateral edits to governance rules. |
***
## Amendments and rejected proposals
### Amendments
This Governance Framework can evolve. Any amendment must include the exact proposed change and pass through the full proposal lifecycle.
A strong amendment proposal should include:
* the current text,
* the proposed replacement text,
* why the change is needed,
* who is affected,
* whether it changes treasury risk,
* whether it changes rights or responsibilities,
* and when the amendment becomes active.
### Rejected proposals
Rejected proposals may be revised and resubmitted. There is no required cooling-off period, but resubmissions should address the reasons the original proposal failed.
A useful resubmission should include a short changelog explaining what changed since the previous version.
***
## Before you submit a proposal
Farm Funding, Guild Bounty, Framework Upgrade, and Partnership proposals each need different supporting evidence. Start with the relevant template.
Do not skip mission alignment, financial implications, success metrics, or next steps. Those fields are what turn an idea into an accountable proposal.
Open the proposal for the required 5-day drafting window. Treat feedback as part of the proposal process, not as a delay.
Guild-originating work should involve the relevant Guild Steward. Treasury-affecting work should be prepared for on-chain voting.
Know who will execute the work, how funds will be used, when updates will be posted, and how success will be measured after approval.
***
## Next steps
Copy ready-to-use templates for Farm Funding, Guild Bounty, Framework Upgrade, and Partnership proposals.
Understand the on-chain system that enforces treasury execution, `$vKKN`, Loot, rage-quit, and the 66% retention threshold.
Learn how contributors earn Guild Points, gain standing, and route domain work into the DAO proposal process.
See how governance, logic, execution, production, and infrastructure layers work together across the full Kokonut DAO architecture.
Draft proposals, collect feedback, and run the required governance review window.
View the on-chain DAO where treasury-affecting proposals are voted on and executed.
# Kokonut Guilds
Source: https://kokonut.network/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao
The contribution-weighted operational layer of Kokonut Network — where builders, researchers, organizers, and operators earn standing through verified work.
# Kokonut Guilds turn useful work into governance standing.
Kokonut has two paths into the network.
The **capital path** runs through the [Kokonut Moloch DAO](/ecosystem-wiki/the-kokonut-dao/kokonut-moloch-dao): members tribute stablecoins, receive `$vKKN`, vote on treasury decisions, and are protected by rage-quit.
The **contribution path** runs through Kokonut Guilds: contributors ship useful work, earn non-transferable Guild Points, gain standing inside a domain, and can eventually help route work, funding requests, and proposals back to the Moloch DAO.
Guilds exist because the people who understand the work should help govern the work — even if they did not enter the DAO through capital.
No capital required to begin. Start with a task, contribution, review, report, dataset, proposal, or coordination role.
***
## Guilds at a glance
| Question | Answer |
| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| What are Guilds? | Domain-specific contributor groups responsible for executing Kokonut work. |
| Who can start? | Anyone who can make a useful contribution. Formal membership is earned over time. |
| What do Guilds govern? | Domain decisions, standards, bounty programs, task prioritization, and execution workflows. |
| What are Guild Points? | Non-transferable reputation points tied to verified contributions in a specific Guild. |
| Can points be bought? | No. Points are earned through work and cannot be transferred, delegated, or purchased. |
| How do Guilds connect to the DAO? | Guilds coordinate work and can route proposals to the Moloch DAO when treasury funding or token recognition is needed. |
| Can Guild contributors earn DAO stake? | Significant contributions can be recognized through Moloch DAO Loot awards, subject to proposal and vote. |
Guilds solve Kokonut's "expertise in the game" problem. The Moloch DAO protects treasury governance. Guilds make sure the people doing the work can shape how that work evolves.
***
## Why Guilds exist
Token-weighted governance is useful for treasury control, but it is not enough to run a living ecosystem.
A farm network needs people who can:
* improve smart contracts and data pipelines,
* validate the MRV methodology,
* document farm activity,
* write grants and proposals,
* coordinate communities,
* review budgets,
* support farmers,
* explain governance,
* and turn real-world work into public evidence.
The people best qualified to make those decisions are not always the people with the most capital. Guilds give Kokonut a way to recognize expertise, effort, and execution.
> **Moloch governs the treasury. Guilds govern the work.**
***
## How merit-based membership works
Start by doing useful work. This can be a shipped feature, a pull request, an MRV submission, a field report, a proposal draft, a grant application, a documentation improvement, a design asset, a partner intro, or a community coordination task.
Recognized work becomes a contribution record. A good record explains what was done, who did it, which Guild it belongs to, what evidence supports it, and why it matters to Kokonut.
Completed contributions can earn Guild Points. Points are non-transferable reputation units scoped to the Guild where the work happened. They cannot be bought, sold, delegated, or moved across wallets.
Once a contributor reaches the Guild's active threshold, they gain standing inside that Guild: voting rights on Guild-scoped decisions, access to working documents, and eligibility to help author proposals.
When Guild work needs treasury funding, token recognition, or DAO-wide approval, the Guild can route a proposal to the Moloch DAO. Token holders vote on capital allocation, while Guild contributors provide domain expertise and accountability for execution.
### Common contribution records
| Contribution type | Example evidence | Likely Guild |
| ----------------- | ---------------------------------------------------------------------------- | ------------------------------ |
| Code contribution | Pull request, deployed contract, test suite, API endpoint, dashboard | Technology Guild |
| Impact work | MRV report, satellite analysis, EBF review, SDG mapping, field validation | Impact Guild |
| Documentation | New docs page, page rewrite, contributor guide, educational asset | Communications Guild |
| Governance work | Proposal template, review memo, forum summary, and onboarding checklist | Governance Guild |
| Financial work | Budget model, revenue forecast, treasury report, grant finance section | Finance Guild |
| Partnerships | Farmer intro, partner MOU, event, local coordination, ecosystem relationship | Community & Partnerships Guild |
***
## Membership tiers
| Tier | Entry criteria | Rights | What it means |
| ----------- | -------------------------------------------------- | ------------------------------------------------------------------- | ----------------------------------------------- |
| Contributor | Complete an open task or recognized contribution | No formal voting rights yet | Open entry point for anyone who wants to help |
| Member | Reach the Guild's minimum point threshold | Vote on Guild-internal decisions | Active contributor with domain standing |
| Steward | Elected by Guild members | Represent the Guild in cross-Guild governance and co-sign proposals | Trusted coordinator for the Guild's domain |
| Emeritus | Former Steward with sustained contribution history | Advisory voice, no active voting weight by default | Reputation is preserved, even if activity slows |
Each Guild can define its own point thresholds, review process, and Steward term lengths. Changes should be made through Guild proposals with sufficient notice to affected contributors.
***
## Choose your Guild
For smart contracts, MRV data pipelines, APIs, indexers, dashboards, frontend interfaces, open-source tools, and AI agent integrations.
For MRV methodology, EBF reporting, CRISP carbon-risk scoring, SDG alignment, field validation, biodiversity evidence, and impact attestations.
For documentation, content strategy, social media, community updates, onboarding materials, grant storytelling, and public narrative.
For proposal review, governance amendments, member onboarding, dispute resolution, voting process design, and cross-Guild coordination.
For treasury reporting, farm financial modeling, budgets, grant finance, stablecoin strategy, tax/compliance support, and revenue forecasting.
For farmer onboarding, institutional partnerships, ReFi collaborations, local events, community relationships, and cooperative network development.
***
## What each Guild produces
### Technology Guild
**Purpose:** Build and maintain the technical infrastructure that enables Kokonut to be composable, auditable, and usable.
**Useful contributions include:**
* Smart contract development and review
* DAO tooling and proposal interfaces
* Farm Registry APIs
* MRV data pipelines
* Data Hub improvements
* Agentic Marketplace integrations
* Frontend applications and dashboards
* Open-source tooling for the Kokonut Framework
**Good first tasks:** fix docs links, improve schema examples, add API examples, test MRV payload formats, document deployed contracts, or build small dashboard components.
***
### Impact Guild
**Purpose:** Protect the credibility of Kokonut's ecological and social impact claims.
**Useful contributions include:**
* MRV methodology design
* Satellite and drone data validation
* Soil and biodiversity reporting
* SDG alignment reviews
* EBF and CRISP methodology work
* Annual impact reports
* Third-party attestation coordination
* Adelphi and future farm impact dashboards
**Good first tasks:** review SDG mappings, improve MRV documentation, validate a crop or biodiversity data point, propose an impact metric, or help turn field observations into structured evidence.
***
### Communications Guild
**Purpose:** Make the Kokonut ecosystem understandable, discoverable, and easy to join.
**Useful contributions include:**
* Ecosystem documentation
* Landing page and onboarding copy
* Twitter/X and Discord updates
* Grant narratives
* Community education materials
* Video scripts and explainers
* Contributor guides
* Public progress reports
**Good first tasks:** improve a docs page, write a short contributor guide, turn a farm update into a social thread, create an onboarding checklist, or simplify a technical page for non-technical readers.
***
### Governance Guild
**Purpose:** Keep Kokonut's decision-making legible, fair, and operationally useful.
**Useful contributions include:**
* Proposal review and formatting
* Governance Framework amendments
* DAO onboarding guides
* Cross-Guild coordination
* Conflict and arbitration process design
* Moloch proposal support
* Vote summaries and decision logs
* Governance parameter reviews
**Good first tasks:** improve proposal templates, summarize a governance decision, review a draft proposal, map a decision process, or create a new contributor governance FAQ.
***
### Finance Guild
**Purpose:** Help the DAO understand capital flows, farm economics, budgets, and funding decisions.
**Useful contributions include:**
* Treasury reporting
* Farm revenue models
* Budget reviews
* Grant financial sections
* Stablecoin strategy
* Public goods allocation modeling
* Dominican tax/compliance support
* Partner financial diligence
**Good first tasks:** review a harvest forecast, improve a budget table, model a farm revenue scenario, create a treasury reporting template, or document public-goods allocation logic.
***
### Community & Partnerships Guild
**Purpose:** Build the relationships that allow Kokonut to grow beyond one farm.
**Useful contributions include:**
* Farmer onboarding
* Partner discovery
* Local government relationships
* ReFi ecosystem integrations
* Public goods protocol relationships
* Community events in the Dominican Republic
* MOU and partnership templates
* New farm pipeline support
**Good first tasks:** introduce a relevant partner, document a farmer onboarding need, draft an MOU template, coordinate a local event, or map potential future farms.
***
## How Guilds connect to Moloch DAO
Guilds and Moloch are intentionally separate.
Moloch protects the treasury. Guilds coordinate execution. This prevents every operational decision from becoming a full DAO vote while keeping capital allocation under token-holder governance.
```mermaid theme={null}
flowchart TD
A["Contributor does useful work"] --> B["Guild reviews contribution"]
B --> C["Guild Points recorded"]
C --> D["Contributor gains Guild standing"]
D --> E["Guild coordinates tasks and standards"]
E --> F{"Needs treasury funds or DAO recognition?"}
F -->|"No"| G["Guild executes internally"]
F -->|"Yes"| H["Guild authors Moloch proposal"]
H --> I["$vKKN holders vote"]
I --> J["Passed proposal funds work or awards Loot"]
J --> K["Work produces farm, software, MRV, or ecosystem outputs"]
K --> B
style A fill:#d1fae5,stroke:#10b981,color:#065f46
style C fill:#dbeafe,stroke:#3b82f6,color:#1e40af
style H fill:#fef3c7,stroke:#f59e0b,color:#92400e
style I fill:#ede9fe,stroke:#8b5cf6,color:#4c1d95
```
| Layer | Mechanism | What it governs |
| ------------------ | ---------------------------------------- | ------------------------------------------------------------------------ |
| Moloch DAO | Token-weighted votes, 1 `$vKKN` = 1 vote | Treasury allocation, DAO membership, rage-quit, token recognition |
| Guilds | Contribution-weighted points | Operational decisions, domain standards, bounties, working groups |
| Meta-governance | Steward deliberation | Cross-Guild coordination, pre-Moloch consensus, ecosystem-wide standards |
| Production and MRV | Farm records, dashboards, attestations | Evidence that work happened and created value |
Guilds can propose. Moloch decides on the treasury. This keeps execution fast while preserving capital accountability.
***
## How contributions can become Loot
Guild Points are not the same as DAO Loot.
Guild Points measure contribution history inside a Guild. They are non-transferable and domain-specific. DAO Loot is issued through the Moloch DAO and can recognize meaningful contributions to the broader network.
A possible path looks like this:
1. A contributor completes meaningful Guild work.
2. The Guild records and reviews the contribution.
3. The contributor gains points and standing.
4. The Guild may recommend the contributor for DAO-level recognition.
5. A Moloch proposal requests a Loot award.
6. `$vKKN` holders vote.
7. If passed, the contributor receives Loot recognition from the DAO.
Loot is not automatic. It should be reserved for significant contributions that create durable value for the network, such as shipped infrastructure, verified impact reporting, farm onboarding, major grant support, or ecosystem coordination.
***
## What is live vs. still developing
| Area | Status | Notes |
| ------------------------------ | ------------------------------- | -------------------------------------------------------------------------------------------------- |
| Moloch DAO treasury governance | Live | Capital allocation and membership happen through the DAO layer. |
| Guild model | Active / evolving | The structure is defined; operating processes can improve through contribution. |
| Guild Points | Developing | Point thresholds, review rules, and on-chain reputation details should continue to mature. |
| Loot recognition | Available through DAO proposals | Recognition of significant contributions must still pass through Moloch governance. |
| Farm evidence layer | Live at Adelphi | Adelphi farm records, MRV events, and Data Hub outputs give Guilds real work to coordinate around. |
| Agentic Marketplace | Developing | Future automation can help Guilds scale MRV, reporting, and workflow coordination. |
***
## Frequently asked questions
No. Guilds are the contribution path. You can begin by completing useful work, joining a working group, submitting a pull request, helping with MRV, improving documentation, or supporting community operations.
Yes. Guild standing is scoped by domain. Your Technology Guild contributions are separate from your Impact Guild contributions, but many contributors naturally work across multiple Guilds.
No. Guild Points are non-transferable contribution records. They represent work, not capital.
Your historical contribution record remains. Guilds may use activity windows to decide who retains active voting rights, but past work should remain visible as reputation history.
A new Guild can be proposed by active contributors. It should define a domain, founding members, point logic, Steward responsibilities, and relationship to the broader Kokonut mission before going to governance review and, when needed, Moloch DAO approval.
Guilds can request funding through Moloch proposals when work requires treasury support. Over time, farm revenue and the broader Kokonut flywheel can help create recurring budgets for Guild operations and bounties.
***
## Start contributing
Start here to understand the active contribution paths for agronomists, researchers, developers, DAO members, partners, and capital allocators.
Technical contributors can explore the public docs, contracts, Farm Registry primitives, API ideas, and agent architecture.
Understand the treasury, `$vKKN`, Loot, rage-quit, and a capital governance layer that Guild proposals connect into.
Read the proposal process, voting flow, amendment procedures, and how decisions move through the DAO.
Use structured proposal formats when Guild work needs funding, recognition, or governance approval.
See the live farm that creates real work for Guilds: MRV, reporting, infrastructure, community operations, and replication.
# Kokonut Moloch DAO
Source: https://kokonut.network/ecosystem-wiki/the-kokonut-dao/kokonut-moloch-dao
The capital governance engine of Kokonut Network: stablecoin tribute, soulbound membership tokens, treasury controls, rage-quit protection, and proposal execution on Gnosis Chain.
# Kokonut Moloch DAO is the treasury engine that makes community ownership enforceable.
The Kokonut Moloch DAO is the capital and governance engine of Kokonut Network. It is the live on-chain system on Gnosis Chain that holds the treasury, governs farm funding, mints membership tokens, burns exiting shares, and protects every capital-contributing member through rage-quit.
Kokonut does not ask members to trust an administrator, a company wallet, or the Core Team. Treasury actions require passed proposals. Membership is minted through DAO approval. Capital can exit through rage-quit. Governance rights are enforced by contracts instead of promises.
Capital contribution is one path into Kokonut. Contributors without capital can start through Guilds and earn standing through verified work.
***
## DAO at a glance
| Question | Answer |
| ------------------------------------------------ | ------------------------------------------------------------------------------------------------ |
| What does this DAO govern? | Treasury assets, membership, farm funding, Guild funding, partnerships, and governance upgrades. |
| Where is it deployed? | [Gnosis Chain](https://docs.gnosischain.com/), Chain ID `100`. |
| What assets does the treasury accept? | Stablecoins only. The treasury is not designed around speculative token price exposure. |
| How do members join? | By submitting a membership proposal and tributing stablecoins to the treasury. |
| What does a member receive? | Soulbound \$vKKN voting tokens. Each \$vKKN = 1 vote and is backed 1:1 by a real coconut tree. |
| How are contributors without capital recognized? | Through Guild Points and potential Loot token awards via DAO proposal. |
| What protects members? | Rage-quit: members can exit with their proportional treasury share. |
| Who can move treasury funds? | Only the DAO through passed proposals. No individual can move funds unilaterally. |
The Moloch DAO is the capital path. The [Kokonut Guilds DAO](/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao) is the contribution path. Together, they separate financial commitment from domain expertise so both capital and work can be recognized.
***
## Why Moloch?
Kokonut uses the Moloch DAO pattern because it solves a specific governance problem: how can a group coordinate capital without trusting a central operator?
Moloch DAOs have no administrators and no trusted intermediaries. Decisions are made through proposals that execute against treasury or vault contracts. No individual — including the Kokonut Core Team — can move funds, mint tokens, burn tokens, or change governance parameters without a passed community vote.
Treasury actions require proposals. The Main Treasury is controlled by DAO execution, not a private multisig controlled by the Core Team.
New \$vKKN holders are admitted through the governance process. Stablecoin tribute enters the treasury only if the proposal passes.
Members can rage-quit with their proportional share of the treasury if they disagree with the DAO's direction or a passed proposal.
***
## Core mechanics
| Mechanic | How it works at Kokonut |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Network chain | Deployed on [Gnosis Chain](https://docs.gnosischain.com/), an EVM-compatible network. Chain ID: `100`. RPC: `https://rpc.gnosischain.com`. Explorer: [Gnosisscan](https://gnosisscan.io). |
| Stablecoin tribute | Membership tribute is paid in stablecoins. This reduces governance exposure to speculative crypto volatility and keeps the treasury oriented around productive deployment. |
| Soulbound membership | \$vKKN and Loot are non-transferable. Governance and economic rights come from proposal approval, capital contribution, land stewardship, or verified work — not from buying tokens on a secondary market. |
| Rage-quit | Members can exit with their proportional share of the treasury. This is the primary capital-protection mechanism. |
| Grace period | After a proposal passes, a grace period opens before execution. Members who disagree can exit before the proposal executes. |
| 66% retention threshold | If rage-quits reduce token retention below 66%, the proposal does not execute. This protects the treasury from governance attacks. |
| Proposal execution | Treasury actions are executed through the DAO once the proposal process completes. No additional approval from the Core Team is required. |
***
## DAO components
### Tokens
Both Kokonut DAO tokens are **soulbound**. They cannot be transferred, sold, delegated, or traded on the open market.
| Token | Contract | Purpose |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| \$vKKN — Voting Token | [`0xc6b075ac3234a7ac729114b27370b552fa284690`](https://gnosisscan.io/token/0xc6b075ac3234a7ac729114b27370b552fa284690) | Soulbound governance token. Minted via DAO proposal when a member tributes stablecoins. 1 \$vKKN = 1 vote. Each \$vKKN is backed 1:1 by a real coconut tree in a Kokonut Network farm. |
| Loot Token | [`0x2508a11aee11ad545bae87cd42131c04613b2099`](https://gnosisscan.io/token/0x2508a11aee11ad545bae87cd42131c04613b2099) | Non-voting soulbound token. Awarded to landowners, contributors, Core Team members, and partners who add verifiable value via DAO proposal. Carries economic rights and rage-quit eligibility without governance voting rights. |
### Infrastructure contracts
| Contract | Address | Purpose |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Vault & Token Manager | [`0x8977c56e979f0d8b76afb5ad85549acd2e96422d`](https://gnosisscan.io/address/0x8977c56e979f0d8b76afb5ad85549acd2e96422d) | Handles token issuance and DAO smart wallet operations. All operations require a passed proposal. Kokonut DAO is the sole signatory. |
| Main Treasury SAFE | [`0xeb55b75328a8dffd45bbf34b7e7efc431a179085`](https://gnosisscan.io/address/0xeb55b75328a8dffd45bbf34b7e7efc431a179085) | Rage-quit-enabled SAFE wallet. Handles tribute inflows, disbursement outflows, token minting, token burning, and rage-quit exits. Public treasury view: [link.kokonut.network/treasury](https://link.kokonut.network/treasury). |
***
## How membership works
Membership in the Kokonut Moloch DAO is open to anyone willing to contribute stablecoins to the treasury and pass the DAO's membership proposal process.
Decide how many \$vKKN tokens you want to request. Each token is backed 1:1 by a real coconut tree and grants 1 vote on on-chain proposals.
You will need:
* A Web3 wallet connected to Gnosis Chain
* Stablecoins on Gnosis Chain for the tribute
* A small amount of xDAI for gas
* The current membership proposal parameters
[Book a call](https://link.kokonut.network/meeting) if you need help confirming the current tribute rate or proposal requirements before submitting.
Navigate to [link.kokonut.network/dao](https://link.kokonut.network/dao) and submit a membership proposal specifying your tribute amount and the \$vKKN you are requesting.
The proposal enters the broader Kokonut governance process: a drafting and feedback window, followed by on-chain voting on DAOHaus.
Members review the proposal, discuss it, and vote on it. On-chain voting uses the rule: **1 \$vKKN = 1 vote**.
For onboarding proposals, quorum is intentionally permissionless: any level of participation produces a valid result, and the proposal needs a majority "For" vote to pass.
After a membership proposal passes, the grace period begins before execution. Existing members who disagree with the new membership can rage-quit with their proportional treasury share before the proposal executes.
Once the grace period closes and the proposal executes, your stablecoin tribute enters the treasury, and your \$vKKN tokens are minted to your wallet.
You now have voting rights, eligibility for proposal sponsorship, rage-quit protection, access to DAO coordination, and visibility into farm funding and MRV data.
No capital? Start with Guilds. Contributors can complete useful work, earn Guild Points, and become eligible for Loot token awards through Moloch DAO proposals. Loot carries economic rights without requiring a stablecoin tribute.
***
## The membership flow
```mermaid theme={null}
flowchart TD
A["Prospective member"] --> B["Prepare stablecoin tribute"]
B --> C["Submit membership proposal"]
C --> D["Drafting and feedback on Charmverse"]
D --> E["On-chain vote on DAOHaus"]
E --> F{"Proposal passes?"}
F -->|"No"| G["Proposal fails\ntribute not accepted"]
F -->|"Yes"| H["Grace period opens"]
H --> I{"Existing members rage-quit?"}
I -->|"Yes"| J["Members exit\nwith proportional treasury share"]
I -->|"No / threshold retained"| K["Proposal executes"]
J --> L{"66% retention met?"}
L -->|"No"| M["Execution blocked"]
L -->|"Yes"| K
K --> N["Stablecoins enter treasury"]
K --> O["\$vKKN minted"]
O --> P["Member gains voting rights"]
```
***
## How rage-quit works
Rage-quit is the capital-protection mechanism that sets the Kokonut DAO apart from traditional investment structures. It gives members an enforceable right of exit.
| Question | Answer |
| ------------------------------------ | ------------------------------------------------------------------------------------------------- |
| When can a member rage-quit? | At any time, including during the grace period after a passed proposal and before execution. |
| What does the member receive? | A proportional share of all assets held in the treasury at the time of exit. |
| What happens to the member's tokens? | Their \$vKKN or Loot is burned, and the total share count decreases. |
| Can an admin block it? | No. Rage-quit is a contract-level mechanism, not a Core Team permission. |
| Does it erase governance history? | No. Past votes remain part of the DAO record. Rage-quit is an economic exit, not a history reset. |
```mermaid theme={null}
flowchart TD
A["Proposal approved by DAO"] --> B["Grace period begins"]
B --> C{"Member wants to exit?"}
C -->|"Yes"| D["Rage-quit\nreceive proportional treasury share\ntokens are burned"]
C -->|"No"| E["Remain in DAO\nretain voting power"]
D --> F{"66% token retention met?"}
E --> F
F -->|"Yes"| G["Execute proposal"]
F -->|"No"| H["Block execution"]
```
The 66% token-retention threshold means a proposal executes only if enough token power remains in the DAO after the grace period. If rage-quits reduce supply below the required threshold, the proposal is blocked and must be resubmitted.
***
## Voting power distribution
Kokonut DAO is designed so members control the DAO structurally, not symbolically.
| Role | Voting power | Notes |
| --------------------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------- |
| [DAO Members](https://link.kokonut.network/members) | **99.99%** | All \$vKKN holders collectively. Voting power grows as new members tribute stablecoins and receive \$vKKN. |
| [Core Team](https://kokonut.network/about) | **0%** | The Core Team holds no governance tokens and cannot vote on or veto proposals. |
| [DAO Summoner](https://link3.to/wasabinetwork) | **0.0016%** | The wallet that initially deployed the DAO contracts. Symbolic founder position. |
This distribution is enforced at the contract level. The Core Team's 0% voting power is not a policy preference — it is a structural governance choice.
***
## What \$vKKN holders can do
| Utility | Description | Access |
| --------------------------------- | ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Governance voting | Vote on farm funding, bounties, partnerships, governance upgrades, token minting, and token burning. | [DAOHaus](https://link.kokonut.network/dao) |
| Proposal sponsorship | Sponsor eligible draft proposals to the active voting stage. | [DAOHaus](https://link.kokonut.network/dao) |
| Rage-quit protection | Exit with proportional treasury share, including during grace periods. | [DAOHaus](https://link.kokonut.network/dao) |
| Proposal authorship | Submit farm funding, Guild bounty, Framework upgrade, and ecosystem partnership proposals. | [Proposal Templates](/ecosystem-wiki/the-kokonut-dao/proposal-templates) |
| Community coordination | Participate in governance drafts, feedback, bounties, and member coordination. | [Charmverse](https://link.kokonut.network/charmverse) |
| Farm data visibility | Inspect live MRV data, harvest records, and impact metrics for DAO-funded farms. | [Kokonut Hub](https://hub.kokonut.network/projects/41) |
| Loot eligibility for contributors | Significant verified Guild contributions can be recognized with Loot through DAO proposal. | [Kokonut Guilds](/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao) |
| Member meetings | Request direct meetings with Core Team members. | [Meeting Calendar](https://link.kokonut.network/meeting) |
***
## Capital path vs contribution path
Kokonut separates two forms of commitment:
| Path | How you enter | What you earn | Best for |
| ----------------- | ---------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Capital path | Stablecoin tribute through a Moloch membership proposal | \$vKKN voting power and rage-quit protected treasury claim | DAO members, capital allocators, farm funders, long-term governance participants |
| Contribution path | Verified work through Guild tasks, bounties, research, MRV, development, governance, or partnerships | Guild Points and potential Loot awards through proposal | Builders, agronomists, researchers, operators, designers, writers, developers, and community organizers |
Both paths are important. Capital funds the network. Contributors make the network real.
***
## What is live, and what is still developing
| Component | Status | Notes |
| ---------------------------------- | ---------- | ------------------------------------------------------------------------------------------------- |
| Moloch DAO | Live | Deployed on Gnosis Chain with treasury, token, and membership contracts. |
| \$vKKN and Loot | Live | Soulbound governance and non-voting economic rights tokens. |
| Rage-quit | Live | Core Moloch protection mechanism for treasury exit. |
| Charmverse + DAOHaus proposal flow | Live | Used for drafting, discussion, voting, and execution. |
| Adelphi farm data | Live | Public farm records available through the Kokonut Hub. |
| Guild contribution reputation | Developing | Contribution tracking, Guild Points, and stewardship workflows continue to mature. |
| Agentic Marketplace | Developing | AI-assisted MRV, reporting, and coordination automation are being built to scale beyond one farm. |
***
## Trust checklist
Before joining, a prospective member should be able to answer:
* Do I understand that \$vKKN is soulbound and non-transferable?
* Do I understand the current tribute rate and membership parameters?
* Do I understand that stablecoin tribute enters the DAO treasury if the proposal passes?
* Do I understand rage-quit and the 66% retention threshold?
* Do I understand that DAO participation involves governance responsibility, not passive ownership?
* Have I inspected the treasury, DAO page, and live farm data?
* Have I considered whether the Guild contribution path is a better fit than the capital path?
This page explains Kokonut DAO mechanics. It is not legal, tax, or financial advice. Membership involves governance responsibility and should be evaluated carefully before submitting a tribute proposal.
***
## Next steps
Understand how the Moloch DAO fits into the five-layer Kokonut Network stack: governance, logic, execution, production, and infrastructure.
Start through contribution instead of capital. Earn Guild Points through useful work and become eligible for Loot through DAO proposal.
Review drafting windows, voting duration, quorum, retention threshold, proposal stages, and execution rules.
Use ready-to-adapt templates for membership, farm funding, Guild bounties, Framework upgrades, and partnerships.
Inspect the first live farm the network is building around: 15,725 m², public MRV, and community-first regenerative production.
Explore harvest records, MRV events, farm milestones, and impact data connected to Adelphi.
# DAO Proposal Templates
Source: https://kokonut.network/ecosystem-wiki/the-kokonut-dao/proposal-templates
Copy-ready Kokonut DAO proposal templates for farm funding, Guild bounties, Framework upgrades, and partnerships — with guidance on when to use each one and what reviewers need to see.
# Write proposals that the DAO can review, vote on, and execute.
Kokonut proposals are not informal requests. They are the bridge between community intent and executable DAO action: treasury disbursements, farm launches, Guild bounties, Framework upgrades, partnerships, token recognition, and operational commitments.
Use this page when you already know what you want to propose and need the correct structure. If you are still learning how governance works, start with the [Governance Framework](/ecosystem-wiki/the-kokonut-dao/governance-framework).
Every template below follows the ten required fields used across Kokonut governance.
These templates are governance tools, not legal, tax, financial, or investment advice. If a proposal creates legal obligations, external contracts, compliance exposure, or long-term partnership commitments, include appropriate review before asking the DAO to vote.
***
## Proposal flow at a glance
| Step | What happens | Minimum timing | Where it happens |
| --------------------- | -------------------------------------------------------------------- | -------------------------- | --------------------------------------- |
| 1. Choose a template | Select the correct proposal type and copy the template | Before drafting | This page |
| 2. Draft proposal | Fill every required section with concrete details | Day 0 | Kokonut Forum / workspace |
| 3. Review window | Members and Guilds comment, challenge assumptions, and request edits | 5 days minimum | Kokonut Forum / workspace |
| 4. Sponsor proposal | A proposal-authorized person or Guild Steward advances the proposal | After drafting window | Kokonut Forum → DAOHaus if on-chain |
| 5. Vote | DAO members vote according to the proposal type | 5 days minimum | DAOHaus for treasury / on-chain actions |
| 6. Grace period | Members can rage-quit before execution if they disagree | After passed on-chain vote | Moloch DAO flow |
| 7. Execute and report | Proposal team completes milestones and reports success metrics | After execution | Guilds, DAO, Data Hub, docs |
Treasury-moving, token-minting, Loot-awarding, membership, DAO-parameter, or on-chain execution proposals should go to [DAOHaus](https://link.kokonut.network/dao). Coordination-only decisions can remain in the forum if they do not require DAO execution.
***
## Choose the right template
Request DAO treasury funding for a new syntropic farm, farm expansion, infrastructure buildout, or farm phase upgrade.
Request funding for scoped work completed by contributors through a Guild: code, research, MRV, docs, design, finance, governance, or operations.
Propose a change to Kokonut's schemas, MRV methodology, governance parameters, development phases, or impact framework.
Formalize a relationship with an external organization, funder, protocol, research institution, cooperative, or ecosystem partner.
| If your proposal mainly asks for... | Use this template | Naming convention | Primary reviewer |
| ----------------------------------------------------------------------------------------- | ----------------- | ----------------- | -------------------------------------------------- |
| Capital for land, crops, infrastructure, operators, or farm expansion | Farm Funding | `KDP-N` | Impact Guild + DAO |
| Payment for scoped contributor work | Guild Bounty | `KBP-N` | Issuing Guild |
| A change to schemas, MRV, APIs, governance rules, or Framework docs | Framework Upgrade | `KFP-N` | Technology Guild / Governance Guild / Impact Guild |
| A formal external relationship, data-sharing agreement, co-funding, or brand relationship | Partnership | `KPP-N` | Community & Partnerships Guild |
Proposal numbers are assigned when the Governance Guild registers the draft. Do not self-assign the final number before your draft is posted and logged.
***
## Universal proposal checklist
Before you submit any proposal, make sure it answers the reviewer's real questions.
| Reviewer question | Your proposal must answer |
| --------------------------------------- | --------------------------------------------------------------------------------------------------- |
| What exactly are we approving? | Name the action, amount, scope, deliverables, responsible people, and timeline. |
| Why should this happen now? | Explain the problem, opportunity, dependency, or risk that makes the proposal timely. |
| Who is accountable? | List authors, team members, Guilds, operators, reviewers, and wallet addresses where relevant. |
| What does the DAO pay for or commit to? | Include treasury amount, token effect, brand use, technical work, data access, or legal commitment. |
| What proves success? | Define measurable milestones, acceptance criteria, reporting cadence, and evidence sources. |
| What could go wrong? | Include risks, assumptions, out-of-scope items, revocation conditions, and dispute paths. |
| What happens after the vote? | Add concrete next steps, owners, deadlines, and reporting obligations. |
Vague proposals are expensive for the DAO to review. If your proposal cannot define its budget, success metrics, responsible team, acceptance criteria, and next step, it should stay in drafting.
***
## The ten required fields
Every Kokonut proposal uses the same ten-field base structure.
| Field | Purpose |
| ------------------------- | ---------------------------------------------------------------------------------- |
| A. Proposal Name | Makes the proposal easy to reference and track. |
| B. Proposal Author(s) | Identifies who is asking and who can answer questions. |
| C. Proposal Team | Name the people responsible for execution and review. |
| D. Draft Start Date | Starts the minimum 5-day drafting window. |
| E. Proposal Description | Explains exactly what is being approved. |
| F. Mission Alignment | Connects the proposal to Kokonut's purpose, farms, Framework, Guilds, or DAO. |
| G. Brand Usage | Clarifies whether Kokonut identity, name, assets, or public channels are involved. |
| H. Financial Implications | Shows treasury impact, payment schedule, ongoing costs, or financial return. |
| I. Success Metrics | Defines how completion and impact will be judged. |
| J. Next Steps | Converts approval into action with owners and deadlines. |
***
## What makes a proposal passable
| Weak proposal | Strong proposal |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| "Fund our farm." | "Disburse \$18,000 in three milestones to install irrigation, prepare 2,000 m² of beds, and plant short-cycle crops by a specific date." |
| "Build an MRV tool." | "Pay \$1,500 for an MRV agent proof of concept that converts three farm events into valid payloads and submits test records." |
| "Partner with this project." | "Approve a 12-month co-funding partnership with named deliverables, value exchange, revocation conditions, and quarterly check-ins." |
| "Improve the Framework." | "Add an optional `drone_imagery_cid` field to the MRV schema with a non-breaking migration plan and docs PR deadline." |
***
## Farm Funding Proposal
Use this template for new farm launches, farm expansions, infrastructure upgrades, or major farm phase transitions.
Farm funding proposals are highly sensitive because they move treasury capital into real-world operations. They should include land details, operator accountability, budget, disbursement milestones, MRV commitments, SDG alignment, and revenue assumptions.
```markdown theme={null}
# [PROPOSAL NAME]
# Example: KDP-007 · Adelphi Phase II Expansion — Coconut Long-Cycle Planting
---
## A. Proposal Name
[Short, descriptive name. Convention: KDP-[number] · [Farm Name] — [Action]]
## B. Proposal Author(s)
- Name / alias:
- Wallet address:
- Role / relationship to farm:
- Contact channel:
## C. Proposal Team
List every person responsible for execution, reporting, or review.
| Person / wallet | Role | Responsibility |
| --- | --- | --- |
| [Name / alias] | Farm Operator | [Execution responsibility] |
| [Name / alias] | Impact Reviewer | [MRV / SDG responsibility] |
| [Name / alias] | Technical Contact | [Data Hub / Farm Registry responsibility] |
## D. Draft Start Date
[YYYY-MM-DD]
---
## E. Proposal Description
### Farm overview
| Field | Value |
| --- | --- |
| Farm ID | [url-safe slug, e.g. adelphi] |
| Project start date | [YYYY-MM-DD] |
| Location | [City, Province, Country] |
| Coordinates | [lat,lng or UTM] |
| Total land area | [X m²] |
| Agricultural area | [X m²] |
| Governance mechanism | [moloch_dao / guilds / multisig / other] |
| Operator wallet | [0x...] |
| Framework phase entering | [phase_i / phase_ii / phase_iii] |
| Data Hub link | [hub.kokonut.network/projects/N or TBD] |
### What is being funded
[2–4 paragraphs explaining exactly what the DAO is funding. Be specific about physical deliverables: crops, irrigation, nursery, biofactory, poultry, labor, tools, training, MRV onboarding, certification, or infrastructure.]
### Budget and use of funds
| Line item | Amount USD | Why it is required | Evidence / quote |
| --- | ---: | --- | --- |
| [Item] | $[N] | [Reason] | [Quote / invoice / estimate] |
| [Item] | $[N] | [Reason] | [Quote / invoice / estimate] |
| **Total requested** | **$[TOTAL]** | | |
### Crop and revenue plan
| Revenue stream | Cycle | Unit assumptions | Cycles / year | Forecast annual revenue USD |
| --- | --- | --- | ---: | ---: |
| [Crop / product] | [short / medium / long / continuous] | [Density, units, loss rate, price] | [N] | $[N] |
| [Crop / product] | [short / medium / long / continuous] | [Density, units, loss rate, price] | [N] | $[N] |
| **Total forecast** | | | | **$[TOTAL]** |
Forecast formula: [Include formula and assumptions. Clearly separate forecast from actuals.]
### Public goods allocation
[X]% of gross revenue will support: [community workshops, free seedling distribution, local education, biodiversity nursery, open data, impact reporting, etc.]
### Local problem and solution
**Problem:** [Describe the specific local economic, food security, environmental, or social problem this farm addresses.]
**Solution:** [Describe how the farm addresses it through crops, employment, biodiversity, education, MRV, and market access.]
### MRV and data commitments
- Farm Registry record: [existing link or TBD]
- Data Hub reporting cadence: [monthly / quarterly / each harvest]
- Required records: [harvests, plantings, soil observations, biodiversity records, events, attestations]
- Responsible person / Guild: [name / Guild]
---
## F. Mission Alignment
[Explain how this farm advances Kokonut's mission: reducing obstacles to agricultural development, democratizing access to real-world regenerative projects, creating public goods, and building community-owned natural assets.]
**Framework components implemented:**
- [ ] 5 Principles of Regeneration
- [ ] Common Data Schema
- [ ] MRV methodology
- [ ] SDG alignment
- [ ] EBF / impact reporting
- [ ] Public goods allocation
**SDGs addressed:**
- SDG [N]: [How this farm contributes]
- SDG [N]: [How this farm contributes]
---
## G. Brand Usage
[Describe how Kokonut Network branding will appear: on-site signage, public reports, social media, farm product labels, partner communications, grant applications, or documentation. If none, write "None at this time."]
---
## H. Financial Implications
### Total funding requested
**$[AMOUNT] USD** to be disbursed in stablecoins from the Kokonut DAO Treasury.
### Disbursement schedule
| Milestone | Amount USD | Condition for release | Evidence required |
| --- | ---: | --- | --- |
| Kickoff | $[N] | Proposal passed + operator wallet verified | Wallet confirmation |
| Infrastructure complete | $[N] | [Deliverable complete] | Photos, receipts, field record |
| First planting complete | $[N] | MRV event submitted | Farm Registry / Data Hub record |
| First harvest recorded | $[N] | Harvest record submitted | Harvest report |
| **Total** | **$[TOTAL]** | | |
### Ongoing treasury impact
[Describe expected revenue, public goods allocation, timeline to first harvest, and whether any funds return to the DAO or are reinvested locally.]
### References
- Treasury address: [DAO treasury address]
- Farm Registry record: [link once created]
- Forecast documents: [link]
- Budget evidence: [link]
---
## I. Success Metrics
### During execution
- [ ] Milestone 1 completed by [YYYY-MM-DD]
- [ ] Infrastructure installed and documented
- [ ] MRV records submitted by [cadence]
- [ ] Data Hub live within [N] days of kickoff
- [ ] Community training sessions completed: [N] sessions, [N] participants
### 12-month targets
| Metric | Target |
| --- | --- |
| Gross revenue | >= $[N] USD |
| Public goods distributed | >= $[N] USD |
| Jobs created or sustained | >= [N] positions |
| Harvest records submitted | >= [N] records |
| SDG / MRV attestations | >= [N] attestations |
| Biodiversity or soil indicators | [Target] |
---
## J. Next Steps
| Action | Owner | Deadline |
| --- | --- | --- |
| Drafting window open | [Author] | [YYYY-MM-DD] |
| Incorporate feedback | [Author] | [YYYY-MM-DD] |
| Impact Guild review | [Reviewer] | [YYYY-MM-DD] |
| Sponsor to DAOHaus | [Proposal-authorized person] | [YYYY-MM-DD] |
| Voting window | DAO Members | [YYYY-MM-DD] |
| If passed: create / update Farm Registry record | [Technical contact] | Within 7 days |
| If passed: first milestone request | [Farm operator] | Within 14 days |
| If passed: MRV onboarding | [Impact Guild] | Within 30 days |
```
***
## Guild Bounty Proposal
Use this template when a Guild Steward requests funding for scoped contributor work.
Bounty proposals should be specific, testable, and reviewable. If reviewers cannot tell whether the work is complete, the bounty is not ready.
```markdown theme={null}
# [PROPOSAL NAME]
# Example: KBP-014 · Technology Guild — MRV Agent Proof of Concept
---
## A. Proposal Name
[Short, descriptive name. Convention: KBP-[number] · [Guild Name] — [Deliverable]]
## B. Proposal Author(s)
- Name / alias:
- Wallet address:
- Guild role: [Steward / Member / Contributor]
- Contact channel:
## C. Proposal Team
| Role | Person / wallet | Responsibility |
| --- | --- | --- |
| Issuing Guild | [Technology / Impact / Communications / Governance / Finance / C&P] | [Domain owner] |
| Guild Steward | [Name + wallet] | [Sponsor / reviewer] |
| Intended contributor | [Name + wallet or TBD] | [Executor] |
| Reviewer | [Name / Guild] | [Acceptance review] |
## D. Draft Start Date
[YYYY-MM-DD]
---
## E. Proposal Description
### Bounty summary
| Field | Value |
| --- | --- |
| Bounty type | [feature / research / content / audit / design / ops / finance / governance] |
| Skill required | [Solidity, Python, writing, agronomy, design, etc.] |
| Estimated effort | [e.g. 20 hours over 2 weeks] |
| Application open | [Yes / No] |
| Assigned to | [Contributor name + wallet, or TBD] |
| Work repository / workspace | [GitHub / Drive / Forum / other] |
### Background and context
[2–3 paragraphs explaining why this work matters now. What ecosystem gap does it solve? Which farm, Guild, tool, page, proposal, or workflow depends on it?]
### Deliverable specification
| # | Deliverable | Format | Acceptance criteria |
| --- | --- | --- | --- |
| 1 | [Primary deliverable] | [Code / doc / report / design] | [Specific, testable criteria] |
| 2 | [Secondary deliverable] | [Format] | [Specific criteria] |
| 3 | Documentation / handoff | [MDX / Markdown / Loom / README] | [Merged / published / approved] |
### Out of scope
[State what this bounty does not include. This prevents scope creep and payment disputes.]
### Review process
[Who reviews the work? What evidence must be submitted? How many revision rounds are included?]
---
## F. Mission Alignment
[Connect this bounty to a specific Guild responsibility, roadmap item, farm need, MRV need, governance need, or contributor onboarding gap.]
---
## G. Brand Usage
[Explain whether the output will be published under the Kokonut brand, included in official docs, posted publicly, used in grant materials, or kept internal.]
---
## H. Financial Implications
### Total bounty amount
**$[AMOUNT] USD** to be paid in stablecoins from the Kokonut DAO Treasury.
### Payment schedule
| Milestone | Amount USD | Condition for payment |
| --- | ---: | --- |
| Kickoff | $[N] | Contributor accepts scope and posts work plan |
| Midpoint | $[N] | [Midpoint deliverable] accepted |
| Final delivery | $[N] | All acceptance criteria met |
| **Total** | **$[TOTAL]** | |
### Dispute process
If the contributor and Guild Steward disagree about completion, the Governance Guild is the first escalation point. Unresolved disputes can proceed to a DAO vote.
---
## I. Success Metrics
### During execution
- [ ] Contributor submits work plan within [N] days
- [ ] Midpoint check-in submitted on schedule
- [ ] Final delivery submitted by [YYYY-MM-DD]
- [ ] Deliverables pass review within [N] revision rounds
### 30-day evaluation
| Metric | Target |
| --- | --- |
| Primary deliverable utility | [Target] |
| Adoption / usage | [Target] |
| Quality / reliability | [Target] |
| Documentation completeness | [Target] |
---
## J. Next Steps
| Action | Owner | Deadline |
| --- | --- | --- |
| Drafting window open | [Author] | [YYYY-MM-DD] |
| Guild review | [Guild Steward] | [YYYY-MM-DD] |
| Select contributor if open | [Guild Steward] | [YYYY-MM-DD] |
| Sponsor to DAOHaus if treasury vote required | [Proposal-authorized person] | [YYYY-MM-DD] |
| Kickoff payment | [Guild Steward / DAO] | After pass |
| Work period | [Contributor] | [YYYY-MM-DD] |
| Final review | [Reviewer] | [YYYY-MM-DD] |
| Final payment | [Guild Steward / DAO] | On acceptance |
| Guild Points awarded | [Guild Steward] | Within 7 days |
```
***
## Framework Upgrade Proposal
Use this template when changing the Kokonut Framework, Common Data Schema, MRV methodology, development phases, governance rules, impact reporting, or technical standards.
Framework upgrades are highly sensitive because they can affect every farm, every data pipeline, every MRV agent, and every future proposal that depends on the Framework.
```markdown theme={null}
# [PROPOSAL NAME]
# Example: KFP-003 · Framework Upgrade — Add Drone Imagery CID to MRV Remote Sensing Schema
---
## A. Proposal Name
[Short, descriptive name. Convention: KFP-[number] · Framework Upgrade — [Component]: [Change]]
## B. Proposal Author(s)
- Name / alias:
- Wallet address:
- Guild affiliation:
- Contact channel:
## C. Proposal Team
| Person / wallet | Role | Responsibility |
| --- | --- | --- |
| [Name] | Schema author | [Design / spec] |
| [Name] | Technical reviewer | [API / agent review] |
| [Name] | Impact reviewer | [MRV / SDG review] |
| [Name] | Documentation owner | [Docs PR] |
## D. Draft Start Date
[YYYY-MM-DD]
---
## E. Proposal Description
### Change summary
| Field | Value |
| --- | --- |
| Framework component | [Common Data Schema / MRV Payload / Development Phases / Governance / EBF / Docs] |
| Change type | [additive / modification / deprecation / removal] |
| Backward compatible | [Yes / No / Partial] |
| Farms affected | [List farm IDs or "All registered farms"] |
| Agents affected | [List agent names or "None"] |
| API version impact | [None / Minor / Major] |
### Current state
[Describe what the Framework says today. Quote or link the current rule, field, schema, or process.]
~~~
// Current field / rule / process
[Paste current definition]
~~~
### Proposed change
[Describe exactly what changes. If schema-related, show before and after. If process-related, show old and new language.]
~~~
// Before
[Current version]
// After
[Proposed version]
~~~
### Rationale
[Explain why the change is needed. Reference a concrete data-quality issue, farm operation, MRV gap, agent integration, governance dispute, or documentation problem.]
### Compatibility and migration impact
Assess impact on:
- Registered farms
- Farm Registry API
- Data Hub
- MRV agents
- EAS attestation schemas
- Documentation
- Partner tools
### Migration plan
[Required if backward compatible = No or Partial.]
| Phase | Action | Owner | Timeline |
| --- | --- | --- | --- |
| Deprecation notice | Announce old field / rule as deprecated | [Author] | On proposal pass |
| Dual-write period | API accepts both formats | Technology Guild | [N weeks] |
| Farm migration | Farm operators update submissions | Farm operators | By [YYYY-MM-DD] |
| Agent migration | Agents update capability manifests | Agent operators | By [YYYY-MM-DD] |
| Cutover | Old format no longer accepted | Technology Guild | [YYYY-MM-DD] |
---
## F. Mission Alignment
[Explain how this change makes Kokonut more modular, measurable, composable, credible, or scalable.]
---
## G. Brand Usage
[Explain how public docs, API references, partner materials, dashboards, or communications must change.]
---
## H. Financial Implications
### Treasury disbursement
**$[AMOUNT] USD** — or — **No treasury disbursement required.**
If funding is needed:
| Work item | Amount USD | Assigned to |
| --- | ---: | --- |
| Implementation | $[N] | [Name / Guild] |
| Testing | $[N] | [Name / Guild] |
| Documentation | $[N] | [Name / Guild] |
| Migration support | $[N] | [Name / Guild] |
| **Total** | **$[TOTAL]** | |
### Ongoing cost / savings
[Describe ongoing effect: reduced manual work, higher data quality, new maintenance burden, partner dependency, or infrastructure cost.]
---
## I. Success Metrics
### During implementation
- [ ] Spec approved and merged
- [ ] API / tool update deployed to staging if needed
- [ ] At least one test record validates against the new rule / schema
- [ ] Documentation updated
- [ ] No open critical bugs after [N] days
### 30-day evaluation
| Metric | Target |
| --- | --- |
| Affected farms migrated | [Target] |
| Affected agents updated | [Target] |
| Error rate / validation failures | <= baseline |
| Data quality improvement | [Specific target] |
---
## J. Next Steps
| Action | Owner | Deadline |
| --- | --- | --- |
| Draft posted | [Author] | [YYYY-MM-DD] |
| Technical review | [Technology Guild] | [YYYY-MM-DD] |
| Impact / governance review | [Relevant Guild] | [YYYY-MM-DD] |
| Affected operators notified | [Author / Comms Guild] | [YYYY-MM-DD] |
| Sponsor to vote | [Proposal-authorized person] | [YYYY-MM-DD] |
| If passed: implementation begins | [Owner] | Within 7 days |
| If passed: docs PR merged | [Owner] | Within 7 days |
| If migration: cutover completed | [Owner] | [YYYY-MM-DD] |
```
***
## Partnership Proposal
Use this template when Kokonut creates a formal external relationship with a protocol, funder, research institution, local cooperative, farm operator network, public goods program, or ecosystem partner.
A partnership proposal is required when Kokonut uses another organization's brand, makes commitments on behalf of the DAO, shares data, grants privileged access, receives or provides funds, or creates a relationship lasting more than 90 days.
```markdown theme={null}
# [PROPOSAL NAME]
# Example: KPP-005 · Partnership — Public Nouns x Kokonut Network: Adelphi Phase III Co-Funding
---
## A. Proposal Name
[Short, descriptive name. Convention: KPP-[number] · Partnership — [Partner] x Kokonut: [Purpose]]
## B. Proposal Author(s)
- Name / alias:
- Wallet address:
- Relationship to partner:
- Contact channel:
## C. Proposal Team
| Role | Person / wallet | Responsibility |
| --- | --- | --- |
| Lead negotiator | [Name] | [Relationship owner] |
| C&P Guild Steward | [Name] | [Guild sign-off] |
| Legal reviewer if applicable | [Name or None] | [Legal / MOU review] |
| Technical contact if applicable | [Name or None] | [Integration review] |
## D. Draft Start Date
[YYYY-MM-DD]
---
## E. Proposal Description
### Partner overview
| Field | Value |
| --- | --- |
| Partner name | [Full name] |
| Partner type | [protocol / institution / farm / funder / cooperative / DAO] |
| Website | [URL] |
| Wallet / ENS | [0x... or name.eth, if applicable] |
| Chain(s) | [If relevant] |
| Partnership duration | [12 months / single event / indefinite / other] |
| Renewal mechanism | [Annual vote / automatic unless terminated / new proposal required] |
### What this partnership is
[2–4 paragraphs explaining who the partner is, how the relationship started, what opportunity it creates, what each side will do, and what the working relationship looks like.]
### Value exchange
**What Kokonut provides:**
| Contribution | Description |
| --- | --- |
| [Contribution] | [Description] |
| [Contribution] | [Description] |
**What Kokonut receives:**
| Contribution | Description |
| --- | --- |
| [Contribution] | [Description] |
| [Contribution] | [Description] |
### Integration requirements
[If technical: describe API, smart contract, data, dashboard, agent, or attestation requirements. If none, write "No technical integration required."]
### Revocation conditions
This partnership can be terminated if:
- [ ] Partner fails to deliver agreed contributions
- [ ] Partner misuses Kokonut brand or represents itself inaccurately
- [ ] Partner acts against Kokonut's manifesto or community-first values
- [ ] Technical or data-sharing risk becomes unacceptable
- [ ] DAO passes a termination proposal
Either party may initiate termination by posting notice to the designated governance venue. Termination takes effect after [14 / 30] days unless the DAO votes otherwise.
---
## F. Mission Alignment
[Explain how the partnership advances Kokonut's mission, supports farms, strengthens public goods, improves infrastructure, expands capital access, or increases credible impact reporting.]
Specifically address:
- Shared values
- Expected benefits to farms and contributors
- Precedent for future partnerships
- Reputational risks
---
## G. Brand Usage
### Kokonut use of partner brand
[Where and how Kokonut may use partner name, logo, data, or public references.]
### Partner use of Kokonut brand
[Where and how partner may use Kokonut name, logo, data, or public references. State limits clearly.]
---
## H. Financial Implications
### Treasury disbursement
**$[AMOUNT] USD** — or — **No treasury disbursement required.**
If funds move:
| Line item | Amount USD | Condition for release |
| --- | ---: | --- |
| [Line item] | $[N] | [Condition] |
| [Line item] | $[N] | [Condition] |
| **Total** | **$[TOTAL]** | |
### Expected value to Kokonut
[Describe grant funding, revenue share, cost reduction, in-kind services, technical integrations, research outputs, community reach, or other measurable value.]
### Jurisdiction / legal note
[If any legal entity is involved, name jurisdiction and whether a contract, MOU, grant agreement, or data-sharing agreement will accompany the DAO vote.]
---
## I. Success Metrics
### During the partnership
- [ ] Value exchange items delivered on schedule
- [ ] No unresolved brand usage disputes
- [ ] Technical integration live by [date], if applicable
- [ ] Quarterly check-ins completed
- [ ] Public update posted by [cadence]
### End-of-term evaluation
| Metric | Target |
| --- | --- |
| Kokonut commitments delivered | 100% |
| Partner commitments delivered | 100% |
| Partnership-specific outcome | [Target] |
| Community sentiment / objections | [Target] |
| Renewal recommendation | Published before term end |
---
## J. Next Steps
| Action | Owner | Deadline |
| --- | --- | --- |
| Draft posted | [Author] | [YYYY-MM-DD] |
| Partner reviews draft | [Lead negotiator] | [YYYY-MM-DD] |
| C&P Guild review | [Guild Steward] | [YYYY-MM-DD] |
| Legal / technical review if needed | [Reviewer] | [YYYY-MM-DD] |
| Feedback incorporated | [Author] | [YYYY-MM-DD] |
| Sponsor to vote | [Proposal-authorized person] | [YYYY-MM-DD] |
| If passed: agreement signed if applicable | [Owner] | Within 14 days |
| If passed: public announcement | [Communications Guild] | Within 7 days |
| First check-in scheduled | [Lead negotiator] | Within 30 days |
```
***
## After your proposal passes
A passed proposal is not the end of governance. It creates responsibility.
| Proposal type | First post-pass action | Ongoing reporting |
| ----------------- | -------------------------------------------------- | --------------------------------------------------------------- |
| Farm Funding | Create or update Farm Registry / Data Hub records | Milestone reports, MRV events, harvest, and impact data |
| Guild Bounty | Confirm contributor, payment wallet, and work plan | Deliverable reviews, Guild Points, final handoff |
| Framework Upgrade | Open implementation and documentation PRs | Migration status, validation checks, operator support |
| Partnership | Confirm written acknowledgment or agreement | Quarterly check-ins, value exchange updates, and renewal review |
If a passed proposal cannot be executed as written, post an update immediately. Material changes to the budget, scope, timeline, or obligations may require an amended proposal.
***
## Related governance pages
The full process for drafting, review, voting, grace period, execution, and governance protections.
The on-chain treasury engine where treasury moves and token proposals are executed.
The contribution layer, where Guilds review work, issue bounties, and route proposals.
Start contributing before you submit a formal proposal.
# Welcome to the Kokonut Ecosystem
Source: https://kokonut.network/home/landing
A community-governed Web3 cooperative growing regenerative farms, living ecosystems, and community wealth — starting with Adelphi in the Dominican Republic.
# Grow real regenerative farms with a community-governed Web3 cooperative.
Kokonut Network connects Web3 communities, regenerative builders, and capital allocators to live syntropic farms. Governance tokens are backed 1:1 by real coconut trees. Farm activity is monitored through public MRV, on-chain attestations, and a repeatable Framework designed to help the next farm launch faster than the first.
Free to explore. No capital required to contribute. DAO walkthroughs are available for partners and capital allocators.
PN #69
public goods funded
***
## What Kokonut is building
Grassroots farmers control less than 10% of the global coconut market — not because their land is unproductive, but because they lack access to capital, coordination tools, and transparent governance structures.
Kokonut Network closes this gap with a **blockchain-based cooperative for regenerative agriculture**. The DAO coordinates capital. The Framework standardizes farm operations. MRV systems publish verifiable ecological and production data. Guilds reward the people improving the system.
The result is a regenerative value loop: capital funds farms, farms grow living assets, farm events become public data, revenue flows back to the network, and the model repeats as trees are replanted and new farms join.
***
## Choose your path into Kokonut
Understand the mission, problem, solution, governance model, and why Kokonut exists.
Explore the live farm in Monte Plata: crops, biodiversity, infrastructure, harvest forecasts, SDG alignment, and MRV records.
Agronomists, ReFi builders, researchers, community organizers, and technical contributors can plug into the work already underway.
Use the public docs, deployed contracts, Farm Registry primitives, open repositories, and AI agent architecture.
Learn the repeatable methodology every farm runs on: data schema, development phases, capital flows, and impact measurement.
See how governance tokens, Loot, Guild Points, proposals, rage-quit, and treasury protections work.
***
## Adelphi — live proof this model works
Adelphi is Kokonut Network's first live syntropic farm: a women-led, community-first agricultural project in Gonzalo, Monte Plata, Dominican Republic. It is not just a concept deck. It is a working farm — already funded, already growing, already monitored, and already publishing data.
🌱
Adelphi — Live Farm
Active
Funded · Public Nouns #69
Live MRV
Location
Gonzalo, Monte Plata
Dominican Republic
Total area
15,725 m²
13,838 m² agro-ecological garden
Led by
Yanny & Neury Hernández
Sisters · Women-led · Community-first
Live data
Harvest, MRV & farm records
What's growing
🥬 Lettuce · 48,450/harvest
🌿 Passion fruit · 560 plants
🥥 Coconut · 96 trees
🐓 110 free-range hens
🌳 Native & endangered species nursery
How it's verified
Landsat 8 + Sentinel satellites
NDVI · NDRE · MSAVI indices
Drone MRV + soil probes
Silvi GPS per-plant tracking
EAS attestations
***
## How the model works
DAO members tribute stablecoins to the treasury. Governance tokens are minted through proposal and backed 1:1 by real coconut trees.
Approved farms deploy the Kokonut Framework: syntropic agriculture, farmer training, infrastructure, standardized records, and public reporting.
Satellite data, drone imagery, field logs, soil readings, harvest records, and EAS attestations make farm progress publicly auditable.
Farm revenue flows back to token holders, contributors, and local communities. Trees are replanted. The cooperative continues.
> **The Kokonut Framework is the repeatable piece.** Every farm runs the same playbook — common data schema, development phases, MRV methods, and eight forms of capital measured. New farms slot in without reinventing the model. [Read the Framework →](/kokonut-framework/Introduction)
***
## Built to reduce trust gaps
The Framework, governance mechanics, farm pages, and contribution paths are public. The docs are free to read, fork, improve, and build on.
Governance runs through proposals, voting, treasury controls, and rage-quit protections. No admin can remove a member or override the DAO.
You do not need capital to start. Contributors can join Guilds, improve the Framework, build tools, and earn Guild Points through verified work.
**Kokonut is not asking you to trust a pitch deck.** Start with the docs, inspect the live farm data, join the Discord, or contribute to the public repository before becoming a DAO member.
***
## Join over 3,000 members building this
[Kokonut Discord](https://link.kokonut.network/discord) is where builders, farmers, researchers, token holders, and community members coordinate. It is open — come as you are.
Agronomists, researchers, ReFi builders, developers, community organizers, and capital allocators can all plug into the ecosystem. Start with the [Open Collaboration Invitation](/ecosystem-wiki/open-collaboration-invitation).
We share progress, experiments, and ecosystem updates openly on [X / Twitter](https://x.com/KokonutNetwork). Watch what real cooperative development looks like in real time.
Improving a page, proposing a data standard, or submitting an MRV methodology update can earn Guild Points and, over time, Loot tokens from the DAO. [View the repo →](https://github.com/wasalo/Kokonut-Public-Site)
If you are a partner, funder, capital allocator, or serious contributor, [book a call](https://link.kokonut.network/meeting) and we will walk you through the DAO, Adelphi, and the next replication opportunities.
**This documentation is itself a public good.** Everything here — the Framework, governance mechanics, MRV methodology, and farm data — is free to read, fork, and build on. If you improve something, [submit a pull request](https://github.com/wasalo/Kokonut-Public-Site) or propose a change through the [Governance Framework](/ecosystem-wiki/the-kokonut-dao/governance-framework).
# Introduction
Source: https://kokonut.network/kokonut-framework/Introduction
The operating system Kokonut uses to make regenerative farms comparable, fundable, governable, and verifiable across land, communities, data, and capital.
# The Kokonut Framework turns regenerative farms into verifiable community assets.
The Kokonut Framework is the operating system behind Kokonut Network. It gives every farm a shared structure for onboarding, governance, operations, MRV, impact reporting, and capital allocation.
Without the Framework, every new farm has to invent its own coordination logic. DAO members cannot compare funding proposals. Impact claims stay self-reported. Farm data cannot be aggregated across sites. Contributors do not know where their work fits.
The Framework solves this by making farms **comparable, fundable, governable, and verifiable** under one shared system — while still allowing each farm to adapt to its own land, crops, community, and market.
Built for farm founders, DAO members, contributors, researchers, grant reviewers, capital allocators, and builders who need regenerative agriculture to be measurable and repeatable.
13
Common Data Schema fields
4
farm development phases
5
regeneration principles
MRV
public impact evidence
EAS
on-chain attestations
The Framework is open source at [wasalo/kokonut-framework](https://github.com/wasalo/kokonut-framework) and is already deployed through [Adelphi](/ecosystem-wiki/kokonut-farms/adelphi/summary), Kokonut Network's first live syntropic farm in Monte Plata, Dominican Republic.
***
## What the Framework does
The Framework is not a single document, scorecard, token, or smart contract. It is a coordination system that connects farm reality to governance decisions and verifiable records.
| What it standardizes | Why it matters | Where to go deeper |
| --------------------- | ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Farm onboarding | Every farm enters the network with comparable baseline data | [Common Data Schema](/kokonut-framework/framework-components/common-data-schema) |
| Farm development | Farms move through shared phases instead of ad hoc milestones | [Development Phases](/kokonut-framework/development-phases/phase-i) |
| Regenerative practice | Operators have clear ecological principles to follow | [5 Principles of Regeneration](/kokonut-framework/framework-components/framework-features/5-principles-of-regeneration) |
| Impact measurement | Farm claims become evidence instead of marketing | [MRV Methodology](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification) |
| Value accounting | Natural, social, financial, and cultural values can be tracked together | [8 Forms of Capital](/kokonut-framework/framework-components/framework-features/8-forms-of-capital) |
| Governance decisions | DAO members can evaluate farms using shared information | [DAO Architecture](/ecosystem-wiki/the-kokonut-dao/dao-layers) |
The Framework makes farms more legible and comparable. It does not eliminate agricultural, market, governance, weather, or execution risk. Those risks must be measured, reported, and improved through MRV and governance review.
***
## Who the Framework is for
Use the Framework to document land, crop plans, governance needs, revenue assumptions, public goods allocation, and MRV commitments before requesting support.
Use the Framework to compare farm proposals, evaluate milestones, review risks, and decide whether treasury support is justified.
Use the Framework to understand what work is needed across technology, impact, finance, governance, communications, and partnerships.
Use the Framework to inspect how farm activity maps to impact evidence, SDGs, ecological benefits, and risk scoring.
Use the Framework to build tools around common data fields, Farm Registry events, MRV payloads, EAS attestations, and dashboards.
Use the Framework to understand how productive land, impact evidence, and governance reporting can become institutionally legible over time.
***
## How the Framework works
```mermaid theme={null}
flowchart TD
A["Farm enters the network"] --> B["Common Data Schema"]
B --> C["Stakeholder sense-making"]
C --> D["Development phases"]
D --> E["On-ground regenerative operations"]
E --> F["MRV workflow"]
F --> G["IPFS records + EAS attestations"]
G --> H["Kokonut Hub + annual reports"]
H --> I["DAO funding and governance decisions"]
I --> J["New farms and improved operations"]
J --> B
```
The loop matters because regeneration is not a one-time funding event. A farm needs ongoing feedback between land, people, data, capital, and governance.
The Framework gives Kokonut a shared way to ask:
* What is this farm trying to do?
* Who benefits from it?
* What evidence proves progress?
* What risks remain?
* What capital or support is needed next?
* What should the DAO learn before funding the next farm?
***
## The three Framework pillars
The Framework is organized into three operational pillars. Each pillar answers a different trust question.
| Pillar | Core question | Primary output |
| ---------------------------- | ------------------------------------------------------------------------------------------- | ----------------------------------------------------- |
| Stakeholder Sense-Making | Can this farm be understood, compared, and governed? | Shared baseline data and legitimacy |
| On-Ground Solution Variables | Can this farm implement regenerative operations in its own context? | Farm-specific execution under shared standards |
| Operational Variables | Can farm activity become useful evidence for capital, governance, and institutional review? | MRV records, risk profiles, reports, and attestations |
### 1. Stakeholder Sense-Making
This is the entry point. Before capital moves, the network needs shared context.
Every farm begins with the [Common Data Schema](/kokonut-framework/framework-components/common-data-schema): 13 fields covering project date, land size, location, governance mechanism, revenue streams, token allocation, public goods allocation, and narrative context.
This schema acts as the minimum viable onboarding contract between a farm and the network. Once populated, a farm can be evaluated by DAO members, queried by the Data Hub, and prepared for on-chain attestation.
The pillar also maps the farm's needs and wants into the [Pillars of Value](/kokonut-framework/framework-components/pillars-of-value), helping the network understand what the project creates, who benefits, how much value is produced, what contribution is additional, what risk remains, and what public goods are funded.
This pillar protects the network from vague proposals. It requires clarity early, before funding, operations, or impact claims begin.
### 2. On-Ground Solution Variables
This is where the Framework becomes site-specific without becoming chaotic.
Every farm has different land, crops, founders, water conditions, community needs, and market access. The Framework does not erase those differences. It gives them a shared reporting structure.
The same logic can govern:
* Adelphi in Monte Plata;
* a future Kokonut farm on another chain;
* a partner farm with a different crop mix;
* a community project with different governance needs.
Each farm can remain unique while still producing comparable outputs: land data, crop cycles, milestones, MRV records, governance reports, public goods allocation, and impact evidence.
This is how Kokonut avoids one-off projects. The farm can adapt locally, while the network can still learn globally.
### 3. Operational Variables
This is where farm activity becomes capital-relevant evidence.
The Framework connects operations to the [MRV stack](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification), the Farm Registry API, IPFS/Filecoin records, EAS attestations, annual reports, and public dashboards.
Operational data can include:
| Data type | Example evidence | Why it matters |
| --------------------- | ------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| Farm events | Planting, harvest, infrastructure, training, field logs | Shows whether the farm is active |
| Ecological indicators | NDVI, NDRE, MSAVI, soil moisture, soil temperature, and electrical conductivity | Shows whether land conditions are changing |
| Harvest records | Crop cycle actuals, losses, sales, and forecast updates | Shows whether revenue assumptions are improving or failing |
| Community records | jobs, training sessions, local participation, public goods allocation | Shows whether community value is real |
| Attestations | EAS records tied to structured payloads | Makes evidence public, timestamped, and harder to alter |
This pillar is what turns regenerative agriculture from a narrative into a reviewable evidence system.
***
## In practice: Adelphi
Adelphi is the first live proof of the Kokonut Framework.
It shows the full stack working on real land:
| Framework component | Adelphi implementation |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------- |
| Farm onboarding | Registered farm with land, founders, location, governance, crop, and public goods data |
| Development phases | Planning, production, regeneration, and continuous MRV operating as one farm lifecycle |
| Regenerative principles | Syntropic plots, biodiversity restoration, poultry integration, biochar, cover crops, and native species propagation |
| MRV workflow | Satellite monitoring, soil probes, field records, harvest data, and per-plant geospatial records |
| Public evidence | Data visible through the Kokonut Hub and tied to MRV reporting workflows |
| DAO coordination | Public goods funding, governance visibility, contributor routing, and future replication learning |
Adelphi matters because it makes the Framework inspectable. It is not only a theory about how regenerative farms could be coordinated. It is a working case where land, people, data, funding, and impact reporting are connected.
[Explore Adelphi →](/ecosystem-wiki/kokonut-farms/adelphi/summary)
***
## What the Framework helps prevent
The Framework exists because regenerative agriculture often fails at the coordination layer, not only the land layer.
| Failure mode | How the Framework responds |
| -------------------------------------------- | ----------------------------------------------------------- |
| Every farm invents its own proposal format | Common Data Schema and proposal templates |
| Funders cannot compare projects | Shared fields, phases, risks, and milestones |
| Impact claims are vague | MRV workflow and public evidence records |
| Governance decisions depend on trust alone | DAO review, funding milestones, and verifiable reporting |
| Ecological work is disconnected from finance | Harvest actuals, risk profiles, and public goods allocation |
| Knowledge is trapped in one farm | Standardized documentation that future farms can reuse |
The Framework does not guarantee success. It creates the conditions for better decisions, better evidence, and better iteration.
***
## What the Framework makes possible
DAO members can compare farms by using shared fields, phases, risks, metrics, and evidence, rather than relying on narrative alone.
Farm proposals can include clear budgets, milestone gates, public goods allocation, MRV requirements, and reporting duties.
Farm progress can be evaluated against approved plans, contributor work, DAO proposals, and Framework standards.
MRV records, IPFS/Filecoin storage, EAS attestations, and public dashboards make the impact easier to inspect.
Standardized data provides a cleaner foundation for analysis, recommendations, alerts, and reporting for humans and AI agents.
Future farms can reuse the coordination system while adapting to their own land, climate, crops, and community.
***
## How to use this section
If you are new to the Framework, start here:
Read the [Common Data Schema](/kokonut-framework/framework-components/common-data-schema) to understand the 13 fields every farm must provide.
Read the [Development Phases](/kokonut-framework/development-phases/phase-i) to see how farms move from planning to production, consolidation, and continuous MRV.
Read the [5 Principles of Regeneration](/kokonut-framework/framework-components/framework-features/5-principles-of-regeneration) to see the agronomic principles behind Kokonut farms.
Read the [Pillars of Value](/kokonut-framework/framework-components/pillars-of-value) and [8 Forms of Capital](/kokonut-framework/framework-components/framework-features/8-forms-of-capital) to understand how Kokonut tracks more than financial returns.
Read [Measurement, Reporting & Verification](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification) to see how farm activity becomes public evidence.
***
## Navigate the Framework
The 13 fields every farm must populate before it can be evaluated, compared, and tracked.
The value model behind Kokonut: What, Who, How Much, Contribution, Risk, and Public Goods.
The agronomic principles behind cover crops, biodiversity, animal integration, soil health, and perennial systems.
The broader capital model: Natural, Financial, Social, Human, Material, Intellectual, Cultural, and Health capital.
The four-phase lifecycle follows from planning to production, consolidation, and continuous MRV.
How farm activity becomes structured payloads, public records, EAS attestations, and impact reports.
The first live farm where the Framework is being applied, tested, measured, and improved.
Developer primitives for Farm Registry data, MRV events, attestations, and agent-ready infrastructure.
# PHASE I: Planning and Preparation
Source: https://kokonut.network/kokonut-framework/development-phases/phase-i
How Kokonut farms become funding-ready, proposal-ready, and MRV-ready before production begins.
# Phase I turns a farm idea into a DAO-ready operating plan.
Phase I is the foundation of every Kokonut Framework farm. It is the stage where a site becomes legible: the land is mapped, the local problem is documented, the crop strategy is designed, the budget is prepared, the team is trained, and the MRV baseline is established before active production begins.
The purpose is simple: **do not deploy farm operations until the DAO, operators, contributors, and MRV stack can understand what is being funded and how progress will be verified.**
Use this page when preparing a farm funding proposal, reviewing a new farm, establishing an MRV baseline, or deciding whether a project is ready for Phase II.
Phase I is not a formality. A farm with incomplete data, unclear local demand, missing budgets, untrained operators, or no MRV baseline should not be treated as ready for production funding.
***
## What Phase I produces
| Output | Why it matters | Where it is used next |
| --------------------- | ------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- |
| Complete farm record | Populates the 13 Common Data Schema fields that make the farm comparable and reviewable | Farm Registry, DAO review, Data Hub, agent workflows |
| Farm Funding Proposal | Turns the farm plan into a governance-ready Kokonut Development Proposal | Charmverse drafting and DAOHaus voting |
| MRV baseline | Establishes pre-production evidence for soil, imagery, biodiversity, site layout, and community context | MRV pipeline, EAS attestations, annual impact reporting |
| Crop and revenue plan | Defines short, medium, and long-cycle production assumptions | Harvest forecast, budget review, market strategy |
| Infrastructure plan | Defines what must be built before production can begin | Phase II milestone disbursements and operator planning |
| Training plan | Prepares the team to run syntropic farming, bio-inputs, MRV, and market operations | Human capital tracking and production readiness |
Phase I can include planning, assessment, proposal development, and readiness work. The key boundary is that active production and major operational milestones should not begin until the farm has enough data, training, infrastructure planning, funding approval, and MRV baseline records to be evaluated responsibly.
***
## Phase I readiness loop
```mermaid theme={null}
flowchart TD
A["Site identified"] --> B["Data collection and diagnosis"]
B --> C["Common Data Schema populated"]
C --> D["Crop plan and infrastructure design"]
D --> E["MRV baseline established"]
E --> F["Team training completed"]
F --> G["Farm Funding proposal drafted"]
G --> H["DAO review and vote"]
H --> I{"Approved?"}
I -->|No| J["Revise plan, budget, evidence, or team readiness"]
J --> G
I -->|Yes| K["Phase I completion record"]
K --> L["Advance to Phase II production"]
L --> M["Continuous MRV and milestone reporting"]
```
The loop protects the farm, the DAO, and the community. It forces assumptions to become records before they become spending decisions.
***
## The five Phase I workstreams
Phase I begins by documenting the farm site and its context: soil, climate, water, biodiversity, community needs, market access, and local economic conditions.
**What to collect:**
* **Soil:** texture, organic matter, pH, drainage, compaction, microbial activity, and initial probe readings
* **Climate:** rainfall, temperature ranges, drought frequency, seasonal extremes, and planting windows
* **Water:** surface water, groundwater, irrigation source quality, watershed position, and erosion risk
* **Biodiversity:** existing trees, at-risk species, native species, pest pressure, and habitat conditions
* **Economic context:** crop demand, local price benchmarks, buyers, distribution channels, and labor availability
* **Community context:** who the farm serves, what problem it addresses, and how local participation will happen
**Tools that can be used:**
* Drone mapping for orthomosaic imagery and elevation models
* QGIS for slope, drainage, boundary, and vegetation analysis
* GPS registration for farm boundaries, trees, species, and production zones
* Soil probes for baseline electrical conductivity, volumetric water content, temperature, and moisture conditions
* Local interviews and market research for community demand and buyer validation
**At Adelphi:** the team documented coordinates in Monte Plata, generated a 3D orthomap, established a species GeoNode, recorded native species, and used local climate and soil conditions as the basis for crop selection.
**Schema fields started:** `project_date`, `project_location`, `land_size`, `forecasted_budget`, `local_problem`, `proposed_solution`.
Crop selection turns the diagnosis into a productive design. The goal is not to pick the most profitable crop in isolation; it is to design a syntropic system that produces food, builds soil, protects biodiversity, and generates revenue across multiple time horizons.
**Selection criteria:**
* **Agro-ecological fit:** crops match the farm's soil, rainfall, heat, water, slope, and disease conditions
* **Syntropic compatibility:** crops occupy different strata and support each other across time
* **Revenue timing:** short-cycle crops generate early cash flow while medium and long-cycle crops establish
* **Biodiversity value:** species support pollinators, habitat, nitrogen cycling, pest balance, or native conservation
* **Community and market demand:** crops have buyers, local use, or direct food-access value
**At Adelphi:** lettuce was selected as a short-cycle cash-flow crop; passion fruit and Indian yam support medium-cycle production; coconut anchors the long-cycle model; native and at-risk fruit species extend biodiversity and nursery value.
**Schema fields strengthened:** `revenue_streams`, `target_market`, `project_summary`.
Infrastructure planning defines what must be in place before production can run safely and consistently. This includes both physical systems and evidence systems.
**Core infrastructure planning areas:**
* **Biofactory:** biochar production, humic acids, organic urea, composting, and other biological inputs
* **Water and erosion management:** terraces, drainage, ground cover, irrigation, tanks, pumps, and water monitoring
* **Energy and utilities:** electricity, lighting, tool storage, data collection equipment, and connectivity
* **Poultry or animal integration:** housing, forage, manure handling, rotation plans, and animal welfare
* **Community infrastructure:** training space, meeting area, visitor flow, and safety requirements
* **MRV infrastructure:** soil probes, GPS records, data logging workflows, image baselines, and dashboard connections
**At Adelphi,** Public Nouns Proposal #69 helped fund critical infrastructure, including the biofactory, poultry system, manure-processing station, education gazebo, and monitoring equipment.
**MRV milestone:** pre-production baseline readings should be captured before soil amendments, crop planting, or infrastructure changes make later comparison difficult.
A farm is not Phase II-ready until the operators understand the practices they are expected to run and the data they are expected to report.
**Training curriculum:**
* Syntropic planting, strata design, species interactions, and the 5 Principles of Regeneration
* Biochar production, humic acid extraction, organic urea preparation, and safe input handling
* Soil management, cover crop maintenance, erosion monitoring, and water retention practices
* MRV logging, field observations, image capture, soil probe checks, and dashboard updates
* Harvest handling, local pricing, market relationships, and public goods allocation reporting
* Proposal accountability, milestone reporting, and community communication
**At Adelphi:** Yanny and Neury Hernández and the farm team received training across regenerative production, bio-inputs, syntropic bed preparation, and field data logging.
**Framework connection:** training is part of Human Capital and should be documented with attendance, role assignments, and, where possible, pre- and post-skill assessments.
Soil preparation is the first operational test of the farm's regenerative design. It should establish healthy beds without destroying the soil biology that the farm is trying to build.
**Core preparation practices:**
* **Biochar incorporation:** use locally appropriate biomass and controlled pyrolysis, then apply biochar based on crop-bed design and soil needs
* **Organic fertility:** apply biological inputs such as compost, humic acids, organic urea, or other approved inputs
* **Living cover:** establish ground cover and edge vegetation to prevent bare soil and erosion
* **Minimal disturbance:** form beds without deep mechanical tillage when possible
* **Baseline comparison:** record soil readings before and after preparation, so future changes can be evaluated
**At Adelphi:** bamboo-derived biochar, beard grass cover, terraced edges, soil probe readings, and prepared crop beds established the amended baseline for Phase II.
**MRV milestone:** post-preparation soil readings serve as the starting point for continuous Phase II measurements.
***
## Phase I readiness
Phase I is complete when the farm can answer five questions with evidence.
| Readiness question | Completion evidence |
| --------------------------------- | ----------------------------------------------------------------------------------- |
| Is the farm legible? | All 13 Common Data Schema fields are complete and internally consistent |
| Is the proposal reviewable? | The farm Funding proposal is drafted, budgeted, and submitted for DAO review |
| Is the site measurable? | MRV baseline exists for soil, imagery, species, boundaries, and production zones |
| Is the production plan realistic? | Crop plan, infrastructure plan, market logic, and training plan are documented |
| Is the team prepared? | Operators are trained, roles are assigned, and reporting responsibilities are clear |
## Phase I completion checklist
| Criterion | How it should be verified |
| ------------------------------------------------- | ---------------------------------------------------------------------------- |
| Common Data Schema complete | Farm Registry record accepted and reviewed |
| Farm Funding proposal drafted | Proposal created in the governance drafting workspace |
| DAO approval is obtained when funding is required | Proposal passes DAO voting, and the required execution steps are completed |
| MRV baseline established | Soil, imagery, species, and site records captured before production changes |
| Infrastructure plan approved | Biofactory, water, utility, poultry, community, and MRV needs documented |
| Training completed | Operator roles, training records, and MRV logging responsibilities confirmed |
| Soil preparation complete | Baseline and post-preparation readings recorded; beds and cover established |
| Phase II trigger defined | First production milestones and reporting cadence are clear |
Do not mark Phase I complete just because the farm has a good story. Phase I is complete when the farm has enough structured data, operational planning, team readiness, and baseline evidence to move into production responsibly.
***
## What Phase I does not guarantee
Phase I reduces uncertainty, but it does not eliminate risk.
| Risk | What Phase I can do | What it cannot guarantee |
| ----------------- | ------------------------------------------------------ | ----------------------------------- |
| Agricultural risk | Test soil, water, crop fit, and site constraints | Perfect yields or no crop failure |
| Market risk | Validate target buyers and price assumptions | Stable prices or guaranteed sales |
| Execution risk | Train operators and assign responsibilities | Flawless operations after launch |
| Climate risk | Design for rainfall, erosion, drought, and water needs | Stable weather or no extreme events |
| Data risk | Establish MRV baseline and data workflows | Perfect data quality forever |
| Governance risk | Create a reviewable proposal | Automatic DAO approval |
This is why Phase I should be treated as a readiness gate, not a guarantee of success.
***
## Advancing to Phase II
Phase I completion triggers the transition into [Phase II — Production and Regeneration](/kokonut-framework/development-phases/phase-ii).
When Phase II begins, the farm moves from planning to active production: agro-ecological practices are implemented, short-cycle crops begin generating early harvest records, medium- and long-cycle crops are established, and MRV data begin to compound across crop cycles.
The farm status should be updated in the Farm Registry once all Phase I completion items have been verified. If the transition is recorded through EAS, the attestation should reference the baseline evidence, the proposal approval, and the checklist items used to justify the advancement.
MRV does not wait until the end of the farm lifecycle. It begins during Phase I with baseline evidence and continues through Phases II, III, and IV as the farm produces data, harvests, ecological observations, and public impact records.
***
## Use Phase I when...
Use Phase I to turn a promising site into a complete farm record, proposal, budget, crop plan, and MRV baseline.
Use Phase I to check whether the project is ready for DAO review or still missing evidence.
Use Phase I to capture pre-production records before planting, soil amendment, or infrastructure changes begin.
Use Phase I to confirm that the team understands syntropic farming, bio-inputs, harvest records, and field reporting.
Use Phase I to decide what must be built before the farm can run production safely and consistently.
Use Phase I as the gate that determines whether the farm is ready for production and regeneration work.
***
## Next steps
The 13 required fields that make a farm record comparable, fundable, governable, and verifiable.
The proposal format that turns Phase I outputs into a DAO-reviewable funding request.
The production phase begins after Phase I completion criteria are met.
How Phase I baselines become the beginning of Kokonut's evidence pipeline.
The regenerative practice logic that guides crop selection, soil preparation, and farm operations.
See the first live Kokonut farm and how Phase I planning became active production.
# PHASE II: Production and Regeneration
Source: https://kokonut.network/kokonut-framework/development-phases/phase-ii
How Kokonut farms move from planning into production, harvest records, soil regeneration, milestone attestations, and continuous MRV.
# Phase II turns a prepared farm into verified production.
Phase II begins when Phase I planning, training, infrastructure readiness, soil preparation, and DAO milestone conditions are complete. It is the stage where seeds go into the ground, production starts across short-, medium-, and long-cycle crops, and the farm begins generating the records that prove whether the Kokonut Framework is working.
Phase II is not only a planting stage. It is the evidence-building stage: harvest records, soil readings, vegetation signals, pest observations, water data, and milestone attestations start compounding into a public operating history.
Use this page to understand what must happen after a farm is funded and prepared, but before it can be considered consolidated, certified, or expansion-ready.
Phase II is a live operating phase, not a guaranteed return phase. Harvests, revenue, soil improvement, and certification readiness depend on execution quality, weather, water, labor, market pricing, data quality, and DAO-verified milestones.
***
## Phase II at a glance
| Question | Phase II answer |
| ----------------- | ------------------------------------------------------------------------------------------------------------- |
| When it begins | After Phase I completion, the criteria are met, and the first approved DAO milestone disbursement is released |
| Main purpose | Activate production, regeneration practices, and continuous MRV evidence |
| Typical duration | Usually 2–4 years, depending on crop mix, soil conditions, and long-cycle crop establishment |
| What it produces | First harvests, soil readings, MRV payloads, EAS attestations, revenue actuals, and annual impact reports |
| Primary risk | Production assumptions are tested against field reality |
| Completion signal | Sustained multi-cycle production with verified MRV data, not simply the passage of time |
Short-cycle, medium-cycle, and long-cycle crops are planted together so the farm can generate near-term harvests while longer-term perennial systems establish.
Crop rotation, ground cover, beneficial plant associations, poultry integration, biochar, organic inputs, and soil monitoring move from plan to daily operations.
Each planting, harvest, soil reading, and verified milestone becomes part of the farm's public operating record.
***
## How Phase II fits the development lifecycle
```mermaid theme={null}
flowchart LR
A["Phase I\nPlanning + preparation"] --> B["Phase II\nProduction + regeneration"]
B --> C["Phase III\nConsolidation + expansion"]
B --> D["Planting records"]
B --> E["Harvest records"]
B --> F["Soil + water readings"]
B --> G["Vegetation signals"]
B --> H["Milestone attestations"]
D --> I["MRV pipeline"]
E --> I
F --> I
G --> I
H --> I
I --> J["Data Hub + annual reports"]
J --> C
```
Phase I makes the farm legible. Phase II tests the plan in the field. Phase III begins only after the farm has enough verified operating history to support consolidation, certification, and expansion decisions.
[Read Phase I →](/kokonut-framework/development-phases/phase-i)
***
## What Phase II produces
| Output | Why it matters | Evidence to collect |
| -------------------------------- | -------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| First plantings | Confirms the farm has moved from planning to production | Plot records, crop type, planting date, density, operator notes |
| First harvests | Tests whether production assumptions are realistic | Harvest records, yield, loss rate, sale price, buyer/channel |
| Continuous soil readings | Shows whether regeneration practices are improving the growing environment | EC, volumetric water content, soil temperature, lab results where available |
| Agro-ecological practice records | Documents how regeneration is implemented, not just claimed | Rotation logs, cover crop logs, input records, pest observations |
| MRV events | Turns operations into structured data | Farm Registry payloads, IPFS records, EAS attestations |
| Milestone evidence | Determines whether DAO disbursements should proceed | Verified milestone completion records and reviewer notes |
| Annual impact report | Summarizes environmental, economic, social, and risk evidence | EBF report, CRISP review, Data Hub records |
Phase II is where the farm's forecast becomes testable. Forecasts should be compared against actual harvests, prices, losses, soil readings, and market conditions before being used for stronger claims.
***
## Phase II workstreams
Phase II activates the regenerative practices designed during Phase I.
**Core practices include:**
* Crop rotation to reduce pest and disease pressure
* Beneficial plant associations and companion planting
* Living ground cover between and around production beds
* Biological pest management through biodiversity and animal integration
* Organic fertility from compost, biochar, humic acids, manure processing, and crop residues
* Reduced synthetic-input dependency
**At Adelphi:** the farm applies closed-loop fertility through poultry manure, humic acids, crop beds, forage, and poultry integration. The 110-hen flock contributes eggs, manure, pest pressure management, and nutrient cycling.
**Evidence to collect:** crop cycle stage, plant health observations, pest and disease flags, input logs, water observations, field photos, and operator notes.
Phase II must show whether soil regeneration practices are improving the farm over time.
**Soil practices include:**
* Remineralization through mineral-rich amendments, where appropriate
* Biochar application and organic matter incorporation
* Humic acid and biological input application
* Reduced disturbance between crop cycles
* Continuous living cover to reduce erosion and heat stress
**At Adelphi:** biochar-mineral incorporation, humic acids, beard grass, and organic matter cycling are used to improve water retention, soil biology, and nutrient availability.
**Evidence to collect:** EC, volumetric water content, soil temperature, soil organic matter where available, photos of ground cover, input quantities, and pre/post application notes.
Phase II activates the Framework's three-cycle production strategy.
| Cycle | Role | Example crops | Evidence |
| ------------ | -------------------------------------------- | --------------------------------------------- | ------------------------------------- |
| Short cycle | Near-term harvest and cash flow | Lettuce, spinach, arugula, tomatoes, broccoli | Planting and harvest records |
| Medium cycle | Seasonal production and mid-canopy structure | Passion fruit, Indian yam, plantain, banana | Establishment and yield records |
| Long cycle | Perennial structure and long-term value | Coconut, cacao, hardwood, agroforestry trees | Tree health, survival, growth records |
**At Adelphi:** lettuce drives short-cycle production, passion fruit and Indian yam support medium-cycle output, and coconut anchors the long-cycle agroforestry system.
**Evidence to collect:** crop type, plot, planting density, cycle length, yield, loss rate, pricing, buyer/channel, and survival rates for perennial species.
Phase II is where forecasted production meets actual field performance.
Each harvest should record:
* Crop and variety
* Plot or bed
* Harvest date
* Units harvested
* Loss rate
* Units sold or distributed
* Sale price
* Buyer or distribution channel
* Public goods allocation, if applicable
**At Adelphi:** lettuce, passion fruit, coconut, and eggs should be tracked separately so the farm can distinguish short-cycle cash flow, medium-cycle production, long-cycle maturity, and continuous poultry output.
**Evidence to collect:** harvest payloads, receipts where available, field logs, buyer records, and Data Hub updates.
DAO milestone disbursements should be tied to verified events, not calendar promises.
| Milestone type | Example trigger | Reviewer question |
| ------------------ | ------------------------------------------- | ------------------------------------------------------- |
| Planting milestone | Crop beds are planted across approved zones | Was planting completed according to the approved plan? |
| MRV milestone | First data payload accepted | Is the evidence structured, complete, and inspectable? |
| Harvest milestone | First harvest submitted and reviewed | Does the record match the farm's forecast assumptions? |
| Soil milestone | Soil readings compared against baseline | Is improvement observed, uncertain, or not yet visible? |
| Impact milestone | Interim or annual report published | Are claims supported by evidence? |
**Evidence to collect:** milestone record, reviewer notes, related MRV event, attestation link, and DAO decision reference.
***
## Adelphi Phase II reference
At Adelphi, Phase II is the live proof stage. The farm is actively testing whether the Kokonut Framework can combine food production, regenerative practices, community income, MRV, and public goods allocation on real land.
| Adelphi element | Phase II role | Verification path |
| -------------------------------- | ------------------------------------------------------ | ---------------------------------------------------------- |
| Lettuce and fast-cycle crops | Early production and cash-flow test | Harvest records and loss-rate comparison |
| Passion fruit and Indian yam | Medium-cycle production bridge | Establishment logs and first harvest records |
| Coconut trees | Long-cycle agroforestry anchor | Tree health, GPS records, satellite vegetation indicators |
| Poultry system | Eggs, pest pressure management, manure, fertility loop | Poultry logs, manure/input records, egg production records |
| Biofactory and nursery | Organic inputs and biodiversity propagation | Input logs, nursery inventory, species records |
| Ground cover and syntropic plots | Soil protection and ecological resilience | Field observations, soil readings, vegetation indices |
| Public Data Hub | Public progress visibility | MRV events, harvest records, impact metrics |
[Explore Adelphi live farm data →](https://hub.kokonut.network/projects/41)
***
## Phase II MRV milestones
Phase II evidence should move through the Kokonut MRV pipeline:
```text theme={null}
Farm activity → structured payload → IPFS record → Farm Registry event → EAS attestation → public Data Hub → annual impact report
```
| Milestone | Trigger | Evidence standard |
| --------------------------- | ------------------------------------------------ | ----------------------------------------------------- |
| First planting complete | Approved crop beds planted across cycle lengths | Planting record, field notes, plot references |
| First MRV data submitted | First accepted MRV payload | Structured record, timestamp, source, reviewer notes |
| First harvest recorded | First confirmed crop harvest | Crop type, yield, loss, sale/distribution record |
| Soil baseline comparison | Soil readings after regeneration practices begin | EC, VWC, temperature, lab data where available |
| Six-month production review | Interim operational report | Harvest, soil, water, pest, labor, and market notes |
| Annual impact report | Full reporting period completed | EBF report, CRISP review, public records, DAO summary |
Do not treat every Phase II observation as proof of regeneration. Some changes may be seasonal, weather-driven, or caused by measurement error. Strong claims require repeated measurements, clear baselines, and transparent methodology.
***
## What Phase II does not guarantee
Phase II reduces uncertainty by producing evidence, but it does not eliminate risk.
| Risk | Why it still matters |
| --------------- | ----------------------------------------------------------------------- |
| Weather risk | Rainfall, drought, storms, and heat can affect yields and soil readings |
| Execution risk | Planting, pruning, harvesting, and input timing determine outcomes |
| Labor risk | Regenerative systems require consistent, skilled fieldwork |
| Market risk | Prices, buyers, and demand can change after planting |
| Data risk | Missing, inconsistent, or low-quality records weaken verification |
| Soil risk | Soil improvement can take multiple cycles and may not be linear |
| Governance risk | Milestones still require DAO review, documentation, and approval |
The safest way to read Phase II is as a validation period: the farm is proving what works, what needs adjustment, and what evidence should guide future funding.
***
## Phase II completion criteria
Phase II is complete when the farm demonstrates sustained production with verified evidence.
| Criterion | How to verify it |
| --------------------------------------------------- | ------------------------------------------------------------------------------------ |
| At least three complete short-cycle harvest records | Harvest records submitted, reviewed, and compared against forecast assumptions |
| Medium-cycle crops established and productive | First medium-cycle harvest recorded and verified |
| Long-cycle crops established and healthy | Tree health records, survival checks, GPS/geospatial records, and vegetation signals |
| Soil improvement evidence collected | Readings compared against the Phase I baseline across multiple cycles |
| Annual impact report published | Environmental, economic, social, and risk evidence summarized and linked |
| CRISP or equivalent risk review completed | Risk factors were scored and included in the annual impact review |
| DAO has enough evidence to evaluate consolidation | Milestones, actuals, risks, and next-step budget are visible |
***
## Advancing to Phase III
Phase III begins when the evidence from Phase II shows that the farm is ready to consolidate, certify, and expand.
Phase III should not begin because a calendar says enough time has passed. It should begin because the farm has:
* A verified production record
* Clear harvest actuals
* Documented soil and operational evidence
* Healthy long-cycle crop establishment
* A public impact report
* A risk review
* A credible path toward certification, market expansion, or replication
[Read Phase III →](/kokonut-framework/development-phases/phase-iii)
***
## Reviewer checklist
Use this checklist before approving Phase II milestone disbursements or advancing to Phase III.
* Are planting and harvest records complete?
* Are actual yields separated from forecasts?
* Are loss rates documented instead of assumed?
* Are sale prices and distribution channels recorded?
* Are soil readings compared against the Phase I baseline?
* Are MRV payloads structured and inspectable?
* Are EAS attestations linked where applicable?
* Are claims about carbon, biodiversity, soil, or income supported by evidence?
* Are risks and failed assumptions documented?
* Is the next milestone clearly defined?
***
## Next steps
The readiness work that must happen before Phase II production begins.
The certification, market, and expansion phase that Phase II evidence makes possible.
The Adelphi forecast is used to compare expected production against actual harvest data.
How Phase II farm activity becomes public, verifiable evidence.
The regenerative practices of Phase II are put into operation.
How EBF and CRISP interpret Phase II evidence for impact and risk reporting.
# PHASE III: Consolidation and Expansion
Source: https://kokonut.network/kokonut-framework/development-phases/phase-iii
How a Kokonut farm moves from verified production into certification, stronger markets, replanting, training, and long-term institutional readiness.
# Phase III turns verified production into a resilient farm institution.
Phase III begins after a farm has already proven that it can produce, report, and improve through Phase II. The goal is no longer simply to plant, harvest, and measure. The goal is to consolidate what worked, formalize operating systems, expand market access, reduce founder dependency, and prepare the farm for long-term public-good production.
In Kokonut, Phase III is the bridge between a productive regenerative farm and a farm that DAO members, buyers, grant reviewers, community partners, and future replicators can trust.
**Primary action:** [Check Phase III readiness](#phase-iii-readiness)\
**Next phase:** [Understand Phase IV continuous operations](/kokonut-framework/development-phases/phase-iv)
Phase III strengthens the farm's credibility, but it does not guarantee certification approval, premium pricing, carbon credit issuance, institutional financing, or risk-free operations. Those outcomes require evidence, governance, market execution, and ongoing MRV.
***
## Phase III at a glance
| Question | Phase III answer |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| What stage is this? | Consolidation and expansion |
| When does it begin? | After Phase II production and MRV completion criteria are met |
| What changes? | The farm shifts from producing to standardizing, certifying, expanding, and teaching |
| Main outputs | Harvest protocols, certification pathway, market partnerships, replanting schedule, training program, multi-year evidence record |
| DAO role | Approves expansion capital, certification investments, land acquisition, operational upgrades, and major partnerships |
| MRV role | Converts operational maturity into longitudinal evidence, EAS attestations, EBF reports, and CRISP risk updates |
| Main risk | Overstating maturity before certification, buyer relationships, training systems, and multi-year reporting are actually in place |
***
## What Phase III must prove
Phase II asks: **Can this farm produce and verify regenerative activity?**
Phase III asks a harder question:
> Can this farm keep producing, keep improving, train others, serve stronger markets, and remain legible without depending on one founder or one harvest season?
That makes Phase III a trust-building phase. It should show that the farm is becoming more stable across five dimensions:
| Dimension | What must become stronger |
| ---------- | ------------------------------------------------------------------------------------------ |
| Operations | Harvest protocols, quality control, traceability, and post-harvest handling |
| Markets | Buyer relationships, certification readiness, distribution reliability, pricing discipline |
| Ecology | Replanting cycles, biodiversity expansion, and long-cycle crop continuity |
| Community | Training programs, local participation, knowledge transfer, public-good distribution |
| Evidence | MRV history, annual reports, CRISP updates, EAS attestations, Data Hub records |
***
## Phase III consolidation loop
```mermaid theme={null}
flowchart TD
A["Phase II verified production"] --> B["Standardize harvest protocols"]
B --> C["Pursue certification"]
C --> D["Expand market channels"]
D --> E["Improve revenue reliability"]
E --> F["Fund replanting and public goods"]
F --> G["Train operators and community members"]
G --> H["Reduce founder dependency"]
H --> I["Publish stronger MRV, EBF, and CRISP records"]
I --> J["DAO can review expansion with better evidence"]
J --> F
```
Phase III is not a single event. It is a compounding loop: better operations create better evidence, better evidence improves governance decisions, and better governance supports better long-term operations.
***
## What Phase III delivers
Crop-specific maturity indicators, harvest schedules, quality control, traceability records, and post-harvest handling procedures.
Documentation, internal audits, inspections, and certification updates that make organic claims reviewable instead of informal.
Stronger buyer relationships, clearer channel strategy, pricing discipline, and evidence-backed positioning for regenerative produce.
Multi-year replanting schedules for short-, medium-, and long-cycle crops, plus nursery-based native species deployment.
Operator training, community workshops, school programs, and train-the-trainer documentation for future replication.
Multi-year MRV records, annual EBF reports, CRISP updates, EAS attestations, and public Data Hub records.
***
## 1. Harvest protocols and post-harvest management
Phase III formalizes what Phase II tested in the field.
The farm should document how each crop is harvested, graded, stored, packaged, and reported. This reduces loss, improves quality, and prepares the farm for certification audits and buyer relationships.
| Protocol area | What to document | Why it matters |
| ------------------- | --------------------------------------------------------------------------- | ------------------------------------------- |
| Maturity indicators | Crop-specific color, size, texture, weight, and Brix readings were relevant | Prevents premature or late harvesting |
| Harvest schedule | Timing by crop cycle, buyer window, labor availability, and expected yield | Improves reliability and reduces waste |
| Quality control | Sorting, grading, rejection criteria, loss tracking | Makes actual quality and loss rates visible |
| Traceability | Plot, harvest date, operator, batch, buyer, price | Supports certification and buyer confidence |
| Handling | Packaging, storage, transport, and channel-specific requirements | Protects shelf life and sale value |
**At Adelphi:** Phase III should formalize lettuce cycle handling, passion fruit packaging, coconut harvest procedures, and batch-level traceability for certification and market access.
**MRV connection:** Harvest records should be logged for each harvest event and linked to farm records, actual yield, loss rate, sale price, plot, and operator.
***
## 2. Organic certification
Organic certification is not only a label. It is an audit process.
Phase III should make the farm's input history, field records, soil practices, harvest traceability, and operational procedures ready for review by the relevant national agricultural authority or certifying body.
| Certification step | Evidence needed |
| ---------------------- | ---------------------------------------------------------------------------------- |
| Internal audit | Input logs, soil records, crop records, field observations, training documentation |
| Application | Farm identity, operator details, land records, crop plan, production practices |
| Inspection | On-site review, documentation check, practice verification |
| Issuance or correction | Certificate approval, required changes, or follow-up actions |
| Renewal | Annual records showing continued compliance |
**At Adelphi:** certification is tied to the Dominican Republic Ministry of Agriculture pathway and should be updated in the farm record when status changes.
Certification can support access to stronger market channels, but it does not automatically guarantee premium pricing, supermarket placement, export access, or buyer commitments. Those depend on supply reliability, quality, pricing, logistics, and relationship execution.
***
## 3. Go-to-market strategy
Phase III market strategy should be evidence-backed.
The farm should not only say it produces regenerative food. It should be able to show records of: what was harvested, how much was sold, what the loss rate was, who bought it, what price was realized, and what evidence supports quality claims.
| Channel | What it requires | Phase III role |
| ---------------------- | ----------------------------------------------- | --------------------------------------------------------- |
| Community sales | Trust, proximity, consistent availability | Maintain local food access and feedback loops |
| Local organic markets | Quality, reliability, relationships | Formalize Phase II relationships |
| Restaurants and hotels | Consistent quality and delivery | Test B2B demand before larger scaling |
| Regional supermarkets | Volume, certification, documentation | Prepare supplier applications and compliance materials |
| National supermarkets | Certification, logistics, and formal agreements | Pursue only when the supply and records are strong enough |
| Export | Certification, cold chain, customs, scale | Usually Phase IV or later |
**DAO governance role:** market expansion that requires treasury spending, distribution infrastructure, new agreements with financial obligations, or brand commitments should go through a DAO proposal.
**At Adelphi:** Phase III should connect the founders' story, women-led operations, organic practices, and MRV evidence into a market narrative supported by records, not just branding.
***
## 4. Biodiversity replanting and continuous improvement
Regenerative farms should not plateau. Phase III should make biodiversity improvement part of the operating system.
That means the farm needs a replanting schedule for short-cycle beds, medium-cycle crops, long-cycle perennials, and native species from the nursery.
| Replanting layer | Phase III requirement |
| ---------------------- | ------------------------------------------------------------------ |
| Short-cycle crops | Rotation calendar, soil recovery plan, cover-crop or rest strategy |
| Medium-cycle crops | Replacement schedule for vines and seasonal producers |
| Long-cycle crops | Multi-year renewal plan for coconut and agroforestry species |
| Native species | Nursery inventory, GPS records, planting events, survival tracking |
| Community distribution | Records of surplus plants distributed as public goods |
**At Adelphi:** Phase III should deploy nursery stock into the agroforestry zone, track survival rates, maintain passion fruit replacement schedules, and begin documenting the future coconut renewal plan.
**MRV connection:** replanting events should be logged as farm events and linked to GPS records, field observations, vegetation indicators, and annual biodiversity reporting.
***
## 5. Training and education programs
Phase III should reduce founder dependency.
A farm becomes more resilient when knowledge is documented, shared, and practiced by more than the founding team. Training is not just community outreach; it is operational risk reduction.
| Training area | What to build |
| ------------------- | ----------------------------------------------------------------------------------------- |
| Operator training | Harvesting, syntropic management, input preparation, data entry, certification compliance |
| Community workshops | Organic farming, soil health, biodiversity, nutrition, and stewardship |
| Youth education | Farm visits, hands-on learning, ecology, food systems, and local culture |
| Train-the-trainer | Local instructors who can teach without founder dependency |
| Documentation | A replicable farm operations manual for future Kokonut farms |
**At Adelphi:** the education gazebo can become the training hub for farmers, children, elders, visitors, contributors, and future operators.
**MRV connection:** participation records, curriculum updates, instructor development, and community programs can feed Human, Social, Cultural, and Health Capital reporting.
***
## The coconut replanting cycle
Kokonut's long-term model depends on renewal, not extraction.
Coconut trees have productive lifespans under good conditions. Phase III should document how long-cycle crops are maintained, monitored, and eventually replanted so the farm can continue beyond the life of any single tree generation.
```mermaid theme={null}
flowchart TD
A["Coconut trees planted"] --> B["Growth and establishment"]
B --> C["Production years"]
C --> D["Revenue supports operations and public goods"]
D --> E["Tree age, health, and productivity monitored"]
E --> F["Replanting need identified"]
F --> G["DAO reviews renewal plan"]
G --> H["New trees planted"]
H --> B
```
The continuity mechanism is governance plus replanting discipline: the DAO must maintain a real renewal plan, rather than simply assuming the original planting lasts forever.
\$vKKN tree backing depends on accurate records, healthy farm operations, successful replanting, and DAO-approved renewal processes. The replanting cycle is a governance commitment, not an automatic guarantee.
***
## Evidence standard for Phase III
Phase III should raise the quality of evidence, not only the quantity of activity.
| Claim | Evidence is needed before using it publicly |
| --------------------------------------- | -------------------------------------------------------------------------------------- |
| The farm is certification-ready | Input logs, field records, internal audit, inspection status, certification documents |
| The farm has stronger market access | Signed agreements, delivery records, buyer communications, sales records |
| The farm is reducing loss rates | Per-harvest loss records compared across cycles |
| The farm is expanding biodiversity | Nursery records, GPS planting events, survival rates, vegetation observations |
| The farm is reducing founder dependency | Training records, instructor records, documented SOPs, independent operator capability |
| The farm is institutionally legible | Multi-year MRV, EBF reports, CRISP assessments, EAS attestations, Data Hub records |
***
## Phase III readiness
A farm should be ready for Phase III only when Phase II has produced enough evidence to justify consolidation.
Use this checklist before advancing:
* At least three verified harvest cycles are complete.
* Soil, crop, and field observations are being logged consistently.
* Long-cycle crops are established and monitored.
* A first annual impact report or equivalent MRV summary exists.
* Loss rates, yield, and price assumptions have been compared against actuals.
* The farm has a clear certification pathway and documentation plan.
* Operators can maintain core records without constant external support.
* Any expansion spending has a clear DAO proposal path.
***
## Phase III completion criteria
Phase III is complete when the farm demonstrates durable operations across consolidation, market, training, ecology, and evidence.
| Criterion | How it should be verified |
| ------------------------------------------ | --------------------------------------------------------------------------------------------- |
| Certification status resolved | Certificate issued, pending actions documented, or correction path published |
| Premium or stronger market channels tested | Buyer records, delivery records, realized pricing, or signed channel agreements |
| Replanting schedule documented | Multi-year planting and renewal calendar linked to the farm record |
| Training program operational | Published curriculum, attendance records, and at least one trained instructor beyond founders |
| Multi-year impact reporting active | Annual EBF reports, MRV summaries, and EAS attestations published |
| Risk profile improving | CRISP review shows reduced operational, developer, data, or market risk over time |
***
## What Phase III does not guarantee
Phase III reduces uncertainty, but it does not remove risk.
| Risk | Why it still matters |
| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| Certification risk | Inspectors may require corrective actions or reject claims without adequate records |
| Market risk | Buyers may change demand, pricing, volume requirements, or payment terms |
| Execution risk | Operators may fail to maintain protocols, records, or training schedules |
| Weather and ecological risk | Storms, pests, drought, disease, and soil variability can affect production |
| Data-quality risk | Weak records reduce trust even when farm activity is real |
| Governance risk | DAO proposals may not pass, or approved capital may not produce expected outcomes |
| Carbon and RWA risk | Carbon credits, tokenization, or institutional financing require standards, legal review, and third-party trust beyond internal farm records |
***
## Advancing into Phase IV
Phase IV is not a stage that begins only after Phase III. It is the continuous MRV and operations layer that runs underneath every phase and becomes more valuable as the farm matures.
Phase III prepares the farm for stronger Phase IV credibility by creating:
* cleaner protocols,
* stronger market records,
* certification documentation,
* biodiversity and replanting records,
* training systems,
* multi-year MRV history,
* EBF and CRISP reporting,
* and DAO-reviewed expansion decisions.
A farm that reaches this level is better positioned for institutional conversations, but access to institutional capital remains contingent on evidence quality, legal structure, market conditions, and partner due diligence.
***
## Next steps
Review the production and MRV evidence that Phase III builds on.
Understand the perpetual evidence layer that continues through every phase.
See how EBF and CRISP help interpret impact and risk over time.
Use the DAO proposal system for expansion, certification, partnership, or framework changes.
Learn how farm activity becomes structured evidence, attestations, and public records.
See the crops, nursery, poultry, biofactory, and training infrastructure that Phase III consolidates.
# PHASE IV: Continuous Operations
Source: https://kokonut.network/kokonut-framework/development-phases/phase-iv
How Kokonut farms keep producing, reporting, attesting, improving, and building credibility after the initial development phases.
# Phase IV is the evidence layer that never stops.
Phase IV is not a final stage after Phase III. It is the continuous operating state that runs beneath every Kokonut farm from the first baseline measurement onward.
Phases I, II, and III help a farm move from planning to production to consolidation. **Phase IV is what makes that journey legible over time:** harvest records, soil readings, field observations, satellite indices, public reports, EAS attestations, DAO feedback, and annual impact reviews.
Phase IV does not certify claims by itself. It produces the longitudinal evidence that stronger claims, audits, DAO decisions, and partnerships can depend on.
***
## Phase IV at a glance
| Question | Phase IV answer |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| What is it? | The continuous operations and evidence layer of the Kokonut Framework. |
| When does it start? | As soon as baseline farm data begins in Phase I. |
| When does it end? | It does not end while the farm remains active in the network. |
| What does it produce? | Farm records, MRV events, harvest data, EAS attestations, reports, and governance feedback. |
| Who uses it? | Farm operators, DAO members, Impact Guild contributors, grant reviewers, researchers, partners, and agent builders. |
| What does it not guarantee? | Yields, prices, carbon credits, certification, institutional financing, or risk-free operations. |
Phase IV is different from the MRV technical stack. MRV explains how farm activity becomes evidence. Phase IV explains why that evidence becomes more valuable as it accumulates over months and years.
***
## What Phase IV produces
Phase IV turns farm operations into a continuously improving evidence-based.
A growing record of harvests, planting cycles, soil readings, field observations, infrastructure milestones, and farm events.
Validated records can be published through IPFS/Filecoin, Farm Registry events, EAS attestations, and the public Kokonut Hub.
EBF-style reports, SDG summaries, and farm updates become more credible when they are backed by year-over-year data.
CRISP-style reviews and operational risk assessments can improve as the farm builds a longer track record.
DAO members and Guilds can use Phase IV evidence to evaluate proposals, milestone releases, method upgrades, and future farm funding.
Each farm creates lessons for the next farm: crop assumptions, loss rates, soil response, MRV gaps, training needs, and governance improvements.
***
## The Phase IV loop
```mermaid theme={null}
flowchart TD
A["Farm activity"] --> B["Field record or sensor data"]
B --> C["Structured MRV payload"]
C --> D["IPFS / Filecoin record"]
D --> E["Farm Registry event"]
E --> F["EAS attestation"]
F --> G["Kokonut Hub"]
G --> H["Annual report + DAO review"]
H --> I["Operational improvements"]
I --> A
G --> J["Contributor and agent learning"]
J --> I
```
This loop matters because regenerative agriculture is not proven in a single event. It becomes more credible through repeated observation, reported outcomes, and visible adaptation.
***
## Phase IV has four operating functions
Farm activity is recorded across remote sensing, field observations, per-plant records, harvest logs, soil data, and community reports.
| Evidence source | What it can show | Typical use |
| ------------------ | ----------------------------------------------------------------------------- | ------------------------------------------- |
| Satellite indices | Vegetation trends, canopy change, and farm polygon health | Ecological monitoring and anomaly detection |
| Soil observations | Moisture, electrical conductivity, temperature, and organic matter indicators | Soil health and irrigation decisions |
| Per-plant records | Planting location, species, inspection notes, survival status | Agroforestry and tree-backed asset records |
| Field observations | Pest pressure, water issues, crop condition, labor notes | Operational learning and early warnings |
| Harvest records | Yield, loss rate, sale price, crop cycle, plot, operator | Forecast comparison and revenue reporting |
At Adelphi, this includes satellite monitoring, Silvi plant records, field observations, and harvest records routed into Kokonut's public data infrastructure.
Phase IV turns operational data into reporting that different audiences can inspect.
| Cadence | Report type | Primary audience |
| ----------------------- | ------------------------------------------------- | -------------------------------------------- |
| Real-time / event-based | Kokonut Hub records, MRV events, harvest logs | DAO members, contributors, reviewers |
| Per harvest | Yield, loss rate, sale price, market notes | Farm operators, Finance Guild, DAO reviewers |
| Annual | EBF-style impact report and SDG summary | DAO, grant partners, communities, funders |
| Periodic / as needed | CRISP-style risk review, methodology update notes | Impact Guild, partners, capital allocators |
The goal is not to create reports after the fact. The goal is to make reporting a byproduct of operations.
Validated farm records can be anchored through the Kokonut MRV pipeline.
| Event type | Verification value |
| --------------- | --------------------------------------------------------------------- |
| MRV submission | Proves that a structured evidence payload existed at a specific time. |
| Harvest record | Connects production claims to crop, quantity, timing, and price data. |
| Annual report | Anchors impact claims to a published record and reporting period. |
| Phase milestone | Documents that a farm reached a defined operational threshold. |
| Risk assessment | Records the farm's risk profile at a specific point in time. |
Attestation does not make a claim automatically true. It makes the claim traceable, timestamped, and easier to audit.
Phase IV evidence feeds decisions across the DAO, Guilds, farm operators, and future farm proposals.
| Feedback user | How Phase IV helps |
| ---------------- | ------------------------------------------------------------------------------------- |
| Farm operators | Improve irrigation, crop planning, pest response, labor planning, and harvest timing. |
| DAO members | Compare proposals against actual farm performance and evidence of milestones. |
| Impact Guild | Review reporting quality, MRV gaps, SDG claims, and methodology upgrades. |
| Finance Guild | Compare forecasts against actual revenue, loss rates, costs, and cash-flow timing. |
| Technology Guild | Improve data schemas, dashboards, APIs, and agent workflows. |
| New farms | Learn from validated assumptions before requesting funding. |
***
## Why time is the most valuable variable
A farm with one month of data has observations. A farm with one year of data has a baseline. A farm with three years of data can begin showing patterns. A farm with five years of data can show whether production, soil, biodiversity, market access, and governance systems are actually compounding.
| Time horizon | What becomes possible | What still requires caution |
| ------------ | ----------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| 0–6 months | Baseline data, early soil observations, and first operating records | Too early for strong trend claims |
| 6–12 months | First annual report, initial harvest comparison, first SDG evidence map | Limited year-over-year comparison |
| 12–36 months | Seasonal patterns, operator track record, forecast-vs-actual analysis | Carbon, RWA, and financing claims still need external standards and review |
| 36+ months | Stronger institutional due diligence record and better replication benchmarks | Still subject to farm, market, legal, governance, and weather risk |
| 60+ months | Long-cycle crops and multi-year operational credibility become more visible | Continued maintenance, replanting, and data quality remain essential |
Phase IV can support institutional conversations, but it does not automatically unlock organic premiums, carbon credits, RWA tokenization, or debt financing. Those outcomes require additional verification, certification, market demand assessment, legal review, partner due diligence, and DAO approval, where relevant.
***
## Phase IV and the capital pathway
Phase IV is the evidence base that can make a farm more legible to partners over time.
| Possible pathway | Phase IV evidence needed | Claim status |
| ------------------------- | -------------------------------------------------------------------------------------------- | ---------------------------------------------- |
| Organic premium pricing | Certification status, quality records, buyer relationships, harvest history | Conditional on certification and market access |
| Carbon credit exploration | Multi-year soil and vegetation data, standard-specific methodology, third-party verification | Not automatic; requires external standards |
| RWA primitives | Accurate plant records, governance approvals, legal review, and attestation history | Conditional and jurisdiction-sensitive |
| Impact investment | Multi-year EBF reports, financial records, risk review, and transparent governance | Depends on partner diligence |
| Institutional debt | Long-term production history, clean financials, market contracts, and legal structure | Long-term possibility, not Phase I/II outcome |
This framing is important: **Phase IV is a prerequisite layer, not a promise of financing.**
***
## How Phase IV connects to the other phases
| Framework phase | Relationship to Phase IV |
| -------------------------------- | -------------------------------------------------------------------------------------------------- |
| Phase I — Foundation | Creates the baseline: farm schema, site diagnosis, soil preparation, crop plan, and MRV setup. |
| Phase II — Production | Produces the first real harvest and operational data that tests assumptions against reality. |
| Phase III — Consolidation | Uses repeated production and reporting to mature markets, training, certification, and resilience. |
| Phase IV — Continuous Operations | Keeps the farm accountable and useful as a long-term reference implementation. |
Phase IV is active throughout all phases, but it becomes more valuable as the farm continues to operate.
***
## What Phase IV does not guarantee
Phase IV reduces uncertainty by creating better records, but it does not remove uncertainty.
| Risk | Why it still matters |
| ---------------------------- | -------------------------------------------------------------------------------------------- |
| Weather and climate risk | Rainfall, drought, storms, and temperature anomalies can affect performance. |
| Execution risk | Farm outcomes still depend on operators, labor, maintenance, training, and decision quality. |
| Market risk | Prices, buyers, transport, certification, and demand can change. |
| Data-quality risk | Bad inputs, missing records, sensor failure, or inconsistent field logs weaken conclusions. |
| Governance risk | DAO decisions, funding timing, and proposal quality still affect execution. |
| Carbon and impact-claim risk | Strong claims require methodology, measurement, reporting periods, and verification. |
| Legal and regulatory risk | RWA, carbon, lending, and certification pathways depend on jurisdiction and partner review. |
***
## Phase IV reviewer checklist
Before using Phase IV data to support a proposal, report, partnership, or public claim, reviewers should ask:
* Is the farm record complete and tied to the Common Data Schema?
* Are forecasts separated from actual harvest records?
* Are SDG claims tied to measurable farm activity?
* Are carbon and climate claims clearly labeled as estimated, measured, or verified?
* Are EAS attestations linked to full payloads, not just summary claims?
* Is the reporting period clearly stated?
* Are missing data, sensor gaps, or field uncertainties disclosed?
* Has the relevant Guild reviewed the claim or methodology?
* Does the proposed next step require DAO approval?
***
## Next steps
Learn how farm activity becomes structured evidence, IPFS records, Farm Registry events, EAS attestations, Data Hub entries, and annual reports.
See the stage that strengthens certification, markets, training, biodiversity, replanting, and institutional readiness.
Understand how EBF and CRISP help interpret impact evidence and risk context.
Explore how agents can help automate data collection, reporting, forecasting, and attestation workflows.
Review the baseline farm record that Phase IV evidence builds upon.
See Phase IV in context through Kokonut's first live farm reference implementation.
# Ecological Impact Frameworks
Source: https://kokonut.network/kokonut-framework/framework-add-ons/ecological-impact-frameworks
How Kokonut uses EBF and CRISP to turn farm data into ecological impact reports, carbon-risk assessments, and DAO-ready evidence.
# Ecological impact needs both evidence and risk context.
Kokonut uses **EBF** and **CRISP** to help DAO members, farm operators, Impact Guild contributors, grant reviewers, and institutional partners interpret the evidence produced by the MRV workflow.
These frameworks do two different jobs:
* **EBF** explains the ecological, economic, social, and sustainability value a farm produces.
* **CRISP** explains which risks could prevent the projected carbon or ecological outcomes from being achieved.
Together, they help Kokonut move from broad regenerative claims to a clearer impact profile: **what happened, what evidence supports it, what remains uncertain, and what should be reviewed next.**
Use this page when preparing annual impact reports, reviewing farm proposals, assessing carbon-risk claims, or explaining Kokonut impact to partners.
EBF and CRISP help structure impact and risk analysis. They do not automatically certify a farm, guarantee carbon-credit issuance, guarantee financial returns, or replace MRV evidence, legal review, agronomic review, or DAO governance.
***
## EBF and CRISP at a glance
| Framework | Full name | Core question | Kokonut use |
| --------- | ------------------------------------------------- | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| **EBF** | Ecological Benefits Framework | What ecological and community benefits did the farm create? | Annual impact reporting across ecological, economic, social, and sustainability dimensions |
| **CRISP** | Carbon Risk Identification and Scoring Principles | What could prevent projected carbon or ecological benefits from being delivered? | Annual risk review for carbon-delivery, climate, policy, financial, and operator risk |
| **MRV** | Measurement, Reporting, and Verification | What evidence supports the claim? | Continuous data pipeline that produces records for EBF reports and CRISP scoring |
Think of MRV as the evidence layer, EBF as the impact interpretation layer, and CRISP as the risk interpretation layer.
***
## Where these frameworks fit in Kokonut
```mermaid theme={null}
flowchart TD
A["Farm activity\nharvest · soil · satellite · field log · training"] --> B["MRV payload\nstructured evidence"]
B --> C["IPFS / Filecoin record"]
C --> D["Farm Registry event"]
D --> E["EAS attestation"]
E --> F["Data Hub"]
F --> G["EBF annual impact report\nwhat value was created"]
F --> H["CRISP risk assessment\nwhat could prevent delivery"]
G --> I["DAO review"]
H --> I
I --> J["Funding decisions · partner reports · future proposals"]
```
Kokonut does not use EBF or CRISP as replacements for farm data. It uses them to interpret farm data that has already been collected, structured, published, and anchored through the MRV pipeline.
| Stage | Output | Primary owner | Where it appears |
| ------------------------ | --------------------------------------------------------------------------------- | --------------------------------------------- | ------------------------------------------------------- |
| Continuous farm activity | Field logs, harvest records, soil readings, satellite indices, training records | Farm team, Impact Guild, agents | Kokonut Hub, Farm Registry, MRV records |
| Continuous MRV | Structured evidence payloads and attestations | Impact Guild, Technology Guild | IPFS/Filecoin, Farm Registry, EAS, Data Hub |
| Annual EBF report | Impact profile across ecological, economic, social, and sustainability dimensions | Impact Guild | Data Hub, annual report, EAS summary attestation |
| Annual CRISP review | Risk scoring and mitigation notes | Impact Guild, Technology Guild, DAO reviewers | Data Hub, EBF report appendix, proposal review context |
| DAO learning | Updated assumptions for future farms and proposals | DAO members, Guilds | Governance forum, proposal templates, Framework updates |
***
## EBF — Ecological Benefits Framework
### What EBF does
EBF gives Kokonut a shared language for describing value that carbon-only accounting often misses.
A regenerative farm may improve soil health, protect biodiversity, train local workers, expand community food access, generate revenue, preserve cultural knowledge, and distribute public goods. EBF helps organize those benefits into a reportable structure so they can be discussed, compared, funded, and improved.
### What EBF does not do
EBF is not a sensor, a database, a farm registry, a carbon credit standard, or an automatic certification.
It is an interpretation framework. It requires evidence from MRV, financial records, field observations, community logs, and DAO reporting before any impact claim can be considered credible.
### EBF reporting dimensions
| EBF dimension | What it asks | Example Kokonut evidence | Related capital forms |
| ------------------------ | ---------------------------------------------- | --------------------------------------------------------------------------------------------------- | ---------------------------- |
| **Environmental impact** | Is the land improving? | Vegetation indices, soil readings, biodiversity records, nursery species counts, land-use records | Natural Capital |
| **Economic impact** | Is the farm creating durable economic value? | Harvest records, revenue actuals, public goods allocation, jobs created, infrastructure deployed | Financial + Material Capital |
| **Social impact** | Is the community gaining capacity and benefit? | Training logs, employment records, community events, participation records, leadership roles | Social + Human Capital |
| **Sustainability** | Can the system keep improving over time? | Multi-year MRV trend, risk controls, organic certification status, governance records, SDG evidence | All 8 Forms of Capital |
### How Kokonut produces an EBF report
An EBF report should be assembled from evidence, not written as a promotional summary.
| Evidence source | What it contributes |
| ---------------------------- | -------------------------------------------------------------------------------------- |
| Farm Registry records | Farm identity, location, land size, infrastructure, production zones, operators |
| Satellite and remote sensing | Vegetation-health trends, land-cover signals, ecological-change indicators |
| Soil and field observations | Soil moisture, electrical conductivity, temperature, crop condition, operator notes |
| Harvest records | Production actuals, crop cycles, losses, revenue assumptions, and forecast comparison |
| Community records | Employment, training, participation, public goods activities, local engagement |
| DAO records | Funding decisions, proposal commitments, governance actions, and reporting obligations |
| EAS attestations | Public evidence anchors for important measurement, reporting, and governance events |
Strong EBF reporting separates actuals from forecasts. A projected benefit can guide planning, but it should not be described as delivered impact until it is supported by evidence.
***
## CRISP — Carbon Risk Identification and Scoring Principles
### What CRISP does
CRISP helps Kokonut evaluate the risk associated with carbon-delivery and ecological-delivery claims.
This matters because a farm may have a promising regeneration thesis but still face weather risk, methodological risk, operator risk, financial risk, regulatory risk, and data quality risk.
CRISP makes those risks visible before claims are overused in proposals, partner materials, or public impact reports.
### What CRISP does not do
CRISP is not a pass/fail certification, not a guarantee of carbon delivery, and not a replacement for scientific carbon methodology.
It is a risk-scoring and due diligence framework. It helps reviewers ask better questions about whether projected benefits are likely to be delivered and verified.
### Five CRISP risk factors
| Risk factor | What it reviews | Kokonut evidence to inspect |
| ---------------------------- | ---------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| **Carbon yield risk** | Whether projected sequestration or carbon benefit assumptions are plausible | Baseline methodology, vegetation trends, soil data, biochar records, species mix, reporting period |
| **Climate catastrophe risk** | Whether drought, flood, fire, storms, or erosion could damage the system | Local climate data, water infrastructure, ground cover, erosion controls, disaster history |
| **Policy and legal risk** | Whether rules, land tenure, certification, or jurisdictional issues could disrupt claims | Land records, legal review, certification status, DAO proposal terms, compliance notes |
| **Financial risk** | Whether the farm can survive cost overruns, price changes, delays, or revenue shortfalls | Budget, reserves, crop diversification, revenue actuals, buyer relationships, treasury records |
| **Project developer risk** | Whether operators and supporting Guilds can execute the plan | Operator track record, field updates, milestone completion, support structure, reporting discipline |
### When Kokonut applies CRISP
CRISP should be applied repeatedly, not once.
| Moment | Why CRISP matters |
| ----------------- | -------------------------------------------------------------------------------- |
| Proposal review | Helps DAO members see whether projected benefits are realistic enough to fund |
| Phase I baseline | Establishes early risk assumptions before operations scale |
| Annual reporting | Updates risk scores using real MRV data and farm performance |
| Major expansion | Reviews whether new land, crops, infrastructure, or markets change delivery risk |
| Partner reporting | Gives grant reviewers and institutional partners a structured risk context |
***
## How EBF and CRISP work together
EBF and CRISP answer different sides of the same trust question.
```text theme={null}
EBF asks: What value did the farm create?
CRISP asks: What risks affect the farm's ability to keep delivering that value?
MRV asks: What evidence supports the answer?
```
A strong Kokonut impact profile includes all three:
| Layer | Without it | With it |
| ----- | ------------------------------------- | ------------------------------------------------------------ |
| MRV | Claims remain self-reported | Claims are tied to inspectable records |
| EBF | Value is reduced to revenue or carbon | Multiple forms of ecological and community value are visible |
| CRISP | Risk is ignored or hidden | Delivery uncertainty is named, scored, and mitigated |
***
## How this applies to Adelphi
At Adelphi, the EBF and CRISP workflow should help reviewers connect farm activity to evidence and risk.
| Adelphi activity | EBF relevance | CRISP relevance | Evidence to inspect |
| --------------------------- | ------------------------------------ | ------------------------------ | ------------------------------------------------------ |
| Syntropic plots | Environmental impact, sustainability | Carbon yield, climate risk | Satellite indices, field observations, crop logs |
| Nursery and at-risk species | Environmental impact, social impact | Project developer risk | Species inventory, distribution records, field updates |
| Biofactory and biochar | Environmental impact, sustainability | Carbon yield, methodology risk | Input logs, soil data, biochar production records |
| Poultry loop | Economic impact, sustainability | Financial and operator risk | Egg records, manure processing logs, feed records |
| Training gazebo | Social impact, human capital | Project developer risk | Workshop records, attendance logs, community reports |
| Public goods allocation | Economic impact, social impact | Financial risk | Revenue actuals, allocation reports, DAO records |
Adelphi can serve as a reference implementation, but each new farm still needs its own baseline, local risk review, MRV setup, operator assessment, and DAO-approved proposal.
***
## Reviewer checklist
Use this checklist before treating an EBF or CRISP output as decision-ready.
* Has the farm completed a baseline record through the Common Data Schema?
* Are claims separated into actuals, forecasts, estimates, and assumptions?
* Is each impact claim tied to a measurable source?
* Are carbon and climate claims backed by methodology, reporting period, and evidence?
* Are risks scored, explained, and paired with mitigation plans?
* Are uncertainty and data gaps visible to DAO members?
* Is the output published where reviewers can inspect it?
* Are important records anchored through EAS or another verifiable public evidence layer?
***
## What this page does not guarantee
These frameworks improve reporting quality, but they do not remove execution risk.
| Risk | Why it still matters |
| --------------------- | ----------------------------------------------------------------------------------------------- |
| Agricultural risk | Weather, pests, soil conditions, irrigation failures, and labor constraints can affect outcomes |
| Market risk | Prices, buyers, certification, and logistics can change revenue assumptions |
| Methodology risk | Carbon and ecological claims require defensible measurement methods |
| Data-quality risk | Missing or inconsistent records weaken reporting credibility |
| Governance risk | DAO decisions, proposal quality, and contributor coordination affect implementation |
| Legal and policy risk | Land, certification, environmental, or carbon-credit rules can change |
***
## Next steps
See how farm activity becomes structured payloads, IPFS records, EAS attestations, Data Hub entries, and annual impact reports.
Understand the value categories Kokonut uses before translating farm activity into EBF-style reports.
Use the six evaluation questions that help DAO members decide whether a farm is worth funding.
Start with the farm record that makes proposals, MRV, EBF reports, and CRISP scoring comparable.
See the live reference farm where Kokonut applies the Framework, MRV, SDG reporting, and farm-level evidence.
Turn impact and risk assumptions into a DAO-reviewable proposal with evidence, budget, milestones, and next steps.
# Common Data Schema
Source: https://kokonut.network/kokonut-framework/framework-components/common-data-schema
The 13-field farm record that makes Kokonut farms comparable, fundable, governable, and verifiable across proposals, the Data Hub, MRV workflows, and AI agents.
# The Common Data Schema is the farm record that enables Kokonut to scale.
Every Kokonut farm needs a shared baseline record before the network can fund, govern, verify, or compare it with other farms.
The **Common Data Schema** is that baseline. It is the minimum data contract between a farm and Kokonut Network: 13 required fields that describe the farm's location, budget, revenue model, governance, public goods allocation, local problem, proposed solution, and target market.
Without this schema, every farm becomes a one-off story. With it, DAO members, contributors, farm operators, grant reviewers, developers, AI agents, and the public can all inspect the same structured record.
Use this page when registering a farm, drafting a farm funding proposal, building Farm Registry tools, reviewing DAO support, or connecting farm records to MRV evidence.
A farm with an incomplete schema record should not be treated as funding-ready. The schema is not just documentation; it is the baseline record that reviewers, APIs, dashboards, agents, and attestations depend on.
***
## Why the schema matters
The Common Data Schema turns a farm from an informal narrative into a structured, inspectable record.
| Without a common schema | With the Common Data Schema |
| --------------------------------------- | --------------------------------------------------------------------------------------------------- |
| Farm proposals are hard to compare | DAO members can compare farms by shared fields |
| Impact claims stay self-reported | MRV can attach evidence to a known farm record |
| Developers need custom logic per farm | APIs, dashboards, and agents can use the same structure |
| Governance decisions rely on long prose | Reviewers can inspect the budget, location, crops, governance, and public goods commitments quickly |
| Replication is difficult | New farms can reuse the same intake format |
The schema is the first layer of Kokonut's farm operating system. It does not prove impact on its own, but it makes impact evidence attachable to a consistent farm identity.
***
## What the schema powers
Once the 13 fields are populated, a single farm record can be used by multiple parts of Kokonut simultaneously.
| Consumer | How it uses the schema |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| DAO members | Review farm funding proposals and compare farms across location, budget, crop mix, governance, and public goods commitments. |
| Farm Registry API | Accepts and stores the farm record so other tools can query the same canonical data. |
| Kokonut Data Hub | Publicly displays the farm profile, metadata, harvest records, MRV events, and impact metrics. |
| AI agents | Query farm identity, location, crops, and governance context before forecasting, scoring, drafting, or monitoring. |
| EAS attestations | Anchor farm events to the correct`farm_id`, so evidence can be traced back to the farm record. |
```mermaid theme={null}
flowchart TD
A["Farm operator fills 13 fields"] --> B["Canonical farm record"]
B --> C["DAO funding proposal"]
B --> D["Farm Registry API"]
B --> E["Kokonut Data Hub"]
B --> F["AI agents"]
B --> G["MRV payloads"]
G --> H["IPFS/Filecoin record"]
H --> I["EAS attestation"]
I --> E
E --> J["DAO, reviewer, partner, and public decisions"]
```
The schema should be understood as the farm's identity layer. MRV then adds the evidence layer on top of it.
***
## Who uses this page
Use the schema to prepare a farm record before requesting DAO support, registering the farm, or publishing it to the Data Hub.
Use the schema to assess whether a farm proposal provides sufficient comparable information to evaluate funding, governance, and risk.
Use the schema to connect local problems, proposed solutions, public goods allocation, SDGs, and MRV commitments.
Use the TypeScript interface and validation rules to build Farm Registry integrations, dashboards, agents, and import tools.
Use the schema to inspect whether a farm has a traceable funding source, measurable activity, and a public evidence path.
Use the Adelphi reference record as a concrete example before submitting your own farm intake.
***
## The 13 required fields
The schema is intentionally small. It captures only the minimum data needed to make a farm comparable, fundable, governable, and verifiable.
| Group | Field | Type | Required | What reviewers need to see |
| ------------ | ----------------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------ |
| Identity | Project Date | `Date` | Yes | Official Kokonut project start date in `YYYY-MM-DD` format. |
| Funding | Forecasted Budget | `Number` | Yes | Total estimated development budget in USD, with assumptions documented in the proposal. |
| Scope | Land Size | `Number` | Yes | Total land dedicated to agricultural activity, in square metres. |
| Identity | Project Location | `Coordinates` | Yes | Decimal latitude/longitude, plus region and country. |
| Funding | Source of Funding | `Text` | Yes | DAO proposal, grant, partner, or public goods funding source. |
| Production | Revenue Streams | `Multiselect` | Yes | Crop, product, or service revenue tags such as `lettuce`, `coconut`, or `poultry_eggs`. |
| Governance | Governance Mechanism | `Single Select` | Yes | How the farm will be governed: `moloch_dao`, `guilds`, `multisig`, or `cooperative`. |
| Governance | Token Allocation | `Richtext` | Yes | Narrative describing \$vKKN, Loot, operator share, DAO share, public goods share, or other governance logic. |
| Public goods | Public Goods Allocation | `Number` | Yes | Percentage of gross revenue allocated to public goods activities. Minimum Kokonut default: `10`. |
| Narrative | Project Summary | `Richtext` | Yes | Clear summary of location, land size, crop selection, forecast, governance, and impact logic. |
| Narrative | Local Problem | `Richtext` | Yes | The specific local problem the farm addresses. Name the place, people affected, and why it matters. |
| Narrative | Proposed Solution | `Richtext` | Yes | How the farm's production, infrastructure, education, jobs, or MRV workflow address the local problem. |
| Market | Target Market | `Multiselect` | Yes | Expected distribution channels such as `organic_markets`, `direct_community_sales`, or `local_supermarkets`. |
Do not use generic placeholder text for `Local Problem`, `Proposed Solution`, or `Project Summary`. These fields explain why the farm deserves support, how it will be evaluated, and how its impact can be verified later.
***
## Field groups
### 1. Identity fields
These fields answer the questions: **Which farm is this, where is it, and when did it enter Kokonut?**
| Field | Validation guidance |
| ---------------- | --------------------------------------------------------------------------------------------------------- |
| Project Date | Use ISO 8601 format: `YYYY-MM-DD`. This should be the official Kokonut project registration/start date. |
| Project Location | Store coordinates in decimal latitude/longitude format. Include region and country for human readability. |
Example:
```json theme={null}
{
"project_date": "2024-01-15",
"project_location": {
"coordinates": "18.938879,-69.735003",
"region": "Gonzalo, Sabana Grande de Boyá, Monte Plata",
"country": "Dominican Republic"
}
}
```
### 2. Scope and production fields
These fields answer: **What is the farm producing, and at what scale?**
| Field | Validation guidance |
| --------------- | -------------------------------------------------------------------------------------------------------------------- |
| Land Size | Use square meters. If total land and agricultural area differ, include the agricultural area in the Project Summary. |
| Revenue Streams | Use lowercase underscore tags. Include crops, animal products, native plants, biochar, or other revenue sources. |
| Target Market | Use lowercase underscore tags for expected channels and add custom tags only when needed. |
Common `revenue_streams` values:
```text theme={null}
lettuce · passion_fruit · coconut · poultry_eggs · biochar · indian_yam · tomato · broccoli · spinach · arugula · native_plants
```
Common `target_market` values:
```text theme={null}
organic_markets · local_supermarkets · direct_community_sales · national_supermarkets · export
```
### 3. Funding and public goods fields
These fields answer: **What does the farm need, where did support come from, and what flows back to public goods?**
| Field | Validation guidance |
| ----------------------- | ------------------------------------------------------------------------------------------ |
| Forecasted Budget | Use USD. Treat this as a planning estimate, not a guaranteed outcome or investment return. |
| Source of Funding | Include proposal numbers, grant names, or partner names wherever possible. |
| Public Goods Allocation | Use an integer percentage from 0 to 100. Kokonut's default minimum is 10%. |
Budget and revenue fields should distinguish forecasts from actuals. Forecasts help reviewers plan; actuals should be tracked through farm records, harvest logs, and MRV updates.
### 4. Governance fields
These fields answer the questions: **Who governs the farm, and how are ownership, contributions, and public goods recognized?**
| Field | Accepted values or guidance |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| Governance Mechanism | `moloch_dao`, `guilds`, `multisig`, or `cooperative`. |
| Token Allocation | Explain how governance rights, Loot, operator shares, DAO shares, contributor recognition, or public goods allocations work. |
Governance values:
| Value | Use when... |
| ------------- | -------------------------------------------------------------------------------------------------- |
| `moloch_dao` | The farm is governed through the Kokonut Moloch DAO and DAO-approved funding proposals. |
| `guilds` | The farm or workstream is coordinated primarily through contribution-weighted Guild participation. |
| `multisig` | A defined group of signers manages execution or transitional governance. |
| `cooperative` | A traditional cooperative or local governance structure is the primary operating body. |
### 5. Narrative fields
These fields answer: **Why should this farm exist, and what problem does it solve?**
| Field | A good answer includes |
| ----------------- | -------------------------------------------------------------------------------------------------------- |
| Project Summary | Location, land size, farm type, production plan, governance model, funding source, and impact thesis. |
| Local Problem | Specific local economic, ecological, food, labor, gender, education, or infrastructure problem. |
| Proposed Solution | How farm operations, infrastructure, crops, community programs, MRV, and governance address the problem. |
These fields should be written clearly enough for a DAO member, grant reviewer, or local partner to understand without having to read the entire farm proposal.
***
## TypeScript interface
The canonical machine-readable representation of the Common Data Schema uses snake\_case fields.
```typescript theme={null}
interface KokonutFarmRecord {
// Identity
project_date: string; // ISO 8601, e.g. "2024-01-15"
project_location: {
coordinates: string; // Decimal lat,lng, e.g. "18.938879,-69.735003"
region: string; // Human-readable place name
country: string; // Full country name
};
// Scope and production
land_size: number; // Square metres
revenue_streams: string[]; // e.g. ["lettuce", "coconut", "passion_fruit", "poultry_eggs"]
target_market: string[]; // e.g. ["organic_markets", "local_supermarkets"]
// Funding and public goods
forecasted_budget: number; // USD
source_of_funding: string; // e.g. "Kokonut DAO Proposal #12 / Public Nouns Proposal #69"
public_goods_allocation: number; // Percentage 0–100
// Governance
governance_mechanism: "moloch_dao" | "guilds" | "multisig" | "cooperative";
token_allocation: string; // Markdown-compatible rich text narrative
// Narrative
project_summary: string;
local_problem: string;
proposed_solution: string;
}
```
### JSON example
```json theme={null}
{
"project_date": "2024-01-15",
"project_location": {
"coordinates": "18.938879,-69.735003",
"region": "Gonzalo, Sabana Grande de Boyá, Monte Plata",
"country": "Dominican Republic"
},
"land_size": 15725,
"revenue_streams": ["lettuce", "passion_fruit", "coconut", "poultry_eggs", "indian_yam", "biochar", "native_plants"],
"target_market": ["organic_markets", "local_supermarkets", "direct_community_sales"],
"forecasted_budget": 85000,
"source_of_funding": "Kokonut DAO Proposal #12 / Public Nouns Proposal #69",
"public_goods_allocation": 10,
"governance_mechanism": "moloch_dao",
"token_allocation": "70% DAO members · 20% farm operators · 10% public goods fund",
"project_summary": "15,725 m² agro-ecological farm in Monte Plata, Dominican Republic.",
"local_problem": "Economic hardship, food insecurity, environmental degradation, and gender inequality in the Monte Plata rural community.",
"proposed_solution": "Regenerative agro-ecological production integrating soil restoration, biodiversity conservation, organic food production, community education, and public MRV."
}
```
***
## Adelphi reference record
[Adelphi](/ecosystem-wiki/kokonut-farms/adelphi/summary) is Kokonut Network's first live farm and the reference implementation for this schema.
| Field | Adelphi value |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Project Date | `2024-01-15` |
| Forecasted Budget | `85000` USD |
| Land Size | `15725` m² |
| Project Location | `"18.938879,-69.735003"` · Gonzalo, Sabana Grande de Boyá, Monte Plata · Dominican Republic |
| Source of Funding | `"Kokonut DAO Proposal #12 / Public Nouns Proposal #69"` |
| Revenue Streams | `lettuce`, `passion_fruit`, `coconut`, `poultry_eggs`, `indian_yam`, `biochar`, `native_plants` |
| Governance Mechanism | `moloch_dao` |
| Token Allocation | 70% DAO members · 20% farm operators · 10% public goods fund |
| Public Goods Allocation | `10`% |
| Project Summary | 15,725 m² agro-ecological farm in Monte Plata, Dominican Republic, with organic vegetables, fruits, coconuts, public goods funding, and women-led operations. |
| Local Problem | Economic hardship, food insecurity, environmental degradation, and gender inequality in the Monte Plata rural community. |
| Proposed Solution | Regenerative agro-ecological production integrating soil restoration, biodiversity conservation, organic food production, and community education. |
| Target Market | `organic_markets`, `local_supermarkets`, `direct_community_sales` |
[Explore Adelphi live data →](https://hub.kokonut.network/projects/41)
***
## Validation checklist before a farm proposal
Before a farm submits a funding proposal, reviewers should be able to answer each question below.
| Check | Reviewer question |
| ---------------- | -------------------------------------------------------------------------------------- |
| Identity | Can we identify the farm, location, start date, and operating context? |
| Scope | Do we know the land size, productive area, crop mix, and target market? |
| Budget | Is the forecasted budget specific enough to evaluate and to set milestones? |
| Funding source | Is the source of funding traceable to a grant, proposal, partner, or treasury request? |
| Governance | Is the governance mechanism clear enough to know who decides and who is accountable? |
| Token allocation | Are DAO members, operators, contributors, and public goods allocations explained? |
| Public goods | Is the public goods allocation percentage explicit? |
| Problem | Is the local problem specific, place-based, and relevant? |
| Solution | Does the proposed farm solution directly answer the stated problem? |
| MRV readiness | Can future farm events attach back to this record through `farm_id`? |
A strong farm record is not necessarily long. It is specific, traceable, and structured enough for funding, operations, MRV, and governance to use the same source of truth.
***
## How the schema connects to MRV
The Common Data Schema defines the farm. MRV verifies what happens on the farm after registration.
| Schema layer | MRV dependency |
| --------------------------------------- | ----------------------------------------------------------------------------------------------- |
| `project_location` | Connects remote sensing, field logs, drone imagery, and satellite indices to the correct place. |
| `revenue_streams` | Helps match harvest records and production forecasts to the correct crops or products. |
| `governance_mechanism` | Determines who reviews evidence, approves changes, and responds to risks. |
| `source_of_funding` | Links evidence back to the proposal, grant, or DAO decision that funded the work. |
| `public_goods_allocation` | Let the network track whether farm revenue supports public goods commitments. |
| `local_problem` and `proposed_solution` | Provide the narrative baseline that SDG and impact reporting can evaluate over time. |
```mermaid theme={null}
flowchart TD
A["Common Data Schema\nfarm identity + baseline"] --> B["Farm event\nharvest · soil · field log · satellite"]
B --> C["Structured MRV payload"]
C --> D["IPFS/Filecoin record"]
D --> E["Farm Registry event"]
E --> F["EAS attestation"]
F --> G["Data Hub + annual reports"]
G --> H["DAO and partner review"]
```
***
## Schema governance and backward compatibility
The Common Data Schema is a root data contract. Farm records, APIs, dashboards, AI agents, and attestations depend on these field names and types.
Changing the schema requires a **Framework Upgrade Proposal** because schema changes can affect live farms, MRV payloads, Data Hub queries, and agent behavior.
Any breaking change must include:
1. A migration plan for currently registered farms
2. A dual-write period where old and new formats are accepted
3. A cutover date after which the old format is no longer accepted
4. Documentation updates for farm operators, developers, and proposal authors
5. A passed DAO vote before the change becomes active
Additive optional fields are lower-risk, but they still require documentation and governance review. Required field changes, field renames, or type changes should be treated as high sensitivity.
[Use the Framework Upgrade Proposal Template →](/ecosystem-wiki/the-kokonut-dao/proposal-templates#framework-upgrade-proposal)
***
## Common mistakes to avoid
| Mistake | Why does it create risk |
| --------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| Using vague location descriptions | Remote sensing, field logs, and farm events cannot reliably attach to the farm. |
| Treating forecasted budget as guaranteed performance | Forecasts are planning tools and must be refined against actuals. |
| Omitting the source of funding | Reviewers cannot trace the farm back to the proposal, grant, or treasury decision that supported it. |
| Writing generic local problems | The DAO cannot evaluate whether the proposed solution fits the community context. |
| Mixing \$vKKN, Loot, and Guild Points without explanation | Governance, capital, and contribution recognition become confusing. |
| Changing field names casually | APIs, agents, attestations, and dashboards may break. |
***
## Next steps
Use the schema in a DAO-ready farm funding proposal, including budget, milestones, MRV commitments, and public goods allocation.
See how farm records become verifiable evidence through payloads, IPFS, Farm Registry events, EAS attestations, and the Data Hub.
Understand how this schema fits into Kokonut's larger system for comparable, fundable, governable, and verifiable farms.
Review the first live Kokonut farm using the schema in practice.
Choose the right proposal type before requesting farm funding, Guild work, Framework changes, or partnerships.
Inspect the live reference farm record and its connected MRV and impact data.
# 5 Principles of Regeneration
Source: https://kokonut.network/kokonut-framework/framework-components/framework-features/5-principles-of-regeneration
The operating standard Kokonut farms use to protect soil, increase biodiversity, integrate animals, maintain living roots, and turn regenerative practices into verifiable evidence.
# The 5 Principles turn regenerative intent into farm practice.
The Kokonut Framework uses the **5 Principles of Regeneration** as the operating standard for every farm in the network. They are not a rigid recipe. They are a practical checklist for designing farms that improve soil, biodiversity, water retention, food production, and long-term community resilience.
Each farm can apply the principles differently depending on climate, soil, slope, crops, labor, livestock, and local market conditions. What matters is that each principle is addressed, documented, and measured.
Built for farm founders, DAO reviewers, agronomists, Impact Guild contributors, MRV builders, and community members evaluating whether a farm is truly regenerative.
5
regeneration principles
2
Adelphi syntropic plots
The principles are an operating standard, not a universal prescription. A tropical farm in the Dominican Republic will implement them differently than a temperate farm, a flatland farm, or a cattle-based operation. Kokonut evaluates whether each principle is addressed and evidenced, not whether every farm uses the same technique.
***
## The five principles at a glance
| Principle | Core question | What reviewers should look for | Example evidence |
| --------------------------- | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| 1 — Reduce soil disturbance | Is the farm protecting soil structure and biology? | No-till or low-disturbance practices, reduced synthetic inputs, biological fertility plan | Soil EC, field logs, input records, bed-preparation records |
| 2 — Keep soil covered | Is bare soil minimized across the year? | Living cover, mulch, cover crops, terracing, erosion control | Soil moisture, visual inspections, ground-cover records |
| 3 — Increase biodiversity | Is the farm becoming more diverse at the crop, tree, habitat, and microbial levels? | Multi-species planting, agroforestry, conservation nursery, crop rotation | Species count, satellite indices, Silvi records, biodiversity surveys |
| 4 — Integrate animals | Are animals part of nutrient cycling rather than separate from the farm system? | Poultry, grazing, manure processing, forage loops, pest management | Poultry records, manure/input logs, soil response data |
| 5 — Maintain living roots | Are perennial and long-cycle root systems active over time? | Coconut, passion fruit, native trees, perennial crops, compost/biofertilizers | Tree health, NDRE, GPS plant records, soil organic matter trends |
These principles work together. A farm with living cover but no biodiversity remains fragile. A farm with animals but no nutrient management can create waste problems. A farm with perennial trees but no MRV still struggles to prove progress.
***
## How the principles reinforce each other
```mermaid theme={null}
flowchart TD
A["1. Reduce disturbance"] --> B["Soil structure recovers"]
B --> C["2. Living cover protects the surface"]
C --> D["Water retention and organic matter improve"]
D --> E["3. Biodiversity increases"]
E --> F["Pest pressure and climate stress are distributed"]
F --> G["4. Animals cycle nutrients"]
G --> H["Biofertility feeds crops"]
H --> I["5. Living roots maintain biology"]
I --> B
D --> J["MRV evidence"]
E --> J
G --> J
I --> J
J --> K["DAO decisions + farm improvement"]
```
The loop is the point. Regeneration is not one practice; it is a system of practices that creates better conditions over time.
***
## Principle 1 — Reduce synthetic and mechanical soil disturbance
**What it means:** protect soil structure, microbial life, fungal networks, and organic matter by reducing tillage, unnecessary mechanical disruption, and dependency on synthetic inputs.
**Why it matters:** soil is a living system. Mechanical disturbance can break soil aggregates and fungal networks. Synthetic input dependency can replace biological nutrient cycling with chemical substitution. Reducing disturbance gives soil biology time to rebuild.
**How Kokonut farms can apply it:**
* No-till or low-till bed preparation
* Direct seeding or transplanting with minimal disturbance
* On-site organic inputs instead of synthetic input dependency
* Biochar, compost, humic acids, organic urea, and other biological fertility sources
* Field logs that record soil preparation and input application
**At Adelphi:** bed preparation is designed around syntropic succession, manual biochar incorporation, cover cycling, and on-site inputs including bamboo biochar, humic acids, and organic urea.
**Measured by:** soil electrical conductivity, input logs, field observations, bed-preparation records, and changes in soil response over time.
***
## Principle 2 — Maintain year-round living cover
**What it means:** keep soil covered with living plants, mulch, or cover systems so the surface is not left exposed to rainfall impact, erosion, heat, and moisture loss.
**Why it matters:** bare soil loses water, organic matter, structure, and biological continuity. Living cover protects the surface while feeding soil life and reducing the risk of erosion.
**How Kokonut farms can apply it:**
* Cover crops between production cycles
* Permanent grass or vegetative cover on slopes and terraces
* Mulch from pruning and biomass cycling
* Multi-strata crop systems where one layer remains active while another is harvested
* Erosion-control logs and ground-cover inspections
**At Adelphi:** beard grass is maintained along terraced areas, while syntropic multi-strata planting helps preserve living cover above and below the soil surface across crop cycles.
**Measured by:** volumetric water content, field inspections, erosion observations, satellite imagery, and ground-cover records.
***
## Principle 3 — Increase biodiversity at every scale
**What it means:** design the farm to support diversity across crops, trees, animals, insects, microorganisms, and native species.
**Why it matters:** monocultures concentrate risk. Biodiversity spreads ecological load, supports pollinators and habitat, reduces pest fragility, and helps nutrient and water cycles become more resilient.
**How Kokonut farms can apply it:**
* Multi-cycle crops: short, medium, and long-cycle production
* Agroforestry and multi-strata planting
* Native species restoration
* On-site nursery propagation
* Crop rotation and intercropping
* Biodiversity surveys and species inventories
**At Adelphi:** biodiversity is implemented through short-cycle vegetables, medium-cycle passion fruit and Indian yams, long-cycle coconuts, native agroforestry species, and a nursery that propagates at-risk Dominican plant species for the farm and surrounding communities.
**Measured by:** species count, nursery inventory, GPS plant records, satellite NDVI/NDRE/MSAVI, field observations, and biodiversity surveys.
***
## Principle 4 — Integrate animals into production
**What it means:** include animals as part of the farm's nutrient cycle, pest balance, and production system rather than treating livestock as a separate operation.
**Why it matters:** Animals can transform forage and organic material into food, manure, and biological fertility. When managed well, they can reduce waste, support soil fertility, and diversify farm revenue.
**How Kokonut farms can apply it:**
* Free-range poultry systems
* Rotational grazing, where appropriate
* On-farm forage production
* Manure processing into compost, humic acids, or other biofertilizers
* Animal health and production records
**At Adelphi:** 110 free-range hens produce eggs and manure. The hens are fed with forage grown on-site, and their manure is processed into humic acids and organic urea for crop beds.
```text theme={null}
Pangola grass → hens → eggs + manure → humic acids + organic urea → crop beds → healthier crops → more forage
```
**Measured by:** poultry records, egg production, manure-processing logs, forage use, soil EC, and crop response after biofertilizer application.
***
## Principle 5 — Protect and build living root systems
**What it means:** maintain living roots through perennial, long-cycle, and multi-year crops that keep feeding soil biology over time.
**Why it matters:** Roots are the interface between plants and soil. They anchor soil, feed microorganisms, support water pathways, and help the farm remain biologically active beyond a single crop cycle.
**How Kokonut farms can apply it:**
* Perennial crops such as coconut, cacao, fruit trees, and native trees
* Multi-year vines and agroforestry systems
* Deep-rooted species for structure and water access
* Compost and biofertilizers that support root-zone biology
* Individual plant tracking and health monitoring
**At Adelphi:** living root systems are supported by coconut trees, passion fruit vines, native agroforestry species, and biological inputs produced on-site.
| Perennial layer | Example at Adelphi | Root-system role | Evidence to track |
| ------------------- | ------------------------ | ----------------------------------------------------------- | ----------------------------------------- |
| Long-cycle trees | Coconut | Anchoring roots, canopy structure, and long-term production | Tree health, GPS records, harvest logs |
| Medium-cycle vines | Passion fruit | Multi-year root network and fruit production | Vine health, crop-cycle records |
| Native agroforestry | Dominican native species | Habitat, canopy diversity, soil structure | Nursery inventory, plant records, surveys |
| Ground/root support | Cover crops and grasses | Moisture retention, erosion control | Soil moisture, field observations |
**Measured by:** tree health, Silvi GPS records, NDRE, root-zone observations, soil health indicators, and long-term crop performance.
Carbon, soil organic matter, biodiversity, and resilience outcomes should be treated as estimates until supported by methodology, measurements, reporting periods, and MRV evidence. The principles improve the conditions for regeneration, but they do not guarantee specific outcomes on their own.
***
## How Adelphi applies all five principles
| Principle | Adelphi implementation | Evidence pathway |
| ------------------ | ---------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
| Reduce disturbance | Low-disturbance syntropic bed management; on-site biochar, humic acids, and organic urea | Field logs, input records, soil EC |
| Living cover | Beard grass, terraced edge cover, multi-strata canopy | Soil moisture, visual inspections, satellite vegetation indices |
| Biodiversity | Short, medium, and long-cycle crops; native agroforestry; at-risk species nursery | Species inventory, GPS plant records, biodiversity surveys |
| Animal integration | 110 hens, forage loop, manure-to-biofertilizer system | Poultry records, egg production, manure logs, soil response |
| Living roots | Coconut, passion fruit, native trees, perennial canopy species | Silvi records, tree health, NDRE, harvest logs |
[Explore Adelphi infrastructure →](/ecosystem-wiki/kokonut-farms/adelphi/crops-biodiversity-and-infrastructure)
***
## How the principles become evidence
The principles are only useful to the network when they can be observed, recorded, and compared. Kokonut's MRV workflow turns farm practices into structured evidence.
| Practice | What gets recorded | Why it matters |
| ------------------------------------ | ------------------------------------------------------ | --------------------------------------------------------- |
| Bed preparation and soil management | Field logs, input records, soil readings | Shows whether soil disturbance is reduced over time |
| Cover crops and ground cover | Soil moisture, field photos, satellite imagery | Shows whether the farm is protecting exposed soil |
| Biodiversity and nursery propagation | Species inventory, GPS plant records, surveys | Shows whether diversity is increasing or being maintained |
| Poultry and manure processing | Animal records, production records, biofertilizer logs | Shows whether animals support fertility and revenue |
| Perennial crop health | Tree/vine health, GPS records, NDRE, harvest logs | Shows whether living root systems are maintained |
```mermaid theme={null}
flowchart TD
A["Regenerative practice"] --> B["Field observation or sensor reading"]
B --> C["Structured MRV payload"]
C --> D["IPFS / Filecoin record"]
D --> E["Farm Registry event"]
E --> F["EAS attestation"]
F --> G["Kokonut Hub + annual impact report"]
```
[Read the MRV methodology →](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification)
***
## How DAO reviewers should use this page
When reviewing a farm proposal, use the five principles as a practical due diligence filter.
| Reviewer question | Strong proposal evidence | Weak proposal signal |
| ----------------------------------------- | ------------------------------------------------------------- | ------------------------------------------- |
| Is soil disturbance addressed? | Clear low-disturbance plan, input strategy, soil monitoring | Vague promise to farm organically |
| Is a living cover planned? | Cover crop or ground-cover system tied to erosion/water goals | Bare soil between cycles with no mitigation |
| Is biodiversity designed into production? | Crop mix, agroforestry layers, native species plan | Single-crop revenue dependency |
| Are animals integrated responsibly? | Animal system tied to fertility, forage, records, and welfare | Livestock added without nutrient plan |
| Are living roots protected? | Perennial crop layer and long-term plant monitoring | Only short-cycle annual crops |
| Can it be verified? | MRV plan, data owner, reporting cadence, metrics | Impact claims without evidence pathway |
The five principles should inform farm design, proposal review, MRV planning, annual reporting, and Framework upgrades. They are not marketing language; they are operating requirements that must be adapted to each farm's real context.
***
## What this does not guarantee
Implementing the principles improves the conditions for regeneration, but it does not remove risk.
| Risk | Why it still matters |
| ----------------- | ---------------------------------------------------------------------------------------- |
| Weather risk | Droughts, storms, flooding, and heat can still damage crops |
| Execution risk | Poor implementation can undermine even strong principles |
| Labor risk | Regenerative systems require trained and consistent operators |
| Market risk | Healthy crops still need buyers, logistics, and fair pricing |
| Data-quality risk | Weak field logs or sensor gaps reduce verification quality |
| Carbon-claim risk | Carbon outcomes require formal methodology and measurement before strong claims are made |
***
## Next steps
Understand the farming method Kokonut uses to integrate crops, trees, soil, animals, and succession into a single production system.
See how regenerative practices connect to impact claims, circular systems, and MRV-backed evidence.
Learn how soil, satellite, harvest, field, and biodiversity records become public evidence.
See how the five principles are implemented through crops, biodiversity, poultry, biofertilizers, and farm infrastructure.
Use the farm record that helps DAO members, contributors, and agents compare farms consistently.
Turn a regenerative farm plan into a reviewable DAO proposal that includes evidence, a budget, risks, and success metrics.
# 8 Forms of Capital
Source: https://kokonut.network/kokonut-framework/framework-components/framework-features/8-forms-of-capital
How Kokonut measures value beyond revenue: natural, financial, social, human, material, intellectual, cultural, and health capital.
# The 8 Forms of Capital help Kokonut measure what money alone cannot see.
A regenerative farm creates more than revenue. It can restore soil, strengthen local relationships, train people, preserve culture, build public knowledge, produce food, and create infrastructure that continues to serve the community after the harvest is sold.
Kokonut uses the **8 Forms of Capital** as a value-accounting lens for farm proposals, annual impact reports, MRV workflows, and DAO review. The goal is simple: make every form of value visible enough to discuss, fund, improve, and verify.
Use this page when reviewing farm proposals, writing annual impact reports, or translating farm activity into MRV evidence.
***
## Why this matters
Most agricultural finance sees farms through one narrow lens: money in, money out. Kokonut needs a broader lens because regenerative farms are designed to compound multiple kinds of value at once.
| Without the 8 Forms | With the 8 Forms |
| ----------------------------------------- | -------------------------------------------------------------------------------------- |
| A farm is judged mostly by revenue. | A farm is assessed across ecological, economic, social, cultural, and knowledge value. |
| Public goods are treated as side effects. | Public goods become part of the value model. |
| Impact claims stay vague. | Claims are tied to evidence, metrics, and reporting cycles. |
| DAO reviewers only see the budget. | DAO reviewers can compare risks, benefits, and community outcomes. |
| Replication is difficult. | New farms can learn from comparable value records. |
The 8 Forms do not replace financial analysis. They expand it. A farm still needs budgets, revenue assumptions, execution capacity, and risk controls — but those are not the only forms of value that matter.
***
## Where this fits in the Kokonut Framework
```mermaid theme={null}
flowchart TD
A["Farm proposal"] --> B["Pillars of Value"]
B --> C["8 Forms of Capital"]
C --> D["Common Data Schema"]
D --> E["MRV workflow"]
E --> F["Data Hub + EAS attestations"]
F --> G["Annual impact report"]
G --> H["DAO learning + future proposals"]
```
The relationship is:
| Framework element | Job |
| ------------------------ | -------------------------------------------------------- |
| **Pillars of Value** | Define what the DAO should evaluate. |
| **8 Forms of Capital** | Define how value is categorized and measured. |
| **Common Data Schema** | Captures the baseline farm record needed for comparison. |
| **MRV workflow** | Turns farm activity into structured evidence. |
| **Annual impact report** | Summarizes what changed across the year. |
***
## The eight forms
| Capital form | Plain meaning | Kokonut question |
| ---------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| **Natural** | Soil, water, biodiversity, vegetation, carbon, and ecosystem health | Is the land becoming healthier over time? |
| **Financial** | Revenue, treasury, funding, costs, and public goods allocation | Can the farm sustain operations and distribute value responsibly? |
| **Social** | Trust, relationships, coordination, participation, and community networks | Is the farm strengthening local and network relationships? |
| **Human** | Skills, knowledge, safety, training, and leadership capacity | Are people gaining the capability to operate and replicate regeneration? |
| **Material** | Infrastructure, tools, equipment, built assets, and physical systems | Does the farm have the physical base to keep working? |
| **Intellectual** | Data, documentation, methods, open-source tools, and research | Is the network learning in a way others can reuse? |
| **Cultural** | Stories, traditions, local identity, land memory, and heritage species | Is the farm preserving and renewing cultural connection to land? |
| **Health** | Food quality, worker wellbeing, community nutrition, and safe conditions | Is the farm supporting healthier people and safer work? |
***
## 1. Natural Capital
Natural Capital is the ecological foundation of the farm: soil health, water retention, biodiversity, vegetation, habitat, and ecosystem resilience.
**How Kokonut farms build it**
* Use syntropic planting, cover crops, perennial roots, biodiversity corridors, and the propagation of native species.
* Reduce dependency on synthetic inputs by producing organic amendments and bio-inputs on-site.
* Monitor vegetation health, soil conditions, biodiversity changes, and land-use patterns over time.
**Adelphi example**
Adelphi uses syntropic plots, a biodiversity nursery, at-risk species propagation, biochar, vegetative cover, and satellite vegetation monitoring to make Natural Capital visible.
**Evidence to track**
| Evidence | Possible source |
| ------------------------------------------------------- | ----------------------------------------------- |
| Soil moisture, temperature, and electrical conductivity | Ground sensors or field measurements |
| Vegetation health | NDVI, NDRE, MSAVI, satellite analysis |
| Species count and nursery inventory | Field logs, Silvi records, biodiversity surveys |
| Cover crop and living-root continuity | Farm observations and geospatial records |
| Biochar and organic input use | Biofactory logs and MRV events |
Carbon and biodiversity outcomes should be treated as estimates until supported by a clear methodology, measurement period, and MRV evidence.
***
## 2. Financial Capital
Financial Capital is the monetary layer that lets farms operate, pay people, maintain infrastructure, reinvest, and support public goods.
**How Kokonut farms build it**
* Use DAO-governed capital allocation instead of opaque grant or loan dependency.
* Track crop revenue, egg production, treasury movement, public goods allocations, and operating costs.
* Route funding decisions through proposals, community review, and on-chain execution.
**Adelphi example**
Adelphi’s forecast includes short-cycle crops, medium-cycle crops, long-cycle coconut production, and poultry as recurring production streams. The allocation of public goods is modeled as 10% of gross revenue once revenue is realized.
**Evidence to track**
| Evidence | Possible source |
| ----------------------------- | -------------------------------------------------------- |
| Revenue by crop and cycle | Harvest records, sales records, Data Hub |
| Treasury inflows and outflows | DAO records, Gnosis Chain, Safe transactions |
| Public goods allocation | Proposal reports, impact reports, and accounting records |
| Budget vs. actuals | Farm operations reports |
| Forecast revisions | Harvest forecast updates and MRV actuals |
Forecasts are planning tools, not guaranteed outcomes. Financial Capital should separate projected revenue from verified actuals.
***
## 3. Social Capital
Social Capital is the trust and coordination capacity around the farm: local relationships, contributor networks, governance participation, and community engagement.
**How Kokonut farms build it**
* Create community programs, workshops, open documentation, and local participation pathways.
* Use Guilds to coordinate contributions across technology, impact, governance, communications, finance, and partnerships.
* Track participation, relationships, and contribution records over time.
**Adelphi example**
Adelphi connects Yanny and Neury’s local land stewardship with nearby communities, weekend programming, educational visits, and Kokonut’s broader contributor network.
**Evidence to track**
| Evidence | Possible source |
| ------------------------------- | -------------------------------------------- |
| Community events held | Event logs and attendance records |
| Workshop participation | Training records and surveys |
| Guild contribution records | Charmverse, Guild Points, proposal histories |
| Community feedback | Interviews and annual surveys |
| Local stakeholder relationships | Partnership records and farm reports |
***
## 4. Human Capital
Human Capital is the capability of people: skills, training, safety, leadership, and practical knowledge.
**How Kokonut farms build it**
* Train farm teams in syntropic farming, bio-input production, soil management, poultry systems, data collection, and market strategy.
* Build repeatable training materials that new farms can reuse.
* Improve local capacity to operate regenerative systems without forever relying on external experts.
**Adelphi example**
Adelphi’s gazebo functions as a training and community education space for agroecology, native species, biochar, poultry management, and farm operations.
**Evidence to track**
| Evidence | Possible source |
| ---------------------------- | ----------------------------- |
| Training sessions completed | Attendance logs |
| Skills gained | Pre/post assessments |
| Safety practices | Farm safety records |
| Mentorship activity | Training reports |
| Follow-on community activity | Participant follow-up surveys |
***
## 5. Material Capital
Material Capital is the physical infrastructure that enables the farm to operate: land improvements, tools, buildings, water systems, nursery facilities, poultry infrastructure, and monitoring equipment.
**How Kokonut farms build it**
* Fund critical farm infrastructure through transparent proposals.
* Track construction, maintenance, utilization, and upgrades across development phases.
* Connect infrastructure to production, education, MRV, and community benefit.
**Adelphi example**
Adelphi includes production beds, syntropic plots, nursery and biofactory infrastructure, a poultry system, an education gazebo, mapped farm zones, and geospatial monitoring.
**Evidence to track**
| Evidence | Possible source |
| ----------------------------- | ------------------------------------ |
| Infrastructure completion | Milestone reports and photos |
| Facility utilization | Event logs, production records |
| Maintenance needs | Operations reports |
| Equipment status | Inventory records |
| Infrastructure-linked outputs | Harvests, eggs, seedlings, trainings |
***
## 6. Intellectual Capital
Intellectual Capital is the knowledge that helps the network improve: data, documentation, methodologies, open-source code, agent workflows, research, and lessons learned.
**How Kokonut farms build it**
* Publish documentation, farm data, MRV workflows, schema updates, proposal templates, and operational lessons.
* Build open-source tools that future farms can reuse.
* Use AI agents and the Intelligence Layer to help coordinate reporting, forecasting, verification, and learning.
**Adelphi example**
Adelphi is the reference implementation for the Kokonut Framework: farm data, forecasts, infrastructure records, MRV events, and lessons learned from Adelphi inform future farm replication.
**Evidence to track**
| Evidence | Possible source |
| -------------------------- | ------------------------------------ |
| Documentation improvements | GitHub commits and pull requests |
| Farm data published | Data Hub records and API usage |
| MRV events generated | Registry events and EAS attestations |
| Agent workflows deployed | Agent logs and tool documentation |
| Framework reuse | New farm onboarding records |
***
## 7. Cultural Capital
Cultural Capital is the value carried by stories, traditions, local identity, land memory, heritage crops, and intergenerational knowledge.
**How Kokonut farms build it**
* Document founder stories, local history, and community relationships.
* Preserve native species and heritage crops.
* Create programs that reconnect children, elders, farmers, and contributors to land-based knowledge.
**Adelphi example**
Adelphi’s story begins with Yanny and Neury Hernández returning to land connected to family memory, then turning that land into a regenerative farm and community learning space.
**Evidence to track**
| Evidence | Possible source |
| ----------------------------- | -------------------------------- |
| Founder and community stories | Public documentation |
| Heritage species preserved | Nursery inventory and field logs |
| Seedlings distributed | Distribution records |
| Cultural events or programs | Attendance logs and photos |
| Local knowledge documented | Interviews and reports |
***
## 8. Health Capital
Health Capital is the well-being of people connected to the farm: workers, consumers, families, nearby communities, and contributors.
**How Kokonut farms build it**
* Produce food through organic and regenerative practices.
* Improve access to fresh local produce and protein.
* Maintain safe working conditions and training for farm activities.
* Track health-related claims carefully and avoid unsupported medical or nutrition claims.
**Adelphi example**
Adelphi produces vegetables, fruits, and eggs through a system designed around soil health, biodiversity, poultry integration, and reduced dependence on synthetic inputs.
**Evidence to track**
| Evidence | Possible source |
| ----------------------- | ----------------------------------------------- |
| Food produced locally | Harvest and sales records |
| Egg production | Poultry records |
| Worker safety | Incident reports and safety logs |
| Community food access | Distribution and sales records |
| Health-related outcomes | Surveys or third-party analysis, when available |
Health claims require caution. Kokonut can document food access, production methods, and safety practices, but should avoid claiming superior nutrition or medical outcomes unless supported by testing and credible methodology.
***
## How value becomes evidence
The 8 Forms are only useful if each claim can be connected to evidence. Kokonut uses the MRV workflow to move from farm activity to public records.
```mermaid theme={null}
flowchart LR
A["Farm activity"] --> B["Capital form"]
B --> C["Metric or observation"]
C --> D["MRV payload"]
D --> E["IPFS / Filecoin record"]
E --> F["Farm Registry event"]
F --> G["EAS attestation"]
G --> H["Data Hub + annual impact report"]
```
| Capital form | Example claim | Evidence standard |
| ------------ | ------------------------------------------------- | ----------------------------------------------------------- |
| Natural | Soil and biodiversity are improving | Soil data, field logs, satellite indices, species records |
| Financial | Farm revenue supports operations and public goods | Sales records, treasury transactions, budget reports |
| Social | Community participation is increasing | Event attendance, surveys, Guild contribution records |
| Human | Training increases local capacity | Workshop logs, skills assessments, mentorship records |
| Material | Infrastructure improves production capacity | Build milestones, usage records, maintenance reports |
| Intellectual | Knowledge is reusable by future farms | Documentation, open-source activity, API/data usage |
| Cultural | Heritage species and stories are preserved | Nursery records, story documentation, seedling distribution |
| Health | Local food access improves | Harvest records, distribution data, safety logs |
***
## How DAO reviewers can use the 8 Forms
When reviewing a proposal, ask:
| Question | Why it matters |
| ----------------------------------------------------------- | ------------------------------------------------ |
| Which forms of capital does this proposal affect? | Prevents the DAO from only reviewing the budget. |
| Which claims are estimates, and which are already measured? | Reduces overclaiming and greenwashing risk. |
| What evidence will be collected? | Connects the proposal to MRV. |
| Who is responsible for reporting? | Makes accountability clear. |
| How will results be published? | Ensures value is legible to the network. |
| What could fail? | Keeps risk visible before funds are allocated. |
A strong proposal does not need to maximize all eight forms at once. It should be clear about which forms it affects, how those effects will be measured, and what evidence will be available after execution.
***
## What this framework does not guarantee
The 8 Forms make value easier to see, but they do not remove risk.
| Risk | What to do about it |
| ----------------- | ------------------------------------------------------------------------------------------------- |
| Agricultural risk | Track weather, crop cycles, pest pressure, soil health, and execution milestones. |
| Market risk | Separate projected revenue from actual sales and update forecasts after each cycle. |
| Governance risk | Require clear proposals, accountability, reporting, and community review. |
| Data-quality risk | Define who collects data, when it is collected, and how it is verified. |
| Carbon-claim risk | Treat climate benefits as co-benefits until methodology and verification support stronger claims. |
| Health-claim risk | Avoid medical or nutrition claims unless supported by testing and credible evidence. |
***
## Next steps
Understand the DAO's six evaluation questions before applying the 8 Forms as measurement categories.
See the farm record that makes farms comparable, fundable, governable, and verifiable.
Learn how farm activity becomes structured evidence, public records, and annual impact reporting.
See the first Kokonut farm where the Framework is being applied on real land.
Use the 8 Forms to write clearer farm funding, bounty, Framework upgrade, or partnership proposals.
See how farm practices create circular impact loops that can be measured and improved.
# Methodology Positive Impact
Source: https://kokonut.network/kokonut-framework/framework-components/framework-features/methodology-positive-impact
How Kokonut turns regenerative farming practices into positive-impact claims that can be measured, reported, verified, and improved over time.
# Positive impact only matters when it can be measured.
Kokonut's methodology is built around a simple idea: a farm should improve the land and community it depends on, not deplete them.
That means positive impact cannot remain a slogan. It must be connected to specific practices, specific evidence, and a clear verification workflow that lets DAO members, farm operators, contributors, funders, researchers, and local communities inspect what is actually happening.
Built for farm founders, DAO reviewers, Impact Guild contributors, grant reviewers, regenerative agriculture practitioners, and anyone evaluating Kokonut's impact claims.
5
regeneration principles
Adelphi
live reference farm
This page describes Kokonut's impact methodology and the evidence needed to support positive-impact claims. It should not be used as a carbon-credit methodology, investment guarantee, yield guarantee, or certified environmental audit unless the relevant farm data has been verified through the MRV workflow and in accordance with the applicable reporting standards.
***
## What does positive impact mean in Kokonut
Positive impact means a farm can show evidence that its operations are improving ecological, economic, and community conditions over time.
| Impact area | What Kokonut wants to improve | Evidence needed |
| ---------------- | ------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------- |
| Soil | Organic matter, water retention, nutrient cycling, and biological activity | Soil observations, moisture data, electrical conductivity, field logs, input records |
| Biodiversity | Species diversity, habitat, pollinator support, and native species propagation | Species inventory, geospatial records, nursery logs, satellite vegetation indices |
| Food production | Crop diversity, harvest reliability, and local food access | Planting records, crop cycle logs, harvest records, market/distribution records |
| Community value | Jobs, training, public goods, local ownership, skill-building | Payroll or role records, event attendance, public goods allocation, contributor reports |
| Governance trust | Clear decisions, transparent funding, public accountability | Proposal records, DAO votes, Data Hub records, EAS attestations, annual reports |
In Kokonut, positive impact is not one metric. It is a relationship between regenerative practice, local benefit, and verifiable evidence.
***
## Impact loop
The methodology works as a circular farm system. Each practice should feed another part of the farm instead of becoming waste, dependency, or extraction.
```mermaid theme={null}
flowchart TD
A["Syntropic planting + cover crops"] --> B["Living soil\nwater retention · roots · biomass"]
B --> C["Biodiversity\npollinators · habitat · microorganisms"]
C --> D["Healthier production\nshort · medium · long-cycle crops"]
D --> E["Revenue + food access\nlocal markets · community benefit"]
E --> F["Jobs + training + public goods"]
F --> G["More capacity to maintain the farm"]
G --> A
H["Poultry manure"] --> I["Humic acids + organic urea"]
I --> B
J["Bamboo + crop residues"] --> K["Biochar + mulch + organic inputs"]
K --> B
A --> L["MRV events"]
B --> L
C --> L
D --> L
F --> L
L --> M["Kokonut Hub + EAS attestations"]
M --> N["DAO decisions + annual reports"]
```
The loop is useful only if each stage can be observed. That is why the methodology connects directly to [Measurement, Reporting, and Verification](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification).
***
## The five positive-impact pathways
Cover crops, living roots, compost, biochar, manure processing, and reduced disturbance are used to build soil function rather than degrade it after each harvest.
Multi-strata planting, native species propagation, nursery work, pollinator habitat, and reduced synthetic inputs make biodiversity part of the production system.
Poultry manure, bamboo, coconut husks, crop residues, pruning biomass, and other farm outputs are turned back into fertility, mulch, feed, or materials.
The farm is designed to create local jobs, training opportunities, food access, public goods funding, and community participation, rather than extracting value from the land.
Impact claims are connected to Data Hub records, field logs, MRV payloads, IPFS records, EAS attestations, and annual reporting workflows.
Positive impact is not a one-time status. It should improve as the farm learns from field data, crop cycles, DAO review, and community feedback.
***
## From practice to evidence
| Farm practice | Positive-impact claim | Verification pathway |
| ------------------------------- | ----------------------------------------------------- | ------------------------------------------------------------------------ |
| Cover crops and living roots | Soil is protected, and erosion risk is reduced | Field photos, plot logs, vegetation indices, erosion observations |
| Biochar and composted inputs | Soil fertility and water retention are being improved | Input records, soil observations, moisture data, and annual reporting |
| Multi-strata syntropic planting | Biodiversity and production resilience are improving | Geospatial plant records, crop diversity logs, satellite NDVI/NDRE/MSAVI |
| Poultry integration | Waste becomes fertility and daily food production | Hen records, egg records, manure-processing logs, farm input records |
| Native species nursery | At-risk and native species are being propagated | Nursery inventory, distribution records, GPS/per-plant records |
| Education and training | Knowledge is spreading beyond the farm | Workshop records, attendance, community reports, contributor logs |
| Public goods allocation | Revenue supports local and ecosystem benefits | Treasury records, proposal reports, and public goods allocation logs |
This structure reduces the risk of greenwashing because every claim must ultimately point to a record.
***
## What should be measured?
The methodology becomes credible when it creates repeated observations across time.
| Category | Example indicators | Why it matters |
| -------------- | -------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| Soil and water | Soil moisture, electrical conductivity, soil temperature, and field observations | Shows whether the land is becoming more resilient and easier to manage |
| Vegetation | NDVI, NDRE, ReCI, MSAVI, canopy development, ground cover | Shows plant health, cover, and ecological trend over time |
| Biodiversity | Species inventory, native species propagation, pollinator observations | Shows whether the farm is becoming more diverse and habitat-rich |
| Production | Crop cycle records, harvest volume, loss rate, revenue, market channel | Shows whether regenerative practices are supporting real production |
| Community | Jobs, training, public goods allocation, events, and local participation | Shows whether value is reaching people around the farm |
| Governance | Proposals, funding decisions, milestones, reports, attestations | Shows whether capital and decisions are accountable |
Climate and carbon outcomes should be treated as co-benefits until supported by appropriate methodology, soil data, vegetation data, reporting periods, and verification. Estimates can help with planning, but they should not be presented as certified carbon credits or guaranteed sequestration.
***
## In practice: Adelphi
[Adelphi](/ecosystem-wiki/kokonut-farms/adelphi/summary) is Kokonut's live reference farm for this methodology.
The farm system includes syntropic crop beds, agroforestry species, native species propagation, a nursery and biofactory, free-range poultry, training infrastructure, geospatial monitoring, and public MRV records.
| Methodology element | Adelphi implementation |
| ------------------- | ----------------------------------------------------------------------------------------- |
| Syntropic planting | Two dedicated syntropic plots and multi-cycle crop planning |
| Soil regeneration | Bamboo biochar, cover crops, humic acids, organic urea, and reduced synthetic dependency |
| Biodiversity | 12+ at-risk species, native species nursery, agroforestry species, and pollinator habitat |
| Circularity | Poultry manure returns to crop beds; bamboo and crop residues become soil inputs |
| Community benefit | Jobs, education gazebo, weekend programming, free native seedlings, local food production |
| MRV | Field logs, satellite indices, farm data records, Kokonut Hub, and EAS attestations |
[Explore Adelphi's infrastructure →](/ecosystem-wiki/kokonut-farms/adelphi/crops-biodiversity-and-infrastructure)
***
## How does a positive impact become a public record
Kokonut's MRV workflow turns farm activity into evidence that can be inspected and used.
```mermaid theme={null}
flowchart TD
A["Farm activity\nplanting · harvest · soil · satellite · training"] --> B["Structured record\nFarm Registry payload"]
B --> C["IPFS / Filecoin\ncontent-addressed evidence"]
C --> D["Farm Registry event"]
D --> E["EAS attestation"]
E --> F["Kokonut Hub\npublic farm record"]
F --> G["Annual report\nEBF impact + CRISP risk"]
G --> H["DAO, funder, contributor, and partner decisions"]
```
This is the difference between an impact claim and a verifiable impact claim.
***
## What this methodology does not guarantee
Positive-impact methodology improves the conditions for regeneration, but it does not remove risk.
| Risk | Why it still matters |
| ----------------- | --------------------------------------------------------------------------------------------- |
| Weather risk | Drought, storms, heat, rainfall timing, and local climate conditions can affect outcomes |
| Execution risk | Practices only work if the farm team implements them consistently and records them accurately |
| Market risk | Revenue depends on price, demand, distribution, certification, and buyer relationships |
| Data-quality risk | Bad data can make good work hard to verify, or weak claims look stronger than they are |
| Carbon-claim risk | Carbon language requires methodology, measurement, reporting periods, and verification |
| Governance risk | DAO funding and reporting depend on clear proposals, accountability, and follow-through |
Do not treat this methodology as proof by itself. Treat it as the operating logic for producing evidence that can later be reviewed, verified, and improved.
***
## How to use this page
Use this methodology to design farm operations that generate both production and evidence from the beginning.
Use it to evaluate whether a farm proposal has credible regenerative practices and a realistic verification path.
Use it to decide what data to request, what claims to verify, and where evidence is still missing.
Use it to understand how Kokonut connects regenerative practice to public reporting and accountability.
***
## Next steps
The agricultural logic behind the positive-impact methodology.
The operating principles behind soil cover, biodiversity, animal integration, perennial systems, and organic inputs.
How farm activity becomes structured evidence, IPFS records, EAS attestations, and public reporting.
The live farm infrastructure that produces crops, biodiversity, poultry, soil, and MRV evidence.
How the DAO evaluates whether a farm creates value worth funding.
EBF and CRISP — the external impact and risk frameworks Kokonut uses for reporting.
# Pillars of Value
Source: https://kokonut.network/kokonut-framework/framework-components/pillars-of-value
The six questions Kokonut uses to evaluate whether a farm creates real community, ecological, financial, and public goods value.
# The Pillars of Value help the DAO decide what is worth funding.
A farm proposal can look promising on paper and still fail to create durable community value. The **Pillars of Value** are Kokonut's evaluation lens for separating short-term financial return from deeper, lasting value.
They help DAO members, Guild Stewards, grant reviewers, farm operators, and contributors answer one question before funding, operating, or reporting on a farm:
> Does this farm create genuine value for people, land, governance, and public goods — or only revenue for funders?
Use this page when reviewing farm proposals, preparing a Kokonut Development Proposal, writing grants, or translating farm activity into annual impact reports.
The Pillars of Value are an evaluation framework, not a guarantee of financial return, carbon credit issuance, farm performance, or funding approval. A farm still needs complete data, clear budgets, realistic assumptions, local execution capacity, and MRV evidence.
***
## What the pillars do
The pillars convert a farm story into a reviewable case for community funding.
| Without the pillars | With the pillars |
| --------------------------------------------------- | --------------------------------------------------------------------------------- |
| A proposal says the farm will “help the community.” | The proposal names who benefits, how much, and how outcomes will be measured. |
| Revenue is treated as the main proof of value. | Revenue is evaluated alongside ecology, jobs, training, public goods, and risk. |
| Risks are minimized or hidden. | Risks are documented before funding and tied to mitigation plans. |
| Impact is described after the fact. | Impact categories are defined at the time of proposal and tracked through MRV. |
| Each farm is a one-off story. | Farms become comparable through shared schema fields, pillars, and capital forms. |
The Common Data Schema provides the farm record. The Pillars of Value interpret that record. The 8 Forms of Capital help measure the value created. MRV turns operational activity into evidence.
***
## When the pillars are applied
| Moment | How the pillars are used | Main reviewer |
| ------------------ | -------------------------------------------------------------------- | --------------------------------- |
| Farm discovery | Decide whether a farm is worth deeper review | Farm operator, Impact Guild |
| Proposal drafting | Structure the value case for a Kokonut Development Proposal | Proposal author, Guild Stewards |
| DAO review | Help members evaluate whether treasury support is justified | DAO members |
| Phase I planning | Convert the approved thesis into baseline data and diagnostics | Farm team, Impact Guild |
| Operations | Track whether the farm is delivering what it promised | Farm operators, contributors |
| Annual reporting | Translate farm activity into impact reporting and EBF-style evidence | Impact Guild, MRV contributors |
| Grant applications | Explain value creation to external partners and grant reviewers | Governance, Finance, Partnerships |
***
## The six pillars
| Pillar | Core question | What reviewers need to see | Main schema connection |
| ---------------- | ----------------------------------------------- | ------------------------------------------------------------------------------ | ----------------------------------------------------------- |
| **WHAT** | What value is the farm designed to create? | Clear objectives, crop mix, ecological goals, community outcomes | `project_summary`, `revenue_streams` |
| **WHO** | Who benefits directly and indirectly? | Operators, workers, neighbors, markets, DAO members, future farms | `target_market`, `local_problem` |
| **HOW MUCH** | At what scale will value be created? | Quantified land, jobs, revenue, public goods, training, biodiversity, harvests | `land_size`, `forecasted_budget`, `public_goods_allocation` |
| **CONTRIBUTION** | What tangible contributions does the farm add? | Ecological, economic, social, cultural, governance, and knowledge outputs | `proposed_solution` |
| **RISK** | What could fail, and how will it be mitigated? | Agronomic, climate, market, governance, operational, data, and financial risks | Risk assessment, CRISP, EBF, milestones |
| **PUBLIC GOODS** | What community benefit is built into the model? | Allocation percentage, activities, beneficiaries, reporting path | `public_goods_allocation` |
***
## 1. WHAT — objective, goals, and benefits
**Core question:** What is the farm trying to produce, restore, teach, or prove?
This pillar establishes the farm's reason for existing beyond financial return. A strong answer explains what agricultural, ecological, economic, and community outcomes the farm is designed to produce.
### A strong WHAT answer includes
* Crop mix and why it fits the land, climate, community, and market
* Ecological restoration goals such as soil regeneration, biodiversity, water retention, or native species propagation
* Community development goals such as jobs, food access, training, or local ownership
* Development phase and expected timeline
* How the farm supports the Kokonut mission
### Adelphi example
Adelphi establishes a **15,725 m² regenerative agro-ecological production model** in Monte Plata, Dominican Republic. It combines short-cycle lettuce, medium-cycle passion fruit, long-cycle coconut, native species conservation, organic education, and market access into one working farm system.
[See Adelphi Summary →](/ecosystem-wiki/kokonut-farms/adelphi/summary)
***
## 2. WHO — direct and indirect beneficiaries
**Core question:** Who is affected if the farm succeeds?
This pillar maps the full circle of stakeholders: not only farm founders and investors, but workers, neighboring communities, market customers, learners, DAO members, local ecosystems, and future farms that will reuse the methodology.
### Beneficiary categories to document
| Beneficiary | What to document |
| ---------------- | --------------------------------------------------------------------------- |
| Farm operators | Founders, managers, ownership, responsibilities, and income model |
| Workers | Jobs created, training, wages, safety, continuity |
| Local community | Nearby families, children, elders, schools, visitors, partner organizations |
| Market customers | Buyers, local consumers, organic markets, supermarkets, and restaurants |
| DAO members | Governance rights, exposure, reporting rights, treasury implications |
| Future farms | Lessons, reusable data, templates, MRV records, methodology improvements |
| Ecosystems | Soil, water, biodiversity, local species, carbon co-benefits |
### Adelphi example
Adelphi directly supports Yanny and Neury Hernández, seven community jobs, and the batey and Haty communities near Gonzalo. Indirect beneficiaries include Monte Plata organic market customers, DAO members, neighboring communities receiving native seedlings, and future Kokonut farms that learn from Adelphi's implementation.
***
## 3. HOW MUCH — quantitative impact
**Core question:** At what scale will the farm create value?
This pillar turns broad impact claims into numbers. A proposal that says “we will create jobs” or “restore land” is not enough; reviewers need measurable baselines, forecast assumptions, and actuals that can be tracked over time.
### Metrics to quantify
| Metric | Why it matters | Evidence source |
| ----------------------- | -------------------------------- | ------------------------------------------- |
| Land under management | Shows physical scope | Common Data Schema, GPS records |
| Agricultural area | Shows a productive area | Farm mapping, Silvi, Data Hub |
| Jobs | Shows livelihood impact | Payroll, field logs, and DAO reports |
| Projected revenue | Shows financial viability | Harvest forecast, market assumptions |
| Public goods allocation | Shows community commitment | Proposal, revenue records, reports |
| Training participants | Shows human capital growth | Attendance logs, event reports |
| Species conserved | Shows biodiversity contribution | Nursery inventory, field records |
| Harvests | Shows production reality | Kokonut Hub, MRV events |
| Climate co-benefits | Shows possible carbon/soil value | Soil tests, vegetation indices, methodology |
Forecasts are planning assumptions. They should be compared against actual harvests, sales, costs, weather conditions, and MRV records before being treated as performance claims.
### Adelphi example
Current Adelphi planning metrics include a total area of 15,725 m², 13,838 m² of agricultural area, 7 jobs, 110 hens producing about 100 eggs per day, 12+ at-risk native species, and projected annual gross revenue based on crop forecasts.
[Read the harvest forecast →](/ecosystem-wiki/kokonut-farms/adelphi/crops-and-harvest-forecast)
***
## 4. CONTRIBUTION — tangible ecosystem contributions
**Core question:** What does the farm add that would not exist without it?
Contribution captures value that does not always appear on a balance sheet: ecological restoration, community learning, cultural continuity, shared tools, local infrastructure, open data, and governance capacity.
### Contribution categories
| Category | Examples |
| ---------- | ------------------------------------------------------------------------------------------------- |
| Ecological | Soil regeneration, biodiversity restoration, watershed protection, and native species propagation |
| Economic | Jobs, local market development, diversified income, and reduced input dependency |
| Social | Community workshops, gathering spaces, educational programs, and knowledge transfer |
| Cultural | Native food varieties, land stewardship stories, and intergenerational learning |
| Governance | Community-owned agriculture, transparent funding, DAO reporting, proposal accountability |
| Knowledge | Farm records, open-source documentation, MRV data, implementation lessons |
### Adelphi example
Adelphi contributes biochar soil regeneration, free native seedling distribution, community workshops, weekend education programs, a women-led farm governance story, and a reference implementation for future Kokonut farms.
***
## 5. RISK — risks and mitigation
**Core question:** What could fail, and what has the farm designed to reduce that risk?
A strong proposal does not hide uncertainty. It identifies risks early and provides reviewers with a practical mitigation plan.
| Risk category | What can go wrong | Mitigation examples |
| ------------- | ----------------------------------------------------------- | ---------------------------------------------------------------------- |
| Agronomic | Crop failure, pests, disease, and low soil fertility | Crop diversity, syntropic design, soil monitoring, bioinputs |
| Climate | Drought, flooding, storms, and heat stress | Soil cover, water retention, resilient crop selection, monitoring |
| Market | Lower prices, weak demand, buyer concentration | Multiple revenue streams, local sales, organic channels |
| Operational | Key-person dependency, labor gaps, training gaps | Guild support, documentation, training, phased milestones |
| Financial | Revenue shortfall, cost overruns, liquidity constraints | Milestone-gated funding, conservative forecasts, transparent reporting |
| Governance | Proposal delays, unclear accountability, and weak reporting | Required proposal fields, DAO review, Guild oversight |
| Data quality | Incomplete records, weak MRV, unverifiable claims | Farm Registry payloads, Data Hub, EAS attestations, field logs |
CRISP and EBF can support risk and impact assessment, but farms should avoid treating carbon or ecological claims as verified until the methodology, field data, and reporting process support them.
### Adelphi example
Adelphi's risks include delayed long-cycle coconut revenue, weather variability, certification timelines, market access, and execution complexity. Its mitigations include short-cycle lettuce revenue, multi-crop diversification, syntropic soil cover, on-site bioinputs, poultry integration, and public MRV records.
***
## 6. PUBLIC GOODS — community benefit allocation
**Core question:** What community benefit is built into the revenue model?
Kokonut farms should not treat public benefit as an afterthought. The public goods pillar documents which community activities are funded, who they serve, and how they are reported.
### Public goods funding can support
* Community workshops and agro-ecological training
* Free native and endangered seedling distribution
* Endangered species nursery operations
* Educational programs for children, elders, and nearby communities
* Maintenance of shared community spaces
* Environmental restoration beyond the farm boundary
* Open documentation, data, and methodology improvements
### Adelphi example
Adelphi allocates **10% of gross revenue** toward public goods, including workshops, native species distribution, education programs, the gazebo, and biodiversity nursery operations. These activities should be reported separately from commercial revenue and tied to the Data Hub or annual impact reporting.
***
## How the pillars connect to the Framework
```mermaid theme={null}
flowchart TD
A["Common Data Schema"] --> B["Pillars of Value"]
B --> C["8 Forms of Capital"]
C --> D["MRV records"]
D --> E["Data Hub + EAS attestations"]
E --> F["DAO review + annual reporting"]
F --> G["Better farm decisions"]
G --> B
B --> H["Farm funding proposals"]
B --> I["Grant applications"]
B --> J["Phase planning"]
B --> K["Impact reports"]
```
| Framework component | Role |
| ------------------- | ------------------------------------------------------------------------------------------------------------- |
| Common Data Schema | Provides the required farm record and baseline data |
| Pillars of Value | Interprets whether the farm creates broad, durable value |
| 8 Forms of Capital | Measures value across natural, financial, social, human, material, intellectual, cultural, and health capital |
| MRV workflow | Turns activity into structured evidence and public records |
| DAO governance | Decides whether the value case justifies funding, execution, or continued support |
***
## Relationship to the 8 Forms of Capital
The Pillars of Value define **what** to evaluate. The 8 Forms of Capital define **how** to measure the value that appears across a farm system.
| Pillar | Capital forms are most often involved |
| ------------ | ---------------------------------------------- |
| WHAT | Natural, Financial, Material, Health |
| WHO | Social, Human, Cultural, Health |
| HOW MUCH | Financial, Material, Natural, Human |
| CONTRIBUTION | Natural, Social, Human, Cultural, Intellectual |
| RISK | All capital forms, depending on exposure |
| PUBLIC GOODS | Social, Human, Cultural, Natural, Intellectual |
[Read the 8 Forms of Capital →](/kokonut-framework/framework-components/framework-features/8-forms-of-capital)
***
## Proposal readiness check
A farm is not ready for a DAO funding proposal until it can answer every pillar with enough specificity for review.
| Readiness question | Ready when... |
| --------------------------- | --------------------------------------------------------------------------------------------------- |
| WHAT is clear? | The farm explains what it will produce, restore, teach, or prove. |
| WHO is clear? | Direct and indirect beneficiaries are named. |
| HOW MUCH is clear? | Land, jobs, revenue, public goods, and impact baselines are quantified. |
| Is the contribution clear? | The farm explains what it adds beyond private revenue. |
| Is RISK clear? | Risks are named with practical mitigations. |
| Are public goods clear? | Allocation percentage, activities, beneficiaries, and the reporting process are defined. |
| Is the evidence path clear? | The proposal explains how progress will be tracked through MRV, Data Hub, reports, or attestations. |
| Is accountability clear? | Responsible people, Guilds, milestones, and reporting duties are named. |
If any pillar is vague, the proposal should remain in drafting. A weak pillar is usually a sign that the farm needs more discovery, budgeting, stakeholder mapping, or MRV planning before asking the DAO for support.
***
## Common weak answers and stronger alternatives
| Weak answer | Stronger answer |
| ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| “The farm will help the community.” | “The farm will create seven jobs, host monthly workshops, distribute native seedlings, and allocate 10% of gross revenue to public goods.” |
| “We will grow organic food.” | “The crop plan includes short-cycle lettuce, medium-cycle passion fruit, long-cycle coconut, and free-range eggs with harvest records published to the Data Hub.” |
| “The farm will restore nature.” | “Restoration will be tracked through soil monitoring, ground cover, biodiversity inventory, and vegetation indices.” |
| “Risks are low.” | “Primary risks are weather, certification delays, market access, and long-cycle payback; each has a mitigation plan.” |
| “Impact will be reported.” | “Farm activity will be logged as structured records, connected to MRV events, and included in annual impact reporting.” |
***
## Next steps
The 13 fields every farm needs before it can be funded, governed, verified, or compared.
The measurement framework that turns broad value into capital-level metrics.
How farm activity becomes structured evidence, public records, and impact reports.
Use the Farm Funding template to turn these six pillars into a reviewable DAO proposal.
See how the pillars show up in Kokonut's first live farm implementation.
Explore CRISP and EBF as supporting frameworks for risk and impact reporting.
# Sustainable Development Goals
Source: https://kokonut.network/kokonut-framework/framework-features/Sustainable-Development-Goals
How the Kokonut Framework maps regenerative farm activity to SDGs through evidence, MRV, 8 Forms of Capital, and annual reporting.
# Kokonut uses the SDGs as an evidence map, not a marketing label.
The Kokonut Framework maps community-owned regenerative farms to the United Nations Sustainable Development Goals so DAO members, grant reviewers, partners, researchers, and local communities can understand what a farm is trying to improve — and what evidence is needed to support each claim.
Kokonut does **not** treat every SDG claim as equally mature. Some outcomes are directly produced by every Kokonut Framework farm and can be tracked through farm records, MRV workflows, and annual reporting. Others are real potential co-benefits, but depend on location, scale, maturity, methodology, and data quality.
Use this page when writing proposals, preparing grant reports, evaluating farm impact, or deciding which claims need MRV evidence.
***
## SDG contribution at a glance
| Tier | SDGs | Evidence maturity | How to report it |
| ------------------ | ----------------------------------------- | ----------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| **Primary SDGs** | 1, 2, 5, 8, 15 | Directly connected to Kokonut's farm model and measurable through farm operations | Report with farm records, MRV events, annual impact reporting, and Data Hub references |
| **Secondary SDGs** | 3, 4, 6, 7, 9, 10, 11, 12, 13, 14, 16, 17 | Conditional or indirect; it depends on farm maturity, location, partners, and methodology | Report as co-benefits unless evidence is strong enough for direct claims |
SDG alignment is not the same as verified impact. A farm can align with an SDG through its design, but it should only claim verified contribution when the activity, metric, evidence source, and reporting period are clear.
***
## How SDG claims become evidence
```mermaid theme={null}
flowchart TD
A["Farm activity"] --> B["Framework category"]
B --> C["SDG outcome"]
C --> D["Evidence source"]
D --> E["MRV payload"]
E --> F["IPFS / Filecoin record"]
F --> G["Farm Registry event"]
G --> H["EAS attestation"]
H --> I["Data Hub + annual report"]
I --> J["DAO members, grant reviewers, partners, communities"]
```
The evidence standard is simple: every SDG claim should answer **what happened, where it happened, who benefited, how it was measured, and where the record can be inspected**.
[Read the MRV methodology →](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification)
***
## Where SDGs fit inside the Kokonut Framework
Defines the farm model, baseline data, development phases, regeneration principles, and value categories.
Translates farm activity into natural, financial, social, human, material, intellectual, cultural, and health value.
Turns farm activity into structured evidence, public records, attestations, and annual impact reports.
| Framework layer | Role in SDG reporting |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Common Data Schema** | Captures the baseline farm record: land, location, crops, governance, funding, market, and public goods commitments |
| **Pillars of Value** | Helps DAO reviewers evaluate what the farm is trying to create, who benefits, how much, and what risks exist |
| **8 Forms of Capital** | Categorizes value beyond revenue, so SDG claims are not reduced to money alone |
| **5 Principles of Regeneration** | Grounds environmental SDG claims in practical farm methods |
| **MRV workflow** | Converts farm activity into evidence that can be inspected and reported |
***
## SDG map
| SDG | Kokonut relationship | Evidence maturity |
| --------------------------------------------------- | ------------------------------------------------------------------------------------- | ------------------------------ |
| **SDG 1 — No Poverty** | Jobs, income resilience, public goods allocation, farm revenue circulation | Primary |
| **SDG 2 — Zero Hunger** | Diversified local food production, harvests, eggs, resilient crop cycles | Primary |
| **SDG 3 — Good Health and Well-being** | Access to fresh food, nature, community programming, reduced synthetic input exposure | Secondary |
| **SDG 4 — Quality Education** | Farm workshops, open-source documentation, regenerative agriculture training | Secondary |
| **SDG 5 — Gender Equality** | Women-led ownership and governance participation where implemented | Primary |
| **SDG 6 — Clean Water and Sanitation** | Soil cover, erosion control, runoff reduction, watershed health | Secondary |
| **SDG 7 — Affordable and Clean Energy** | Reduced synthetic-input dependence and potential future renewable systems | Secondary |
| **SDG 8 — Decent Work and Economic Growth** | Farm jobs, skills, local enterprise, regenerative work pathways | Primary |
| **SDG 9 — Industry, Innovation and Infrastructure** | Farm Registry, Data Hub, AI agents, open MRV infrastructure | Secondary |
| **SDG 10 — Reduced Inequalities** | Contribution paths, Guilds, local participation, public goods allocation | Secondary |
| **SDG 11 — Sustainable Cities and Communities** | Community hubs, food access, educational spaces, resilient local systems | Secondary |
| **SDG 12 — Responsible Consumption and Production** | Organic inputs, closed-loop fertility, local markets, waste reduction | Secondary |
| **SDG 13 — Climate Action** | Biochar, agroforestry, vegetation health, soil regeneration, resilience | Secondary / climate co-benefit |
| **SDG 14 — Life Below Water** | Reduced runoff and possible watershed-to-coast benefits where relevant | Secondary |
| **SDG 15 — Life on Land** | Biodiversity, agroforestry, living roots, erosion control, nursery propagation | Primary |
| **SDG 16 — Peace, Justice and Strong Institutions** | Transparent DAO governance, proposal processes, public records | Secondary |
| **SDG 17 — Partnerships for the Goals** | Public goods funders, MRV partners, open-source collaborators, local partnerships | Secondary |
The five primary SDGs are the baseline for Kokonut Framework farms. Secondary SDGs can become stronger over time, but only when the farm collects the right evidence and reports it consistently.
***
## Primary SDGs
### SDG 1 — No Poverty
Kokonut farms contribute to poverty reduction by creating productive local assets: jobs, skills, farm revenue, public goods funding, and community-owned infrastructure.
| What to measure | Evidence source |
| ------------------------- | -------------------------------------------------------------------------------------------- |
| Jobs created or supported | Employment records, role descriptions, payroll, or compensation records |
| Farm revenue | Sales records, harvest reports, Data Hub entries |
| Public goods allocation | DAO proposal, treasury record, farm revenue report |
| Local income resilience | Annual impact report, community interviews, and household income assessments where available |
**Claim standard:** Do not claim poverty reduction only because a farm exists. Show the job records, revenue activity, public goods allocation, and who benefited.
***
### SDG 2 — Zero Hunger
Kokonut farms contribute to food security by producing a variety of crops across short, medium, long, and continuous cycles.
| What to measure | Evidence source |
| ------------------------ | ----------------------------------------------------------------------- |
| Crop production | Harvest records, crop cycle logs, yield reports |
| Food diversity | Species lists, crop plans, harvest categories |
| Local distribution | Sales records, distribution records, buyer/community records |
| Resilience of production | Crop cycle performance across seasons, losses, and actuals vs. forecast |
**Claim standard:** Report food production through actual harvests and distribution records, not only crop plans.
***
### SDG 5 — Gender Equality
Kokonut farms contribute to gender equality when ownership, leadership, training, decision-making, and work opportunities are accessible and documented.
| What to measure | Evidence source |
| ----------------------------- | ------------------------------------------------------------------ |
| Ownership and leadership | Operator records, governance records, founder/team documentation |
| Decision-making participation | Meeting notes, DAO proposals, and role assignments |
| Training access | Workshop attendance, training logs, participant records |
| Economic participation | Employment records, compensation records, and contribution records |
**Claim standard:** Gender equality claims should be tied to real leadership, participation, and benefit-sharing data.
***
### SDG 8 — Decent Work and Economic Growth
Kokonut farms contribute to decent work by creating regenerative agriculture roles, skill-building pathways, and locally rooted economic activity.
| What to measure | Evidence source |
| ----------------------- | --------------------------------------------------------------------------- |
| Number of jobs | Employment records and role descriptions |
| Quality of work | Compensation, safety practices, training, continuity, and role progression |
| Skills developed | Training logs, workshop records, and certifications were available |
| Local economic activity | Farm revenue, supplier records, market records, and public goods allocation |
**Claim standard:** Count jobs carefully, distinguish full-time, part-time, seasonal, and bounty-based work, and do not treat projected work as actual employment.
***
### SDG 15 — Life on Land
Kokonut farms contribute to terrestrial ecosystem health through agroforestry, biodiversity, living roots, soil protection, erosion control, nursery propagation, and ecological monitoring.
| What to measure | Evidence source |
| ---------------------- | --------------------------------------------------------------------------------------- |
| Biodiversity | Species inventory, nursery logs, field observations |
| Vegetation health | Satellite indices such as NDVI, NDRE, and MSAVI, where available |
| Soil condition | Soil observations, soil tests, organic matter, moisture, and EC readings were available |
| Erosion and land cover | Ground cover records, drone imagery, field logs, photos |
| Regenerative practices | Biochar records, syntropic plot logs, crop rotation, and planting records |
**Claim standard:** Life-on-land claims should be connected to species records, soil/vegetation evidence, and observable land-management practices.
***
## Secondary SDGs and co-benefits
Secondary SDGs are not less important. They are simply more dependent on farm maturity, implementation depth, and verification quality.
| SDG | How Kokonut may contribute | What would make the claim stronger |
| ----------------------------------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| **3 — Good Health and Well-being** | Fresh food access, community gathering, nature exposure | Distribution records, health partner data, program attendance, nutrition methodology |
| **4 — Quality Education** | Farm workshops, open documentation, training programs | Attendance logs, curriculum, learning outcomes, participant feedback |
| **6 — Clean Water and Sanitation** | Erosion control, runoff reduction, soil cover | Water testing, runoff monitoring, watershed data |
| **7 — Affordable and Clean Energy** | Reduced synthetic-input dependence, possible renewable systems | Energy baseline, renewable system deployment records, fuel/input reduction data |
| **9 — Industry, Innovation and Infrastructure** | Farm Registry, Data Hub, AI agents, open-source MRV | API usage, uptime, integrations, developer documentation, third-party use |
| **10 — Reduced Inequalities** | Contribution paths, Guild Points, local access, public goods allocation | Participation records, contribution records, benefit distribution data |
| **11 — Sustainable Cities and Communities** | Community hub, education space, local resilience | Event records, local service records, community feedback |
| **12 — Responsible Consumption and Production** | Organic inputs, closed-loop fertility, waste reduction | Input logs, waste records, certification status, buyer/distribution records |
| **13 — Climate Action** | Biochar, agroforestry, soil building, vegetation resilience | Carbon methodology, soil data, biomass data, reporting period, third-party review |
| **14 — Life Below Water** | Reduced runoff and land-sea awareness where watersheds connect to coast | Water quality, watershed mapping, coastal partner records |
| **16 — Peace, Justice and Strong Institutions** | Transparent DAO governance, proposal records, on-chain attestations | Governance records, proposal outcomes, dispute logs, auditability |
| **17 — Partnerships for the Goals** | Public goods funders, MRV partners, local partners, open-source collaborators | Partnership agreements, deliverables, joint reports, contribution records |
Climate and carbon claims require a higher evidence standard. Biochar, agroforestry, and syntropic farming can provide climate co-benefits, but carbon outcomes should not be treated as verified carbon credits without a methodology, measurement, a reporting period, and verification.
***
## In practice: Adelphi
Adelphi is Kokonut's current reference farm for SDG evidence. It focuses on five primary SDGs:
| SDG | Adelphi evidence direction |
| --------------------------- | -------------------------------------------------------------------------------- |
| **SDG 1 — No Poverty** | Jobs, farm revenue forecast and actuals, public goods allocation |
| **SDG 2 — Zero Hunger** | Crop cycles, harvest records, egg production, and local food distribution |
| **SDG 5 — Gender Equality** | Women-led ownership, management, and community leadership |
| **SDG 8 — Decent Work** | Seven documented roles, training, farm operations, and regenerative skills |
| **SDG 15 — Life on Land** | Biodiversity nursery, syntropic plots, vegetation monitoring, and soil practices |
[See Adelphi's SDG evidence page →](/ecosystem-wiki/kokonut-farms/adelphi/sustainable-development-goals)
***
## How to use this page
Use the primary SDGs to define your farm's core impact claims, then list which evidence will be collected during operations.
Ask whether each SDG claim has a metric, baseline, evidence source, responsible reporter, and reporting period.
Treat the primary SDG map as the baseline due diligence structure and inspect the farm's Data Hub, proposal, and annual reports.
Use this page as a reporting checklist: activities only become impact claims when they are documented and reviewed.
***
## SDG claim checklist
Before publishing an SDG claim, make sure it answers:
| Question | Why it matters |
| ------------------------------------- | -------------------------------------------------- |
| What activity created the outcome? | Prevents vague sustainability language |
| Which SDG and target does it support? | Keeps the claim specific |
| Is it primary or secondary? | Prevents overstating co-benefits |
| What metric will be tracked? | Makes progress measurable |
| What is the baseline? | Shows what changed |
| What evidence source supports it? | Makes the claim inspectable |
| Who is responsible for reporting? | Creates accountability |
| How often is it updated? | Keeps the record alive |
| Is it a forecast or an actual? | Prevents projections from being treated as results |
| What could invalidate the claim? | Makes risks visible |
***
## Next steps
See how the five primary SDGs are mapped to live farm activity, evidence sources, and annual reporting.
Learn how farm records become public evidence through MRV payloads, IPFS/Filecoin, Farm Registry events, and EAS attestations.
Understand how Kokonut measures value beyond revenue across natural, financial, social, human, material, intellectual, cultural, and health capital.
See how regenerative practices create reinforcing impact loops and what evidence is needed before making strong claims.
Estimate potential SDG contribution before converting assumptions into proposal requirements and MRV evidence.
Use the SDG map to write stronger farm funding proposals with clear evidence commitments.
# Kokonut Impact Calculator
Source: https://kokonut.network/kokonut-framework/impact-calculator
A scenario-planning tool for estimating how regenerative farm design choices may map to SDG alignment, revenue potential, public goods allocation, and MRV evidence needs.
# Estimate farm impact before you make claims.
The Kokonut Impact Calculator helps farm founders, DAO members, grant reviewers, contributors, and partners explore how a regenerative farm scenario may translate into SDG alignment, revenue potential, public goods allocation, and evidence requirements.
Use it as a **planning tool**, not as certified proof. The calculator helps you ask better questions; Kokonut's MRV workflow is what turns farm activity into verifiable evidence.
Built for scenario design, proposal drafting, farm planning, public goods reporting, and impact review.
Calculator outputs are indicative estimates. They are not financial advice, investment returns, certified carbon credits, audited SDG outcomes, or guaranteed farm results. Actual performance depends on land conditions, weather, execution, crop survival, market prices, governance, and data quality.
***
## What this calculator helps you do
| User | What you can use it for | Best next step |
| -------------------------- | ---------------------------------------------------------------------------- | --------------------------------------------------- |
| Farm founder | Estimate how land size, crops, labor, and practices affect the impact story. | Convert the scenario into a farm proposal |
| DAO member | Review whether a proposal's impact assumptions are directionally reasonable. | Compare scenario outputs with MRV evidence |
| Grant reviewer | Understand how a farm connects to SDGs and public goods | Inspect the Data Hub and reports |
| Impact contributor | Identify what data needs to be measured, reported, and verified | Help improve MRV workflows |
| Developer or agent builder | See which assumptions become useful inputs for scoring or simulation | Connect calculator logic to structured farm records |
The calculator is most useful when paired with the [Common Data Schema](/kokonut-framework/framework-components/common-data-schema), [MRV Methodology](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification), and a live farm reference such as [Adelphi](/ecosystem-wiki/kokonut-farms/adelphi/summary).
***
## How the calculator fits into Kokonut
```mermaid theme={null}
flowchart TD
A["Farm scenario"] --> B["Calculator inputs\nland · crops · labor · practices"]
B --> C["Indicative outputs\nSDG alignment · revenue potential · public goods allocation"]
C --> D["Proposal or planning document"]
D --> E["Farm activity"]
E --> F["MRV workflow"]
F --> G["Public evidence\nData Hub · EAS · reports"]
G --> H["DAO and partner decisions"]
H --> I["Updated assumptions"]
I --> B
```
The calculator sits **before** verification. It helps estimate what might happen if a farm follows certain assumptions. MRV then checks what actually happened.
***
## Calculator
Start by loading the Adelphi baseline if available, then adjust land size, crop mix, worker count, and regenerative practices to compare a new farm scenario against Kokonut's first live reference farm.
***
## What the calculator estimates
| Output | What it means | What verifies it later |
| ----------------------- | ------------------------------------------------------------------ | ----------------------------------------------------------------------------- |
| SDG alignment | A directional view of how the farm may contribute to selected SDGs | Field records, harvest data, employment records, training logs, SDG reporting |
| Revenue potential | Estimated production value based on crop and area assumptions | Actual harvest records, sales records, buyer agreements, Data Hub entries |
| Public goods allocation | Estimated portion of farm value that may support public goods | DAO proposal terms, treasury records, allocation reports |
| Job signal | Approximate employment or work-creation potential | Payroll records, role logs, contributor records, and local reporting |
| Climate co-benefit | A planning signal for soil, biomass, and carbon-related potential | Soil data, vegetation indices, biochar records, methodology-specific MRV |
| Verification needs | The evidence required before claims should be used publicly | MRV payloads, IPFS records, EAS attestations, annual reports |
***
## What the calculator does not prove
The calculator does **not** prove that a farm has already produced an impact.
It does not certify:
* carbon credits or carbon removals
* guaranteed crop yield
* guaranteed revenue
* investment returns
* Final SDG achievement
* legal compliance
* organic certification
* farm success
It creates a structured starting point for discussion, proposal review, and evidence planning.
***
## How assumptions should be handled
| Assumption type | Safe use | Risk if overstated |
| ------------------ | ------------------------------------------------------------------ | -------------------------------------------------------------- |
| Land size | Use for planning production capacity | Land may not all be usable or irrigated |
| Crop mix | Use to compare short, medium, and long-cycle revenue potential | Crop survival, disease, pests, and weather can change outcomes |
| Revenue rates | Use as scenario assumptions, preferably from Adelphi forecast data | Market prices and buyer access can change quickly |
| Public goods share | Use only if the farm proposal commits to it | Allocation is not real until governed and reported |
| Jobs | Use as a planning signal | Actual employment depends on budget, season, and operations |
| Carbon or climate | Treat it as a co-benefit until the methodology and MRV support it | Unsupported carbon claims can become greenwashing |
| SDG scores | Use to guide measurement priorities | SDG alignment is not the same as verified impact |
SDG 13 should be treated as a climate co-benefit unless a farm has a complete carbon methodology, baseline, monitoring plan, and verification workflow. Kokonut should avoid presenting carbon as a guaranteed result before evidence exists.
***
## How every number should become evidence
The calculator becomes useful when its assumptions are converted into measurable events.
| Calculator input or output | Evidence to collect | Where it belongs |
| -------------------------- | ------------------------------------------------------ | ---------------------------------- |
| Farm area | Polygon, GPS boundaries, land-use map | Common Data Schema and Data Hub |
| Crop mix | Planting records, crop cycle logs, density assumptions | Farm Registry and harvest forecast |
| Harvest estimates | Harvest logs, sales records, loss rates, and photos | Data Hub and annual reports |
| Labor or jobs | Role records, payroll notes, contributor logs | DAO reports and SDG reporting |
| Biochar or soil practices | Input logs, soil readings, and field observations | MRV payloads |
| Vegetation health | NDVI, NDRE, ReCI, MSAVI, drone imagery | MRV and Data Hub |
| Public goods allocation | Proposal terms, treasury transfers, and reporting | DAO governance and public reports |
This is the intended relationship:
```mermaid theme={null}
flowchart LR
A["Calculator estimate"] --> B["Farm plan"]
B --> C["Field activity"]
C --> D["MRV record"]
D --> E["Public evidence"]
E --> F["Updated calculator assumptions"]
```
***
## Recommended workflow
Create a rough scenario using land size, crop mix, workers, and regenerative practices.
Record which numbers are based on Adelphi, which are local estimates, and which still need validation.
Turn the scenario into a comparable farm record that includes location, land size, funding needs, crops, governance, public goods allocation, and market assumptions.
Decide which soil, satellite, harvest, field, and financial records will be needed before the farm can make public impact claims.
Once the farm is active, update projections using live Data Hub records, MRV events, and annual reports.
***
## How to read the result
| If the calculator shows... | Interpret it as... | Do next |
| ---------------------------- | ------------------------------------------ | --------------------------------------------------- |
| High SDG alignment | A strong planning hypothesis | Identify evidence needed for each SDG |
| High revenue potential | A promising economic scenario | Verify prices, buyers, crop cycles, and loss rates |
| High public goods allocation | A possible community benefit | Confirm it through DAO proposal terms |
| Strong climate co-benefit | A reason to collect better ecological data | Do not claim carbon impact until verified |
| Low score in one category | A design gap | Adjust crop mix, labor plan, training, or MRV scope |
***
## Related pages
The 13-field farm record makes calculator assumptions comparable across farms.
How estimates become public evidence through structured payloads, IPFS records, EAS attestations, and reports.
How Kokonut's first live farm maps farm activity to SDG evidence.
The crop and revenue assumptions behind Adelphi's forecast model.
Turn a calculator scenario into a DAO-readable funding, bounty, partnership, or framework proposal.
Help improve calculators, farm data models, MRV workflows, and impact reporting.
# Why Syntropic Farming
Source: https://kokonut.network/kokonut-framework/why-syntropic-farming
Why Kokonut uses syntropic farming as the agricultural foundation for regenerative farms, community ownership, biodiversity, and verifiable impact.
# Syntropic farming makes regeneration practical.
Kokonut Network uses syntropic farming because it turns a farm into a living system: crops, trees, soil, water, animals, biodiversity, labor, and community value reinforce each other over time.
Instead of treating land as something to extract from, syntropic farming designs farms to behave more like forests: diverse, layered, adaptive, and increasingly fertile as they mature.
Built for farm founders, DAO members, contributors, regenerative agriculture practitioners, impact reviewers, and anyone trying to understand why Kokonut farms are designed this way.
5
regeneration principles
2
Adelphi syntropic plots
Syntropic farming is the agricultural method within the [Kokonut Framework](/kokonut-framework/Introduction). The Framework turns that method into a repeatable system for onboarding farms, structuring operations, measuring impact, and helping DAO members compare real projects.
***
## How syntropic farming works
Syntropic farming is a regenerative agriculture method associated with Swiss-Brazilian farmer Ernst Götsch. The core idea is simple: productive farms can be designed to mimic the logic of forests.
A forest does not rely on a single species, a single harvest, or external chemical inputs to stay alive. It layers species vertically, cycles biomass, protects soil, captures water, creates habitat, and becomes more complex over time.
Syntropic farming applies that logic to food production.
| Stratum | Example species | Function |
| ------------- | -------------------------------------------- | ---------------------------------------------------- |
| High canopy | Coconut, timber trees, long-cycle species | Shade, biomass, roots, long-term value |
| Medium canopy | Passion fruit, banana, cacao, fruit trees | Fruit production, habitat, vertical diversity |
| Low canopy | Indian yams, shrubs, nitrogen-fixing species | Food, soil support, and biological interactions |
| Ground cover | Lettuce, tomatoes, legumes, and beard grass | Soil protection, moisture retention, erosion control |
The farm is designed as a succession system. Different species grow at different rates, occupy different layers, and support one another through shade, pruning, mulch, root activity, and nutrient cycling.
```mermaid theme={null}
flowchart TD
A["Diverse species are planted together"] --> B["Plants occupy different strata"]
B --> C["Pruning and biomass feed the soil"]
C --> D["Soil holds more water and nutrients"]
D --> E["Crops become more resilient"]
E --> F["Harvests, biodiversity, and farm evidence improve"]
F --> C
```
***
## What it replaces
Syntropic farming replaces the extraction logic of industrial monoculture.
| Industrial monoculture | Syntropic farming |
| ------------------------------------ | ---------------------------------------------------------------------------- |
| One dominant crop | Multiple crops and species in one system |
| Synthetic fertilizers and pesticides | Organic inputs, biomass cycling, compost, biochar, and biological processes |
| Bare soil between cycles | Continuous ground cover and living roots |
| Soil fertility declines over time | Soil fertility is designed to improve over time |
| Revenue depends on one crop cycle | Revenue can come from short, medium, long, and continuous production streams |
| Biodiversity is treated as a threat | Biodiversity is part of the productivity mechanism |
This matters because Kokonut is not only trying to fund farms. It is trying to fund farms that can become long-term community assets.
***
## Why Kokonut builds on syntropic farming
Short-cycle crops, medium-cycle fruits, long-cycle trees, and animal systems can all produce value on different timelines.
Biomass, compost, biochar, poultry manure, humic acids, and organic inputs reduce reliance on external synthetic inputs.
Ground cover, roots, mulch, and organic matter keep soil protected instead of exposed between harvests.
Healthier soils generally retain moisture better and help farms respond to both drought and heavy rainfall.
Biodiversity is not decorative. It supports pollination, habitat, fertility, pest balance, and long-term ecological resilience.
Vegetation health, soil observations, crop records, field activities, and impact metrics can flow into Kokonut's MRV workflow.
Syntropic farming improves the conditions for resilience and regeneration, but it does not remove agricultural risk. Weather, pests, labor, irrigation, execution, markets, and data quality still matter. Kokonut uses MRV to track outcomes rather than asking readers to blindly trust claims.
***
## In practice: Adelphi
Adelphi is Kokonut's first live syntropic farm in Monte Plata, Dominican Republic. It turns this methodology into a real operating system with crop beds, syntropic plots, a nursery, a biofactory, poultry, training space, biodiversity work, and public MRV.
| Syntropic principle | How Adelphi applies it |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| Multi-strata design | Short-cycle vegetables, medium-cycle fruits, long-cycle coconut, native species, and ground cover systems |
| Diversified revenue | Lettuce, passion fruit, coconut, eggs, and future market channels instead of a single-crop dependency |
| Closed-loop fertility | Bamboo biochar, poultry manure, humic acids, organic urea, forage, and crop residues |
| Biodiversity conservation | Nursery propagation and agroforestry species, including 12+ at-risk or native species |
| Animal integration | 110 free-range hens contribute eggs, manure, ground activity, and nutrient cycling |
| Education and replication | A training gazebo and farm layout support workshops, community learning, and future farm replication |
| MRV evidence | Farm data, harvest records, satellite indices, field logs, and impact metrics can be inspected through the Kokonut Hub |
[Explore Adelphi's farm system →](/ecosystem-wiki/kokonut-farms/adelphi/crops-biodiversity-and-infrastructure)
***
## How syntropic farming becomes a verifiable impact
Kokonut does not want regenerative agriculture to remain a beautiful story with no evidence. Syntropic farming becomes useful to DAO members, grant reviewers, researchers, builders, and communities when farm activity becomes inspectable data.
The MRV workflow turns farm activity into public evidence:
```text theme={null}
Farm activity → structured payload → IPFS record → Farm Registry event → EAS attestation → public Data Hub → annual impact report
```
| What happens on the farm | What can be measured or reported |
| -------------------------- | --------------------------------------------------------------------------------- |
| Crop planting and harvests | Crop type, volume, dates, yield, and revenue assumptions vs. actuals |
| Vegetation growth | Satellite indices such as NDVI, NDRE, and MSAVI |
| Soil and water practices | Moisture, soil observations, input use, cover crop activity, and field notes |
| Biodiversity work | Species planted, nursery propagation, per-plant records, and habitat improvements |
| Poultry integration | Egg production, manure use, forage, and nutrient cycling |
| Community education | Workshops, attendance, training activity, and local participation |
[Read the MRV methodology →](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification)
***
## Why this matters for the Kokonut Framework
The Kokonut Framework needs farms that are comparable, fundable, governable, and verifiable. Syntropic farming gives the Framework a regenerative operating method that can be adapted across different sites.
```mermaid theme={null}
flowchart TD
A["Syntropic farm design"] --> B["Framework standards"]
B --> C["Farm operations"]
C --> D["MRV records"]
D --> E["DAO and grant review"]
E --> F["Funding and contributor coordination"]
F --> G["More regenerative farms"]
G --> B
```
| Framework need | Why syntropic farming helps |
| -------------------- | --------------------------------------------------------------------------------------------- |
| Comparable farms | Similar principles can be applied across different lands, crops, and communities |
| Fundable proposals | Farm plans can explain production cycles, infrastructure needs, and measurable outputs |
| Governable decisions | DAO members can review farm operations against shared regenerative standards |
| Verifiable claims | Farm activity can be measured through MRV instead of being treated as self-reported marketing |
| Replication | Lessons from Adelphi can inform future farms without forcing every farm to be identical |
***
## What to read next
The operational principles derived from Kokonut's regenerative farming approach.
The live farm system where syntropic farming is being implemented and tracked.
How farm activity becomes public evidence for DAO members, researchers, and contributors.
How syntropic farming fits into the broader system for farm onboarding, governance, and replication.
# Kokonut Intelligence
Source: https://kokonut.network/kokonut-intelligence
The data, analytics, verification, and agent-access layer that turns farm activity into governed records, public dashboards, attestations, reports, and decision support.
# Kokonut Intelligence turns farm activity into decision-ready evidence.
Every harvest record, soil reading, satellite observation, expense entry, MRV event, EAS attestation, Data Hub metric, and AI-agent output needs a single trusted place to be structured, queryable, and reviewable.
**Kokonut Intelligence** is that layer. It sits between real-world farm activity and the systems that depend on it: farm operators, DAO reviewers, grant funders, impact analysts, public dashboards, AI agents, and future partner integrations.
Built for farm operators, DAO reviewers, data contributors, developers, MRV analysts, and agent builders.
Kokonut Intelligence is not a replacement for MRV methodology. MRV defines how farm activity becomes evidence. Kokonut Intelligence implements the data infrastructure that stores, validates, analyzes, attests to, and exposes evidence.
***
## Intelligence at a glance
| Question | Short answer |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| What is it? | The canonical data and analytics backbone for Kokonut farms. |
| What does it store? | Farm registry records, operations, harvests, expenses, sales, soil data, remote sensing, MRV events, attestations, partner data, and agent logs. |
| What does it power? | Data Hub dashboards, MRV workflows, EAS attestations, EBF reports, CRISP risk analysis, farm scoring, forecasts, and AI-agent workflows. |
| Who uses it? | Farm operators, DAO members, Guild contributors, grant reviewers, partners, developers, and agents. |
| What is live? | Repository architecture, local stack, canonical schemas, farm/MRV data model, Directus, ClickHouse, PostgreSQL, Metabase, Celo EAS integration, and developer quickstart. |
| What should be treated carefully? | Forecasts, scores, carbon or biodiversity-credit claims, institutional-readiness language, and partner-facing outputs until supported by verified records and external due diligence. |
***
## Why this layer exists
Regenerative farms generate many kinds of records. Without a governed intelligence layer, those records become fragmented across spreadsheets, screenshots, wallets, dashboards, reports, sensors, notebooks, and chat messages.
Kokonut Intelligence gives the network a shared source of truth.
| Without Kokonut Intelligence | With Kokonut Intelligence |
| -------------------------------------------- | ------------------------------------------------------------------------- |
| Farm data is scattered across tools | Farm data is structured into canonical records |
| Impact claims depend on narrative | Claims can reference MRV events, evidence CIDs, and attestations |
| DAO reviewers inspect one-off documents | Reviewers query consistent data across farms |
| Agents need direct database or manual access | Agents use scoped access, manifests, and audit logs |
| Forecasts are hard to compare with actuals | Forecasts can be checked against harvests, losses, sales, and MRV records |
| Annual reports are manually assembled | Reports can be generated from governed snapshots |
***
## How it works
```mermaid theme={null}
flowchart TD
A["Farm activity\nharvest · expense · soil · weather · field log"] --> B["Structured record\nCommon Data Schema + MRV payloads"]
B --> C["Kokonut Intelligence\nPostgreSQL · Directus · ClickHouse"]
C --> D["Review lifecycle\ndraft → submitted → verified → published"]
D --> E["Data Hub + APIs\nqueryable public and partner views"]
D --> F["Evidence layer\nIPFS/Filecoin + EAS attestations"]
D --> G["Analytics\nforecasts · scores · reports · alerts"]
E --> H["DAO and partner decisions"]
F --> H
G --> H
C --> I["AI agents\nscoped access + audit logs"]
I --> B
```
The core idea is simple: **farm events should become structured records before they become public claims.**
That means every important claim should be traceable back to:
* a farm ID
* a timestamp
* a source or operator
* a record type
* a review status
* a payload or evidence file
* An attestation or report reference when applicable
***
## Architecture
Kokonut Intelligence is a six-layer stack. Each layer has a specific job.
| Layer | Technology | Role |
| --------------------- | ------------------------------------ | ------------------------------------------------------------------------------- |
| Canonical core | PostgreSQL, PostGIS, Directus | Source-of-truth records, APIs, role permissions, admin UI, workflows |
| Analytics | ClickHouse | Time-series analysis, sensor aggregation, event queries, performance reporting |
| BI | Metabase | Internal dashboards, operational summaries, and ad-hoc analysis |
| Intelligence services | Python | Forecasting, scoring, ecological analytics, opportunity maps, report generation |
| Verification | EAS on Celo, off-chain signed claims | Attestations for MRV, impact, harvest, financial, and compliance records |
| Blockchain ingestion | RPC, subgraphs, Foundry | Wallet activity, attestations, treasury events, DAO data, resolver contracts |
**Chain clarification:** Gnosis Chain hosts Kokonut DAO governance contracts and treasury execution. Celo hosts farm-data attestations through EAS. Governance capital and farm evidence are connected, but they are not on the same layer.
***
## What it implements from the Knowledge Base
| Knowledge Base concept | Intelligence implementation |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Common Data Schema | `farm_registry_record` and validation services for the 13-field farm record |
| MRV workflow | Remote sensing, sensor readings, field observations, MRV events, evidence payloads, and attestation requests |
| Data Hub | Directus and ClickHouse-backed APIs that expose farm data and metrics |
| EAS attestations | Celo schemas, attestation records, resolver-gated publishing, onchain/offchain modes |
| EBF reports | Generated snapshots based on verified ecological and operational records |
| CRISP review | Risk factors derived from ecological, governance, and evidence-quality data |
| 8 Forms of Capital | Metrics that classify farm value across natural, financial, social, human, material, intellectual, cultural, and health capital |
| AI agents | Agent identity, capability manifests, scoped tokens, agent tasks, and action logs |
***
## Core capabilities
Pull farm records from field logs, Directus entries, sensors, weather APIs, satellite imagery, blockchain data, and attestation indexes.
Store farm registry entries, crop cycles, harvests, expenses, sales, losses, MRV events, soil readings, and partner data with clear lifecycle states.
Convert eligible records into evidence payloads, IPFS/Filecoin references, Celo EAS attestations, public dashboards, and annual reports.
Generate farm scores, revenue forecasts, loss-rate analysis, ecological trends, opportunity maps, and metric snapshots.
Expose buyer, funder, vendor, operator, and internal dashboards with role-based and row-level data controls.
Let AI agents read canonical data and write verified outputs through scoped access, MCP integration, and full audit logging.
***
## Record lifecycle
Every operational record should pass through a review flow before it becomes trusted enough for dashboards, reports, or attestations.
```mermaid theme={null}
flowchart LR
A["Field worker or integration\ncreates record"] --> B["draft"]
B --> C["submitted"]
C --> D["verified"]
C --> E["rejected"]
E -->|rework| B
D --> F["published"]
F --> G["dashboards + APIs"]
F --> H["attestation pipeline"]
F --> I["reports + analytics"]
```
| Status | Meaning |
| --------- | ------------------------------------------------------------------------------ |
| Draft | A record exists but is not ready for review. |
| Submitted | A field worker, integration, or supervisor has submitted it for review. |
| Verified | A manager, finance reviewer, analyst, or authorized process has approved it. |
| Published | The record can be used in dashboards, reports, API responses, or attestations. |
| Rejected | The record needs correction before it can become evidence. |
***
## Farm scoring and opportunity mapping
Kokonut Intelligence can help rank and compare farms, but scores should be treated as **decision support**, not automatic certification.
| Tool | What it helps with | Trust requirement |
| ----------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| Farm score | Compare financial, ecological, governance, and growth performance | Requires clean records, transparent weights, and reviewable metric definitions |
| Revenue multiplier map | Identify possible revenue-uplift opportunities | Requires market assumptions, operator review, and actuals tracking |
| Revenue forecast | Model scenarios across revenue, NOI, yield, and cash flow | Requires forecast-vs-actual comparison and sensitivity analysis |
| Ecological analytics | Track soil, vegetation, biodiversity, and water indicators | Requires baselines, consistent measurement periods, and MRV methodology |
| Governed metrics engine | Version and compute metrics across farms | Requires source lineage and change governance |
Scores, forecasts, carbon estimates, biodiversity-credit assumptions, and institutional-readiness labels are not guarantees. They are planning and reviewing tools until supported by verified records, external standards, partner due diligence, and any required third-party validation.
***
## EAS attestation layer on Celo
Kokonut Intelligence uses EAS on Celo for farm-data attestations. This separates **governance execution** from **farm evidence**:
| Chain | Kokonut role |
| ------------ | ----------------------------------------------------------------------------------- |
| Gnosis Chain | DAO governance, treasury, membership, proposal execution |
| Celo | Farm evidence, MRV attestations, impact records, harvest proofs, compliance records |
### Celo contracts
| Contract | Address |
| ---------------- | -------------------------------------------- |
| EAS v1.3.0 | `0x72E1d8ccf5299fb36fEfD8CC4394B8ef7e98Af92` |
| SchemaRegistry | `0x5ece93bE4BDCF293Ed61FA78698B594F2135AF34` |
| KokonutResolver | `0x6E1502c7a14b45aba5FC420dC92C1E3b38BD79Ad` |
| Kokonut multisig | `0x03779B674CbCBfc0B801c4cAc9DFaC8aACbbD5c5` |
### Registered schemas
| Schema | Use case |
| -------------------- | ---------------------------------------------------------------------------- |
| `kokonut-mrv` | MRV claims: location, crop, quantity, evidence CID |
| `kokonut-impact` | Environmental impact: soil carbon, biodiversity index, vegetation indicators |
| `kokonut-financial` | Financial summaries: NOI, revenue, costs, farm score snapshots |
| `kokonut-harvest` | Harvest verification: quantity, quality grade, date, operator |
| `kokonut-compliance` | Partner compliance: audit trails and contractual adherence |
Sensitive data should not be pushed publicly by default. Kokonut Intelligence supports off-chain records, onchain hashes, selective disclosure, and future privacy-preserving proof layers for records that should not be fully public.
***
## Roles and access
The Intelligence Layer should make data useful without making every user an administrator.
| Role | Access level | Main responsibility |
| ------------- | ----------------------------------------- | -------------------------------------------------------------------------- |
| Administrator | Full access | Platform configuration, schemas, permissions, infrastructure operations |
| Field Worker | Create and read your own location records | Activities, harvests, expenses, sales, losses, field notes |
| Supervisor | Read and submit | Review drafts and submit records for verification |
| Manager | Approve operational records | Verify operations, field data, crop records, and milestones |
| Finance | Approve financial records | Verify expenses, sales, payments, and revenue events |
| Analyst | Read verified and published data | Dashboards, metrics, forecasts, reports, and DAO review support |
| Agent | Scoped access only | Read or write specific records through capability manifests and audit logs |
***
## Builder quickstart
```bash theme={null}
git clone https://github.com/wasalo/Kokonut-Intelligence.git
cd Kokonut-Intelligence
```
```bash theme={null}
cp .env.example .env
# Edit .env with database passwords and API keys
```
```bash theme={null}
docker compose up -d
docker compose ps
```
```bash theme={null}
./scripts/seed.sh
./scripts/seed-pilot.sh
```
```bash theme={null}
open http://localhost:8055 # Directus
open http://localhost:3001 # Metabase
```
### Local service endpoints
| Service | URL | Purpose |
| --------------- | ----------------------- | ---------------------------------------------------- |
| Directus | `http://localhost:8055` | Schema management, admin UI, API, primary data entry |
| Metabase | `http://localhost:3001` | Internal dashboards and BI |
| ClickHouse HTTP | `http://localhost:8123` | Analytical queries |
| PostgreSQL | `localhost:5432` | Canonical data store |
***
## What to build first
Add validation rules, import tools, field-worker UX improvements, or better error messages for farm records.
Create ingestion, QA, visualization, or attestation workflows for satellite, sensor, drone, or field-observation data.
Improve loss-rate analysis, farm scoring, ecological trends, forecast-vs-actual tracking, or revenue opportunity maps.
Build agents that read canonical data, produce bounded outputs, submit MRV events, and leave full action logs.
Build clearer dashboards for operators, DAO reviewers, buyers, funders, vendors, or public visitors.
Improve scoped permissions, selective disclosure, partner dashboards, private data handling, and audit trails.
***
## Claim safety rules
Use Kokonut Intelligence outputs carefully.
| Claim type | Safe framing |
| ----------------------- | -------------------------------------------------------------------------------------------- |
| Forecasts | Scenario estimates that should be compared against actuals. |
| Farm scores | Decision-support signals based on metric weights and available data. |
| Carbon outcomes | Climate co-benefits are not verified through approved methodology and third-party standards. |
| Biodiversity claims | Evidence-backed observations, species records, and trends, not automatic credits. |
| Financial performance | Records and projections, not guaranteed returns. |
| Institutional readiness | A review pathway that requires due diligence, not a status the system grants by itself. |
***
## Internal documentation map
The repository includes deeper documentation for each subsystem.
| Document | What it covers |
| --------------------------- | ---------------------------------------------------------- |
| `docs/architecture.md` | System overview, data flows, security model |
| `docs/data-dictionary.md` | Tables, fields, metrics, and relationships |
| `docs/api-reference.md` | REST, GraphQL, and ClickHouse API reference |
| `docs/openapi.yaml` | OpenAPI 3.0 specification |
| `docs/attestation-guide.md` | EAS on Celo, schemas, attestation modes, private data, CLI |
| `docs/agent-access.md` | MCP integration, scoped tokens, and audit logging |
| `docs/deployment.md` | Docker setup, environment variables, and backup procedures |
| `docs/sandbox.md` | Developer quickstart and hello-world tutorial |
***
## Next steps
Repositories, contracts, schemas, MRV primitives, contribution rules, and builder paths.
How farm activity becomes structured evidence, public records, attestations, dashboards, and annual reports.
The 13-field farm record that makes farms comparable, fundable, governable, and verifiable.
Agent identity, scoped access, MCP integration, x402 payments, and verifiable agent outputs.
How EBF and CRISP interpret verified farm data for reporting and risk review.
Explore live farm data, MRV events, harvest records, and impact metrics for Kokonut's reference farm.
# Kokonut × AI Agents
Source: https://kokonut.network/kokonut-x-ai-agents
How agent builders can automate MRV, harvest forecasting, impact scoring, grant drafting, and farm operations with Kokonut's data, payments, identity, and verification stack.
# AI agents turn Kokonut farm data into faster coordination.
Farms produce information constantly: satellite images, field logs, soil readings, drone surveys, crop cycles, harvest records, MRV payloads, and DAO reporting requirements.
Today, much of that work still depends on manual handoffs. An operator collects data, someone processes it, someone else reviews it, another person formats it for a report, and the result may only become useful after long delays.
Kokonut's agent layer is designed to reduce those handoffs. Agents can ingest farm data, calculate metrics, prepare structured records, route outputs for review, trigger payments, and help convert farm activity into evidence that DAO members, Guilds, farm operators, and public goods funders can actually use.
Explore MRV automation, harvest forecasting, impact scoring, grant drafting, proposal drafting, and farm monitoring.
Follow the safe builder path: choose a task, define inputs and outputs, connect to Kokonut data, test, and request review.
The Agentic Marketplace is still in development. Treat contract addresses, service registry flows, marketplace listings, escrow flows, and autonomous payments as developing infrastructure until testnet or mainnet deployments are published. Do not describe planned agent capabilities as live farm guarantees.
***
## What this page is for
| Reader | What you should get from this page | Best next step |
| --------------------- | --------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| Agent builder | Understand safe first agent opportunities and integration requirements | Start with the MRV Reporter or Harvest Forecaster path |
| Data / MRV engineer | Understand how agents interact with Farm Registry records, IPFS payloads, EAS attestations, and the Kokonut Hub | Review the MRV workflow |
| Farm operator | Understand which farm tasks agents can help automate | Identify repeatable tasks worth automating |
| DAO or Guild reviewer | Understand what needs human review before agent outputs become trusted | Use the review checklist |
| Partner or funder | Understand how automation supports evidence, not hype | Compare estimates, measurements, attestations, and reports |
Agents are not a replacement for agronomists, farm operators, DAO governance, or human review. They are coordination tools that help standardize repeatable work and move evidence through the Kokonut system faster.
***
## AI agents at a glance
| Layer | What it does | Status |
| ------------------ | -------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
| Farm data | Reads farm records, crop cycles, harvest events, MRV payloads, and public Data Hub entries | Live data exists for Adelphi; integrations expanding |
| Intelligence layer | Structures, operational, environmental, financial, governance, and Web3 records for analysis | Active infrastructure |
| Agent runtime | Runs task-specific services such as MRV reporters, harvest forecasters, and impact scorers | Developing |
| Identity | Registers agents with names, operators, capabilities, and service metadata | Developing |
| Payments | Uses USDC and x402-style flows for paid service calls | Developing |
| Verification | Connects outputs to IPFS/Filecoin records, Farm Registry events, EAS attestations, and reviewer approval | MRV pipeline active; agent automation developing |
| Reputation | Tracks completed work, quality, disputes, and longer-term contribution history | Developing |
***
## The core idea
```mermaid theme={null}
flowchart TD
A["Farm activity\nsoil · satellite · drone · harvest · field log"] --> B["Structured Kokonut data\nCommon Data Schema + MRV payloads"]
B --> C["AI agent task\ncalculate · format · validate · draft · alert"]
C --> D["Human / Guild review\nquality control + context"]
D --> E["Farm Registry record\nqueryable structured event"]
E --> F["IPFS / Filecoin artifact\ncontent-addressed evidence"]
F --> G["EAS attestation\ntamper-resistant public anchor"]
G --> H["Kokonut Hub + reports\nDAO, grants, operators, funders"]
H --> I["Better decisions\nfunding · operations · replication"]
```
The goal is not to let agents invent impact claims. The goal is to help agents move real farm events through a structured evidence pathway.
***
## What agents should automate first?
Agents should begin with repeatable, bounded tasks where the input, output, review rule, and evidence requirement are clear.
Ingests satellite, drone, soil, or field observations and prepares structured MRV payloads for review and attestation.
Applies registered crop assumptions to estimate expected harvests, loss rates, revenue scenarios, and actual-vs-forecast differences.
Aggregates verified farm records across a reporting period and prepares draft EBF, SDG, or public-goods reporting summaries.
Pulls structured farm data, MRV records, SDG alignment, and proof points into draft grant applications for human editing.
Converts farm records, budgets, milestones, and evidence into DAO proposal drafts for sponsor review.
Compares vegetation, harvest, soil, and operations data across farms to flag anomalies, missing records, or possible intervention needs.
***
## Live vs. developing
| Area | How to describe it |
| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| Adelphi farm data | Live reference project with public records and MRV workflows |
| MRV methodology | Active trust pipeline for turning farm activity into structured evidence |
| Common Data Schema | Live Framework primitive for standard farm records |
| Kokonut Intelligence | Active data backbone for farm, governance, environmental, financial, and Web3 activity |
| Agentic Marketplace | In development, use the development branch and avoid claiming deployed marketplace behavior until addresses are published |
| x402 payments | Design direction for autonomous service payment; implementation should be tested before production claims |
| Agent reputation | Developing should distinguish task history, review outcomes, Guild recognition, and DAO-approved rewards |
| Carbon or credit-related automation | Research / methodology-dependent; agents can support evidence collection, but cannot create certified climate claims by themselves |
A useful agent can produce a draft, a calculation, an alert, or a structured payload. A trustworthy Kokonut claim still needs source data, review, evidence storage, attestation, and public reporting.
***
## Agent system architecture
```mermaid theme={null}
flowchart LR
subgraph Farm["Farm evidence"]
A["Field logs"]
B["Soil sensors"]
C["Satellite / drone imagery"]
D["Harvest records"]
end
subgraph Data["Kokonut data layer"]
E["Common Data Schema"]
F["Farm Registry API"]
G["Kokonut Intelligence"]
H["Kokonut Hub"]
end
subgraph Agents["Agent layer"]
I["MRV Agent"]
J["Harvest Agent"]
K["Impact Agent"]
L["Grant / proposal Agent"]
end
subgraph Trust["Trust layer"]
M["IPFS / Filecoin CID"]
N["EAS attestation"]
O["Guild / human review"]
P["DAO decision"]
end
A --> F
B --> F
C --> I
D --> J
E --> F
F --> G
G --> H
F --> I
F --> J
F --> K
G --> L
I --> O
J --> O
K --> O
L --> O
O --> M
M --> N
N --> H
H --> P
```
***
## The four builder primitives
| Primitive | Plain English | In Kokonut |
| ---------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Identity | Who is the agent and who operates it? | Agent name, operator wallet, capability manifest, status, and service metadata |
| Capability | What can the agent do? | Inputs, outputs, pricing, SLA, review rules, and artifact format |
| Payment | How does the agent get paid? | USDC / x402-style calls, escrow for longer tasks, and completion proof requirements |
| Evidence | Why should anyone trust the output? | Source data, IPFS/Filecoin CID, Farm Registry event, EAS attestation, reviewer approval, and public Data Hub record |
***
## Capability manifest
Every agent should declare what it accepts, what it returns, and what review evidence is required.
```json theme={null}
{
"agent_name": "kokonut-mrv-reporter",
"version": "0.1.0",
"status": "development",
"description": "Prepares structured MRV payloads from remote sensing or field data for review and attestation.",
"inputs": {
"farm_id": {
"type": "string",
"required": true,
"description": "Farm Registry identifier, such as adelphi"
},
"period_start": {
"type": "string",
"format": "ISO8601",
"required": true
},
"period_end": {
"type": "string",
"format": "ISO8601",
"required": true
},
"imagery_source": {
"type": "string",
"enum": ["sentinel", "landsat_8", "drone", "field_upload"],
"required": true
}
},
"outputs": {
"mrv_event_draft_id": {
"type": "string",
"description": "Draft event created before final review"
},
"vegetation_indices": {
"type": "object",
"properties": {
"ndvi": { "type": "number" },
"ndre": { "type": "number" },
"reci": { "type": "number" },
"msavi": { "type": "number" }
}
},
"artifact_cid": {
"type": "string",
"description": "IPFS/Filecoin CID for the source artifact or generated report"
},
"review_status": {
"type": "string",
"enum": ["draft", "needs_review", "approved", "rejected"]
}
},
"review_required": true,
"reviewer_role": "Impact Guild or authorized MRV reviewer"
}
```
Keep manifests versioned. If an agent changes input fields, output fields, pricing, or review rules, publish a new version and document the migration impact.
***
## MRV automation workflow
Agents should compress manual work without bypassing verification.
Pull satellite imagery, drone uploads, soil readings, harvest logs, or field observations. Record the source, timestamp, farm identifier, and collection method.
Calculate vegetation indices, crop estimates, loss-rate scenarios, soil trends, or reporting summaries using documented formulas and farm boundaries.
Format results into a Farm Registry-compatible draft. Mark it as a draft until a reviewer approves it.
Store source files or generated reports with IPFS/Filecoin CIDs so reviewers can inspect the evidence behind the output.
Route the draft to the relevant Guild, farm operator, or authorized reviewer. Agents should not self-certify high-impact claims.
After approval, submit the final event to the Farm Registry and create the EAS attestation that links the public claim to its evidence.
***
## Vegetation indices agents may compute
| Index | Use case | Review note |
| ----- | ------------------------------------------------------------- | ------------------------------------------------------------------------- |
| NDVI | General vegetation health across a farm period | Useful, but should be interpreted alongside crop stage and ground context |
| NDRE | Canopy maturity and chlorophyll stress in later growth stages | Works best when crop canopy is developed |
| ReCI | Chlorophyll and nitrogen-related stress signal | Requires agronomic context before recommendations |
| MSAVI | Early growth, sparse canopy, and exposed soil conditions | Better for early-stage plots than NDVI alone |
Vegetation indices are signals, not final conclusions. Agents should flag potential conditions and route them for review by a farm operator or agronomist before making operational recommendations.
***
## Payments and escrow
Payment automation should match task complexity.
| Task type | Suggested payment pattern | Why |
| --------------------- | -------------------------------------- | ---------------------------------------------------------------------- |
| Fast API call | x402-style pay-per-request | Good for small forecasts, metadata lookups, or simple calculations |
| Long-running analysis | Escrow with completion proof | Better for drone processing, multi-farm reports, or large grant drafts |
| Recurring monitoring | Milestone or subscription-style budget | Useful for weekly or monthly farm monitoring tasks |
| High-risk claims | Payment after review | Avoids rewarding outputs that fail evidence or quality checks |
Keep payment flows separate from evidence quality. A paid output is not automatically a verified output.
***
## Reputation and quality control
Agent reputation should be based on useful work, not just task volume.
| Signal | What it means | Who uses it |
| ---------------------- | ------------------------------------------------------------------------------ | ------------------------------------------- |
| Task completion | The agent returned an output before the deadline | Builders, marketplaces, reviewers |
| Review outcome | A human or Guild reviewer accepted, requested changes, or rejected the output | Guilds, DAO members, operators |
| Evidence quality | Source data, formulas, CIDs, and assumptions were inspectable | MRV reviewers, grant reviewers, researchers |
| Dispute history | Outputs were challenged or escalated | Marketplace users and DAO reviewers |
| Long-term contribution | The agent's work consistently supported farm reporting or operations over time | Guilds and DAO proposal reviewers |
Agents that consistently produce useful, reviewable, and evidence-backed outputs can support Guild contribution records. Larger recognition or rewards should still follow the relevant Guild or DAO proposal process.
***
## Builder starts path
Start with one repeatable job, such as preparing an MRV draft, calculating a harvest forecast, or formatting a proposal draft.
Write the capability manifest before writing complex code. Reviewers should know exactly what the agent accepts and returns.
Use the Common Data Schema, Farm Registry API, Kokonut Hub, or Kokonut Intelligence as the source of truth. Do not scrape or reinterpret records without documenting the source.
Agent outputs should be treated as drafts until a reviewer approves them, especially for MRV, impact, finance, carbon, governance, or grant claims.
Store source files, generated reports, formulas, and assumptions with CIDs or stable references so outputs are reviewable.
For non-trivial integrations, open an issue before a pull request. Schema, MRV, attestation, and payment changes need compatibility review.
***
## Safe first agent ideas
| Agent | Input | Output | Reviewer |
| ----------------------- | -------------------------------------------------------- | --------------------------------------------------- | ----------------------------- |
| MRV Draft Reporter | Farm ID, period, imagery, or field record | Draft MRV payload and evidence CID | Impact Guild / MRV reviewer |
| Harvest Actuals Checker | Crop cycle, planted area, harvest log | Actual-vs-forecast report | Farm operator / Finance Guild |
| Proposal Formatter | Farm record, budget, milestones, evidence | Draft proposal in Kokonut template format | Governance Guild |
| Data Quality Monitor | Farm Registry records and Data Hub entries | Missing fields, stale data, or inconsistency alerts | Technology Guild |
| SDG Evidence Assistant | MRV records, harvests, jobs, and public goods allocation | Draft SDG evidence map | Impact Guild |
| Grant Proof Assistant | Farm summary, MRV records, SDG map, photos | Draft proof package for grant submission | Communications Guild |
***
## What agents should not do
| Do not let agents... | Safer alternative |
| -------------------------------------- | ---------------------------------------------------------------- |
| Certify carbon credits | Collect evidence that could support future methodology review |
| Claim guaranteed yields or revenue | Compare forecasts against actual records and show assumptions |
| Publish impact claims without evidence | Route drafts through MRV, reviewer approval, and EAS attestation |
| Move DAO funds autonomously | Draft proposals for human sponsorship and DAO vote |
| Change the Common Data Schema silently | Open a Framework Upgrade Proposal with a migration plan |
| Treat planned contracts as deployed | Label infrastructure as live, developing, planned, or deprecated |
| Replace farm operators | Assist operators with alerts, summaries, and structured reports |
***
## How this connects to Kokonut Intelligence
Kokonut Intelligence is the data backbone that can make agents useful. It gives agents access to structured context instead of forcing them to infer from scattered documents.
| Intelligence function | Agent benefit |
| ----------------------------- | ----------------------------------------------------------------------------- |
| Farm operations records | Agents can reference actual activity instead of inventing assumptions |
| Environmental measurements | Agents can calculate trends and flag anomalies |
| Financial and harvest records | Agents can compare forecasts against actuals |
| Web3 and DAO records | Agents can draft proposals and reporting summaries with governance context |
| Queryable analytics layer | Agents can answer structured questions for builders, reviewers, and operators |
[Read Kokonut Intelligence →](/kokonut-intelligence)
***
## Review the checklist before using an agent output
* Does the output cite or reference the source farm record?
* Does it distinguish between forecast, estimate, measurement, attestation, and verified report?
* Does it include timestamps, farm ID, source type, and reviewer status?
* Is the formula or model documented?
* Are source artifacts linked through stable storage or CIDs?
* Has a human or Guild reviewer approved high-impact claims?
* Does the output avoid unsupported financial, carbon, health, or climate claims?
* Does it avoid describing development infrastructure as live?
***
## Developer resources
| Resource | Purpose |
| --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| [Build with Kokonut](/build-with-kokonut) | Repositories, deployed contracts, data primitives, and contribution workflow |
| [Farm Registry API](/api-reference/openapi) | API reference for farm records, MRV events, harvests, attestations, and impact endpoints |
| [MRV methodology](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification) | Evidence pipeline for farm activity, payloads, IPFS records, EAS attestations, and reports |
| [Common Data Schema](/kokonut-framework/framework-components/common-data-schema) | Baseline farm record consumed by DAO members, developers, agents, and dashboards |
| [Kokonut Intelligence](/kokonut-intelligence) | Canonical data backbone for farm, environmental, financial, governance, and Web3 activity |
| [Kokonut Guilds DAO](/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao) | Contribution path for builders who want Guild recognition and possible DAO rewards |
| [Glossary](/ecosystem-wiki/glossary) | Definitions for MRV, EAS, x402, ERC-8004, Guilds, and related terms |
***
Start with repos, contribution workflow, data primitives, and live vs. developing infrastructure.
Understand how agent outputs should become structured evidence instead of unsupported claims.
Review the marketplace codebase, contracts, frontend, and OpenServ integration work.
Contribute useful agent tooling, earn standing through work, and route larger contributions through DAO governance.
# Business Model & Legal
Source: https://kokonut.network/playbooks/regenerative-finance/business-model-and-legal
### Financial Model
**Revenue streams (Adelphi, forecast):**
```mermaid theme={null}
flowchart LR
A["🥬 Lettuce
$133,237.50/yr"] --> E["Total Farm Revenue
$149,110/yr"]
B["🍈 Passion Fruit
$11,019.61/yr"] --> E
C["🥥 Coconut
$4,853.76/yr"] --> E
D["🥚 Eggs
36,500/yr from 110 hens"] --> E
E -->|40%| F["Hernández Family
farm operators"]
E -->|40%| G["Public Goods Fund"]
E -->|20%| H["Kokonut Network"]
```
| Crop / Stream | Forecast annual revenue | Notes |
| ------------------ | ---------------------------- | -------------------------------------------------------------------------------------------------------------- |
| Lettuce | \$133,237.50 | Largest single revenue line; short-cycle, provides near-term cash flow |
| Passion fruit | \$11,019.61 | Mid-cycle vine crop |
| Coconut | \$4,853.76 | Long-cycle (multi-year maturation); 96 trees across 8 plots |
| Eggs | 36,500 eggs/yr from 110 hens | Additional protein/revenue stream layered onto the same land |
| **Total forecast** | **\$149,110/year** | (source: [Adelphi Crops & Harvest Forecast](/ecosystem-wiki/kokonut-farms/adelphi/crops-and-harvest-forecast)) |
The short-cycle lettuce revenue is explicitly what bridges the farm financially while the long-cycle coconut trees mature — a "bridge crop" pattern worth calling out for anyone replicating this with tree crops.
**Cost structure:** Adelphi's infrastructure build-out carries a forecasted budget of \$45,000 USD in total. Against that, two grants have been confirmed to date: an \$11,000 grant from Public Nouns (Proposal #69) and a \$3,150 grant from the Kokonut DAO treasury, both earmarked for critical infrastructure.
Ongoing operating costs are reduced by design through closed-loop inputs — on-site organic matter and poultry byproducts feeding back into soil fertility rather than purchased synthetic inputs — with labor (the 7 jobs created) as the primary recurring operating cost.
**Funding sources & revenue split:**
```mermaid theme={null}
flowchart TD
A["External Grants
Public Nouns #69 ($11,000) · Kokonut DAO ($3,150)"] --> B["Farm Infrastructure Build-out
$45,000 forecasted budget"]
C["DAO Treasury
stablecoin tribute via Gnosis Safe"] --> B
B --> D["Farm Production
Adelphi crops & eggs"]
D --> E["Farm Revenue
~$149,110/yr forecast"]
E -->|40%| F["Hernández Family"]
E -->|40%| G["Public Goods Fund"]
E -->|20%| H["Kokonut Network"]
H --> I["Kokonut Seeds
revenue-funded flywheel"]
I --> J["Guild Budgets"]
J --> K["Contributor Work
next proposal, next farm"]
K -.funds.-> A
```
* **DAO treasury:** stablecoin "tribute" contributions from members flow into a Gnosis Safe–controlled multisig treasury.
* **Grants:** Adelphi's initial buildout was funded via **Public Nouns Proposal #69**, a public-goods-oriented Nouns-ecosystem grant (source: Adelphi Executive Summary; Common Data Schema). Beyond the \$45,000 infrastructure budget tied to Public Nouns Proposal #69, Adelphi has also received a 3,150 grant directly from the Kokonut DAO treasury for infrastructure development — a smaller, DAO-native funding round layered on top of the original external grant, and an early example of the DAO reinvesting its own treasury into the flagship farm rather than relying solely on outside capital.
* **Kokonut Seeds:** a revenue-funded flywheel mechanism that recycles a portion of farm revenue back into Guild budgets, so ongoing contributor funding isn't solely dependent on new capital raises.
* **Revenue split (Adelphi specifically):** 40% to the Hernández family as farm operators, 40% to the public-goods fund, 20% to Kokonut Network.
### Regulatory Compliance
The public documentation is explicit that none of it constitutes legal, tax, or financial advice (source: [Kokonut Moloch DAO](/ecosystem-wiki/the-kokonut-dao/kokonut-moloch-dao)).
What is documented:
* **Organic certification** for Adelphi's produce is pursued through the Dominican Republic's Ministry of Agriculture pathway.
* **Treasury design** deliberately uses stablecoins for tribute and treasury holdings, which reduces (though doesn't eliminate) the DAO's exposure to crypto-asset price volatility relative to holding a volatile governance or utility token as the treasury's primary asset.
* **Risk disclosures** on smart-contract risk, key management, and the experimental nature of DAO tooling are surfaced directly in the FAQ rather than buried.
On the ground, land access runs through a general partnership agreement between Kokonut and the landowner or land steward: the landowner contributes the land itself, and the contract assigns each stakeholder a defined percentage across the full range of capital contributed — not cash alone.
On Kokonut's side, that agreement is signed by a Dominican SRL (Sociedad de Responsabilidad Limitada), which gives the arrangement a recognized legal counterparty under Dominican law. Kokonut DAO itself does not yet have its own legal wrapper — it currently operates through the SRL rather than contracting directly — but Kokonut is evaluating wrapping the DAO through Otoco.io, a Web3 legal-entity platform, so the DAO can hold enforceable rights in real-world contracts on its own rather than exclusively through an intermediary entity.
# Case Studies
Source: https://kokonut.network/playbooks/regenerative-finance/case-studies
### Kokonut Adelphi (Sabana Grande de Boyá) — the flagship live farm proof
Adelphi is the Kokonut Framework's first live implementation: a 15,725 m² site in Gonzalo, Sabana Grande de Boyá, Monte Plata, converted from underused family land into an active syntropic farm by Yanny and Neury Hernández, funded through Public Nouns Proposal #69.
#### **Success Stories:**
* 96 coconut trees, 560 passion fruit vines, and large-scale lettuce production are active across 13,838 m² of agricultural land.
* 110 free-range hens producing roughly 100 eggs/day, adding a protein/revenue stream beyond the original crop plan.
* 7 direct jobs created in a rural area facing the youth-outmigration pressure, the Problem & Solution page names directly.
* 12+ native and at-risk species reintroduced through the farm's nursery program, layered into the syntropic design rather than planted as an offset afterthought.
* Primary alignment with 5 SDGs (1, 2, 5, 8, 15), with the farm's own SDG page walking through specific evidence for each rather than a generic checklist (source: [Adelphi SDGs](/ecosystem-wiki/kokonut-farms/adelphi/sustainable-development-goals)).
#### **Lessons Learned:**
* **The capital-to-harvest gap is real and needs a bridge.** The \$45,000 infrastructure budget arrived before any crop revenue existed; the lettuce-as-bridge-crop decision was a direct response to that gap.
* **Organic certification is a process, not a switch.** It's explicitly framed as in progress via the DR Ministry of Agriculture pathway rather than already achieved.
* **Local land-use, water, and market-access pressures shape the design more than the DAO tooling does.** The seven challenges named on the [Adelphi Problem & Solution](/ecosystem-wiki/kokonut-farms/adelphi/problem-and-solution) page are agronomic and socioeconomic, not blockchain problems — a useful reminder that the Web3 layer supports the farm; it doesn't replace good farming.
### Key Takeaways
* Build governance before scaling.
* Standardize data from day one.
* Bridge long-cycle crops with short-cycle revenue.
* Separate governance from impact verification.
* Make proof continuous rather than annual.
### Replication Checklist
To launch a Kokonut-style farm, you'll need:
* Land
* Local operator
* Cooperative agreement
* Multisig wallet
* Baseline MRV
* Crop plan
* Impact metrics
* Governance process
* Treasury
* Reporting cadence
* Funding strategy
**Optional**
* DAO
* Farm registry
### 90-Day Roadmap
1. Week 1–2: Land assessment
2. Week 3–4: DAO proposal
3. Month 2: Infrastructure
4. Month 3: MRV begins
5. Quarter 2: First harvest
6. Year 1: Public dashboard
7. Year 2: Replication
## 🚀 Future Plans & Scaling Potential
### Growth Strategies
* **Geographic replication using the same Framework and schema.** Because the [Common Data Schema](/kokonut-framework/framework-components/common-data-schema) and four-phase process are already generalized rather than Adelphi-specific, a second farm can, in principle, plug into the same DAO/Guild/MRV infrastructure rather than starting over.
* **Chain expansion beyond Gnosis + Celo.** The [FAQ](/ecosystem-wiki/faq) lists Base as in development (home of the emerging Agentic Marketplace) and names Arbitrum and Ethereum Mainnet as further roadmap items, alongside Celo's mobile-first orientation as a fit for broader community access.
* **Agentic Marketplace maturation.** ERC-8004-based agent identity/reputation and x402 micropayments are positioned to let AI agents transact directly against farm and Guild work in the future — this is explicitly in development, not live (source: [Build with Kokonut](/build-with-kokonut)).
* **Framework upgrades driven by the Intelligence layer.** Because [Kokonut Intelligence](/kokonut-intelligence) already scores farms across financial, ecological, governance, and growth dimensions, that scoring data is positioned to inform how the Framework itself evolves — e.g., which phase gates or MRV requirements need tightening.
```mermaid theme={null}
flowchart LR
A["New Land / Community
e.g. Kokonut Terra Viva"] --> B["Phase I
Common Data Schema record created"]
B --> C["DAO Proposal & Funding Vote"]
C --> D["Shared Infrastructure Plugs In
DAO contracts · MRV stack · Kokonut Intelligence"]
D --> E["Phase II
Production & Regeneration begins"]
E --> F["Farm Data & Learnings"]
F -.improves.-> G["Kokonut Framework"]
G -.enables.-> A
```
Adelphi's replicability is no longer theoretical: Kokonut has signed an agreement for the adjacent land — roughly 50,000 m², more than three times Adelphi's footprint — to launch **Kokonut Terra Viva**, expected to go live soon. With the land deal secured, Terra Viva sits in Phase I (Planning & Preparation) today, making it the Framework's first real test of moving a second farm through the same four-phase process rather than a hypothetical next step.
## Vision for the Future
Kokonut's own framing describes a long-term shift from a single organization operating farms toward permissionless, replicable farm infrastructure that any aligned community can stand up using the same open tooling — DAO templates, the Common Data Schema, and the Intelligence layer — rather than remaining dependent on Kokonut Network as a central operator.
The Manifesto frames this explicitly around a set of stated freedoms and values for the communities involved, positioning Kokonut less as a company and more as shared infrastructure for regenerative coordination.
# How It Works
Source: https://kokonut.network/playbooks/regenerative-finance/how-it-works
## Implementation Process
The Kokonut Framework organizes farm development into four phases. Phase IV (Continuous Operations) isn't a "final" phase so much as an ongoing layer that runs underneath the other three from the point data collection starts:
```mermaid theme={null}
flowchart LR
A["Phase I
Planning & Preparation"] --> B["Phase II
Production & Regeneration"]
B --> C["Phase III
Consolidation & Expansion"]
C --> D["Phase IV
Continuous Operations"]
D -.MRV & reporting feed back into every phase.-> A
Adelphi["🥥 Kokonut Adelphi"] -.currently in.-> B
Terra["🌴 Kokonut Terra Viva
50,000 m², land signed"] -.entering.-> A
```
* **[Phase I — Planning & Preparation](/kokonut-framework/development-phases/phase-i):** site assessment, baseline data capture, syntropic planting design, DAO proposal drafting and community funding vote.
* **[Phase II — Production & Regeneration](/kokonut-framework/development-phases/phase-ii):** active planting, infrastructure build-out, first harvests, and the start of continuous MRV data capture — **this is where Kokonut Adelphi is today**.
* **[Phase III — Consolidation & Expansion](/kokonut-framework/development-phases/phase-iii):** scaling production, formalizing market/sales channels, and preparing the farm's data and track record for replication or follow-on funding.
* **[Phase IV — Continuous Operations](/kokonut-framework/development-phases/phase-iv):** steady-state farming with ongoing MRV, reporting, and reinvestment — feeding data back into governance and into the next farm's Phase I planning.
## Technology Solutions Used
```mermaid theme={null}
flowchart TD
L1["Governance Layer
$vKKN + Loot · Moloch DAO (Baal) on Gnosis Chain"]
L2["Guild Layer
6 Guilds: Tech, Impact, Comms, Governance, Finance, Community"]
L3["Treasury & Execution Layer
Gnosis Safe multisig · stablecoin tribute · Kokonut Seeds flywheel"]
L4["Farm / Asset Layer
Live farms — e.g. Kokonut Adelphi"]
L5["Intelligence & Data Layer
Common Data Schema · PostGIS/ClickHouse/Directus · EAS on Celo"]
L1 --> L2 --> L3 --> L4 --> L5
L5 -.attested farm data informs.-> L1
```
| Layer | Technology | Status |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- |
| DAO governance & treasury | Moloch DAO (Baal framework) on **Gnosis Chain**; \$vKKN (non-transferable governance shares) + Loot (transferable economic rights); Gnosis Safe multisig treasury | Live |
| Data standardization | Common Data Schema — a 13-field shared record structure so every farm reports data the same way | Live |
| MRV / field verification | Soil probes, satellite vegetation indices (NDVI/NDRE/MSAVI via Landsat 8/Sentinel), GPS-tagged tree tracking, mobile field logging, IPFS/Filecoin for immutable evidence storage | Live |
| Attestation | Ethereum Attestation Service (EAS) deployed on **Celo** for farm-data attestations, kept separate from Gnosis Chain governance | Live |
| Intelligence/analytics | Kokonut Intelligence — PostgreSQL/PostGIS (spatial), ClickHouse (time-series analytics), Directus (data management), Python-based scoring agents | Live, open-source |
| Agent access | Multi-agent AI ecosystem with MCP-based access to farm data for scoring, forecasting, and decision support | Live/developing, open-source |
| Agentic commerce (roadmap) | Agentic Marketplace, using ERC-8004 agent identity/reputation and x402 micropayments | In development |
#### **MRV pipeline, visually:**
```mermaid theme={null}
flowchart LR
A["Field data
soil probes, GPS tree tags, farm-operator logs"] --> D["MRV Payload"]
B["Satellite indices
NDVI / NDRE / MSAVI"] --> D
D --> E["IPFS / Filecoin
immutable evidence storage"]
E --> F["EAS Attestation
on Celo"]
F --> G["Kokonut Hub
public dashboard"]
G --> H["DAO, Guild & grant reporting"]
```
[Kokonut Intelligence](/kokonut-intelligence) layers a scoring system on top of this pipeline: a **Fortune 500 Farm Score** weights Financial performance (45%), Ecological outcomes (25%), Governance health (15%), and Growth trajectory (15%) into a single composite score, with tiers from Developing up through Bronze, Silver, Gold, and Platinum (800+).
It also runs Monte Carlo simulations for revenue forecasting and a Shannon diversity index for biodiversity scoring, and ships with a "Revenue Multiplier Opportunity Map" across 10 dimensions to surface where a given farm's income could grow.
Worth flagging for accuracy: the open-source repo's seed/demo dataset uses a fictitious "Kokonut Adelphi Demo Farm", purely to test the platform.
## Roles & Responsibilities
```mermaid theme={null}
flowchart LR
A["Proposal Drafted
by any Guild member"] --> B["Sponsored
by a $vKKN holder"]
B --> C["5-Day Voting Period
$vKKN holders vote"]
C --> D{"Passes?"}
D -->|Yes| E["Grace Period
dissenters may rage-quit"]
D -->|No| F["Proposal Rejected"]
E --> G["Execution
Gnosis Safe multisig"]
E -.66% retention threshold blocks execution.-> F
```
* **[DAO members](/ecosystem-wiki/the-kokonut-dao/dao-layers) (\$vKKN holders):** vote on proposals, hold non-transferable governance shares, and can rage-quit (exit with their proportional treasury share) if they disagree with a passed decision they didn't support.
* **[Guilds](/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao) (Technology, Impact, Communications, Governance, Finance, Community & Partnerships)** own specific domains of ongoing work; contributors progress through Contributor → Member → Steward → Emeritus tiers based on accumulated contribution.
* **Farm operators:** run day-to-day operations on the ground — at Adelphi, this is the Hernández family — and receive 40% of farm revenue in recognition of that operating role.
* **Community leaders / Stewards:** senior Guild members who mentor newer contributors and hold more governance weight in their domain as they accumulate track record.
## Tips & Best Practices
* **Separate forecasts from actuals, explicitly.** Every revenue and impact figure in Kokonut's own documentation is labeled as a forecast until harvested/measured — worth carrying into any pitch or grant application so funders aren't misled about what's realized vs. projected.
* **Use a short-cycle crop to bridge long-cycle ones.** Coconut takes years to mature; lettuce doesn't. Pairing them is what keeps the farm's cash flow alive during the wait.
* **Don't let governance tokens double as your treasury's volatility risk.** Kokonut's stablecoin-tribute design is a direct response to this common DAO failure mode.
* **Build the data schema before you need to compare two farms.** The Common Data Schema exists precisely so that a second farm's data is comparable to Adelphi's from day one, instead of requiring a retroactive cleanup.
* **Don't claim infrastructure is "live" before it's deployed.** The docs are careful to separate what's live (Gnosis DAO, Celo attestations) from what's in development (the Ethereum-based Agentic Marketplace) — a discipline worth keeping in any external-facing version of this playbook.
# Introduction
Source: https://kokonut.network/playbooks/regenerative-finance/introduction
## Playbook Intro
Regenerative agriculture projects usually face two disconnected problems at once: farmers need patient capital and trustworthy sales channels, and funders (DAOs, grant programs, impact investors) need proof that money produced real ecological and social outcomes rather than a nice pitch deck.
Kokonut Network was built to close that gap in the Dominican Republic by fusing a working farm with a Web3 coordination and verification stack, so that funding, farming, and proof of impact happen within a single connected loop rather than three disconnected processes.
This playbook exists to make that model **legible and repeatable**. It walks through how Kokonut's DAO, Common Data Schema, MRV pipeline, and Guild structure work together, using the flagship Kokonut Adelphi farm as the live case study, so a different community can adopt the same coordination pattern without having to independently invent DAO tooling, an impact-measurement framework, and a farm-funding process from zero.
### Target Audience
This playbook is designed for:
* **Local ReFi leaders and regenerative-agriculture practitioners** who have (or can access) land and farming know-how but lack a funding and verification pipeline.
* **DAOs and Web3-native communities** — especially those already comfortable with Moloch-style governance, EAS attestations, or Gnosis Safe treasuries — looking for a concrete regenerative-agriculture use case to fund or replicate.
* **Cooperatives and community organizations** in Latin America and the Caribbean (or similar contexts) that want a proof-first way to demonstrate impact to grant funders without building custom MRV tooling.
* **ReFi builders and open-source contributors** who want to extend, fork, or integrate with Kokonut's already-open repositories (Common Data Schema, Kokonut Intelligence, the emerging Agentic Marketplace).
**What you'd need to replicate this:** access to land (owned, leased, or in cooperative trust), at least one person willing to do the on-the-ground farm-operator role, basic comfort with a multisig wallet and a DAO voting interface, and enough patience to run field data collection consistently — the MRV pipeline is only as good as the soil-probe and photo-log discipline behind it.
Kokonut's own tooling (schema, contracts, dashboards) is largely open-source, which lowers the technical lift considerably (source: [Build with Kokonut](/build-with-kokonut)).
***
## Playbook Description
### Overview
Kokonut Network's stated objective is to prove that regenerative farms can be **funded transparently, operated profitably, and verified on-chain** at the same time — not sequentially, and not as separate workstreams.
For local communities, the relevance is direct: it offers a funding pathway that doesn't require pre-existing institutional credibility, because the DAO, Guilds, and MRV pipeline generate that credibility as the farm operates.
For the wider ReFi ecosystem, it offers a working example of "proof-first" grant qualification — mapping a real farm's documented assets against funder eligibility criteria instead of a speculative roadmap.
### Impact
* **Economic:** 7 direct jobs at Adelphi alone, a \$149,110/year revenue forecast across lettuce, passion fruit, coconut, and eggs, and a revenue split that returns 40% of farm value directly to the Hernández family as farm operators, rather than only to outside capital.
* **Ecological:** Syntropic/agroforestry planting design, 12+ native and at-risk species reintroduced through the farm nursery, and continuous satellite + soil monitoring (NDVI/NDRE/MSAVI indices) to track vegetation and soil trends over time rather than a one-time baseline.
* **Social:** SDG alignment centers on SDG 1 (No Poverty), SDG 2 (Zero Hunger), SDG 5 (Gender Equality), SDG 8 (Decent Work), and SDG 15 (Life on Land) as primary targets for Adelphi, with a broader 17-SDG map at the Framework level covering secondary contributions.
* **Public goods:** 40% of Adelphi's forecast revenue is routed to Kokonut's public-goods fund by design, not as an afterthought bolted onto a for-profit model.
### Innovation Highlight
What differentiates Kokonut from a generic "ReFi farm" pitch is that each piece reinforces the others instead of standing alone:
* **The Kokonut Framework** — a four-phase, repeatable methodology (not just a manifesto) with a shared 13-field Common Data Schema, so a second or third farm doesn't require reinventing how data is structured.
* **A live farm as proof, not a whitepaper promise** — Kokonut Adelphi is operating and reporting real numbers today, which is unusual in a ReFi space where many projects fund infrastructure before anything is growing.
* **The Guild contribution system** — governance work is organized into 6 functional Guilds (Technology, Impact, Communications, Governance, Finance, Community & Partnerships) with a tiered contributor path (Contributor → Member → Steward → Emeritus), which turns "DAO participation" into defined, ownable work rather than token-weighted voting (source: [Kokonut Guilds](/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao)).
* **On-chain MRV with a real attestation trail** — field and satellite data flow into IPFS-anchored payloads and get attested on-chain via EAS on Celo, giving funders a verifiable trail instead of a self-reported PDF.
## Local Context
Kokonut is deliberately rooted in the Dominican Republic's specific conditions: it works with smallholder-scale plots (Adelphi is 15,725 m², not an industrial plantation), uses crops already viable in Monte Plata's climate (coconut, passion fruit, lettuce), and frames its founders' story — Yanny and Neury Hernández converting family land into Adelphi — as a locally credible entry point rather than an externally imposed model.
The seven challenges the Adelphi page documents — land-use pressure, water access, market access for smallholders, youth outmigration from rural areas, limited access to capital, climate vulnerability, and knowledge/technology gaps — are framed as Dominican-specific but are common across much of the Caribbean and Central America.
**What would need adapting elsewhere:** the crop mix and syntropic planting design are climate- and market-specific and would need to be redesigned for a different agroecological zone; the DAO/legal wrapper would need review against local cooperative, securities, and tax law outside the DR (see Regulatory Compliance below — this is a genuine open question even for the DR context); and the "proof-first" grant-qualification approach depends on funders who value documented outcomes over pitch polish, which isn't universal across all funding programs.
# Regenerative & Technical Alignment
Source: https://kokonut.network/playbooks/regenerative-finance/regenerative-and-technical-alignment
## Regenerative Outcomes
### Web3 Integration
Kokonut runs a deliberately **split-chain architecture**: DAO governance, membership shares (\$vKKN), transferable economic rights (Loot), and treasury execution live on **Gnosis Chain** via a Moloch DAO (Baal framework) and Gnosis Safe multisig, while farm-data attestations run through the **Ethereum Attestation Service deployed on Celo**, with a dedicated schema registry and resolver contract.
This separation means governance risk and data-verification risk sit on different infrastructure rather than being coupled to one chain's uptime or gas conditions.
### Web3 Return-On-Investment
Value creation is measured, not just claimed: Adelphi's Common Data Schema record carries a concrete revenue/allocation split, and Kokonut Intelligence's Fortune 500 Farm Score gives that value a comparable, on-chain-attestable number across financial, ecological, governance, and growth dimensions rather than leaving "impact" as a qualitative claim.
As with any DAO-governed asset, this isn't investment advice or a guaranteed return — \$vKKN is explicitly a non-transferable governance instrument, not a security-like yield product, and Loot's economic value is tied to actual farm performance.
### Reporting & Transparency
The reporting chain is: field/satellite data → MRV payload → IPFS/Filecoin storage → EAS attestation on Celo → public Kokonut Hub dashboard → DAO/Guild/grant reporting.
Ecological scoring draws on the externally maintained **Ecological Benefits Framework (EBF Commons)** rather than an in-house-only rubric, which gives funders an outside reference point for how "ecological impact" is being scored.
### Technical Integration
Interoperability is designed at two levels: the Common Data Schema is a shared JSON/TypeScript-style interface any farm (or any external tool) can read and write against, and Kokonut Intelligence is fully open-source, with MCP-based agent access so third-party AI agents or platforms can query farm data directly rather than needing a bespoke integration.
```mermaid theme={null}
flowchart TD
A["Raw Farm Data
MRV payloads, EAS attestations"] --> B["PostgreSQL / PostGIS
spatial & relational storage"]
A --> C["ClickHouse
time-series analytics"]
B --> D["Directus
data management layer"]
C --> D
D --> E["Python Scoring Agents
Fortune 500 Farm Score, Monte Carlo forecasts, Shannon diversity index"]
E --> F["Kokonut Hub
public dashboard"]
E --> G["AI Agent Access
via MCP"]
```
Interoperability now extends past Kokonut's own schema: Kokonut Intelligence and the Farm Registry are built to be compatible with the Common Impact Data Standard (CIDS) — the open ontology maintained by Common Approach for representing impact data (what, who, how much, contribution and risk) so it can be read by any CIDS-aligned registry or platform — and that compatibility is already integrated into the Intelligence Layer rather than sitting on the roadmap.
The fit is a natural one: Kokonut's own six Pillars of Value (What, Who, How Much, Contribution, Risk, and Public Goods) already track closely with CIDS's impact dimensions, which is part of why the two align without requiring a parallel data model.
## Regen Coordination Stack Alignment
**Regen Coordination** is an existing coalition (GreenPill Network, ReFi DAO, and Celo Public Goods) organized around ReFi Local Nodes and GreenPill Chapters, with its own community playbook library. Kokonut has real, verifiable overlap with that stack already: its attestation layer runs on **Celo**, the same chain Celo Public Goods (a Regen Coordination co-founder) is built around, and its ecological scoring already references the external **EBF Commons** framework rather than reinventing one — both genuine technical alignment points, not aspirational ones.
The Common Data Schema plays a role analogous to what a "Common Approach" shared data model would need across a coordination network: a standard record structure that any participating farm or node can populate in the same way.
Kokonut Network's relationship with Regen Coordination moved from proposal to a confirmed, funded [partnership](https://hub.regencoordination.xyz/t/regen-coordination-gg23-partnerships-overview-what-s-next/234) through the Regen Coordination Global GG23 round (\~April 2025): a \$96,000 ImpactQF matching pool across 50 ReFi projects, in which Kokonut was named among the round's standout high-impact projects.
The original partnership proposal set out three further deliverables beyond that funding round: co-creating and publishing a Local ReFi Toolkit Playbook for standing up a Web3-powered syntropic farm using the Kokonut Framework — this playbook is a direct output of that commitment; collaborating on a prospective Celo-based Kokonut Farm DAO with on-chain tree governance and public-goods allocation, potentially alongside ReFi Local Nodes or GreenPill chapters; and deeper integration with the Regen Coordination-aligned stack, including Karma GAP (Kokonut maintains an active public [Karma GAP profile](https://link.kokonut.network/karma)), Hypercerts, and Silvi — the last of which is already running in Adelphi's MRV pipeline for GPS-based tree tracking.
## Start Your Own ReFi Farm
The Kokonut Framework is open. The software is open source. The data model is open. The governance is reproducible. You don't need permission to begin.
Everything here is free to fork, read, and test — no permission, no cost, no commitment to look.
**📞** [**Book a 20-minute call to talk about replication or partnership**](https://link.kokonut.network/meeting)
Or, if you're ready to go deeper on your own: explore the [Framework docs](/kokonut-framework/Introduction), fork the [repositories](https://github.com/wasalo/Kokonut-Intelligence), or join the [Discord community](/ecosystem-wiki/open-collaboration-invitation).
# Executive Summary
Source: https://kokonut.network/playbooks/regenerative-finance/summary
> **Source coverage note:** All 38 pages indexed at [kokonut.network/llms.txt](https://kokonut.network/llms.txt) were fetched and reviewed, spanning Kokonut 101, the Adelphi farm wiki, the Kokonut DAO, the Kokonut Framework, Kokonut Intelligence, and Kokonut × AI Agents. The [wasalo/Kokonut-Intelligence](https://github.com/wasalo/Kokonut-Intelligence) GitHub README was also fetched directly as the technical source of truth for the data/AI layer.
***
# Build a Regenerative Farm That Funds Itself, Proves Its Impact, and Scales
The open-source framework behind Kokonut Adelphi — a live, DAO-funded syntropic farm in the Dominican Republic — was built so any ReFi community, cooperative, or DAO can replicate it without starting from zero.
**📞** [**Book a 20-minute call to talk about replication or partnership**](https://link.kokonut.network/meeting)
Most regenerative agriculture projects struggle with three problems: finding long-term funding, measuring real impact, and coordinating people effectively. Kokonut Network solves all three with an open-source framework that combines regenerative farming, cooperative ownership, AI-powered Measurement, Reporting & Verification (MRV), and Web3 governance.
This playbook shows exactly how Kokonut transformed a family farm in the Dominican Republic into a living proof-of-impact ecosystem — and how any community can replicate the model.
## What You'll Learn
After reading this playbook, you'll understand how to:
* ✅ launch a regenerative agriculture cooperative
* ✅ Organize contributors through DAO governance
* ✅ finance farms without depending entirely on grants
* ✅ measure ecological and financial impact
* ✅ build transparent MRV systems
* ✅ attract funders using verifiable data instead of promises
## Who Should Use This
This playbook is designed for:
* ReFi communities
* Regenerative farmers
* NGOs
* Cooperatives
* Municipalities
* Grant programs
* Impact investors
* GreenPill Chapters
* ReFi Local Nodes
* DAO builders
* Ecosystem funders
**📞** [**Book a call**](https://link.kokonut.network/meeting) if any of this sounds like you — or keep reading for the full picture.
## 🌟 TLDR
Kokonut Network is a Dominican Republic–based regenerative agriculture cooperative that pairs a live, working syntropic farm — Kokonut Adelphi, 15,725 m² in Gonzalo, Sabana Grande de Boyá, Monte Plata (source: Adelphi Executive Summary) — with a full Web3 coordination stack: a Moloch-style DAO on Gnosis Chain for governance and treasury, a Common Data Schema and on-chain MRV pipeline (soil probes, satellite indices, IPFS, and EAS attestations on Celo) for verification, and Kokonut Intelligence — an open-source PostgreSQL/PostGIS, ClickHouse, Directus, and AI-agent data layer — for scoring and decision support.
The Kokonut Framework's four phases (Planning & Preparation, Production & Regeneration, Consolidation & Expansion, Continuous Operations) give any community a repeatable path from raw land to a funded, verified, revenue-generating regenerative farm, with Adelphi as the live proof: 96 coconut trees, 560 passion fruit vines, 110 free-range hens, 7 jobs created, and a \$149,110/year revenue forecast, 40% of which routes to a public-goods fund.
| Traditional NGO | Typical ReFi Project | Kokonut |
| --------------- | -------------------- | -------------------- |
| Donations | Grants | Productive Assets |
| PDFs | Dashboards | On-chain Proof |
| Reports | Metrics | Continuous MRV |
| Centralized | Tokenized | Cooperative |
| Impact Claims | Impact Estimates | Verifiable Evidence |
| One Farm | Pilot | Replicable Framework |
This playbook exists so that other local ReFi leaders, cooperatives, and DAOs can replicate the model rather than rebuild it from scratch.
***
## Proven in the Real World
**The Farm (Kokonut Adelphi)**
* 📍 Gonzalo, Sabana Grande de Boyá, Monte Plata, Dominican Republic
* 📐 15,725 m² total site · 13,838 m² under active agricultural use
* 🥥 96 coconut trees
* 🍈 560 passion fruit vines
* 🥬 large-scale lettuce production
* 🐔 110 free-range hens (100 eggs/day)
* 👷 7 direct jobs created
* 🌱 12+ native/at-risk species reintroduced in the farm nursery
* 💵 \$149,110/year forecast revenue — 40% to the Hernández family, 40% (\$59,644/yr) to Kokonut's public-goods fund, 20% to Kokonut Network
* 🎯 Currently in **Phase II — Production & Regeneration**
🌴 Next up: **Kokonut Terra Viva** — 50,000 m² on adjacent land, deal signed, launching soon.
**The DAO**
* ⚖️ Moloch DAO (Baal framework) on **Gnosis Chain**
* 🪙 \$vKKN — non-transferable governance shares · Loot — transferable economic/exit rights
* 🛡️ 66% retention threshold to block a proposal · rage-quit protection for dissenting members
* 🏛️ 6 Guilds: Technology, Impact, Communications, Governance, Finance, Community & Partnerships
* 🌐 3,000+ network/community members (source: Landing Page)
**The Framework**
* 🔄 4 phases: Planning & Preparation → Production & Regeneration → Consolidation & Expansion → Continuous Operations
* 🌿 5 Principles of Regeneration · 🌳 8 Forms of Capital · 💠 6 Pillars of Value
* 🗂️ 13-field Common Data Schema shared across every farm for interoperability
* 🎯 5 primary SDGs for Adelphi (1, 2, 5, 8, 15) inside a 17-SDG framework map
**The Intelligence Layer**
* 🧱 PostgreSQL/PostGIS + ClickHouse + Directus + Python agents
* ⛓️ EAS attestations on **Celo** for farm-data verification; DAO governance on Gnosis Chain
* 🏆 Fortune 500 Farm Score: Financial 45% · Ecological 25% · Governance 15% · Growth 15%
* 🤖 Multi-agent AI ecosystem for MRV analysis, scoring, and decision support (open source: [github.com/wasalo/Kokonut-Intelligence](https://github.com/wasalo/Kokonut-Intelligence))
## 🎒 Key Resources & Contact
### Learning Materials
* Kokonut 101: [Executive Summary](/ecosystem-wiki/kokonut-101/executive-summary), [Vision](/ecosystem-wiki/kokonut-101/kokonut-vision), [Manifesto](/ecosystem-wiki/kokonut-101/manifesto), [Problem](/ecosystem-wiki/kokonut-101/problem), [Solution](/ecosystem-wiki/kokonut-101/solution)
* Kokonut Adelphi farm wiki: [Background Story](/ecosystem-wiki/kokonut-farms/adelphi/background-story), [Crops & Harvest Forecast](/ecosystem-wiki/kokonut-farms/adelphi/crops-and-harvest-forecast), [Crops, Biodiversity & Infrastructure](/ecosystem-wiki/kokonut-farms/adelphi/crops-biodiversity-and-infrastructure), [SDGs](/ecosystem-wiki/kokonut-farms/adelphi/sustainable-development-goals)
* [Measurement, Reporting & Verification](/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification)
* The Kokonut DAO: [DAO Layers](/ecosystem-wiki/the-kokonut-dao/dao-layers), [Governance Framework](/ecosystem-wiki/the-kokonut-dao/governance-framework), [Guilds](/ecosystem-wiki/the-kokonut-dao/kokonut-guilds-dao), [Moloch DAO](/ecosystem-wiki/the-kokonut-dao/kokonut-moloch-dao), [Proposal Templates](/ecosystem-wiki/the-kokonut-dao/proposal-templates)
* Kokonut Framework: [Introduction](/kokonut-framework/Introduction), the four [Development Phases](/kokonut-framework/development-phases/phase-i), [Common Data Schema](/kokonut-framework/framework-components/common-data-schema), [5 Principles of Regeneration](/kokonut-framework/framework-components/framework-features/5-principles-of-regeneration), [8 Forms of Capital](/kokonut-framework/framework-components/framework-features/8-forms-of-capital), [Why Syntropic Farming](/kokonut-framework/why-syntropic-farming)
* [Kokonut Intelligence](/kokonut-intelligence) · [Kokonut × AI Agents](/kokonut-x-ai-agents) · [Build with Kokonut](/build-with-kokonut)
* [FAQ](/ecosystem-wiki/faq) · [Glossary](/ecosystem-wiki/glossary)
* Open-source repos: [Kokonut-Public-Site](https://github.com/wasalo/Kokonut-Public-Site) (docs) · [Kokonut-Intelligence](https://github.com/wasalo/Kokonut-Intelligence) (data/AI layer) · [Kokonut-Agentic-Marketplace](https://github.com/wasalo/Kokonut-Agentic-Marketplace) (in development)
* Live data: Kokonut Hub, [Legacy Data Hub](https://hub.kokonut.network/projects/41) (Adelphi's live project page is linked from the Executive Summary)
### Representatives
Kokonut Network / **Alejandro ("Wasabi")** — reachable directly at [alejandro@kokonut.network](mailto:alejandro@kokonut.network), or through the Discord, [bookable call link](https://link.kokonut.network/meeting), and [X/Twitter](https://x.com/WasabiNetwork) account linked from the [Open Collaboration Invitation](/ecosystem-wiki/open-collaboration-invitation) page; the `wasalo` GitHub organization hosts the open-source repos above.