Aurora Information Uplink - User contributions [en]

Biesel

2022-12-16T15:03:00Z

Lucaken: Changed Valkyrie's temperature to no longer be impossible per the laws of physics.

{{Navbox Lore}}
{{Navbox Human Lore}}

<center>[[File:Mendell pixel.png]]</center>

Biesel was one of the first habitable exoplanets discovered and was located in Tau Ceti in the early days of exploration. Seventeen years after the [[Timeline#The Discovery of Warp|development of the Warp Drive]], its first colony was established in 2147. The planet consisted of simple flora in the pre-human era, and small furry gopher-like animals called Barks by early colonizers. Then humans colonized and introduced animals and plants from [[Earth]]. Despite conservation efforts, these animals quickly disappeared due to being out-competed by earth animals entering the wild and because they were viewed as pests for their loud, obnoxious barks and insatiable desire to chew wires. As a result of its sustained terraforming effort and colonization, Biesel has become one of the most wealthy and influential planets in human space. Following the aftermath of an economic recession during which the Sol Alliance was suffering, the [[Republic of Biesel|Federal Republic of Biesel]] and the Tau Ceti System achieved independence in 2452. Most of the major corporations operated on Biesel before its independence, but since the creation of the Free Trade Zone, they have been gradually bought out or undermined by the larger megacorporations. [[Nanotrasen Corporation|Nanotrasen]] and its subsidiaries account for the majority of all business in Biesel and Tau Ceti today.

== Environment ==

Biesel's rich resource base is attributed to a collision with a large celestial body early in its development. From the time Biesel was colonized, geologists have been studying Peterdiezel Crater closely. According to theories, the crater was created by the collision of a moon with the planet. This collision not only brought Biesel's moon, Valkyrie, into existence, but also created a wealth of resources. A part of Valkyrie is thought to be Biesel, while the other is thought to be the celestial body responsible for creating Peterdiezel Crater.

There is very little risk of Tsunamis on Biesel, because of the almost non-existent tectonic activity; tropical storms form with a similar frequency to Earth, but because of the smaller land area, the tropical storms can be much stronger. Many coastal cities have detection systems that sound an alarm if the correct atmospheric conditions are met.

As settlers colonized the planet, they introduced plants and animals brought over from Earth into the ecosystems of the planet. Unlike the introduced species of plants and animals that immediately followed human settlement, local species had historically thrived in Biesel before human settlement. After a total transformation, the habitat in Biesel resembles Earth with its flora and fauna.

A variety of species of animals, including deer, elk, wolves and bees, can be found in coniferous and temperate forests. There are also earth species found in deserts and on the ocean. As a result of the terraforming work carried out on Biesel, nearly all native alien species have disappeared. Few native rodents, insects, and fish have managed to adapt to the new ecosystem and have prospered. Only a few large animals remain in zoos for public viewing.

== Continents and Major Cities ==
[[File:BieselV3.png|400px|thumb|right|A labled map depicting Biesel.]]
<div class="toccolours mw-collapsible mw-collapsed">
=== Astraeus ===
<div class="mw-collapsible-content">

In spite of its size, Astraeus is the most affluent of Biesel's three continents and it is home to the capital, Mendell City. Even today, it remains the most heavily populated area in Biesel, largely due to the availability of natural resources and the low-lying plains that were easily colonized by early settlers. Many of their homesteads soon turned into cities, dotting the landscape around the two mountain ranges in the north, the Grattle, and in the south, the Uratines. In its long history, the Grattle range has evolved from a mining zone to a destination recognized for its top-performing ski resort that can lure visitors from the furthest reaches of Orion Spur.

==== Mendell City ====

See: [[Mendell City]]

Known as the most affluent city in all of space, [[Mendell City]] is the capital of Biesel. There are countless educational institutes where people of all backgrounds can hone their intellect and reach new heights before they are eagerly hired by corporate giants. However, the city has low-income neighbourhoods that exist on the outskirts of its more wealthy neighbourhoods. These low-income areas are home to a large population of non-humans used by Nanotrasen in exchange for cheap labour. In reality, very few people are actually living in abject poverty since basic utilities and public services are available, though these are infrequently reliable and there are very few higher education institutions available.

==== Cape City ====

Cape City, otherwise known as the “City of Splendor” by many Bieselites, is a city focused heavily on entertainment, production of holovids, and exorbitant tourist attractions. Situated around and on the side of Mount Nevermeet in the midst of the Cape Sea, the entertainment centre sits comfortably by scenic vistas, large themed resorts, and studios for filming and recording. However, due to unique labor laws, it has gained a bad reputation among non-humans for being exploitative and predatory in their practices. Any xenos looking to gain entry into fields like animation, studio production, acting, and the like face harsh stereotypes and discrimination, poorer qualities of living, and shop and drop contracts (hiring someone, forcing them to work an unusually high amount of hours a week, then “dropping” them if they protest or request different hours after a short period contract expires). Nonetheless, Cape City is on the up-and-up, and only time will tell its rise to the intergalactic stage as a media giant or not.
</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
=== Selene ===
<div class="mw-collapsible-content">

The second-largest continent of Biesel, Selene, is situated north of Astraeus. In spite of its size, Selene is the continent with the lowest population density of the three, with almost all of its inhabitants living in coastal towns. Those not biding their time on the coasts are usually tending the inland plains that often are lined with farmsteads. The Greatkrag range that runs across Selene has come to symbolize the Biesel Escarpment, an area consisting of steep slopes that transition into arctic plateaus, which entice those seeking to escape civilization.

==== Phoenixport ====

In a similar way to Mendell City, Selene's capital, Phoenixport, is located along the inner coast of its continent along Severson's Rift. After rebranding as a "successor" to Mendell City, the city gained prominence and briefly achieved its goal. Phoenixport was briefly successful, but fell off the radar and eventually became a breeding ground for nefarious behaviour. In another effort to revive interest in the city, government officials introduced replicas of various ancient architectural wonders. Examples include the Eiffel Tower and the Parthenon. Overall, the construction scheme did improve the quality of the city and even attracted large numbers of tourists eager to see the wonders rebuilt far from the dire conditions on Earth. [[Einstein Engines]] recent acquisition of Phoenixport has left many wondering whether the city will see yet another revival.

'''Unfortunately, NanoTrasen has not taken the transfer of ownership idly - any NanoTrasen employees within Phoenixport have been given until March of 2463 to relocate or be summarily fired, Phoenixport residents found outside of the city’s limits are often summarily stopped and searched by NanoTrasen-owned police officers, and Phoenixport-flagged spacecraft are similarly “randomly” searched by SCC patrol vessels. Yet despite this the prospect of having a business not owned by NanoTrasen continues to attract new capital to Phoenixport.'''

'''After an appeal by NanoTrasen in 2464, which proved that Einstein Engines had illegally acquired assets within Phoenixport, much of the corporate assets found themselves up for grabs yet again. Despite assistance from Idris Incorporated, NanoTrasen failed to secure a majority holding within Phoenixport, with Einstein Engines continuing its hegemony over the city. Subsequently, the discrimination faced by those in Phoenixport by local law enforcement has decreased significantly, as well as the "random" searches of Phoenixport-flagged spacecraft. Some of those forced from their homes during the original dispute have since begun to slowly return.'''

==== Belle Cote ====

Situated at the southernmost edge of the Pandeia Penisula, hedged in by the Greatkrag ranges, Belle Cote is considered Biesel’s centre of finance, fashion and arts. The Selenian Moth, an insect that produces a resilient fibre that is common in textile manufacturing, was discovered by colonists early on in the development of the colony. A result of this discovery was the rapid decline of fishing and the emergence of the fashion industry. With an annual show, Belle Cote pushed the boundaries of fashion vogue and still does so to this day. Those living in Belle Cote are often considered to be a bit stuck up, looking down on others who don't keep up to date with their trendy outlandish trends. Even the poorest dress themselves in their eccentric styles. It is a popular honeymoon and wedding destination, which the artisanal community has begun franchising upon.

==== Ashton ====

In the heart of Selene, Ashton sits among miles of rolling farmlands that are home to dozens of different species of flora, including some that are native to Biesel. Due to its dominant agricultural industry, the community's economy has become centred on agriculture, as illustrated by its bimonthly Ashton farmer's market, which draws residents from surrounding cities alike and has become a cornerstone of the community's economy. As a whole, Ashtons are noted for being incredibly welcoming and cheerful.
</div></div>

<div class="toccolours mw-collapsible mw-collapsed">

=== Eos ===
<div class="mw-collapsible-content">

The largest continent of the three, Eos resides mostly within the eastern hemisphere of Biesel and is the most industrialized. The large amount of coastal flatlands, supplied by rugged inlands, rich with minerals and resources of all varieties has led to most of the cities doting Eos to form along with the two major mountain ranges. They are the northern Latra range, which is heavily mined for its abundance of copper and iron, and the southern Sevul range, mined for its large quantities of heavy metals. Eos is also known for its sports fanatics, who host regular tournaments between the major population centres on Biesel.

==== Scottsdan ====

Scottsdan, the continental capital of Eos and the industrial giant of Biesel. Its abundance of raw resources, provided by the Sevul Range, and the refinery processing capabilities has resulted in megacorporations expanding their operations within the city. There is a growing robotics industry, with Hephaestus Industries, Confiance Technologies and Terranius Diagnostics locked in a perpetual war of dominance. Most of the goods produced within Scottsdan are transported via monorails designed to carry freight to Ports-Ville, the closest port to both Mendell City and Phoenixport on Eos. Citizens of Scottsdan are remarkably hard-working according to the megacorporations, however, some prefer to call them stuck up doormats due to their snooty, sycophant tendencies.

==== Top of the World ====

Previously a sleepy town with little going for it, Lakeside has now shot to prominence after Miranda Trasen’s funding into the borough. After clearing several acreages lined along the coast of Griff’s Lake, inhabitants suffered round the clock cacophonies echoing from the construction equipment now infesting the demolished meadows. Eventually, it became evident what was being constructed by the Orion Spur’s wealthiest woman. The acreages were not longer vast empty fields, but instead the entrance to a gated community floating along the lake. Construction at long last was completed, and yielded what is now known to be “Top of the World”.

It is uniquely populated by those who are gifted access by Miranda Trasen herself, or those able to afford the ridiculously expensive “warranty”. Only the highest of echelons exist within the man-made island. Beneath its surface exists an experimental tesla engine, one of unprecedented scale. On particularly bad days, those residing in Lakeside are warned from partaking in aquatic activities.

Majority of the labour force was previously comprised of IPCs, resulting in the creation of an entire community of positronics that existed purely to maintain and provide both the grand structure and its inhabitants. However, as of 2463, these IPCs have been made obsolete after the introduction of a triumvirate of artificial intelligences; Exteriores, Interiorem and Centrum. They coordinate with an array of bound drones, completing the tasks previously assigned to hundreds of independent positronic bodies, a cost-saving measure as cited by sceptics when comparing the value to ageing IPCs.

The integrated positronic chassis’ of Top of the World, who used to labour in a warm and maintained community of privileged construction and endless labour, all suffered redundancy and were put into other jobs or positions within NanoTrasen if owned. Free IPCs were often dumped to the curb and labelled as obsolete. The quality of life between Top of the World and Lakeside is stark. Poverty grips the majority of the population nestled within the backwater town. Dilapidated houses are a common sight within Lakeside, even entire houses sunken into the growing marsh. Free IPCs that previously called Top of the World home still remain in the area, stripped of any corporate identification in an often haphazard fashion, with clear signs of decay on their chassis.

==== Ports-Ville ====

Ports-Ville was originally established as a fishing and shipbuilding hub when Biesel was originally settled. For decades, the city was prosperous, supplying the planet with massive cargo ships to traverse its great blue oceans. After Biesel’s independence from the Alliance, however, Solarian subsidies for the industry disappeared and NanoTrasen found that shipbuilding was now cost-inefficient due to the continuing decrease of shipping goods by shuttle or spacecraft. The company withdrew most of its investment in the city’s heavy industry nearly overnight, causing the local economy to recede and the city itself to gradually decay into a patchwork of run-down apartment blocks, abandoned shipyards, and fishing ports in desperate need of maintenance.

Recently, however, [[Hephaestus Industries]] has brought up much of these abandoned facilities with hopes of retooling the city into a spaceship production centre on Biesel. This has also coincided with the megacorporation inviting many Martian refugees fleeing from the [[Mars#The Violet Dawn Explosion|Violet Dawn disaster]] to resettle in the city to work at these new facilities. Ports-Ville itself is unprepared for this great migration of people and is in the middle of a severe housing shortage, with many new arrivals finding themselves living in makeshift tent-town camps as a result. It is yet to be seen if this new investment by Hephaestus Industries will pay off and revitalise the city once more, as the influx of Martian refugees has so far only continued to strain the city’s already declining economy.

==== New Marfa ====

Established along the eastern coastline of Eos, New Marfa is one of few cities on Biesel without megacorporate dominance, which is largely attributed to its status as a hub for [[Republic of Elyra|Elyran]] migrants; half if not most of the citizens are either Elyran immigrants and expatriates or directly descended from one. Elyran culture is dominant in the city, to the point that at a glance, it has become nearly indistinguishable from a city in Persepolis. Elyran megacorporations retain a minority over the market with the SCC megacorporations, and the competition has led to a flourishing synthetic development sector. With a thriving glass refining industry and healthy technology sector, New Marfa’s advancements in the fields of robotics are said to be at least a year ahead of everything else on Biesel.

==== Craterview ====

Craterview has managed to become the vacation and resort city of the Republic of Biesel, with large [[Idris Incorporated|Idris]] Hotels lining the interior perimeter of the beaches and small family-run motels dotting the plots of land surrounding the beaches. Crime rates soar the farther one strays from the city centre, as locals defraud and steal from tourists drawn to their slice of Biesel. Other than the tourism industry, the fishing industry also does well, leading to a growing presence of local seafood hibachi restaurants. In addition to year-round sunshine and tropical climate, Craterview is occasionally interrupted by tropical storms. It is no wonder that boat races have become an attraction, even becoming an event for betting. In the rich suburbs, marinas line beachfront estates where [[Eridani Federation Military|Eridani Private Military Contractors]] are often spotted. It is well known that residents of Craterview are both competitive and sceptical of the wealthy.
</div></div>

== Life on Biesel ==
=== Entertainment ===

*'''Peterdiezel Boat Racing''' is an annual competition that begins in Craterview. The race is a three-day excursion and is usually recorded through observation drones following the individual boats racing against the clock. There are several routes all across Peterdiezel Crater, some more dangerous than others. While anyone can participate, most of the competitors are city teams such as the Mendell City Boat Club or the Cape Cods.

*'''Eos Sporting Tournaments''' are an annually held, international series of sporting events in which megacorporation-sponsored athletes participate in competitions involving human and alien sports. Every team or participant will represent a corporation during the competitions. Due to the corporate nature of the event, every participant must be employed in the megacorporation they represent. It is common for corporations to offer better salaries and benefits to notorious athletes in an attempt to poach them from their original employers. Games are usually hosted in any of Eos' cities except New Marfa.

*'''Belle Cote Fashion Show''' is a series of designer presentations held annually in Belle Cote. Sponsored by Idris, a variety of venues are used throughout the city to display the best-performing styles and themes of the year. Both Chief Executive Officers of Caishen Jewellers and Le Soleil Royal are regular hosts of the show, their fashion lines the staple of the event.

=== Festivals and Celebrations ===

*'''Republic Day''' (also known to some as Xavier’s Gala) is a holiday which commemorates the declaration of independence of Tau Ceti from the Solarian Alliance. The crippling economic recession experienced by the Solarian Alliance allowed the Republic of Biesel to leverage their independence, and ultimately be awarded it. It is hosted on May 5th of each year, and usually involves total rejection of both Solarians and Megacorporations. Fireworks, parades, fairs and concerts are often commonly associated with Republic Day.

*'''Tribuisti de Colonis''', or Festival of the Settlers, is a massive Carnival celebration marking Biesel’s colonization. The festivities usually begin on the third Friday of October, through to the Sunday. Mendell City has become the most well-known celebrator of the festival, parading through the streets of the various districts with eccentric clothing and massive floats (usually of the planet’s native species). Other popular cities include Craterview, which celebrates the festival with dazzling fireworks and displays of lights, and Belle Cote, which throws its annual fashion show over the weekend the festival takes place.

*'''Heritage Day''' is a holiday that recognizes and celebrates the cultural wealth of the Republic of Biesel. Celebrations differ from person to person and usually depends on their cultural heritage and the remembrance of such. Some believe the wearing of cultural garments is enough, while others may partake in cultural festivities hosted across Tau Ceti. It is usually held every September 24th.

=Valkyrie=

<div class="mw-collapsible-content">
<div style="font-size:110%; border:2px solid #ccc; margin:0; background:#4e29c7; padding:.1em; color:#fff;"></div>
<div class="toccolours mw-collapsible mw-collapsed">

In spite of being outperformed in terms of production by both New Gibson and Biesel, Valkyrie has managed to cement itself as a major player within the Republican economy. Its strategic location within its star system has enabled the planet to become a hub for trade, commerce and even tourism via extensive upgrades to its infrastructure. Valkyrie was originally a mining outpost that expanded rapidly after it was colonized shortly after Biesel in the 2150s. As a result of its proximity to Biesel, as well as its abundant raw resources, it has become popular among the megacorporations that have established outposts across the moon's surface. The Commonwealth of Valkyrie is treated as an independent member-state within the Republic of Biesel and receives planetary recognition.

<div class="mw-collapsible-content">

[[File:ValkyrieFlag.png|300px|right|thumb| The Flag of Valkyrie, representing both inhabited and uninhabited planets within Tau Ceti. The largest orb is Valkyrie, whilst the red orbs represent Biesel, New Gibson and Reade.]]

==Government==

Council of Valkyrian Affairs (commonly referred to as “The Council”) was established shortly after Valkyrie achieved recognized independence from Biesel, and were tasked to oversee the moon’s administration. Four councillors administer the various proceedings of the moon, which are under the direction of the Moon's director-governor. Within the Valkyrian Exchange Terminal, the Council occupies the Councillors' Chambers. There is often remark that it can even be seen with the naked eye on Biesel, which is sometimes met with hostility from Skrell, who seem unable to understand the sarcasm behind the comment.

Director-Governor: Charles Arcos, Human, 41

Councillor of Economic Development: Arthur O’Donnell, [[Offworlder Humans| Offworlder]], 66

Councillor of Foreign Relations: Michael Cox, Human, 39

Councillor of Law Enforcement: Hzi’ann Zskzi, [[Unathi]], 43

Councillor of Interior Affairs: Liu Shan, [[Offworlder Humans| Offworlder]],58

==Environment==
Since Valkyrie does not tidally lock to Biesel, it differs from most moons. There is a rotational period of approximately 16 hours. Moreover, its proximity to Biesel has resulted in a much smaller orbital period, taking only a week to complete one rotation around its parent planet. Valkyrie's surface temperatures tend to fluctuate between -100°C and -265°C depending on its location. In terms of size, it is similar to [[Luna]].
A repeated onslaught of asteroids dislodging themselves from the Dust Belt has left Valkyrie's landscape in a mess of jagged, overlapping ridges and craters. Its frightening environment has not stopped several corporations from taking over big segments of the moon for mining, shipbuilding, or other purposes.
Over the millennia, collisions between asteroids have inevitably resulted in Valkyrie being a repository for a large number of heavy metals, used for the production of spacecraft and weapons. As a consequence, generations of illegal mining operations have been carried out deep inside the crust of the moon, where many have lost their lives in an attempt to get rich fast.

==Major Outposts==
===Helios Manufacturing Site - Hephaestus Industries Valkyrian Outpost===

Located within one of the deepest trenches on Valkyrie, Helios is a megapolis centred around Hephaestus’ primary manufactory within the Republic of Biesel. Although it has had significant growth since its inception following a brief bidding war during the 2320s, its importance was only realized after the discovery of rich quantities of palladium, titanium, and aluminium. As opposed to setting up routes to transport resources outside of Tau Ceti, Hephaestus began building the first of many factories that would refine these metals and ultimately be used to build spacecraft. The Helios Manufacturing Site continued to expand greatly after its unveiling and now encompasses almost a sixth of Valkyrie.

===Hyperion Data Nexus - NanoTrasen Corporation Valkyrian Outpost===

The area in which the Nexus lies, as opposed to the other corporate outposts around Valkyrie, was privately purchased by Nanotrasen after [[Timeline#Discovery of Phoron|it discovered Phoron]] in 2418 and was used to start Nanotrasen's first laboratories for researching the crystal. It was only after the megacorporation achieved dominance on the crystal that the Nexus began expanding across the Valkyrian plains, with the establishment of a shipyard along the ridges marking an end to the plain on which the outpost occupied. Research and development remains a significant component of some laboratories, but a large portion has been replaced by mining or refinery apparatus.

===Mach-Rassvet Research Anchorage - Zavodskoi Interstellar Valkyrian Outpost===

The Mach-Rassvet Research Anchorage is one of the more recent developments located on Valkyrie and was opened in 2445 after a brief auction in which [[Zavodskoi Interstellar]] (Previously Necropolis Industries) acquired the rights to the territory. Initially meant to be a genetics research facility, Zavodskoi Interstellar’s retraction from the field of genetics instead prompted the development of a ConTec Facility that primarily focused on positronic research and development manufacturing. Almost two decades after it was founded, the Mach Rassvet Research Anchorage is still producing the majority of the components necessary to construct integrated positronic chassis in Biesel. These assets continue to sustain the income of Zavodskoi Interstellar.

===Valkyrie Exchange Terminal - Neutral Valkyrian Outpost===

The Valkyrie Exchange Terminal is not so much a cargo terminal as it is a small city dug into an equatorial trench spanning a tenth of the moon’s surface. The Terminal contains the largest shipping infrastructure on Valkyrie; everything needed for the transport of goods, from the launch infrastructure, warehouses, and boarding areas are present within the Terminal. In addition, the [[Tau Ceti Foreign Legion|TCFL]] maintains its shipyards within the terminal, maintaining its eclectic fleet. The Legion assists in the operation and enforcement of the Terminal's Air Traffic Control, which is responsible not only for incoming and outgoing vessels but also for tracking ships and stations within the moon's orbit with satellites. It serves as the closest thing the planet has to a capital city, with the moon’s government conducting its business from a skyscraper overlooking the Terminal.

== Life on Valkyrie ==

Valkyrie is home to the largest trade infrastructure in the Republic of Biesel, with the moon being surrounded by a ring of orbital stations that handle what is generally regarded as the heaviest space traffic in human space. Just as many ports exist on the surface of the moon, ferrying cargo and people to and from the orbit of the world. Most ships doing business in Tau Ceti will stop at least once on the moon, usually for repairs or refit. The sheer amount of traffic on the moon has led to it being constantly visible in Biesel’s sky, even during the day.

Valkyrie is a melting pot of peoples and cultures due to its status as a port. Most inhabitants of the moon are migrants; workers brought in by the corporations or simply remaining on the moon due to its proximity to work opportunities. As a result, Valkyrie holds an amorphous blend of cultures, most notably from the surrounding systems. It’s not uncommon for a Valkyrian dock to be staffed by a Solarian, Biesellite, [[Empire of Dominia|Dominian]], and [[Background summary#The Free Frontier|Frontiersperson]] all at the same time.
Gaining residency in Valkyrie is regarded as even laxer than the rest of the Republic, with the sheer amount of comings and goings rendering it impossible for everyone to be tracked. As a result, the local government has adopted a very open policy with immigrants, nearly to the point of settler rights. If a person lives on the moon and is willing to vouch for them, they are almost always granted residency.
That being said, a minority of permanent [[Offworlder Humans|offworlders]] has established themselves on the colony, having lived there since the Republic first colonized the moon. These offworlders are typically given managerial positions in the local industries, owing to their experience in the affairs of the moon.

===Hephaestus’ Valkyrian Dream===
For many of those fleeing the desolate [[The Wasteland|wastelands of Moghes]], Valkyrie was a promised land in which they could achieve their dreams if they had the strength to carve themselves an existence within the Republic of Biesel. Hephaestus’ influence on both the species and the moon resulted in the megacorporation’s franchisement on the “Valkyrian Dream” which branded the migration as a “necessary risk” that would reward them greatly, only should they be strong enough to prove themselves as worthy settlers. This has evolved into a mentality where hard work isn’t enough, and inhabitants of the barren moon must go above and beyond for those are the people which Valkyrie rewards.

The growing presence of [[Unathi]] has resulted in Hephaestus’ increasing dependency on the species to continue propping up their facilities across Valkyrie. While initially brought across as cheap labour, Unathi have managed to seep into almost every aspect of Valkyrie, even finding themselves rising through both civil and corporate ranks into positions of power — cementing the “Valkyrian Dream" ideology amongst many of them.

Guided also by the Valkyrian Dream movement, as well as general Hephaestus management of the area, the [[Vaurca Hives#K’lax|K’lax Hive]] has managed to establish on the Biesellite moon. The conditions of those living in Valkyrie are often considered to be less than ideal, but an improvement nevertheless when compared with Mendell. The population of K’lax largely encompasses Workers, many of whom are involved in the extraction and refinement of minerals. However, [[Leto, The Seeker|Leto]] has also settled some of her brood’s best xenoarcheologists here, mostly because of a belief that the phoron deposits in Tau Ceti somehow travelled from [[Sedantis I|Sedantis]]. [[Vedhra, Princess of Configurations|Vedhra]], in partnership with Hephaestus, has managed to position some of her own inside government office jobs, as well as general employment in the Exchange Terminal.
</div></div>
{{Navbox Human Lore}}
{{Navbox Lore}}

[[Category:Pages]]
[[Category:Planets and Systems]]
[[Category:Humanity]]

User:Caelphon/Sandbox

2022-12-14T12:22:15Z

Lucaken: Makes the wording of the last event more in-line with actual events.

{{toc_right}}
{| id="mp-eventarc" style="width:65%; background:#963283; text-align:center; margin-top:1.2em; margin-left:2em; border:4px solid #ccc;"
| style="width:56%; color:#000;" |
<div style="font-size:162%; border:2px solid #ccc; margin:0; background:#602956; padding:.1em; color:#fff;">Consequences of the Future</div>
<center>
{{Template:2022 Event Timeline}}
<div style="font-size:110%; border:2px solid #ccc; margin:0; background:#602956; padding:.1em; color:#fff;">This is the overview and timeline page for the Consequences of the Future arc, which began on '''11/02/2022''' and pertains largely to interstellar affairs.</div>
<div style="font-size:110%; border:2px solid #ccc; margin:0; background:#602956; padding:.1em; color:#fff;">
</div>

<div style="font-size:110%; border:2px solid #ccc; margin:0; background:#602956; padding:.1em; color:#fff;">Below is a summary of the arc's events, applicable news articles and additions.</div>

<div class="toccolours mw-collapsible mw-collapsed">

=Orchard Moon Complete; Icarus Arrives=
'''News Article'''

'''Publisher : The Orion Spur Oracle'''

'''Writer : Caelphon'''

'''Editor : The Lore Team'''

The NDV Icarus arrives to the NSS Orchard Moon, stationed there to protect it in the event unsavoury aspects of the Spur wish to see its downfall. The NSS Orchard Moon is completed, and is commencing extraction and refinement operations for phoron.

<div class="mw-collapsible-content">

Construction has been completed on the NSS Orchard Moon, supposedly the Orion Spur’s saviour. It finds itself nestled within an array of deep space asteroids inhabiting the southern Corporate Reconstruction Zone. However, the Orchard Moon deposits are less than the ones found across the Clandestine deposit, they will still bring much-needed relief to the phoron scarcity that plagues the interstellar community.

NanoTrasen has confirmed that the NDV Icarus has been dispatched to ensure the protection of the NSS Orchard Moon in a capacity similarly seen when it was stationed in close proximity to the NSS Aurora; which has now seen itself in a diminished capacity as a result of the decreased phoron deposits.

The Stellar Corporate Conglomerate has affirmed that this is a venture solely by NanoTrasen and that it will not have a share within the facilities. However, NanoTrasen has announced its intention to work closely with the other constituent megacorporations of the Conglomerate that have proven to be invaluable to the future of the Republic of Biesel, and its sovereignty that has been tried and tested numerous times.

Date: 11/02/2464

</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
=Consequences of the Future: Arming Up=
'''Event'''

'''Location : The SCCV Horizon'''

'''Host : Caelphon'''

11/05/2464

The first event of the Consequences of the Future Arc

<div class="mw-collapsible-content">

The SCCV Horizon must rendevous with the NSS Orchard Moon, following the events of [[Dreary Futures]] in order to be outfitted with naval armaments that will allow it to defend itself and corporate interests. The Crew was allowed to tour the NSS Orchard Moon and see various aspects of the facility on display.

</div></div>

<div class="toccolours mw-collapsible mw-collapsed">

=Tau Ceti Foreign Legions reports to Valley Hale=
'''News Article'''

'''Publisher : The Orion Spur Oracle'''

'''Writer : Caelphon'''

'''Editor : The Lore Team'''

The Tau Ceti Foreign Legion is redirected to the Valley Hale region of the Orion Spur following their staged removal from Mictlan, where they've been sent to ensure the protection of the corporate facility the NSS Orchard Moon, complimenting the NDV Icarus' presence.

<div class="mw-collapsible-content">

Following their staged removal from Mictlan, the Tau Ceti Foreign Legion has been reassigned to the Valley Hale region of the Orion Spur, with President Joseph Dorn of the Republic of Biesel announcing the movements to ensure the protection of the NSS Orchard Moon and the valuable mineral that it intends to harvest. Some fear the deployment of troops so close to the Serene Republic of Elyra may worsen the tension – with the latter still alleging that there has been territorial encroachment.

Some of the Tau Ceti Foreign Legion has already arrived, supplementing the NDV Icarus and its patrols throughout the region, with claims that there have already been minor border skirmishes with unknown parties – a spokesman for the Legion confirmed that this might pose a threat to the armed forces’ ability to meaningfully exert control, but with the presence of NanoTrasen’s warship, will likely be dealt with quickly and efficiently.

When asked to comment, both NanoTrasen and the Republic of Biesel reported that hostile parties have been engaged in Valley Hale but both were quick to deny theories that the Serene Republic of Elyra was responsible for the attacks, stating that the idea is "unfounded and fear-mongering in nature" and that while the region is well within the borders of both Republics, warlords from the former Solarian territories, pirates hailing from the Empire of Dominia, and other rogue parties are known to operate in the region. It is believed that fears of Elyran attacks on Biesellite vessels stem from a false report of an incursion on the SCCV Horizon, which has been denied by all parties involved.

The NSS Orchard Moon is expected to allow normalcy to return within the next few months, with travel in the area by Stellar Corporate Conglomerate vessels steadily increasing as the vital phoron-extraction facility continutes to soldier on in earnest. NanoTrasen has reaffirmed its goal of working closely with the other megacorporations regarding the facility, quoting the success of the NSS Aurora following the integration of contractors from other megacorporations that now make up the Stellar Corporate Conglomerate.

Date: 11/09/2464

</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
=Consequences of the Future: Kobayashi Maru=
'''Event'''

'''Location : The SCCV Horizon'''

'''Host : Caelphon'''

11/12/2464

The second event of the Consequences of the Future Arc

<div class="mw-collapsible-content">

The SCCV Horizon's crew enters a virtual reality against a Solarian Cruiser, the SAMV Everest, in order to test its naval gunneries. The Crew does remarkably well in the face of certain doom, with the SCCV Horizon evacuating shortly after Command declared victory an impossible task.

</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
=Consequences of the Future: Operation Altalaq=
'''Event'''

'''Location : The SCCV Horizon'''

'''Host : Lucaken'''

11/17/2464

The third event of the Consequences of the Future Arc

<div class="mw-collapsible-content">

The SCCV Horizon encounters an attack force of the Free Solarian Fleets ("Kruger's Revenge) and an Elyran Special Operations Taskforce ("Bridge Burners") facing off one another. The SCCV Horizon intervenes, saving the Bridge Burners and launching an attack against Kruger's Revenge. Following being saved, the Elyran Special Operations Taskforce reveals information to the SCCV Horizon about unsavoury elements of the Southern Fleet Administration and their supposed involvement in a recently missing tanker moving phoron.

</div></div>

<div class="toccolours mw-collapsible mw-collapsed">

=Southern Fleet Administration Behind Skirmishes=
'''News Article'''

'''Publisher : The Orion Spur Oracle'''

'''Writer : Caelphon'''

'''Editor : The Lore Team'''

The Tau Ceti Foreign Legion, in conjunction with the NDV Icarus, uncover that the Southern Fleet Administration is behind the skirmishes within Valley Hale. Furthermore, evidence suggests [[Einstein Engines]] is behind the decayed organisation's recent resurging.

<div class="mw-collapsible-content">

The Tau Ceti Foreign Legion, alongside the NDV Icarus, engaged in several fleets earlier today – where it was revealed the culprit behind the attacks within the region: the Southern Fleet Administration. Though they posed a threat to the Stellar Corporate Conglomerate’s Flagship the Horizon, it was thought that the group had moved on to less high-profile targets, but the discovery today only further outlines that they seem to be remaining within Valley Hale, and possibly other regions within the galactic south.

Following the brief conflict, Biesellite and auxiliary corporate forces boarded the remnants of the Southern Fleet Administration, stumbling on a rather crucial finding – Einstein Engines technology, which poses a question as to whether it was stolen, or possibly even provided. Though, Einstein Engines has denied the involvement in these wandering warlord remnants. Tension appears to have lessened between the Serene Republic of Elyra and the Republic of Biesel, with confirmation from the Stellar Corporate Conglomerate that they are working with intelligence provided by Elyran authorities – attempting to recover the location of a tanker that went missing shortly after departing the NSS Orchard Moon.

Date: 11/27/2022

</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
=Consequences of the Future: Venator =
'''Event'''

'''Location : The SCCV Horizon'''

'''Host : Lucaken'''

12/03/2464

The fourth event of the Consequences of the Future Arc

<div class="mw-collapsible-content">

The SCCV Horizon uncovers a trail of phoron leading within the Badlands, eventually discovering a Southern Fleet Administration hideout that reveals a sinister plot against NanoTrasen - aiming to destroy the NSS Orchard Moon with a dirty warhead composed of phoron stolen from various tankers attacked within Valley Hale.

</div></div>

<div class="toccolours mw-collapsible mw-collapsed">
=Consequences of the Future: Thunder in the Orchard =
'''Event'''

'''Location : The SCCV Horizon'''

'''Host : Lucaken'''

12/07/2464

The fifth and final event of the Consequences of the Future Arc

<div class="mw-collapsible-content">

The SCCV Horizon, and numerous other corporate fleets, are directed to the NSS Orchard Moon to delay and prevent an attack on the facility. The Southern Fleet Administration launched an assault on the NSS Orchard Moon with the SFAV Helios - a dilapidated, jury-rigged cruiser housing the photonic warhead - with numerous other corvettes distracting those on the frontline. The SCCV Horizon's distance from the initial incursion allowed it to detect the SFAV Helios break the frontline and attempt to deploy the warhead and engage it almost immediately. After a costly conflict for both sides, the SFAV Helios was disabled and several of the SCCV Horizon's crew boarded -- unfortunately, many lost their lives in the process, but successfully prevented the warhead from detonating and throwing the Orion Spur into further disarray. The SCCV Horizon itself sustained heavy structural damage, but nevertheless proved itself to be capable of much more than research and discovery.
</div></div>

<div class="toccolours mw-collapsible mw-collapsed">

=NSS Orchard Moon Attacked=
'''News Article'''

'''Publisher : The Orion Spur Oracle'''

'''Writer : Caelphon'''

'''Editor : The Lore Team'''

The NSS Orchard Moon was attacked by the Southern Fleet Administration's remnants, headed by rogue Commodore Anastasija Siljan.

<div class="mw-collapsible-content">

The NSS Orchard Moon was attacked just days ago by the dilapidated Southern Fleet Administration, which had been routed by the Nralakk Federation earlier this year, with the intention of bringing an era of chaos across the Orion Spur by destroying the corporate installation with a dirty phoronic warhead that is suspected to have had sufficient tonnage to level the entirety of Mendell City. It is unknown how it was created, and probes by NanoTrasen have commenced, but a combination of efforts has prevented additional harm from befalling the Spur.

The NDV Icarus, SCCV Horizon, and several other spacecraft were ordered to the NSS Orchard Moon to assist in repelling an attack from a force of unknown composition, with NanoTrasen relying on the SCCV Horizon’s advanced sensors to uncover details on the exact SFA vessels that wished to attack the corporate installation. The NDV Icarus held the line as it used its carrier-class status to secure the NSS Orchard Moon; however, the SFAV Helios managed to break the frontline, a refitted cruiser hosting the phoronic warhead, gutted of any significant ability to protect itself in order to host the enormous explosive.

The SCCV Horizon provided necessary sensor data to the other fleets within the area. It was the only vessel available to prevent the SFAV Helios from reaching its destination – engaging with the Helios and subsequently boarding it. It is without a doubt that the Orion Spur owes great gratitude to those that defended the NSS Orchard Moon, but especially to the SCCV Horizon and those that gave their lives to ensure that the lives of billions of others – in the ensuing chaos should the NSS Orchard Moon have been destroyed – will not be lost.

The Serene Republic of Elyra announced their gratitude to the Republic of Biesel, and the Stellar Corporate Conglomerate, regarding their handling of the situation – thanking them both for averting a crisis on the shared borders of the two Republics. Additionally, President Joseph Dorn thanked the Serene Republic of Elyra for providing the information needed to prevent the destruction of the NSS Orchard Moon.

The rogue Commodore Anastasija Siljan was detained by the Stellar Corporate Conglomerate following her failed attack on the corporate facility, and has been taken to an unnamed site to undergo advanced interrogation to further learn of any plots that the Southern Fleet Administration may have planned with the goals of unfolding the Republic of Biesel – and subsequently the Orion Spur.

The Stellar Corporate Conglomerate has affirmed that injuries sustained whilst off-duty during the attack on the NSS Orchard Moon will be covered by the corporate medical schemes for only the unfolding events that took place on Saturday, 10th of December 2464. Injuries sustained following the conclusion of the attack will not be covered by the Conglomerate or its affiliated megacorporations.

Date: 12/12/2464

</div></div>

Lore Staff Guidelines

2022-11-25T12:04:30Z

Lucaken: Changed 'null' to 'Lucaken as Deputy Loremaster

This thread is a comprehensive and definitive collection of the procedures and regulations of the lore team. It outlines the expectations and responsibilities of lore writers and the lore team administration. It includes “how-to” guides on wiki development, writing articles, and handling whitelist applications. It also includes a code of conduct, staffing procedures, and an explanation of the powers of lore team administration.

'''Disclaimer: All previous rules not contained within this thread are null and void, and anything in this thread which contradict previous policy supersede those previous policies. Any additions or edits to this thread will be announced to the whole lore team.
'''

== THE LICENSE - YOUR RIGHTS AS A WRITER ==

All work written after 13 August 2019 for the server is licensed under CC BY-SA 4.0. The license only applies to text as it is written. Ideas, names, and concepts are not subject to copyright.

Full license of CC BY-SA 4.0 can be found here: https://creativecommons.org/licenses/by-sa/4.0/legalcode

Simplified summary can be found here: https://creativecommons.org/licenses/by-sa/4.0/

All work which is written for use by the server is licensed under this.

== THE LORE TEAM HIERARCHY ==

The heads of the lore team are the Loremaster and Deputy Loremaster, referred to throughout this thread as either “Lore Team Administration” or “Lore Team Management.” Your current administration is Caelphon as Loremaster and Lucaken as Deputy Loremaster.

Under the management of the lore team administration are the lore departments, each headed by a lore writer. These departments are based on each major race in our server’s setting. The departments are Humans, Skrell, Unathi, Synthetics, Diona, Vaurca, and Tajara. Each lore writer may choose to have up to two deputies to assist them in their duties.

== HOW-TO GUIDES ==

=== NEWS ARTICLES ===

There are a variety of news organizations in the galactic news database on the forums. Articles are an important feature of living lore and let us tell stories and arcs in real time by providing everyone with in character news updates from around the setting. These serve as important storytelling tools which the whole server can read. When writing an article, the content of a news article can be anything from war reports, political and economic drama, sports news, advances in technology, or even dramatic retellings of events that occurred on the server. While the writing can be just about anything a writer chooses, here’s a few key things to keep in mind when writing an article.

1. Only write articles for news agencies which are under the jurisdiction of your lore department. If you are a deputy, make sure your direct superior approves of your article before posting it. If you are writing an article which is under the jurisdiction of another team, first get their approval before posting your article. EXCEPTION: Mendell City and Tau Ceti based channels are a common area for the whole lore team. However, any articles submitted to these channels must be reviewed by lore team administration.

2. Respect the formatting and voice of the news channel you are writing for. Most of the news channels in the galactic news database have a specific formatting and bias associated with them. If a channel has a header in all of its articles, include it. If it's formatted in a specific way from dates and times to spacing or even font, use that as well. If the channel is biased or written in a certain way, maintain consistency by keeping that same “voice.” While these can and have changed over time, it should be done with careful consideration, and should never be done by deputies or other departments without the approval of the relevant lore writer.

3. Never use news articles as a vehicle for retcons. When writing an article, make sure to carefully read any relevant previous articles to ensure retcons or contradictions do not occur. Articles are the highest visibility form of lore writing off-server, and contradicting previous articles may cause great confusion with the news reading community.

4. Coordinate with relevant writers when writing your articles. If you article prominently features another department’s race, you must gain their approval before posting your article. This is to ensure that their race is portrayed appropriately and consistently with that writer’s canon and does not contain contradictions. In general, you want to coordinate with any interested lore team members as much as possible using the coordination channels. This way you can gather as much feedback as possible and improve the consistency of our lore. When articles consist of large arcs or major changes to the setting, you must get the approval of lore team administration before posting it. Examples of these would be starting wars, major changes in international politics and trade, changes in national leadership, the larger galactic economy, or the destruction of major planets.

5. All edits, changes, or deletion of past articles must be approved by Lore Team Management. This is important for quality control. If previous articles must be tampered with or even archived and removed from circulation to facilitate changes to lore, they must be approved by lore team administration as an important check for the far reaching consequences it may have on our shared lore setting.

6. Lore Team Management reserves the right to curate lore in news articles. This means if you post an article which contradicts one of the above points, or otherwise is deemed unacceptable to the direction of the server’s lore, the loremasters reserve the right to edit, modify, retcon, or even delete any violating articles. All relevant writers will be notified and in the case of deletion or retcon, an announcement will be made to the community. If the writer displays malicious intent in violating the rules when posting such an article, disciplinary action may be taken. However, if it is the result of an unintentional creative difference, no disciplinary action will be taken.

=== HOW TO RETCON NEWS ARTICLES ===

Over the course of years of lore development older articles become defunct in their nature. Whether they are forgotten and new lore which directly contradicts them is made, or they become incompatible with changes in lore over time, the need to remove old articles crops up. Follow the Major Retcons guide and rules in the Wiki Development section of these rules and regulations in order to have retconned news articles archived. All articles that are archived will be announced to the community and a description of why it was no longer canon will be affixed to the article in the archive.

=== WIKI DEVELOPMENT ===

The wiki is an invaluable resource for creating our universe. It also should importantly serve as a place to summarize our news articles in a way that is quick and easy to digest. It is the number one resource for describing the lore of our races and nations, and for whitelist applicants and whitelistees alike. Lore on the wiki can be anything and everything, providing a great depth for our playerbase to enjoy and a deeper story telling for the community. Wiki pages provide a guide for how players should play from different races, factions, and cultures. It also helps them to contextualize and understand the ramifications of developments in news articles. While the content on the wiki can bring a wealth of great variety, when deciding on formatting you should maintain some consistency with other lore pages. Make sure to consult with other lore writers and the wiki maintenance team when you are unsure of the appearance of a wiki page. Pictures and captions can greatly help break up word walls and make for far more appetizing content. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. Here are the key points you want to keep in mind when creating wiki pages and wiki content:

1. Only edit or create pages within your jurisdiction. Writers should only create and edit pages within their own department. Any additions or changes to another lore department must have the approval of their writer. Deputies must likewise gain the approval of their respective writer before publishing content to the wiki. EXCEPTION: Mendell City and Tau Ceti based pages are a common area for the whole lore team. However, any additions or changes to these pages must be reviewed by lore team administration.

2. Maintain consistency with other lore pages. Unless a retcon is intentional, other lore pages related to your subject should be carefully considered. While the wiki is the primary location for retcons, we want to make sure all changes are intentional and carefully deliberated. All major retcons must follow the Major Retcons process.

3. Coordinate with all relevant writers. If your wiki page has content which prominently features races, factions, cultures, religions or nations of another department’s jurisdiction, coordinate with them and gain their approval before publishing your content. This is to ensure that their portrayals are consistent. In general you want to coordinate with all interested writers for feedback in the coordination channels on the staff discord.

4. Avoid the WIP status on pages. Any pages which are writing in progress for substantial periods of time without active development are subject to deletion under the maintenance of the wiki maintainers. Set deadlines for yourself to complete in-progress pages in a timely fashion and communicate these to others to avoid deletion.

5. Avoid superfluous pages. If a page you are creating is sufficiently small enough, please cannibalize it into any relevant pages to enhance the ease of navigating our lore. Only create a new page if the information it contains is substantial enough in size to not be acceptable on another relevant page. As a general best practice, avoid writing content which is not compelling enough to contribute to the overall server lore or otherwise largely irrelevant to either the station, the setting, the factions in the setting, or the players of any relevant races.

6. Lore Team Management reserves the right to curate lore in wiki content. If pages are sufficiently unnecessary, underused, or do not contribute to player engagement to lore they may be subject to moderation such as edits, additions, changes, and deletions. None of these actions will occur without prior notice and discussion of alternatives with the relevant lore writers.

7. Lore about reproductive organs, namely genitals, is forbidden.

==== MAJOR RETCONS ====
In order to formalize a review process for retcons in our lore, all major retcons must first have a feedback thread on the lore staff forum for the duration of no less than 72 hours and no more than one week before it may be implemented. These feedback threads will then be announced to the lore team where they will be allowed to input criticisms, praises, and suggestions. After one week, the Lore Master will then have to choose if the retcon will go into effect. If the Lore Master is unsure about their decision, or if suggestions in the threads are determined to be necessary and may take some time to include, the Lore Master may delay the decision by a maximum of 72 hours, unless the lore developer making the proposal requests more time to make changes based on suggestions. No major retcons may take effect until this process has been completed and the Lore Master has agreed to implement the proposed changes.

A major retcon is defined as moderate to large changes in pre-existing lore, such as species rewrites, history reworks, deletion or removal of existing content, or any significant reworking of lore-based wiki pages.

The following '''does not''' qualify as a major retcon: Spelling corrections, formatting changes, general corrections to syntax or grammar, rewording the same sentences, any new lore additions which do not intentionally contradict pre-existing lore, corrections to mistakes such as wrong dates or names, small changes which have minimal impact on the overall culture and narrative of its field in our lore.

If the Lore Master feels a major retcon may require wider community input, the Lore Master may bring the proposed retcon to the public for feedback within this one week window, either on the forums or one of the official discords.

If you are unsure if a retcon would be a minor or major retcon, or if it would need this review process, '''ask the Lore Master''' or Lore Master Deputy. Always inform the loremaster before posting a retcon feedback thread to the forums. Although the Lore Master must be informed and has discretion if a major retcon may take effect, the Lore Master may not refuse to allow a lore developer from beginning the major retcon feedback process.

=== WHITELIST MANAGEMENT ===

==== GRANTING A WHITELIST ====
Whitelists may only be granted following a whitelist application process, unless special permission for a specific case has been granted by lore team administration. However, lore team administration may never grant itself special permission to dispense whitelists, even in the case of a lore writer vacancy.

==== PROCESSING WHITELIST APPLICATIONS ====

Discretion on whether to accept or deny a whitelist application rests with the writer for the relevant lore department. Applications may be accepted or denied entirely at a writer’s discretion. For best results, a lore writer should carefully check the application against any relevant wiki pages and take feedback in an application thread into consideration. A race’s main wiki page should contain all of the relevant core content required for a whitelist application. If an application has any work which contradicts other wiki pages under the care of a lore department, the applicant should be worked with to bring their application in line with the overall lore instead of denied outright. Once an application is accepted or denied, a tag should be edited into the title saying either [Accepted] or [Denied]. The thread must then be locked and moved into the whitelist applications archives.

After an application is accepted, in order to grant the whitelist you must log into the web interface at https://byond.aurorastation.org/ and search for their ckey in the players category under the admin tab. Once you have found their profile on the web interface, click the “add whitelist” button next to the relevant whitelist. A general best practice is to discuss the contents of an application with the applicant and provide the opportunity to correct for any discrepancies before making a decision. An application must stand for a minimum of 24 hours before a ruling on the application can be made. This is in order to provide time for feedback to be posted on the application. An application must receive input from the relevant lore writer within 72 hours. If you need more time you must say so in the thread along with a tentative self-imposed deadline on when a decision can be expected. Discussing the application and any possible issues with the applicant, demonstrating active engagement with the application, provides flexibility to the deadline by which the application must be decided on. If no input from the relevant lore writer is forthcoming after 72 hours, the applicant may reach out to lore team administration.

Multiple requests will be issued to the relevant lore writer until they do something about the application. Failure to handle the application will result in lore team management handling the application at their own discretion. The results of an application being handled at lore team management’s discretion is that the decision cannot be grounds for reversal and whitelist granting or stripping. The decision is final and the whitelist can only be stripped through violation of whitelist expectations over the course of play, or granted through another application. In the absence of a lore writer in a lore department, the lore team administration must handle the whitelist applications or delegate it to a relevant lore department deputy.

'''Addendum #1'''

Applications that find themselves being denied due to administrative actions, lack of display of the knowledge of a species’ lore, or any other reason must wait a certain amount of time before applying, chosen by respective species' Lore Writers from the following: three days, a week, two weeks, a month, and two months. The initial denial of an application cannot be extended beyond two months. It must be reapplied upon the denial of the reapplication should behaviour not have improved, or not displaying adequate knowledge of the species’ lore to the expectations of the species’ respective Lore Writers. It is within the jurisdiction of the species’ respective Lore Writers to set additional requirements for reapplication, outside of the prescribed time constraints. A species’ Lore Writers may deny an application due to information that has remained confidential to the wide public. In such cases, the specific behaviours which should be improved should be discussed in private, if they can be improved upon. If a player believes they are being denied for unfair reasons, they are entitled to lodge a staff complaint against the denying staff member(s). If a time constraint regarding reapplication was issued by a Lore Writer that is no longer on the Lore Team, it will persist until the allocated time constraint has been completed.

==== STRIPPING WHITELISTS ====

Whitelists are for managing the quality of roleplay of whitelisted races. If the quality of roleplay a whitelisted player engages in is contradictory to the lore of the whitelisted race, or demonstrates a lack of understanding for the whitelisted race’s lore, their whitelist may be stripped. To remove a whitelist log onto the web interface at https://byond.aurorastation.org/ and search for their profile in the players category through the admin tab. Once you have found their profile, click the “remove whitelist” button next to the relevant whitelist. For a best practice, a whitelist must never be stripped without good reason. Warnings should be issued prior to stripping a whitelist to allow for correction in their behavior. The amount of warnings before stripping a whitelist is at the discretion of the relevant lore writer. Keep a log of warnings issued to whitelisted players for accountability to lore team administration. For conduct which is especially egregious, a whitelist may be stripped without prior warning. For proper guidance on handling whitelist management, consult lore team management when unsure. Stripping whitelists without appropriate cause may result in disciplinary action. However, lore team administration should be lenient and handle these situations on a case to case basis.

=== EVENTS ===

Spoiler
TBA, refer to the following thread for the time being: [https://forums.aurorastation.org/topic/11560-how-to-events/]

==== CANONICAL DEATHS IN EVENTS: ====

From the server rules:

"Happenings related to canon events, usually ran by admins with the guidance of lore staff, are considered canon. The lore writer and the admin coordinating the event can make exceptions if permitted by the lore masters and the headmins. In the case of character death caused by the canon event, the death is considered canon and permanent unless the lore masters and headmins permit the character to undergo the cloning procedure."

This only applies to deaths related to the canon event. The other canon and death rules are still valid, this applies only to stuff that happens due to the event itself.

== LORE TEAM EXPECTATIONS AND STAFFING ==

=== LORE TEAM ADMINISTRATION ===

The lore team administration consists of the loremaster and deputy loremaster. They are at the head of the lore team and steer the direction of our game’s direction in story telling. They are responsible for curating the content of our official lore in all forms, managing the lore team, staffing lore departments, handling neglected whitelist applications, and mediating disputes between different lore departments. The loremaster cannot concurrently serve as a lore writer or lore deputy. The deputy loremaster may concurrently serve as a lore writer. This is to prevent the loremaster from having a bias when writing lore, and to help them to serve as an impartial arbitrator when discussing the direction of our lore and disputes between different lore departments. The loremaster is appointed by the server’s head developers and in turn appoints their own deputy loremaster, typically through an application process. The loremaster has the power to take disciplinary actions against lore writers and deputies only with the approval of the deputy loremaster. The loremaster may only staff lore writers through an application process which provides the community with the opportunity to provide their input, and cannot directly appoint a lore writer without observing the process. Lore team administration may not appoint deputies, however all lore deputies must be approved by lore team administration before their applications can be accepted. The requirements for the lore writer application process are at the discretion of lore team administration. Lore deputy hopefuls must also go through the application process before they can join the team. In the event that there is a lore writer vacancy, jurisdiction over that department is absorbed into the responsibilities of lore team administration, but the duties associated with it may be delegated to any deputies within that department. Even in the event of a lore writer vacancy, the loremaster may not appoint deputies to that department but must appoint a lore writer first who may then select their deputies within the rules. Lore team management is expected to be active in both the management and editorial review of content, and in interaction with the community through discord, forums and server play. Lore team management is expected to set the example in both lore writing and code of conduct.

=== LORE WRITERS ===

Lore writers are the departmental heads of the lore team. Each lore writer is in charge of a major playable race of our server’s setting, and handles all of their lore and manages the whitelists associated with their jurisdiction. Lore writers are appointed by lore team management through the developer application process. Writers are expected to be active in both terms of lore writing and server play. They are expected to maintain consistency between their news articles, wiki pages, and on-station events. They are expected to follow the rules laid out in the “How-to” guides above. Writers are also expected to coordinate with their fellow writers in their projects and to uphold the code of conduct in their interactions with each other, their fellow staff, and the community. They are allowed to appoint up to two deputies through the developer application process and may delegate any of their duties to their deputies as they see fit. Lore Writers reserve the right to modify the application process when selecting their deputies to any extra requirements they desire, and cannot be forced to accept deputies against their will by lore team administration. A lore writer cannot concurrently serve as the writer for multiple lore departments and is ineligible for lore deputy positions. However, a lore writer can concurrently serve as deputy loremaster.

=== LORE DEPUTIES ===

Lore deputies are the appointed help of lore writers who assist by performing any tasks delegated to them by their lore writer, or lore team management in the absence of a direct superior. They are the de facto proteges of their writer and should be trained as heir apparents by their superior. Despite this, lore team management reserves the right to appoint other applicants to lore writer positions when vacancies occur. A lore deputy cannot serve in multiple deputy positions simultaneously. If a lore deputy would like to apply for a different deputy position, they may apply but if accepted must forfeit their previous position. Lore deputies are not expected to manage an entire lore department unless there is a lore writer vacancy in their department. Even though lore deputies have decreased responsibilities when compared to writers, they are still expected to maintain a degree of activity in both lore writing and on-server play. Like everyone else on the lore team, deputies are expected to abide by the code of conduct in their interactions with their team members, fellow staff, and the community.

== CODE OF CONDUCT ==

1. All members of lore team are expected to maintain property civility and respect to their team members, fellow staff, and the community. Insults, harassment, or hate speech to any members of the community may be subject to disciplinary action. As members of staff, lore team is expected to be an example of good behavior to the community, and ideally, even to other staff. Observing decorum, whether in public or debating fellow team members in staff channels or private messages, is a requirement for continued participation in lore team.

2. All members of lore team are expected to be active. Activity requirements are to be met in a composite of interaction with the community and fellow staff on discord, the forums, or the server. Large lapses of on-server play may be forgiven if there is a sufficient amount of lore writing and community interaction. Inactivity is determined at the discretion of lore team administration, however unless a team member has ghosted from server play for months of time and has not maintained any significant community or team interaction, a member will generally be considered active enough.

3. All leaves must be preceded with prior notice to lore team administration and the lore team. If a team member is going on leave they must notify the lore team, as well as ping or private message lore team administration with notice. Explanations for going on leave are not required, however a general estimate on when a leave is ending must be provided if available. If a lore writer goes on leave their duties are handled by lore team management unless otherwise delegated to relevant lore deputies. If the loremaster goes on leave, the deputy loremaster will assume the duties of lore team management in their absence.

4. All resignations must take place by informing lore team administration. While lore team administration will discuss the resignation intent with the relevant lore writer and lore deputies, lore team administration must be informed of any opening vacancies in order to notify the community and prepare the recruitment and staffing for the relevant team. A general best practice is for a lore team administration to conduct exit interviews with resigning team members in order to gain insight into the issues affecting lore team.

5. All procedures and regulations outlined in this thread must be followed. Failing to follow lore team procedures and regulations may incur disciplinary action, even if as a result of ignorance.

6. In the event that the loremaster is found to have engaged in a code of conduct violation, the deputy loremaster will handle disciplinary action against the loremaster. If a loremaster and lore writer or deputy are in a dispute over code of conduct or procedure, the deputy loremaster will mediate the dispute. If lore team management and a lore writer or deputy are in a dispute over code of conduct or procedure, head admins and developers will be asked to mediate and take any relevant disciplinary action. Staff complaints still maintain their full functionality, and this procedure does not infringe upon the rights of team members to file a complaint.

== DISCIPLINARY ACTIONS AND PROCEDURE ==

=== WARNINGS ===

A warning is a written notice from lore team administration to a lore team member requesting a behavioral or procedural correction. All warnings are confidential and may only be discussed with relevant parties, such as the heads of staff teams, injured parties, or relevant lore writers in the case of deputies and deputy applicants. All warnings are logged by lore team administration along with the date the warning took place and a brief description of why the warning was given. Older warnings will be weighed less when deciding future disciplinary actions. A “Final Warning” may be issued for violations which are significant enough to warrant termination, but where lore team administration would prefer to work with the lore team member to return to good standing. A final warning is not required for termination, and there is no minimum or maximum amount of warnings a lore team member can receive prior to termination. Usage of warnings is at lore team administration discretion. Warnings can only be assigned when there is a consensus to warn between both loremaster and deputy loremaster. Warnings are generally assigned by the loremaster, but can be delegated to the deputy loremaster or a lore writer, in the event of a deputy receiving warning. All lore writers must be notified prior to the warning of their deputies by lore team administration.

=== TERMINATIONS ===

Terminations are the last resort of disciplinary action and are the removal of a lore team member from the lore team against their will. Unless if a lore team member has received a permanent ban from the server or has committed a particularly egregious code of conduct offence, warnings will be issued before resorting to a termination. Terminations will be announced to the staff team, but will be announced as resignations to the wider public community. This is to prevent “dogpiling” or public ridicule from the wider community while keeping fellow staff informed of misconduct. In most cases, a lore team member will be asked if they wish to resign before a termination is issued, especially in the case of inactive team members. Termination is not a permanent ban from involvement in server lore nor from reapplying to lore team in the future. However, past terminations and warnings will be taken into consideration when former lore team members apply to positions.

== MISCELLANEOUS ==

In the event of any situation which is currently not covered by these rules, use your best judgement to ascertain the spirit of the law. '''Never be afraid to ask the Loremaster for guidance''' in any situation where you are unsure about the applicability of the rules and regulations, or code of conduct.