Resource Allocation Framework ✏️ [EDITED]

The following post has been edited based on discussion and experimental use of this process via the Navnaut Request for Funding proposal. Original resource allocation post and discussion here.

Experimental Period: My proposal for this resource allocation framework is using it for 3 months ‒ until August/September [exact date TBD, based on when this is ratified] ‒ and then revising it, if need be. Based on recent Orca FM spaces discussing resource allocation, I’ve personally observed that resource allocation is one of the things that rapidly changes as the organization changes. I want to make sure we’re constantly updating these types of frameworks (as they can become very outdated and slow things down).

Goal: create a minimum viable framework for resource allocation throughout Orca.

Note: “Resources” in this context refers to assets used to fund initiatives.

Consent required: This framework is for use by the Source Pod and thus requires consent from members of the Source Pod.

Action Items

Please reply with edits that:

  1. Should have been made but were not made to this document (which is my fault ‒ I probably missed a few)
  2. Feel necessary to make this resource allocation framework safe to try and good enough for now

Design Principles

  1. Amount of funds allocated to a given pod is determined by the domains a pod takes on and the budget allocated to each domain
  2. Funding is distributed to pods that have responsibility over a given set of domains
  3. Source Pod is responsible for consenting to the allocation of resources across pods

Commissioned Domains

Domains that have a pre-allocated budget.

Note: today, that means funded by Sonar Labs – in the future, this could mean a pre-allocated budget from the Orca treasury more broadly or from external parties.

Non-commissioned Domains

Domains that do not have a pre-allocated budget.

Note: non-commissioned domains can become commissioned domains with consent from the Source Pod. See “Review of Non-commissioned Domains” for details.

Funding Process

Request for Funding

Requesting a commissioned domain requires (at minimum):

  1. Clearly articulated domain
  2. Proposed budget for domain (requested in ETH terms)
  3. Source of funds
  4. What does success look like?
  5. Committed individual(s) who are responsible for stewardship of the domain

:x: Removed from last draft:

2. Pod taking on the domain

Reference for removal.

:heavy_plus_sign: Added from last draft:

2. Proposed budget for domain (requested in ETH terms)

Reference for addition.

The Source Pod consents to commissioned domains quarterly and holds special meetings for processing funding of non-commissioned domains.

Quarterly Resource Allocation

The Source Pod meets quarterly to consent to commissioned domains. The process for consenting to domains is as follows:

  1. Each pod is responsible for submitting unique request for funding (see Request for Funding) for each domain they wish to work on for the next quarter
  2. The Source Pod holds one meeting with two brief rounds for each domain’s request for funding
    a. Question round – Source Pod members ask clarifying questions about each domain’s request for funding
    b. Feedback round – Source Pod members give initial thoughts on each domain’s request for funding
  3. One week period where authors of the request for funding have the opportunity to incorporate feedback and clarifications, if necessary
  4. The Source Pod holds final meeting to consent to each domain’s request for funding

Given current funding periods, the first quarterly resource allocation would occur July 1.

Special Meetings for Non-commissioned Domains

For domains that are not commissioned, any Orcanaut or Cadet may request a Review of Non-commissioned Domains. This request asks that the Source Pod discuss the commissioning of a domain that currently exists as a non-commissioned domain or a domain that has yet to be created but that requires funding.

The process is as follows:

  1. Submit a request for funding (see Request for Funding) for the domain that is requesting funding
  2. The Source Pod holds one meeting with two brief rounds for the domain’s request for funding
    a. Question round – Source Pod members ask clarifying questions about the domain’s request for funding
    b. Feedback round – Source Pod members give initial thoughts on the domain’s request for funding
  3. One week period where author of the request for funding has the opportunity to incorporate feedback and clarifications, if necessary
  4. The Source Pod holds final meeting to consent to the domain’s request for funding

Additional Guidelines

  1. Anyone may submit a request for funding proposal ‒ but it is encouraged that proposers are at minimum Cadets who have taken the time to gain context and understanding of Orca’s community and vision
  2. Each pod has the autonomy to decide how to allocate resources to pod members using the budgets they have been granted (compensating leads, facilitators, secretary, individuals doing the work, etc)
4 Likes

I consent to this Resource Allocation Framework as modifed.

Thank you!

2 Likes

Wooo! This is great to hear ‒ thank you for following up on this.

For organizational memory purposes, also want to flag that consent from all other Source Pod members was gathered at the Source Pod call on June 9th, 2022.

2 Likes

Moving this to #governance

1 Like