Skip to main content

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:

Technology Solutions Used

LayerTechnologyStatus
DAO governance & treasuryMoloch DAO (Baal framework) on Gnosis Chain; $vKKN (non-transferable governance shares) + Loot (transferable economic rights); Gnosis Safe multisig treasuryLive
Data standardizationCommon Data Schema — a 13-field shared record structure so every farm reports data the same wayLive
MRV / field verificationSoil probes, satellite vegetation indices (NDVI/NDRE/MSAVI via Landsat 8/Sentinel), GPS-tagged tree tracking, mobile field logging, IPFS/Filecoin for immutable evidence storageLive
AttestationEthereum Attestation Service (EAS) deployed on Celo for farm-data attestations, kept separate from Gnosis Chain governanceLive
Intelligence/analyticsKokonut Intelligence — PostgreSQL/PostGIS (spatial), ClickHouse (time-series analytics), Directus (data management), Python-based scoring agentsLive, open-source
Agent accessMulti-agent AI ecosystem with MCP-based access to farm data for scoring, forecasting, and decision supportLive/developing, open-source
Agentic commerce (roadmap)Agentic Marketplace, using ERC-8004 agent identity/reputation and x402 micropaymentsIn development

MRV pipeline, visually:

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

  • DAO members ($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 (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.