Roles

Each member of SESO has one or more roles. They are multiple categories of roles, with the Executive Board being the most influential set of people.

All operatives of the Executive Board follow the naming scheme of Chief X Officer and generically referred to as CxOs. Each CxO has their own list of responsibilities which are widespread. In most cases, vacant positions within the Executive Board are fulfilled by the CEO.

All CxOs hold reputations of authority, often have overlapping jurisdictions, and access to sensitive server infrastructure. To prevent competition between CxOs, the Rule of Non-inteference applies the following:

Also known as CEO, manages the Executive Board and drives the unit towards an overall vision.

Unofficially, they are the leader of the unit. They possess access to all parts of SESO. Though, most responsibilities belong to other CxOs.

• Settle critical decisions for the unit
• Hire and onboard CxOs onto the Executive Board
• Manage and assist other CxOs of the Executive Board in their own responsibilities
• Maintain SESO Mission Framework
• Invest funds towards the unit
• Ensure SESO fulfills its mission

When on LOA, the CEO's responsibilities are inherited by the highest available CxO listed on this board. Usually, their responsibilities are inherited by the COO.

Also known as COO, manages Hosts and all aspects of hosting operations.

SESO's bread and butter are our operations. The COO ensures their quality and proliferation. This includes all aspects both the technical, such as the server panel and mod configuration, and the design, such as storytelling and time management.

• Promote passion in the mission design and storytelling of SESO
• Ensure utmost quality of operations within SESO, using Hosts and the server infrastructure as the foundation.
• Maintain a respectful reputation of SESO's hosts and their operations to attract New Hosts
• Improve accessibility to operations through use of scripts, engaging gameplay, and intuitive hosting
• Provide a varied set of mods and tools for Hosts to enhance operation quality and improve operation hosting efficiency
• Coordinate unit-wide changes with the Executive Board to support these operations

When on LOA, the COO's responsibilities are inherited by the highest available CxO listed on this board. Usually, their responsibilities are inherited by the CEO.

Also known as CHRO, manages these ⁠rules and solves interpersonal conflicts.

Any community is dependent on its cooperation and friendliness. However, interpersonal conflicts are inevitable. The CHRO attempts to settle people's differences through the enforcement of rules. Additionally, they can act as mediators in conflicts. All in all, the CHRO is essential in keeping SESO an friendly environment.

• TBA

When on LOA, the CHRO's responsibilities are inherited by the highest available CxO listed on this board. Usually, their responsibilities are inherited by the CEO.

Also known as CCO, ###

####

TODO

When on LOA, the CCO's responsibilities are inherited by the highest available CxO listed on this board. Usually, their responsibilities are inherited by the CEO.

Also known as CTO, manages Arma 3 servers, unit websites, and other unit technologies

Like this wiki, SESO hosts a variety of services that depend on our central infrastructure. The primary warden of our technology is the CTO. While other roles use SESO infrastructure to fulfill their missions, the CTO's missions revolve around the infrastructure itself.

• Help CxOs meet their mission needs by providing technology services and assistance
• Ensure utmost quality of the infrastructure backend for efficient use of resources
• Promote our public image through technical means such as the SESO website
• Centralize projects and developers under CTO's jurisdiction for quick and efficient decision-making
• Improve existing workflows through automated systems such as Kakapo's cogs
• Uphold security of server infrastructure via access to sensitive and powerful backend interfaces such as SSH

When on LOA, the CHRO's responsibilities are inherited by the highest available CxO listed on this board. Usually, their responsibilities are inherited by the CEO.

Also known as CGO, manages non-Arma 3 game servers.

While SESO is mostly focused on Arma-related content, there is occasional demand for other games. The CGO meets these demands by hosting other games and managing community game sessions. They serve the community on an ad hoc basis depending on the requests that come from operatives. In other words, they may be multiple games hosted at a time or none at all depending on the trends of the unit.

• Promote comradery and respectful attitudes through cooperation and friendly competition
• Authorizing game servers based off the interests of operatives and capabilities of the server infrastructure
• Maintain an intuitive and equal access to game servers for all operatives
• Coordinate with the CHRO to enforce and produce relevant rules
• Ensure utmost quality of games through operation of the server infrastructure

When on LOA, the CGO's responsibilities are inherited by the highest available CxO listed on this board. Usually, their responsibilities are inherited by the CEO.

Also known as LEADCERT.

Also known as MEDCERT.

Also known as LOGICERT.

Also known as CAVCERT.

Also known as CSS.