Treasury Action Schema

Overview

The Treasury Action Schema defines the structure for logging and managing treasury-related actions within the Matou DAO ecosystem. It ensures that all treasury actions are recorded, tracked, and aligned with the community's financial governance processes.

Schema Structure

Core Entities

{
  "treasury_action": {
    "metadata": "TreasuryActionMetadata",
    "details": "TreasuryActionDetails",
    "status": "TreasuryActionStatus",
    "relationships": "TreasuryActionRelationships"
  }
}

Data Fields

1. TreasuryActionMetadata

Field	Type	Required	Description	Example
id	UUID	Yes	Unique action identifier	action_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"
description	String	Yes	Action title	"Transfer to Development Fund"
reason	Enum	Yes	Reason for the action	proposal_approved

2. TreasuryActionDetails

Field	Type	Required	Description	Example
amount	String	Yes	Amount involved in the action	"10,000 UTIL"
currency	Enum	Yes	Currency type	UTIL, CTR, NZD
action_type	Enum	Yes	Type of action	transfer, allocation, withdrawal, deposit
source	UUID	Yes	Source of the distribution	source_001
destination	UUID	Yes	Destination of the distribution	contributor_001

3. TreasuryActionStatus

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

4. TreasuryActionRelationships

Field	Type	Required	Description	Example
related_proposals	Array[UUID]	No	Related proposals	[]
related_contributions	Array[UUID]	No	Related contributions	[]
initiated_by	UUID	Yes	Initiator ID	initiator_001
signed_off_by	UUID	Yes	Treasury steward ID who signed off the action	steward_001

Validation Rules

1. Data Integrity Rules

• Unique Identifiers: All action 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
• Currency Validation: Only supported currencies can be used

Integration Points

1. Governance System Integration

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

• Action Status Synchronization: When action statuses change, the system automatically updates associated governance statuses to maintain consistency across the governance workflow

2. Token System Integration

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

• UTIL Transfer: Automated UTIL token transfers occur upon action completion, providing immediate access to utility tokens for completed actions
• Distribution Tracking: The system now tracks the source and destination of each distribution, ensuring transparency and accountability in treasury actions.

Conclusion

The Treasury Action Schema provides a comprehensive foundation for managing treasury actions within the DAO ecosystem. By integrating financial governance processes and technical requirements, this schema ensures:

• Transparency: All action data is visible and auditable
• Scalability: Machine-readable data enables automation and growth
• 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 financial transparency. Regular reviews and updates ensure it continues to serve the community effectively as the DAO grows and develops.