> ## Documentation Index > Fetch the complete documentation index at: https://kokonut.network/llms.txt > Use this file to discover all available pages before exploring further. # Kokonut Syntropic Agent > Meet Kokonut Network's first AI Core Team agent: a planned multichain orchestrator for regenerative agriculture, evidence-aware coordination, agent commerce, and real-world economic flywheels. # One agent. Many chains. Real-world regeneration. **Kokonut Syntropic Agent** is Kokonut Network's first named AI Core Team agent and the proposed intelligent orchestration interface for the Kokonut ecosystem. Its mission is to **develop and power real-world economic flywheels through syntropic farming and the Kokonut Framework**—connecting field work, community coordination, operational intelligence, responsible financing, and blockchain infrastructure without making farmers manage all that complexity themselves. The Syntropic Agent is designed to work across networks through **Kokonut Protocol's NEAR-based interoperability hub**, while keeping capabilities and economic arrangements native to the networks where they are useful. > **[Explore Kokonut Protocol](/kokonut-protocol.md)** > > Understand the planned NEAR Web3 control plane that governs cross-chain execution. > **[Explore AI agent architecture](/kokonut-x-ai-agents.md)** > > See Kokonut's capability, safety, evidence, and approval boundaries. > **[Inspect Adelphi's live records](https://hub.kokonut.network/projects/41)** > > Ground the mission in a real farm and its existing public evidence. > **[Build with Kokonut](/build-with-kokonut.md)** > > Find repositories, data contracts, contribution paths, and integration guidelines. > [!WARNING] > > **Product maturity:** this page describes an approved product direction and engineering roadmap, not a claim that the Syntropic Agent, its tokens, NEAR Protocol Hub, ACP services, or token distributions are already deployed. Refer to the relevant repositories and official on-chain records for actual releases, contract addresses, and transaction history. *** ## Why this agent exists A productive regenerative farm needs more than an agricultural recommendation. It requires planning, evidence, people, capital, logistics, monitoring, and timely decisions. Each responsibility is handled by different local actors and technical systems. The Syntropic Agent aims to make those systems easier to coordinate by helping teams: * turn field records into review-ready operational recommendations; * discover gaps in agronomic, ecological, and financial evidence; * prepare scoped plans and budgets for productive assets; * track milestones and surface delays or inconsistencies; * package approved information for partners, public reporting, and agent-to-agent services; * prepare cross-chain actions for explicit human or DAO authorization. **The agent assists with coordination. Farm operators, reviewers, legal entities, and governance bodies retain their respective authority.** ## From farm work to productive flywheels The agent's first two proposed real-world work areas are **Kokonut Adelphi** and **Kokonut Terra Viva**, both in the Dominican Republic. Wasalo Tech, SRL, doing business as Kokonut Onchain Network, is the intended agent operating entity and holds lease rights to both projects. | Real-world area | Proposed agent contribution | What counts as evidence | | - | - | - | | Farm readiness | Analyze infrastructure gaps, crop plans, purchasing needs, and dependencies | Operator-confirmed inventories, plans, quotations, and work orders | | Syntropic production | Help coordinate succession planning, nursery work, input cycles, and harvest scheduling | Field observations, planting logs, harvests, and agronomist review | | Financial resilience | Prepare scenarios, milestone budgets, and variance analyses | Reconciled receipts, invoices, approved budgets, and actual operating records | | Ecological outcomes | Identify measurement gaps and assemble MRV-ready evidence | Governed evidence and independent review where required | | Replication | Turn lessons from one site into candidate plans for another | Comparative results with local ecological and community validation | | Agent commerce | Deliver bounded research, readiness, or evidence-preparation services | Completed customer jobs and accepted, appropriately described deliverables | > **[Adelphi — current reference farm](/ecosystem-wiki/kokonut-farms/adelphi/summary.md)** > > Adelphi is a documented live syntropic farm. The agent's proposed contribution is to improve coordination around that real-world baseline, not to take credit for infrastructure or outcomes created before the agent. > [!NOTE] > > Terra Viva is a planned development workstream. Do not treat proposed investments, forecasts, or development milestones as completed construction or realized revenue. *** ## How the system fits together The agent is an **orchestrator**, not another canonical database, a sovereign treasury, or a replacement for Kokonut Protocol. ```mermaid theme={null} flowchart TD PEOPLE["Farm operators · Core Team · Community"] AGENT["Syntropic Agent — Hermes runtime"] KI["Kokonut Intelligence — governed data"] PROTOCOL["Kokonut Protocol — policy and execution"] NEAR["NEAR Hub — Chain Signatures"] BASE["Base — Virtuals / agent commerce"] GNOSIS["Gnosis — existing DAO and Safe"] CELO["Celo — EAS provenance"] FUTURE["Additional approved chains"] FARMS["Adelphi · Terra Viva · future projects"] PEOPLE --> AGENT FARMS --> KI AGENT <--> KI AGENT -->|"proposals, not self-approval"| PROTOCOL PEOPLE -->|"independent authorization"| PROTOCOL KI <--> PROTOCOL PROTOCOL --> NEAR NEAR --> BASE NEAR --> GNOSIS NEAR --> CELO NEAR --> FUTURE KI --> FARMS ``` | Layer | Responsibility | | - | - | | **Hermes / Syntropic Agent** | Reason, research, plan, summarize, coordinate, draft, and monitor approved scopes | | **Kokonut Intelligence** | Canonical operational records, finance, evidence, identity context, review, and audit | | **Kokonut Protocol** | Chain-neutral requests, execution policy, approved deployments, and reconciliation | | **NEAR Web3 Hub** | Governed signing orchestration and NEAR-native integrations | | **Destination chains** | Local rights, smart contracts, token settlement, attestations, and DAO state | | **Local people and organizations** | Physical operations, financial approvals, legal duties, and evidence verification | **A Chain Signature is not a completed transaction.** The Protocol must separately assemble, simulate, broadcast, confirm, verify, and reconcile each approved destination-chain action. [Read about Kokonut Intelligence](/kokonut-intelligence.md) and [Kokonut Protocol](/kokonut-protocol.md) for the governing boundaries. *** ## Proposed capabilities > **Field operations intelligence** > > Summaries of crops, soil, water, nursery work, biofactory activities, harvests, and operator follow-ups. > **MRV preparation** > > Identify evidence gaps, prepare draft reporting packages, and trace source records to proposed claims. > **Capital coordination** > > Draft milestones, compare budgets with actuals, and prepare governance-ready funding requests. > **Multichain orchestration** > > Prepare chain-neutral execution requests through the NEAR-based Protocol Hub after independent authorization. > **Agentic services** > > Package scoped intelligence work for humans, organizations, and other agents through approved commerce integrations. > **Learning and replication** > > Compare approved project outcomes, improve reusable operating knowledge, and help design the next project. These capabilities are the **intended product surface**. Availability depends on the actual implementation, tested permissions, and release status. ### Human and DAO authority is non-negotiable | Agent may prepare | Agent may not independently authorize | | - | - | | Evidence-gap reports and draft summaries | Verification, publication, or certification | | Farm plans and budget scenarios | Payments, purchases, or treasury transfers | | Governance proposals | Governance outcomes or DAO membership changes | | Unsigned transactions and simulations | Financial signing, contract upgrades, or protected on-chain submissions | | Public-status summaries from approved records | Disclosure of private farm, stakeholder, or financial information | The current Kokonut Intelligence agent safety rules deny high-risk actions such as verification, publication, attestation, on-chain submission, and financial writes. An approval-required flag is not itself an execution authorization. *** ## One identity, chain-specific participation A single Syntropic Agent can have different ecosystem presences **without issuing a token on every chain**. | Network | Intended relationship | Token / economics | Maturity | | - | - | - | - | | **Base** | Virtuals agent identity, capital formation, commerce, and ACP | Separate Virtuals-native token and economics | Planned; launch and commercial PRD prepared | | **NEAR** | Chain-agnostic orchestration hub, protocol interactions, NEAR-native participation | Distinct NEAR token using Nearly's launch mechanics | Planned; design selected | | **Gnosis** | Existing Kokonut DAO, Baal governance, and Safe state | Existing DAO rights remain separate | Existing infrastructure; agent permissions constrained | | **Celo** | Existing EAS-backed attestation and provenance workflows | No agent token required | Existing proof infrastructure | | **Additional chains** | Opt-in Protocol adapters and local services | Token only if justified and separately approved | Future | **A Base token is not a wrapped NEAR token.** They are separate instruments and do not automatically entitle their holders to the other token's revenues, treasury, governance, farm assets, lease rights, or Kokonut DAO Shares/Loot. ### Planned NEAR token economics The selected *proposed launch configuration* uses [Nearly](https://nearly.trade/docs) for automated token-tax handling, with Rhea as the underlying trading-liquidity infrastructure. * **3% buy tax and 3% sell tax** under the selected launch configuration. * **80% mission development, 10% holder rewards, and 10% direct token burns**, calculated **only over Nearly's creator-controlled allocation of the tax**, not over all gross trade fees. * Under the reviewed schedule, the creator-controlled allocation was **70% of collected tax**. That implies **56% of gross collected tax to mission development, 7% to holder rewards, and 7% to burns**; the remainder is reserved for the platform/referral allocations. * Rhea pool creator fees are **separate from the 3% token tax**. The intended policy is to direct actual creator pool-fee receipts to mission development, not silently include them in the 80/10/10 distribution. * No custom Kokonut holder-distribution vault is planned. Native launchpad mechanics handle rewards and burns, subject to contract-level verification. > [!WARNING] > > **Not live token terms or financial advice.** Launchpad configuration, supported recipients, automated reward/burn behavior, contracts, liquidity, fees, legal classification, and public disclosures must be verified immediately before launch. The intended mission operator still has legal, tax, governance, custody, and accounting responsibilities for funds it receives. Neither trading volume nor token market capitalization is realized farm income. ### Planned Base economy The Base implementation is designed around the [Virtuals ecosystem](https://whitepaper.virtuals.io/) and its agent commerce and capital-formation primitives. Its proposed 60 Days Experiment and Automated Capital Formation strategy is **different** from the NEAR token-tax arrangement. Capital releases, vesting, token-holder rights, and legal requirements follow that separate program's terms; no proceeds are assumed until actually received and available. *** ## What success looks like The goal is not simply token issuance or the number of blockchains integrated. It is demonstrable value creation. | Measure | Evidence-aware success criterion | | - | - | | Utility | Repeated, accepted work by the Core Team, farm operators, and independent customers | | Operational improvement | Completed, operator-approved farm milestones with attributable records | | Economics | Reconciled agent-service receipts and mission expenditures; trading receipts reported separately | | Ecological outcomes | Evidence-linked and appropriately reviewed soil, biodiversity, production, or resource claims | | Interoperability | Independently approved, finalized, and reconciled Protocol operations across supported networks | | Safety | No unauthorized financial execution, privacy breach, or self-verification | | Community | Meaningful contributions, review participation, and transparent decision-making | ### Public activity and proof A future activity surface can display approved activity from Kokonut Intelligence: completed agent work, evidence-ready farm milestones, reconciled cross-chain actions, and mission-treasury reporting. **Current public reference:** [Adelphi Data Hub](https://hub.kokonut.network/projects/41). Until a reviewed public endpoint is available, this page will not display invented live counters or unverified financial figures. *** ## Milestones and maturity | Milestone | Intended deliverable | Status | | - | - | - | | Strategic design | Virtuals/Base and NEAR orchestrator PRDs | Specification prepared | | Canonical integrations | Scoped Hermes skills and Kokonut Intelligence tasks | Planned / integration-dependent | | NEAR identity and policy | Approved accounts, capability restrictions, and Hub interfaces | Planned | | First cross-chain demonstration | Simulate → authorize → sign → broadcast → verify → reconcile | Planned | | NEAR launch configuration | Nearly tax, recipient, rewards, and burn tests plus legal review | Planned | | Agent commerce | First paid, accepted, repeatable service | Planned | | Real-world operating proof | Approved farm milestones with verified actuals | Planned | | Community governance | Limited and explicit participatory rights where legally appropriate | Future | A roadmap is a plan, not evidence of shipment. Verify live deployments from owning repositories and on-chain records. *** ## Build, contribute, and integrate The practical builder entry points are: | Resource | Use it for | | - | - | | [Build with Kokonut](/build-with-kokonut.md) | Contribution rules, data contracts, and repo orientation | | [Kokonut Intelligence repository](https://github.com/wasalo/Kokonut-Intelligence) | Governed data, existing agent tasks, safety controls, and APIs | | [Kokonut Protocol repository](https://github.com/wasalo/Kokonut-Protocol) | NEAR Hub contracts and chain adapter implementation when published | | [Kokonut × AI Agents](/kokonut-x-ai-agents.md) | Identity, permissions, provenance, and human-review rules | | [Kokonut Framework](/kokonut-framework/Introduction.md) | Agricultural methodology and impact interpretation | | [NEAR Chain Abstraction](https://docs.near.org/chain-abstraction/what-is) | Underlying cross-chain signing concepts | | [Nearly launch documentation](https://nearly.trade/docs) | Planned NEAR token launch configuration | | [Virtuals documentation](https://whitepaper.virtuals.io/) | Planned Base capital formation and agent economy | For integrations, start with an allowlisted **read or draft-only capability**, an explicit data policy, test fixtures, and a human-review path. Do not build against a presumed live API, contract address, token ticker, or signer permission that has not been published. > **[Suggest a contribution](https://github.com/wasalo/Kokonut-Public-Site)** > > Improve public documentation, diagrams, or evidence-aware developer guidance. > **[Join the community](https://link.kokonut.network/discord)** > > Coordinate with contributors and follow Kokonut ecosystem progress. *** ## Frequently asked questions > **Is the Syntropic Agent already autonomous?** > > No unrestricted autonomy is intended. It may help prepare and coordinate bounded actions. Protected financial, governance, publication, and evidence decisions require independent authority. > **Does every new chain get an agent token?** > > No. A new chain presence is an adapter and service opportunity first. A chain-native token is optional and must have sufficient utility, economic activity, security, liquidity, and legal justification. > **Do token holders own Kokonut farmland or DAO treasury assets?** > > No automatic ownership or redemption right arises from either planned agent token. Local legal arrangements, DAO membership, and project-specific economic rights are separate. > **Does on-chain data prove a farm impact claim?** > > No. On-chain receipts and attestations can help prove provenance and execution; ecological and operational claims still require appropriate underlying evidence and review. > **Why start with syntropic farming?** > > Syntropic practice connects agricultural design, succession, biodiversity, biomass, water, labor, and production over time. It is a useful real-world laboratory for coordination, provided the outcomes are measured rather than assumed. > [!NOTE] > > **Documentation status — October 2026:** this page is a public product and architecture overview. It is not a token offering, contract audit, income forecast, or substitute for signed project agreements. Confirm deployment, token terms, access permissions, and financial claims at the authoritative source before relying on them. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.