Prophet Handbook

All Staff

While we are split into three roles, it is important to remember that we are one team of staff. Communication is vital between us and therefore all staff are required to keep up to date on the appropriate channels on our Staff Discord server. Each role in the staff team is vital to the continued growth and development of the site and no one role is more important than another. Reviewing threads, approving CSes and answering questions in the Q & A forum are responsibilities held by all staff.

All staff are able to apply for further responsibilities should they choose to and / or might be asked to consider taking something on by their TL. These responsibilities are purely at your discretion and you can always say no! However, they come with the expectation that you will commit to handling and/or finishing them. If you’re not able to, then after a maximum of a month’s time, your duties will be evaluated by your Team Lead.

All staff teams have two ranks plus a Team Lead. The ranks are "Apprentice Staff" or "Staff". Apprentice Staff have less responsibilities as they are learning their role. Team leads are voted in by the whole staff following whole staff nominations. Their roles will be reviewed and a re-nomination/ vote will be held once a year.

• Apprentice Staff: All Teams - Responsibilities include: Reviewing Threads, Reviewing CSes, Keeping Up To Date, Viewing the PSF, Maintaining own activity tracker / project load.
• Staff: All Teams - Responsibilities include: Reviewing Threads, Reviewing CSes, Keeping Up To Date, Answering Tickets in the PSF (after approval / training), , Maintaining own activity tracker / project load.
• Team Leads: All Teams - Responsibilities include: Reviewing Threads, Reviewing CSes, Keeping Up To Date, Answering Tickets in the PSF, , Maintaining own activity tracker / project load Maintaining Team Communication, Focusing Team Priorities, Overview of team activity tracker / project load , Staff v staff conflict management.

Please note the minimum activity expectations for staff are listed in the Staff Application Form. These are tracked in the activity tracker staff use to avoid duplication of work etc. All staff must make sure this is kept up to date with their part of it.

Storytellers

A Storyteller's main focus is on what the name suggestions: the story. These moderators mostly handle city moderation and structure, building and updating lore, calendars, locations, approving jobs and wage requests, approving city development requests and sponsoring, planning, and completing moderated threads. They review threads, plan and lead global plotlines, participate in Immortal meetups with characters, and organize city events. Another responsibility of a Storyteller is to maintain player interest.

Below are the Storyteller ranks. Please keep in mind that the duties listed below for your rank come second to your character and first to any cross role participation. That means if you have a modded thread that’s waiting for your reply while you’re also developing a blessing with another person, the modded thread comes first.

If you have a question about something not listed in the below information, please contact your Storyteller Team Lead.

• Apprentice Staff: Storyteller - All new STs are assigned a mentor. Their responsibilities will be discussed and negotiated with their mentor and so will be individual in nature.
• Staff: Storyteller - Responsibilities include: Mentoring Apprentice Staff, city moderation / oversight, regional and global plotting. Also overseeing aspects of the CTW and Q &A forums. Driving the story forward and providing our players with a great experience.
• Team Lead: Storyteller - Additional Responsibilities include: Overseeing regional and global plotting, identifying team focus, goal setting etc.

Developers

Developers are tasked with creating, expanding and/or organizing information for world building purposes. These individuals are responsible for world development, building off of and creating meta-plots, developing history, skills, races, Immortals, blessings and curse, etc. Developers are the suppliers to Storyteller (and player) demand. They provide information for all characters to use within story and create goals for character advancements and achievements. Developers create the foundation for plot and work in tandem with Storytellers to ensure all the puzzle pieces mesh nicely.

Below are the Developer ranks. Please keep in mind that the duties listed below for your rank come second to your character and first to any cross role participation. That means if you have a blessing you’re working on and a player guide you’re writing up, the blessing comes first.

If you have a question about something not listed in the below information, please contact your Developer Team Lead.

• Apprentice Staff: Developer - All new Developers will be assigned a project to work on. Their responsibilities will be discussed and negotiated with their Team Lead at interview and will be individual in nature, depending on the project.
• Staff: Developer - Responsibilities include: Taking on larger Development projects, overseeing aspects of the CTW and Q &A forums. Supporting City Mods with Development pieces and providing feedback on Development projects.
• Team Lead: Developer - Additional Responsibilities include: Overseeing regional and global Development, identifying team focus, goal setting etc.

Lore Analysts

Standing Trials is a constantly growing, changing and evolving world. With the depth of lore and the complexity of Idalos' history, Lore Analysts are needed to ensure that everything is in line with everything else. Lore Analysts are tasked with reviewing existing Lore and ensuring that it is up to date and consistent with the meta-plot. The way they work is to consider and review a single aspect of Lore (eg: a race) and all associated Lore pieces (eg: their patron Immortal and that Immortal's Blessing). Lore Analysts identify, and fix, issues and inconsistencies and they also update. If a piece of Lore requires updating, Lore Analysts work with the Storytellers to implement that update in a plot; where there are gaps, they work with the Development Team to identify what needs to be written in order to make the Lore cohesive and fully usable for our players. The work we do requires a very broad knowledge of the site, it's Lore, history and rules; we work in groups and small teams in order to ensure that we catch as many details as possible.

Below are the Lore Analyst ranks. Please keep in mind that the duties listed below for your rank come second to your character and first to any cross role participation. That means if you have a blessing you’re working on and a working group for analysis of a particular article you're part of, the working group comes first.

If you have a question about something not listed in the below information, please contact your Lore Analysis Team Lead.

• Apprentice Staff: Lore Analyst - All new Lore Analysts will be assigned a mentor to work with and a role in an existing or new Analysis Project. Their responsibilities will be discussed and negotiated with their Team Lead at interview and will be individual in nature, depending on the project ongoing.
  
• Staff: Lore Analyst - Responsibilities include: Taking on mentor responsibilities, overseeing Analysis Projects. Supporting City Mods with Lore consistency and providing feedback on Development projects.
  
• Team Lead: Lore Analyst - Additional Responsibilities include: Overseeing all working groups and Analysis Projects, identifying team focus, goal setting etc.

A Note On The Winged Horse:

Pegasus has responsibility for the site, in so far as she pays for hosting and tech support. She has equal access to the ACP and site as the two other team leads and those who have agreed to bug test new extensions / code on the Development site. That means that, there are times when Peg will make a decision about site maintenance or upkeep, about extensions or wiki formatting etc. She does not and will not ever have control over policy decisions on how we run the site, nor does her vote count as more. There may be times when she says "nope, we can't do this because..." but the because will be for technical / admin reasons. In terms of the site and it's vision, Peg is a staff member and all the rules apply to her the same as every other staffer. There is no single person "in charge".

Peg also has sole access to the Paypal account. Because it's linked to her bank account. She will post up a "current balance" once a month in the staff Lounge to make sure that staff know how much we have - and that can be a thread where suggestions for how we spend it (don't get excited, really...) happen.

If it should happen that Peg simply ups and disappears, then the site has been paid for three months in advance, as has tech support. Tech guy has the Paypal account details.