1. Protocol

Anchor
1. 1.

This is a set of actions for acquiring the necessary resources for yunity. Each action should be considered more preferable than the one following it.

1.1. Expenditure

1.1.1. Avoidance

Anchor
1.1.1. 1.1.1.

Avoiding the use of money on behalf of yunity should always be the starting consideration when acquiring resources.

1. Assess necessity. Take a moment to consider whether we need this resource.
2. Acquisition without the use of money. The following sub-list of options is not exclusive;
   
   1. Reclamation. Rescue the resource from being wasted, abandoned or unused.
   2. Construction. Make the resource from other available resources.
   3. Borrowing. Individual or organization who already has the resource lends it.
   4. Donation. Individual or organization who already has the resource donates it - this is different to actively purchasing a resource explicitly to donate it, see Donation by proxy transaction below.

1.1.2. Donation by proxy transaction

Anchor
1.1.2. 1.1.2.

No one is expected to use money on behalf of yunity. If an individual or organization wishes to purchase a resource to donate to help yunity achieve it's Vision and Mission, they can.

1. Assess necessity. Consider whether this resource can be acquired with the Avoidance of money use. If not, consult 5. Collaborate with yunity or check with an active yunity contributor to see whether yunity actually needs the resource.
2. Donor makes transaction.
   1. Donation. Individual or organization who purchased the resource donates it.
   2. Record details. For anything that is explicitly purchased for donation to yunity, it is highly recommended to record the name of donor, date of transaction and a copy of receipt - if the donor consents. Recording these details is not to glorify the donor but to identify where yunity is still indirectly reliant on money - this knowledge will direct efforts into finding ways to avoid the use of money for acquiring the resource in future.

1.1.3. Donation by proxy transaction with refund request

Anchor
1.1.3. 1.1.3.

No one is expected to use money on behalf of yunity. If an individual or organization wishes to purchase a resource to donate to help yunity achieve it's Vision and Mission, they can. If for whatever reason they wish to have their expenditure refunded, they may make a request for this.

1. Assess necessity. Consider whether this resource can be acquired with the Avoidance of money use. If not, consult 5. Collaborate with yunity or check with an active yunity contributor to see whether yunity actually needs the resource. Consider whether whether a simple Donation by proxy transaction is actually desired.
2. Assess likelihood of refund. Refunding is never guaranteed, but an indication of refund likelihood can be made;
   
   1. Consult Explicit decisions. If the resource lies within the 'acceptable' section of Explicit decisions for Expenditure and has been refunded in the past, this will provide the most reliable indication of whether similar transactions are likely to be refunded in the future.
   2. Consult Guidelines. If the resource lies within the 'acceptable' section of Guidelines for Expenditure, this provides some indication or whether a transaction will be refunded in future
3. Donor makes transaction.
   1. Donation. Individual or organization who purchased the resource donates it.
   2. Record details. If refund requested, donor must provide;
      1. full use name
      2. date of purchase
      3. electronic copy of receipt
      4. consent that
         
         1. no transaction is guaranteed to be refunded
         2. if refunding of the transaction is accepted, there is no guarantee or indication when the refund will occur (i.e. might never happen).
         3. if refunding of the transaction is accepted, only the value that was spent at the time will be refunded (i.e. not adjusted for inflation).

1.1.4. Organizational transaction

Anchor
1.1.4. 1.1.4.

Refunding of of Donation by proxy transaction with refund request: Transactions which lie which ie within the accepted section of Explicit decisions for Expenditure or lie within the accepted section of the Guidelines for Expenditure can be reimbursed refunded if a Treasurer and two others consent. If there is doubt or disagreement dissent, the individual or organization who made the transaction should be contacted and notified of the relevant reasons why refunding was not consented upon and asked whether they want to pursue the refunding process or if the transaction is now a donationthey no longer wish to be refunded. If refunding is still sought, the decision goes to full Online systemic consensus to determine whether refunding should occur and the result is recorded in Explicit decisions.

Active organizational transaction: Transactions for resources amounting to less than €100.00 and which lie within the accepted section of Explicit decisions for Expenditure or lie within the accepted section of the Guidelines for Expenditure can be reimbursed purchased by the yunity organization if a Treasurer and two others consent. If there is dissent, or if the transaction exceeds €100.00, the decision goes to full Online systemic consensus to determine whether the purchase can be made and the result is recorded in Explicit decisions.

1.2. Income

All yunity organization income is held in the organizational bank account: money held by individuals is an individual matter.

1.2.1. Avoidance

Individuals or organizations wishing to donate money to yunity are first invited to assess our requirements - currently outlined in 5. Collaborate with yunity - then purchase and donate things that we actually need, see Donation by proxy transaction.

1.2.2. Unconditional acceptance

Truly anonymous financial donations are automatically accepted. This is only achievable by unconventional routes such as the use of BitCoin or anonymous donation boxes.

1.2.3. Conditional acceptance

Donations from individuals: name, amount and date recorded. Donations from companies, organizations, collectives, charities and institutions identified and brought forward for systemic consensus on a case-by-case basis according to the with decisions being appended to these guidelines.)

2. Explicit decisions

Anchor
2. 2.

This is a record of previous decisions made by full Online systemic consensus on whether transactions were acceptable or unacceptable in the name of yunity. This is the most reliable indication on whether a Proxy transaction will be refunded or not, though refunding is never guaranteed.This record is also the first consideration if making an Organization transaction.

2.1. Expenditure

Anchor
2.1. 2.1.

2.2. Income

3. Guidelines

Anchor
3. 3.

These are guidelines and as such individual cases are subject to interpretation. This is deliberate as outlining every single scenario is impossible, many speculated scenarios might never arise and we might suffocate in over-bureaucratization. This is a record of previous decisions n whether transactions were acceptable or unacceptable in the name of yunity. This is the most reliable indication on whether a Proxy transaction will be refunded or not, though refunding is never guaranteed.This record is also the first consideration if making an Organization transaction.

3.1. Expenditure

Anchor
3.1. 3.1.

Transaction that directly facilitate the achievement of the yunity Mission and Vision may if the desired resource cannot be gotten reasonably in any other way, see Avoidance and Donation by proxy transaction. All expenditure is for the project as a whole.

3.2. Income

It is important that in receiving money we do not compromise our values or the achievement of our goals. No donations or sponsorship should alter how we work or what we do, nor should they originate from sources that directly or explicitly go against our Mission and Vision. All income is for the project as a whole.

4. Changes to policy

Changes to this policy are to be made using the result of Online systemic consensus where;

• At least one week is given for the proposal forming phase and
• At least one week is given for the voting phase and
• The #core-team Slack channel has been suitably notified.