(USA) Abner "Oldwood" Site Admin App

Abner "Oldwood"

Moderator
Moderator
SCP-RP Staff
Jul 21, 2025
42
4
61
Steam ID: STEAM_0:0:224459998
Discord name: Segmentus Majoris
For how long have you played on CN SCP: 4 years on and off
Age: 28
In what country are you located?: USA
Time zone: EST
Character name(s): Abner "Oldwood"
Civilian name: Abner Rosecairn
What server are you applying for? (SCP-RP USA):
Do you have a mic?: yes
-

List all whitelisted, MTF, or CI roles that you hold or have held:​

  • Chief of Security
  • Security Captain / Senior Captain / Security SGT
  • ISD investigator
  • Chemical Research Board (CRB) Ambassador
I have spent a significant amount of my time working within GSD and its leadership structure. Before becoming Chief of Security, I spent roughly two years as a Security Captain and around a year as a Senior Captain. During that time, I helped train and develop numerous members of GSD leadership and was involved in several departmental programs, subdivisions, and sub-regiments.

I have also worked extensively with other Foundation departments through joint operations, agreements, training, and departmental administration. This has given me experience dealing with situations beyond GSD alone and has helped me better understand how different departments operate together within the Foundation.



Have you received any kicks/bans/warning? and why?:​

I have not received any warns, bans, kicks, or arrests.


Why are you applying for Site Advisor?​

I am applying for Site Advisor because I want to expand the role I currently play within the server and contribute to the Foundation on a broader level.

A large portion of my time has been dedicated to GSD. As Chief of Security, I have had the opportunity to manage personnel, develop policies, oversee leadership, resolve internal problems, coordinate with other departments, and help determine the future direction of the department. While I greatly enjoy that responsibility, Site Advisor would allow me to take the experience I have gained from GSD and apply it to the site as a whole.

One of the things that interests me most about Site Administration is that the position is not supposed to revolve around one department. A Site Advisor needs to understand the needs of multiple departments and consider what is best for the overall health and operation of the site.

I also believe the position would give me opportunities to participate in more complex RP. Instead of only responding to security-related situations, I could become involved in administrative disputes, departmental problems, investigations, major incidents, interdepartmental negotiations, policy discussions, and long-term storylines.

I have spent a considerable amount of time helping build and improve one department. I would now like the opportunity to use that experience to help improve RP and operations across the entire site.


What makes you suitable for Site Administration?:​

I believe my strongest qualification is my leadership experience and my willingness to actively work toward improving the server rather than simply maintaining what already exists.

I have spent years within GSD leadership, progressing through Captain and Senior Captain before eventually becoming Chief of Security. This has required me to manage people with very different personalities, experience levels, and approaches to RP.

As Chief, I am responsible for much more than simply giving orders during security situations. I have to consider departmental structure, personnel management, promotions, discipline, training, policy changes, interdepartmental relations, and the long-term health of GSD.

I have also helped create, lead, and manage sub divisions and sub regiments such as T&G, G&I (the original) TRT, EPU, and other departmental initiatives. These experiences have taught me that creating something is only the beginning. You also have to maintain it, listen to feedback, adapt it when circumstances change, and make sure that it actually improves the experience of the people using it.

One of the accomplishments I am particularly proud of is my involvement in the development of the new Senior CL4 roles for the core departments. I was partially responsible for helping push and develop the concept of giving the core departments an additional Senior CL4 leadership position, allowing experienced departmental leadership to take on greater responsibilities and providing another level of progression.
The GSD Senior CL4 position, Security Major, is especially important to me because the original concept was largely my brainchild. I had been working toward the idea for quite some time because I believed there was a significant gap between Captain-level leadership and the Chiefs of Security. My goal was to create a position that could take responsibility for individual areas of GSD rather than forcing every major departmental matter directly onto the Chiefs.
That idea eventually developed into the Security Major structure, with Majors being given responsibility over different areas such as D-Block operations, LCZ–EZ operations, training and development, and disciplinary/professional standards, while also helping manage the subdivisions and sub-regiments connected to those responsibilities.

I believe this demonstrates something that would be extremely valuable within Site Administration: the ability to identify a structural problem, develop a realistic solution, work with other people to refine it, and ultimately help turn that concept into something that benefits the server.

The fact that similar Senior CL4 positions are now being introduced across the core departments also makes me proud because the concept grew beyond simply improving GSD. It became something that could potentially improve progression and leadership opportunities across several departments.

Another strength I would bring to Site Administration is my willingness to communicate and work with other departments. GSD cannot function in isolation. During my time in leadership, I have worked alongside groups such as Site Administration, ISD, LE, FISA, DEA, NU-7, E-11, Research, Medical, and other Foundation departments. This experience has taught me how important compromise and communication are. Something that benefits one department may negatively affect another, and senior leadership needs to understand that before making a decision.

I am also willing to admit when I am wrong. Leadership does not mean that every decision you make will be correct. What matters is being able to listen to criticism, recognize when something is not working, and change your approach rather than allowing pride to interfere with the situation.

Most importantly, I understand that becoming a Site Advisor would not simply mean receiving greater authority. It would mean accepting greater responsibility. Site Administration should exist to facilitate RP, support departments, solve larger problems, and help create improvements that benefit the site as a whole.

I believe my experience taking ideas from concepts into actual departmental changes, particularly with the new Senior CL4 Security Major position, shows that I am willing and capable of doing exactly that.


What are the responsibilities of Site Administration in RP?:​

In RP, I believe the primary responsibility of Site Administration is to oversee the broader operation of the site while allowing individual departments to perform their own responsibilities. Site Administration should provide direction rather than unnecessarily micromanaging departments. Department Directors and their command teams should generally be allowed to manage their own personnel and internal operations unless a situation requires administrative involvement.

Site Administration should instead focus on larger issues that affect multiple departments or the Foundation as a whole. This can include coordinating departments during major incidents, addressing conflicts between departmental leadership, reviewing major operational concerns, communicating Foundation priorities, overseeing important projects, and making decisions when an issue extends beyond the authority of an individual department.

Another important responsibility is creating and facilitating RP.

A Site Advisor should not simply sit in an office waiting for somebody to request authorization or wait for something between the departments to break down. They should actively look for opportunities to create situations that give other players something meaningful to participate in.

This could involve organizing inspections, meetings, investigations, departmental evaluations, emergency planning, policy discussions, negotiations, or larger storylines involving several departments.

Site Administration should also act as a bridge between departments. Different departments naturally have different priorities, and disagreements will occasionally happen. Site Administration should be capable of hearing each side, understanding the circumstances, and reaching a reasonable solution without automatically favoring one department.

Ultimately, I see Site Administration as responsible for maintaining the overall stability, coordination, and RP environment of the site while ensuring departments still have room to operate independently.


Site Administration Character Lore​

Abner "Oldwood"
Name: Abner Gideon Rosecairn
Date of Birth: November 19, 1973
Age: 52
Height: 6'3"
Weight: Approximately 215 lbs
Status: Active Foundation Personnel
Former Service: United States Navy
Military Service: 20 Years
Foundation Service: 15 Years
Marital Status: Divorced

Abner "Oldwood" is a 52-year-old former United States Navy officer who has spent nearly his entire adult life serving within military and Foundation command structures. Standing approximately 6'3" and weighing around 215 pounds, Abner still maintains much of the physical presence expected of someone who spent decades in military service. His hair has begun to gray considerably with age, although his most recognizable feature is the absence of his right eye.

Before entering Foundation service, Abner spent 20 years in the United States Navy, eventually rising to command the Arleigh Burke-class destroyer USS Ramage. His naval career was defined by discipline, leadership, and an unusual ability to remain functional under extreme psychological pressure.

USS Ramage Incident — SCP-3000​

The defining event of Abner's naval career occurred during a classified operation involving SCP-3000.

Abner was serving as commanding officer of the USS Ramage as part of a larger naval strike group when exposure to SCP-3000's anomalous effects began severely compromising the mental state of personnel throughout the formation.
Command structures rapidly deteriorated. Officers and sailors became increasingly confused, paranoid, irrational, and eventually hostile toward one another.
Ships that had entered the operation as allies began turning their weapons against each other.

The USS Carney and USS Hopper were eventually destroyed during the chaos, while the USS Ramage sustained extensive damage.
Despite the deteriorating situation, Abner remained aboard and continued attempting to maintain command of his vessel.

During the fighting, he suffered catastrophic injuries that resulted in the permanent loss of his right eye.
However, something about Abner caught the Foundation's attention.

Despite prolonged exposure to the same psychological effects that had caused much of the strike group to lose control, Abner remained mentally functional.
Whether this was the result of exceptional psychological resilience, unusual resistance to the anomaly, or something else entirely was never completely determined.
Either way the event left a permanent impact on Abner.

He rarely speaks about the Ramage, his missing eye, or the sailors who died during the incident. To Foundation researchers, his survival represents an unusual case worthy of continued study. To Abner, it represents the day he watched trained sailors and officers turn their weapons against eachother.

The experience ultimately left him with a belief that would define his approach to leadership for the rest of his life:

"When everyone else loses control, someone has to remain standing."

"The Pillar"

Foundation Career​

Following the conclusion of his naval career, Abner eventually entered the service of the SCP Foundation.

His military command experience, operational knowledge, and demonstrated resistance to anomalous psychological effects made him particularly valuable within Foundation security.
Over the following 15 years, Abner gradually moved through increasingly senior positions, eventually becoming heavily involved in the leadership and administration of Foundation security operations.

His responsibilities expanded beyond simply commanding personnel. Abner became involved in training, personnel development, disciplinary matters, departmental policy, containment procedures, interdepartmental coordination, and larger operational decisions.
By this point in his life, Abner had accumulated approximately 35 years of combined military and Foundation service.

His extensive time within security eventually pushed him toward responsibilities outside the boundaries of a single department. He increasingly found himself participating in departmental disputes, policy discussions, investigations, negotiations, and decisions affecting the wider site.

This experience ultimately created his interest in Site Administration.
For most of his career, Abner had been responsible for ensuring that the decisions of senior leadership could actually be carried out.
Moving into Site Administration would place him on the opposite side of that relationship.
He would now be responsible for helping make those decisions.

Education​

Alongside his military and Foundation experience, Abner possesses an extensive academic background:
  • International Relations, and Education (Double Majored Bachelor) while minoring in Philosophy.
  • Political Science and a Minor in Pre law.
His education complements his decades of practical leadership experience, particularly when dealing with diplomacy, policy, interdepartmental disagreements, organizational leadership, and Foundation regulations.

Personality​

Abner is generally reserved, disciplined, stubborn, and extremely difficult to intimidate.
He rarely raises his voice simply to demonstrate authority. After decades in command positions, he is far more interested in whether someone is competent and dependable than whether they appear impressive.
His greatest strength is his ability to remain composed when situations begin deteriorating.

The SCP-3000 incident reinforced his belief that leadership matters most when normal command structures begin failing. Whether facing a containment breach, departmental dispute, hostile incursion, or internal crisis, Abner's instinct is generally to determine what happened, establish order, identify what resources remain available, and rebuild a functioning command structure.

However, this mentality is also one of his weaknesses.
Abner is extremely stubborn and occasionally approaches administrative problems as though they were military operations. He prefers clearly defined responsibilities, chains of command, and solutions, even when Foundation politics rarely provide any of those things.

Site Administration Storylines​

Abner's primary storyline within Site Administration would focus on his transition from military officer, to security commander, to Site administrator.

For most of his life, Abner was the person expected to execute the decisions made by those above him.

As a Site Advisor, he would increasingly become the person responsible for making those decisions—and accepting responsibility for their consequences.

His history within security would also create an interesting conflict. After spending years working alongside and developing security personnel, Abner would have to demonstrate that he could separate his personal connections from his administrative responsibilities.

There may be situations where the interests of security directly conflict with those of another department. Abner would have to determine what is best for the Foundation as a whole, even if that means ruling against the people he previously served beside.

His background also provides opportunities for storylines involving interdepartmental negotiations, investigations, disciplinary hearings, Foundation policy, departmental evaluations, emergency preparedness, containment failures, GOI activity, and major site-wide incidents.

His connection to SCP-3000 could also become a recurring storyline.

Foundation researchers may eventually become interested in determining exactly why Abner remained functional when so many others aboard the strike group did not. This could result in psychological evaluations, requests for testing, investigations into surviving records from the Ramage, or even questions regarding whether his resistance was entirely natural.

Abner himself would have little interest in discovering the answer.

To him, the Ramage is not an experiment.

It is something he survived.

Ultimately, Abner's Site Administration character would revolve around a man who has spent 35 years being responsible for other people's lives learning how to carry that responsibility on an entirely different scale.

For most of his life, remaining standing meant staying on the bridge and keeping his people alive.

As a Site Advisor, it would mean helping keep the entire site together.

"When everyone else loses control, someone has to remain standing."

"The Pillar".
 
Last edited: