Contribute useful work before you contribute capital.
Kokonut Network is an open collaboration ecosystem around regenerative agriculture. You do not need to become a DAO member, buy a token, or contribute capital to begin. You can start by improving documentation, reviewing a farm record, researching a method, writing code, helping with MRV, strengthening a proposal, contributing agronomic knowledge, supporting a partnership, or solving another clearly defined problem.The best first contribution is small enough to review, useful enough to matter, and documented well enough that someone else can learn from it.
Find a place to contribute
Start with an issue, a documentation gap, a bounded research question, a Guild task, or another contribution that can be reviewed.
Understand the live context first
Adelphi is the first live reference farm. Understand the land, operators, evidence, and current system before proposing changes around it.
Contribution and capital are separate paths. The Moloch DAO coordinates capital and treasury decisions. Guilds and project workflows coordinate useful work. A contributor can begin without capital.
Who this invitation is for
Kokonut needs different kinds of knowledge because regenerative agriculture is not only an agronomy problem, a software problem, or a funding problem.Farmers, agronomists & syntropic practitioners
Improve crop systems, soil practices, water management, planting design, biodiversity work, nursery systems, organic inputs, and field-operating knowledge.
Researchers & MRV contributors
Strengthen measurement methods, remote sensing, soil and water evidence, biodiversity records, impact methodology, data quality, and claim review.
Developers & data builders
Improve farm data tools, APIs, dashboards, analytics, attestations, developer workflows, Kokonut Intelligence, and agent-assisted infrastructure.
Governance & coordination contributors
Improve proposal quality, review processes, contributor workflows, Guild coordination, governance documentation, and decision transparency.
Finance & ReFi contributors
Work on budgets, forecasts, treasury reporting, grant finance, public-goods allocation, scenario analysis, and financial assumptions.
Community, communications & partnerships
Improve onboarding, educational content, community coordination, partner research, documentation, ecosystem updates, and relationship-building.
How contribution works
Kokonut’s contribution model is designed around useful work + evidence + review, not visibility or proximity to the core team.1. Understand the context
Read the relevant documentation, inspect live records when available, and understand whether the system you want to change is live, evolving, developing, or proposed.
2. Choose a bounded contribution
Define one useful outcome: fix a page, review a forecast, validate a record, write a research note, improve a method, build a small tool, or prepare a proposal draft.
3. Open an issue when the change is material
Architecture, methodology, governance, MRV, schemas, APIs, navigation, contract behavior, and other shared primitives should be discussed before implementation.
4. Do the work in a reviewable form
Produce something another person can inspect: a pull request, report, dataset, model, field record, design, analysis, proposal, or documented coordination outcome.
5. Submit evidence and assumptions
Explain what changed, why it matters, what sources support it, what assumptions remain, and what could be affected.
6. Review before recognition
Relevant contributors, Guilds, maintainers, farm operators, or governance participants review the work according to its domain and impact.
7. Build a contribution record
Reviewed work can become part of a contributor’s history: what was done, who did it, what evidence supports it, and which domain it belongs to.
Recognition is not automatic. Completed and reviewed contributions can qualify for Guild Points under the relevant Guild’s rules. Significant network-level recognition can require a Moloch DAO proposal. Guild Points themselves are still a developing coordination system.
Good first contributions
A good first contribution usually does not require governance authority or a large budget.Small, finished, reviewable work is more useful than a large idea nobody can validate.
Where contributions belong
Different work should be reviewed by the people closest to the relevant responsibility.
The point is not bureaucracy.
The point is to avoid having one group approve work outside its expertise.
The six Guild domains
Kokonut uses Guilds as the contribution-oriented coordination layer.
Read the full Kokonut Guilds model →
Capital participation is a different path
Some contributors may also want to participate in Kokonut’s capital governance. That path runs through the Kokonut Moloch DAO, not through ordinary contribution activity. Capital participation can involve:- stablecoin tribute;
- membership proposals;
- $vKKN governance rights;
- treasury voting;
- rage-quit protections;
- proposal sponsorship and review.
- useful work;
- contribution records;
- Guild review;
- Guild Points when awarded under the relevant rules;
- potential DAO-level recognition for significant work.
You can contribute to Kokonut without joining the Moloch DAO. You can also become a DAO member without being qualified to make farm, technical, scientific, or domain-specific decisions outside the scope of capital governance.
Contribution principles
The collaboration model follows the same standards used across the Knowledge Base.Evidence over claims
Material claims should link to records, methods, sources, or clearly stated assumptions.
Actuals are not forecasts
Estimates, scenarios, targets, forecasts, and modeled outcomes must remain distinguishable from recorded results.
Local context matters
A method that works at Adelphi should not automatically be imposed on another farm without understanding its ecology, people, markets, and regulation.
Compatibility matters
Schema, API, MRV, attestation, and shared-method changes should explain migration and backward-compatibility implications.
AI does not remove responsibility
AI-assisted work is welcome, but contributors remain responsible for factual accuracy, evidence, review, and the consequences of public claims.
Open should create capacity
Prefer documentation, standards, tools, and workflows that make future contributors and communities more capable rather than more dependent.
Work that needs extra review
Some contributions can affect live farms, governance, data compatibility, or public claims. Open an issue before implementation when changing:- the Common Data Schema;
- MRV payloads or evidence requirements;
- attestation structures;
- governance rules or proposal processes;
- token or contract behavior;
- public farm-data interpretation;
- impact methodology;
- financial or harvest assumptions used across multiple pages or tools;
- navigation or major information architecture;
- API contracts or shared data models.
- what problem you are solving;
- who or what is affected;
- why the current approach is insufficient;
- whether the change is backward compatible;
- what evidence supports the proposal;
- how it should be reviewed or migrated.
Ecosystem surfaces you can contribute to
The ecosystem is at different stages of maturity, so contribution should match the current state of each surface.Public documentation — Live
Improve guides, architecture, evidence, navigation, examples, and onboarding directly through the public repository.
Adelphi — Live reference farm
Improve farm documentation, evidence quality, agronomic knowledge, MRV, forecasts, public records, and community-facing materials.
Kokonut Framework — Live and evolving
Improve shared farm data, development phases, regenerative methodology, value accounting, and reusable implementation guidance.
Kokonut Intelligence — Active infrastructure
Contribute to data integration, analytics, research, scoring, reporting, synthesis, and decision-support workflows.
AI-agent infrastructure — Developing
Prototype bounded, reviewable agent workflows for data quality, MRV drafts, forecasting support, proposals, and reporting.
Replication — Being tested
Terra Viva is documented in Phase I as the next replication test. Contributions should treat it as planning-stage work, not an already operating farm.
What a strong contribution looks like
Before submitting work, ask:- Is the problem clear?
- Is the scope bounded?
- Did I use the current repository and live records rather than stale assumptions?
- Are facts, estimates, and opinions distinguishable?
- Can another person inspect my evidence?
- Did I preserve local context?
- Did I avoid overstating the maturity of developing infrastructure?
- If I changed a shared primitive, did I explain compatibility?
- Did I identify who should review the work?
- Does the contribution leave the ecosystem easier to understand, operate, verify, or improve?
Start here
Read Kokonut 101
Start with the Executive Summary so you understand the problem, solution, vision, and manifesto before changing the system.
Inspect the live farm
Review Adelphi and the Kokonut Hub when your contribution touches farm claims or operations.
Choose one contribution
Pick a bounded task that matches your skills. If it is material or cross-system, open an issue before building.
Join the community conversation
Join the Kokonut Discord, introduce yourself, and share the problem or contribution you want to work on.
Submit something reviewable
Open a pull request, publish a research note, provide a dataset, submit a proposal draft, or share another artifact with enough evidence for review.
Use the formal path when needed
Larger changes, funding requests, Framework upgrades, and DAO-level recognition should move through the relevant Guild or governance process.
Contribute to the public repository
Open an issue, improve the docs, review current work, or propose a focused change.
Join the community
Meet contributors and find where your skills can be useful.
Understand the Guilds
Learn how contribution records, Guild Points, domain coordination, and DAO-level recognition are designed to work.
Book a walkthrough
Partners, farms, funders, institutions, and serious collaborators can discuss a specific opportunity with the team.
Open collaboration means you do not need permission to start being useful. It does not mean every contribution is automatically accepted, funded, rewarded, or granted governance rights. Useful work becomes part of the ecosystem through evidence, review, and the coordination process appropriate to its impact.