Skip to content

Governance Framework Adoption History

This page preserves the original rollout plan from the Head Admin Acceptance Proposal (Version 1.0) for historical reference. It is a record of how the Governance Framework was originally adopted — it is not current policy. For current policy, see the Administrative Governance Framework.

Origin

The Governance Framework began as a set of conditions for accepting the Head Admin position, proposed to improve consistency in administration, reduce staff burnout, improve transparency and accountability, clarify expectations for staff and players, protect volunteers while maintaining appropriate standards, and establish clear procedures for future growth.

Original Immediate Implementation Priorities

At adoption, these were called out as the first things to land:

  • Confirm TP zone structure.
  • Implement rotating RCON messages.
  • Create Staff Code of Conduct.
  • Create Staff Updates channel.
  • Create Staff Availability channel.
  • Implement review tags.
  • Review inactive staff status.
  • Open July recruitment process.
  • Establish Discord Moderator role.
  • Finalize administrative governance policies.

Original 30-Day Implementation Plan

Week 1

  • Finalize policy approval.
  • Establish TP zones.
  • Implement RCON messages.
  • Create Staff Updates channel.
  • Create Staff Availability channel.

Week 2

  • Finalize Staff Code of Conduct.
  • Create anonymous feedback form.
  • Implement review tags.
  • Review inactive staff status.

Week 3

  • Review Trial Admin promotions.
  • Open Trial Admin applications.
  • Create Discord Moderator role.

Week 4

  • Conduct first leadership review.
  • Gather staff feedback.
  • Adjust policies as necessary.

Why This Lives Here Instead of the Living Framework

The rollout plan above was a one-time transition plan tied to a specific adoption date, not standing policy — dated action items ("open applications in July," a four-week checklist) go stale the moment they're completed and clutter a document that's supposed to describe current expectations. Keeping them here instead preserves the historical record — including the reasoning that produced today's policy — without making the living Governance Framework page harder to trust as "what's true right now."

See Document Revision History for a running log of what changed in the framework itself, version over version.