Decision Plan Schema

Overview

The Decision Plan Schema defines the structure for tracking governance actions required as part of the decision-making process. It ensures that all actions are aligned with the community's goals and governance processes.

Schema Structure

Core Entities

{
  "decision_plan": {
    "metadata": "DecisionPlanMetadata",
    "content": "DecisionPlanContent",
    "status": "DecisionPlanStatus",
    "relationships": "DecisionPlanRelationships",
    "evaluation": "DecisionPlanEvaluation"
  }
}

Data Fields

1. DecisionPlanMetadata

Field	Type	Required	Description	Example
id	UUID	Yes	Unique decision plan identifier	dp_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	Decision plan title	"Governance Actions for New Website"

2. DecisionPlanContent

Field	Type	Required	Description	Example
description	Text	Yes	Detailed description	"Outline of governance actions required for proposal approval..."
objectives	Array[String]	Yes	Objectives of the decision plan	"Ensure cultural alignment"
expected_outcomes	Array[String]	Yes	Expected outcomes	"Approved proposal with clear governance path"
governance_actions	Array[GovernanceAction]	Yes	List of associated governance actions	[ga_2025_001, ga_2025_002]

3. DecisionPlanStatus

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

4. DecisionPlanRelationships

Field	Type	Required	Description	Example
related_proposals	Array[UUID]	No	Related proposals	[]
governance_steward	UUID	Yes	Governance steward ID	steward_001

5. DecisionPlanEvaluation

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

Example

{
  "decision_plan": {
    "metadata": {
      "id": "dp_2025_001",
      "created_at": "2025-01-15T10:30:00Z",
      "updated_at": "2025-01-15T14:45:00Z",
      "version": "0.1",
      "title": "Governance Actions for New Website"
    },
    "content": {
      "description": "Outline of governance actions required for proposal approval...",
      "objectives": ["Ensure cultural alignment from Cultural Elders", "Ensure strategic alignment and budget priority from Community Reps", "Ensure project alignment from Contributors House" ],
      "expected_outcomes": ["Approved proposal with clear governance path"],
      "governance_actions": [
        {
          "id": "ga_2025_001",
          "title": "Elders Council Meeting",
          "description": "Discussion on proposal PROP_2025_001...",
          "house": "elders_council",
          "action_type": "meeting",
          "status": "planned",
          "related_decision_plan_id": "dp_2025_001",
          "created_by": "steward_001",
          "assigned_to": "steward_002",
          "due_date": "2025-01-20T10:00:00Z",
          "completed_at": null,
          "notes": "Initial meeting to discuss proposal."
        }
      ]
    },
    "status": {
      "current_status": "draft",
      "status_history": [
        {"status": "draft", "timestamp": "2025-01-15T10:30:00Z"}
      ]
    },
    "relationships": {
      "related_proposals": ["PROP_2024_001"],
      "governance_steward": "steward_001"
    },
    "evaluation": {
      "evaluation_outcome": "approved",
      "evaluation_feedback": "Comprehensive plan, meets all criteria",
      "evaluated_by": "evaluator_001",
      "evaluated_at": "2025-01-16T16:00:00Z"
    }
  }
}

Validation Rules

1. Data Integrity Rules

• Unique Identifiers: All decision plan 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

2. Business Logic Rules

• Status Transitions: Only valid status transitions are allowed
• Assignment Rules: Decision plans can only be assigned to open proposals

Integration Points

1. Governance System Integration

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

• Decision Plan Status Synchronization: When decision plan statuses change, the system automatically updates associated governance statuses to maintain consistency across the governance workflow
• Action Tracking: All decision plan-related actions are automatically recorded in the governance history, providing a complete audit trail of community decisions and their implementation

Conclusion

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

• Cultural Alignment: Decision plans respect and advance community values
• Transparency: All decision plan 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.