DAO Proposal Templates

# [PROPOSAL NAME]
# e.g. "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 / Active Member]
 
## C. Proposal Team
- **Issuing Guild:** [Technology / Impact / Communications / Governance / Finance / Community & Partnerships]
- **Guild Steward (sponsor):** [Name / alias + wallet]
- **Intended contributor(s):** [Name / alias / "open for applications"]
 
## D. Draft Start Date
[YYYY-MM-DD]
 
---
 
## E. Proposal Description
 
### Bounty summary
| Field              | Value                                                   |
|--------------------|---------------------------------------------------------|
| Bounty Type        | [feature / research / content / audit / design / ops]   |
| Skill required     | [e.g. Solidity, Python, technical writing, agronomy]    |
| Estimated effort   | [e.g. ~20 hours over 2 weeks]                           |
| Application open   | [Yes — link to bounty / No — pre-assigned]   |
| Assigned to        | [Contributor name + wallet, or "TBD via application"]   |
 
### Background and context
[2–3 paragraphs explaining why this work needs to happen now. What problem does it
solve? What does the ecosystem currently lack that this bounty produces? Reference
specific pages, contracts, or processes that this work improves.]
 
### Deliverable specification
 
This bounty is complete when all of the following are submitted and accepted:
 
| # | Deliverable                  | Format           | Acceptance criteria                                       |
|---|------------------------------|------------------|-----------------------------------------------------------|
| 1 | [Primary deliverable]        | [code/doc/report]| [Specific, testable criteria — not "looks good"]          |
| 2 | [Secondary deliverable]      | [format]         | [Criteria]                                                |
| 3 | [Documentation / write-up]   | MDX / Markdown   | Merged to relevant repo via reviewed PR                   |
 
### Technical requirements
[If applicable: language, framework, chain, API version, test coverage requirement,
PR review requirement, specific contracts or endpoints the work must integrate with.
If not applicable, write "No specific technical requirements."]
 
### Out of scope
[Explicitly state what this bounty does NOT cover, to prevent scope creep and
disputes at review time. e.g. "This bounty covers the proof-of-concept only.
Production deployment is a separate future bounty."]
 
---
 
## F. Mission Alignment
[Connect this bounty to a specific ecosystem gap or roadmap item. Reference the
relevant Guild's domain. e.g. "This bounty advances the Technology Guild's
responsibility to maintain the Kokonut Agentic Marketplace by building the first
working MRV agent — a core piece of the automation layer that reduces manual farm
reporting overhead."]
 
---
 
## G. Brand Usage
[Describe whether the deliverable will be published under the Kokonut brand:
e.g. "The agent will be listed on the Marketplace under the Kokonut namespace at
mrv-poc.kokonutnetwork.eth" or "This research report will be published on the Kokonut
docs site and attributed to the Impact Guild."]
 
---
 
## H. Financial Implications
 
### Total bounty amount
**$[AMOUNT] USD** (to be disbursed in stablecoins from the Kokonut DAO Treasury)
 
### Payment schedule
 
| Milestone                          | Amount (USD) | Condition for payment                                |
|------------------------------------|--------------|------------------------------------------------------|
| Kickoff confirmation               | $[N]         | Contributor confirms acceptance + posts work plan    |
| Mid-point check-in                 | $[N]         | Draft / WIP submitted for review       |
| Final delivery                     | $[N]         | All deliverables accepted by Guild Steward           |
| **Total**                          | **$[TOTAL]** |                                                      |
 
Payments are released by Guild Steward confirmation to the contributor's wallet
following each milestone. Full payment is contingent on all deliverables meeting
their acceptance criteria.
 
### Dispute process
If the contributor and Guild Steward cannot agree on whether a deliverable meets
its acceptance criteria, the Governance Guild serves as the first escalation point.
Unresolved disputes proceed to a full DAO vote.
 
---
 
## I. Success Metrics
 
### During execution
- [ ] Contributor submits work-plan within 3 days of kickoff payment
- [ ] Mid-point check-in deliverable submitted on schedule
- [ ] Final delivery submitted before deadline: [YYYY-MM-DD]
- [ ] Deliverables pass all acceptance criteria on first or second review
 
### After delivery (30-day evaluation)
| Metric                              | Target                                              |
|-------------------------------------|-----------------------------------------------------|
| [Primary deliverable utility]       | [e.g. MRV agent handles 3 consecutive test tasks]   |
| [Adoption or usage metric]          | [e.g. Merged and linked from main docs within 30d]  |
| [Quality / reliability metric]      | [e.g. Zero critical bugs filed within 30 days]      |
 
---
 
## J. Next Steps
 
| Action                                          | Owner                   | Deadline        |
|-------------------------------------------------|-------------------------|-----------------|
| Drafting window open (5 days minimum)           | [Author]                | [YYYY-MM-DD]    |
| Post bounty to applications board               | [Guild Steward]         | [YYYY-MM-DD]    |
| Select contributor (if open application)        | [Guild Steward]         | [YYYY-MM-DD]    |
| Sponsor to DAOHaus if >= $500                   | [Proposal-auth person]  | [YYYY-MM-DD]    |
| Kickoff payment disbursed                       | [Guild Steward]         | On vote passing |
| Work period                                     | [Contributor]           | [YYYY-MM-DD]    |
| Final review and acceptance                     | [Guild Steward]         | [YYYY-MM-DD]    |
| Final payment disbursed                         | [Guild Steward]         | On acceptance   |
| Guild Points awarded to contributor             | [Guild Steward]         | Within 7 days   |

# [PROPOSAL NAME]
# e.g. "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: [Technology / Impact / Governance / other]
 
## C. Proposal Team
List everyone involved in designing, reviewing, and implementing this change:
- [Name] — [Role: e.g. Schema Author, Farm Operator Impact Reviewer, Documentation]
- [Name] — [Role]
- **Reviewing Guild:** [Guild responsible for technical review before DAO vote]
 
## 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] |
| Change type               | [additive / modification / deprecation / removal]                           |
| Backward compatible       | [Yes / No / Partial — see migration plan]                                   |
| Farms currently affected  | [List farm_ids or "All registered farms"]                                   |
| Agents currently affected | [List agent names or "None" or "All MRV agents"]                            |
| API version impact        | [None / Minor (new optional field) / Major (breaking change)]               |
 
### Current state
[Describe exactly what the Framework says today. Quote the relevant field, rule,
or section. If this is a schema change, paste the current field definition.
If this is a process change, quote the current process language.]
 
~~~
// Current field / rule / spec — paste verbatim
~~~
 
### Proposed change
[Describe exactly what will change. If this is a schema change, show the before
and after side by side. If this is a process change, show the old and new language.
Be precise — ambiguous Framework changes cause disputes downstream.]
 
~~~
// Before
"field_name": "type": "string", "required": true
 
// After
"field_name": "type": "string", "required": true
"new_field":  "type": "number", "required": false, "description": "..."
~~~
 
### Rationale
[Why is this change needed? Reference a specific farm operation, data quality
issue, agent integration gap, or governance problem that the current Framework
does not handle well. Concrete examples are required — abstract improvement
rationale does not pass the drafting review.]
 
### Backward compatibility impact
[Assess impact on:
- Farms currently submitting data against the existing schema
- The Farm Registry API (which endpoints are affected)
- Deployed agents that consume or produce Framework-defined data
- Third-party tools using the Framework (Silvi, Atlantis App, QGIS pipelines)
- Existing EAS attestation schemas on Gnosis Chain or Base
 
If the change is additive with all new fields optional: state this clearly.
If any existing field is renamed, retyped, or removed: a migration plan is
required in the next section.]
 
### 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 old and new formats          | Technology Guild | [N weeks]        |
| Farm migration     | Each farm updates their data submission       | Farm operators   | By [YYYY-MM-DD]  |
| Agent migration    | Each agent updates capability manifest        | Agent operators  | By [YYYY-MM-DD]  |
| Cutover            | Old format no longer accepted                 | Technology Guild | [YYYY-MM-DD]     |
 
Farms and agents that have not migrated by the cutover date will receive
API validation errors. The Technology Guild is responsible for proactive
outreach before cutover.
 
---
 
## F. Mission Alignment
[Explain why this change makes the Kokonut Framework more modular, more accurate,
more composable, or more scalable. Connect it to a specific Framework goal:
making ecology measurable and financeable, enabling repeatable farm implementations,
or improving governance integrity.]
 
---
 
## G. Brand Usage
[Describe how this change affects Kokonut's public documentation, API reference,
or technical communications. e.g. "The updated schema will be reflected in the
Common Data Schema page, the OpenAPI spec, and the Build with Kokonut developer
guide within 7 days of proposal passing."]
 
---
 
## H. Financial Implications
 
### Treasury disbursement (if any)
**$[AMOUNT] USD** — or — **No treasury disbursement required.**
 
If funding is needed (e.g. for a bounty to implement the change):
 
| Work item                          | Amount (USD) | Assigned to                |
|------------------------------------|--------------|----------------------------|
| Schema implementation              | $[N]         | [Name / Technology Guild]  |
| API update and testing             | $[N]         | [Name / Technology Guild]  |
| Documentation update               | $[N]         | [Name / Comms Guild]       |
| Farm operator migration support    | $[N]         | [Name / Impact Guild]      |
| **Total**                          | **$[TOTAL]** |                            |
 
### Ongoing cost / savings
[Describe any ongoing effect: e.g. "The new field reduces manual data cleaning
effort by the Impact Guild, estimated at ~3 hours/month across all farms."]
 
---
 
## I. Success Metrics
 
### During implementation
- [ ] API update deployed to staging and tested against all four Farm Registry endpoints
- [ ] At least one farm operator has submitted a test record against the new schema
- [ ] At least one MRV agent has updated its capability manifest to the new spec
- [ ] Documentation PRs merged to Kokonut-Public-Site and kokonut-framework
- [ ] No open critical bugs 5 days after staging deployment
 
### Post-implementation (30 days)
| Metric                                   | Target                                        |
|------------------------------------------|-----------------------------------------------|
| API error rate for affected endpoints    | <= baseline error rate (no regression)        |
| Farms migrated (if migration required)   | 100% of registered farms                      |
| Agents updated (if manifest change)      | 100% of affected agents                       |
| Data quality improvement                 | [Specific measurable improvement]             |
 
---
 
## J. Next Steps
 
| Action                                                    | Owner                  | Deadline        |
|-----------------------------------------------------------|------------------------|-----------------|
| Drafting window open — notify all vote-authorized members | [Author]               | [YYYY-MM-DD]    |
| Technology Guild technical review                         | [Guild Steward]        | [YYYY-MM-DD]    |
| Farm operators notified of proposed change                | [Author / Comms Guild] | [YYYY-MM-DD]    |
| Feedback incorporated                                     | [Author]               | [YYYY-MM-DD]    |
| Sponsor to DAOHaus active voting stage                    | [Proposal-auth person] | [YYYY-MM-DD]    |
| Voting window (5 days)                                    | DAO Members            | [YYYY-MM-DD]    |
| If passed: deprecation notice issued                      | [Author]               | Within 48 hours |
| If passed: API staging deployment                         | Technology Guild       | Within 7 days   |
| If passed: documentation PRs merged                       | Comms Guild            | Within 7 days   |
| If passed: cutover (if migration required)                | Technology Guild       | [YYYY-MM-DD]    |

# [PROPOSAL NAME]
# e.g. "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 (if any): [e.g. "No prior relationship" / "Community member of both"]
 
## C. Proposal Team
- **Lead negotiator:** [Name + wallet — the person who will manage this relationship]
- **Community & Partnerships Guild Steward:** [Name + wallet]
- **Legal reviewer (if applicable):** [Name or "None — no legal entity involved"]
- **Technical contact (if integration required):** [Name + wallet]
 
## D. Draft Start Date
[YYYY-MM-DD]
 
---
 
## E. Proposal Description
 
### Partner overview
| Field                | Value                                                                              |
|----------------------|------------------------------------------------------------------------------------|
| Partner name         | [Full legal or DAO name]                                                           |
| Partner type         | [protocol / institution / farm / ReFi ecosystem / public goods funder / coop]     |
| Partner website      | [URL]                                                                              |
| Partner wallet / ENS | [0x... or name.eth — if applicable]                                                |
| Partner chain(s)     | [Chains the partner operates on, if relevant]                                      |
| Partnership duration | [e.g. 12 months / indefinite / single-event]                                       |
| Renewal mechanism    | [e.g. Automatic unless either party posts a termination proposal / Annual vote]    |
 
### What this partnership is
[2–4 paragraph description of the relationship: who the partner is, what they
do, and what this specific partnership entails. Explain how the two organizations
met, what problem or opportunity this partnership addresses, and what
the working relationship will look like day-to-day.]
 
### Value exchange
 
**What Kokonut Network provides:**
 
| Contribution                         | Description                                                      |
|--------------------------------------|------------------------------------------------------------------|
| [e.g. Ecosystem data access]         | [e.g. Read access to Farm Registry API for partner's indexer]    |
| [e.g. Co-branding on farm materials] | [e.g. Partner logo on Adelphi educational materials]             |
| [e.g. Treasury allocation]           | [$N USD from DAO treasury — requires milestone in Section H]     |
| [e.g. DAO proposal co-sponsorship]   | [Kokonut will co-sponsor partner's onboarding proposal]          |
 
**What Kokonut Network receives:**
 
| Contribution                         | Description                                                      |
|--------------------------------------|------------------------------------------------------------------|
| [e.g. Grant funding]                 | [$N USD toward [specific farm or initiative]]                    |
| [e.g. Technical integration]         | [e.g. Partner's oracle integrated into MRV pipeline]             |
| [e.g. Community reach]               | [e.g. Exposure to partner's N-member community]                  |
| [e.g. Research output]               | [e.g. Co-authored impact report published under both brands]     |
 
### Integration requirements (if technical)
[If this partnership requires any technical work — API access, smart contract
integration, data pipeline, agent registration — describe the scope here.
Reference the relevant contracts or endpoints. If no technical integration
is required, write "No technical integration required."]
 
### Revocation conditions
This partnership is terminated automatically if any of the following occur:
- [ ] [e.g. Partner organization dissolves or ceases operations]
- [ ] [e.g. Partner publicly acts against Kokonut's core values or manifesto]
- [ ] [e.g. Partner fails to deliver their stated contributions within [N] days of agreed deadline]
- [ ] A DAO vote passes a termination proposal at any time
 
Either party may initiate termination by posting a notice to Charmverse.
Termination takes effect after a [14-day / 30-day] notice period unless
the DAO votes to extend the relationship.
 
---
 
## F. Mission Alignment
[Explain how this partnership advances Kokonut's mission: reducing obstacles
to agricultural development, democratizing investment in real-world projects,
and building a regenerative community-owned network.
 
Specifically address:
- How this partner shares or complements Kokonut's values
- Whether this partnership creates precedent for future similar partnerships
- Any reputational considerations — does the partner's public positioning
  align with Kokonut's community-first ethos?]
 
---
 
## G. Brand Usage
 
### Kokonut use of partner brand
[Describe exactly where and how Kokonut will use the partner's name, logo, or
assets: e.g. "Partner logo will appear on the Adelphi farm page, in the
open-collaboration-invitation, and in co-authored grant applications.
All usage is subject to partner's brand guidelines."]
 
### Partner use of Kokonut brand
[Describe exactly where and how the partner may use Kokonut's name, logo,
or assets: e.g. "Partner may reference this partnership in their ecosystem
announcements and grant applications. Partner may not represent themselves
as a DAO member or governance participant unless separately onboarded."]
 
---
 
## H. Financial Implications
 
### Treasury disbursement (if any)
**$[AMOUNT] USD** — or — **No treasury disbursement required.**
 
If Kokonut is providing treasury funds to the partner or to a shared initiative:
 
| Line item                           | Amount (USD) | Condition for release                              |
|-------------------------------------|--------------|----------------------------------------------------|
| [e.g. Joint farm funding tranche]   | $[N]         | [e.g. Partner delivers matching funds first]       |
| [e.g. Integration development]      | $[N]         | [e.g. Technical milestone verified by Tech Guild]  |
| [e.g. Co-branded event costs]       | $[N]         | [e.g. Event date confirmed + budget approved]      |
| **Total**                           | **$[TOTAL]** |                                                    |
 
### Expected financial return to Kokonut
[Describe any monetary or equivalent value expected to flow to the DAO or
to farms as a result of this partnership: grant funding, revenue share,
cost reduction, in-kind services with estimated USD value.]
 
### Jurisdiction note
[If either party is a legal entity, note the jurisdiction and whether any
formal legal agreement (MOU, contract) will accompany this proposal.
e.g. "This proposal creates a DAO-to-DAO relationship with no formal legal
agreement. No legal entity on either side." or "Partner is a registered
nonprofit in [country]. A Memorandum of Understanding will be signed by
the Kokonut Network Core Team alongside this DAO vote."]
 
---
 
## I. Success Metrics
 
### During the partnership
- [ ] Value exchange items delivered on the schedule agreed in Section E
- [ ] No brand usage disputes or public misrepresentations by either party
- [ ] Technical integration (if applicable) tested and live within [N] days
- [ ] Quarterly check-in between lead negotiator and partner counterpart
 
### End-of-term evaluation (at renewal or termination)
| Metric                                      | Target / Minimum                                             |
|---------------------------------------------|--------------------------------------------------------------|
| Kokonut contributions delivered             | 100% of commitments in Section E                             |
| Partner contributions delivered             | 100% of commitments in Section E                             |
| [Partnership-specific outcome metric]       | [e.g. >= $N in co-funding secured]                           |
| [Community sentiment]                       | [e.g. No unresolved objections filed to Charmverse]          |
| Renewal recommendation                      | Lead negotiator recommendation published before term end     |
 
---
 
## J. Next Steps
 
| Action                                                       | Owner                  | Deadline        |
|--------------------------------------------------------------|------------------------|-----------------|
| Drafting window open — notify all vote-authorized members    | [Author]               | [YYYY-MM-DD]    |
| Partner reviews and acknowledges draft                       | [Lead negotiator]      | [YYYY-MM-DD]    |
| Community & Partnerships Guild Steward sign-off              | [Guild Steward]        | [YYYY-MM-DD]    |
| Legal review (if applicable)                                 | [Legal reviewer]       | [YYYY-MM-DD]    |
| Feedback incorporated and draft finalized                    | [Author]               | [YYYY-MM-DD]    |
| Sponsor to DAOHaus active voting stage                       | [Proposal-auth person] | [YYYY-MM-DD]    |
| Voting window (5 days)                                       | DAO Members            | [YYYY-MM-DD]    |
| If passed: formal agreement signed (if applicable)           | Core Team + Partner    | Within 14 days  |
| If passed: technical integration kickoff (if applicable)     | Technology Guild       | Within 14 days  |
| If passed: public announcement                               | Communications Guild   | Within 7 days   |
| First quarterly check-in scheduled                          | Lead negotiator        | Within 30 days  |