These are votes of confidence. If you are unfamiliar or on the fence about someone, vote NO or don't vote at all. Only vote yes if the candidate has your confidence and you genuinely feel that they are ready for mod tool access.

Previous discussion here.

This is an open vote for operational staff and above.

Candidate:	radian628
Captain/Admin:	aismallard and stormbreath
Why:	Mod tools are needed due to the nature the Technical Team's work, which frequently involves making maintenance edits to various pages across the site (which may be locked), system pages, components, and themes, all of which limit who can edit them. Additionally, Radian is developing tools to automate several routine tasks which include editing file attachments on existing pages.

Candidate:	wackdog
Captain/Admin:	aismallard and stormbreath
Why:	Mod tools are needed due to the nature the Technical Team's work, which frequently involves making maintenance edits to various pages across the site (which may be locked), system pages, components, and themes, all of which limit who can edit them. Additionally, wackdog and HaydenSaintPascal are leading an accessibility audit across our site.

Candidate:	HaydenSaintPascal
Captain/Admin:	aismallard and stormbreath
Why:	Mod tools are needed due to the nature the Technical Team's work, which frequently involves making maintenance edits to various pages across the site (which may be locked), system pages, components, and themes, all of which limit who can edit them. Additionally, wackdog and HaydenSaintPascal are leading an accessibility audit across our site.

Candidate:	Dino--Draws
Captain/Admin:	Uncle Nicolini (deletions subteam VC) / Deadly Bread (MAST captain)
Why:	Dino--Draws has consistently proven firself to be a useful member of deletions and upon speaking with fir, fi has shown interest in taking on the deleter more fully.

Vote YES or NO. Per the proposal, only yes and no votes will be counted.

The promotion vote will end in:

||~ **Candidate** ||~ YES ||~ NO || || [[*user radian628]] || X || X || || [[*user wackdog]] || X || X || || [[*user HaydenSaintPascal]] || X || X || || [[*user Dino--Draws]] || X || X ||

radian628

wackdog

HaydenSaintPascal

Dino--Draws

For radian628, wackdog, and HaydenSaintPascal:

All three are trusted members of the Technical Team, who, due to the nature of our team's work, frequently involves making maintenance edits to various pages across the site (which may be locked), as well as system pages, components, and themes, all of which limit who can edit them.

In particular, wackdog and HaydenSaintPascal are leading an accessibility audit across our site, an active effort that involves analyzing and proposing edits to a large number of these pages, which presently requires significant latency due to continually needing to request pages to be unlocked or edits made on their behalf.

As such, stormbreath and I feel that the users gaining access to Mod Tools is both positive for the site and necessary.

For Dino--Draws:

Dino--Draws has consistently proven firself to be a useful member of deletions and upon speaking with fir, fi has shown interest in taking on the deleter more fully. As of right now, its mostly been just Nico and Kufat with neb occasionally pitching in but dino is really consistent and we cold use fir help. Having mod tools would facilitate that.

If you have anything to say about these users getting Mod Tools, be it positive, negative, or something in between, please let it be known in this thread.

Discussion will go on for one week.

See Promotions-Policy for how promotions are to be handled. And see the Candidate Discussions on the main-site thread and 05 thread for more information about candidates.

These are votes of confidence. If you are unfamiliar or on the fence about someone, vote NO or Abstain. Only vote yes if the candidate has your confidence and you genuinely feel that they are ready for promotion.

Please post even if you are abstaining from voting. Staff may abstain from voting on any individual votes.

This promotion vote will end in:

Operational Staff Candidates:

Below is a group of suggestions regarding Junior Staff who Team Captains have nominated to be voted upwards to Operational Staff. Please read the commentary provided in order to help your judgement regarding these staff.

Junior Staff Member:	HaydenSaintPascal
Captain/Team:	Tech (aismallard / stormbreath)
Why:	HaydenSaintPascal has been an fantastic addition to the Technical Team. Since joining, they have been helpful as a theme reviewer, has brought valuable contributions to team and technical policy discussions, and is co-leading an accessibility initiative on the site along with wackdog. We do not have any reservations about their promotion to operational staff.
Optional areas of improvement:	N/A

Junior Staff Member:	wackdog
Captain/Team:	Tech (aismallard / stormbreath)
Why:	wackdog has been an extraordinary addition to Tech. He has contributed to tech policy work and discussions, theme reviews, and has been co-leading a valuable accessibility initiative alongside HaydenSaintaPascal. We do not have any reservations about his promotion to operational staff.
Optional areas of improvement:	N/A

Junior Staff Member:	AstralNavigator
Captain/Team:	Discord Crit (AstersQuill/Queerious)
Why:	AstralNavigator has been an active and productive member in both moderation and process work. He recently took the initiative to rewrite the writing channel rules for clarity, and drove the process through to completion. He has a good head for issues of moderation and policy, and acts with the level of confidence and care we look for in all Discord Critique members. When asked to self-reflect on why he should be promoted, Astral responded as such: "I think I've found my footing in my staff role to the point where I am able to take initiative and contribute in ways beyond just "clocking in" and doing the usual assigned tasks only, such as with the rules rewrite."
Optional areas of improvement:	We asked AstralNavigator where he could improve as an OS, and he noted wanting to be involved more in general staff matters.

Junior Staff Member:	wackdog
Captain/Team:	Discord Crit (AstersQuill/Queerious)
Why:	Wackdog, though a more recent addition to our roster, has proved himself to be competent and committed in moderation. This is best shown with his frequent contributions in spotting and reporting AI-generated works. When asked to self-reflect on why he should be promoted, Wackdog responded with: " Since joining critique I have made an active effort to integrate into the team and handle the day to day duties of critique staff to the best of my ability. I feel as though I have done a good job maintaining the respective topics and encouraging supportive culture of the Deer College channels. I have also made sure to keep on top of certain aspects of critique that get overlooked: such as mirroring sitebans as crit kicks and so on."
Optional areas of improvement:	We asked Wackdog where he could improve as an OS, and he responded with: "Something I can think of improving on is being slightly more decisive during staff discussions. A couple times I have found myself saying "I'm easy" during a discussion on what action to take. While it is fine to do this, I feel there might be times where it is better for me to make sure I pick a definitive side for a clearer consensus."

Junior Staff Member:	battlecruiser12
Captain/Team:	Licensing (Naepic)
Why:	Battlecruiser has been actively and quietly working her way through the Sisyphean task that is checking licenseboxes and adding the tag. She is working with the same initiative that led to Elenee successfully finishing a similar initiative a few years ago, and in due time, she and her fellow licenseheads will overcome. She knows how to pace herself well; if an article has an overwhelming number of images or otherwise requires extra work, battlecruiser will act accordingly and limit herself. Moreover, promoting her would potentially grant her access to mod tools, something she will need in future as she stumbles into more images that need replacement. Battlecruiser has been diligently working at this for half a year now, taking breaks when needed, and I think its time for a promotion. —Nico
Optional areas of improvement:	I asked battlecruiser to tell me what she views as her own areas of improvement as an OS and this is what she said: "I believe my greatest shortcoming as a member of staff is that I struggle with self-discipline. I will often end up taking breaks of a couple of days from making license boxes without really intending to because I become distracted by other things, which is something I will really need to work on if I'm going to be promoted to operational staff, and potentially being trusted with mod tools later down the line." Personally, I think that as previously mentioned, battlecruiser is merely pacing herself well. I think she has an excellent head on her shoulders and is able to keep herself from burnout— a very important skill to have as staff.

Junior Staff Member:	MetalRavioli
Captain/Team:	Community Outreach (Naepic)
Why:	Ravioli is dependable, diligent, kind, and intelligent— all good traits I think staffers should have. She, alongside another user who has unfortunately not been with us long enough to promote, have been key in revitalizing the Data Analysis team, which has oft languished in the past. That aside, Ravioli has been a key player in Site News team for her entire tenure on staff, helping to get it pushed out on time efficiently. —Nico
Optional areas of improvement:	I asked Ravioli to tell me what she views as her own areas of improvement as an OS and this is what she said: "I definitely feel my biggest weakness as a staffer is procrastination. I’ve procrastinated on staff tasks before, (eg. the Site News page features) which can stress me out when I have to get it all done at the last minute." Personally, I think that Ravioli does a good enough job of keeping herself on task. The only instance of which we have had an issue relating to news being late was January 2026, but that was not Ravioli's fault, or anyone's, really, we were just doing something new that took time to execute correctly.

Junior Staff Member:	Sinking_Otter
Captain/Team:	Community Outreach (Naepic)
Why:	Otter is an unstoppable force. Managing the Facebook and Instagram almost singlehandedly and fielding constant promotional posts where I am unable, she has proven herself incredibly diligent as well as intelligent and capable when it comes to general IO policy. I am proud to call her a member of my staff and see a very bright future for her on this team. —Prom
Optional areas of improvement:	I asked Otter if she felt she had any shortcomings as it relates to staff or areas she felt she could/should improve. This is what she has to say: "In terms of shortcomings, I do realise that I have a very formal and I would say corporate approach to how I communicate which isn’t always ideal given social media often demands a more informal approach. I also recognise that while I communicate frequently with off-site, I don’t reach out to the on-site community as much. I’d like to fix that as I believe in my position being immersed in both communities is key. When it comes to staff specifically, I recognise I'm not as involved as other junior staff as I prefer to hold back unless I feel I can benefit a discussion by contributing. I'd like to jump in more or potentially get involved with other teams so that I might contribute more." I agree with Otter's assessment regarding her relative lack of on-site presence, but I believe she is more than capable of remedying this easily. I would like to see her participate in policy discussions among other staff, as she is excellent at it with respect to IO-focused matters. Regarding communication styles and formality, I appreciate her sense of conversation and attitude, as while it differs from my natural demeanor and that of other IO members to some degree, I feel a diversity of personality is valuable in any group that expects to reach people. Otter is a very strong organizing force that helps me keep things on track.

Vote YES or NO. Someone who you are ambivalent to should not receive your vote of confidence for staff, thus abstain or no. If you don't know who someone is, then I invite you to educate yourself and get to know their work before voting.

||~ Operational Staff Candidate||~ YES||~ NO|| ||[[*user HaydenSaintPascal]]|| X || X || ||[[*user wackdog]]|| X || X || ||[[*user AstralNavigator]]|| X || X || ||[[*user battlecruiser12]]|| X || X || ||[[*user MetalRavioli]]|| X || X || ||[[*user Sinking_Otter]]|| X || X ||

Per the Mod Tools Policy all Captains must decide to Renew or Remove the Mod Tools of their team members during the Winter Promotion cycle. Below are the lists of those with mod tools corresponding to whether or not their Captain opted to have them keep their mod tools.

Per the Policy, Captains will have until the conclusion of the Winter Promotion cycle to list any corrections in this thread.

This thread is open to Captains and Vice Captains.

Mod Tools Renewals:

The following members of staff have had their names put forward to have their mod tools renewed.

Staff Member	Teams Renewing
Aftokrator	MAST, Curations
Deadly Bread	MAST
DrRevan	Forum Crit
Erminustay	Licensing
Esperion	MAST, Curations
EstrellaYoshte	Tech, MAST
JackalRelated	MAST, Curations
Jerden	MAST, Curations
Naepic	Licensing
NebulousStar	MAST, Licensing
OriTiefling	Forum Crit
Riemann	Licensing, Curations
VapidPoem	Curations
Woedenaz	Tech

Mod Tools Removals:

The following members of staff have not had their names put forward to have their mod tools renewed, or requested for them to not be renewed.

Staff Member
AstersQuill

Mainsite Mirror

See Promotions-Policy for how promotions are to be handled.

This discussion is open to all users. Please feel free to leave your thoughts. This is NOT a voting post.

Rules and Decorum:

This thread exists to allow commentary and criticism on candidates as candidates. All comments should be addressing one of the following:

• Concern or support for a candidate's ability to perform their duties after promotion.
• Concern or support for a candidate's character only in so far as it will affect their ability to perform their duties or their standing as staff.

What is not allowed in this thread:

• General complaints that you don't like a candidate for reasons that would not effect their ability to perform their duties.
• Comments that contain neither concern nor support for any candidate. A totally neutral stance does not need commented.
• Vehemence, rudeness, and incivility. While this is a place to post concerns, it is not a place to attack candidates.

Replies to comments are allowed but not required. Any user may respond to any concerns or support, including the candidate in question. All of the same rules apply to replies.

Staff will be monitoring this thread and will issue orders to stop discussion only if they have passed into unproductive vehemence. Staff will remove any comments that are extremely rule-breaking.

This discussion will be open for two weeks. After which time it will move to a staff vote.

Operational Staff Candidates:

Below is a group of suggestions regarding Junior Staff who Team Captains have nominated to be voted upwards to Operational Staff. Please read the commentary provided in order to help your judgement regarding these staff.

Junior Staff Member:	HaydenSaintPascal
Captain/Team:	Tech (aismallard / stormbreath)
Why:	HaydenSaintPascal has been an fantastic addition to the Technical Team. Since joining, they have been helpful as a theme reviewer, has brought valuable contributions to team and technical policy discussions, and is co-leading an accessibility initiative on the site along with wackdog. We do not have any reservations about their promotion to operational staff.
Optional areas of improvement:	N/A

Junior Staff Member:	wackdog
Captain/Team:	Tech (aismallard / stormbreath)
Why:	wackdog has been an extraordinary addition to Tech. He has contributed to tech policy work and discussions, theme reviews, and has been co-leading a valuable accessibility initiative alongside HaydenSaintaPascal. We do not have any reservations about his promotion to operational staff.
Optional areas of improvement:	N/A

Junior Staff Member:	AstralNavigator
Captain/Team:	Discord Crit (AstersQuill/Queerious)
Why:	AstralNavigator has been an active and productive member in both moderation and process work. He recently took the initiative to rewrite the writing channel rules for clarity, and drove the process through to completion. He has a good head for issues of moderation and policy, and acts with the level of confidence and care we look for in all Discord Critique members. When asked to self-reflect on why he should be promoted, Astral responded as such: "I think I've found my footing in my staff role to the point where I am able to take initiative and contribute in ways beyond just "clocking in" and doing the usual assigned tasks only, such as with the rules rewrite."
Optional areas of improvement:	We asked AstralNavigator where he could improve as an OS, and he noted wanting to be involved more in general staff matters.

Junior Staff Member:	wackdog
Captain/Team:	Discord Crit (AstersQuill/Queerious)
Why:	Wackdog, though a more recent addition to our roster, has proved himself to be competent and committed in moderation. This is best shown with his frequent contributions in spotting and reporting AI-generated works. When asked to self-reflect on why he should be promoted, Wackdog responded with: " Since joining critique I have made an active effort to integrate into the team and handle the day to day duties of critique staff to the best of my ability. I feel as though I have done a good job maintaining the respective topics and encouraging supportive culture of the Deer College channels. I have also made sure to keep on top of certain aspects of critique that get overlooked: such as mirroring sitebans as crit kicks and so on."
Optional areas of improvement:	We asked Wackdog where he could improve as an OS, and he responded with: "Something I can think of improving on is being slightly more decisive during staff discussions. A couple times I have found myself saying "I'm easy" during a discussion on what action to take. While it is fine to do this, I feel there might be times where it is better for me to make sure I pick a definitive side for a clearer consensus."

Junior Staff Member:	battlecruiser12
Captain/Team:	Licensing (Naepic)
Why:	Battlecruiser has been actively and quietly working her way through the Sisyphean task that is checking licenseboxes and adding the tag. She is working with the same initiative that led to Elenee successfully finishing a similar initiative a few years ago, and in due time, she and her fellow licenseheads will overcome. She knows how to pace herself well; if an article has an overwhelming number of images or otherwise requires extra work, battlecruiser will act accordingly and limit herself. Moreover, promoting her would potentially grant her access to mod tools, something she will need in future as she stumbles into more images that need replacement. Battlecruiser has been diligently working at this for half a year now, taking breaks when needed, and I think its time for a promotion. —Nico
Optional areas of improvement:	I asked battlecruiser to tell me what she views as her own areas of improvement as an OS and this is what she said: "I believe my greatest shortcoming as a member of staff is that I struggle with self-discipline. I will often end up taking breaks of a couple of days from making license boxes without really intending to because I become distracted by other things, which is something I will really need to work on if I'm going to be promoted to operational staff, and potentially being trusted with mod tools later down the line." Personally, I think that as previously mentioned, battlecruiser is merely pacing herself well. I think she has an excellent head on her shoulders and is able to keep herself from burnout— a very important skill to have as staff.

Junior Staff Member:	MetalRavioli
Captain/Team:	Community Outreach (Naepic)
Why:	Ravioli is dependable, diligent, kind, and intelligent— all good traits I think staffers should have. She, alongside another user who has unfortunately not been with us long enough to promote, have been key in revitalizing the Data Analysis team, which has oft languished in the past. That aside, Ravioli has been a key player in Site News team for her entire tenure on staff, helping to get it pushed out on time efficiently. —Nico
Optional areas of improvement:	I asked Ravioli to tell me what she views as her own areas of improvement as an OS and this is what she said: "I definitely feel my biggest weakness as a staffer is procrastination. I’ve procrastinated on staff tasks before, (eg. the Site News page features) which can stress me out when I have to get it all done at the last minute." Personally, I think that Ravioli does a good enough job of keeping herself on task. The only instance of which we have had an issue relating to news being late was January 2026, but that was not Ravioli's fault, or anyone's, really, we were just doing something new that took time to execute correctly.

Junior Staff Member:	Sinking_Otter
Captain/Team:	Community Outreach (Naepic)
Why:	Otter is an unstoppable force. Managing the Facebook and Instagram almost singlehandedly and fielding constant promotional posts where I am unable, she has proven herself incredibly diligent as well as intelligent and capable when it comes to general IO policy. I am proud to call her a member of my staff and see a very bright future for her on this team. —Prom
Optional areas of improvement:	I asked Otter if she felt she had any shortcomings as it relates to staff or areas she felt she could/should improve. This is what she has to say: "In terms of shortcomings, I do realise that I have a very formal and I would say corporate approach to how I communicate which isn’t always ideal given social media often demands a more informal approach. I also recognise that while I communicate frequently with off-site, I don’t reach out to the on-site community as much. I’d like to fix that as I believe in my position being immersed in both communities is key. When it comes to staff specifically, I recognise I'm not as involved as other junior staff as I prefer to hold back unless I feel I can benefit a discussion by contributing. I'd like to jump in more or potentially get involved with other teams so that I might contribute more." I agree with Otter's assessment regarding her relative lack of on-site presence, but I believe she is more than capable of remedying this easily. I would like to see her participate in policy discussions among other staff, as she is excellent at it with respect to IO-focused matters. Regarding communication styles and formality, I appreciate her sense of conversation and attitude, as while it differs from my natural demeanor and that of other IO members to some degree, I feel a diversity of personality is valuable in any group that expects to reach people. Otter is a very strong organizing force that helps me keep things on track.

These are votes of confidence. If you are unfamiliar or on the fence about someone, vote NO or don't vote at all. Only vote yes if the candidate has your confidence and you genuinely feel that they are ready for mod tool access.

Previous discussion here.

This is an open vote for operational staff and above.

Candidate:	Elenee FishTruck
Captain/Admin:	Naepic
Why:	Elenee is being nominated for mod tools, through Licensing as a part of her duties with the Licensebox Team. This team requires constant editing access to locked pages as well as the ability to upload images to pages that she is not the OP for. Elenee is among the most trusted members of senior staff, though she is someone a lot of the newer staffers might not recognize since she has been gone a few years. However, in order to carry out this daunting task, she needs mod Tools. So let's grant them to her.

Vote YES or NO. Per the proposal, only yes and no votes will be counted.

The promotion vote will end in:

||~ **Candidate** ||~ YES ||~ NO || || [[*user Elenee Fishtruck]] || X || X ||

See Promotions-Policy for how promotions are to be handled. And see the Candidate Discussions on the main-site thread and 05 thread for more information about candidates.

These are votes of confidence. If you are unfamiliar or on the fence about someone, vote NO or Abstain. Only vote yes if the candidate has your confidence and you genuinely feel that they are ready for promotion.

Please post even if you are abstaining from voting. Staff may abstain from voting on any individual votes.

This promotion vote will end in:

Operational Staff Candidates:

Below is a group of suggestions regarding Junior Staff who Team Captains have nominated to be voted upwards to Operational Staff. Please read the commentary provided in order to help your judgement regarding these staff.

Junior Staff Member:	radian628
Captain/Team:	Tech (aismallard / stormbreath)
Why:	radian628 is a newcomer to staff but in that short time has made a huge impact on the Technical Team. They have been reliably helpful and observant, noting areas of improvement in terms of site tooling and technology, improving staff workflows, site appearance and usability, and analyzing Wikidot features and complications. Despite being very insightful and offering useful suggestions to match, they understand the need for staff communication and accountability. In a manner befitting a junior staffer, they also have brought up suggestions for discussion prior to implementing them, ensured they had captain sign-off before big actions, and talk with staff outside Tech for things that affect the whole site. While the shortness of their time on staff so far is something to be aware of, their conduct during that time has given the Technical Team captains confidence that they can be an effective operational staffer.
Optional areas of improvement:	N/A

Junior Staff Member:	Rhineriver
Captain/Team:	Community Outreach (Naepic)
Why:	Rhine has been dutifully putting its nose to the proverbial grindstone on Site News for about a year now, consistently doing a good job and structuring the monthly releases. It has a good attitude, its friendly, and it is a delight to have around on the team. Despite what it says is its biggest weakness below, it has yet to not come through for Site News throughout its tenure on the team. —Nico
Optional areas of improvement:	I asked Rhine to tell me what it views as its own areas of improvement as an OS and this is what it said: "I could definitely improve on my time management. It hasn’t caused any real problems with me just doing new content for now and I will definitely pay harder attention as opstaff but I have been pretty late to start my news work in general." Personally, I think that Rhine's biggest weakness is its lack of involvement in other staff affairs, especially considering how it yet to fail to meet a deadline, but far be it from me to tell people they're not lacking where they think they are. That being said, Rhine has said in the Site News chat when it starts working on its duties, and its usually near the end of the month. This isn't inherently a bad thing, I usually put it off to the last minute myself when I was in charge of it myself, especially due to the nature of the job, but doing it all correctly on short notice is difficult. All this to say, I would like to see Rhine be more involved in other staff matters more than I would like for it to be more timely.

Junior Staff Member:	ProblemPal
Captain/Team:	Community Outreach (Naepic)
Why:	PP has taken on the role of a Site News correspondent handily, writing monthly news stories as well as managing the Monthly Writing Prompts she inherited from ParallelPotatoes before him. She has a good eye for detail and has helped keep Site News on track for the past months since his joining the team. PP also has a great ability to interface with the community, as she does this frequently on the official Discord's #writing-events channel whenever he publishes a new Writing Prompt and frequently asks for more. All in all, PP is an excellent candidate for OS in my opinion. — Nico
Optional areas of improvement:	I asked PP to tell me what she views as her own areas of improvement as an OS and this is what he said: "My staff weakness is keeping up with general staff affairs." Personally, I think PP could afford to be a little more invested in staff affairs, especially if we are considering promoting her to OS, but I also think he is very good at his current role of interfacing with the community. As long as she is kept up to date with what's going on with staff and makes an effort to become more involved, I don't see a reason why she shouldn't be promoted, especially considering his good work.

Junior Staff Member:	ProblemPal
Captain/Team:	Discord Crit (AstersQuill/Queerious)
Why:	ProblemPal has been an effective and active member of the crit team since they have arrived, both in issues of moderation and generally being a helpful member of chat. ProblemPal helps cover the "Night Shift" of Deer College, where much of the team is either asleep or elsewhere, and it has been nothing but smooth sailing. During moderation talks, ProblemPal is level-headed, and taking the necessary time to collect his thoughts before coming to a decision.
Optional areas of improvement:	I asked ProblemPal for her thoughts on where she thinks she will improve as an OS. They noted wanting to work on self-assuredness, both in cases of policy and difficult cases of moderation, making sure they are confident in the decisions they are making or the opinions they are expressing.

Junior Staff Member:	Dino--Draws
Captain/Team:	MAST (Deadly Bread)
Why:	Dino has been providing consistently quality work throughout fir time on MAST, both in terms of activity and attitude. Fi understands the qualities of a good tagger, and maintains that quality throughout work and fir interactions with staff. Dino has also been a positive force in staff discussions both within and outside of MAST, and has pitched in whenever possible with the same high-quality work fi brings to tagging. Recently Dino had taken a slight break from tagging due to life busyness, but has immediately jumped back into tagging with posting opening for the 9000 Contest, and if anything shows that fi understands the need to balance staff work and other responsibilities to avoid burnout, a problem all too common to the Tagging Team.
Optional areas of improvement:	N/A

Junior Staff Member:	Fishish
Captain/Team:	Discord (AriadnesThread)
Why:	Fishish has been a consistently active moderator, quick to act in ongoing situations, especially when it comes to trolls, and is engaged with the community both on site and on discord. We've had him on the team on and off a few times, and these have been consistent traits we are happy to have. Since returning to the team, he has shown diligence and transparency in his staffwork and we fully expect this to continue.
Optional areas of improvement:	N/A

Vote YES or NO. Someone who you are ambivalent to should not receive your vote of confidence for staff, thus abstain or no. If you don't know who someone is, then I invite you to educate yourself and get to know their work before voting.

||~ Operational Staff Candidate||~ YES||~ NO|| ||[[*user radian628]]|| X || X || ||[[*user Rhineriver]]|| X || X || ||[[*user ProblemPal]]|| X || X || ||[[*user Dino--Draws]]|| X || X || ||[[*user Fishish]]|| X || X ||

Elenee FishTruck

In her staff duties within licensing, Elenee is a member of licenseboxing team, which often requires mod tools to edit locked articles and localize images. With Mod Tools at her disposal, Elenee will be unimpeded in her duties and won't have to slow down to ask permission for pages to be unlocked. It should also be noted that Elenee was the former lead of licensing and is a highly trusted individual by both myself and Naepic.

Please voice any questions, comments, or concerns you have over Elenee gaining Mod Tools. Discussion will last one week.

Mainsite Mirror

See Promotions-Policy for how promotions are to be handled.

This discussion is open to all users. Please feel free to leave your thoughts. This is NOT a voting post.

Rules and Decorum:

This thread exists to allow commentary and criticism on candidates as candidates. All comments should be addressing one of the following:

• Concern or support for a candidate's ability to perform their duties after promotion.
• Concern or support for a candidate's character only in so far as it will affect their ability to perform their duties or their standing as staff.

What is not allowed in this thread:

• General complaints that you don't like a candidate for reasons that would not effect their ability to perform their duties.
• Comments that contain neither concern nor support for any candidate. A totally neutral stance does not need commented.
• Vehemence, rudeness, and incivility. While this is a place to post concerns, it is not a place to attack candidates.

Replies to comments are allowed but not required. Any user may respond to any concerns or support, including the candidate in question. All of the same rules apply to replies.

Staff will be monitoring this thread and will issue orders to stop discussion only if they have passed into unproductive vehemence. Staff will remove any comments that are extremely rule-breaking.

This discussion will be open for two weeks. After which time it will move to a staff vote.

Operational Staff Candidates:

Below is a group of suggestions regarding Junior Staff who Team Captains have nominated to be voted upwards to Operational Staff. Please read the commentary provided in order to help your judgement regarding these staff.

Junior Staff Member:	radian628
Captain/Team:	Tech (aismallard / stormbreath)
Why:	radian628 is a newcomer to staff but in that short time has made a huge impact on the Technical Team. They have been reliably helpful and observant, noting areas of improvement in terms of site tooling and technology, improving staff workflows, site appearance and usability, and analyzing Wikidot features and complications. Despite being very insightful and offering useful suggestions to match, they understand the need for staff communication and accountability. In a manner befitting a junior staffer, they also have brought up suggestions for discussion prior to implementing them, ensured they had captain sign-off before big actions, and talk with staff outside Tech for things that affect the whole site. While the shortness of their time on staff so far is something to be aware of, their conduct during that time has given the Technical Team captains confidence that they can be an effective operational staffer.
Optional areas of improvement:	N/A

Junior Staff Member:	Rhineriver
Captain/Team:	Community Outreach (Naepic)
Why:	Rhine has been dutifully putting its nose to the proverbial grindstone on Site News for about a year now, consistently doing a good job and structuring the monthly releases. It has a good attitude, its friendly, and it is a delight to have around on the team. Despite what it says is its biggest weakness below, it has yet to not come through for Site News throughout its tenure on the team. —Nico
Optional areas of improvement:	I asked Rhine to tell me what it views as its own areas of improvement as an OS and this is what it said: "I could definitely improve on my time management. It hasn’t caused any real problems with me just doing new content for now and I will definitely pay harder attention as opstaff but I have been pretty late to start my news work in general." Personally, I think that Rhine's biggest weakness is its lack of involvement in other staff affairs, especially considering how it yet to fail to meet a deadline, but far be it from me to tell people they're not lacking where they think they are. That being said, Rhine has said in the Site News chat when it starts working on its duties, and its usually near the end of the month. This isn't inherently a bad thing, I usually put it off to the last minute myself when I was in charge of it myself, especially due to the nature of the job, but doing it all correctly on short notice is difficult. All this to say, I would like to see Rhine be more involved in other staff matters more than I would like for it to be more timely.

Junior Staff Member:	ProblemPal
Captain/Team:	Community Outreach (Naepic)
Why:	PP has taken on the role of a Site News correspondent handily, writing monthly news stories as well as managing the Monthly Writing Prompts she inherited from ParallelPotatoes before him. She has a good eye for detail and has helped keep Site News on track for the past months since his joining the team. PP also has a great ability to interface with the community, as she does this frequently on the official Discord's #writing-events channel whenever he publishes a new Writing Prompt and frequently asks for more. All in all, PP is an excellent candidate for OS in my opinion. — Nico
Optional areas of improvement:	I asked PP to tell me what she views as her own areas of improvement as an OS and this is what he said: "My staff weakness is keeping up with general staff affairs." Personally, I think PP could afford to be a little more invested in staff affairs, especially if we are considering promoting her to OS, but I also think he is very good at his current role of interfacing with the community. As long as she is kept up to date with what's going on with staff and makes an effort to become more involved, I don't see a reason why she shouldn't be promoted, especially considering his good work.

Junior Staff Member:	ProblemPal
Captain/Team:	Discord Crit (AstersQuill/Queerious)
Why:	ProblemPal has been an effective and active member of the crit team since they have arrived, both in issues of moderation and generally being a helpful member of chat. ProblemPal helps cover the "Night Shift" of Deer College, where much of the team is either asleep or elsewhere, and it has been nothing but smooth sailing. During moderation talks, ProblemPal is level-headed, and taking the necessary time to collect his thoughts before coming to a decision.
Optional areas of improvement:	I asked ProblemPal for her thoughts on where she thinks she will improve as an OS. They noted wanting to work on self-assuredness, both in cases of policy and difficult cases of moderation, making sure they are confident in the decisions they are making or the opinions they are expressing.

Junior Staff Member:	Dino--Draws
Captain/Team:	MAST (Deadly Bread)
Why:	Dino has been providing consistently quality work throughout fir time on MAST, both in terms of activity and attitude. Fi understands the qualities of a good tagger, and maintains that quality throughout work and fir interactions with staff. Dino has also been a positive force in staff discussions both within and outside of MAST, and has pitched in whenever possible with the same high-quality work fi brings to tagging. Recently Dino had taken a slight break from tagging due to life busyness, but has immediately jumped back into tagging with posting opening for the 9000 Contest, and if anything shows that fi understands the need to balance staff work and other responsibilities to avoid burnout, a problem all too common to the Tagging Team.
Optional areas of improvement:	N/A

Junior Staff Member:	Fishish
Captain/Team:	Discord (AriadnesThread)
Why:	Fishish has been a consistently active moderator, quick to act in ongoing situations, especially when it comes to trolls, and is engaged with the community both on site and on discord. We've had him on the team on and off a few times, and these have been consistent traits we are happy to have. Since returning to the team, he has shown diligence and transparency in his staffwork and we fully expect this to continue.
Optional areas of improvement:	N/A

These are votes of confidence. If you are unfamiliar or on the fence about someone, vote NO or don't vote at all. Only vote yes if the candidate has your confidence and you genuinely feel that they are ready for mod tool access.

Previous discussion here.

This is an open vote for operational staff and above.

Candidate:	VapidPoem
Captain/Admin:	Riemann
Why:	Vapid is being nominated for mod tools, through Curations as a part of her duties with the Rewrite and Anonymous Articles Posting teams. These teams require constant editing access to the metadata pages as well as the ability to move pages in and out of the unlisted: category. Vapid is among the most enthusiastic about fulfilling their duties among both these teams, and in order to fully be able to do her job, she needs mod Tools. So let's grant them to her.

Vote YES or NO. Per the proposal, only yes and no votes will be counted.

The promotion vote will end in:

||~ **Candidate** ||~ YES ||~ NO || || [[*user VapidPoem]] || X || X ||

VapidPoem

In her staff duties within Curations, Vapid is a member of both Rewrite and Anonymous Articles posting, both of which require mod tools to move articles to different slots/categories, as well as change metadata attribution. With Mod Tools at her disposal, Vapid will more easily be able to complete her duties as a member of staff.

Please voice any questions, comments, or concerns you have over Vapid gaining Mod Tools. Discussion will last one week.

See Promotions-Policy for how promotions are to be handled. And see the Candidate Discussions on the main-site thread and 05 thread for more information about candidates.

These are votes of confidence. If you are unfamiliar or on the fence about someone, vote NO or Abstain. Only vote yes if the candidate has your confidence and you genuinely feel that they are ready for promotion.

Please post even if you are abstaining from voting. Staff may abstain from voting on any individual votes.

This promotion vote will end in:

Operational Staff Candidates:

Below is a group of suggestions regarding Junior Staff who Team Captains have nominated to be voted upwards to Operational Staff. Please read the commentary provided in order to help your judgement regarding these staff.

Junior Staff Member:	VapidPoem
Captain/Team:	Curations (Riemann)
Why:	Vapid has taken on the role of the Rewrite team workhorse, helping expedite a process that once took weeks or even months into one that only takes a few days, up to a week at worst nowadays. She shows a drive to help the articles improve, while still staying true to their original visions. It has also stepped up into the Anonymous Articles team, where she has helped post anonymous articles at a time when no one else was able to. Overall, Vapid has a great disposition and willingness to help, as well as take on work. I have no doubt she would make an excellent Opstaffer. —Nico
Optional areas of improvement:	I asked Vapid to tell me what she views as her own areas of improvement as an OS and this is what she said: "My biggest weakness is that I've only been staff for a few months. There is still plenty of stuff to learn - just the other day I was learning how to edit metadata for the first time. However I still definitely am working to improve and will most certainly ask questions if I am unsure about something or how to perform a task, as well as look over guides and resources provided to figure out how to do a task until I feel comfortable doing it." Personally, I think Vapid is comfortable asking questions and is willing to learn, so I am not worried about her not learning something quickly, and even if it does make a mistake, I am confident she will learn from it.

Junior Staff Member:	Strange Matter
Captain/Team:	Community Outreach (WhiteGuard/Naepic)
Why:	Strange Matter has been working quietly but diligently on Site News for some time now. He often writes stories which involve interviews, a very involved process that requires thinking of thoughtful questions to ask to users. His interviews have ranged from contest winners, contest runners, canon runners and GoI creators, and he is very good at asking thought-provoking questions. Strange Matter has proven himself reliable and consistently capable of producing stories, and I think it's time he is acknowledged. Plus with my current head of Site News retiring effective June 1st, I could use another hand on deck as a candidate for mod tools for posting the Site News. —Nico
Optional areas of improvement:	I asked Strange Matter to tell me what he views as his own areas of improvement as an OS and this is what he said: "Speaking solely as a Community Outreach staffer, I feel as though I could push further into the role. For instance, I would like to get in contact with artists or with people in other foreign branches of the site and do coverage with them." Personally, I do not doubt his capabilities as a Site News correspondent, but I would like to see him get a bit more involved in matters that aren't immediately related to his particular scope, as well as learn how the Site News posting process works.

Junior Staff Member:	sailorenoch
Captain/Team:	Community Outreach (WhiteGuard/Naepic)
Why:	Enoch is very proactive on the art committee, always having artists and artwork pieces to spotlight. They also have contributed art to Pridefest 2024 and 2025, and I generally trust them to do good. By promoting them, we can potentially run Enoch for Mod Tools, which would facilitate their role on the art committee. —Nico
Optional areas of improvement:	I asked Enoch to tell me what they view as their own areas of improvement as an OS and this is what they said: "I would like myself to build confidence in my decision-making. I recognize that I doubt my own judgement and seek approval for things I can handle myself. While communication is always good, I think I could take more initiative." Personally, I find myself agreeing with Enoch's self-assessment, but I am confident in their ability to grow into their new position as op-staff should they be promoted, as well as their ability to improve their self-confidence.

Junior Staff Member:	pr0m37h3um
Captain/Team:	Community Outreach (WhiteGuard/Naepic)
Why:	Prom is active on Bluesky and has managed the Pride features for years on its own. It is a hard worker for the Internet Outreach subteam of CO, and it is capable of making the call of what is a good post and what isn't, as well as catching onto trends as they happen. I think it's time we promote Prom for its hard work; I see a bright future of it leading IO at some point. —Nico Since joining the moderation team, Prom has been one of the most consistent, active staff present in the extremely busy chats of 19cord. Not only has Prom worked daily to ensure the safety of all users present in the chats, it has also been open to ownership and improvement in the case of any errors. We absolutely support and encourage Prom's promotion. - Ari
Optional areas of improvement:	I asked Prom to tell me what it views as its own areas of improvement as an OS and this is what it said: "I'd say I have trouble practicing what I preach and making commitments I can't always live up to. I'll work on managing my own expectations and being more realistic to myself and others" Personally, I feel that Prom's history as lead of the now defunct Recap team speaks more here than anything else. It took on the Sisyphean task of cataloging all the inane shit staff was saying during a time when Site trust in staff was at an all time low. It's efforts led to the opening up of staffcord to the public, as well as regained lost trust. I am confident in its ability to improve its overcommitment flaw, and am happy to endorse it as an opstaff candidate once more.

Junior Staff Member:	Diogene_s
Captain/Team:	MAST (Deadly Bread)
Why:	Diogene_s is an indispensable member of the tagging team, constantly going above and beyond in terms of both the consistent quantity and quality of their tagging output. They've been extremely reliable when it comes to maintaining current and shifting tag standards in both new and old articles, quite often bringing to attention ones that have slipped through the cracks. By being promoted Dio could also qualify for Mod Tools, which would invariably come in handy based on their consistent interaction with the tags of older, locked articles.
Optional areas of improvement:	I am slightly worried about Dio burning out based on their just sheer level output in one area, and would like to see them take some opportunities to branch out in other areas of staff work, but even so this worry is fairly minimal given the consistency in their output and their clear interest in the tagging process beyond just application.

Administrator Candidates:

Below is a suggestion regarding an Operational Staff member who the Administrator Team has nominated to be voted upwards to Administrator. Please read the commentary provided in order to help your judgement regarding these staff.

Staff Member:	Kufat
Captain/Team:	Admin Team
Why:	Kufat has long been a driving force for improvement on the wiki. He is often the one handling Disciplinary and AI Reports, is on the front lines of Deletions, runs the Timers we as staff utilize for many things and often take for granted, and takes the time to answer questions in #help-desk on the official Discord. In policy discussions, he is always open to hearing what others have to say even if he doesn't agree with it partially or even in full, and he is always willing to hear you out and provide well-informed, nuanced counterarguments. To say that Kufat is an important, irreplaceable organ in the staff body is an understatement.
Self Reflection:	I think I'd be a good choice for admin because I've demonstrated that I'm responsible, helpful, and willing to put in hard work: I've had mod tools for a while now and have routinely handled deletions, attribution metadata edits, thread and page locking, etc. I frequently answer questions and handle user requests and reports in #site17, 19cord's #help-desk, Staffcord's #observer-chat, and on /r/scp, as well as helping other staffers when they're in need of assistance. In addition to the usual day-to-day tech/disc/deletions work I've contributed to everything from policy (writing the Plagiarism Jurisdiction policy and participating in the writing of others) to software (enhancements to the deletions timer tool; tool for listing empty slots with titles) as well as enhancing site security. As an admin I'd continue this sort of work, with a greater emphasis on developing policy, as well as being able to take on some of the application processing and revocation/ban workload when needed.
Optional areas of improvement:	One area in which I'd like to improve would be working on a way to more effectively keep track of everything I have on my to-do list. At any given time I tend to have one or two larger staff or community projects and a bunch of smaller tasks going on, and it's sometimes difficult to juggle all of them.

Staff Member:	Queerious
Captain/Team:	Admin Team
Why:	Queerious has taken staff by storm ever since she joined last year. In her short time with us, she has become the Acting Captain of Discord Crit, Captain of Disciplinary Team, VC of Curations, has taken over the Bright Works Project, helped create a new workflow system for Rewrite, and helped pen a new (but as of yet unimplemented) Licensing policy, all while still finding the time to do her regular staff work. She possesses an excellent work ethic, and has proven herself capable of handling high-sensitivity and high-workload tasks, as well as managing policy discussion flawlessly. If staff work represents important bodily functions of the wiki, Queerious is a cyberpunk enhancement.
Self Reflection:	When I think about what I want to do to help the community, I always find myself thinking about large-scale issues, or problems that touch multiple staff teams. In that regard, I have joined many staff teams, so that I can have a full understanding of what that team needs specifically, so that I can make better decisions about what would help the most. I believe that sense of staff as a whole, and trying to improve communication and collaboration is something important for Administrators to do, as a higher-level unifying force for staff, and I think I would fit that role well. Additionally, in the past months, I have repeatedly found myself stepping up to sift through a more complex, messy or controversial situation or problem, that others may be more hesitant to participate in. Given my background, I am readily able to separate myself from the objective, and know how to keep progress moving, so that we can resolve these kinds of concerns in a reasonable manner. Between the Bright Works project, assorted in-depth Disciplinary reviews, and even the rewrite workflows, I have shown that I can get a framework and system built that supports other staff taking over responsibility for it, once I have helped to resolve the immediate issue. I believe that I would be able to continue this kind of work, at a high level, to assist in dealing with the more messy, inter-staff team issues.
Optional areas of improvement:	In terms of self-improvement, I think the biggest aspect would be that, if I get the promotion, I would need to evaluate where I can best spend my time devoted to staff work. There are a number of responsibilities that I have already began the process of transitioning to systemic support (ie: moving 914 maintenance to Curations), so I think my biggest area of self-improvement would be to continue seeing what I can delegate from my day-to-day, so that I have more time to focus on the bigger picture issues.

Vote YES or NO. Someone who you are ambivalent to should not receive your vote of confidence for staff, thus abstain or no. If you don't know who someone is, then I invite you to educate yourself and get to know their work before voting.

||~ Operational Staff Candidate||~ YES||~ NO|| ||[[*user VapidPoem]]|| X || X || ||[[*user Strange Matter]]|| X || X || ||[[*user sailorenoch]]|| X || X || ||[[*user pr0m37h3um]]|| X || X || ||[[*user Diogene_s]]|| X || X || ||~ Admin Staff Candidate||~ YES||~ NO|| ||[[*user Kufat]]|| X || X || ||[[*user Queerious]]|| X || X ||

Mainsite Mirror

See Promotions-Policy for how promotions are to be handled.

This discussion is open to all users. Please feel free to leave your thoughts. This is NOT a voting post.

Rules and Decorum:

This thread exists to allow commentary and criticism on candidates as candidates. All comments should be addressing one of the following:

• Concern or support for a candidate's ability to perform their duties after promotion.
• Concern or support for a candidate's character only in so far as it will affect their ability to perform their duties or their standing as staff.

What is not allowed in this thread:

• General complaints that you don't like a candidate for reasons that would not effect their ability to perform their duties.
• Comments that contain neither concern nor support for any candidate. A totally neutral stance does not need commented.
• Vehemence, rudeness, and incivility. While this is a place to post concerns, it is not a place to attack candidates.

Replies to comments are allowed but not required. Any user may respond to any concerns or support, including the candidate in question. All of the same rules apply to replies.

Staff will be monitoring this thread and will issue orders to stop discussion only if they have passed into unproductive vehemence. Staff will remove any comments that are extremely rule-breaking.

This discussion will be open for two weeks. After which time it will move to a staff vote.

Operational Staff Candidates:

Below is a group of suggestions regarding Junior Staff who Team Captains have nominated to be voted upwards to Operational Staff. Please read the commentary provided in order to help your judgement regarding these staff.

Junior Staff Member:	VapidPoem
Captain/Team:	Curations (Riemann)
Why:	Vapid has taken on the role of the Rewrite team workhorse, helping expedite a process that once took weeks or even months into one that only takes a few days, up to a week at worst nowadays. She shows a drive to help the articles improve, while still staying true to their original visions. It has also stepped up into the Anonymous Articles team, where she has helped post anonymous articles at a time when no one else was able to. Overall, Vapid has a great disposition and willingness to help, as well as take on work. I have no doubt she would make an excellent Opstaffer. —Nico
Optional areas of improvement:	I asked Vapid to tell me what she views as her own areas of improvement as an OS and this is what she said: "My biggest weakness is that I've only been staff for a few months. There is still plenty of stuff to learn - just the other day I was learning how to edit metadata for the first time. However I still definitely am working to improve and will most certainly ask questions if I am unsure about something or how to perform a task, as well as look over guides and resources provided to figure out how to do a task until I feel comfortable doing it." Personally, I think Vapid is comfortable asking questions and is willing to learn, so I am not worried about her not learning something quickly, and even if it does make a mistake, I am confident she will learn from it.

Junior Staff Member:	Strange Matter
Captain/Team:	Community Outreach (WhiteGuard/Naepic)
Why:	Strange Matter has been working quietly but diligently on Site News for some time now. He often writes stories which involve interviews, a very involved process that requires thinking of thoughtful questions to ask to users. His interviews have ranged from contest winners, contest runners, canon runners and GoI creators, and he is very good at asking thought-provoking questions. Strange Matter has proven himself reliable and consistently capable of producing stories, and I think it's time he is acknowledged. Plus with my current head of Site News retiring effective June 1st, I could use another hand on deck as a candidate for mod tools for posting the Site News. —Nico
Optional areas of improvement:	I asked Strange Matter to tell me what he views as his own areas of improvement as an OS and this is what he said: "Speaking solely as a Community Outreach staffer, I feel as though I could push further into the role. For instance, I would like to get in contact with artists or with people in other foreign branches of the site and do coverage with them." Personally, I do not doubt his capabilities as a Site News correspondent, but I would like to see him get a bit more involved in matters that aren't immediately related to his particular scope, as well as learn how the Site News posting process works.

Junior Staff Member:	sailorenoch
Captain/Team:	Community Outreach (WhiteGuard/Naepic)
Why:	Enoch is very proactive on the art committee, always having artists and artwork pieces to spotlight. They also have contributed art to Pridefest 2024 and 2025, and I generally trust them to do good. By promoting them, we can potentially run Enoch for Mod Tools, which would facilitate their role on the art committee. —Nico
Optional areas of improvement:	I asked Enoch to tell me what they view as their own areas of improvement as an OS and this is what they said: "I would like myself to build confidence in my decision-making. I recognize that I doubt my own judgement and seek approval for things I can handle myself. While communication is always good, I think I could take more initiative." Personally, I find myself agreeing with Enoch's self-assessment, but I am confident in their ability to grow into their new position as op-staff should they be promoted, as well as their ability to improve their self-confidence.

Junior Staff Member:	pr0m37h3um
Captain/Team:	Community Outreach (WhiteGuard/Naepic)
Why:	Prom is active on Bluesky and has managed the Pride features for years on its own. It is a hard worker for the Internet Outreach subteam of CO, and it is capable of making the call of what is a good post and what isn't, as well as catching onto trends as they happen. I think it's time we promote Prom for its hard work; I see a bright future of it leading IO at some point. —Nico Since joining the moderation team, Prom has been one of the most consistent, active staff present in the extremely busy chats of 19cord. Not only has Prom worked daily to ensure the safety of all users present in the chats, it has also been open to ownership and improvement in the case of any errors. We absolutely support and encourage Prom's promotion. - Ari
Optional areas of improvement:	I asked Prom to tell me what it views as its own areas of improvement as an OS and this is what it said: "I'd say I have trouble practicing what I preach and making commitments I can't always live up to. I'll work on managing my own expectations and being more realistic to myself and others" Personally, I feel that Prom's history as lead of the now defunct Recap team speaks more here than anything else. It took on the Sisyphean task of cataloging all the inane shit staff was saying during a time when Site trust in staff was at an all time low. It's efforts led to the opening up of staffcord to the public, as well as regained lost trust. I am confident in its ability to improve its overcommitment flaw, and am happy to endorse it as an opstaff candidate once more.

Junior Staff Member:	Diogene_s
Captain/Team:	MAST (Deadly Bread)
Why:	Diogene_s is an indispensable member of the tagging team, constantly going above and beyond in terms of both the consistent quantity and quality of their tagging output. They've been extremely reliable when it comes to maintaining current and shifting tag standards in both new and old articles, quite often bringing to attention ones that have slipped through the cracks. By being promoted Dio could also qualify for Mod Tools, which would invariably come in handy based on their consistent interaction with the tags of older, locked articles.
Optional areas of improvement:	I am slightly worried about Dio burning out based on their just sheer level output in one area, and would like to see them take some opportunities to branch out in other areas of staff work, but even so this worry is fairly minimal given the consistency in their output and their clear interest in the tagging process beyond just application.

Administrator Candidates:

Below is a suggestion regarding an Operational Staff member who the Administrator Team has nominated to be voted upwards to Administrator. Please read the commentary provided in order to help your judgement regarding these staff.

Staff Member:	Kufat
Captain/Team:	Admin Team
Why:	Kufat has long been a driving force for improvement on the wiki. He is often the one handling Disciplinary and AI Reports, is on the front lines of Deletions, runs the Timers we as staff utilize for many things and often take for granted, and takes the time to answer questions in #help-desk on the official Discord. In policy discussions, he is always open to hearing what others have to say even if he doesn't agree with it partially or even in full, and he is always willing to hear you out and provide well-informed, nuanced counterarguments. To say that Kufat is an important, irreplaceable organ in the staff body is an understatement.
Self Reflection:	I think I'd be a good choice for admin because I've demonstrated that I'm responsible, helpful, and willing to put in hard work: I've had mod tools for a while now and have routinely handled deletions, attribution metadata edits, thread and page locking, etc. I frequently answer questions and handle user requests and reports in #site17, 19cord's #help-desk, Staffcord's #observer-chat, and on /r/scp, as well as helping other staffers when they're in need of assistance. In addition to the usual day-to-day tech/disc/deletions work I've contributed to everything from policy (writing the Plagiarism Jurisdiction policy and participating in the writing of others) to software (enhancements to the deletions timer tool; tool for listing empty slots with titles) as well as enhancing site security. As an admin I'd continue this sort of work, with a greater emphasis on developing policy, as well as being able to take on some of the application processing and revocation/ban workload when needed.
Optional areas of improvement:	One area in which I'd like to improve would be working on a way to more effectively keep track of everything I have on my to-do list. At any given time I tend to have one or two larger staff or community projects and a bunch of smaller tasks going on, and it's sometimes difficult to juggle all of them.

Staff Member:	Queerious
Captain/Team:	Admin Team
Why:	Queerious has taken staff by storm ever since she joined last year. In her short time with us, she has become the Acting Captain of Discord Crit, Captain of Disciplinary Team, VC of Curations, has taken over the Bright Works Project, helped create a new workflow system for Rewrite, and helped pen a new (but as of yet unimplemented) Licensing policy, all while still finding the time to do her regular staff work. She possesses an excellent work ethic, and has proven herself capable of handling high-sensitivity and high-workload tasks, as well as managing policy discussion flawlessly. If staff work represents important bodily functions of the wiki, Queerious is a cyberpunk enhancement.
Self Reflection:	When I think about what I want to do to help the community, I always find myself thinking about large-scale issues, or problems that touch multiple staff teams. In that regard, I have joined many staff teams, so that I can have a full understanding of what that team needs specifically, so that I can make better decisions about what would help the most. I believe that sense of staff as a whole, and trying to improve communication and collaboration is something important for Administrators to do, as a higher-level unifying force for staff, and I think I would fit that role well. Additionally, in the past months, I have repeatedly found myself stepping up to sift through a more complex, messy or controversial situation or problem, that others may be more hesitant to participate in. Given my background, I am readily able to separate myself from the objective, and know how to keep progress moving, so that we can resolve these kinds of concerns in a reasonable manner. Between the Bright Works project, assorted in-depth Disciplinary reviews, and even the rewrite workflows, I have shown that I can get a framework and system built that supports other staff taking over responsibility for it, once I have helped to resolve the immediate issue. I believe that I would be able to continue this kind of work, at a high level, to assist in dealing with the more messy, inter-staff team issues.
Optional areas of improvement:	In terms of self-improvement, I think the biggest aspect would be that, if I get the promotion, I would need to evaluate where I can best spend my time devoted to staff work. There are a number of responsibilities that I have already began the process of transitioning to systemic support (ie: moving 914 maintenance to Curations), so I think my biggest area of self-improvement would be to continue seeing what I can delegate from my day-to-day, so that I have more time to focus on the bigger picture issues.

These are votes of confidence. If you are unfamiliar or on the fence about someone, vote NO or don't vote at all. Only vote yes if the candidate has your confidence and you genuinely feel that they are ready for mod tool access.

Previous discussion here.

This is an open vote for operational staff and above.

Candidate:	Aftokrator
Captain/Admin:	Riemann
Why:	Afto is being nominated for mod tools, through Curations, as a part of the duties with collaboration pages, including pruning and maintenance. Given we have elected to move things like the 914 logs under collaboration pages, which uses locked pages, mod tools would enable Afto to effectively do their work, without needing to ping mod tool users for assistance.

Vote YES or NO. Per the proposal, only yes and no votes will be counted.

The promotion vote will end in:

||~ **Candidate** ||~ YES ||~ NO || || [[*user Aftokrator]] || X || X ||

Aftokrator

Edit: To clarify the reason, an explanation has been added below for the work Afto would be doing that requires Mod Tools

Afto is being nominated for mod tools, through Curations, as a part of the duties with collaboration pages, including pruning and maintenance. Given we have elected to move things like the 914 logs under collaboration pages, which uses locked pages, mod tools would enable afto to effectively do their work, without needing to ping mod tool users for assistance.

If you have anything to say about this user getting Mod Tools, be it positive, negative, or something in between, please let it be known in this thread.

Discussion will go on for one week.

Per the Mod Tools Policy all Captains must decide to Renew or Remove the Mod Tools of their team members during the Winter Promotion cycle. Below are the lists of those with mod tools corresponding to whether or not their Captain opted to have them keep their mod tools.

Per the Policy, Captains will have until the conclusion of the Winter Promotion cycle to list any corrections in this thread.

This thread is open to Captains and Vice Captains.

Mod Tools Renewals:

The following members of staff have had their names put forward to have their mod tools renewed.

Staff Member	Teams Renewing
AstersQuill	Curation
Deadly Bread	MAST
DrRevan	Forum Crit
Erminustay	Licensing
Esperion	MAST
EstrellaYoshte	Tech
FlyPurgatorio	CO, Curation
JackalRelated	Curation, MAST
Jerden	CO
Kufat	Tech
Modulum	CO
Naepic	Licensing
NebulousStar	MAST, Licensing
ParallelPotatoes	CO
psychicprogrammer	MAST, Tech
Queerious	Curation, Licensing
Riemann	Curation, Licensing
WhiteGuard	CO
Woedenaz	Tech

Mod Tools Removals:

The following members of staff have not had their names put forward to have their mod tools renewed.

Staff Member
Hexick
Joreth

These are votes of confidence. If you are unfamiliar or on the fence about someone, vote NO or don't vote at all. Only vote yes if the candidate has your confidence and you genuinely feel that they are ready for mod tool access.

Previous discussion here.

This is an open vote for operational staff and above.

Candidate:	Esperion
Captain/Admin:	Deadly Bread
Why:	As the current head of 05 Updating, having access to mod tools would assist Espy's work in maintaining consistency between 05 Command and mainsite pages, a majority of which is behind pages locked to regular users. As Espy's shown great effort in maintaining the record of staff, this would greatly streamline that process.

Candidate:	Queerious
Captain/Admin:	Riemann
Why:	Queerious' ability is self evident. She has been a powerhouse of Curations and, I would imagine, any other team she is on. Mod tools will greatly aid her ability to perform rewrite duties and her additional responsibilities from being Curations VC. And clearly she deserves it. Come on.

Vote YES or NO. Per the proposal, only yes and no votes will be counted.

This promotion vote will end in:

||~ **Candidate** ||~ YES ||~ NO || || [[*user Queerious]] || X || X || || [[*user Esperion]] || X || X ||

See Promotions-Policy for how promotions are to be handled. This is the newest, shiniest version of mod tools promotions, requiring a discussion period for potential candidates for mod tools.

We have two candidates for mod tools for discussion this time. Please discuss to your hearts content.

This promotion vote will end in:

Candidate:	Esperion
Captain/Admin:	Deadly Bread
Why:	As the current head of 05 Updating, having access to mod tools would assist Espy's work in maintaining consistency between 05 Command and mainsite pages, a majority of which is behind pages locked to regular users. As Espy's shown great effort in maintaining the record of staff, this would greatly streamline that process.

Candidate:	Queerious
Captain/Admin:	Riemann
Why:	Queerious' ability is self evident. She has been a powerhouse of Curations and, I would imagine, any other team she is on. Mod tools will greatly aid her ability to perform rewrite duties and her additional responsibilities from being Curations VC. And clearly she deserves it. Come on.

See Promotions-Policy for how promotions are to be handled. And see the Candidate Discussions on the main-site thread and 05 thread for more information about candidates.

These are votes of confidence. If you are unfamiliar or on the fence about someone, vote NO or Abstain. Only vote yes if the candidate has your confidence and you genuinely feel that they are ready for promotion.

Please post even if you are abstaining from voting. Staff may abstain from voting on any individual votes.

This promotion vote will end in:

Operational Staff Candidates:

This is an open vote for operational staff and above.

Below is a group of suggestions regarding Junior Staff who Team Captains have nominated to be voted upwards to Operational Staff. Please read the commentary provided in order to help your judgement regarding these staff. If you feel they have displayed readiness, vote yes. If they are not ready, vote no; please explain your reasoning.

Junior Staff Member:	Queerious
Captain/Team:	Discord Crit (Pedagon)
Why:	Queerious joined Discord Critique Team fairly recently, but has become a major part of the team (and other teams) since. Queerious, in her time since joining Discord Critique Team, has shown incredible passion and drive towards making Deer College a better place through patching holes in policies, improving communication between staff members and those who use our critique spaces, and being a driving force for new ideas that benefit the critique experience in Deer College. She has taken the initiative and led the effort to rework many of our documentation standards, processes, and created systems to help both the users, as well as support the rest of Critique Staff. She was also responsible for updating the greenlighting standards, leading the creation of the #specialized-critique channel, and has become a consistent presence within Deer College. As well, Queerious has joined the Discord Moderation Team and has worked to advance our interteam communication effectiveness. This drive to improve within and beyond the boundaries of teams is what I believe will make Queerious a fantastic person to give powers of policy voting to. Given all of the above, the promotion to OS will only give Queerious more room to grow, and she has clearly shown that she is ready for it.
Optional areas of improvement:	Before writing this statement I asked Queerious to tell me what she views as her own areas of improvement as an OS and this is what she said: "While Queerious has a strong handle on procedural processes, I would like to see her continue to find a healthy balance between her assorted roles, as well as being better at coordinating efforts. She has demonstrated the ability to execute on her own, OS will give her the opportunity to grow further into more leadership-adjacent opportunities." (which I agree with). As well, I would like to see Queerious think outside of the teams more often and act more as a holistic staff between the teams.
Junior Staff Member:	Queerious
Captain/Team:	Curations (Riemann)
Why:	Queerious has taken rewrite by storm ever since her addition to the team. She has helped push out articles that were languishing in the pipeline, helped me (Uncle Nicolini) set up and maintain the new In-Rewrite Workbench, has helped me push out rewrite policy and create the rewrite policy tree, and has become my second in command for the team. She has a mind for policy and does excellent work at it, something that will undoubtedly earn her the admin position in the near future. But for now, I am happy to say that Queerious deserves to be and should be promoted to opstaff.
Optional areas of improvement:	N/A
Junior Staff Member:	syuzhet
Captain/Team:	Community Outreach (Naepic)
Why:	steph has become an indispensable person on the contests team, from her art contributions on hubs to the input she provides on how running contests need to be adjusted. Her feedback is as flexible as it is important, responding accordingly to the ever-changing landscapes and sentiments that contest induce.
Optional areas of improvement:	N/A

Vote YES or NO. Someone who you are ambivalent to should not receive your vote of confidence for staff, thus abstain or no. If you don't know who someone is, then I invite you to educate yourself and get to know their work before voting.

||~ Operational Staff Candidate||~ YES||~ NO|| ||[[*user Queerious]]|| X || X || ||[[*user syuzhet]]|| X || X ||