Thanks for your feedback, @Planet_X. I wasn’t expecting any less from you. ; )
It helps us shed some light on the less clear sections.
Not quite. A Domain nowadays is something close to “a group of talent with some common skills”. While it is entirely possible that this is translated 1:1, I can also see Core Units appearing to solve other pressing issues that Governance might have.
A mandated actor is a generic name for the Core Unit Facilitator.
Now there’s a lot of a budget. With this MIP set, a Core Unit can get approved and expect a stream of payments; Governance needs to approve it once (and any subsequent modifications) but:
- Contributors benefit from knowing that they will be paid.
- Governance knows that the Facilitator will administer that budget to achieve the Core Unit Mandate.
This is the first step so that:
- any group that brings value to Governance can be proposed and get a budget.
- it works with current solutions (manual
suck()), solutions being developed (MIP34: Keg Streaming Payments Module), and any future solution that we haven’t yet thought about (bonuses/rewards/etc).
- more importantly: groups can organize in different ways according to their jurisdiction/processes/the desired outcome. For example:
- a Facilitator could set up a company and decide to make contributors employees (with the corresponding benefits).
- or they could decide to contribute as freelancers.
- or a group could create a DAO / LAO to organize that group that is providing these services to Maker).
Thanks again for your questions, @Planet_X. We appreciate them.