🎯 Contribution Process Simulation: New DAO Website Development

This document provides a comprehensive simulation of the Matou contribution process, starting with a proposal to develop a new website for the DAO. The simulation follows the complete lifecycle from proposal creation through implementation and completion.

📋 Simulation Overview

Scenario: A community member proposes developing a new website for the Matou DAO to improve community engagement, governance transparency, and member onboarding.

Timeline: 8-week project from proposal to completion Budget: 15,000 UTIL + 3,000 CTR tokens Team Size: 1 Project Steward, 1 Project Lead, 4 Contributors

🌱 Phase 1: Proposal Creation & Governance

Week 1: Proposal Creation

1.1 Community Validation

Community Member: Sarah (proposer) surfaces the idea in community channels
Discussion: Community discusses current website limitations and desired improvements
Validation: Community agrees the proposal addresses real needs and should move forward

1.2 Proposal Submission

Action 1: Sarah completes the proposal form with all required information

Action 2: Sarah submits the proposal through the governance portal

Action 3: System automatically creates proposal record with status "submitted"

Proposal Details:

{
  "proposal_id": "PROP_2025_001",
  "title": "Develop New Matou DAO Website",
  "estimated_budget": "15,000 UTIL",
  "timeline": "6 weeks development + 2 weeks testing",
  "current_status": "submitted"
}

See the proposal schema doc for full breakdown of proposal properties

1.3 Proposal Steward Contribution Request Creation

Action 4: System automatically creates two separate contribution requests

Primary Proposal Steward Contribution Request:

{
  "contribution": {
    "id": "CTR_2025_001_001",
    "proposal_id": "PROP_2025_001",
    "contribution_type": "governance",
    "estimated_duration": 20,
    "title": "Proposal Steward: New DAO Website Development",
    "current_status": "open",
    "contribution_reviewer": "",
    "assigned_contributor": "",
    "child_contributions": [
        {"id": "CTR_2025_001_001_001", "title": "Review Proposal", "current_status": "open", "rewards": [{"type": "util","amount": 200}]},
        {"id": "CTR_2025_001_001_002", "title": "Create Decision Plan", "current_status": "open", "rewards": [{"type": "util", "amount": 300}]},
        {"id": "CTR_2025_001_001_003", "title": "Action Decision Plan", "current_status": "open", "rewards": [{"type": "util", "amount": 400}]},
        {"id": "CTR_2025_001_001_004", "title": "Complete Proposal Governance", "current_status": "open", "rewards": [{"type": "util", "amount": 100}]}
    ]
  }
}

Proposal Steward Peer Reviewer Contribution Request:

{
  "contribution": {
    "id": "CTR_2025_001_002",
    "proposal_id": "PROP_2025_001",
    "contribution_type": "governance",
    "estimated_duration": 5,
    "title": "Proposal Steward Peer Reviewer",
    "current_status": "open",
    "contribution_reviewer": null,
    "assigned_contributor": "governance_system",
    "child_contributions": [
        {"id": "CTR_2025_001_002_001", "title": "Sign Off on Decision Plan", "current_status": "open", "rewards": [{"type": "util", "amount": 150}]},
        {"id": "CTR_2025_001_002_002", "title": "Support Proposal Governance", "current_status": "open", "rewards": [{"type": "util", "amount": 100}]}
    ]
  }
}

Please see the Contribution Schema Doc for a full breakdown of the Contribution properties

Action 5: All governance stewards are notified of the new contribution opportunities

1.4 Governance Steward Selection & Assignment

Action 6: Governance stewards register their interest in either the parent or child contribution requests

  // add registered_interest['steward_1, 'steward_2'] to the contributions
  {"id": "CTR_2025_001_001", "title": "Proposal Steward: New DAO Website Development", "registered_contributors": ["steward_1", "steward_2"]}
  {"id": "CTR_2025_001_001_002", "title": "Create Decision Plan",  "registered_contributors": ["steward_3"]}
  {"id": "CTR_2025_001_002", "title": "Proposal Steward Peer Reviewer", "registered_contributors": ["steward_1", "steward_2"]}

Action 7: System implements fair selection process for both roles. Alex is offered to Primary Proposal Stewards Contributions and Maria is offered to Peer Proposal Steward Contributions

{ "contribution_id": "CTR_2025_001_001", "title": "Primary Proposal Steward", "current_status": "on_offer", "assigned_contributor": "primary_steward_alex" }
{"contribution_id": "CTR_2025_001_002", "title": "Proposal Steward Peer Reviewer", "current_status": "assigned", "assigned_contributor": "peer_steward_maria" }

Fair Selection Process:

Interest Registration Period: 48-hour window for all governance stewards to register interest
Selection Criteria:

Primary Steward: Based on availability, relevant experience, and recent contribution load
Peer Reviewer: Based on governance expertise, availability, and lack of conflicts of interest

Load Balancing: System considers current contribution load to ensure fair distribution
Experience Matching: Prioritizes stewards with relevant proposal management experience
Random Selection: For equally qualified candidates, system uses weighted random selection

1.5 Governance Steward starts contribution

Action 8: Alex and Maria receive the offers and accept the contribution assignemnt

  { "contribution_id": "CTR_2025_001_001", "title": "Primary Proposal Steward", "current_status": "accepted", "assigned_contributor": "primary_steward_alex" }
  { "contribution_id": "CTR_2025_001_002", "title": "Proposal Steward Peer Reviewer", "current_status": "accepted", "assigned_contributor": "peer_steward_maria" }

Action 9: Alex naviages to the first contribution: Review Proposal and clicks "start contribution"

1.1 Review Proposal (CTR_2025_001_001_001) and parent contribution: Primary Proposal Steward status is updated to in_progress

  { "contribution_id": "CTR_2025_001_001_001", "title": "Review Proposal", "current_status": "in_progress" }
  { "contribution_id": "CTR_2025_001_001", "title": "Primary Proposal Steward", "current_status": "in_progress" }

1.6 Proposal Review & Validation

Action 10: Alex reviews the proposal for completeness and alignment

Action 11: Alex coordinates with Sarah to ensure all requirements are met

Action 12: Alex updates the "Review Proposal" contribution to complete

{
  "contribution_id": "CTR_2025_001_001_001", 
  "title": "Review Proposal", 
  "current_status": "completed",
  "completion_evidence": [
    "Complete proposal",
    "Alignment assessment documentation",
    "Requirements validation checklist",
    "Coordination notes"
  ],
  "actual_duration": "2.5 hours",
  "estimated_duration": "2 hours",
  "completion_notes": "Proposal successfully reviewed and validated. All requirements are complete and aligned with DAO mission. Ready for decision plan creation phase."
}

Action 13: Maria conducts review of the contribution for completeness

{ "id": "CTR_2025_001_001_001", "title": "Review Proposal", "current_status": "in_review" }

Action 14: Maria signs off the contribution and an additional 3 CTR is awarded based on her contribution review

{ 
  "id": "CTR_2025_001_001_001", 
  "title": "Review Proposal", 
  "current_status": "signed_off", 
  "rewards": [
    { "type": "util", "amount": 200 },
    { "type": "ctr", "amount": 3 }
  ] ,
  "review_feedback": "Excellent work on proposal review. All requirements thoroughly validated, alignment assessment is comprehensive, and stakeholder coordination demonstrates effective communication. Contribution meets all quality standards.",
}

Action 15: System automatically generates distribution request for rewards for the signed off contribution. The request is signed off by Treasury Steward

{
  "treasury_action": {
    "id": "TA_2025_001_001",
    "description": "Reward Distribution for Contribution CTR_2025_001_001_001",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "200 UTIL",
      "currency": "UTIL",
      "action_type": "distribution",
      "description": "Distribution of rewards for the completion and sign-off of the contribution CTR_2025_001_001_001."
    },
    "current_status": "completed",
    "destination": "primary_steward_alex"
    "relationships": {
      "related_proposals": ["PROP_2025_001"],
      "related_contributions": ["CTR_2025_001_001_001"],
      "initiated_by": "primary_steward_alex",
      "signed_off_by": "teasury_steward_jo"
    }
  }
}

Please see the Treasury Action Schema for a full breakdown of the Treasury Action properties

1.7 Decision Plan Creation

Action 16: Alex updates "Decision Plan Contribution" to "in_progress"

// CTR_2025_001_001_002: Create Decision Plan - Status Update to In Progress

{ "contribution_id": "CTR_2025_001_001_002", "title": "Create Decision Plan", "current_status": "in_progress" }

Action 17: Alex works with the proposer, and peer steward to design a Decision Plan

Alex collaborates with Sarah (the proposer) and Maria (the peer steward) to create a comprehensive decision plan that outlines the governance path for the website development proposal. They work together to:

Define the specific decisions needed from each governance house
Establish timelines for each decision phase
Identify key stakeholders and their roles
Create facilitation strategies for each governance group
Develop communication plans for the proposal

This information is then formed into a Decision Plan and associated Governance Actions

{
  "decision_plan": {
      "id": "dp_2025_001",
      "description": "Outline of governance actions required for effective decision making",
      "expected_outcomes": ["Approved proposal with clear governance path"],
      "governance_actions": ["GA_2025_001_001", "GA_2025_001_002", "GA_2025_001_003", "GA_2025_002_001", "GA_2025_002_002"],
      "current_status": "draft"
  }
}

Please see the Decision Plan Schema for a full breakdown of the Decision Plan properties

Action 18: Alex updates the "Create Decision Plan" contribution to "complete"

{ "contribution_id": "CTR_2025_001_001_002", "title": "Create Decision Plan", "current_status": "complete" }

1.8 Decision Plan Review and Validation

Action 19: Maria reviews the Decision Plan for completeness and alignment with governance objectives

  { "contribution_id": "CTR_2025_001_001_002", "title": "Create Decision Plan", "current_status": "in_review" }

Action 20: Maria coordinates with Alex to ensure all governance requirements are met

Action 21: Maria updates the 'Create Decision Plan' contribution to 'signed_off' and 3 CTR is added to the rewards as part the review

{
  "contribution_id": "CTR_2025_001_001_002", 
  "title": "Create Decision Plan", 
  "current_status": "signed_off",
  "rewards": [{ "type": "util", "amount": 300 }, { "type": "ctr", "amount": 3 }]
}

Action 22: System automatically generates distribution request for rewards for the signed off contribution. The request is signed off by Treasury Steward

{
  "treasury_action": {
    "id": "TA_2025_001_002",
    "description": "Reward Distribution for Contribution CTR_2025_001_001_002",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "300",
      "currency": "UTIL",
    },
    "destination": "primary_steward_alex"
  }
}

Week 2: Governance Voting

2.1 Decision Plan Action

2.1.1 Elder Council Veto Vote

Process: 5-day voting period with facilitated discussion

Action 23: Alex starts action decision plan contribution

  { "contribution_id": "CTR_2025_001_001_003", "title": "Action Decision Plan", "current_status": "in_progress" }

Action 24: Alex presents proposal to council

  "decision_plan": {
    { "id": "DP_2025_001_001", "current_status": "council_proposal_introduction_complete" }
  }

Action 25: Alex coordinates council discussion

"decision_plan": {
  { "id": "DP_2025_001_001", "current_status": "council_discussion_complete" }
}
"governance_action": {
    "id": "ga_2025_002_001",
    "house": "elders_council"
    "action_type": "discussion",
    "current_status": "complete",
}

Action 26: Alex introduces council vote

"decision_plan": {
  { "id": "DP_2025_001_001", "current_status": "council_vote_opened" }
}
"governance_action": {
    "id": "ga_2025_002_001",
    "house": "elders_council",
    "action_type": "decision",
    "current_status": "open",
    "description": "Review cultural considerations of proposal and decide if proposal needs to be blocked",
}

Action 27: Council completes vote

"decision_plan": {
  { "id": "DP_2025_001_001", "current_status": "council_vote_complete" }
}
"governance_action": {
    "id": "ga_2025_002_001",
    "house": "elders_council",
    "action_type": "decision",
    "current_status": "complete",
    "outcome": "no_veto"
}

2.1.2 Community Representatives Strategic Vote

Process: 5-day voting period with facilitated discussion

Action 28: Alex presents proposal to community representatives

{ "id": "DP_2025_001_001", "current_status": "community_reps_proposal_introduction_complete" }

Action 29: Alex coordinates community reps discussion

{ "id": "DP_2025_001_001", "current_status": "community_reps_discussion_complete" }
{ "id": "GA_2025_002_002", "house": "community_reps", "action": "discussion", "current_status": "complete" }

Action 30: Alex introduces community reps vote

{ "id": "DP_2025_001_001", "current_status": "community_reps_vote_opened" }
{ "id": "GA_2025_001_002", 
  "house": "community_reps", 
  "action": "decision", 
  "description": "decide if the proposal sufficiently aligns with the collectives strategic direction", "current_status": "open" 
}
{ "id": "GA_2025_001_003", 
  "house": "community_reps", 
  "action": "decision", 
  "description": "decide if the collective should allocate the funds to the proposal", 
  "current_status": "open" 
}

Action 31: Community reps complete vote

{ "id": "DP_2025_001_001", "current_status": "community_reps_vote_complete" }

{ "id": "GA_2025_001_002", 
  "current_status": "complete", 
  "outcome": "approved", 
  "total_vote_tokens_for": 20, 
  "total_vote_tokens_against": 5, 
  "total_vote_power_for": 10, 
  "total_vote_power_against": 3, 
  "total_vote_participants": 10, 
  "feedback": [{ "id": "contributor_ian", "response": "this feels like exactly whats needed now" }] 
}
{ "id": "GA_2025_001_003",
  "current_status": "complete", 
  "outcome": "approved", 
  "total_vote_tokens_for": 18, 
  "total_vote_tokens_against": 7, 
  "total_vote_power_for": 9, 
  "total_vote_power_against": 4, 
  "total_vote_participants": 10 
}

Decisions:
- GA_2025_001_002: Strategic alignment: ✅ APPROVED (77% approval)
- GA_2025_001_003: Budget priority: ✅ APPROVED (69% approval)

2.1.3 Contributor Parameters Vote

Process: 5-day voting period with facilitated discussion

Action 32: Alex presents proposal to contributors

  { "id": "DP_2025_001_001", "current_status": "contributors_proposal_introduction_complete" }

Action 33: Alex coordinates contributors discussion

  { "id": "DP_2025_001_001", "current_status": "contributors_discussion_complete" }
  { "id": "GA_2025_002_003", "house": "contributors", "action": "discussion" }

Action 34: Alex introduces contributors vote

  { "id": "DP_2025_001_001", "current_status": "contributors_voting_opened" }
  { "id": "GA_2025_001_004", 
    "house": "contributors", 
    "action": "decision", 
    "current_status": "open", 
    "description": "decide if the proposed solution is technically viable" 
  }
  { "id": "GA_2025_001_005", 
    "house": "contributors", 
    "action": "decision", 
    "current_status": "open", 
    "description": "decide if the budget allocation is viable"
  }
  { "id": "GA_2025_001_006", 
    "house": "contributors", 
    "action": "decision", 
    "current_status": "open", 
    "description": "decide if the proposed implementation plan is viable"
  }

Action 35: Contributors complete vote

{ "id": "DP_2025_001_001", "current_status": "contributors_voting_complete" }
{ "id": "GA_2025_001_004", 
  "house": "contributors", 
  "action": "decision", 
  "current_status": "complete", 
  "description": "decide if the proposed solution is technically viable",
  "total_vote_tokens_for": 40, "total_vote_tokens_against": 10, 
  "total_vote_power_for": 20, "total_vote_power_against": 9, 
  "vote_outcome": "approved", 
  "total_vote_participants": 2x0, 
  "feedback": [{ "id": "contributor_ben", "response": "great idea, glad we are not using a CMS for implementation." }] 
}
{ "id": "GA_2025_001_005", 
"current_status": "complete", 
"description": "decide if the proposed budget allocation is reasonable", 
"total_vote_tokens_for": 40, "total_vote_tokens_against": 10, 
"total_vote_power_for": 20, "total_vote_power_against": 9, 
"vote_outcome": "approved", 
"total_vote_participants": 20
}
{ "id": "GA_2025_001_006",
  "house": "contributors", 
  "action": "decision", 
  "current_status": "complete", 
  "description": "decide if the implementation plan is reasonable",
  "total_vote_tokens_for": 40, "total_vote_tokens_against": 10, 
  "total_vote_power_for": 20, "total_vote_power_against": 9, 
  "vote_outcome": "approved",
  "total_vote_participants": 20
}

Decisions:
- GA_2025_001_004: Technical feasability: ✅ APPROVED (68% approval)
- GA_2025_001_005: Reasonable budget: ✅ APPROVED (68% approval)
- GA_2025_001_006: Reasonable implementation plan: ✅ APPROVED (68% approval)

Final Status: ✅ PROPOSAL APPROVED - Ready for implementation

2.2 Decision Plan Action Review and validation

Action 36: Alex completes contribution "Action decision plan"

{ "contribution_id": "CTR_2025_001_001_003", "title": "Action Decision Plan", "current_status": "complete" }

Action 37: Maria signs off on contribution "Action decision plan" and 10 CTR is awarded based on the review

{
"contribution_id": "CTR_2025_001_001_002", 
"title": "Action Decision Plan", 
"current_status": "signed_off",
"rewards": [{ "type": "util", "amount": 400 }, { "type": "ctr", "amount": 10 }]
}

Action 38: System automatically generates distributions for rewards for the signed off contributions. The request is signed off by a Treasury Steward

{
  "treasury_action": {
    "id": "TA_2025_001_003",
    "description": "Reward Distribution for signed off Contributions CTR_2025_001_001_003",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "400",
      "currency": "UTIL",
    },
    "destination": "primary_steward_alex"
  }
},
{
  "treasury_action": {
    "id": "TA_2025_001_004",
    "description": "Reward Distribution for signed off Contributions CTR_2025_001_001_003",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "10",
      "currency": "CTR",
    },
    "destination": "primary_steward_alex"
  }
}

🪴 Phase 2: Project Preparation

Week 4: Project Setup

1.1 Project Resouces Allocated

Action 39: The treasury system automatically allocates treasury funds to the proposal based on the successful proposal

  {
    "treasury_action": {
      "id": "TA_2025_002_001",
      "description": "Treasury Allocation for Proposal PROP_2025_001",
      "reason": "successful_proposal",
      "amount": "15000",
      "currency": "UTIL",
      "action_type": "allocation",
      "destination": "PROP_2025_001",
      "current_status": "allocated",
      "treasury_balance": {
        "unallocated": {
          "UTIL": 9985000,
          "NZD": 100000,
          "ADA": 100000,
          "USD": 50000,
          "ETH": 10000
        },
        "allocated": {
          "UTIL": 15000
        }
      }
    }
  }

1.2 Project Leadership Contributors

Action 40: Alex creates a "project steward contribution request" and a "project lead contribution request"

{
  "contribution": {
    "id": "CTR_2025_001_003",
    "proposal_id": "PROP_2025_001",
    "contribution_type": "governance",
    "estimated_duration": 10,
    "title": "Project Steward: New DAO Website Development",
    "current_status": "open",
    "child_contributions": [
        {"id": "CTR_2025_001_003_001", "title": "review and sign off implementation plan", "current_status": "open", "rewards": [{"type": "util","amount": 200}]},
        {"id": "CTR_2025_001_003_002", "title": "support project completion", "current_status": "open", "rewards": [{"type": "util", "amount": 300}]}
    ]
  }
}

{
  "contribution": {
    "id": "CTR_2025_001_004",
    "proposal_id": "PROP_2025_001",
    "contribution_type": "governance",
    "estimated_duration": 20,
    "title": "Project Lead: New DAO Website Development",
    "current_status": "open",
    "child_contributions": [
        {"id": "CTR_2025_001_004_001", "title": "create implementation plan and contributions", "current_status": "open", "rewards": [{"type": "util","amount": 500}]},
        {"id": "CTR_2025_001_004_002", "title": "complete implementation plan", "current_status": "open", "rewards": [{"type": "util", "amount": 1500}]}
    ]
  }
}

Action 41: Project stewards register their interest to steward the project implementation

Action 42: Alex identifies Mary as the best suited project steward and offers them the contribution assignment

// project steward contribution status updated to "on_offer" and assigned_contributot to steward_mary
{ "id": "CTR_2025_001_003", "title": "Project Steward: New DAO Website Development", "current_status": "on_offer", "assigned_contributor": "project_steward_mary"
}

Action 43: Mary accepts the offer

// project steward contribution status updated to "on_offer" and assigned_contributot to steward_mary
{ "id": "CTR_2025_001_003", "title": "Project Steward: New DAO Website Development", "current_status": "assigned" }

Action 44: Alex onboards Mary to the project and together they identify Hemi as project lead.

{ "id": "CTR_2025_001_004", "title": "Project Lead: New DAO Website Development", "current_status": "on_offer", "assigned_contributor": "project_lead_hemi"
}

Action 45: Hemi accepts the offer

{ "id": "CTR_2025_001_004", "title": "Project Lead: New DAO Website Development", "current_status": "assigned" }

1.3 Governace Stewards Handover

Action 46: Alex marks Contribution "Handover Proposal" as complete

  { "id": "CTR_2025_001_001_004", "title": "Handover Proposal", "current_status": "complete" }

Action 47: Maria reviews and verifies the contribution is complete

  { "id": "CTR_2025_001_001_004", "title": "Complete Proposal Governance", "current_status": "signed_off" }

Action 48: Maria marks contribution "Support Proposal Governance" task to complete

  { "id": "CTR_2025_001_002_002", "title": "Support Proposal Governance", "current_status": "complete" }

Action 49: The system verifies that the dependent Complete Proposal Contribution is signed off and signs off Maria's "Support Proposal Governance" contribution

  { "id": "CTR_2025_001_002_002", "title": "Support Proposal Governance", "current_status": "signed_off" }

Action 50: System automatically generates distributions for rewards for the signed off contributions. The request is signed off by a Treasury Steward

{
  "treasury_action": {
    "id": "TA_2025_001_008",
    "description": "Reward Distribution for signed off Contributions CTR_2025_001_001_004",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "100",
      "currency": "UTIL",
    },
    "destination": "primary_steward_alex"
  }
},
{
  "treasury_action": {
    "id": "TA_2025_001_009",
    "description": "Reward Distribution for signed off Contributions CTR_2025_001_001_004",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "3",
      "currency": "CTR",
    },
    "destination": "primary_steward_alex"
  }
}

{
  "treasury_action": {
    "id": "TA_2025_001_010",
    "description": "Reward Distribution for signed off Contributions CTR_2025_001_002_002",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "150",
      "currency": "UTIL",
    },
    "destination": "peer_steward_maria"
  }
},
{
  "treasury_action": {
    "id": "TA_2025_001_011",
    "description": "Reward Distribution for signed off Contributions CTR_2025_001_002_002",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "3",
      "currency": "CTR",
    },
    "destination": "peer_steward_maria"
  }
}

2.1 Implementation Plan Creation

Action 51: Hemi starts the Create Project Implementation Plan contribution

  { "id": "CTR_2025_001_004_001", "title": "Create implementation plan", "current_status": "in_progress" }

  { "id": "CTR_2025_001_004", "title": "Project lead: New DAO website", "current_status": "in_progress" }

// Implementation plan

{
  "implementation_plan": {
    "id": "ip_2025_001",
    "title": "New Website Development",
    "total_budget": "12,500 UTIL",
    "milestones": [
      {
        "milestone_id": "ms_2025_001",
        "title": "Discovery & Design",
        "duration": "2 weeks",
        "contributions": [
          { "id": "CTR_2025_001_007", "title": "User research", "status": "draft", "reward": { "util": "800" }},
          { "id": "CTR_2025_001_008", "title": "Website wireframes", "status": "draft", "reward": { "util": "800" }},
          { "id": "CTR_2025_001_009", "title": "Website design", "status": "draft", "reward": { "util": "1800" }}
        ]
      },
      {
        "milestone_id": "ms_2025_002",
        "title": "Development",
        "duration": "4 weeks",
        "contributions": [
          { "id": "CTR_2025_001_010", "title": "Frontend development", "status": "draft", "reward": { "util": "3000" }},
          { "id": "CTR_2025_001_011", "title": "Backend API", "status": "draft", "reward": { "util": "1500" }},
          { "id": "CTR_2025_001_012", "title": "Database setup", "status": "draft", "reward": { "util": "2000" }}
        ]
      },
      {
        "milestone_id": "ms_2025_003",
        "title": "Testing & Deployment",
        "duration": "2 weeks",
        "contributions": [
          { "id": "CTR_2025_001_013", "title": "Testing", "status": "draft", "reward": { "util": "1000" }},
          { "id": "CTR_2025_001_014", "title": "Deployment", "status": "draft", "reward": { "util": "800" }},
          { "id": "CTR_2025_001_015", "title": "Documentation", "status": "draft", "reward": { "util": "800" }}
        ]
      }
    ],
    "current_status": "draft",
    "related_proposals": ["PROP_2025_001"],
    "project_lead": "project_lead_hemi",
    "evaluation_outcome": "draft"
  }
}

Please see the Implementation Plan Schema Doc for a full breakdown of the Implementation Plan properties

Action 52: Hemi completes Create Project Implementation Plan contribution

  { "id": "CTR_2025_001_004_001", "title": "Create implementation plan", "current_status": "complete" }

Action 53: Mary reviews the plan and signs off on the plan and associated contributions

  { "id": "CTR_2025_001_004_001", "title": "Create implementation plan", "current_status": "signed_off" }

{
  "implementation_plan": {
    "id": "ip_2025_001",
    "title": "New Website Development",
    "milestones": [
      {
        "milestone_id": "ms_2025_001",
        "title": "Discovery & Design",
        "contributions": [
          { "id": "CTR_2025_001_007", "title": "User research", "status": "open", "reward": { "util": "800" }},
          { "id": "CTR_2025_001_008", "title": "Website wireframes", "status": "open", "reward": { "util": "800" }},
          { "id": "CTR_2025_001_009", "title": "Website design", "status": "open", "reward": { "util": "1800" }}
        ]
      },
      {
        "milestone_id": "ms_2025_002",
        "title": "Development",
        "duration": "4 weeks",
        "contributions": [
          { "id": "CTR_2025_001_010", "title": "Frontend development", "status": "open", "reward": { "util": "3000" }},
          { "id": "CTR_2025_001_011", "title": "Backend API", "status": "open", "reward": { "util": "1500" }},
          { "id": "CTR_2025_001_012", "title": "Database setup", "status": "open", "reward": { "util": "2000" }}
        ]
      },
      {
        "milestone_id": "ms_2025_003",
        "title": "Testing & Deployment",
        "duration": "2 weeks",
        "contributions": [
          { "id": "CTR_2025_001_013", "title": "Testing", "status": "open", "reward": { "util": "1000" }},
          { "id": "CTR_2025_001_014", "title": "Deployment", "status": "open", "reward": { "util": "800" }},
          { "id": "CTR_2025_001_015", "title": "Documentation", "status": "open", "reward": { "util": "800" }}
        ]
      }
    ],
    "current_status": "approved",
    "related_proposals": ["PROP_2025_001"],
    "project_lead": "project_lead_hemi",
    "evaluation_outcome": "approved"
  }
}

Action 54: Mary updates "Review and sign off implementation plan" contribution to "complete"

  { "id": "CTR_2025_001_003_001", "title": "Review and sign off implementation plan", "current_status": "complete" }

Action 55: The system automatically signs off on Mary's contribution

Action 56: Rewards are automatically distributed to Hemi and Mary

{
  "treasury_action": {
    "id": "TA_2025_001_012",
    "description": "Reward Distribution for signed off Contributions CTR_2025_001_003_001",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "200",
      "currency": "UTIL",
    },
    "destination": "project_steward_mary"
  }
},
{
  "treasury_action": {
    "id": "TA_2025_001_013",
    "description": "Reward Distribution for signed off Contributions CTR_2025_001_003_001",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "3",
      "currency": "CTR",
    },
    "destination": "project_steward_mary"
  }
}

{
  "treasury_action": {
    "id": "TA_2025_001_014",
    "description": "Reward Distribution for signed off Contributions CTR_2025_001_004_001",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "1500",
      "currency": "UTIL",
    },
    "destination": "project_lead_hemi"
  }
},
{
  "treasury_action": {
    "id": "TA_2025_001_015",
    "description": "Reward Distribution for signed off Contributions CTR_2025_001_004_001",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "8",
      "currency": "CTR",
    },
    "destination": "project_lead_hemi"
  }
}

🛠️ Phase 3: Project Contributions

Week 5: Contribution Assignment

Action 57: The open contributions are listed for contributor registration

Action 58: Contributors register their interest to complete the contribution

Action 59: Mary and Hemi make contribution offers to contributors

{
  "implementation_plan": {
    "contributions": [
      { "id": "CTR_2025_001_007", "title": "User research", "status": "on_offer", "assigned_contributor": "designer_dave"},
      { "id": "CTR_2025_001_008", "title": "Website wirefranes", "status": "on_offer", "assigned_contributor": "designer_dave"},
      { "id": "CTR_2025_001_009", "title": "Website design", "status": "on_offer", "assigned_contributor": "designer_dave"},
      { "id": "CTR_2025_001_010", "title": "Frontend development", "status": "on_offer", "assigned_contributor": "developer_dani"},
      { "id": "CTR_2025_001_011", "title": "Backend API", "status": "on_offer", "assigned_contributor": "developer_dani"},
      { "id": "CTR_2025_001_012", "title": "Database setup", "status": "on_offer", "assigned_contributor": "developer_dani"}
      { "id": "CTR_2025_001_013", "title": "Testing", "status": "on_offer", "assigned_contributor": "designer_dave"},
      { "id": "CTR_2025_001_014", "title": "Deployment", "status": "on_offer", "assigned_contributor": "developer_dani"},
      { "id": "CTR_2025_001_015", "title": "Documentation", "status": "on_offer", "assigned_contributor": "developer_dani"}
    ]
  }
}

Weeks 6 - 12: Contribution completion

Action 60: Designer Dan and Developer Dani accept the contribution offers

{
  "implementation_plan": {
    "contributions": [
      { "id": "CTR_2025_001_007", "title": "User research", "status": "assigned", "contribution_lead": "designer_dave", "contribution_reviewer": "project_steward_mary"},
      { "id": "CTR_2025_001_008", "title": "Website wirefranes", "status": "assigned", "contribution_lead": "designer_dave", "contribution_reviewer": "project_steward_mary"},
      { "id": "CTR_2025_001_009", "title": "Website design", "status": "assigned", "contribution_lead": "designer_dave", "contribution_reviewer": "project_steward_mary"},
      { "id": "CTR_2025_001_010", "title": "Frontend development", "status": "assigned", "contribution_lead": "developer_dani", "contribution_reviewer": "project_steward_mary"},
      { "id": "CTR_2025_001_011", "title": "Backend API", "status": "assigned", "contribution_lead": "developer_dani", "contribution_reviewer": "project_steward_mary"},
      { "id": "CTR_2025_001_012", "title": "Database setup", "status": "assigned", "contribution_lead": "developer_dani", "contribution_reviewer": "project_steward_mary"}
      { "id": "CTR_2025_001_013", "title": "Testing", "status": "assigned", "contribution_lead": "designer_dave", "contribution_reviewer": "project_steward_mary"},
      { "id": "CTR_2025_001_014", "title": "Deployment", "status": "assigned", "contribution_lead": "developer_dani", "contribution_reviewer": "project_steward_mary"},
      { "id": "CTR_2025_001_015", "title": "Documentation", "status": "assigned", "contribution_lead": "developer_dani", "contribution_reviewer": "project_steward_mary"}
    ]
  }
}

Action 61: Dave starts the "User Research"

{ "id": "CTR_2025_001_007", "title": "User research", "status": "in_progress"},

Action 62: Dave completes user research

{ "id": "CTR_2025_001_007", "title": "User research", "status": "completed", "evidence_submitted": "user_research_report.md" },

Action 63: Hemi confirms contribution completion

{ "id": "CTR_2025_001_007", "title": "User research", "status": "in_review" },

Action 64: Hemi coordinates with Mary to sign off on the contribution

{ "id": "CTR_2025_001_007", "title": "User research", "status": "signed_off" },

Action 65: The contribution reward is distributed to Dave

{
  "treasury_action": {
    "id": "TA_2025_001_013",
    "description": "Reward Distribution for signed off Contributions CTR_2025_001_007",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "800",
      "currency": "UTIL",
    },
    "destination": "designer_dave"
  }
},
{
  "treasury_action": {
    "id": "TA_2025_001_013",
    "description": "Reward Distribution for signed off Contributions CTR_2025_001_007",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "4",
      "currency": "CTR",
    },
    "destination": "designer_dave"
  }
}

Actions 61-65 are repeated for all contributions until all "Implementation Plan Contributions" are "complete"

Action 87: Hemi updates the implementation plan status to complete

// Implementation plan

{
  "implementation_plan": {
    "id": "ip_2025_001",
    "title": "New Website Development",
    "total_budget": "12,500 UTIL",
    "milestones": [
      {
        "milestone_id": "ms_2025_001",
        "title": "Discovery & Design",
        "duration": "2 weeks",
        "contributions": [
          { "id": "CTR_2025_001_007", "title": "User research", "status": "complete", "reward": { "util": "800" }},
          { "id": "CTR_2025_001_008", "title": "Website wireframes", "status": "complete", "reward": { "util": "800" }},
          { "id": "CTR_2025_001_009", "title": "Website design", "status": "complete", "reward": { "util": "1800" }}
        ]
      },
      {
        "milestone_id": "ms_2025_002",
        "title": "Development",
        "duration": "4 weeks",
        "contributions": [
          { "id": "CTR_2025_001_010", "title": "Frontend development", "status": "complete", "reward": { "util": "3000" }},
          { "id": "CTR_2025_001_011", "title": "Backend API", "status": "complete", "reward": { "util": "1500" }},
          { "id": "CTR_2025_001_012", "title": "Database setup", "status": "complete", "reward": { "util": "2000" }}
        ]
      },
      {
        "milestone_id": "ms_2025_003",
        "title": "Testing & Deployment",
        "duration": "2 weeks",
        "contributions": [
          { "id": "CTR_2025_001_013", "title": "Testing", "status": "complete", "reward": { "util": "1000" }},
          { "id": "CTR_2025_001_014", "title": "Deployment", "status": "complete", "reward": { "util": "800" }},
          { "id": "CTR_2025_001_015", "title": "Documentation", "status": "complete", "reward": { "util": "800" }}
        ]
      }
    ],
    "current_status": "complete",
    "related_proposals": ["PROP_2025_001"],
    "project_lead": "project_lead_hemi",
  }
}

Action 88: Hemi updates Complete Implementation Plan Contribution to complete

{ "id": "CTR_2025_001_004_002", "title": "Complete Implementation Plan", "status": "completed", "evidence_submitted": ["implementation_plan.status == "complete"] },

Action 89: Mary signs off the complete implementation plan contribution

{ "id": "CTR_2025_001_004_002", "title": "Complete Implementation Plan", "status": "aigned_off", "contribution_reviewer:": "project_steward_mary" },

Action 90: Mary updates the Support Project Completion Contribution to complete

{ "id": "CTR_2025_001_004_002", "title": "Complete Implementation Plan", "status": "completed", "evidence_submitted": "CTR_2025_001_004_002 == "signed_off" },

Action 91: The system verifies that all implementation contributions are complete and signs off the contribution

Action 92: Rewards are automatically distributed to Hemi and Mary

{
  "treasury_action": {
    "id": "TA_2025_001_021",
    "description": "Reward Distribution for signed off Contributions CTR_2025_001_003_002",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "300",
      "currency": "UTIL",
    },
    "destination": "project_steward_mary"
  }
},
{
  "treasury_action": {
    "id": "TA_2025_001_022",
    "description": "Reward Distribution for signed off Contributions CTR_2025_001_003_002",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "3",
      "currency": "CTR",
    },
    "destination": "project_steward_mary"
  }
}

{
  "treasury_action": {
    "id": "TA_2025_001_23",
    "description": "Reward Distribution for signed off Contributions CTR_2025_001_004_001",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "1500",
      "currency": "UTIL",
    },
    "destination": "project_lead_hemi"
  }
},
{
  "treasury_action": {
    "id": "TA_2025_001_24",
    "description": "Reward Distribution for signed off Contributions CTR_2025_001_004_001",
    "reason": "contribution_signed_off",
    "details": {
      "amount": "8",
      "currency": "CTR",
    },
    "destination": "project_lead_hemi"
  }
}

Action 93: The system updates the proposal status to complete

🔍 Key Learnings & Insights

8.1 Process Strengths

Clear Governance Structure: Multi-house voting ensured comprehensive approval
Cultural Alignment: Elder council involvement maintained cultural integrity
Transparent Budgeting: Clear token allocation and tracking
Quality Assurance: Multiple review layers ensured high standards

8.2 Areas for Improvement

Risk Management: Could benefit from more detailed risk assessment
Treasury Management: Documentation required around distribution management
CTR Distribution Review: Review the CTR distrbution process to include consideration for contribution effort
UTIL Distribution Review: Define the use of effort (time-tracking) and the impact this has on contribution rewards

8.3 Best Practices Identified

Regular Check-ins: System defines requirements with impacting autonomy
Peer Reviews: Multiple review layers ensured quality
Flexible Planning: Agile approach allowed for adaptation
Cultural Integration: Regular cultural validation maintained alignment

🚀 Future Simulation Scenarios

9.1 Potential Scenarios

Delayed Rewards: Simulate different delayed rewards scenarios
Proposal changes: Simulate how changes to the proposal are made based on the governance process
Contribution changes: Simulate requests to change the contribution and the impact that has on project resources
Treasury Steward Signoff: Either simulate or define who/which treasury steward is responsible for distribution signoff.

📚 Conclusion

This simulation demonstrates the comprehensive nature of the Matou governance and contribution process, from initial proposal through successful completion. The process ensures:

Cultural Alignment: All decisions respect community values
Transparency: Clear recording and visibility into all stages and decisions
Quality Assurance: Multiple review layers maintain standards
Fair Compensation: Structured reward system for all contributors
Community Involvement: Multi-house governance ensures representation

The simulation provides a template for future projects and helps identify areas for process improvement and optimization.

This simulation is based on the Matou Contribution Model v1.0 and follows the established governance and contribution processes. For questions or suggestions, please submit through the governance proposal process.

📋 Simulation Overview​

🌱 Phase 1: Proposal Creation & Governance​

Week 1: Proposal Creation​

1.1 Community Validation​

1.2 Proposal Submission​

1.3 Proposal Steward Contribution Request Creation​

1.4 Governance Steward Selection & Assignment​

1.5 Governance Steward starts contribution​

1.6 Proposal Review & Validation​

1.7 Decision Plan Creation​

1.8 Decision Plan Review and Validation​

Week 2: Governance Voting​

2.1 Decision Plan Action​

2.2 Decision Plan Action Review and validation​

🪴 Phase 2: Project Preparation​

Week 4: Project Setup​

1.1 Project Resouces Allocated​

1.2 Project Leadership Contributors​

1.3 Governace Stewards Handover​

2.1 Implementation Plan Creation​

🛠️ Phase 3: Project Contributions​

Week 5: Contribution Assignment​

Weeks 6 - 12: Contribution completion​

🔍 Key Learnings & Insights​

8.1 Process Strengths​

8.2 Areas for Improvement​

8.3 Best Practices Identified​

🚀 Future Simulation Scenarios​

9.1 Potential Scenarios​

📚 Conclusion​