> ## Documentation Index
> Fetch the complete documentation index at: https://kokonut.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Framework — Detailed Introduction

> The full Kokonut Framework reference covering standards, phases, the 13-field schema, regenerative methods, impact interpretation, evidence, governance and replication.

# The Kokonut Framework is the shared methodology behind Kokonut farms.

The Kokonut Framework gives farms a common baseline for:

* describing the farm and its context;
* planning development;
* applying regenerative principles;
* structuring value and impact questions;
* recording operational activity;
* producing reviewable evidence;
* learning across farms over time.

Its purpose is **not** to make every farm identical.

Its purpose is to make farms interoperable enough that local operators, contributors, reviewers, capital participants, researchers, and software systems can work from compatible information.

> **The goal is interoperability, not uniformity: shared structure where coordination benefits from it, local adaptation where land, people, markets, and regulation differ.**

> **[Start with the Common Data Schema](https://kokonut.network/kokonut-framework/framework-components/common-data-schema.md)**
>
> See the current 13-field baseline record used to describe a farm before deeper review, tooling, or comparison.

> **[Follow the four development phases](https://kokonut.network/kokonut-framework/development-phases/phase-i.md)**
>
> Move from planning and preparation into production, consolidation, and continuous evidence-driven improvement.

> **[See the Framework at Adelphi](https://kokonut.network/ecosystem-wiki/kokonut-farms/adelphi/summary.md)**
>
> Review Kokonut's first live reference farm and distinguish documented state, forecasts, operations, and evidence.

> **[Understand the evidence layer](https://kokonut.network/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification.md)**
>
> See how observations become structured records, review, publication, optional attestations, and interpretation.

> [!NOTE]
>
> **The Framework is methodology, not ownership or command authority.** It can define shared fields, phases, evidence expectations, and reusable methods without deciding every farm's crops, labor, land rights, operating choices, or local relationships.

***

## The Framework in one sentence

> **Describe the farm consistently → plan through shared phases → operate locally → record what happened → review the evidence → learn and improve.**

That sequence is more durable than any particular tool, chain, dashboard, or governance mechanism.

```mermaid theme={null}
flowchart LR
    A["Local farm context"] --> B["Shared baseline record"]
    B --> C["Development phase + plan"]
    C --> D["Local agricultural execution"]
    D --> E["Operational records + observations"]
    E --> F["Review + publication"]
    F --> G["Interpretation + reporting"]
    G --> H["Farm / governance / partner decisions"]
    H --> I["Updated plan + shared learning"]
    I --> C
```

The Framework connects those steps.

It does not collapse them into one authority.

***

## What the Framework standardizes — and what it does not

| The Framework can standardize | The Framework should not automatically standardize |
| - | - |
| Baseline farm fields and terminology | Land ownership or legal title |
| Development phases | Crop mix across every farm |
| Regenerative principles | Daily agronomic decisions |
| Evidence and reporting expectations | Local labor arrangements |
| Value-accounting categories | One universal revenue-sharing model |
| Shared claim vocabulary | Community priorities in every location |
| Compatibility across records and tools | One governance mechanism for every farm |
| Review and learning structures | One technology stack for every operator |

This boundary is central to the Framework.

A shared schema can make records compatible.

It does not make the farm a franchise.

A shared development phase can organize work.

It does not make every landscape move at the same speed.

A shared evidence standard can make a claim easier to inspect.

It does not make the claim automatically true.

***

## The current Framework building blocks

The Framework is easier to navigate through the components that are actually documented across this section.

| Building block | Current role | Go deeper |
| - | - | - |
| **Common Data Schema** | 13-field baseline farm record | [Common Data Schema](https://kokonut.network/kokonut-framework/framework-components/common-data-schema.md) |
| **Development Phases** | Four-stage lifecycle for planning, production, consolidation, and continuous evidence/learning | [Phase I](https://kokonut.network/kokonut-framework/development-phases/phase-i.md) |
| **5 Principles of Regeneration** | Shared regenerative practice principles | [5 Principles](https://kokonut.network/kokonut-framework/framework-components/framework-features/5-principles-of-regeneration.md) |
| **Pillars of Value** | Six questions for understanding value, contribution, risk, and public goods | [Pillars of Value](https://kokonut.network/kokonut-framework/framework-components/pillars-of-value.md) |
| **8 Forms of Capital** | Broader value categories beyond financial capital | [8 Forms of Capital](https://kokonut.network/kokonut-framework/framework-components/framework-features/8-forms-of-capital.md) |
| **Positive-impact methodology** | Method for connecting activities, evidence, value categories, and claims | [Positive Impact](https://kokonut.network/kokonut-framework/framework-components/framework-features/methodology-positive-impact.md) |
| **SDG methodology** | Maps supported evidence to primary and secondary Sustainable Development Goals | [SDGs](https://kokonut.network/kokonut-framework/framework-features/Sustainable-Development-Goals.md) |
| **Ecological impact add-ons** | Additional ecological-benefit and risk interpretation tools | [Ecological Impact Frameworks](https://kokonut.network/kokonut-framework/framework-add-ons/ecological-impact-frameworks.md) |
| **MRV** | Evidence lifecycle shared with the farm and data layers | [MRV](https://kokonut.network/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification.md) |
| **Impact calculators** | Scenario and planning tools; outputs are not achieved impact | [Impact Calculator](https://kokonut.network/kokonut-framework/impact-calculator.md) |

> [!NOTE]
>
> The earlier standalone [`wasalo/kokonut-framework`](https://github.com/wasalo/kokonut-framework) repository is public but currently archived. Treat it as historical reference unless it is reactivated. This Knowledge Base is the current documentation surface for the Framework.

***

## Four development phases organize the farm lifecycle

The Framework currently uses four development phases.

| Phase | Primary purpose | Typical evidence |
| - | - | - |
| **I — Planning & Preparation** | Understand the site, operators, baseline, design, infrastructure needs, risks, and funding requirements | Site records, schema, plans, budgets, baseline evidence |
| **II — Production & Regeneration** | Put the farm system into operation | Planting, infrastructure, field activity, production records, MRV |
| **III — Consolidation & Expansion** | Improve operational reliability, markets, recurring systems, and farm capacity | Multi-cycle records, financial actuals, training, quality controls, expanded evidence |
| **IV — Continuous MRV & Improvement** | Maintain longitudinal evidence, compare plans with actuals, report, adapt, and learn | Repeated measurements, reports, variance analysis, review records |

Phase IV is not a finish line after which measurement stops.

Evidence and learning should continue throughout farm operations.

> **[Phase I](https://kokonut.network/kokonut-framework/development-phases/phase-i.md)**
>
> Planning & Preparation.

> **[Phase II](https://kokonut.network/kokonut-framework/development-phases/phase-ii.md)**
>
> Production & Regeneration.

> **[Phase III](https://kokonut.network/kokonut-framework/development-phases/phase-iii.md)**
>
> Consolidation & Expansion.

> **[Phase IV](https://kokonut.network/kokonut-framework/development-phases/phase-iv.md)**
>
> Continuous MRV, reporting, learning, and improvement.

***

## The Common Data Schema is the baseline — not the approval

The current Common Data Schema defines **13 required fields**.

Its purpose is to make a farm record structured enough for multiple actors and systems to work with it.

That can support:

* farm intake;
* proposal preparation;
* data ingestion;
* comparison;
* MRV linking;
* reporting;
* analysis;
* agent workflows.

It should not be interpreted as:

> “13 fields completed = farm approved, funded, verified, or investment-ready.”

Those are separate decisions.

A complete record can still contain:

* weak assumptions;
* unresolved legal questions;
* poor economics;
* insufficient evidence;
* operating risks;
* missing reviewer approval.

> **Structure makes a farm easier to inspect. It does not substitute for judgment.**

***

## Regenerative principles guide practice without becoming a recipe

The Framework documents five regenerative principles as the shared agricultural baseline.

They help organize practice around areas such as:

* soil cover and soil protection;
* biodiversity and diversity;
* perennial and multi-layer systems;
* animal integration where appropriate;
* on-site or biologically oriented inputs and nutrient cycling.

Those principles should guide design and review.

They should not be interpreted as evidence that a desired ecological outcome already occurred.

For example:

| Evidence level | Example |
| - | - |
| **Principle** | Maintain soil cover |
| **Implemented practice** | Mulch / living cover applied |
| **Measurement** | Repeated cover or soil observation |
| **Interpretation** | Evidence supports a claim about erosion or soil improvement |

The last step requires more than documenting the intention.

***

## Value frameworks help ask better questions

The Framework does not reduce farm value to revenue alone.

### Pillars of Value

The six Pillars of Value ask:

1. **WHAT** value is being created?
2. **WHO** experiences the value?
3. **HOW MUCH** changes?
4. **CONTRIBUTION** — what changed because of this intervention?
5. **RISK** — what may not happen or may not persist?
6. **PUBLIC GOODS** — what value extends beyond the immediate transaction?

These are analytical questions.

They do not automatically calculate or certify impact.

### 8 Forms of Capital

The Framework also uses eight capital categories:

* Natural;
* Financial;
* Social;
* Human;
* Material;
* Intellectual;
* Cultural;
* Health.

The purpose is to make different forms of value visible without pretending they are interchangeable.

A stronger financial result does not automatically compensate for ecological damage.

A biodiversity intervention does not automatically prove social benefit.

> **The Framework can hold multiple forms of value in the same analysis without declaring one form sovereign over all the others.**

***

## MRV supplies the evidence layer

The Framework and MRV are related but different.

**The Framework** defines shared structures, methods, phases, and interpretation tools.

**MRV** defines how operational observations become reviewable evidence.

The current MRV sequence is:

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

That means the Framework should not assume a fixed pipeline where every record must move through IPFS and EAS.

Different evidence may use different storage and publication paths.

EAS can add public provenance for significant records.

It does not turn a weak source record into scientific truth.

> **[Read the MRV evidence model](https://kokonut.network/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification.md)**
>
> Review evidence classes, record lifecycle, forecast boundaries, attestation limits, remote sensing, and current maturity.

***

## Kokonut Intelligence implements data infrastructure around the Framework

[Kokonut Intelligence](https://kokonut.network/kokonut-intelligence.md) is not the Framework itself.

It provides infrastructure that can operationalize Framework concepts through:

* canonical farm records;
* operational events;
* review states;
* analytics;
* forecasting;
* reports;
* scoring;
* EAS integration on Celo;
* agent-access workflows.

The distinction matters.

A methodology can remain valid even if a software implementation changes.

And a software score should not become a new methodology merely because it can be calculated.

| Layer | Question |
| - | - |
| **Framework** | What structures and methods should farms share? |
| **MRV** | How should evidence and claims be handled? |
| **Kokonut Intelligence** | How do we store, review, analyze, publish, and automate around those records? |
| **Kokonut Hub** | What published farm/project information can people inspect? |

***

## Governance uses the Framework — it does not own the Framework's subject matter

The Framework can make a farm proposal easier to evaluate.

That does not mean every Framework question belongs to the Moloch DAO.

Different decisions have different authorities.

| Decision | Primary responsibility |
| - | - |
| Shared DAO treasury capital | Moloch DAO |
| Routine farm operations | Local farm operators |
| Contribution work / domain review | Guilds and relevant reviewers |
| Shared Framework schema / methodology | Framework stewards + affected domain reviewers |
| Scientific / ecological claim review | Qualified evidence reviewers |
| Technical implementation | Technical contributors within approved scope |

A Moloch proposal may fund a Framework improvement.

That vote does not make token holders the scientific, agronomic, or technical authority over the content of the method.

[Read the DAO Architecture →](https://kokonut.network/ecosystem-wiki/the-kokonut-dao/dao-layers.md)

***

## Who uses the Framework

> **Farm operators**
>
> Use shared records and phases while preserving local judgment over crops, timing, water, labor, maintenance, and field response.

> **Contributors & Guilds**
>
> Use the Framework to identify bounded work, domain dependencies, evidence needs, and reusable improvements.

> **Capital governance participants**
>
> Use compatible farm information to evaluate Moloch-scoped funding decisions without treating treasury voting as farm management.

> **Impact & research reviewers**
>
> Use shared terminology, baselines, evidence classes, value frameworks, and reporting periods to evaluate claims.

> **Developers**
>
> Use schemas and documented interfaces to build compatible data, MRV, analytics, and reporting tools.

> **Partners & grant reviewers**
>
> Use structured records and evidence to understand what is documented, modeled, delivered, and still uncertain.

***

## Adelphi is the first live reference implementation

Adelphi is where the Framework has its clearest real-world reference.

It combines:

* locally operated land;
* farm-development phases;
* regenerative practice;
* crop and infrastructure systems;
* public-goods funding history;
* forecasts and actual records;
* MRV;
* Kokonut Hub publication;
* governance and contributor coordination.

That makes Adelphi useful for learning.

It does **not** make Adelphi a universal template.

> [!WARNING]
>
> **Adelphi is a reference implementation, not proof of universal scalability.** Its crops, economics, community context, operators, biodiversity, infrastructure, and market conditions should not be copied blindly to another site.

[Explore Adelphi →](https://kokonut.network/ecosystem-wiki/kokonut-farms/adelphi/summary.md)

***

## Terra Viva is the next replication test

The current documentation identifies **Terra Viva** as the next major test of Framework portability.

Terra Viva is described as roughly **50,000 m² of adjacent land under agreement** entering:

**Phase I — Planning & Preparation**

That status matters.

Terra Viva is useful because it can help answer questions that Adelphi alone cannot:

* Which Framework fields transfer cleanly?
* Which methods need local adaptation?
* Which assumptions were specific to Adelphi?
* How should multi-farm comparison work?
* Which evidence can be normalized?
* Where does governance need to remain farm-specific?

It is **not yet evidence of successful multi-farm replication**.

***

## What the Framework can support — and what it cannot guarantee

| The Framework can support | It cannot guarantee |
| - | - |
| More comparable baseline records | Comparable farm outcomes |
| Better-structured funding requests | Funding approval |
| Clearer development milestones | Successful farm execution |
| Shared regenerative principles | Measured ecological improvement |
| More consistent evidence requirements | Scientific certification |
| Stronger forecast-vs-actual learning | Forecast accuracy |
| Reusable reporting structures | Impact |
| Cross-farm analysis | Identical local conditions |
| Better governance inputs | Good governance decisions |
| Agent-readable records | Correct autonomous decisions |

> [!NOTE]
>
> **The Framework reduces ambiguity. It does not remove uncertainty.**

***

## Current maturity of the Framework

| Component | Current status | Interpretation |
| - | - | - |
| **Framework documentation** | **Live and evolving** | Shared methods are documented and actively refined |
| **Common Data Schema** | **Active baseline** | Current 13-field structure; subject to compatibility-aware revision |
| **Four development phases** | **Active methodology** | Shared lifecycle model used across Framework documentation |
| **5 Principles of Regeneration** | **Active methodology** | Shared practice principles, not outcome guarantees |
| **Pillars of Value** | **Active analytical framework** | Helps structure value questions |
| **8 Forms of Capital** | **Active value taxonomy** | Organizes forms of value beyond finance |
| **Positive-impact methodology** | **Active and evolving** | Interpretation depends on evidence quality |
| **SDG methodology** | **Active and evolving** | Alignment and outcomes must remain distinct |
| **Ecological impact add-ons** | **Analytical / decision-support tooling** | Not external certification by themselves |
| **Impact calculators** | **Planning / scenario tools** | Outputs are modeled, not achieved impact |
| **Adelphi** | **Live reference implementation** | Strongest current real-world Framework example |
| **Terra Viva** | **Phase I / planning** | Next replication test, not an operating proof of scale |

***

## Framework principles for this documentation sprint

As the Framework pages are improved, they should preserve these rules.

1. **Interoperability, not uniformity.**
2. **Local operators retain local operating authority.**
3. **Shared structure does not equal automatic approval.**
4. **Implemented practice does not equal measured outcome.**
5. **Forecast does not equal actual.**
6. **Attestation does not equal scientific certification.**
7. **Framework methodology and software implementation remain distinguishable.**
8. **Governance authority stays scoped to the decision being made.**
9. **Public-goods and economic arrangements should follow the approved farm-specific arrangement rather than an unsupported universal rule.**
10. **Replication claims should grow only as multi-farm evidence grows.**

***

## Read the Framework in this order

**1. 1. Establish the baseline record**

Read the [Common Data Schema](https://kokonut.network/kokonut-framework/framework-components/common-data-schema.md) to understand the current 13-field farm record and where its assumptions need evidence.

**2. 2. Understand value before scoring it**

Read the [Pillars of Value](https://kokonut.network/kokonut-framework/framework-components/pillars-of-value.md) to understand WHAT, WHO, HOW MUCH, CONTRIBUTION, RISK, and PUBLIC GOODS.

**3. 3. Understand regenerative practice**

Read the [5 Principles of Regeneration](https://kokonut.network/kokonut-framework/framework-components/framework-features/5-principles-of-regeneration.md) and [Why Syntropic Farming](https://kokonut.network/kokonut-framework/why-syntropic-farming.md).

**4. 4. Expand the value model**

Read the [8 Forms of Capital](https://kokonut.network/kokonut-framework/framework-components/framework-features/8-forms-of-capital.md).

**5. 5. Follow the farm lifecycle**

Move through [Phase I](https://kokonut.network/kokonut-framework/development-phases/phase-i.md), Phase II, Phase III, and Phase IV.

**6. 6. Add impact interpretation carefully**

Read the [Positive-impact methodology](https://kokonut.network/kokonut-framework/framework-components/framework-features/methodology-positive-impact.md), [SDGs](https://kokonut.network/kokonut-framework/framework-features/Sustainable-Development-Goals.md), and [Ecological Impact Frameworks](https://kokonut.network/kokonut-framework/framework-add-ons/ecological-impact-frameworks.md).

**7. 7. Connect methodology to evidence and data**

Read [MRV](https://kokonut.network/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification.md), [Kokonut Intelligence](https://kokonut.network/kokonut-intelligence.md), and [Build with Kokonut](https://kokonut.network/build-with-kokonut.md).

***

## Navigate the Framework

> **[Common Data Schema](https://kokonut.network/kokonut-framework/framework-components/common-data-schema.md)**
>
> The current 13-field baseline farm record.

> **[Pillars of Value](https://kokonut.network/kokonut-framework/framework-components/pillars-of-value.md)**
>
> Six questions for value, contribution, risk, and public goods.

> **[5 Principles of Regeneration](https://kokonut.network/kokonut-framework/framework-components/framework-features/5-principles-of-regeneration.md)**
>
> Shared regenerative practice principles.

> **[8 Forms of Capital](https://kokonut.network/kokonut-framework/framework-components/framework-features/8-forms-of-capital.md)**
>
> Natural, Financial, Social, Human, Material, Intellectual, Cultural, and Health capital.

> **[Development Phases](https://kokonut.network/kokonut-framework/development-phases/phase-i.md)**
>
> The four-stage farm-development lifecycle.

> **[Positive-impact Methodology](https://kokonut.network/kokonut-framework/framework-components/framework-features/methodology-positive-impact.md)**
>
> Connect activities and evidence to impact interpretation without skipping the evidence boundary.

> **[Sustainable Development Goals](https://kokonut.network/kokonut-framework/framework-features/Sustainable-Development-Goals.md)**
>
> Primary and secondary SDG mapping with evidence-aware claim levels.

> **[Ecological Impact Frameworks](https://kokonut.network/kokonut-framework/framework-add-ons/ecological-impact-frameworks.md)**
>
> Additional ecological-benefit and risk interpretation tools.

> **[Why Syntropic Farming](https://kokonut.network/kokonut-framework/why-syntropic-farming.md)**
>
> The agricultural logic behind Kokonut's syntropic and regenerative approach.

> **[Impact Calculator](https://kokonut.network/kokonut-framework/impact-calculator.md)**
>
> Scenario planning for finance and impact; model outputs remain forecasts until actual evidence exists.

> **[MRV Methodology](https://kokonut.network/ecosystem-wiki/kokonut-farms/measurement-reporting-and-verification.md)**
>
> The evidence model that sits beside the Framework.

> **[Adelphi](https://kokonut.network/ecosystem-wiki/kokonut-farms/adelphi/summary.md)**
>
> The first live reference implementation.

> **The Framework succeeds when the next farm can start with more shared knowledge and better coordination than the first one—without losing the local judgment that makes a farm real.**


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.