Proposal Schema

Overview

The Proposal Schema defines the structure for creating, managing, and evaluating proposals within the Matou DAO ecosystem. It ensures that all proposals are aligned with the community's goals and governance processes.

Schema Structure

Core Entities

{
  "proposal": {
    "metadata": "ProposalMetadata",
    "content": "ProposalContent",
    "status": "ProposalStatus",
    "relationships": "ProposalRelationships",
    "evaluation": "ProposalEvaluation"
  }
}

Entity Relationships

graph TD
    A[Proposal] --> B[Proposal Review]
    B --> C[Proposal Evaluation]
    C --> D[Decision Making]
    
    E[Contributor] --> A
    F[Governance Steward] --> A
    
    A --> G[Proposal Feedback]
    G --> H[Feedback & Rating]
    H --> C

Data Fields

1. ProposalMetadata

Field	Type	Required	Description	Example
id	UUID	Yes	Unique proposal identifier	prop_2025_001
created_at	ISO 8601	Yes	Creation timestamp	2025-01-15T10:30:00Z
updated_at	ISO 8601	Yes	Last update timestamp	2025-01-15T14:45:00Z
version	String	Yes	Schema version	0.1
title	String	Yes	Proposal title	"Develop New Matou DAO Website"
type	Array[Enum]	Yes	Proposal type classification	["technical", "community", "governance", "operations"]
priority	Enum	Yes	Priority level	low, medium, high, critical
estimated_budget	String	Yes	Estimated budget	"15,000 UTIL"
timeline	String	Yes	Project timeline	"6 weeks development + 2 weeks testing"

2. ProposalContent

Field	Type	Required	Description	Example
description	Text	Yes	Detailed description	"Create a modern, accessible website..."
problem_statement	Text	Yes	Problem being addressed	"Current website lacks modern UX..."
solution	Text	Yes	Proposed solution	"Develop responsive website with..."
expected_outcomes	Array[String]	Yes	Expected outcomes	"Improved member onboarding experience"
project_plan	Array[Object]	No	Detailed project plan	[{ "milestones": { "id": "milestone_001", "title": "Initial Setup", "duration": "2 weeks", "contributions": ["contrib_001", "contrib_002"] } }]
budget_breakdown	Text	No	Detailed budget breakdown	""
attachments	Array[Object]	No	Supporting documents	[budget.csv, project_plan.doc]

3. ProposalStatus

Field	Type	Required	Description	Example
current_status	Enum	Yes	Current status	draft, submitted, in_review, signed_off, voting_process, approved, rejected, completed
status_history	Array[StatusChange]	Yes	Status change log	[{"status": "submitted", "timestamp": "2025-01-15T10:30:00Z"}]

4. ProposalRelationships

Field	Type	Required	Description	Example
related_proposals	Array[UUID]	No	Related proposals	[]
project_steward	UUID	Yes	Project steward ID	steward_001
project_owner	UUID	Yes	Project owner ID	proposer_001

5. ProposalEvaluation

Field	Type	Required	Description	Example
evaluation_outcome	Enum	No	Evaluation result	approved, rejected, revision_required
evaluation_feedback	Text	No	Evaluation comments	"Excellent proposal, meets all criteria"
evaluated_by	UUID	No	Evaluator ID	evaluator_001
evaluated_at	ISO 8601	No	Evaluation timestamp	2025-01-16T16:00:00Z

Validation Rules

1. Data Integrity Rules

• Unique Identifiers: All proposal IDs must be globally unique
• Required Fields: All required fields must be present and non-null
• Data Types: All field values must match their defined types
• Timestamps: All timestamps must be valid ISO 8601 format
• References: All UUID references must point to valid entities

2. Business Logic Rules

• Status Transitions: Only valid status transitions are allowed
• Assignment Rules: Proposals can only be assigned to open projects
• Dependency Validation: Parent proposals cannot be completed before children
• Sign-off Requirements: All proposals must be signed off by a steward before completion

3. Technical Validation Rules

• File Uploads: Attachments must meet size and format requirements
• URL Validation: All URLs must be valid and accessible
• Data Relationships: Circular dependencies are not allowed

Integration Points

1. Governance System Integration

The proposal schema integrates with the governance system to ensure seamless coordination between proposal management and decision-making processes:

• Proposal Status Synchronization: When proposal statuses change, the system automatically updates associated governance statuses to maintain consistency across the governance workflow
• Voting Integration: Proposal completion directly impacts voting outcomes and decision-making processes, ensuring that governance decisions reflect actual work progress
• Decision Tracking: All proposal-related decisions are automatically recorded in the governance history, providing a complete audit trail of community decisions and their implementation

2. Token System Integration

The schema connects with the token infrastructure to enable automated reward distribution and treasury management:

• Multi-Token Rewards: Support for CTR, UTIL, and NZD rewards with automated distribution through smart contracts and treasury systems
• CTR Minting: Smart contract integration automatically mints CTR tokens when proposals are completed and verified, ensuring timely reward distribution
• UTIL Transfer: Automated UTIL token transfers occur upon proposal completion, providing immediate access to utility tokens for completed work
• NZD Payments: Fiat currency rewards are processed through treasury management systems with proper compliance and tracking

3. Identity System Integration

The proposal system integrates with identity management to ensure proper authentication, authorization, and reputation tracking:

• DID Verification: Decentralized ID validation ensures that only verified community members can participate in proposals and receive rewards
• Role Assignment: Automatic role-based permissions are assigned based on assignment and contributor status, ensuring appropriate access levels and responsibilities
• Reputation Tracking: Contributor reputation systems integrate with proposal outcomes, building long-term trust and recognition within the community

Conclusion

The Proposal Schema provides a comprehensive foundation for managing proposals within the DAO ecosystem. By integrating cultural values, governance processes, and technical requirements, this schema ensures:

• Cultural Alignment: Proposals respect and advance community values
• Transparency: All proposal data is visible and auditable
• Scalability: Machine-readable data enables automation and growth
• Fairness: Clear rules and validation ensure equitable treatment
• Efficiency: Automated workflows reduce administrative overhead

The schema is designed to evolve with the community's needs while maintaining the core principles of decentralized governance and cultural preservation. Regular reviews and updates ensure it continues to serve the community effectively as the DAO grows and develops.