Admin Protocol

The protocol provides a convention to common administrative duties. We operate as a council and must reach unanimity prior to executing reforms and updates to the server.

Articles of Conduct

Each article is organized for your convenience, especially when invoked. You may simply cite the letter or share a screenshot of the article in a discussion.

#A — Direction

Administrators agree to be bound by protocol. While we hold more power and access, our actions are also more regulated. For example, when we exercise administrative authority we also must pass a unanimous directive, ensuring all administrators are informed, educated, and supportive of the action.

In order for a directive to be considered active you must submit the directive to the directive catalogue once it has satisfied the desired approval level.

Administrative Approval

Administrative approval requires unanimous support. Exerting your administrative authority customarily requires an administration-approved directive.

There is even utility to reaching admin approval for missions which do not require it.

  • You ensure all administrators are aware of and understand the incoming changes.
  • You verify that the full team is on-board, supports the mission, and will assist you to the best of their ability.

The peace of mind of an approved directive is a blessing.

Admin Approval reached during a meeting is known as Maximum Approval and takes precedence over all other forms of approval.

Limited Approval

Limited approval requires at least 50% support. An example of a situation where Limited Approval is generally acceptable is a public communication of earlier approved directives. You must openly declare and @ping the team when filing for a limited approval. Waiting 24 hours is recommended.

Expedited Approval

You may expedite a time-sensitive directive where absolutely necessary. Submit a ! check-mark reaction and openly document the rationale for urgency in the admin channel. The directive in question must reach approval within 7 days. If approval is unmet, the change is then void.

Predicated Approval

You may specify a special predicated status for a directive. A predicated approval is only effective once a chosen antecedent directive is admin approved, even if all members have voted in favour.

This is useful to split multi-step or massive missions into specific chunks—especially when certain directives only make sense in the context of prerequisite changes. Directives should specify particular changes as lumping many changes into one approval is considered bad practice.

#B — Contradicting Approvals

In order to update or overturn a directive, you must reach at least the level of approval attained by the chosen directive. The highest rated directive filed the most recently always holds priority.

#C — Neutral Vote

Abstaining from voting or voting neutrally both count as a denying vote. It is important that the administration is unambiguous in our support of one another, even if discussions take a bit longer as a result.

If you 'shrug' on an approval you are signalling that you would like further discussion or clarification on the topic. It is a way to let your fellow administrators know you have read and understood the directive without straight-out denying it and that you will vote at a later date.

#D — Conduct

We hold each other accountable to the highest level. This means we enjoy ourselves responsibly and we disagree responsibly. You are free within admin channels to express yourself as openly as you desire.

Representation

In public, we must make an effort to be a stable and unifying force. Make an effort to avoid subtly or explicitly alluding to conflict within the administration. If you absolutely must then disclaim that your beliefs on the matter are personal—though this is only acceptable in private mediums of communication.

  • You may not declare the vote preference of any admin without their permission.
  • You may voice concerns on existing policies and suggest reformation in a moderate and non-provoking manner.
  • Recording or sharing sensitive admin material is forbidden, including post-tenure.

Community Safety

  • Upon notice of an incident regarding community safety, you must disclose any report to the administration.

#E — Admin Meeting

An admin meeting is a convention based in voice between all non-hiatus members. We consider directives approved during an admin meeting to be the highest level of authority.

  • Any member may call for a meeting.
  • All members must declare their availability for the next week.
  • The team may file maximum approval rated directives during a meeting.

The administration should strive for a minimum of one full team meeting a month.

#F — Activity Check-in

An Activity Check-in is a call for agenda that gives a member the opportunity to highlight their current work and recent activity to the rest of the team. If a member appears inactive this gives them a chance to reveal any undeclared work or disclose extenuating circumstances.

The admin subject to this call must explain their recent activity to the best of their ability.

#G — Deferral Of Action

Heated conversations rarely end well and cripple our ability to compromise. A deferral pauses a particular discussion or action for up to 12 hours. Compliance is mandatory for all members.

A member may only invoke this once a day. Please respect the motion and understand that it is not a reflection on their competence but on the controversial charge of the situation.

#H — Permanent Bans

Two types of bans are considered permanent, and may not be appealed:

  • Terms of Service Violations (excluding Store Terms of Service)
  • Player Conduct Violations

Permanent bans require administrative approval. Reversing permanent bans is unprecedented, and requires server owner approval and new evidence.

#I — Hiatus

A hiatus simply removes you from the voting pool for a duration that you choose. A single declaration of hiatus may only last 30 days.

Hiatus can be declared on behalf of another member using Limited Approval. The hiatus comes into effect only after 72 hours without challenge. A member challenges a hiatus declaration by an active show of presence and tangible deeds.

A hiatus can be waived any time by the member on hiatus.

#J — Resignation

Once you resign, you have 7 days where you may unconditionally repeal your resignation. If you address the public with your departure then this does not apply.

#K — Promotion

In order to approve a candidate for the administration, the member must be vetted with a unanimous admin approval.

Admin Protocol

A candidate approved to join must first read and verify their understanding of protocol and, finally, they must agree to abide by it in good faith.

Demi-Admin

The preliminary phase lasts 3 months from the day of promotion. Once the preliminary phase is complete, the admin enters a 3 day review period where they must be admin approved by the original administrators in order to become a qualified administrator.

If this directive does not pass then they must depart the administration.

#L — Termination

A mandate for termination is a document presented to all administration which contains the rationale behind the directive. This requires maximum approval excluding the subject in question.

In order to terminate the administrator, the server owner must sign off on the document and agree to remove them from their position.

Members relieved from their duty this way are permanently blacklisted from the team. The process itself is confidential and leaking the matter authorizes a ban.

#M — Protocol Revision

Protocol revision requires maximum approval.

#N — Protocol Violation

A protocol violation must be recorded as a memo with the subject and details of the event. Expedited directives which violate or contradict protocol are considered immediately void.

Other Notes

What are examples of what I should approve?

In general, if you are unsure then you should veer on the side of caution and get the action approved. The reason is, if you are making a change that influences server direction then it is mandatory that you get it approved.

This does not include the day-to-day inner workings of your team, as there are many things you can do openly without seeking any level of admin approval. For example, adding/removing members on your team is not a matter of admin approval, neither is manager selection and etc. unless it contradicts an existing admin directive.

Some other examples include monthly team updates that announce general team ongoings, etc. If you're not announcing major team restructuring, a team wipe, changes to rules, or something of that level—then you do not need to seek approval for it. Replying to threads and speaking on behalf of your team generally is fine as the same idea.

Memo

A memo is a non-binding declaration by a single administrator. Memos serve to document & inform other administrators of minor actions and are not mandatory. If you are making changes that relate to a memo filed by another admin, you should inform the team.