---
# System prepended metadata

title: 2. Core Units

---

# 2. Core Units

## Summary

This MIP proposal contains a framework for managing Core Units and modifying them in the DAO Primitives State MIP.

## Motivation

Core Units provide mission critical, long term areas of work and can cover a broad set of responsibilities. They are the basic units of domain work that Maker Governance is able to oversee, manage and prioritize.

## Specification / Proposal Details

### 1. Core Units Overview

- Core Units are a primary DAO Primitive used to enable Maker Governance to signal and prioritize the main objectives the domains need to solve.
- Core Units are at the intersection of Domains, which denotes skillsets and capabilities, and Core Objectives which denote cross-domain long term work streams. A Core Unit can participate in multiple Core Objectives, and can in some cases fall under multiple Domains.
    - Note on Core Objectives and Domains. Both Core Objectives and Domains are not directly defined in the DAO Primitives, but are flexible concepts that emerge through the interaction of DAO Primitives.
- The Mandate of a Core Unit is very important in setting the direction of the work that Facilitators should use their budget and their Governance Powers to achieve. The Core Unit Mandate can be seen as a "question" that the facilitator has to "answer" with their Facilitator Commitment when they propose to be onboarded to that Core Unit.
- The Core Unit Mandate should not be overly restrictive or micromanage the processes of the Core Unit, but be broad and open ended enough that Maker Governance leaves room for Facilitators to come up with innovative solutions and efficient processes.

---

### 2. Adding Core Units (Subproposal Process)

- This sub proposal process allows governance to create a new Core Unit with all of its relevant data, including Core Unit Mandate and Strategic Weight
- Once a sub proposal passes, the global state is modified to append a new entry with the new Core Unit name, the Core Unit Mandate and Strategic Weight specified in the sub proposal.
- The proposal parameters are: feedback period: 1 month / frozen period: 1 week
- Template:

c1: Core Unit name

c2: Core Unit Mandate

c3: Strategic Weight

---

### 3. Modifying Core Units

- This sub proposal process allows governance to modify an existing Core Unit by changing some or all of its relevant data, including Core Unit Mandate and strategic weight
- Once a sub proposal passes, the Core Unit specified has its entry modified with the new Core Unit Mandate (if any) and the new Strategic Weight (if any)
- The proposal parameters are: feedback period: 1 month, frozen period: 1 week
- Template:

c1: Core Unit name

c2: Core Unit Mandate

c3: Strategic Weight

---

### 4. Removing Core Units

- This sub proposal process allows governance to permanently delete a Core Unit from the global state. A Core Unit can only be deleted if its budget is set to 0 and it has no active facilitators.
- The proposal parameters are: feedback period 1 month, frozen period: 1 week
- Template:

c1: Core Unit name

---