<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.stf-wiki.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Nicesociety</id>
	<title>Star Trek : Freedom&#039;s Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.stf-wiki.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Nicesociety"/>
	<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php/Special:Contributions/Nicesociety"/>
	<updated>2026-04-22T03:50:20Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.40.0</generator>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Retired_staff&amp;diff=55872</id>
		<title>Retired staff</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Retired_staff&amp;diff=55872"/>
		<updated>2012-09-05T16:18:25Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* Mission Eleven: Into the Darkness, Go I */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;toc colour&amp;quot; style=&amp;quot;margin: 0 0 1em 1em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:goldenrod&amp;quot; align=&amp;quot;center&amp;quot; |&amp;lt;font color=maroon&amp;gt;&#039;&#039;&#039;Ahmed Ibn Salid&#039;&#039;&#039;&amp;lt;br&amp;gt;&amp;lt;font color=maroon&amp;gt;Commanding Officer, USS Rosenante&amp;lt;/font&amp;gt;&amp;lt;br&amp;gt;[[File:IbnSalid.jpg|center|300px|Captain Ahmed Ibn Salid]]&amp;lt;br&amp;gt;&amp;lt;/font&amp;gt;[[File:Rosenante-Alt-2up.jpg|center|300px|USS Rosenante]]&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Vital Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Age: 38&lt;br /&gt;
**Gender: Male&lt;br /&gt;
**Birthplace: [[Cairo]], [[Egypt]], [[Earth]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Physical Information&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Eye Color: Brown&lt;br /&gt;
**Hair Color: Black&lt;br /&gt;
**Height: 5.5 feet&lt;br /&gt;
**Weight: 170 lbs&lt;br /&gt;
**Skin Color: Olive&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Career Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Rank: [[Rank|Captain]]&lt;br /&gt;
** Current Assignment: [[USS Rosenante]]&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Prior Assignments:&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
**Stardates: 2408.01.04 - 2408.01.06&lt;br /&gt;
**[[ Starbase Valhalla]] - [[Engineering|Engineering Operations Officer]]&lt;br /&gt;
**Stardates: 2407.07.09 - 2408.01.04&lt;br /&gt;
**[[USS Hypatia]] - [[First Officer]]&lt;br /&gt;
**Stardates: 2407.04.02 - 2407.07.09&lt;br /&gt;
**[[USS Champlain]] - [[First Officer]]&lt;br /&gt;
**Stardates: 2406.01.04 - 2407.01.22&lt;br /&gt;
**[[USS Nimitz]] - [[Engineering|ACEO, CEO]]&lt;br /&gt;
**Stardates: 2402.03.12 - 2406.01.04&lt;br /&gt;
**[[Starfleet Academy]] - [[Rank|Cadet]]&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;toc color&amp;quot; style=&amp;quot;border:3px solid goldenrod;&amp;quot;align=&amp;quot;center&amp;quot;;&amp;quot;width=246px&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:black&amp;quot; align=&amp;quot;center&amp;quot; |&amp;lt;font color=goldenrod&amp;gt;&amp;lt;small&amp;gt; {{quote|Being hugged by Commander Zzt isn’t that bad really...after you lose consciousness.|Ensign Junior Grade Ahmed Ibn Salid}}&amp;lt;/small&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==Childhood==&lt;br /&gt;
&lt;br /&gt;
Ahmed was born in [[Cairo]], [[Egypt]]- [[Earth]] on Stardate 2382.04.10 to Salid ibn Jaffar and Jasmine Mosatuff. At the time of his birth his father was an engineering ensign aboard the USS Roland and his mother was an artist.&lt;br /&gt;
&lt;br /&gt;
Ahmed lived in Cairo for the vast majority of his life, although he did spend a few years aboard the [[USS Roland]] and the [[USS Archimedes]] with his mother and father.&lt;br /&gt;
&lt;br /&gt;
At the age of five years, Ahmed’s parent’s divorced after Ahmed’s mother Jasmine was discovered to be having an affair, with the USS Archimedes’ Chief Counselor. Ahmed’s father, unable to raise the boy alone and without a desire to release him to his mother’s custody,sent young Ahmed back to Cairo to live with his Uncle Aamihr. Before leaving the Forrester, Ahmed’s mother gave him a necklace to remember her by. He still wears it to this day.&lt;br /&gt;
&lt;br /&gt;
Ahmed had a difficult time adjusting to his new life with his Uncle. When he reached his teens, Ahmed became rebellious and would often disobey his uncle’s wishes. In the interest of finding something to occupy his nephew’s time in a more productive manner, Ahmed’s uncle introduced the boy to [[Sailing]] and [[Boxing]].&lt;br /&gt;
&lt;br /&gt;
There were remarked improvements in Ahmed’s grades as a result of these new interests. It was discovered that he possessed a photographic memory and that he had become bored with his studies, since he could memorize the course curriculum within a few hours. Boxing and Sailing gave him physical challenges as well as mental ones, and he began to work in his uncle’s business, teaching tourists how to sail traditional Egyptian boats on the Mediterranean sea. Ahmed would often participate in unsanctioned boxing clubs in his teens.&lt;br /&gt;
&lt;br /&gt;
It was during this time that Ahmed began to take an intense interest in History. His uncle had revealed Ahmed’s rich family Lineage to the boy at the age of 17. The men in Ahmed’s family have dedicated their lives in the pursuit of Moral Justice. Ahmed began a detailed Genealogy of his male ancestors and was able to trace back his lineage to a general serving in [[Saladin|Saladin&#039;s]] army during the battles of the Crusades. He commissioned an incredible Genealogy scroll of his ancestors that is 4 feet wide and 9 feet tall. It is current displayed on the wall of his quarters aboard the [[USS Rosenante]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
On Stardate 2398.08.12 Ahmed was involved in a near fatal accident. While exploring a recently discovered Egyptian tomb in the [[Valley of the Kings]] with Doctor Sufi Mohammed Sari, a renowned Egyptologist, There was a collapse of a tunnel.&lt;br /&gt;
&lt;br /&gt;
Ahmed was badly injured. He suffered serious trauma in the form of broken bones. It took rescuers thirteen hours to free him from the rubble. As a result of these traumatic times, Ahmed suffers from a mild case of claustrophobia, although he is usually able to fight back the sense of panic that he feels.&lt;br /&gt;
&amp;lt;center&amp;gt;&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
image:Jasmine_Mosatuff_1.jpg|Jasmine Mosatuff in Syria&lt;br /&gt;
image:Salid_Ibn_Jaffar_2.jpg|Salid Ibn Jaffar&lt;br /&gt;
image:Uncle_Aamihr.jpg|Uncle Aamihr&lt;br /&gt;
&amp;lt;/Gallery&amp;gt;&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==University of Cairo==&lt;br /&gt;
&lt;br /&gt;
Ahmed enrolled in the University of Cairo on Stardate 2399.03.06 in the fields of Archeology, Ancient Medicine, and Ancient Engineering. He greatly enjoyed this area of study, but at the insistence of his professors and in messages received from his father, then the Chief Engineer aboard the [[USS Tripoli]], Ahmed finally agreed to take the [[Starfleet]] entry exams.&lt;br /&gt;
&lt;br /&gt;
He graduated with a Masters degree in Archeology from the [[University of Cairo]] on Stardate 2403.03.05.&lt;br /&gt;
&lt;br /&gt;
==Relationships of Note==&lt;br /&gt;
&lt;br /&gt;
[[image:debbie.jpg|thumb|left|&#039;&#039;&#039;Crewman Debbie Weston&#039;&#039;&#039;]][[image:Jasmin_Mohandas_1.jpg|thumb|right| &#039;&#039;&#039;Jasmin Mohandas&#039;&#039;&#039;]]&lt;br /&gt;
&lt;br /&gt;
Salid was involved in a romantic relationship with Engineer Debbie Weston while he was stationed aboard the [[USS Nimitz]] as [[Engineering|Chief Engineer]]. The relationship began to grow somewhat cool after Ahmed&#039;s participation in the Raid on [[Djorn Major XJ-003]]. &lt;br /&gt;
&lt;br /&gt;
The relationship broke up when Ahmed was promoted and assigned to the [[USS Champlain]] as [[First Officer]]. Weston and Ahmed are still friends and are on speaking terms. Ahmed visited the [[USS Hades]] after the end of the Civil War where he spoke once again with Debbie Weston. Debbie was interested in rekindling their relationship, but Ahmed resisted. His concern over maintaining a long distance relationship and his newly acquired interest in [[Jasmin Mohandas]] won out and Ahmed and Debbie agreed to end the romantic aspect of their on-again, off-again relationship.&lt;br /&gt;
&lt;br /&gt;
After the end of the [[Federation Civil War]], Ahmed returned to [[Cairo]] to visit his uncle. He was attacked by an angry mob in the city, as a result of his choice to wear his [[Starfleet]] uniform. He was beaten and struck with stones and lost consciousness. When he recovered he found himself in the home of Jasmin Mohandas. Jasmin had tended his injuries after rescuing him from the mob using a black market [[phaser]]. &lt;br /&gt;
&lt;br /&gt;
During the subsequent discussion, Ahmed discovered that she had been a [[Rank|Lieutenant]] assigned as [[Medical Officer|ACMO]] to the [[USS Pangaea]]. This vessel was a part of the [[Admiral Doenitz|Doenitz]] loyalist force that fought against the [[52nd Fleet]] at the Battle of [[Sector 001]]. Heated words were exchanged and Ahmed was asked to leave.&lt;br /&gt;
[[image:Jasmin_Mohandas_2.jpg|thumb|left| &#039;&#039;&#039;Jasmin Mohandas&#039;&#039;&#039;]]&lt;br /&gt;
&lt;br /&gt;
Several days later, Ahmed saw Jasmin in the local marketplace and apologized. He offered to make her dinner, which she accepted. The meal was terribly cooked, but Ahmed and Jasmin spoke more candidly afterwards and it was then that Ahmed learned that Jasmin was to go before a tribunal for her actions during the battle. After discussing the situation with her, he became convinced that she had done nothing to warrant a Court Martial.&lt;br /&gt;
&lt;br /&gt;
Ahmed spoke to Jasmin&#039;s JAG Officer for the defense and convinced him to allow Salid to speak as a character witness on Jasmin&#039;s behalf. After a hard-sell the counselor agreed and Ahmed was allowed to speak at the Tribunal. He gave an impassioned speech about &#039;&#039;&#039;&#039;&#039;&amp;quot;mercy&amp;quot;&#039;&#039;&#039;&#039;&#039; and &#039;&#039;&#039;&#039;&#039;&amp;quot;healing the wounds of the Federation&amp;quot;&#039;&#039;&#039;&#039;&#039;. It seemed to work, Jasmin was only reduced a single grade as a result of a guilty result of Medical Negligence, while she was found not guilty of the six charges of Murder brought against her.&lt;br /&gt;
&lt;br /&gt;
For several months, while the [[USS Hypatia]] was in Sector 001, Ahmed spent a great deal of time with Yasmin and his uncle Aamihr in Cairo. A young budding romance began between the two and despite the difficulties of a long-distance relationship, is still working.&lt;br /&gt;
&lt;br /&gt;
==[[Starfleet Academy]]==&lt;br /&gt;
&lt;br /&gt;
[[image:Stacademy.jpg|thumb|right|&#039;&#039;&#039;[[Starfleet Academy]], San Francisco, Earth&#039;&#039;&#039;]]&lt;br /&gt;
&lt;br /&gt;
Ahmed took his entry exams on Stardate 2403.06.05, just in time to manage to squeeze into the summer class. Ahmed scored the tenth highest entry exam scores in the history of the [[Starfleet Academy|Academy]], a fact for which he is extremely proud.&lt;br /&gt;
&lt;br /&gt;
He double majored at the Academy in the areas of Materials Engineering/Damage Control and Trauma Medicine. &lt;br /&gt;
&lt;br /&gt;
During his time at the academy, Ahmed joined the [[Boxing|Academy Boxing Team]], [[Sailing|Regatta]] and [[rowing]] teams. He took the Lightweight title for three of the four years that he competed at the Academy. As the captain of the Rowing team, led his crew to victory two years in a row. The Academy Regatta on [[Arctura II]] proved to be another victory for the [[Rank|Cadet]] Salid, as his crew and he took the cup in a ship named the [[Jasmine]].&lt;br /&gt;
&lt;br /&gt;
On stardate 2406.08.02 Ahmed participated in the famed [[Starfleet]] [[Academy Marathon]] on [[Danula II]]. This grueling race saw Ahmed finish 221st out of 693 competitors. While not a clear-cut victory, he was pleased that he managed to finish the 40-kilometer race.&lt;br /&gt;
&lt;br /&gt;
Prior to completing his Course studies at the Academy, Ahmed also took and completed his Bridge Certification Training, Command Staff Training and his Departmental Command Courses. The scored well in each of these additional course, a fact that would assist him later in being selected for the position of [[First Officer]] of the [[USS Champlain]].&lt;br /&gt;
&lt;br /&gt;
Ahmed graduated the Academy Class of 2407 on Stardate 2407.01.22. He ranked second in his class. It was on his graduation day that news arrived of his father’s death aboard the [[USS Tripoli]]. He had sacrificed himself to maintain the containment of the collapsing warp core during the battle of [[Cardassia]].&lt;br /&gt;
&lt;br /&gt;
==Starfleet Career==&lt;br /&gt;
&lt;br /&gt;
[[image:Nimitz.jpg|400px|thumb|right|The USS Nimitz]]&lt;br /&gt;
&lt;br /&gt;
Ahmed was commissioned as an Ensign Junior Grade pursuant to his graduation from Starfleet Academy on Stardate 2407.01.22.&lt;br /&gt;
&lt;br /&gt;
Ahmed was ordered to report to the [[USS Nimitz]], a [[Sovereign Class]] [[Starship]] (Registry NCC-75878-E) captained by Captain [[Devan Sash]].&lt;br /&gt;
&lt;br /&gt;
Ahmed was forced to take a circuitous route to reach the Nimitz due to the Civil War between the Doenitz Loyalists and the [[52nd Fleet]], the latter to which the Nimitz belonged. During his trip he witnessed the oppression of [[Andoria]] first-hand.&lt;br /&gt;
&lt;br /&gt;
He commissioned a respected smuggler and 52nd Fleet loyalist named [[Arkot]], an ex-captain of the Doenitz defeated [[Andorian]] Defense fleet. During his time aboard the Smuggler, he worked in main engineering and repaired an old Romulan cloaking device that was later used to elude a Doenitz loyal Starship.&lt;br /&gt;
&lt;br /&gt;
Ahmed arrived on Starbase [[Geneva]] on Stardate 2407.02.09 nearly a full month after his graduation from the Academy in San Francisco. Once aboard [[Starbase Geneva]] Ahmed wasted no time reporting to the Nimitz.&lt;br /&gt;
&lt;br /&gt;
==Mission One: A Taste of Hate.==&lt;br /&gt;
&lt;br /&gt;
After his arrival on Starbase [[Geneva]], Ahmed was assigned to assist in the investigation concerting an attack on the newly assigned Counselor [[Divon Lronen]]. During the course of the investigation, Ahmed was responsible for finding the weapon used in the assault on the counselor. He was reassigned to the Engineering Department to conduct repairs to the Nimitz as a result of a prior battle.&lt;br /&gt;
&lt;br /&gt;
He reported to Main Engineering and watched in Horror as the current ACEO Lieutenant Miles Davis collapsed after contracting the engineered [[Revelation Virus]] released on Geneva Station by the Terrorist Group [[Humans for Humanity]].&lt;br /&gt;
&lt;br /&gt;
Lieutenant Davis was the first member of the Nimitz crew to succumb to the virus and later died as a result of the illness.&lt;br /&gt;
&lt;br /&gt;
Once it became known what was happening, [[Starbase Geneva]] and the [[USS Nimitz]] were quarantined to prevent further spreading of the virus. The result of the lock-down left Ahmed, newly arrived on the Nimitz as the senior Engineering Officer on the Nimitz, due to Commander Zzt becoming unable to leave the Starbase.&lt;br /&gt;
&lt;br /&gt;
After Hromava, the Nimitz’s First Officer ordered all non-essential personnel to be restricted to quarters, Ahmed and Debbie Weston continued with the repairs to the Nimitz.&lt;br /&gt;
&lt;br /&gt;
Later due to the fact that the virus had been introduced to the crew of the Nimitz, special quarantine areas were established in the ship’s cargo bay, on the orders of the First Officer. It was at this time that Salid discovered an attempt by desperate members of the ship’s crew to escape from the Cargo bay and potentially seize control of the Nimitz. &lt;br /&gt;
&lt;br /&gt;
Ahmed participated in the actions to prevent a mutiny aboard ship.&lt;br /&gt;
&lt;br /&gt;
For his efforts, Captain [[Devan Sash]] promoted him to Ensign Senior grade on Stardate 2407.02.17.&lt;br /&gt;
&lt;br /&gt;
After his promotion Ahmed began a romantic relationship with Engineer Debbie Weston.&lt;br /&gt;
&lt;br /&gt;
==Mission Two: [[Djorn Major Incident|For a Friend]].==&lt;br /&gt;
&lt;br /&gt;
[[Image:VoyagerWarpCore.jpg|thumb|300px|right|Promoted to Chief Engineer]]&lt;br /&gt;
&lt;br /&gt;
On Stardate 2407.03.07 Ahmed was promoted to the position of CEO for the [[USS Nimitz]] by Captain [[Devan Sash]] after it was discovered that Lieutenant Commander Zzt was to be transferred to a Special Theoretical Engineering Unit.&lt;br /&gt;
&lt;br /&gt;
Later that same day, Ahmed would join Captain Sash and several other Nimitz Officers on an unsanctioned mission to Rescue Lieutenant Dru Tagon, a fellow Nimitzer. Tagon had been captured by Doenitz forces and sentenced to be executed. It was discovered that he was being held at [[Djorn Major XJ-003]] to await the completion of his sentence. As the [[52nd Fleet]] was stretched over a wide front in the battle against Deonitz forces, the Admiralty had decided that no vessels could be risked on the rescue. Despite orders to the contrary, Captain sash and several officers made  a rendezvous with the [[IKS Hegh’delar]] a [[Bird-of-Prey|B’rel Class]] scout and entered federation space with the intention of conducting a rescue of Dru Tagon.&lt;br /&gt;
&lt;br /&gt;
Prior to the Arrival at Djorn Major XJ-003, Ahmed spent a considerable amount of effort and time designing material aids to assist in the assault and hopefully give his small team a slight advantage against the station’s garrison. These gadgets included an armored cloaking armored EVA suit, modified from the available Klingon EVA suits, attuned to the IKS Hegh’delar’s [[Cloaking device]]; A series of portable sensor ghost generators, and a mobile handheld command net inderdiction device which later allowed the crew limited access to the station’s main computer systems. Unfortunately despite successful tests of the stealth suits aboard the Hegh’delar, the stealth features seemed to mysteriously fail once aboard the station.&lt;br /&gt;
&lt;br /&gt;
[[image:Horizon.jpg|thumb|300px|left|Djorn Major XJ-003]]&lt;br /&gt;
&lt;br /&gt;
Upon their arrival at Djorn Major XJ-003, The 1st assault team used the [[Ferengi]] assault shuttle the [[Good Deal]] to pass through a gap in the Station’s ventral shields and after An EVA mission to establish a series of transport pattern enhancers, the Crew was aboard the Station.&lt;br /&gt;
&lt;br /&gt;
Ahmed participated in the capture of the Central Computer core of the station in which action he killed a technician.  Later in an attempt to disable the stations shields and weapons, he created a powerful [[plasma]] surge through the tactical systems. The end result was the unexpected explosion of the Station’s Ventral Shield Generator, which was responsible for extensive damage to the station and an unknown number of deaths among station personnel.&lt;br /&gt;
&lt;br /&gt;
Ahmed was injured twice during the mission. Once, he was hit with a [[phaser]] blast in the back fired by station security, which forced him to discard the upper portion of his armored EVA suit. Later he was injured in hand-to-hand combat with a member of Major Julian Wells’ marine unit assigned to guard Lieutenant Tagon. The marine stabbed Ahmed in the lower left arm.&lt;br /&gt;
&lt;br /&gt;
The arrival of the Klingon assault forces from the Hegh’delar led by Doctor [[Jonas Lemar]] allowed the Nimitz crew to reach the Maximum Security Block and force Wells into an honorable ceasefire.&lt;br /&gt;
&lt;br /&gt;
Ahmed and [[Thomas Jackson]] worked together to drop the containment field holding Dru Tagon in his cell. Ahmed also managed to neutralize the explosive collar Tagon wore using the station’s [[transporter]] safety overrides. At Captain [[Devan Sash]]’s order Ahmed transported the assault team to safety, but not before [[Agent Thom Hania|Thom Hania]] had released an explosive grenade which is believed to have killed Major Julian Wells.&lt;br /&gt;
&lt;br /&gt;
The crew escaped Djorn Major and returned to [[Starbase Geneva]] with Lieutenant Tagon. Remarkably, only two members of the rescue effort were killed in action, both were members of the Hegh’delar’s Klingon Marine Contingent led by Doctor Lemar. Later Ensign Thom Hania died under mysterious circumstances prior to the return to the Nimitz. Ensign [[Harry Samuel Doorman]] had survived an apparent attempt at suicide, although later it was discovered that his actions were influenced by the [[Revelation Entity]] affecting Counselor [[Divon Lronen]]. &lt;br /&gt;
&lt;br /&gt;
Surprisingly enough, no member of the Nimitz crew was punished for the undertaking of the unsanctioned rescue of Lieutenant Tagon, Except for Captain Sash.&lt;br /&gt;
&lt;br /&gt;
For his efforts in the rescue of Lieutenant Tagon, Ahmed was promoted to the rank of Lieutenant Junior Grade on Stardate 2407.03.22&lt;br /&gt;
&lt;br /&gt;
==Mission Three: [[To Skin a Cat]].==&lt;br /&gt;
&lt;br /&gt;
On Stardate 2407.03.22 the Nimitz received orders from the Admiralty to conduct a snap raid on [[Cait|Cait Prime (Ferasa)]] with the objective of verifying the existence and destroying a Doenitz research facility believed to be developing biogenetically altered Caitians for use as Super-Soldiers. &lt;br /&gt;
&lt;br /&gt;
The [[USS Nimitz]] arrived in the Ferasa system and was surprised not to find any Doenitz Starships in orbit around the planet.&lt;br /&gt;
&lt;br /&gt;
The away team consisted of the following participants&lt;br /&gt;
[[Rank|Captain]] [[Devan Sash]]&lt;br /&gt;
CTAC [[Eric McDermott]]&lt;br /&gt;
AOPS [[Thomas Jackson]]&lt;br /&gt;
Engineer [[T&#039;Kron]]&lt;br /&gt;
Ensign Leesa Stanton&lt;br /&gt;
COUNS [[Cecilia Bruce]]&lt;br /&gt;
&lt;br /&gt;
As well as several junior members of the security, Science and Engineering departments of the Nimitz.&lt;br /&gt;
&lt;br /&gt;
Upon Arrival on the planet, The Nimitz team Linked up with members of the CLF (Caitian Liberation Front) led by an adolescent Caitian named R&#039;Aul. They also made contact with R&#039;Serrott and [[Shayhiloosh]], both of which were involved in some manner with the facility that the Nimitz crew was sent to destroy.&lt;br /&gt;
&lt;br /&gt;
[[image:Nilas III.jpg|thumb|500px|right|The USS Nimitz at Cait Prime (Ferasa)]]&lt;br /&gt;
&lt;br /&gt;
The crew spent the night with their new found allies in the Caitian Village of [[Chtarr]], where Ahmed participated in a complex and semi-violent game of [[Sarhket]], which is used in some rural areas to resolve disagreements. The game turned out to be a test of the Nimitz crew&#039;s resolve to aid the [[Caitian]]s in their struggle for liberation. Although Salid did not win, he earned the respect of the local CLF members and was accepted among them as a friend.&lt;br /&gt;
&lt;br /&gt;
The following morning the away team, bolstered by their new additions in R&#039;Serrott and Shayhiloosh and accompanied by A&#039;Rul and members of the CLF, marched to and raided an automated train depot that would allow them covert entry to the Capital City of [[Knassis]], only 30 miles away. The raid on the train depot went smoothly without incident.&lt;br /&gt;
&lt;br /&gt;
Once the train depot had been secured, The Nimitz away team hid themselves aboard the supply train and rode the conveyance to their target area. The train was stopped by members of the Local Militia when it was discovered that a trap had been set for the Nimitz team. As a result, The team was instead forced to hike into the target area undetected and assault the underground complex where [[Admiral Doenitz|Doenitz loyalists]] were conducting illegal biogenetic and telepahic manipulation.&lt;br /&gt;
&lt;br /&gt;
Once inside, the team split into two assault groups; one  led by [[Rank|Lieutenant]] Salid and the other by Captain Sash. &lt;br /&gt;
&lt;br /&gt;
The team led by Sash seized the facilities [[transporter]]s and assaulted the telepathic research facilities, While the second team under Lieutenant Salid assaulted the genetics labs and holding cells. Ahmed&#039;s group met light resistance and was able, with the help of Lieutenant Prothal, to destroy the research facilities beyond repair.&lt;br /&gt;
&lt;br /&gt;
Meanwhile, Captain Sash&#039;s team came under attack by facility security and were pinned down in a terrible crossfire. Salid&#039;s team arrived in time to relieve the captain&#039;s team and the two teams then led the assault against the primary telepathic holding facility.&lt;br /&gt;
&lt;br /&gt;
During the assault on that facility, The away team came under psychic attack, that caused some of their number to turn on their allies.  Salid and several other officers managed to fight their way out of the control of the being designated, Patient [[Delta-Seven-Nine|Delta-Seven-Nine (Δ79)]]. Δ79 killed his controller and then died of injuries inflicted upon him by the combined telepathic attacks of [[Cecilia Bruce]] and [[Eric McDermott]].&lt;br /&gt;
&lt;br /&gt;
Once the telepathic research facilities were neutralized, Sash led the remainder of his team and the rescued test subjects from the facility to the city above. &lt;br /&gt;
&lt;br /&gt;
When the word spread that there were Caitains in revolt, the entire [[planet]] rose up and threw off the yoke of the Doenitz Regime.&lt;br /&gt;
&lt;br /&gt;
For his efforts, Ahmed was awarded the Combat Action Ribbon. He was promoted to [[Rank|Lieutenant Commander]] on Stardate 2407.03.29, when it was also announced that he had been selected as [[First Officer]] of the [[USS Champlain]].&lt;br /&gt;
&lt;br /&gt;
== Mission Four: Crossroads ==&lt;br /&gt;
&lt;br /&gt;
[[Image:USSChamplainD.jpg|450px|thumb|right|USS Champlain]]&lt;br /&gt;
After the completion of the mission on Cait Prime, Ahmed was promoted to the Rank of Lieutenant Commander and assigned to the [[USS Champlain]], NCC 2170-C, A [[Galaxy Class]] variant. He reported to [[Starbase Geneva|Geneva Station]] to Captain [[Susan Rivers]], who had also just assumed command of the Champlain after the death of her Captain Edward Wolfe in a battle with the [[USS Wyvern]]. He assumed this position officially on Stardate 2407.04.02, despite the fact that the Champlain had not yet arrived at the Station as she was damaged during the battle. The Champlain was Commanded by [[Rank|Lieutenant]] Bree Frazier during the engagement with the [[USS Wyvern]], which resulted in the enemy vessel&#039;s capture thanks in no small part to the efforts of Lieutenant James Alexander and Lieutenant Jono Janeway.&lt;br /&gt;
&lt;br /&gt;
Captain Rivers advised Lieutenant Commander Salid of the impending assignment of the Champlain to participate in the final push of the [[Federation Civil War]] against [[Admiral Doenitz]] in an amassed attack on [[Sector 001]]. He was assigned to arrange drills and additional training for the crew while the ship remained in dock undergoing repairs.&lt;br /&gt;
&lt;br /&gt;
==Mission Five: [[Do Not Go Gently]]==&lt;br /&gt;
[[Image:Task Force 19 -2.jpg|thumb|300px|right| Task Force 19, of the 52nd Fleet, assembling in preparation to attack Sector 001]]&lt;br /&gt;
&lt;br /&gt;
On stardate 2407.06.25 Ahmed was advised by Captain Susan Rivers that they had finally received their orders to join the remainder of [[Task Force 19]] assembling at [[Tellar]]. The Champlain had been completely overhauled and the ship and her crew were as ready as they could possibly be for the final battle against Doenitz forces guarding sector 001&lt;br /&gt;
&lt;br /&gt;
On Stardate: 2407.07.03 Ahmed and the entire Command Staff of the USS Champlain were briefed on the plans to Attack Sector 001 and [[Earth]] in a final bid to bring an end to the bloody and tenacious Federation Civil War. This [[Task Force Nineteen Briefing|Briefing]] was conducted by Rear Admiral Sevant, Former captain of the [[USS Boudicca]] and the Task Force Commander of [[Task Force 19]], ordered to breach the famous [[Mars Defense Perimeter]] designed to hold of a [[Borg]] Invasion.&lt;br /&gt;
&lt;br /&gt;
Even as the crew of the Champlain begin gearing for the coming battle, Hundreds of [[Starship|ships]] were converging at Tellar in preparation for the massive offensive.&lt;br /&gt;
&lt;br /&gt;
The assignment given to the Champlain was simple in concept but exceptionally complex in practice. The task force was broken into four smaller battle groups and the remaining bulk of the taskforce, consisting of the [[USS Boudicca]] (commanding group B), the [[USS Champlain]] (commanding group C), the [[USS Nimitz]] (commanding Group A), The [[USS Hades]] (commanding group D). The Boudicca was tasked to breach the MDF and assault and capture [[Starbase Valhalla]] in an attempt to shut down the MDF and allow the remainder of Task Force 19 to bypass the MDF without further losses. The USS Champlain, Hades, and Nimitz were ordered to support the operation of the Boudicca, with the Champlain being specifically tasked with screening the Boudicca and her Battlegroup from enemy raiders.&lt;br /&gt;
&lt;br /&gt;
The basic flow of the battle is listed here:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;toc colour&amp;quot; style=&amp;quot;margin: 0 0 1em 1em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;Stardate: 2407.07.05&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1410 HRS&amp;lt;/font&amp;gt;: The order to &amp;quot;Cross the River Acheron&amp;quot; is given by Admiral Sevant, the [[Commanding Officer]] of Task Force 19. Lead elements of the taskforce begin their journey to [[sector 001]] and the final engagement of the civil war.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1414 HRS: Captain Rivers Orders the USS Champlain and Battle Group C to set course for Sector 001.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1415 HRS&amp;lt;/font&amp;gt;:  Battlegroup Theta commanded by  Captain Sarah Smithers orders her specialized assault group underway.&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;Stardate: 2407.07.09&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1328 HRS&amp;lt;/font&amp;gt;: The [[USS Champlain]] and her accompanying battlegroup drop out of warp and steam towards the MDF. Battle Group A consisting of 20 ships, 4 of which are [[Klingon]] [[Negh&#039;Var Class]] vessels, break formation and begin assaulting the MDF at long range. &lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1400 HRS&amp;lt;/font&amp;gt;: The enemy sends out skirmishing vessels to harass battlegroup A with mixed results.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1407 HRS&amp;lt;/font&amp;gt;: The [[USS Boudicca]] begins her run towards the MDF&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1410 HRS&amp;lt;/font&amp;gt;: Battlegroup Laredo (D) attacks the USS Champlain and her associated Battle Group. The raiders uncloak, fire a volley of modified torpedoes into the flank of the C-Group then make a strafing run. Both sides take casualties. The C-Group falls back from B-Group to protect the latter&#039;s flanks from attack.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1415 HRS&amp;lt;/font&amp;gt;: The [[USS Hades]] and [[USS Nimitz]] reach [[Sector 001]]. The Hades goes into Tri-Vector Assault mode.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1417 HRS&amp;lt;/font&amp;gt;: Group Theta arrives at Sector 001 and begins their assault on a weapons repository located just inside the MDF.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1418 HRS&amp;lt;/font&amp;gt;: Battle Group D engage enemy fighters and their support ships.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1425 HRS&amp;lt;/font&amp;gt;: Battle group Laredo makes a second attack run against C-Group then retreats from the battlefield behind the protection of the MDF&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1449 HRS&amp;lt;/font&amp;gt;: The USS Boudicca and her Battlegroup make contact with the MDF.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1455 HRS&amp;lt;/font&amp;gt;: The [[USS Spectre]] arrives in sector 001 with a [[Klingon]] Task force and a group of Ex-Doenitz ships that have defected to the [[52nd Fleet]].&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1750 HRS&amp;lt;/font&amp;gt;: The USS Boudicca and her battle group finally break through the MDF.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1755 HRS&amp;lt;/font&amp;gt;: The USS Champlain and the remnants of Battle Group C breach the MDF while being pursued by the [[USS Majesty]] and her Battle group (D)&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1800 HRS&amp;lt;/font&amp;gt;: Captain Rivers orders Battle group C to form a battle line behind  Battlegroup B to guard the Boudicca&#039;s rear flank. The C-Group turns about 180-degrees and forms a battle line to handle the Majesty and her battle group.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1815 HRS&amp;lt;/font&amp;gt;: The USS Majesty and her battlegroup form a wedge formation to better split through the battle line established by Captain Susan Rivers and the remnants of Battlegroup-C.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1820 HRS&amp;lt;/font&amp;gt;: The two battle groups led by the USS Majesty and the USS Champlain clash. The battle formations are broken and the battle devolves into complete chaos for the two battle groups.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1822 HRS&amp;lt;/font&amp;gt;: After taking fire from Negh&#039;Vars of Battlegroup-A, [[Uru Mtenga]] orders the [[USS Hercules]] and the [[USS Persephone]] to split off from the rest of his battlegroup and deal with the Klingon ships. They destroy all three remaining Ngh&#039;Vars and return to the battle with the Champlain.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1825 HRS&amp;lt;/font&amp;gt;: The [[USS Dennison]] and a small battle group arrive at Sector 001 to aid Task Force 19.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1830 HRS&amp;lt;/font&amp;gt;: The USS Boudicca realizes that they are facing the Black Watch led by Admiral Lydia Stakes as well as elements of the 53rd Heavy Assault Fleet. Captain Archibald Stakes appeals to the morality of the enemy battle group and the majority of the Night watch and the 53rd Heavy defect or stand aside. Those resisting are engaged and subdued by the remainder of Battlegroup-B.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1900 HRS&amp;lt;/font&amp;gt;: The USS Nimitz is destroyed in battle when she rams an enemy ship during a warp core breach. Several members of her crew managed to abandon ship just prior to her destruction.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1907 HRS&amp;lt;/font&amp;gt;: The battle between the Majesty and Champlain Battle groups has depleted both sides resources significantly. The [[USS Hypatia]] from the Black Watch joins the battle. Her captain convinces Captain M&#039;tega that they are still loyal to [[Admiral Doenitz]], then ambushes their former ally. The Majesty is crippled, giving the heavily damaged Champlain a short respite.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1910 HRS&amp;lt;/font&amp;gt;: The [[USS Dennison]] joins the [[USS Hades]] as a defensive screening force while the Hades reintegrates from Tri-Vector mode and begins rescue operations of the surviving Nimitz Crew.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1911 HRS&amp;lt;/font&amp;gt;: The Champlain engages the enemy [[Prometheus Class]] starship, [[USS Persephone]]. The Champlain loses her dorsal nacelle and an unstoppable warp core breach begins. Once Rivers realizes the ship is lost, she orders the abandon ship. The Persephone begins firing on the life boats from the Champlain.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1920 HRS&amp;lt;/font&amp;gt;: The USS Boudicca, press their shields against those of [[Starbase Valhalla]]. This action causes severe damage to the [[Keltoi Class]] ship, but causes the Stations dorsal shields to fail. Stakes orders the abandon ship and the crew of the Boudicca use transporters or life pods to get aboard Valhalla following the Marine assault ships.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1922 HRS&amp;lt;/font&amp;gt;: Several senior officers &amp;quot;volunteer&amp;quot; to stay aboard while the Champlain is guided towards her enemy like a massive missile. &lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1930 HRS&amp;lt;/font&amp;gt;: In an attempt to give their comrades time to get clear of the Persephone&#039;s violent onslaught, the [[USS Wyvern]] draws the larger vessel away from the dying Champlain. The Wyvern is knocked out of commission and all her crew killed.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1949 HRS&amp;lt;/font&amp;gt;: The USS Champlain manned only by a handful of volunteers use the [[Galaxy Class]] vessel to ram the [[USS Persephone]]. Both ships are completely destroyed. The skeleton crew on the Champlain is rescued by the [[USS Hypatia]].&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;2055 HRS&amp;lt;/font&amp;gt;: The rest of [[Task Force 19]] is ordered to go &amp;quot;To Earth!&amp;quot; The offensive for the planet itself begins in earnest. [[Starbase Valhalla]] is secured by the [[52nd Fleet]].&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;Stardate: 2407.07.09&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;0127 HRS&amp;lt;/font&amp;gt;: The [[USS Dennison]] and her support ships destroy the [[USS Caesar Regnum]]&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;0130 HRS&amp;lt;/font&amp;gt;: Reports surface that ex-president and dictator Rodrigo Doenitz is captured by Resistance forces in Geneva Switzerland.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;0205 HRS&amp;lt;/font&amp;gt;: The former president of the [[United Federation of Planets]] is restored and the Civil War and the Battle for [[sector 001|Sector 001]] is finally ended.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Mission Six: [[Picking up the Pieces]].==&lt;br /&gt;
&lt;br /&gt;
[[Image:Homecoming.jpg|thumb|450px|right|The USS Rosenante NCC-924650]]&lt;br /&gt;
With the civil war over and the Champlain lost, Ahmed was assigned as Acting [[First Officer]] of the [[USS Hypatia]] under the command of Acting Captain [[Susan Rivers]].&lt;br /&gt;
&lt;br /&gt;
The Hypatia underwent repairs and participated in some limited recovery work inside the [[Sol|Sol System]].&lt;br /&gt;
&lt;br /&gt;
Salid visited his uncle in [[Cairo]], where he met [[Jasmin Mohandas]]. An ex-ACMO from the [[USS Pangaea]] (a Doenitz ship from the 1st Fleet) when she saved him from a mob that attacked him because he was wearing his [[Starfleet]] uniform. Ahmed discovered that his uncle had been interred and had suffered torture at the hand of Doenitz fundamentalists as a result of his nephew&#039;s involvement with the Sedition.&lt;br /&gt;
&lt;br /&gt;
Ahmed spoke at a tribunal hearing for Lieutenant Mohandas, urging the tribunal to exercise mercy. Miss Mohandas was found innocent of all charges of murder during the battle, but was found guilty of Medical Negligence. She lost one grade in rank as a result.&lt;br /&gt;
&lt;br /&gt;
Ahmed reconciled with his uncle after the two men had an argument about his potential resignation from Starfleet to attend to his uncle&#039;s health needs. &lt;br /&gt;
&lt;br /&gt;
Salid visited his ex-shipmates from the Nimitz who had been reassigned to the [[USS Hades]]. There he and Debbie Weston spoke about the future of their past relationship and about the loss of the [[USS Nimitz]].&lt;br /&gt;
&lt;br /&gt;
After a crushing declaration by Commander Josel, Chief of Personnel for [[Sector 001]] that Ahmed was not qualified to serve in the capacity of First Officer; he was assigned to the Engineering operations Officers aboard [[Starbase Valhalla]] on Stardate 2408.01.04. This assignment did not last for long, however. Captain Susan Rivers acting on the authority of [[Rank|Admiral]] Linden, ordered Ahmed reassigned to the [[USS Rosenante]], as her First officer.&lt;br /&gt;
&lt;br /&gt;
Ahmed and Captain Rivers beamed aboard the Rosenante on stardate 2408.01.06 to assume command from the Acting CO Commander Ian MacBeth.&lt;br /&gt;
&lt;br /&gt;
== Mission Seven: [[A Fine and Private Place]]==&lt;br /&gt;
[[Image:Extrasolar-Binary.jpg|thumb|250px|right|Davros III]]&lt;br /&gt;
&lt;br /&gt;
The [[USS Rosenante]] passed her space worthiness trials without a glitch and was assigned their very first mission, to survey planets for recolonization of the survivors of the [[Colony]] of [[Ivor Prime]]. The Rosenante took on the administrator of the colony and set off for the [[Optima VII|Optima System]] in hopes of finding a planet suitable for the colonists. The Rosenante departed for her official maiden Voyage on Stardate 2408.01.15. The Ceremony was officiated by [[Rank|Admiral]] Hesper Linden.&lt;br /&gt;
&lt;br /&gt;
On Stardate 2408.01.21  the Rosenante received a disturbing [[Sky of Tomorrow Distress Call|distress signal]] from the Federation freighter the &#039;&#039;&#039;[[Sky of Tomorrow]].&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Third Officer, Olen Rhinehardt altered course and alerted the captain and crew to the situation. The Sky of Tomorrow&#039;s signal was traced to the orbit of [[Davros III]], A [[Federation]] Mining [[Colony]].&lt;br /&gt;
&lt;br /&gt;
The Rosenante arrived at the scene only three hours later. Attempts to hail the freighter were not successful. An away team was beamed aboard and to their horror uncovered signs of a violent and bloody conflict. They also encountered an animated dismembered hand. This hand was quarantined and studied upon the return of the away team to the Rosenante, where it was discovered that the hand was infested with a nanite colony derived from [[Borg]] [[nanoprobe]]s.&lt;br /&gt;
&lt;br /&gt;
Ahmed led an away team down to the planet&#039;s surface to search for survivors, when he returned to the Rosenante without three of his security team, Ahmed offered this summary to the Captain:&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;sup&amp;gt;&amp;lt;font color=goldenrod&amp;gt;&lt;br /&gt;
:&#039;&#039;Ahmed followed the Captain into the ready room.  As always the Captain was incredibly calm, ~But then again,~ Ahmed reminded himself, ~she hadn&#039;t just been chased by an indeterminable number of corpses animated by Borg nanites… Or something like that~&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Sit down, Ahmed,&amp;quot; she said, and headed for the replicator. Without asking, she ordered two cups of Ahmed&#039;s special Turkish coffee and a plate of pastries. She sat them down on the table between them and said. &amp;quot;You can talk as you eat,&amp;quot; she ordered, sliding the plate a little closer to him. &amp;quot;I can tell by your face it&#039;s not good news, so let&#039;s hear it. What did you find down there?&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;It&#039;s hard to be clear, so bear with me.&amp;quot; Ahmed said as he added a little goat&#039;s milk to his coffee and took a sip. &amp;quot;When we arrived in the town square, everything was quiet. It was just like one of those wild west ghost towns that you read about in the history books.  All it was missing was the tumble weed.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;We located the residence of doctor Lawson and there we found what appeared to the remains of a lab. It was very obvious that some of the equipment had been moved elsewhere. From that lab there were two almost parallel tunnels leading downward toward the mine. As you know that was when I ordered Lieutenant Janeway, chief fuller and a second security team down to the planet. The idea was that the two teams could each explore one of the tunnels and possibly locate any survivors or clues faster.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;He picked up one of the pastries and took a bite. The orange marmalade was exceptionally good and Ahmed then realized how hungry he really was. He took a sip of his coffee to wash it down.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;We searched for several hours without any sign at all of the miners. For a while there, I was even beginning to wonder if all 1500 of them had somehow managed to leave the planet. We came to a junction and heard what I could only describe as weapons fire. I ordered the team down the tunnel to the source as quickly as possible which opened into a cavern.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;When we arrived, there was an… individual there, a member of the Opthidian species, who was defending himself from some of the miners. It was apparent that he had killed at least ten or twelve of them already. We announced ourselves and ordered the fighting to stop, but instead of being attacked by the visitor as I had originally expected to be, it was the miner&#039;s that attacked us.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Heavy stun doesn&#039;t have much affect on them. Even the kill setting isn&#039;t very effective.  We lost Abernathy in that fight. He was infected by some sort of black ooze, which we were later informed was a nanite colony.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;The Opthidian&#039;s name is Sharott Nachook and he explained a great deal to us concerning what was happening on that colony.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;Ahmed ate some more of his pastry and drank a little more of his coffee. &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;His people encountered the Borg roughly 500 standard years ago. Apparently their physiology doesn&#039;t allow them to be assimilated by Borg Technology. They fought a war and in the end the [[Borg]] left them alone. The Opthidian scientists had dissected several Borg drones during the war and had discovered a way to modify the Borg nanoprobes for their own medical uses. This continued for some time until eventually, the Borg nanoprobes developed some sort of colony-like hive mind and became self-aware. They began to dominate living members of the Opthidian species against their will and when the realization struck, the Opthidian government tried to destroy the nanites.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;The nanites adapted again in a very grotesque manner. They began killing their hosts and maintaining the bodies after death until they were no longer viable. The [[Opthidian]] homeworld had to be biologically sterilized to prevent them from spreading. From what I can gather eventually the Opthidians captured the original colony which they refer to as the matriarch and imprisoned it pending it&#039;s destruction.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Now here&#039;s where the details get a bit sketchy.&amp;quot; Ahmed said then took another sip of his coffee. &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;At some point in the recent past, the Ferengi somehow managed to steal this imprisoned nanite colony and transport it here, where it is believed they sold it to Doctor Lawson. The good doctor is an expert on Borg nanotechnology and was living here with her young daughter, who was very ill with an incurable ailment according to Doctor Caskie&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;We can surmise that Lawson conducted some experiments, maybe even infecting her daughter either with the knowledge that these nanites were self-aware or in ignorance. Regardless of what she knew, that seems the most logical means that this infection was spread. From there, the nanites took over members of the community exponentially until every member was a member of the colony.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Mister Nachook&#039;s people tracked the Ferengi here. They claim to have destroyed the Ferengi ship and admit to attacking Mister Raschen&#039;s ship in an attempt to maintain some semblance of quarantine. It seems that after their losses in the battle, they withdrew, possibly to conduct repairs when we arrived in the system.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;They had dropped Nachook and perhaps a couple of others on the planet with the mission to find and destroy the nanite breeding pool, where apparently the matriarch lives. Mister Nachook claims that destroying her will result in the demise of all her immediate offspring as they are dependant on her for their cognitive abilities.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Just shortly after all this data was given by Nachook, Jono shows up with what is left of Beta team. He was injured and we gathered that they were surrounded and attacked by a large mass of infected miners. They lost Milano during their escape.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Nachook advised Caskie at that time that  he carries some sort of viral weapon in his body that will wipe out the entire biosphere of the planet and make it uninhabitable for roughly 200 standard years. He is confident that the weapon will kill all the nanites present by depriving them of biological hosts and will kill anyone that should set foot there as well and prevent the nanites from managing to get off world.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;Ahmed finished his coffee and sat it on the table. &amp;quot;The catch is that Nachook was injured and some sort of biological process has started that will result in his death and the release of the virus in an uncertain amount of time. Doctor Caskie is confident that she can extract the virus, saving Nachook and that the virus can them be delivered to the planet via modified Photon torpedo, where it will destroy the biosphere and end the threat of it spreading from this planet.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;We had to fight our way out of those tunnels. We lost Hezan there. I vaporized him myself.&amp;quot; &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;Ahmed looked into River&#039;s eyes, before continuing. &amp;quot;I&#039;ve seen a lot of terrible things Captain, but I can not describe to you the sheer terror and fear that these things inspire. I am not a blood thirsty person, but these things need to be eradicated with all due prejudice.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;That said it was my assessment, after my experience on the planet, that these nanites should be treated like a biological outbreak and should be eradicated before they place millions or even billions more at risk. I have ordered Caskie to proceed with her plan after she assured me that she could prevent it from spreading across the ship should there be a mishap. I believe that we have no recourse and that we should treat these nanites as we would Borg. There is no hope of negotiation and that any encounter will result in the supplantation of one species over the other at the complete eradication of the prior.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;To carry through with this, I furthermore, recommend that we transport the nanite-filled hand back to the Sky of Tomorrow and that we undertake steps to destroy it and the freighter as well.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/font&amp;gt;&amp;lt;/sup&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Captain Rivers agreed with Salid&#039;s assessment and ordered the plan carried out. At 2045 hours the orders were given to deploy the viral torpedo and the planet of [[Davros III]] was sterilized. The freighter was destroyed shortly thereafter and Mister Nachook was returned to his ship. &lt;br /&gt;
&lt;br /&gt;
The Rosenante seeded five quarantine probes around the planet before departing to complete their original mission.&lt;br /&gt;
&lt;br /&gt;
On Stardate: 2408.01.25 Captain Rivers was ordered to Starbase Geneva to give evidence for a war crimes tribunal. She was advised that she would not be returning to the command of the Rosenante and Commander Salid was promoted to the rank of Captain and given command of the USS Rosenante.&lt;br /&gt;
&lt;br /&gt;
== Mission Eight: [[Letters of Marques]]==&lt;br /&gt;
&lt;br /&gt;
After the transfer of captain Rivers to the Boudicca, Ahmed is promoted to captain of the Rosenante. &lt;br /&gt;
[[Image:APPLANET.jpg|thumb|250px|right|Arturia Prime]]&lt;br /&gt;
&lt;br /&gt;
It turns out that his first test as captain will place his ship and crew well outside the boundaries of Federation Space.&lt;br /&gt;
&lt;br /&gt;
The Mission began with a communication from Admiral Talbot of Starfleet intelligence.&lt;br /&gt;
&lt;br /&gt;
Prince [[Angor Khamal|Khamal]], the hereditary leader of the Meldovian people had been kidnapped on the eave of a peace treaty that would bring an end to a 400 year old war between the Meldovian and Arturian factions (both of the [[Cartenian]] race).&lt;br /&gt;
&lt;br /&gt;
While traveling to [[Arturia Prime]] from [[Meldovia III]] to conclude the peace treaty, Orion pirates and slavers attacked the Prince&#039;s convoy and took the Prince and many other Meldovians prisoner.&lt;br /&gt;
&lt;br /&gt;
At the request of the [[Vulcan]] Arbiter T&#039;Val, Admiral Talbot assigned the [[USS Rosenante]] to the task of locating and recovering the Prince before the peace negotiations fail.&lt;br /&gt;
&lt;br /&gt;
Salid was ordered to rendezvous with the Arbiter and take on an Arturian, Meldovian and the Vulcan delegations. He is then ordered to proceed into [[Orion]] space and locate and rescue the Prince.&lt;br /&gt;
&lt;br /&gt;
Using their untried cloaking system, the HISS system, the Rosenante slipped into Orion Space to begin their investigation at the heart of the [[Orion Syndicate]]&#039;s notorious slave markets on [[Barakos IV]].&lt;br /&gt;
&lt;br /&gt;
Three away teams are sent to the surface to procure supplies, search for clues to the Prince and gather intelligence.&lt;br /&gt;
&lt;br /&gt;
One of the away teams is tasked with the acquisition of a Orion style shuttle craft to be used in future phases of the mission. This team consisting of the first officer, Janeway, Lt. Dralar, and the CEO Lt. Paul Bird succeed in their mission, but not before Lt. Bird is killed in a senseless brawl by an individual using a poisoned blade.&lt;br /&gt;
&lt;br /&gt;
Bird is transported back to the ship, but the poison works quickly and he is not able to be revived.&lt;br /&gt;
&lt;br /&gt;
The second away team, consisting of Lt. Ro&#039;Dal, Ensign Weaver, PFC Nunez and Lt. Caskie, and Ensign T&#039;Kron search for Meldovians among the slave pens of the market. they are successful in rescuing three Meldovians and a Half-Orion/Half-[[Betazoid]] woman named Sodra, who claims to have information concerning the whereabouts of the prince.&lt;br /&gt;
&lt;br /&gt;
Sodra turns out to have no information at all, instead using her telepathic powers to pluck a few relative pieces of information from Weaver. However, she has done no harm and is restricted to quarters until such time as her disposition can be determined.&lt;br /&gt;
&lt;br /&gt;
Ro&#039;Dal and Caskie do recover three Meldovians with the aid of a new ally, Nodel, who is an amthropoid, a species not yet discovered by the UFP. Their new ally leads them directly to the last three Meldovian slaves in the marketplace.&lt;br /&gt;
&lt;br /&gt;
[[Image:Slave Market on Barakos IV.jpg|thumb|250px|right|The Slave Market on Barakos IV]]&lt;br /&gt;
&lt;br /&gt;
The third away team, consisting of Lt. Sullivan, Ensign [[Chance Raschen]], and Chief Sheridan make contact with Raschen&#039;s grandfather, a reputed Bounty hunter by the name of &amp;quot;Easy Ed&amp;quot; Raschen. They get a solid lead on whom may have the prince, an slaver named O&#039;Banyan at [[Xanadu Gothos]].&lt;br /&gt;
&lt;br /&gt;
Once all three teams have returned to the ship, the senior staff question those that were brought aboard at [[Barakos IV]].&lt;br /&gt;
&lt;br /&gt;
It rapidly becomes apparent that there was a spy within the Prince&#039;s circle of advisors, and that information, coupled with the discovery of an encrypted message into Orion space originating from the Rosenante, led to speculation that there was now an enemy spy aboard the Rosenante as well.&lt;br /&gt;
&lt;br /&gt;
Maddox and Weaver were given the task to decrypt the message in the hopes of discovering it&#039;s origins.&lt;br /&gt;
&lt;br /&gt;
With information acquired from Nodel it is determined that there was a Meldovian of some importance shipped to [[Haldor II]]. While it is unknown if this is the Prince, it is worth investigating and so the Captain orders course set and the Rosenante underway to the Haldor system.&lt;br /&gt;
&lt;br /&gt;
[[Image:Morella.jpg|thumb|left|[[Morella]] Pirate Queen]]&lt;br /&gt;
&lt;br /&gt;
En route, the Holographic marine Program, Ramirez, suddenly activates and attempts to assassinate the Captain and several other key members of the ship&#039;s senior staff.&lt;br /&gt;
&lt;br /&gt;
Chaos ensues as the crew struggle to regain control of the ship&#039;s computers and disable the hologram from operating. It quickly becomes apparent that the saboteur is responsible.&lt;br /&gt;
&lt;br /&gt;
Meanwhile Nodel confides in Ro&#039;Dal that he has heard the voice of a slaver on the ship. This voice he insists is the exact same voice that he heard near the Meldovian cells on [[Barakos IV]].&lt;br /&gt;
&lt;br /&gt;
Nodel and Ro&#039;Dal hatch a plan to potentially identify their would-be slaver and set the plan into action.&lt;br /&gt;
&lt;br /&gt;
With several of the ship&#039;s systems off-line, as a result of Ensign Weavers attempt to stop the holographic marine by disengaging the Cochrane Accelerator field in the main computer and then physically destroying the holographic buses with a hand phaser, the Rosenante takes refuge inside an asteroid belt to avoid detection while the stealth systems and other ship&#039;s critical systems are repaired.&lt;br /&gt;
&lt;br /&gt;
Once those repairs are completed, the ship continues on to [[Haldor II]], where their sensors detect the presence of a living facility protected by an environmental shield.&lt;br /&gt;
&lt;br /&gt;
With no ships in the immediate vicinity, Ahmed orders the ship into a geosynchronous orbit and tasks Lt. Sullivan, Ensign Weaver, lieutenant [[Steven Wade Matrix]] and Lieutenant [[Jennifer Caskie]] to accompany a security team to the surface with the intentions of rescuing the single Meldovian life-sign found on the planet.&lt;br /&gt;
&lt;br /&gt;
After recovering the Meldovian from the planet [[Haldor II]], it became quickly apparent that the individual that they had acquired was a traitorous captain who had been responsible for the ease of the Prince&#039;s kidnapping.&lt;br /&gt;
&lt;br /&gt;
Having no other choice the captain ordered the new prisoner interrogated and the Rosenante to set course for [[Torven III]]. The only other lead that they had to the possible whereabouts of the Prince&#039;s location.&lt;br /&gt;
&lt;br /&gt;
Once arriving in the Torven System, Salid opened negotiations with the trader [[Doyle &#039;Dogface&#039; O&#039;Banyan|Doyle O&#039;Banyan]], An [[Starfleet Marine Corps|ex-marine]] turned smuggler and slave trader. In return for a promise to aid in his rehabilitation, Salid agrees to accept O&#039;Banyan&#039;s assistance in recovering the prince. The Trader had already secretly sent an assault group against Morella in the hopes that they could acquire the Prince.&lt;br /&gt;
&lt;br /&gt;
Surprisingly, the assault works and the Prince as well as O&#039;Banyan&#039;s missing daughter is recovered, allowing the Rosenante to return back to [[Federation]] Space in time to guarantee the successful signing of the Peace between the Meldovian and Arturians and the formal formation of the Cartenian Commonwealth.&lt;br /&gt;
&lt;br /&gt;
Thier mission completed, the Rosenante heads to [[Starbase Geneva]] for some R&amp;amp;R and After action inspections.&lt;br /&gt;
&lt;br /&gt;
== Mission Nine: [[Furlough]]==&lt;br /&gt;
&lt;br /&gt;
The crew of the Rosenante is granted Furlough, while critical inspections concerning the Spiral drive are undertaken.  Captain Salid is forced to demote Lieutenant Janeway by BUPERS from the position of first officer and is assigned a newly promoted Lieutenant Commander Caskie to the position. &lt;br /&gt;
&lt;br /&gt;
The Rosenante also takes on some new senior Crew. Ahmed is reunited with [[Thomas Jackson]] with whom he served aboard the [[USS Nimitz]], in the position of Chief of Operations. Additionally the arrival of Lieutenant Nayati to fill the position of Chief Counselor and third Officer is a welcomed event.&lt;br /&gt;
&lt;br /&gt;
In other news, Salid is saddened by the transfer of Lieutenant Ro&#039;Dal who has been reassigned to the [[USS Mithrandir]].&lt;br /&gt;
&lt;br /&gt;
The Captain and his new FO go for a holographic sailing trip on the Mediterranean in a get to know you cruise, and Salid approves Sullivan&#039;s departure for the Advanced Tactical Theories Academy on [[Andoria]].&lt;br /&gt;
&lt;br /&gt;
== Mission Ten: [[Fields of Elysium]]==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Part I: The Mission&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
In Mid 2408 the [[USS Rosenante]] was assigned to explore a newly discovered region of space that exited from the Tau Sigma Flow of the Subspace River. This region had been discovered by an unmanned survey probe and opened into the [[Beltanis Stellar Nursery]].&lt;br /&gt;
&lt;br /&gt;
When the Rosenante arrived, the captain decided to move into the nebula in the hopes of exploring an undocumented phenomenon. This phenomenon turned out to be an exceptionally rare event known as a [[Subspace Bubble]]. Unfortunately, the bubble burst slamming the vessel with a Class Six [[Graviton|Gravimetric Wave]].&lt;br /&gt;
&lt;br /&gt;
The Rosenante was terribly damaged; suffering irreparable damage to the ship&#039;s Main Deflector Array and Power distribution network. With the ship&#039;s shields failing, the vessel hurriedly returned to the safe-zone at the terminus of the Subspace river.&lt;br /&gt;
&lt;br /&gt;
After a couple of days of assessment and around-the-clock repairs, it was determined that the Rosenante would not be able to return to Federation space via the [[Subspace River]], as they could not open the river terminus without the use of their [[Navigational Deflector]].&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Part II: The Distress Call&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Image:Nova_Class_4.jpg|thumb|175px|right|[[USS Epiphany]]]]&lt;br /&gt;
On their third day in the [[Beltanis Stellar Nursery|Nursery]] the Rosenante detected an automated federation Distress beacon. despite the fact that it was unlikely that any other federation starships were in the area, Captain Salid decided that the Rosenante should investigate.&lt;br /&gt;
&lt;br /&gt;
The beacons prefix identification was finally determined to belong to the the [[USS Epiphany]] a [[Nova Class]] starship registry NCC-913081, which had been declared lost with all hands on Stardate 2392.01.19 (17 years prior.)&lt;br /&gt;
&lt;br /&gt;
When the Rosenante responded, they discovered not the Epiphany, but [[The Harvester]].&lt;br /&gt;
&lt;br /&gt;
The Harvester then proceeded to lock the Rosenante in a Tractor beam like grasp, scan the vessel and transport the Rosenante into the area of the vessel known as the Bone Yard.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Part III: Inside the Harvester&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The arrival inside [[The Harvester]] was anything but accommodating. Upon their rematerialization, the Rosenante was immediately attacked by a group inhabiting the Harvester known as the [[Hur&#039;q]].  These insect-like creatures are those  once referred to in ancient Klingon History as an invader that once tried to conquer the Klingon home world of [[Qo&#039;noS]].&lt;br /&gt;
&lt;br /&gt;
The attack came in the form of a small group of raiders that took advantage of the newly arrived ship&#039;s lack of shields (disrupted by the transport into the Harvester). &lt;br /&gt;
&lt;br /&gt;
Several small groups of assault troops were beamed aboard the Rosenante and these groups managed to tag and steal several supplies from cargo bays as well as a few pieces of minor equipment before they were expelled from the ship. During the skirmish it was determined that the Hur&#039;q were immune to the heavier stun settings on Federation Phasers, and so the crew and security personnel were forced to use the higher level kill and disintegrate settings.&lt;br /&gt;
&lt;br /&gt;
The [[Engineering]] team managed to restore their ship&#039;s only moments after the Hur&#039;q retreated from the ship, although the invaders took all of their dead and it was  believed all of the Rosenante dead as well.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Part IV: The Anti-Hur&#039;q Alliance&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Image:Forest Clearing-Bastion-red.jpg|thumb|300px|right|The Bastion]]&lt;br /&gt;
&lt;br /&gt;
The Rosenante was contacted by the [[Nechani]] ship, [[NSS Oracle&#039;s Tears]] and a meeting was arranged aboard the Bastion.&lt;br /&gt;
&lt;br /&gt;
The Anti-Hur&#039;q Alliance was assembled and comprised of the leaders from the following Species as well as [[Ambassador]] [[Anna Morgan]]:&lt;br /&gt;
&lt;br /&gt;
:The [[Nechani]]&lt;br /&gt;
:The [[Sky Spirits]]&lt;br /&gt;
:The [[Kobali]]&lt;br /&gt;
:The [[Hunters]]&lt;br /&gt;
&lt;br /&gt;
The Rosenante Delegation was lead by [[rank|Commander]] [[Jennifer Caskie]] and was comprised of the following personnel.&lt;br /&gt;
&lt;br /&gt;
:[[Rank|Lieutenant]] [[T&#039;Larah Sullivan]]&lt;br /&gt;
:[[Rank|Lieutenant]] [[Chance Raschen]]&lt;br /&gt;
:[[Rank|Ensign]] [[V&#039;Shera]]&lt;br /&gt;
:[[Rank|Ensign]] [[Dorian Weaver]]&lt;br /&gt;
:[[Rank|Lieutenant]] [[Jon Nayati]]&lt;br /&gt;
:[[Rank|Lieutenant]] [[Thomas Jackson]]&lt;br /&gt;
&lt;br /&gt;
:As well as a few security personnel.&lt;br /&gt;
&lt;br /&gt;
Near the end of the negotiations the meeting was attacked by Hur&#039;q raiders who activated a Transport Inhibitor to trap the Leaders of the alliance in the Bastion. Only Ji&#039;yala had left prior to their arrival.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Part V: The Aftermath&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The aftermath of the battle on the bastion was substantial. The Rosenante Crew lost both Weaver and Sullivan who were killed by Hur&#039;q. Additionally Nayati was missing and  Raschen was critically injured. With such critical officers out of commission, killed or missing, the Rosenante crew are forced to adapt to fill their leadership positions. it later is learned that Nayati was &#039;saved&#039; by the Sky Spirit leader Chaska during the battle. &lt;br /&gt;
&lt;br /&gt;
It is also suspected that the Kobali may be responsible for the missing bodies of the dead crew.&lt;br /&gt;
&lt;br /&gt;
Unknown to the Rosenante crew, Sullivan&#039;s body has undergone the reclamation and is now a member of the Kobali race. &lt;br /&gt;
&lt;br /&gt;
Among those skilled in the battle among the non-Rosenante crew is the Sky Spirit Chief Nekawana and several hunters. Ambassador Morgan has been recovered by members of the Rosenante crew and is currently in sick bay.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Part VI: The Epiphany&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
A survey team lead by Lieutenant Marrow has beamed aboard the Epiphany to begin the survey of her systems in the hopes of reclaiming critical components and salvaging her Main Deflector. Over the course of the next month and a half the Engineering crew of the Rosenante, with assistance from their new alliance members, manage to salvage the Main deflector array and get it installed and operational aboard the USS Rosenante.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Part VII: The Alliance &amp;amp; Escape&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Escape Alliance is formed and all the various species within the Bone Yard of [[The Harvester]] are dedicated to working together to achieve escape. Lieutenant [[Alimi Morrow]] leads a mixed engineering team into the bowels of the Harvester with the goal of disabling the devices Transporters and Tractor beams. That mission is successful.&lt;br /&gt;
&lt;br /&gt;
Additionally the engineering teams work around the clock to modify the Rosenante&#039;s Spiral Warp drive to emit Phased particles.&lt;br /&gt;
&lt;br /&gt;
Using this drive and stabilizing the field with the newly restored navigational array, the Allies are able to escape the Harvester. The allies then parts ways on friendly terms.&lt;br /&gt;
&lt;br /&gt;
==Mission Ten: [[Homecoming]]==&lt;br /&gt;
&lt;br /&gt;
[[Image:Homecoming.jpg|thumb|250px|right|The Rosenante returns to Starbase Geneva]]&lt;br /&gt;
&lt;br /&gt;
After escaping from [[The Harvester]] the [[USS Rosenante]] returns to [[Geneva Station|Starbase Geneva]] for repairs and to give the crew some much needed downtime after their ordeal.&lt;br /&gt;
&lt;br /&gt;
During the three month refit, several members of the crew go on extended leave.  Among those is [[Rank|Lieutenant Commander]] [[Jennifer Caskie]] whose return to her Home in Scotland is under less than ideal circumstances. Her trip is one of necessity rather than desire. She is escorting home the body of her long dead husband Donald Caskie, who was a member of the [[USS Epiphany]] crew. Event though he had been decalred dead nearly two decades earlier, it was disovered that Donald was actually reclaimed by the [[Kobali]] aboard the Harvester. His second death too place during a failed attempt to restore himself to his former life after successfuly restoring [[Rank|Lieutenant]] [[T&#039;Larah Sullivan]] to her previous [[Vulcan]] / [[Human]] heritage after she was killed and reclaimed by the Kobali after a [[Hur&#039;q]] raid.&lt;br /&gt;
&lt;br /&gt;
Additionally, [[Chance Raschen]] and [[T&#039;Larah Sullivan]] are accompanied by Lietenant [[T&#039;Kron]] to [[Vulcan (planet)|Vulcan]] where they will participate in the ancient Vulcan ritual of [[Fal-tor-pan]]. raschen is the recipient of Sullivan&#039;s [[Katra]] after she transferred to him just prior to her death at the hand of a Hur&#039;q subcommander.&lt;br /&gt;
&lt;br /&gt;
Meanwhile back aboard the Rosenante, the ship puts on a masquarade party to help revieve some work related tensions. This party is hosted by Lieutenant [[Thomas Jackson]].  Councilor [[Jon Nayati]] ,the ship&#039;s third officer, attends as does Ensign [[Mitena Rixx]], Head nurse [[Katherine &#039;Kitty&#039; Fisher]] and Doctor [[Sam Lopez]].&lt;br /&gt;
&lt;br /&gt;
Elsewhere, Captain [[Ahmed Ibn Salid]] enjoys a nice relaxing leave on [[Bracas V]] where he enjoys some snorkling and sailing. His trip, however is cut short by a mysterious visit from a [[Dominion]] [[Vorta]] named [[Julman]] and an attending group of [[Jem&#039;Hadar]] soldiers. He isn&#039;t seriously injured although one of the Jem&#039;Hadar are less than pleasant. Other than the initial disagreement, the remainder of the meeting goes along well enough. Julman reveals a terrible peice of information to Salid.&lt;br /&gt;
&lt;br /&gt;
The content of that secret will drive him to consider taking the Rosenante off mission. Is hea leading his ship and crew into a possible Dominion trap or is there a possibility that the information that the Vorta revealed could be true. If it is true, the very future of the [[Alpha Quadrant]] may be at risk.&lt;br /&gt;
&lt;br /&gt;
A few days prior to the relaunch of the Rosenante, Sullivan is promoted to Lieutenant Commander, Raschen to Full Lieutenant and Caskie to Full Commander.&lt;br /&gt;
&lt;br /&gt;
==Mission Eleven: [[Into the Darkness, Go I]]==&lt;br /&gt;
[[Image:Rosenante-Alt-2up.jpg|thumb|right|250px|Battle of Sunali II]]&lt;br /&gt;
After his encounter with [[Julman]], [[Rank|Captain]] [[Ahmed Ibn Salid]] came to a critical decision to break his standing orders to partol the frontier between the [[Cardassian Union]] and the [[United Federation of Planets]].&lt;br /&gt;
&lt;br /&gt;
Instead he ordered the Rosenante off mission towards the [[Ikev Sector]] where indications of a conspiracy to build an [[Omega Device]] was suspected.&lt;br /&gt;
&lt;br /&gt;
En route, a distress signal from the [[Boronite]] mining facility on [[Bardon Alpha]] was intercepted. Ahmed ordered the [[USS Rosenante]] into action, but arrived too late to be of much assistance. By the time that they had arrived, the inhabitants of the facility had been slaughtered, leaving only two survivors. Unfortunately the distress signal had named the attacking starship as the Rosenante despite the fact that the ship was nowhere near the facility. &lt;br /&gt;
&lt;br /&gt;
Suspecting a set-up, Salid prepared to leave the system, but again was unable to withdraw before the arrival of the [[USS Furious]] Commanded by [[Rank|Captain]] [[Saleke]] arrived.&lt;br /&gt;
&lt;br /&gt;
knowing how the situation looked, Ahmed ordered the Rosenante to flee and the Furious pursued. Forced to investigate, Saleke engaged the Rosenante with specially modified [[quantum torpedo]]es which were equipped with [[Cloaking device|phased claoking devices]]. these torpedoes were able to get past the Rosenante&#039;s superior shielding and cause significant damage to the ship.&lt;br /&gt;
&lt;br /&gt;
Only the implementation of a new tactic, now called the [[The Salid Gambit]] allowed the Rosenante to escape into the rough asteroid fields of [[The Mill]]. Ahmed was able to cloak his ship and the furious picking up residual traces of a trail left by the original attacked set of in pursuit as Salid ordered repairs undertaken.&lt;br /&gt;
&lt;br /&gt;
Unknown to both saleke or Salid, the perpetrator in the raid on Bardon alpha was the [[Mirror Universe]] version of Ahmed. He commanded the [[ISS Rosenante]] and had set course to head to [[Hexikor Prime]], with the clear goal of capturing components critical to the completion of an [[Omega Device]].&lt;br /&gt;
&lt;br /&gt;
The ISS Rosenante arrived well before either the Furious or the USS rosenante could intercept her and conducted the raid with expected brutality. The components stolen were  a [[Paratrinic Shield|Paratrinic Shield Generator]] And a [[Class 11 Computer|Class 11 Bioneural Computer]]. The ISS Rosenante departed and headed for thier next target.&lt;br /&gt;
&lt;br /&gt;
The Furious arrived on the scene first and Saleke immediately began an investigation. While that was underway, Salid in the [[USS Rosenante]] arrived in the system under cloak.&lt;br /&gt;
&lt;br /&gt;
Determined not to have a repeat of the encounter at [[Bardon Alpha]], Captain Salid chose to neutralize the threat that the Furious posed by transporting six of their primary power buses off the Furious. These power relay buses, caused the ship to lose all primary power, rendering it unable to use weapons, shields or warp drive. Salid then ordered the surrender of the Furious but was unwilling to accept the surrender of that vessel from their First Officer Commander Erin Sloane. &lt;br /&gt;
[[Image:Omega Device.jpg|thumb|left|250px|Omega Device]]&lt;br /&gt;
Saleke was summoned and his presence was requested aboard the Rosenante. Having been convinced by the data that he had collected thus far in his investigation, Captain Saleke informed Captain Salid that he and his ship were no longer suspects in the attack, nor were they complicit in any plot to acquire and build an [[Omega Device]]. Salid had, independently, arrived at the same conclusion, that the ISS Rosenante, a ship from the Mirror universe was in fact responsible for the attacks. &lt;br /&gt;
&lt;br /&gt;
It was also clear that the Mirror Universe Rosenante was following a pattern that must have been established in their own universe. Which explained how the marauding vessel knew where to acquire the components for the creation of a new Omega Device. &lt;br /&gt;
&lt;br /&gt;
After some discussions, it was decided that the USS Furious and the USS Rosenante would need to combine forces in order to counter the tactical and homicidal threat now posed by the ISS Rosenante. &lt;br /&gt;
&lt;br /&gt;
As long range scans indicated that the Mirror Universe vessel was headed for the [[Kabor Prime|Kabor System]] The Rosenante took the Furious under tow, and using their own shields to protect them, opened a Spiral warp conduit to facilitate maneuvers while the Furious conducted the reinstallation of the power relay buses. &lt;br /&gt;
&lt;br /&gt;
A few days after the attack on the Bynar Facility in the Hexikor system, the ISS Rosenante appeared in the Kabor system. Thier target was a secret production facility known as [[Station Omega]]. The facility had been built by a secret research and development branch of Starfleet Sciences Division during the [[Admiral Doenitz|Doenitz]] regime. Thier primary function was the development of an [[Omega Device]]. &lt;br /&gt;
&lt;br /&gt;
After the end of the [[Federation Civil War]] the facility went underground. Through the actions of a small group of [[Starfleet]] [[Rank|Admirals]], all records pointing to the existence of such a facility were erased and the personnel there continued with their research. Through covert means, the facility was equipped with large Class XII phaser batteries for defense. At the heart of the facilities power center was a stabilized [[Omega Molecule]]. The first that the Station had managed to produce. &lt;br /&gt;
&lt;br /&gt;
The ISS Rosenante arrived in the system, intent on collecting the last few remaining components of the Omega device that they needed to create their own version of the weapon. As the Mirror Universe Ahmed Ibn Salid had worked at this facility in his universe, he had intimate knowledge of the facilities existence and layout. What he had not known was that the station had been armed, as in his universe, it was not protected. &lt;br /&gt;
&lt;br /&gt;
The Mirror universe ship was forced to subdue the facility by force, which cost them a great deal of time, narrowing the lead that they had on their Prime Universe Counterpart the [[USS Rosenante]] and the [[USS Furious]]. This delay would prove to be a great boon to the federation starship over the next few days. &lt;br /&gt;
[[Image:Sunali Sun Destruction.jpg|thumb|right|250px|The Destruction of the Sunali star]]&lt;br /&gt;
Despite this delay, the two [[UFP]] starships did not arrive in the system quickly enough to engage the Imperial Starship. They were however able to track it to it&#039;s next and final location, the [[Sunali II|Sunali System]].&lt;br /&gt;
&lt;br /&gt;
The [[USS Rosenante]] and the [[USS Furious]] entered the [[Sunali II|Sunali System]] to find the [[ISS Rosenante]] engaged in the wanton destruction of [[Cardassian]] merchant shipping. These ships although peaceful, had been destroyed simply because they were Cardassian.&lt;br /&gt;
&lt;br /&gt;
The USS Rosenante ordered the Imperial starship to surrender. That vessel refused.&lt;br /&gt;
&lt;br /&gt;
What followed next was a flurry of conflict, with the Stronger [[ISS Rosenante]] dealing a tremendous amount of damage to both the [[USS Rosenante]] as well as the [[USS Furious]],&lt;br /&gt;
&lt;br /&gt;
During the conflict the Furious engaged her [[Prometheus Class|Tri-vector Attack mode]] to engage the more powerful [[Mirror Universe]] vessel. The Mirror universe [[Andrew Elliot Maddox]] managed to take over the computer of one of the Furious&#039; sections named the Courageous and overload it&#039;s warp core killing all 142 hands on board. &lt;br /&gt;
&lt;br /&gt;
With the battle going against them, captain Salid came up with a plan to stop the Imperial vessel dead in it&#039;s tracks. Building off a suggestion made by [[Rank|Lieutenant]] [[Chance Raschen]], he initiated a transfer of the Omega Directive Protocols into the Imperial Starship&#039;s computer after the junior officer reeled them into communications range for the data transfer. That vessel&#039;s commander, having no experience with the [[Starfleet General Orders &amp;amp; Directives|Omega Directive]] was unable to unlock the ship&#039;s computer, which caused them to lose the battle.&lt;br /&gt;
&lt;br /&gt;
However, the ship had not been neutralized before they had managed to launch the [[Omega Device]] at the [[Sunali II|Sunali]] Sun. Unable to pursue, the Rosenante was forced to allow the [[USS Furious]] to intercept and eventually destroy the weapon.&lt;br /&gt;
&lt;br /&gt;
With the aid of [[Nathan Benoit]] the Furious and the Vigiliant (another element of the Furious), managed to shut down the [[Paratrinic Shield]] protecting the device by bypassing the operating system of the [[Class 11 Computer|Class 11 Bioneural Computer]] that controlled it. With the shields down, The Vigilant was able to destroy the device with Phaser fire just minutes before it would have detonated.&lt;br /&gt;
&lt;br /&gt;
With the battle over, Captain Salid ordered boarding parties to take possession of the [[ISS Rosenante]].&lt;br /&gt;
&lt;br /&gt;
The teams achieved their goals quickly and with little resistance, as the [[Mirror Universe]] Salid had ordered his crew not to resist.&lt;br /&gt;
&lt;br /&gt;
Meanwhile back aboard the USS Rosenante [[Alimi Morrow|Lieutenant Alimi Morrow]] fought to prevent a warp core collapse. his efforts and those of [[Jon Nayati|Lieutenant Jon Nayati]] and [[V&#039;Shera|Ensign V&#039;Shera]] managed to prevent the destruction of the federation vessel. However, it was not without cost. Morrow was seriously injured in the attempt and was treated for severe radiation poisoning. His condition was so critical that he was placed in Stasis until such time as he could receive treatment at [[Geneva Station|Starbase Geneva]]. His life was saved by the quick thinking and intervention of [[Kimiko Ichijo|Doctor Kimiko Ichijo]].&lt;br /&gt;
&lt;br /&gt;
After the Capture of the [[ISS Rosenante]] a deal was struck by which all the data concerning the [[Omega Conspiracy]] in the prime universe would be handed over to Captain Salid and Saleke in exchange for returning the Imperial ship home.  The agreement was made, after some discussion between The two Federation Commanding Officers and the Rosenante&#039;s First officer [[Jennifer Caskie]].&lt;br /&gt;
&lt;br /&gt;
A technical team was assigned to install an [[Interphasic Field Generator]] aboard the Imperial starship, which would force the ship back into it&#039;s normal universe. This same generator would then self destruct, making it impossible for the [[Imperial Union of Planets]] to recreate the devices for their use. Once the device was installed, the imperial ship was returned to the command of the [[Mirror Universe]] Salid and sent home. All indications suggest that the vessel was returned to their proper universe intact.&lt;br /&gt;
&lt;br /&gt;
The Rosenante, towing the [[USS Furious]] then returned to [[Starbase Geneva]] for repairs. &lt;br /&gt;
&lt;br /&gt;
===Mirror Universe Salid===&lt;br /&gt;
&lt;br /&gt;
Ahmed Ibn Salid of the [[Mirror Universe]] is a much different man than the one from our universe. The differences begin early on in his life. &lt;br /&gt;
&lt;br /&gt;
As a teenager, Ahmed showed a distinct aptitude for [[Engineering]]. His status was that of a child prodigy, and he was actually trained as an engineer in the hopes that he would serve in the Imperial Engineering Corps developing weapons and new technology.  He graduated from his classes with honors and was assigned to the [[ISS Templar]], Where he served as an Assistant Chief Engineer. He quickly began to make his way up the chain through deceit or assassination until he reached the rank of Lieutenant and the position of Chief Engineer.&lt;br /&gt;
&lt;br /&gt;
His career was cut short however, when it was discovered that his Father was involved in the planned assassination of the Empire&#039;s [[Klingon]] [[Regent]]. In retaliation, Salid was arrested and shipped to the [[Boronite]] mines on [[Bardon Alpha]]. It was there during his incarceration that he met the future regent [[Admiral Doenitz|Rodrigo Doentiz]]. &lt;br /&gt;
&lt;br /&gt;
Together the two men worked in the mines until the opportunity arose to escape. When that day came, the two men led a slave revolt against the penal colony&#039;s guards. The campaign was swift and brutal, and with the aid of a rebel ship captain, [[Devan Sash]], the two men escaped along with a small cadre of officers, including [[Saleke]], [[Zachary Falthgood]] and [[T&#039;Vhor]]. Later this group would eventually seize control of the leadership of the [[Human|Terran]] Rebellion and later the puppet Government of [[Earth]].&lt;br /&gt;
&lt;br /&gt;
Salid was promoted to Captain of the [[ISS Rosenante]] which became the Flag ship for the newly reformed and reorganized [[Mirror Universe|Imperial Union of Planets]]. His new role put him into direct conflict with several KCA starships, honing his abilities and reputation as an extraordinarily brutal ship commander. His complete dedication and loyalty to Regent Doenitz and the IUP guaranteed his quick rise to a position of power.&lt;br /&gt;
&lt;br /&gt;
In 2408, Ahmed was assigned the task to deploy the [[Omega Device]] against a KCA task force gathering at [[Sunali II]]. The weapon was deployed and it destroyed the enemy ships as well as the traitorous planet, which had defected to the KCA. The [[ISS Rosenante]] was thrown through a dimensional rift into the normal universe.&lt;br /&gt;
&lt;br /&gt;
==Mission Twelve: [[Equals and Opposites]]==&lt;br /&gt;
[[Image:StarbaseGeneva.jpg|thumb|right|300px|Starbase Geneva|200px]]&lt;br /&gt;
&lt;br /&gt;
With the return of the [[USS Rosenante]] and the [[USS Furious]] to [[Starbase Geneva]], refits and repairs from their encounter in the [[Sunali II|Sunali System]] began. With the work taking a great deal of the crews time and efforts, Captain Salid is repeatedly called before members of the admiralty to discuss the unsanctioned nature of his mission as well as reveal details and records of the [[Omega Conspiracy]].&lt;br /&gt;
&lt;br /&gt;
In addition to the briefings and meetings centered around the conspiracy, an official tribunal was called to inquire into the destruction of the  [[USS Furious|Courageous]] during the battle at Sunali II.&lt;br /&gt;
&lt;br /&gt;
The captain is displeased with the findings of the Tribunal, but his hands are tied as he is forced to deal with the harsh political nature of the situation.&lt;br /&gt;
&lt;br /&gt;
==Mission Thirteen: [[The Quondam Season]]==&lt;br /&gt;
[[Image:Iconia planet.jpg|thumb|right|200px|Xega III]]&lt;br /&gt;
The [[USS Rosenante]] is dispatched on a routine resupply mission for the archeological survey team located on [[Xega III]].&lt;br /&gt;
&lt;br /&gt;
The team led by Doctor [[Otto Totenkampf]] has been studying the ruins of the ancient [[Xegan]] civilization for nearly three decades.&lt;br /&gt;
&lt;br /&gt;
Among the tasks assigned to the crew of the Rosenante are standard planetary scans, launch of a pair of orbital satellites to aid the survey team, as well as assisting in planetary thermal and tectonic studies.&lt;br /&gt;
&lt;br /&gt;
Because the planet orbits an Orange giant star which constantly bombards the planet with stellar radiation, which seems to have gathered in the upper ionosphere, the use of transporters is impossible.&lt;br /&gt;
&lt;br /&gt;
The resupply, consisting of a mobile habitation unit, medical and foods supplies, as well as a replacement [[Argo Shuttle|Argo Class]] Shuttle and rover must all be undertaken by shuttlecraft.&lt;br /&gt;
&lt;br /&gt;
Shortly after arriving on the planet however, a strange energy reading is detected from a newly uncovered archeological site. This energy source is emanating from the [[Balancer Machine]], a legendary Xegan construct which was rumored to be able to prevent the planet from being ravaged by the very solar radiation that had caused the decline of the culture that created it.&lt;br /&gt;
&lt;br /&gt;
Suddenly the machine activated, perhaps for the very first time. Massive monoliths burst from the ground every feww hundred miles and rose into the planet&#039;s upper ionosphere. There they began to collect the radiation that was present and generate massive amounts of power into some unseen machine deep beneath the planet&#039;s surface.&lt;br /&gt;
&lt;br /&gt;
The crew of the Rosenante evacuated the archeological team and broke orbit to pbserve from a safer distance, as the monoliths were now creating massive storms in the planet&#039;s thin atmosphere.&lt;br /&gt;
&lt;br /&gt;
After the monoliths gathered energy for a period of roughly two standard days, a buildup was detected in one of the monoliths and a massive beam of light erupted from that monolith travelling towards the planet&#039;s sun.&lt;br /&gt;
&lt;br /&gt;
The affects of that massive energy beam, is unknown however, as at that exact moment, a massive temporal displacement wave, comprised of [[Chroniton]]s and an unidentified particle known as [[Seylerions]] entered the system moving at a speed greater than warp ten.&lt;br /&gt;
&lt;br /&gt;
The Rosenante was caught up in it and was thrust 5 years into the future.&lt;br /&gt;
&lt;br /&gt;
===The Future===&lt;br /&gt;
[[File:Balancer machine.jpg|thumb|300px|left|The Xega III Balancer Machine as seen from orbit]]&lt;br /&gt;
Once the wave had subsided, the crew of the Rosenante began to check their ship&#039;s systems, most notably their chronometers. The wave had caused some minor ships issues, the most serious of whihc was a disruption in the ship&#039;s warp drive systems.&lt;br /&gt;
&lt;br /&gt;
As the crew began repairs and went to work verifying that they had indeed been moved froward in time, Captain Salid ordered a communication sent to [[Starfleet Command]] to inform them of the event.&lt;br /&gt;
&lt;br /&gt;
He was surprised to see that the Rosenante&#039;s communications codes were invalid. At first he received no reply, but eventually, he was contacted by an admiral from command and ordered to hold position. Furthermore he was ordered to maintain a communications blackout, and to await an escort to an unknown location.&lt;br /&gt;
&lt;br /&gt;
Ever suspicious, Captain Salid complied, but prepared his ship for the worst.&lt;br /&gt;
&lt;br /&gt;
===Khitomer===&lt;br /&gt;
&lt;br /&gt;
The Rosenante was met and escorted to [[Khitomer]] by three Federation starships, one of which was a [[Rosenante Class]] vessel.&lt;br /&gt;
&lt;br /&gt;
Once they arrived, it was rather apparent that something massive had happened. A large number of [[starship]]s from the [[52nd Fleet]] had assembled here, along with an even greater number of escorts.&lt;br /&gt;
&lt;br /&gt;
[[Rank|Captain]] [[Ahmed Ibn Salid|Salid]] was ordered to beam down to [[Khitomer Conference|Camp Khitomer]] alone and await a debriefing.&lt;br /&gt;
&lt;br /&gt;
He arrived in the early morning, and was greeted by the sights and sounds of dozens of ship&#039;s commanding officers. Including those from the [[USS Mithrandir]], [[USS Spectre]], [[USS Hades]], [[USS Furious]], and [[USS Boudicca]].&lt;br /&gt;
&lt;br /&gt;
In addition to these officers, [[Rank|Admiral]] [[Robert LoDona]] was brought out of retirement to conduct the debriefing. &lt;br /&gt;
&lt;br /&gt;
Questions concerning the events which brought them here were asked and it quickly became apparent that nearly the entire [[52nd Fleet]] had been affected by the same phenomenon that had pushed the [[USS Rosenante]] forward in time.&lt;br /&gt;
&lt;br /&gt;
Further individual interviews were conducted with the Commanding Officers of the assembled starships before they were allowed to return to their vessels.&lt;br /&gt;
&lt;br /&gt;
Later Starfleet Science teams came aboard and scanned the ship, conducting a series of tests designed to verify the story that had been provided for the disappearance of the ships five years earlier.&lt;br /&gt;
&lt;br /&gt;
In addition to those teams, [[Starfleet Intelligence]] also came aboard to interview various members of the Rosenante&#039;s crew.&lt;br /&gt;
&lt;br /&gt;
After two days of studies and interviews, the rosenante was released from the Khitomer system and headed for [[Starbase Geneva]].&lt;br /&gt;
&lt;br /&gt;
There they underwent some retraining and some minor refits to bring them up to specifications with the technological and professional advances of the last five years.&lt;br /&gt;
&lt;br /&gt;
It was during this time that [[Rank|Commander]] [[Jennifer Caskie]] resigned, as she had discovered that her son Ian had gone missing during the five years prior.&lt;br /&gt;
&lt;br /&gt;
She was discharged from service.&lt;br /&gt;
&lt;br /&gt;
==Mission Fourteen: [[The Gilded Man]]==&lt;br /&gt;
[[File:Scout.jpg|thumb|400px|right| The USS Bohrs]]&lt;br /&gt;
&lt;br /&gt;
In 2314, nearly a decade after the Champlain&#039;s initial sensor readings of a Federation- style warp signature, in the [[Irlix|Irlix System]] the [[USS Bohrs]], a [[Mission Scout]] vessel, (&#039;&#039;&#039;NCC-369477&#039;&#039;&#039;) was dispatched to follow-up on those inital findings.&lt;br /&gt;
&lt;br /&gt;
The Bohrs proceeded to the Irlix system and utilizing her [[Cloaking device]] began to collect cultural and military data in an attempt to isolate the original source of the initial Federation warp signature.&lt;br /&gt;
&lt;br /&gt;
The Bohrs was on station for only a few weeks, when a computer attack shut down her cloaking device and left her vulnerable to attack by military starships belonging to the [[Rhone Union]].&lt;br /&gt;
&lt;br /&gt;
The Bohrs was captured and forced down on the [[planet]] [[Irlix]], where it was stored in the [[Seliya Facility]].&lt;br /&gt;
&lt;br /&gt;
A few days after the capture of the Bohrs, the [[USS Rosenante]] was tasked with the rescue of the crew of the Bohrs as well as the recovery and/or destruction of the starship. As a secondary objective, they were tasked with the discovery of the sudden technological boost found in Irlixian society which was inconsistent with the rest of their technological development.&lt;br /&gt;
&lt;br /&gt;
Because of a significant threat to the Rosenante, in light of the events leading up to the capture of the Bohrs, [[Rank|Captain]] [[Ahmed Ibn Salid]] decided to drop a cosmetically altered away team on the surface of the planet.&lt;br /&gt;
&lt;br /&gt;
After arriving in the Irlix system, the [[USS Rosenante]] approached the planet from a polar orbit acheived by following a very broad hyperbolic course. Once in position, the Away Team was sent down to the planet&#039;s surface, specifically to [[Khoda City]], in pairs, to minimize the chance of detection.&lt;br /&gt;
&lt;br /&gt;
The Away Team made their way to the Hotel Votul, a buisness known locally for allowing [[Irlixian|Gab]] males and [[Irlixian|Mol]] females to mingle in a social setting where they would not normally be permitted to do so. The meeting place at the hotel is marked by an interplexing communications beacon set up by [[Chance Raschen]]. The final meeting spot was a public restroom on the first floor of the hotel.&lt;br /&gt;
&lt;br /&gt;
Things get interesting when [[Mike Rosenbauer]]  shows up with [[Ios Malinae]], an [[Irlixian]] female, that he had &#039;rescued&#039; earlier from an assault and attempted rape. Ios apparently recognized Mike&#039;s blood, seeping from a broken lip as belonging to a [[Human]] rather than an Irlixian. She then revealed through an encounter with her mother, [[Sola Malinae]] that she was associated with the secret [[Seliya Facility]] where the research and development of the Alien ([[Federation]]) technology was being studied and retro-engineered.&lt;br /&gt;
&lt;br /&gt;
Taking a risk, Mike brought her to the meeting to allow [[Rank|Lieutenant Commander]] Sullivan a chance to question her and determine if she possessed any knowledge that may aid the Away Team in their mission.&lt;br /&gt;
&lt;br /&gt;
She was not, however, the only visitor to arrive at the Hotel Votul.&lt;br /&gt;
[[File:Dual moon planet.jpg|thumb|400px|left|Irlix]]&lt;br /&gt;
Senior Detective [[Vilox Nigo]], a member of the Special Police responsible for dealing with espionage inside the Rhine Union, detected the beacon and set into motion police resources in an attempt to capture the away team, which he believed were spies from one of the other major political powers on [[Irlix]].&lt;br /&gt;
&lt;br /&gt;
When the raid began, the away team put up more of a resistance than Vilox had anticipated and managed to escape although [[T&#039;Larah Sullivan|Sullivan]], [[Louis Remey]], [[Steven Wade Matrix|Steve Matrix]] and others were injured in the fighting to some degree.&lt;br /&gt;
&lt;br /&gt;
Thanks to the hard efforts of [[Sanok]], [[Thomas Jackson|Tom Jackson]] and [[Steven Wade Matrix|Steve Matrix]], the Away Team managed to escape the premises, narrowly dodging a perimeter of Police Snipers and pursuing law enforcement forces.&lt;br /&gt;
&lt;br /&gt;
While the away team found themselves in a pickle on the surface the [[USS Rosenante]] was facing difficulties of her own. under the command of [[Rank|Captain]] [[Ahmed Ibn Salid| Salid]], the Rosenante was forced to break orbit and begin a series of maneuvers to avoid detection and capture once it became apparent that the Irlixians were able in some manner to detect the cloaked [[Federation]] [[Starship]].&lt;br /&gt;
&lt;br /&gt;
As the goal was to avoid a confrontation and since the means by which the Irlixians were detecting the position of the Rosenante was unknown, the captain ordered the ship to displace frequently to delay any potential military actions between the Irlixian Fleet and the Rosenante.&lt;br /&gt;
&lt;br /&gt;
It was also interesting to note that the detection means was neither immediate nor precise and that meant that simple maneuvering whenever a course change took place among the Irlixian patrol craft happened were sufficient to keep the Rosenante safe from immediate harm.&lt;br /&gt;
&lt;br /&gt;
With the Rosenante well away from the planet, they found themselves unable to respond to the sudden appearance in the system of a Federation [[Danube Class Runabout|runabout]] without incurring significant risk to the Rosenante.&lt;br /&gt;
&lt;br /&gt;
This runabout was manned by two new recruits to the Rosenante [[Rank|Ensign Junior Grade]] [[Eian O&#039;Neill]] and Ensign Junior Grade Machaire Rabhartaigh. they had been assigned to the ship, but they had not been briefed on the nature of the Rosenante&#039;s mission and therefore found themselves entering hostile space unexpectedly. &lt;br /&gt;
&lt;br /&gt;
[[image:Irlixian Girl2.jpg|thumb|400px|right|An Irlixian Female]]&lt;br /&gt;
&lt;br /&gt;
The [[Irlixian]]s attacked. The result was the crippling of the runabout, which forced O&#039;Neill to crash land the damaged ship outside the Capital of the [[Rhone Union]], [[Khoda City]].&lt;br /&gt;
&lt;br /&gt;
Within minutes of the crash, however, the shuttle was surrounded by a small squad of Irlixian police. This prevented the immediate escape of the crash survivors.&lt;br /&gt;
&lt;br /&gt;
All hope was not lost, however, as Ensign O&#039;Neill had managed to send out a brief mayday message that alerted the away team already on the planet to their plight.&lt;br /&gt;
&lt;br /&gt;
A quick rescue and recovery mission was organized by the away team, still on the planet.The team made good speed from the safe house to the crash site where they relieved the surrounded crash victims before lead elements of the Secret police force under [[Vilox Nigo]] arrived. With the survivors recovered the extraction team returned to the safe house to await contact with the Rosenante and to continue medical treatment of the wounded.&lt;br /&gt;
&lt;br /&gt;
Meanwhile,  back aboard the Rosenante, it was becoming more difficult to avoid the ever shrinking search net of the Irlixian starships.&lt;br /&gt;
&lt;br /&gt;
It was the sudden epiphany offered up by Trade Winds Bar manager, and ex-intelligence officer T&#039;Lela, that the Rosenante was finally able to discover the means by which they were being tracked.&lt;br /&gt;
&lt;br /&gt;
The Irlixians were managing to track the automated communications data streams that all Federation starships use to connect to the [[Memory Alpha]] database as well as to navigational satellites. And while unable to disable this uplink, the deployment of some [[Stealth Buoy]]s, set to monitor the same frequency created a series of decoys that would confound the Irlixians and allow the Rosenante to slip free and return to [[Irlix]] to get an update from the away team there.&lt;br /&gt;
&lt;br /&gt;
When the Rosenante took up a standard orbit and made contact with the away team, it quickly became apparent that the initial mission parameters had no real chance of success. As a result Salid ordered the away team and their civilian adviser, Ios, beamed back aboard the Rosenante.&lt;br /&gt;
&lt;br /&gt;
While the members of the away team visited Sickbay to have the last of their injuries tended to and to have the cosmetic surgeries undone, Captain Salid was speaking with the civilian advise Ios concerning the situation. It was from that brief meeting and interview that a new plan of action was hatched.&lt;br /&gt;
&lt;br /&gt;
Once the away team was restored, and with the Rosenante managing to remain undetected at the polar orbit of the planet, Captain  Salid called a briefing where he outlined the new plan.&lt;br /&gt;
&lt;br /&gt;
He had become convinced after hearing about the history of the Rhone Union from Ios that a member of the Medea crew had managed to infiltrate the government and violated the [[Prime Directive]] for their own benefit.&lt;br /&gt;
&lt;br /&gt;
This in turn led the Captain to implement a three pronged plan of action that would achieve a variety of mission goals simultaneously.&lt;br /&gt;
&lt;br /&gt;
First Salid and [[Louis Remey]] would be making an appearance at a scheduled media conference being put forward by [[Ono Nakamura|Khoda Rhone]]. By hijacking the media feeds of the planet, Salid could insure that the message that he wanted to spread across the planet would remain uninterrupted. Remey would be responsible for running scans of the Rhone Union leadership present in an effort to ferret out the traitor in their midst.&lt;br /&gt;
[[File:Nakamara.jpg|thumb|left|300px|Ono Nakamura in 2393]]&lt;br /&gt;
While Salid and Remey acted as investigators, instigators and distraction, a second team led by [[Rank|Lieutenant]] [[Steven Wade Matrix]] and consisting of [[Marta Nunez]], [[Sanok]] and [[Robert Smith]] would conduct a raid against Rhone Union government offices in an attempt to locate information on the location of the Hostages from the [[USS Bohrs]]. Once that information was located, a third team led by [[Mike Rosenbauer]], and consisting of [[Kimiko Ichijo]], [[Sam Lopez]], and [[Eian O&#039;Neill]] would begin the operation to rescue the hostages while Matrix&#039;s team beamed to the sight of the Bohrs and prepared the ship for departure.&lt;br /&gt;
&lt;br /&gt;
Unfortunately, some parts of the plan did not quite happen as planned. Although The rescue team was deployed, matrix&#039;s team was forced to remain hidden in the government offices due to the fact that the Rosenante, Commanded by [[Rank|Commander]] [[T&#039;Larah Sullivan]], and aided by [[Rank|Lieutenant]] [[Thomas Jackson]] and [[Chance Raschen]], was forced into a military encounter with Rhone Union [[Starship]]s commanded by Fleet Commander [[Frazil]].&lt;br /&gt;
&lt;br /&gt;
Despite this setback, Rosenbauer&#039;s team managed to rescue not only the hostages from the Bohrs, but also [[Rank|Lieutenant]] [[Ben Soma]], previously of the [[USS Mithrandir]] and [[Rank|Lieutenant]] Doug Masters. The reinforced team managed to make their way to the Bohrs, and after a spectacular diversion with a damaged runabout, destroy the partially restored wreckage of the [[USS Medea]] and allow the Bohrs to escape the hanger once her systems were restored.&lt;br /&gt;
&lt;br /&gt;
While members of his crew were engaged in various levels of their portion of the operation, Captain Salid managed to cause Khoda Rhone, whom Remey had identified as [[Ono Nakamura]], previously the Chief Engineering Officer of the [[USS Medea]] to confess to his crimes.&lt;br /&gt;
&lt;br /&gt;
As expected, the [[Irlixian]]s were shocked and Khoda Rhone was ousted from power. He was taken into custody by Remey, while Salid attempted to rectify the cultural contamination that Nakamura had caused.&lt;br /&gt;
&lt;br /&gt;
After an additional eight days of negotiations, the governments of Irlix agreed to establish a provisional planetary government under the leadership of [[Ios Malinae]]. With the arrival of starships from the [[Federation Diplomatic Corps]], the USS rosenante was released from their mission.&lt;br /&gt;
&lt;br /&gt;
They aided in the repairs of the [[USS Bohrs]] before heading to [[Starbase 989]] for some much needed upgrades and R&amp;amp;R.&lt;br /&gt;
&lt;br /&gt;
==Mission Fifteen: [[Touch of the Eidolon]]==&lt;br /&gt;
[[File:Starbase 989.jpg|thumb|right|250px|Starbase 989]]&lt;br /&gt;
&lt;br /&gt;
The [[USS Rosenante]] after returning from [[Irlix]] system is long overdue for some much needed Rest and relaxation time on [[Starbase 989]].The ship put into dock and [[Rank|Captain]] [[Ahmed Ibn Salid|Salid]] held a briefing to bring his crew up to specs for the refit and resupply operations that would need to take place prior to the Rosenante&#039;s departure.For a change it looked as if everything would go well, and that the crew wouldn&#039;t be drawn into any unwanted scuffles with station personnel.It also seems that the reality of things is always different from the desired.&lt;br /&gt;
&lt;br /&gt;
Word quickly spread through the crew that the Starbase was holding the [[Alpha Quadrant|Alpha]]-[[Beta Quadrant]] wide martial arts tournament. The prize was a substantial [[latinum]] prize as well as the title of Champion of two quadrants. The following personnel from the Rosenante entered the tournament:&lt;br /&gt;
&lt;br /&gt;
*[[Kimiko Ichijo]]&lt;br /&gt;
*[[Ben Soma]]&lt;br /&gt;
*[[Eian O&#039;Neill]]&lt;br /&gt;
&lt;br /&gt;
They each competed against their respective opponents and were each in turn disappointed with the scores handed down to them by the panel of judges, which included, [[Ieko Takawa]]. However, rumor soon arose that the tournament may be fixed.  This coupled with information gathered by Soma during his investigation of Captain Taylor&#039;s murder, indicated that somehow the two could have been connected.&lt;br /&gt;
&lt;br /&gt;
[[File:Joseph Taylor.jpg|thumb|left|200px|Captain Joseph Taylor.]]&lt;br /&gt;
The day after the arrival of the [[USS Rosenante]] reports were made of the discovery of the body of [[Rank|Captain]] [[Joseph Taylor]], who was the commanding officer of [[Starbase 989]].  The captain was found dead in his quarters by a security officer from the station who had been dispatched when the Captain failed to respond to calls from his first Officer [[Rank|Lieutenant]] [[Kraal]].&lt;br /&gt;
&lt;br /&gt;
Almost immediately, Kraal contacted [[Rank|Captain]] [[Ahmed Ibn Salid]] and notified him of the grisly discovery. Citing Regulations, Salid, then assumed command of the investigation and assigned the Rosenante&#039;s own  Chief Security Officer [[Ben Soma]] to investigate.&lt;br /&gt;
&lt;br /&gt;
The body was recovered by the Rosenante team and a thorough study of the crime scene was conducted by [[Rank|Lieutenant]] [[Steven Wade Matrix]], and [[Eian O&#039;Neill]]. In addition to the survey of the crime scene, Doctor [[Kimiko Ichijo]] and Doctor [[Sam Lopez]] undertook an autopsy, to determine the cause of death.&lt;br /&gt;
&lt;br /&gt;
From the combined results of these studies clues and mysteries began to form, throwing out a number of plausible scenarios as to how the murder could have been conducted. Among the most puzzling of these mysteries was the nature of the murder weapon, a hook shaped spike that seemingly dematerialized inside the wound after the deed was done. In addition, coupled with the fact that the Captain had secured his personal quarters, the scene of the murder, with a very high level encryption that could only be overridden by other [[Starfleet]] officers of flag rank or greater, left the crew wondering who on the station had the ability to reach the obviously paranoid captain.&lt;br /&gt;
&lt;br /&gt;
To further complicate matters, the captain had no defensive wounds on his body, which would indicate that death was sudden and that the Starbase&#039;s commanding officer did not expect an attack.&lt;br /&gt;
&lt;br /&gt;
A short list of suspects was assembled, after further questioning and DNA evidence discovered that the Captain had been having an affair with two of his junior officers. Early in the investigation, there were strong indications that Captain Taylor may have been corrupt and that his murder may have been caused by a business deal going poorly.&lt;br /&gt;
&lt;br /&gt;
The chief suspects were:&lt;br /&gt;
&lt;br /&gt;
*[[Braak]]&lt;br /&gt;
*[[Pez]]&lt;br /&gt;
*[[Quol Nor]]&lt;br /&gt;
* Doctor [[Gena Harvey]]&lt;br /&gt;
* [[Rank|Lieutenant]] [[Adraa Mosul]]&lt;br /&gt;
*[[Ieko Takawa]]&lt;br /&gt;
&lt;br /&gt;
[[File:Harveq.jpg|thumb|250px|right|The Romulan freighter Harveq]]&lt;br /&gt;
The following day, a second body was discovered by a [[Starfleet]] engineer on duty on the station. He discovered the body of the [[Orion]] Cargo Master [[Nargo]]  of the [[Romulan]] [[starship|freighter]] [[Harveq]]. The ship&#039;s captain was [[T&#039;Sek]], a Romulan merchant. T&#039;Sek&#039;s grandfather is [[Chairman|Vice-Chairman]] [[Somek]] of the [[Romulan Tal Shiar]].&lt;br /&gt;
&lt;br /&gt;
Before the Station security personnel could arrive, however, T&#039;sek and some of his Orion crew recovered Nargo&#039;s body and took it aboard their ship.  When [[Ben Soma]] and his team from the Rosenante arrived, Soma was unhappy with the turn of events and planned to take action to deal with the situation.&lt;br /&gt;
&lt;br /&gt;
After some careful consideration, Soma assigned [[Sanok]] to open discussions with the Romulan ship captain. Little did they know, T&#039;Sek had full intentions of inviting them aboard the [[Harveq]]. The captain had four members f the Rosenante team transported aboard the [[Harveq]], [[Kimiko Ichijo]], [[Ben Soma]], [[Sanok]] and [[Eian O&#039;Neill]]. They were greeted by captain T&#039;Sek and an armed [[Orion]] security team. This event was initially misinterpreted by the away team as aggression, when in fact T&#039;Sek, was merely concerned with the appearance of the situation and did not wish to take a chance that the Starfleet officers were going to attempt to arrest him for interfering with their investigation.&lt;br /&gt;
&lt;br /&gt;
Once the away team was disarmed, the security detail relaxed and T&#039;Sek was amiable to the officers.&lt;br /&gt;
&lt;br /&gt;
[[Image:Holodeck empty.jpg|thumb|250px|left]]&lt;br /&gt;
Meanwhile, it was discovered that an upgrade request for the [[USS Rosenante]] to become upgraded to fully holo-capable had been filed by the new ACEO [[Eian O&#039;Neill]]. This of course, immediately set of a series of alerts, since O&#039;Neill was fully aware that the Rosenante was already completely Holo-capable. &lt;br /&gt;
&lt;br /&gt;
A quick investigation led the security team of the [[USS Rosenante]] to believe that someone had managed to steal a biometric fingerprint signature belonging to the officer.  When questioned, O&#039;Neill revealed that he had, in fact, used his finger print in two places on the station. &lt;br /&gt;
&lt;br /&gt;
The first was the Martial Arts Tournament on [[Starbase 989]]. The second was with [[Quol Nor]] when he booked [[Holodeck|Holosuite]] time on the station so that he could work on a special holoprogram to allow him to spend Christmas with his family, who were several [[Light Year]]s away.&lt;br /&gt;
&lt;br /&gt;
[[Ben Soma]] ordered O&#039;Neill to investigate.&lt;br /&gt;
&lt;br /&gt;
Those, it seemed were not the only technical difficulties facing the Rosenante. When Starbase engineers began their upgrade cycles, they managed to cause significant processing loss to the Rosenante&#039;s [[Computer Core]]s.  This caused a significant delay in the processing of the data collected at the crime scene by [[Steven Wade Matrix]]. In addition, the interlinks connecting the Rosenante to the Starbase were also damaged, meaning that the crew was unable to borrow processing time from the starbase.&lt;br /&gt;
&lt;br /&gt;
[[File:Rosk.jpg|thumb|right|200px|Doctor Rosk]]&lt;br /&gt;
Aboard the [[Harveq]], while [[Kimiko Ichijo|Doctor Ichijo]] and [[Sanok]] were meeting with [[Rosk|Doctor Rosk]] concerning the murder of [[Nargo]], [[Ben Soma]] and [[Rank|Ensign]] [[Eian O&#039;Neill]] were meeting with [[T&#039;Sek]].&lt;br /&gt;
&lt;br /&gt;
The meeting went well, with T&#039;Sek offering  a significant piece of the murder puzzle to the two officers in the form of a [[Cardassian]] [[Optolythic Data Rod]], which are renowned for their difficulty to forge.&lt;br /&gt;
&lt;br /&gt;
The data on the rod pointed firmly to the [[Ferengi]] [[Quol Nor]] as the Captain&#039;s murderer, but as the [[Romulan]] did not wish to testify, the investigation would need further evidence in order to arrest the Ferengi for the [[Rank|Captain&#039;s]] murder.&lt;br /&gt;
&lt;br /&gt;
During the second day of the tournament, Ichijo, Soma and O&#039;Neill confronted the senior judge [[Ieko Takawa]]. Their assertions caused the man to admit to his unwilling involvement in the fixing of the tournament, which indirectly had caused Taylor&#039;s death. He also directly connected  [[Quol Nor]] to the tournament, providing, for the first time a solid motive for the Ferengi. The tournament was suspended and all judgements withdrawn.&lt;br /&gt;
&lt;br /&gt;
[[File:Assassin Hologram.jpg|thumb|left| 350px|Quol Nor&#039;s Assassin Hologram]]&lt;br /&gt;
Convinced that the data was solid and needing more evidence that the [[Assassin Hologram]] was indeed connected to [[Quol Nor]] Soma, Ichijo, O&#039;Neill and Sanok devised a plan to lure the program in so that it could be neutralized and it&#039;s subroutines studied. the plan was simple in its design although rather complex in execution. After reactivating and securing the Holographic systems aboard the Rosenante, [[Eian O&#039;Neill]] prepared to isolate and neutralize the Program once it appeared on the Rosenante.&lt;br /&gt;
&lt;br /&gt;
To insure that it would appear, [[Sanok]] would activate the [[Data Cube]] that was recovered from [[Rank|Captain]] [[Joseph Taylor|Taylor&#039;s]] quarters where it had been disguised as a [[latinum]] sheathed moving sculpture.  Group gambled that the reactivation  of the data cube would alert either the program or it&#039;s [[Ferengi]] controller and that the end result would be that the program would attempt to recover the cube at all costs. With Sanok playing bait, [[Ben Soma]] and [[Kimiko Ichijo]] stood by to render assistance, while [[Eian O&#039;Neill]] would isolate the program.&lt;br /&gt;
&lt;br /&gt;
The plan was a qualified success, as the program appeared as expected. Although O&#039;Neill was quick the program was able to slightly injure both Sanok and Soma before it could be isolated completely.&lt;br /&gt;
&lt;br /&gt;
[[File:Quol Nor and Thugs.jpg|thumb|right|200px|Quol Nor and a pair of Nausicaan Enforcers]]&lt;br /&gt;
Soma, Sanok and O&#039;Neill along with a great many members of base security tracked [[Quol Nor]] down to his place of business where he was arrested by the Security team. The Ferengi threatened that Ferengi lawyers were far superior to anything that the federation possessed and that the Assassin Hologram was sentient, a claim that would later be overturned by a federation panel of experts. The program while highly sophisticated lacked the ability to adapt beyond certain pre-programmed parameters. &lt;br /&gt;
&lt;br /&gt;
The Murderer was brought to justice.&lt;br /&gt;
&lt;br /&gt;
==Mission Sixteen: [[Just Another Saturday Night]]==&lt;br /&gt;
&lt;br /&gt;
[[File:Vexarak Spoiler.png|thumb|left|200px|A Vexarak Spoiler]]&lt;br /&gt;
&lt;br /&gt;
While on shore leave aboard [[Starbase 989]] Captain Salid and the crew of the Rosenante are tied up in a crisis unlike any other that they have faced. &lt;br /&gt;
&lt;br /&gt;
The [[Tellarite]] freighter [[Moarvol]] inadvertently managed to bring a colony of [[Vexarak Spoiler]]s aboard the starbase in a shipment of &lt;br /&gt;
&lt;br /&gt;
[[Magnesite]] ore collected from the [[Zeta Draconis System]].&lt;br /&gt;
&lt;br /&gt;
These parasites consume metals and feed off of energy that they consume from it&#039;s breakdown. They are also capable of feeding from raw plasma.&lt;br /&gt;
&lt;br /&gt;
As a New Year&#039;s Party was underway on the Promenade, the Spoilers escaped their holding bin and began to ingest critical components of the starbase&#039;s power distribution system. This resulted in a cascade failure that plunged the starbase into complete power failure.&lt;br /&gt;
&lt;br /&gt;
When inhabitants of the starbase realized that the back up systems were not coming on-line they [[riot]]ed. Several members of the ship&#039;s crew along with members of the crew serving aboard the [[USS Boudicca]], were celebrating at [[The County Cork]] during the incident.&lt;br /&gt;
&lt;br /&gt;
When riots broke out, they were forced to defend themselves as well as attempt to restore orders and emergency services.&lt;br /&gt;
&lt;br /&gt;
Over the course of the next twenty-four hours, crews from both starships worked in concert to provide services, repairs and power to the starbase. Eventually, several methods were devised to deal with the infestation. Over the following weeks repairs to the starbase were conducted.&lt;br /&gt;
&lt;br /&gt;
After the incident Ahmed was asked and accepted the honor of marrying his long-time friend [[Thomas Jackson]] to [[Dahlia Jackson]] a woman that he had married earlier by [[Ferengi]] contract. The marriage was a formality to honor Jackson&#039;s [[human]] heritage. The ceremony took place at [[Rothal Chapel]] aboard [[Starbase 989]].&lt;br /&gt;
&lt;br /&gt;
==Mission Seventeen: [[Once More Into The Breach]]==&lt;br /&gt;
[[File:Dovek II.jpg|thumb|250px|right|Dovek II]]&lt;br /&gt;
After the near destruction of [[Starbase 989]], the crews of the [[USS Boudicca]] and the [[USS Rosenante]] were ordered to form a Task Force under the command of [[Rank|Captain]] [[Ahmed Ibn Salid]].&lt;br /&gt;
&lt;br /&gt;
After a flag level briefing, in which concerns over recent [[Borg]] activity in the [[Dovek II|Dovek System]], Captain Salid ordered the two ships of the task force immediately underway to the area of Borg activity for the purpose of locating the Borg forces there and determining the nature of their actions.&lt;br /&gt;
&lt;br /&gt;
Salid ordered the two ships to enter the system in such a manner as to utilize the natural formations to aid in the covert approach of the two ships. With the bulk of the Borg activity taking place in orbit around [[Dovek II]], salid and the crew of both ships begin to do research in the hopes of predetermining the potential threat of the Borg Activity.&lt;br /&gt;
&lt;br /&gt;
From the very beginning there were concerns, as a new type of Borg vessel, designated a [[Borg Pyramid]] was seen accompanying a [[Borg Tactical Cube]]. This was a strong indicator to Salid that the mission was sensitive and possibly militaristic in nature. &lt;br /&gt;
&lt;br /&gt;
When later research proved that the Dovek system had once been a part of the now extinct, but once very technologically advanced [[Tkon Empire]], Ahmed&#039;s worst fears came to the forefront.&lt;br /&gt;
&lt;br /&gt;
Upon arriving in the Dovek System, Salid ordered both ships to remain hidden behind Dovek II&#039;s only moon. From there a series of reconnaissance probes were launched in an attempt to gather information remotely. This failed due to the Borg&#039;s use of an [[Antiproton]] weapon for the purpose of large scale excavation on the planet&#039;s surface.&lt;br /&gt;
[[File:Beam attack on planet.jpg|thumb|left|300px|The Antiproton beam strikes Dovek II]]&lt;br /&gt;
Blinded due to the [[Subspace|Subspace Interference]], Salid moved forward with a plan to launch the [[Lorimar Class Runabout]] Lorimar, on an intelligence gathering mission. The runabout was performing well, apparently unheeded by the Borg [[starship]]s until [[Rank|Lieutenant]] [[Detron Trei]] managed to make contact with the [[Borg Collective]] in an attempt to cause panic amongst the [[Borg Drone]]s.&lt;br /&gt;
&lt;br /&gt;
Instead of causing panic, despite orders to not interfere, the telepathic contact made the Borg leader [[Volus]] aware of the [[Federation]] presence in the system. He ordered the Runabout attacked, and as a result the vessel crash-landed on the surface of [[Dovek II]].&lt;br /&gt;
&lt;br /&gt;
It was around this time that the Borg also uncovered their apparent goal, a [[Tkon Nanosphere]] that held incredible potential as a weapon to be used to assimilate [[Earth]].&lt;br /&gt;
&lt;br /&gt;
Now faced with a pair of problems, Salid ordered two separate missions. The first to rescue any crash survivors, while the second would cause plausible asset denial of the sphere from the Borg through the deployment of an [[antimatter]] mine.&lt;br /&gt;
[[File:Mine Detonation.jpg|thumb|250px|right|The Antimatter Mine detonating on Dovek II]]&lt;br /&gt;
With The Borg capital ship&#039;s positioned in such a way as to block any attempts at either mission, Salid ordered both the [[USS Rosenante]] and the [[USS Boudicca]] to act as a screening force against the Borg vessels in an attempt to drawn them away from the [[planet]].&lt;br /&gt;
&lt;br /&gt;
The two ships of the small task force attacked the Borg forces and successfully caused them to displace their position, which allowed the two away teams to penetrate the planet&#039;s atmosphere and carry out their missions.&lt;br /&gt;
&lt;br /&gt;
The crash survivors were rescued and the Antimatter mine deployed, and salid had thought that the Borg operations were thwarted until indications were seen that the [[Borg]] were opening a [[Temporal Vortex]]. realizing that the Collective intended to assimilate the device in the past, Salid ordered both the [[Federation]] [[starship]]s to follow and engage.&lt;br /&gt;
&lt;br /&gt;
On the other side of the vortex, the Federation ships found themselves in the Age of Makto, near the end of the [[Tkon Empire]]. They managed to destroy both the [[Borg Pyramid]] and the [[Borg Tactical Cube]], but not before both ships were boarded during the fight, and [[Borg Drone]]s sent to the surface of the planet, where assimilation of the [[Tkon Nanosphere]] began.&lt;br /&gt;
[[File:Temporal Vortex.jpg|thumb|left|300px|A Temporal Vortex]]&lt;br /&gt;
Fighting a desperate defensive action for their ships, the Federation crews were unable to prevent the [[assimilation]] of the nanosphere. As the Sphere lifted off the planet, Salid ordered one final ditch attempt to purge the two ships of Borg, using a specialized code that attacked the [[Borg]] [[Nanoprobe]]s.&lt;br /&gt;
&lt;br /&gt;
Despite an assassination attempt on his life and with both ship&#039;s free of Borg influence, and the nanosphere opening another [[Temporal Vortex]] Salid once again ordered pursuit.&lt;br /&gt;
&lt;br /&gt;
This time the two ships ended up in Earth&#039;s prehistoric past during a period called the [[Cretaceous Period]]. The two ships were unable to deal any damage to the [[Tkon]] device as long as it&#039;s shields remained operational, so Salid ordered a small elite security force to beam aboard the ship using a theoretical Transporter algorithm.&lt;br /&gt;
[[File:Chicxulub close impact.jpg|thumb|250px|right|The impact with the crust of the planet]]&lt;br /&gt;
A tremendous fight ensued and the away team was barely beamed off the sphere, before the combined firepower of the [[USS Boudicca]] and the [[USS Rosenante]] destroyed it. Along with the destruction of the sphere came that of the Borg leader [[Volus]] and the Tkon scientist [[D&#039;askto]] who had joined forces with the away team.&lt;br /&gt;
&lt;br /&gt;
Although they had destroyed the most immediate threat of assimilation in [[Earth|earth&#039;s]] ancient past, the bulk of the sphere rained down on the planet nearly wiping out all life there.  Ironically, it was this event that wiped out the dinosaurs and allowed [[Human|Humanity]] to evolve.&lt;br /&gt;
&lt;br /&gt;
After several days of repairs and hard work, The combined crews managed to activate the Borg Temporal equipment that was left behind by the Borg Occupation of their ships and used it to return home to the present.&lt;br /&gt;
&lt;br /&gt;
The two ships then limped home to a hero&#039;s welcome.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Mission Eighteen: [[Personal Logs]]==&lt;br /&gt;
With the refit of the [[USS Rosenante]] underway after the battle at [[Dovek II]], Ahmed decided to take some time off and enjoy some friendly competition in the boxing arena on [[Starbase Geneva]].  However things did not go according to plan when he was requested by the [[Rank|Admiralty]] to participate in the general mast hearings for [[Detron Trei]] and [[Andrew Elliot Maddox]], two officers that were under his command during the Dovek II incident.&lt;br /&gt;
[[File:S31.jpg|thumb|left|300px|The symbol for Section 31]]&lt;br /&gt;
He agreed, and after some deliberation a series of disciplinary actions were undertaken against both the officers. He was later to discover that [[Rank|Captain]] [[Alan Durand]] had resigned from the fleet as a result of his actions at Dovek, despite the fact that Salid and other members of the general Admiralty did not feel his performance was inadequate to the situation.&lt;br /&gt;
&lt;br /&gt;
This temporarily left Salid in command of the [[USS Boudicca]] as well as the [[USS Rosenante]] until [[Rank|Captain]] [[Calvin Capps]]  arrived to take command of the Boudicca.&lt;br /&gt;
&lt;br /&gt;
During this time, [[Rank|Commander]] [[Thomas Jackson]] was reassigned to the USS Boudicca as her first officer, displacing her prior first Officer, [[Rank|Commander]] [[Jennifer Caskie]].&lt;br /&gt;
&lt;br /&gt;
For reasons unclear, Caskie was relieved of her command position and reassigned to the Rosenante as their [[Medical Officer|Chief Medical Officer]]. Ahmed was glad to see her return to the ship.&lt;br /&gt;
&lt;br /&gt;
Also during this Ahmed found himself suddenly involved in a situation with [[Section 31]], when they kidnapped a member of his crew, [[Rank|Ensign]] [[Jessica Signos]] after [[Ahmed Ibn Salid]] had reported her dual nature to [[Starfleet Intelligence]].&lt;br /&gt;
&lt;br /&gt;
The kidnapping was actually a ploy by SFI to flush out the [[Section 31]] Operatives on [[Starbase Geneva]]. Salid became involved when he felt that his officer was placed at undue risk as a result of SFI&#039;s slow response to the affectation of her rescue.&lt;br /&gt;
[[Image:Ranger Patch.png|thumb|right|300px|The duty patch of the Starfleet Rangers]]&lt;br /&gt;
Along with [[Eian O&#039;Neill]], his father [[Liam O&#039;Neill]] of the [[USS Kelman]], [[Katherine &#039;Kitty&#039; Fisher]], and [[Chance Raschen]], Salid put together a rescue team in an attempt to affect her release and to capture or eliminate the [[Section 31]] operatives on the station.&lt;br /&gt;
&lt;br /&gt;
The location of the hostage was located in a phased portion of the starbase, and as soon as the location rejoined normal space, Salid and the others beamed in to rescue Signos.&lt;br /&gt;
&lt;br /&gt;
The operation was a success, capturing one Section 31 Operative,  and eliminating almost all of the others. Only [[George Hayden, Jr.|George Hayden]] the cells handler managed to escape the station.&lt;br /&gt;
&lt;br /&gt;
However, after having O&#039;Neill work up a psychological profile for Hayden, a plan was put into place to draw the cell handler back to [[Starbase Geneva]]. Putting himself into a position to illicit irritation and to appear smug at his victory over Hayden, Salid was able to draw the man back into the Starbase.&lt;br /&gt;
&lt;br /&gt;
Hayden however, was not sloppy. He had taken extreme measures to protect himself, and this time, he used a holodeck to mask his presence. He managed to kidnap Salid, and for a short while torture him until [[Eian O&#039;Neill]] managed to fix the Captain&#039;s location.&lt;br /&gt;
&lt;br /&gt;
An assault team [[transporter|beamed in]] to the area and captured Hayden. This operation proved to be a linch-pin for preventing any formal charges from SFI to be levied against Salid and his officers. It did unfortunately put them on Section 31&#039;s radar as potential threats, since they were now aware of their illicit existence.&lt;br /&gt;
&lt;br /&gt;
As a direct result of this operation, Salid, transferred, [[Mike Rosenbauer]] to act as his Yeoman, in an effort to provide himself with a bodyguard of some skill. It was a task for which the former [[Starfleet Rangers|Starfleet Ranger]] was well suited.&lt;br /&gt;
&lt;br /&gt;
==Mission Nineteen: [[The Third Law]]==&lt;br /&gt;
&lt;br /&gt;
While continuing on their mission to explore [[Sector 6309]], the crew of the  Rosenante discovered a rogue planet, which they later discovered was named [[Solyon]]. &lt;br /&gt;
&lt;br /&gt;
Excited about the possible history-making discovery, Captain Salid ordered three teams down to conduct scientific, geological and biological exploration of the unusual planetary body.&lt;br /&gt;
&lt;br /&gt;
While the away teams were on the planet&#039;s surface, Salid ordered the Stellar cartography department to attempt to project Solyon&#039;s course as well as extrapolate it&#039;s path of travel prior to discovery.&lt;br /&gt;
&lt;br /&gt;
Within hours, it was determined that the [[Rogue Planet]] would be passing through a [[Binary stars|binary star system]] which contained an inhabited planet, known as [[Asrai Prime]]. With the planet&#039;s inhabitants, the [[Asrai]], only at a pre-industrial level of technology, a bit of a moral issue arose. Technically, if the Asrai were unaware of other species or if they had not developed any technology akin to warp drive, then they would, under the auspices of the [[Prime Directive]] be left to their extinction.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
{| class=&amp;quot;toc color&amp;quot; style=&amp;quot;border:3px solid goldenrod;&amp;quot;align=&amp;quot;center&amp;quot;;&amp;quot;width=246px&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:black&amp;quot; align=&amp;quot;left&amp;quot; |&amp;lt;font color=goldenrod&amp;gt; &amp;lt;small&amp;gt;{{quote|As the right of each sentient being to live in accordance with its normal cultural evolution is considered sacred, no Starfleet personnel may interfere with the normal and healthy development of alien life and culture. Such interference includes introducing superior knowledge, strength, or technology to a world whose society is incapable of handling such advantages wisely. Starfleet personnel may not violate this Prime Directive, even to save their lives and/or their ships, unless they are acting to right an earlier violation or an accidental contamination of said culture. This directive takes precedence over any and all other considerations, and carries with it the highest moral obligation. |The Prime Directive}}&amp;lt;/small&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To further complicate things somewhat, the survey teams returned to the ship with evidence that Solyon had at one point been [[terraforming|terraformed]]. This caused Captain salid to order two separate missions to be undertaken. The first would travel to Asrai Prime to see if there was any evidence that would make the Asrai exempt to the conditions of the Prime Directive. The second would remain on the rogue planet in an attempt to find a means to deviate or destroy the rogue world if a means could not be found to alter it&#039;s course.&lt;br /&gt;
&lt;br /&gt;
Due to the gravity of the situation, Captain Salid led the away team to Asrai Prime while [[T&#039;Larah Sullivan]] led the mission on the rogue planet.&lt;br /&gt;
&lt;br /&gt;
On Asrai Prime the mission began to develop in a turbulent and difficult atmosphere. The inhabitants communicated as much with body postures and gestures as they did with words. because of this, the Universal translator couldn&#039;t assist them with this type of communication.&lt;br /&gt;
&lt;br /&gt;
[[File:Asrai Prime.jpg|thumb|left|500px|Asrai Prime]]&lt;br /&gt;
&lt;br /&gt;
A misunderstanding saw Salid and Fraiser imprisoned, but in so doing, it allowed the remaining members of the away team to uncover a group of outcasts that seemed to possess advanced technology. The situation quickly became clear. The leadership of the planet had created an enforced reversion in technology while maintaining their own technological advantage to make them the rulers of the world.&lt;br /&gt;
&lt;br /&gt;
This was complicated when the Survey teams from the rosenante on the Rogue planets discovered that the planet was actually an ancient colony ship that had narrowly escaped the destruction of their home world. They were headed for Asrai Prime, the last remaining colony of their ancient civilization. &lt;br /&gt;
&lt;br /&gt;
However the massive ship was badly damaged and required extensive repairs to allow it to adjust it&#039;s mass and avoid disrupting the delicate balance of Asrai Prime.  With the engineering teams working hard on that problem, Salid and Fraiser faced execution.&lt;br /&gt;
&lt;br /&gt;
However, with the discovery of the outcasts and the situation clearly no longer constrained by the Prime Directive, [[Ben Soma]] led a rescue operation and they successfully rescued Fraiser and Salid.&lt;br /&gt;
&lt;br /&gt;
meanwhile Salid and Fraiser had learned of an ancient planetary defense weapon once designed to destroy possible asteroid strikes, that was being prepared to destroy the Rogue Planet. As it was now apparent that the leader of the Asrai was aware that Solyon was actually a colony ship, and with the new information given to Salid, it was decided to prevent the destruction of the colony ship.&lt;br /&gt;
&lt;br /&gt;
In a last-ditch effort, Salid and his away team prevented the destruction of the colony ship and helped re-establish the technological society that had been stripped from the Asrai. the Diplomatic Corps opened an embassy on Asrai prime to help the new Asrai leadership re-integrate the long-neglected masses of the planet, in effect preventing the extinction of the Asrai people.&lt;br /&gt;
&lt;br /&gt;
==Mission Twenty: [[The Captain&#039;s Cotillion]]==&lt;br /&gt;
[[File:Salid-cotillion.jpg|thumb|right|500px|Captain Salid at the Cotillion, serving drinks.]]&lt;br /&gt;
&lt;br /&gt;
After the completion of the mission to save [[Asrai Prime]] the crew of the [[USS Rosenante]] moved into a support role for the new government of that planet. With the institutionalization of a new ruling system headed by the more technologically advanced Asrai from [[Solyon]], Ahmed was determined to insure  a series of programs that would help bring the remainder of the population into line with the new leaders of that planet.&lt;br /&gt;
&lt;br /&gt;
To that end, each of the departments began a program of assisting in building a knowledge infrastructure that the planet could then develop and expand on a planetary basis. To this end, medical databases, civil engineering databases and diplomatic databases have been supplied to the new government.&lt;br /&gt;
&lt;br /&gt;
With the civilization most recently believed to be under the protection of the [[Prime Directive]], which was disproven with the realization that [[Solyon]] was a warp capable colony ship, the [[Federation Diplomatic Corps]] was ordered by [[Starfleet Command]] to send special teams to aid the [[Asrai]] in their modernization efforts. &lt;br /&gt;
&lt;br /&gt;
To celebrate the new relationship and the mutual support between the [[UFP]] and the government of [[Asrai Prime]], [[Rank|Captain]] [[Ahmed Ibn Salid|Salid]] decided to implement a new tradition aboard the Rosenante in the form of a formal dance, which he dubbed the &amp;quot;Captain&#039;s Cotillion&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The affair was punctuated by the appearance of many of the ship&#039;s crew appearing in elaborate outfits, and taking a night on the town. The event filled Cargo Bays one and Two, which had been retrofitted by [[Rank|Commander]] [[Steven Wade Matrix|Matrix]], [[Rank|Lieutenant]] [[Ben Soma|Soma]], [[Rank|Lieutenant]] [[Thomas Jackson|Jackson]] and [[Rank|Lieutenant]] [[Sanok]].&lt;br /&gt;
&lt;br /&gt;
The prevent for the women of the crew took place on the holodeck, where [[Jessica Signos]] invited them all to a Japanese Bath house program for a day of pampering, gossip and spa treatments.&lt;br /&gt;
&lt;br /&gt;
Not all was well, however, as on the eve of the event, Signos and [[Eian O&#039;Neill|O&#039;Neill]] broke off their relationship due to &amp;quot;Lily&amp;quot;. A further incident took place when [[Tayla Fraiser]] inadvertently made telepathic contact with Signos, and was affected by &amp;quot;Lily&#039;s&amp;quot; presence, sending her into a panic attack that later caused her to attack [[Parker Davis]].&lt;br /&gt;
&lt;br /&gt;
This period of time saw the addition of a couple of new crew to the roster as well. [[Rank|Lieutenant]] [[Lanista]] , formerly from the [[USS Mithrandir]] and on return from a 5-year mission in [[Klingon]] space, was assigned to the [[USS Rosenante]] as their newest Chief Science Officer. Lieutenant [[Viskhard]], as a result of this new addition was reassigned to the position of Assistant Chief Science Officer. Another addition to the crew was [[Rank|Lieutenant]] [[Nayeli]], a member of the [[Starfleet Judge Advocate General Corps (JAG)|JAG Corps]]. Her purpose was to look into the possible violations of the [[Prime Directive]] on [[Asrai Prime]]. She was assigned as a standing member of the crew in reflection to Starfleet&#039;s concern over the matter. As a result, Captain Salid has no choice but to keep her aboard.&lt;br /&gt;
&lt;br /&gt;
The crew not only gained  new crew, but sadly have seen some transferred off the ship as well. [[Rank|Commander]] [[T&#039;Larah Sullivan]] was reassigned to the [[Starfleet Marine Corps]], where she assumed the rank of [[Rank|Lieutenant Colonel]]. She was joined by Lieutenant Masters. This left the position of First officer open, and [[Rank|Captain]] [[Ahmed Ibn Salid]] saw no reason not to promote his new Second and Third Officers into empty positions. As such, [[Rank|Lieutenant]] [[Ben Soma]] was promoted to First Officer and advanced in rank to [[Rank|Lieutenant Commander]], while [[Sanok]] was promoted to Second Officer. At this time Salid has not yet selected a third officer for the Rosenante.&lt;br /&gt;
&lt;br /&gt;
Not to be outdone, several members of the Rosenante&#039;s senior staff had their photograph taken for nostalgia&#039;s sake.&lt;br /&gt;
&lt;br /&gt;
==Mission Twenty-one: [[The Veil of the Sky]]==&lt;br /&gt;
[[File:Comet2.jpg|thumb|right|400px|Comet Holladay]]&lt;br /&gt;
&lt;br /&gt;
After [[The Captain&#039;s Cotillion]], the [[USS Rosenante]] was once again underway to continue her survey of [[Sector 6309]] as she had been ordered.  During this time, the crew encountered an unusual [[comets|comet]], which later became known as [[Comet Holladay]] in honor of the scientist who detected it by long-range scans.  Detailed scans and trajectory studies were underway, when an urgent message from [[Starfleet Command]] was received.&lt;br /&gt;
&lt;br /&gt;
A hostage situation had developed on the planet [[Beta Aquillia IV]] a world that supplied the [[Federation]] with a vast majority of the resources needed to rebuild their infrastructure and starships. the planetary government, led by President Kolath had been overthrown by a sudden and unexpected coup. The group responsible was a pro-isolationist group named [[Veil of the Sky]].&lt;br /&gt;
&lt;br /&gt;
During this coup, their leader, [[Habrii]] took Federation [[Ambassador]] [[Joanne Turner]] and her embassy staff hostage. The Rosenante was dispatched to negotiate her release and if possible to determine if there was outside support for the Veil.&lt;br /&gt;
&lt;br /&gt;
Upon their arrival, Salid attempted to make contact with the current government. He was at first ignored. determined to safe-guard refugees displaced by the conflict, especially those with Federation citizenship, Salid sent his crew down to the capital city of Joba to establish a safe-zone and a refugee camp to tend to the needs of the displaced.&lt;br /&gt;
&lt;br /&gt;
To make things more complicated a [[Skorr]] [[Worldripper Class]] warship named the [[Skysplitter]] arrived. it seemed that a Skorr Ambassador was also taken hostage and [[Ambassador]] [[Dralar]] had been sent to recover him. This made the situation potentially unstable.&lt;br /&gt;
&lt;br /&gt;
After the arrival of the Skorr vessel, [[Ben Soma]] led a negotiation team down to the planet with no real success. The political views of the Veil leadership made diplomacy all but impossible. However, the [[Aquillian]] ambassador, Tzorn began to make indications that he would aid the Rosenante crew in locating their ambassador in return for asylum.&lt;br /&gt;
&lt;br /&gt;
[[Chance Raschen]] and [[Mike Rosenbauer]] were assigned to covertly attempt to locate the ambassador on the planet. Mike managed to persuade a Veil member named [[Sien]] to join the Federation&#039;s cause, while chance uncovered some signs of [[Cardassian]] Involvement.&lt;br /&gt;
[[File:Atlantis Station.jpg|thumb|300px|left|Atlantis Station]]&lt;br /&gt;
&lt;br /&gt;
A series of suicide bombings at the refugee camp forced a breakdown in communication between the Veil and the Federation.  Refugee support operations became disaster relief. At Salid&#039;s request [[Dralar]] sent Skorr troops to shore up the Federation position.&lt;br /&gt;
&lt;br /&gt;
Meanwhile on [[Atlantis Station]], [[Niambh McNulty]] allowed the Rosenante&#039;s crew to establish a [[Command Control and Communications Center]]. From there the crew could more easily communicate and organize disaster relief.&lt;br /&gt;
&lt;br /&gt;
As the investigation continued, [[Steven Wade Matrix|Matrix]] and Peter Cohen discovered signs of Romulan involvement. The situation was quickly becoming murky, and it was even more unclear who was truly involved in supporting the Veil.&lt;br /&gt;
&lt;br /&gt;
When word went out that [[Alaya]] the lieutenant of the [[Veil of the Sky]] was responsible for the suicide attacks on the refugee camp, [[Habrii]] ordered her arrested. She was captured, but her escape was secured by Gul [[Matan]] of the [[Obsidian Order]]. Alaya then led a counter-coup against Habrii, capturing him and seizing control of the government.&lt;br /&gt;
&lt;br /&gt;
Meanwhile through subterfuge, the location of [[Ambassador]] Turner and the [[Skorr]] Ambassador became known. The Skorr rescued their Ambassador with the aid of [[Katherine &#039;Kitty&#039; Fisher]], while [[Jessica Signos]] led the rescue of the [[Federation]] Ambassador.&lt;br /&gt;
&lt;br /&gt;
[[File:Camp explosion.jpg|right|thumb|300px|One of the explosions at the refugee camps]]&lt;br /&gt;
&lt;br /&gt;
At the same time, [[Ben Soma]] led a team to extract the [[Aquillian]] Ambassador Tzorn as agreed. With all these actions underway, Salid was also on guard for any [[Cardassian]] or [[Romulan]] interference.&lt;br /&gt;
&lt;br /&gt;
Instead, however, he was forced to deal with the [[Veil of the Sky]] militia troops. [[Alaya]] had ordered them to assault [[Atlantis Station]] as well as the refugee camp protected by the Federation.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Salid utilized the ship&#039;s [[phaser]]s et to heavy stun to slow down the infantry assault against the camp. in addition, he used low-yield photon torpedoes to capsize the boats bombarding Atlantis Station.&lt;br /&gt;
&lt;br /&gt;
Once the refugees were evacuated, Salid recalled his crew. As his orders were to not get directly involved in the political struggle for control of the planet, the Rosenante then departed. But not before McNulty destroyed Atlantis station and the president in Exile Kolath, disappeared into the urban underground to establish a revolutionary movement to regain control of the government of Beta Aquillia IV.&lt;br /&gt;
&lt;br /&gt;
For the crew of the Rosenante, it was a bittersweet victory.&lt;br /&gt;
&lt;br /&gt;
==Mission Twenty-two: [[A Port in the Storm]]==&lt;br /&gt;
&amp;lt;strong&amp;gt;&amp;lt;font color=goldenrod&amp;gt;COMING SOON!&amp;lt;/font&amp;gt;&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Awards and Commendations: ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
image:Cross_of_Fire.gif|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded Cross of Fire: For actions above and beyond the call of duty during the battle for the MDP on stardate 2407.07.09&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
image:Combat_Action_Ribbon.gif|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded Combat Action Ribbon: For services rendered in freeing Cait Prime for the Occupation of Doentiz forces and it&#039;s illegal and immoral experiments.&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
image:Captain&#039;s_Commendation.jpg|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded Captains Commendation: For actions during and after the battle for the MDP, stardate 2407.07.09&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
image:Captain&#039;s_Commendation.jpg|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded Captains Commendation: Awarded on behalf of the Cartenian Commonwealth for Services rendered in the Rescue of Prince Khamal from the Orion Syndicate on Stardate 2408.03.15&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Image:Order_of_Unity-_Ribbon.jpg|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded The Order of Unity: Awarded in commemoration of services rendered during the Federation Civil War.&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
image:Rib19.gif|&amp;lt;small&amp;gt;Awarded Squadron Commander&#039;s Commendation: Awarded on Stardate 2414.02.14 for actions above and beyond the call of duty, critical to the success of the Mission to destroy the T&#039;Kon Sphere held by the Borg.&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
File:Rib05.gif|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded Medal of Distinction: Awarded Stardate 2414.02.16, for gallantry in the line of duty against forces hostile to the United Federation of Planets.&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Rosenante Crew Roster}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Characters]][[Category:History]][[Category:Civil War]][[Category: Mirror Universe]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Retired_staff&amp;diff=55871</id>
		<title>Retired staff</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Retired_staff&amp;diff=55871"/>
		<updated>2012-09-05T16:17:33Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* Mission Six: Picking up the Pieces. */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;toc colour&amp;quot; style=&amp;quot;margin: 0 0 1em 1em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:goldenrod&amp;quot; align=&amp;quot;center&amp;quot; |&amp;lt;font color=maroon&amp;gt;&#039;&#039;&#039;Ahmed Ibn Salid&#039;&#039;&#039;&amp;lt;br&amp;gt;&amp;lt;font color=maroon&amp;gt;Commanding Officer, USS Rosenante&amp;lt;/font&amp;gt;&amp;lt;br&amp;gt;[[File:IbnSalid.jpg|center|300px|Captain Ahmed Ibn Salid]]&amp;lt;br&amp;gt;&amp;lt;/font&amp;gt;[[File:Rosenante-Alt-2up.jpg|center|300px|USS Rosenante]]&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Vital Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Age: 38&lt;br /&gt;
**Gender: Male&lt;br /&gt;
**Birthplace: [[Cairo]], [[Egypt]], [[Earth]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Physical Information&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Eye Color: Brown&lt;br /&gt;
**Hair Color: Black&lt;br /&gt;
**Height: 5.5 feet&lt;br /&gt;
**Weight: 170 lbs&lt;br /&gt;
**Skin Color: Olive&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Career Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Rank: [[Rank|Captain]]&lt;br /&gt;
** Current Assignment: [[USS Rosenante]]&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Prior Assignments:&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
**Stardates: 2408.01.04 - 2408.01.06&lt;br /&gt;
**[[ Starbase Valhalla]] - [[Engineering|Engineering Operations Officer]]&lt;br /&gt;
**Stardates: 2407.07.09 - 2408.01.04&lt;br /&gt;
**[[USS Hypatia]] - [[First Officer]]&lt;br /&gt;
**Stardates: 2407.04.02 - 2407.07.09&lt;br /&gt;
**[[USS Champlain]] - [[First Officer]]&lt;br /&gt;
**Stardates: 2406.01.04 - 2407.01.22&lt;br /&gt;
**[[USS Nimitz]] - [[Engineering|ACEO, CEO]]&lt;br /&gt;
**Stardates: 2402.03.12 - 2406.01.04&lt;br /&gt;
**[[Starfleet Academy]] - [[Rank|Cadet]]&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;toc color&amp;quot; style=&amp;quot;border:3px solid goldenrod;&amp;quot;align=&amp;quot;center&amp;quot;;&amp;quot;width=246px&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:black&amp;quot; align=&amp;quot;center&amp;quot; |&amp;lt;font color=goldenrod&amp;gt;&amp;lt;small&amp;gt; {{quote|Being hugged by Commander Zzt isn’t that bad really...after you lose consciousness.|Ensign Junior Grade Ahmed Ibn Salid}}&amp;lt;/small&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==Childhood==&lt;br /&gt;
&lt;br /&gt;
Ahmed was born in [[Cairo]], [[Egypt]]- [[Earth]] on Stardate 2382.04.10 to Salid ibn Jaffar and Jasmine Mosatuff. At the time of his birth his father was an engineering ensign aboard the USS Roland and his mother was an artist.&lt;br /&gt;
&lt;br /&gt;
Ahmed lived in Cairo for the vast majority of his life, although he did spend a few years aboard the [[USS Roland]] and the [[USS Archimedes]] with his mother and father.&lt;br /&gt;
&lt;br /&gt;
At the age of five years, Ahmed’s parent’s divorced after Ahmed’s mother Jasmine was discovered to be having an affair, with the USS Archimedes’ Chief Counselor. Ahmed’s father, unable to raise the boy alone and without a desire to release him to his mother’s custody,sent young Ahmed back to Cairo to live with his Uncle Aamihr. Before leaving the Forrester, Ahmed’s mother gave him a necklace to remember her by. He still wears it to this day.&lt;br /&gt;
&lt;br /&gt;
Ahmed had a difficult time adjusting to his new life with his Uncle. When he reached his teens, Ahmed became rebellious and would often disobey his uncle’s wishes. In the interest of finding something to occupy his nephew’s time in a more productive manner, Ahmed’s uncle introduced the boy to [[Sailing]] and [[Boxing]].&lt;br /&gt;
&lt;br /&gt;
There were remarked improvements in Ahmed’s grades as a result of these new interests. It was discovered that he possessed a photographic memory and that he had become bored with his studies, since he could memorize the course curriculum within a few hours. Boxing and Sailing gave him physical challenges as well as mental ones, and he began to work in his uncle’s business, teaching tourists how to sail traditional Egyptian boats on the Mediterranean sea. Ahmed would often participate in unsanctioned boxing clubs in his teens.&lt;br /&gt;
&lt;br /&gt;
It was during this time that Ahmed began to take an intense interest in History. His uncle had revealed Ahmed’s rich family Lineage to the boy at the age of 17. The men in Ahmed’s family have dedicated their lives in the pursuit of Moral Justice. Ahmed began a detailed Genealogy of his male ancestors and was able to trace back his lineage to a general serving in [[Saladin|Saladin&#039;s]] army during the battles of the Crusades. He commissioned an incredible Genealogy scroll of his ancestors that is 4 feet wide and 9 feet tall. It is current displayed on the wall of his quarters aboard the [[USS Rosenante]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
On Stardate 2398.08.12 Ahmed was involved in a near fatal accident. While exploring a recently discovered Egyptian tomb in the [[Valley of the Kings]] with Doctor Sufi Mohammed Sari, a renowned Egyptologist, There was a collapse of a tunnel.&lt;br /&gt;
&lt;br /&gt;
Ahmed was badly injured. He suffered serious trauma in the form of broken bones. It took rescuers thirteen hours to free him from the rubble. As a result of these traumatic times, Ahmed suffers from a mild case of claustrophobia, although he is usually able to fight back the sense of panic that he feels.&lt;br /&gt;
&amp;lt;center&amp;gt;&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
image:Jasmine_Mosatuff_1.jpg|Jasmine Mosatuff in Syria&lt;br /&gt;
image:Salid_Ibn_Jaffar_2.jpg|Salid Ibn Jaffar&lt;br /&gt;
image:Uncle_Aamihr.jpg|Uncle Aamihr&lt;br /&gt;
&amp;lt;/Gallery&amp;gt;&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==University of Cairo==&lt;br /&gt;
&lt;br /&gt;
Ahmed enrolled in the University of Cairo on Stardate 2399.03.06 in the fields of Archeology, Ancient Medicine, and Ancient Engineering. He greatly enjoyed this area of study, but at the insistence of his professors and in messages received from his father, then the Chief Engineer aboard the [[USS Tripoli]], Ahmed finally agreed to take the [[Starfleet]] entry exams.&lt;br /&gt;
&lt;br /&gt;
He graduated with a Masters degree in Archeology from the [[University of Cairo]] on Stardate 2403.03.05.&lt;br /&gt;
&lt;br /&gt;
==Relationships of Note==&lt;br /&gt;
&lt;br /&gt;
[[image:debbie.jpg|thumb|left|&#039;&#039;&#039;Crewman Debbie Weston&#039;&#039;&#039;]][[image:Jasmin_Mohandas_1.jpg|thumb|right| &#039;&#039;&#039;Jasmin Mohandas&#039;&#039;&#039;]]&lt;br /&gt;
&lt;br /&gt;
Salid was involved in a romantic relationship with Engineer Debbie Weston while he was stationed aboard the [[USS Nimitz]] as [[Engineering|Chief Engineer]]. The relationship began to grow somewhat cool after Ahmed&#039;s participation in the Raid on [[Djorn Major XJ-003]]. &lt;br /&gt;
&lt;br /&gt;
The relationship broke up when Ahmed was promoted and assigned to the [[USS Champlain]] as [[First Officer]]. Weston and Ahmed are still friends and are on speaking terms. Ahmed visited the [[USS Hades]] after the end of the Civil War where he spoke once again with Debbie Weston. Debbie was interested in rekindling their relationship, but Ahmed resisted. His concern over maintaining a long distance relationship and his newly acquired interest in [[Jasmin Mohandas]] won out and Ahmed and Debbie agreed to end the romantic aspect of their on-again, off-again relationship.&lt;br /&gt;
&lt;br /&gt;
After the end of the [[Federation Civil War]], Ahmed returned to [[Cairo]] to visit his uncle. He was attacked by an angry mob in the city, as a result of his choice to wear his [[Starfleet]] uniform. He was beaten and struck with stones and lost consciousness. When he recovered he found himself in the home of Jasmin Mohandas. Jasmin had tended his injuries after rescuing him from the mob using a black market [[phaser]]. &lt;br /&gt;
&lt;br /&gt;
During the subsequent discussion, Ahmed discovered that she had been a [[Rank|Lieutenant]] assigned as [[Medical Officer|ACMO]] to the [[USS Pangaea]]. This vessel was a part of the [[Admiral Doenitz|Doenitz]] loyalist force that fought against the [[52nd Fleet]] at the Battle of [[Sector 001]]. Heated words were exchanged and Ahmed was asked to leave.&lt;br /&gt;
[[image:Jasmin_Mohandas_2.jpg|thumb|left| &#039;&#039;&#039;Jasmin Mohandas&#039;&#039;&#039;]]&lt;br /&gt;
&lt;br /&gt;
Several days later, Ahmed saw Jasmin in the local marketplace and apologized. He offered to make her dinner, which she accepted. The meal was terribly cooked, but Ahmed and Jasmin spoke more candidly afterwards and it was then that Ahmed learned that Jasmin was to go before a tribunal for her actions during the battle. After discussing the situation with her, he became convinced that she had done nothing to warrant a Court Martial.&lt;br /&gt;
&lt;br /&gt;
Ahmed spoke to Jasmin&#039;s JAG Officer for the defense and convinced him to allow Salid to speak as a character witness on Jasmin&#039;s behalf. After a hard-sell the counselor agreed and Ahmed was allowed to speak at the Tribunal. He gave an impassioned speech about &#039;&#039;&#039;&#039;&#039;&amp;quot;mercy&amp;quot;&#039;&#039;&#039;&#039;&#039; and &#039;&#039;&#039;&#039;&#039;&amp;quot;healing the wounds of the Federation&amp;quot;&#039;&#039;&#039;&#039;&#039;. It seemed to work, Jasmin was only reduced a single grade as a result of a guilty result of Medical Negligence, while she was found not guilty of the six charges of Murder brought against her.&lt;br /&gt;
&lt;br /&gt;
For several months, while the [[USS Hypatia]] was in Sector 001, Ahmed spent a great deal of time with Yasmin and his uncle Aamihr in Cairo. A young budding romance began between the two and despite the difficulties of a long-distance relationship, is still working.&lt;br /&gt;
&lt;br /&gt;
==[[Starfleet Academy]]==&lt;br /&gt;
&lt;br /&gt;
[[image:Stacademy.jpg|thumb|right|&#039;&#039;&#039;[[Starfleet Academy]], San Francisco, Earth&#039;&#039;&#039;]]&lt;br /&gt;
&lt;br /&gt;
Ahmed took his entry exams on Stardate 2403.06.05, just in time to manage to squeeze into the summer class. Ahmed scored the tenth highest entry exam scores in the history of the [[Starfleet Academy|Academy]], a fact for which he is extremely proud.&lt;br /&gt;
&lt;br /&gt;
He double majored at the Academy in the areas of Materials Engineering/Damage Control and Trauma Medicine. &lt;br /&gt;
&lt;br /&gt;
During his time at the academy, Ahmed joined the [[Boxing|Academy Boxing Team]], [[Sailing|Regatta]] and [[rowing]] teams. He took the Lightweight title for three of the four years that he competed at the Academy. As the captain of the Rowing team, led his crew to victory two years in a row. The Academy Regatta on [[Arctura II]] proved to be another victory for the [[Rank|Cadet]] Salid, as his crew and he took the cup in a ship named the [[Jasmine]].&lt;br /&gt;
&lt;br /&gt;
On stardate 2406.08.02 Ahmed participated in the famed [[Starfleet]] [[Academy Marathon]] on [[Danula II]]. This grueling race saw Ahmed finish 221st out of 693 competitors. While not a clear-cut victory, he was pleased that he managed to finish the 40-kilometer race.&lt;br /&gt;
&lt;br /&gt;
Prior to completing his Course studies at the Academy, Ahmed also took and completed his Bridge Certification Training, Command Staff Training and his Departmental Command Courses. The scored well in each of these additional course, a fact that would assist him later in being selected for the position of [[First Officer]] of the [[USS Champlain]].&lt;br /&gt;
&lt;br /&gt;
Ahmed graduated the Academy Class of 2407 on Stardate 2407.01.22. He ranked second in his class. It was on his graduation day that news arrived of his father’s death aboard the [[USS Tripoli]]. He had sacrificed himself to maintain the containment of the collapsing warp core during the battle of [[Cardassia]].&lt;br /&gt;
&lt;br /&gt;
==Starfleet Career==&lt;br /&gt;
&lt;br /&gt;
[[image:Nimitz.jpg|400px|thumb|right|The USS Nimitz]]&lt;br /&gt;
&lt;br /&gt;
Ahmed was commissioned as an Ensign Junior Grade pursuant to his graduation from Starfleet Academy on Stardate 2407.01.22.&lt;br /&gt;
&lt;br /&gt;
Ahmed was ordered to report to the [[USS Nimitz]], a [[Sovereign Class]] [[Starship]] (Registry NCC-75878-E) captained by Captain [[Devan Sash]].&lt;br /&gt;
&lt;br /&gt;
Ahmed was forced to take a circuitous route to reach the Nimitz due to the Civil War between the Doenitz Loyalists and the [[52nd Fleet]], the latter to which the Nimitz belonged. During his trip he witnessed the oppression of [[Andoria]] first-hand.&lt;br /&gt;
&lt;br /&gt;
He commissioned a respected smuggler and 52nd Fleet loyalist named [[Arkot]], an ex-captain of the Doenitz defeated [[Andorian]] Defense fleet. During his time aboard the Smuggler, he worked in main engineering and repaired an old Romulan cloaking device that was later used to elude a Doenitz loyal Starship.&lt;br /&gt;
&lt;br /&gt;
Ahmed arrived on Starbase [[Geneva]] on Stardate 2407.02.09 nearly a full month after his graduation from the Academy in San Francisco. Once aboard [[Starbase Geneva]] Ahmed wasted no time reporting to the Nimitz.&lt;br /&gt;
&lt;br /&gt;
==Mission One: A Taste of Hate.==&lt;br /&gt;
&lt;br /&gt;
After his arrival on Starbase [[Geneva]], Ahmed was assigned to assist in the investigation concerting an attack on the newly assigned Counselor [[Divon Lronen]]. During the course of the investigation, Ahmed was responsible for finding the weapon used in the assault on the counselor. He was reassigned to the Engineering Department to conduct repairs to the Nimitz as a result of a prior battle.&lt;br /&gt;
&lt;br /&gt;
He reported to Main Engineering and watched in Horror as the current ACEO Lieutenant Miles Davis collapsed after contracting the engineered [[Revelation Virus]] released on Geneva Station by the Terrorist Group [[Humans for Humanity]].&lt;br /&gt;
&lt;br /&gt;
Lieutenant Davis was the first member of the Nimitz crew to succumb to the virus and later died as a result of the illness.&lt;br /&gt;
&lt;br /&gt;
Once it became known what was happening, [[Starbase Geneva]] and the [[USS Nimitz]] were quarantined to prevent further spreading of the virus. The result of the lock-down left Ahmed, newly arrived on the Nimitz as the senior Engineering Officer on the Nimitz, due to Commander Zzt becoming unable to leave the Starbase.&lt;br /&gt;
&lt;br /&gt;
After Hromava, the Nimitz’s First Officer ordered all non-essential personnel to be restricted to quarters, Ahmed and Debbie Weston continued with the repairs to the Nimitz.&lt;br /&gt;
&lt;br /&gt;
Later due to the fact that the virus had been introduced to the crew of the Nimitz, special quarantine areas were established in the ship’s cargo bay, on the orders of the First Officer. It was at this time that Salid discovered an attempt by desperate members of the ship’s crew to escape from the Cargo bay and potentially seize control of the Nimitz. &lt;br /&gt;
&lt;br /&gt;
Ahmed participated in the actions to prevent a mutiny aboard ship.&lt;br /&gt;
&lt;br /&gt;
For his efforts, Captain [[Devan Sash]] promoted him to Ensign Senior grade on Stardate 2407.02.17.&lt;br /&gt;
&lt;br /&gt;
After his promotion Ahmed began a romantic relationship with Engineer Debbie Weston.&lt;br /&gt;
&lt;br /&gt;
==Mission Two: [[Djorn Major Incident|For a Friend]].==&lt;br /&gt;
&lt;br /&gt;
[[Image:VoyagerWarpCore.jpg|thumb|300px|right|Promoted to Chief Engineer]]&lt;br /&gt;
&lt;br /&gt;
On Stardate 2407.03.07 Ahmed was promoted to the position of CEO for the [[USS Nimitz]] by Captain [[Devan Sash]] after it was discovered that Lieutenant Commander Zzt was to be transferred to a Special Theoretical Engineering Unit.&lt;br /&gt;
&lt;br /&gt;
Later that same day, Ahmed would join Captain Sash and several other Nimitz Officers on an unsanctioned mission to Rescue Lieutenant Dru Tagon, a fellow Nimitzer. Tagon had been captured by Doenitz forces and sentenced to be executed. It was discovered that he was being held at [[Djorn Major XJ-003]] to await the completion of his sentence. As the [[52nd Fleet]] was stretched over a wide front in the battle against Deonitz forces, the Admiralty had decided that no vessels could be risked on the rescue. Despite orders to the contrary, Captain sash and several officers made  a rendezvous with the [[IKS Hegh’delar]] a [[Bird-of-Prey|B’rel Class]] scout and entered federation space with the intention of conducting a rescue of Dru Tagon.&lt;br /&gt;
&lt;br /&gt;
Prior to the Arrival at Djorn Major XJ-003, Ahmed spent a considerable amount of effort and time designing material aids to assist in the assault and hopefully give his small team a slight advantage against the station’s garrison. These gadgets included an armored cloaking armored EVA suit, modified from the available Klingon EVA suits, attuned to the IKS Hegh’delar’s [[Cloaking device]]; A series of portable sensor ghost generators, and a mobile handheld command net inderdiction device which later allowed the crew limited access to the station’s main computer systems. Unfortunately despite successful tests of the stealth suits aboard the Hegh’delar, the stealth features seemed to mysteriously fail once aboard the station.&lt;br /&gt;
&lt;br /&gt;
[[image:Horizon.jpg|thumb|300px|left|Djorn Major XJ-003]]&lt;br /&gt;
&lt;br /&gt;
Upon their arrival at Djorn Major XJ-003, The 1st assault team used the [[Ferengi]] assault shuttle the [[Good Deal]] to pass through a gap in the Station’s ventral shields and after An EVA mission to establish a series of transport pattern enhancers, the Crew was aboard the Station.&lt;br /&gt;
&lt;br /&gt;
Ahmed participated in the capture of the Central Computer core of the station in which action he killed a technician.  Later in an attempt to disable the stations shields and weapons, he created a powerful [[plasma]] surge through the tactical systems. The end result was the unexpected explosion of the Station’s Ventral Shield Generator, which was responsible for extensive damage to the station and an unknown number of deaths among station personnel.&lt;br /&gt;
&lt;br /&gt;
Ahmed was injured twice during the mission. Once, he was hit with a [[phaser]] blast in the back fired by station security, which forced him to discard the upper portion of his armored EVA suit. Later he was injured in hand-to-hand combat with a member of Major Julian Wells’ marine unit assigned to guard Lieutenant Tagon. The marine stabbed Ahmed in the lower left arm.&lt;br /&gt;
&lt;br /&gt;
The arrival of the Klingon assault forces from the Hegh’delar led by Doctor [[Jonas Lemar]] allowed the Nimitz crew to reach the Maximum Security Block and force Wells into an honorable ceasefire.&lt;br /&gt;
&lt;br /&gt;
Ahmed and [[Thomas Jackson]] worked together to drop the containment field holding Dru Tagon in his cell. Ahmed also managed to neutralize the explosive collar Tagon wore using the station’s [[transporter]] safety overrides. At Captain [[Devan Sash]]’s order Ahmed transported the assault team to safety, but not before [[Agent Thom Hania|Thom Hania]] had released an explosive grenade which is believed to have killed Major Julian Wells.&lt;br /&gt;
&lt;br /&gt;
The crew escaped Djorn Major and returned to [[Starbase Geneva]] with Lieutenant Tagon. Remarkably, only two members of the rescue effort were killed in action, both were members of the Hegh’delar’s Klingon Marine Contingent led by Doctor Lemar. Later Ensign Thom Hania died under mysterious circumstances prior to the return to the Nimitz. Ensign [[Harry Samuel Doorman]] had survived an apparent attempt at suicide, although later it was discovered that his actions were influenced by the [[Revelation Entity]] affecting Counselor [[Divon Lronen]]. &lt;br /&gt;
&lt;br /&gt;
Surprisingly enough, no member of the Nimitz crew was punished for the undertaking of the unsanctioned rescue of Lieutenant Tagon, Except for Captain Sash.&lt;br /&gt;
&lt;br /&gt;
For his efforts in the rescue of Lieutenant Tagon, Ahmed was promoted to the rank of Lieutenant Junior Grade on Stardate 2407.03.22&lt;br /&gt;
&lt;br /&gt;
==Mission Three: [[To Skin a Cat]].==&lt;br /&gt;
&lt;br /&gt;
On Stardate 2407.03.22 the Nimitz received orders from the Admiralty to conduct a snap raid on [[Cait|Cait Prime (Ferasa)]] with the objective of verifying the existence and destroying a Doenitz research facility believed to be developing biogenetically altered Caitians for use as Super-Soldiers. &lt;br /&gt;
&lt;br /&gt;
The [[USS Nimitz]] arrived in the Ferasa system and was surprised not to find any Doenitz Starships in orbit around the planet.&lt;br /&gt;
&lt;br /&gt;
The away team consisted of the following participants&lt;br /&gt;
[[Rank|Captain]] [[Devan Sash]]&lt;br /&gt;
CTAC [[Eric McDermott]]&lt;br /&gt;
AOPS [[Thomas Jackson]]&lt;br /&gt;
Engineer [[T&#039;Kron]]&lt;br /&gt;
Ensign Leesa Stanton&lt;br /&gt;
COUNS [[Cecilia Bruce]]&lt;br /&gt;
&lt;br /&gt;
As well as several junior members of the security, Science and Engineering departments of the Nimitz.&lt;br /&gt;
&lt;br /&gt;
Upon Arrival on the planet, The Nimitz team Linked up with members of the CLF (Caitian Liberation Front) led by an adolescent Caitian named R&#039;Aul. They also made contact with R&#039;Serrott and [[Shayhiloosh]], both of which were involved in some manner with the facility that the Nimitz crew was sent to destroy.&lt;br /&gt;
&lt;br /&gt;
[[image:Nilas III.jpg|thumb|500px|right|The USS Nimitz at Cait Prime (Ferasa)]]&lt;br /&gt;
&lt;br /&gt;
The crew spent the night with their new found allies in the Caitian Village of [[Chtarr]], where Ahmed participated in a complex and semi-violent game of [[Sarhket]], which is used in some rural areas to resolve disagreements. The game turned out to be a test of the Nimitz crew&#039;s resolve to aid the [[Caitian]]s in their struggle for liberation. Although Salid did not win, he earned the respect of the local CLF members and was accepted among them as a friend.&lt;br /&gt;
&lt;br /&gt;
The following morning the away team, bolstered by their new additions in R&#039;Serrott and Shayhiloosh and accompanied by A&#039;Rul and members of the CLF, marched to and raided an automated train depot that would allow them covert entry to the Capital City of [[Knassis]], only 30 miles away. The raid on the train depot went smoothly without incident.&lt;br /&gt;
&lt;br /&gt;
Once the train depot had been secured, The Nimitz away team hid themselves aboard the supply train and rode the conveyance to their target area. The train was stopped by members of the Local Militia when it was discovered that a trap had been set for the Nimitz team. As a result, The team was instead forced to hike into the target area undetected and assault the underground complex where [[Admiral Doenitz|Doenitz loyalists]] were conducting illegal biogenetic and telepahic manipulation.&lt;br /&gt;
&lt;br /&gt;
Once inside, the team split into two assault groups; one  led by [[Rank|Lieutenant]] Salid and the other by Captain Sash. &lt;br /&gt;
&lt;br /&gt;
The team led by Sash seized the facilities [[transporter]]s and assaulted the telepathic research facilities, While the second team under Lieutenant Salid assaulted the genetics labs and holding cells. Ahmed&#039;s group met light resistance and was able, with the help of Lieutenant Prothal, to destroy the research facilities beyond repair.&lt;br /&gt;
&lt;br /&gt;
Meanwhile, Captain Sash&#039;s team came under attack by facility security and were pinned down in a terrible crossfire. Salid&#039;s team arrived in time to relieve the captain&#039;s team and the two teams then led the assault against the primary telepathic holding facility.&lt;br /&gt;
&lt;br /&gt;
During the assault on that facility, The away team came under psychic attack, that caused some of their number to turn on their allies.  Salid and several other officers managed to fight their way out of the control of the being designated, Patient [[Delta-Seven-Nine|Delta-Seven-Nine (Δ79)]]. Δ79 killed his controller and then died of injuries inflicted upon him by the combined telepathic attacks of [[Cecilia Bruce]] and [[Eric McDermott]].&lt;br /&gt;
&lt;br /&gt;
Once the telepathic research facilities were neutralized, Sash led the remainder of his team and the rescued test subjects from the facility to the city above. &lt;br /&gt;
&lt;br /&gt;
When the word spread that there were Caitains in revolt, the entire [[planet]] rose up and threw off the yoke of the Doenitz Regime.&lt;br /&gt;
&lt;br /&gt;
For his efforts, Ahmed was awarded the Combat Action Ribbon. He was promoted to [[Rank|Lieutenant Commander]] on Stardate 2407.03.29, when it was also announced that he had been selected as [[First Officer]] of the [[USS Champlain]].&lt;br /&gt;
&lt;br /&gt;
== Mission Four: Crossroads ==&lt;br /&gt;
&lt;br /&gt;
[[Image:USSChamplainD.jpg|450px|thumb|right|USS Champlain]]&lt;br /&gt;
After the completion of the mission on Cait Prime, Ahmed was promoted to the Rank of Lieutenant Commander and assigned to the [[USS Champlain]], NCC 2170-C, A [[Galaxy Class]] variant. He reported to [[Starbase Geneva|Geneva Station]] to Captain [[Susan Rivers]], who had also just assumed command of the Champlain after the death of her Captain Edward Wolfe in a battle with the [[USS Wyvern]]. He assumed this position officially on Stardate 2407.04.02, despite the fact that the Champlain had not yet arrived at the Station as she was damaged during the battle. The Champlain was Commanded by [[Rank|Lieutenant]] Bree Frazier during the engagement with the [[USS Wyvern]], which resulted in the enemy vessel&#039;s capture thanks in no small part to the efforts of Lieutenant James Alexander and Lieutenant Jono Janeway.&lt;br /&gt;
&lt;br /&gt;
Captain Rivers advised Lieutenant Commander Salid of the impending assignment of the Champlain to participate in the final push of the [[Federation Civil War]] against [[Admiral Doenitz]] in an amassed attack on [[Sector 001]]. He was assigned to arrange drills and additional training for the crew while the ship remained in dock undergoing repairs.&lt;br /&gt;
&lt;br /&gt;
==Mission Five: [[Do Not Go Gently]]==&lt;br /&gt;
[[Image:Task Force 19 -2.jpg|thumb|300px|right| Task Force 19, of the 52nd Fleet, assembling in preparation to attack Sector 001]]&lt;br /&gt;
&lt;br /&gt;
On stardate 2407.06.25 Ahmed was advised by Captain Susan Rivers that they had finally received their orders to join the remainder of [[Task Force 19]] assembling at [[Tellar]]. The Champlain had been completely overhauled and the ship and her crew were as ready as they could possibly be for the final battle against Doenitz forces guarding sector 001&lt;br /&gt;
&lt;br /&gt;
On Stardate: 2407.07.03 Ahmed and the entire Command Staff of the USS Champlain were briefed on the plans to Attack Sector 001 and [[Earth]] in a final bid to bring an end to the bloody and tenacious Federation Civil War. This [[Task Force Nineteen Briefing|Briefing]] was conducted by Rear Admiral Sevant, Former captain of the [[USS Boudicca]] and the Task Force Commander of [[Task Force 19]], ordered to breach the famous [[Mars Defense Perimeter]] designed to hold of a [[Borg]] Invasion.&lt;br /&gt;
&lt;br /&gt;
Even as the crew of the Champlain begin gearing for the coming battle, Hundreds of [[Starship|ships]] were converging at Tellar in preparation for the massive offensive.&lt;br /&gt;
&lt;br /&gt;
The assignment given to the Champlain was simple in concept but exceptionally complex in practice. The task force was broken into four smaller battle groups and the remaining bulk of the taskforce, consisting of the [[USS Boudicca]] (commanding group B), the [[USS Champlain]] (commanding group C), the [[USS Nimitz]] (commanding Group A), The [[USS Hades]] (commanding group D). The Boudicca was tasked to breach the MDF and assault and capture [[Starbase Valhalla]] in an attempt to shut down the MDF and allow the remainder of Task Force 19 to bypass the MDF without further losses. The USS Champlain, Hades, and Nimitz were ordered to support the operation of the Boudicca, with the Champlain being specifically tasked with screening the Boudicca and her Battlegroup from enemy raiders.&lt;br /&gt;
&lt;br /&gt;
The basic flow of the battle is listed here:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;toc colour&amp;quot; style=&amp;quot;margin: 0 0 1em 1em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;Stardate: 2407.07.05&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1410 HRS&amp;lt;/font&amp;gt;: The order to &amp;quot;Cross the River Acheron&amp;quot; is given by Admiral Sevant, the [[Commanding Officer]] of Task Force 19. Lead elements of the taskforce begin their journey to [[sector 001]] and the final engagement of the civil war.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1414 HRS: Captain Rivers Orders the USS Champlain and Battle Group C to set course for Sector 001.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1415 HRS&amp;lt;/font&amp;gt;:  Battlegroup Theta commanded by  Captain Sarah Smithers orders her specialized assault group underway.&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;Stardate: 2407.07.09&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1328 HRS&amp;lt;/font&amp;gt;: The [[USS Champlain]] and her accompanying battlegroup drop out of warp and steam towards the MDF. Battle Group A consisting of 20 ships, 4 of which are [[Klingon]] [[Negh&#039;Var Class]] vessels, break formation and begin assaulting the MDF at long range. &lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1400 HRS&amp;lt;/font&amp;gt;: The enemy sends out skirmishing vessels to harass battlegroup A with mixed results.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1407 HRS&amp;lt;/font&amp;gt;: The [[USS Boudicca]] begins her run towards the MDF&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1410 HRS&amp;lt;/font&amp;gt;: Battlegroup Laredo (D) attacks the USS Champlain and her associated Battle Group. The raiders uncloak, fire a volley of modified torpedoes into the flank of the C-Group then make a strafing run. Both sides take casualties. The C-Group falls back from B-Group to protect the latter&#039;s flanks from attack.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1415 HRS&amp;lt;/font&amp;gt;: The [[USS Hades]] and [[USS Nimitz]] reach [[Sector 001]]. The Hades goes into Tri-Vector Assault mode.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1417 HRS&amp;lt;/font&amp;gt;: Group Theta arrives at Sector 001 and begins their assault on a weapons repository located just inside the MDF.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1418 HRS&amp;lt;/font&amp;gt;: Battle Group D engage enemy fighters and their support ships.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1425 HRS&amp;lt;/font&amp;gt;: Battle group Laredo makes a second attack run against C-Group then retreats from the battlefield behind the protection of the MDF&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1449 HRS&amp;lt;/font&amp;gt;: The USS Boudicca and her Battlegroup make contact with the MDF.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1455 HRS&amp;lt;/font&amp;gt;: The [[USS Spectre]] arrives in sector 001 with a [[Klingon]] Task force and a group of Ex-Doenitz ships that have defected to the [[52nd Fleet]].&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1750 HRS&amp;lt;/font&amp;gt;: The USS Boudicca and her battle group finally break through the MDF.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1755 HRS&amp;lt;/font&amp;gt;: The USS Champlain and the remnants of Battle Group C breach the MDF while being pursued by the [[USS Majesty]] and her Battle group (D)&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1800 HRS&amp;lt;/font&amp;gt;: Captain Rivers orders Battle group C to form a battle line behind  Battlegroup B to guard the Boudicca&#039;s rear flank. The C-Group turns about 180-degrees and forms a battle line to handle the Majesty and her battle group.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1815 HRS&amp;lt;/font&amp;gt;: The USS Majesty and her battlegroup form a wedge formation to better split through the battle line established by Captain Susan Rivers and the remnants of Battlegroup-C.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1820 HRS&amp;lt;/font&amp;gt;: The two battle groups led by the USS Majesty and the USS Champlain clash. The battle formations are broken and the battle devolves into complete chaos for the two battle groups.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1822 HRS&amp;lt;/font&amp;gt;: After taking fire from Negh&#039;Vars of Battlegroup-A, [[Uru Mtenga]] orders the [[USS Hercules]] and the [[USS Persephone]] to split off from the rest of his battlegroup and deal with the Klingon ships. They destroy all three remaining Ngh&#039;Vars and return to the battle with the Champlain.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1825 HRS&amp;lt;/font&amp;gt;: The [[USS Dennison]] and a small battle group arrive at Sector 001 to aid Task Force 19.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1830 HRS&amp;lt;/font&amp;gt;: The USS Boudicca realizes that they are facing the Black Watch led by Admiral Lydia Stakes as well as elements of the 53rd Heavy Assault Fleet. Captain Archibald Stakes appeals to the morality of the enemy battle group and the majority of the Night watch and the 53rd Heavy defect or stand aside. Those resisting are engaged and subdued by the remainder of Battlegroup-B.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1900 HRS&amp;lt;/font&amp;gt;: The USS Nimitz is destroyed in battle when she rams an enemy ship during a warp core breach. Several members of her crew managed to abandon ship just prior to her destruction.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1907 HRS&amp;lt;/font&amp;gt;: The battle between the Majesty and Champlain Battle groups has depleted both sides resources significantly. The [[USS Hypatia]] from the Black Watch joins the battle. Her captain convinces Captain M&#039;tega that they are still loyal to [[Admiral Doenitz]], then ambushes their former ally. The Majesty is crippled, giving the heavily damaged Champlain a short respite.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1910 HRS&amp;lt;/font&amp;gt;: The [[USS Dennison]] joins the [[USS Hades]] as a defensive screening force while the Hades reintegrates from Tri-Vector mode and begins rescue operations of the surviving Nimitz Crew.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1911 HRS&amp;lt;/font&amp;gt;: The Champlain engages the enemy [[Prometheus Class]] starship, [[USS Persephone]]. The Champlain loses her dorsal nacelle and an unstoppable warp core breach begins. Once Rivers realizes the ship is lost, she orders the abandon ship. The Persephone begins firing on the life boats from the Champlain.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1920 HRS&amp;lt;/font&amp;gt;: The USS Boudicca, press their shields against those of [[Starbase Valhalla]]. This action causes severe damage to the [[Keltoi Class]] ship, but causes the Stations dorsal shields to fail. Stakes orders the abandon ship and the crew of the Boudicca use transporters or life pods to get aboard Valhalla following the Marine assault ships.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1922 HRS&amp;lt;/font&amp;gt;: Several senior officers &amp;quot;volunteer&amp;quot; to stay aboard while the Champlain is guided towards her enemy like a massive missile. &lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1930 HRS&amp;lt;/font&amp;gt;: In an attempt to give their comrades time to get clear of the Persephone&#039;s violent onslaught, the [[USS Wyvern]] draws the larger vessel away from the dying Champlain. The Wyvern is knocked out of commission and all her crew killed.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1949 HRS&amp;lt;/font&amp;gt;: The USS Champlain manned only by a handful of volunteers use the [[Galaxy Class]] vessel to ram the [[USS Persephone]]. Both ships are completely destroyed. The skeleton crew on the Champlain is rescued by the [[USS Hypatia]].&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;2055 HRS&amp;lt;/font&amp;gt;: The rest of [[Task Force 19]] is ordered to go &amp;quot;To Earth!&amp;quot; The offensive for the planet itself begins in earnest. [[Starbase Valhalla]] is secured by the [[52nd Fleet]].&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;Stardate: 2407.07.09&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;0127 HRS&amp;lt;/font&amp;gt;: The [[USS Dennison]] and her support ships destroy the [[USS Caesar Regnum]]&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;0130 HRS&amp;lt;/font&amp;gt;: Reports surface that ex-president and dictator Rodrigo Doenitz is captured by Resistance forces in Geneva Switzerland.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;0205 HRS&amp;lt;/font&amp;gt;: The former president of the [[United Federation of Planets]] is restored and the Civil War and the Battle for [[sector 001|Sector 001]] is finally ended.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Mission Six: [[Picking up the Pieces]].==&lt;br /&gt;
&lt;br /&gt;
[[Image:Homecoming.jpg|thumb|450px|right|The USS Rosenante NCC-924650]]&lt;br /&gt;
With the civil war over and the Champlain lost, Ahmed was assigned as Acting [[First Officer]] of the [[USS Hypatia]] under the command of Acting Captain [[Susan Rivers]].&lt;br /&gt;
&lt;br /&gt;
The Hypatia underwent repairs and participated in some limited recovery work inside the [[Sol|Sol System]].&lt;br /&gt;
&lt;br /&gt;
Salid visited his uncle in [[Cairo]], where he met [[Jasmin Mohandas]]. An ex-ACMO from the [[USS Pangaea]] (a Doenitz ship from the 1st Fleet) when she saved him from a mob that attacked him because he was wearing his [[Starfleet]] uniform. Ahmed discovered that his uncle had been interred and had suffered torture at the hand of Doenitz fundamentalists as a result of his nephew&#039;s involvement with the Sedition.&lt;br /&gt;
&lt;br /&gt;
Ahmed spoke at a tribunal hearing for Lieutenant Mohandas, urging the tribunal to exercise mercy. Miss Mohandas was found innocent of all charges of murder during the battle, but was found guilty of Medical Negligence. She lost one grade in rank as a result.&lt;br /&gt;
&lt;br /&gt;
Ahmed reconciled with his uncle after the two men had an argument about his potential resignation from Starfleet to attend to his uncle&#039;s health needs. &lt;br /&gt;
&lt;br /&gt;
Salid visited his ex-shipmates from the Nimitz who had been reassigned to the [[USS Hades]]. There he and Debbie Weston spoke about the future of their past relationship and about the loss of the [[USS Nimitz]].&lt;br /&gt;
&lt;br /&gt;
After a crushing declaration by Commander Josel, Chief of Personnel for [[Sector 001]] that Ahmed was not qualified to serve in the capacity of First Officer; he was assigned to the Engineering operations Officers aboard [[Starbase Valhalla]] on Stardate 2408.01.04. This assignment did not last for long, however. Captain Susan Rivers acting on the authority of [[Rank|Admiral]] Linden, ordered Ahmed reassigned to the [[USS Rosenante]], as her First officer.&lt;br /&gt;
&lt;br /&gt;
Ahmed and Captain Rivers beamed aboard the Rosenante on stardate 2408.01.06 to assume command from the Acting CO Commander Ian MacBeth.&lt;br /&gt;
&lt;br /&gt;
== Mission Seven: [[A Fine and Private Place]]==&lt;br /&gt;
[[Image:Extrasolar-Binary.jpg|thumb|250px|right|Davros III]]&lt;br /&gt;
&lt;br /&gt;
The [[USS Rosenante]] passed her space worthiness trials without a glitch and was assigned their very first mission, to survey planets for recolonization of the survivors of the [[Colony]] of [[Ivor Prime]]. The Rosenante took on the administrator of the colony and set off for the [[Optima VII|Optima System]] in hopes of finding a planet suitable for the colonists. The Rosenante departed for her official maiden Voyage on Stardate 2408.01.15. The Ceremony was officiated by [[Rank|Admiral]] Hesper Linden.&lt;br /&gt;
&lt;br /&gt;
On Stardate 2408.01.21  the Rosenante received a disturbing [[Sky of Tomorrow Distress Call|distress signal]] from the Federation freighter the &#039;&#039;&#039;[[Sky of Tomorrow]].&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Third Officer, Olen Rhinehardt altered course and alerted the captain and crew to the situation. The Sky of Tomorrow&#039;s signal was traced to the orbit of [[Davros III]], A [[Federation]] Mining [[Colony]].&lt;br /&gt;
&lt;br /&gt;
The Rosenante arrived at the scene only three hours later. Attempts to hail the freighter were not successful. An away team was beamed aboard and to their horror uncovered signs of a violent and bloody conflict. They also encountered an animated dismembered hand. This hand was quarantined and studied upon the return of the away team to the Rosenante, where it was discovered that the hand was infested with a nanite colony derived from [[Borg]] [[nanoprobe]]s.&lt;br /&gt;
&lt;br /&gt;
Ahmed led an away team down to the planet&#039;s surface to search for survivors, when he returned to the Rosenante without three of his security team, Ahmed offered this summary to the Captain:&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;sup&amp;gt;&amp;lt;font color=goldenrod&amp;gt;&lt;br /&gt;
:&#039;&#039;Ahmed followed the Captain into the ready room.  As always the Captain was incredibly calm, ~But then again,~ Ahmed reminded himself, ~she hadn&#039;t just been chased by an indeterminable number of corpses animated by Borg nanites… Or something like that~&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Sit down, Ahmed,&amp;quot; she said, and headed for the replicator. Without asking, she ordered two cups of Ahmed&#039;s special Turkish coffee and a plate of pastries. She sat them down on the table between them and said. &amp;quot;You can talk as you eat,&amp;quot; she ordered, sliding the plate a little closer to him. &amp;quot;I can tell by your face it&#039;s not good news, so let&#039;s hear it. What did you find down there?&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;It&#039;s hard to be clear, so bear with me.&amp;quot; Ahmed said as he added a little goat&#039;s milk to his coffee and took a sip. &amp;quot;When we arrived in the town square, everything was quiet. It was just like one of those wild west ghost towns that you read about in the history books.  All it was missing was the tumble weed.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;We located the residence of doctor Lawson and there we found what appeared to the remains of a lab. It was very obvious that some of the equipment had been moved elsewhere. From that lab there were two almost parallel tunnels leading downward toward the mine. As you know that was when I ordered Lieutenant Janeway, chief fuller and a second security team down to the planet. The idea was that the two teams could each explore one of the tunnels and possibly locate any survivors or clues faster.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;He picked up one of the pastries and took a bite. The orange marmalade was exceptionally good and Ahmed then realized how hungry he really was. He took a sip of his coffee to wash it down.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;We searched for several hours without any sign at all of the miners. For a while there, I was even beginning to wonder if all 1500 of them had somehow managed to leave the planet. We came to a junction and heard what I could only describe as weapons fire. I ordered the team down the tunnel to the source as quickly as possible which opened into a cavern.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;When we arrived, there was an… individual there, a member of the Opthidian species, who was defending himself from some of the miners. It was apparent that he had killed at least ten or twelve of them already. We announced ourselves and ordered the fighting to stop, but instead of being attacked by the visitor as I had originally expected to be, it was the miner&#039;s that attacked us.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Heavy stun doesn&#039;t have much affect on them. Even the kill setting isn&#039;t very effective.  We lost Abernathy in that fight. He was infected by some sort of black ooze, which we were later informed was a nanite colony.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;The Opthidian&#039;s name is Sharott Nachook and he explained a great deal to us concerning what was happening on that colony.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;Ahmed ate some more of his pastry and drank a little more of his coffee. &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;His people encountered the Borg roughly 500 standard years ago. Apparently their physiology doesn&#039;t allow them to be assimilated by Borg Technology. They fought a war and in the end the [[Borg]] left them alone. The Opthidian scientists had dissected several Borg drones during the war and had discovered a way to modify the Borg nanoprobes for their own medical uses. This continued for some time until eventually, the Borg nanoprobes developed some sort of colony-like hive mind and became self-aware. They began to dominate living members of the Opthidian species against their will and when the realization struck, the Opthidian government tried to destroy the nanites.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;The nanites adapted again in a very grotesque manner. They began killing their hosts and maintaining the bodies after death until they were no longer viable. The [[Opthidian]] homeworld had to be biologically sterilized to prevent them from spreading. From what I can gather eventually the Opthidians captured the original colony which they refer to as the matriarch and imprisoned it pending it&#039;s destruction.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Now here&#039;s where the details get a bit sketchy.&amp;quot; Ahmed said then took another sip of his coffee. &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;At some point in the recent past, the Ferengi somehow managed to steal this imprisoned nanite colony and transport it here, where it is believed they sold it to Doctor Lawson. The good doctor is an expert on Borg nanotechnology and was living here with her young daughter, who was very ill with an incurable ailment according to Doctor Caskie&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;We can surmise that Lawson conducted some experiments, maybe even infecting her daughter either with the knowledge that these nanites were self-aware or in ignorance. Regardless of what she knew, that seems the most logical means that this infection was spread. From there, the nanites took over members of the community exponentially until every member was a member of the colony.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Mister Nachook&#039;s people tracked the Ferengi here. They claim to have destroyed the Ferengi ship and admit to attacking Mister Raschen&#039;s ship in an attempt to maintain some semblance of quarantine. It seems that after their losses in the battle, they withdrew, possibly to conduct repairs when we arrived in the system.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;They had dropped Nachook and perhaps a couple of others on the planet with the mission to find and destroy the nanite breeding pool, where apparently the matriarch lives. Mister Nachook claims that destroying her will result in the demise of all her immediate offspring as they are dependant on her for their cognitive abilities.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Just shortly after all this data was given by Nachook, Jono shows up with what is left of Beta team. He was injured and we gathered that they were surrounded and attacked by a large mass of infected miners. They lost Milano during their escape.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Nachook advised Caskie at that time that  he carries some sort of viral weapon in his body that will wipe out the entire biosphere of the planet and make it uninhabitable for roughly 200 standard years. He is confident that the weapon will kill all the nanites present by depriving them of biological hosts and will kill anyone that should set foot there as well and prevent the nanites from managing to get off world.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;Ahmed finished his coffee and sat it on the table. &amp;quot;The catch is that Nachook was injured and some sort of biological process has started that will result in his death and the release of the virus in an uncertain amount of time. Doctor Caskie is confident that she can extract the virus, saving Nachook and that the virus can them be delivered to the planet via modified Photon torpedo, where it will destroy the biosphere and end the threat of it spreading from this planet.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;We had to fight our way out of those tunnels. We lost Hezan there. I vaporized him myself.&amp;quot; &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;Ahmed looked into River&#039;s eyes, before continuing. &amp;quot;I&#039;ve seen a lot of terrible things Captain, but I can not describe to you the sheer terror and fear that these things inspire. I am not a blood thirsty person, but these things need to be eradicated with all due prejudice.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;That said it was my assessment, after my experience on the planet, that these nanites should be treated like a biological outbreak and should be eradicated before they place millions or even billions more at risk. I have ordered Caskie to proceed with her plan after she assured me that she could prevent it from spreading across the ship should there be a mishap. I believe that we have no recourse and that we should treat these nanites as we would Borg. There is no hope of negotiation and that any encounter will result in the supplantation of one species over the other at the complete eradication of the prior.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;To carry through with this, I furthermore, recommend that we transport the nanite-filled hand back to the Sky of Tomorrow and that we undertake steps to destroy it and the freighter as well.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/font&amp;gt;&amp;lt;/sup&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Captain Rivers agreed with Salid&#039;s assessment and ordered the plan carried out. At 2045 hours the orders were given to deploy the viral torpedo and the planet of [[Davros III]] was sterilized. The freighter was destroyed shortly thereafter and Mister Nachook was returned to his ship. &lt;br /&gt;
&lt;br /&gt;
The Rosenante seeded five quarantine probes around the planet before departing to complete their original mission.&lt;br /&gt;
&lt;br /&gt;
On Stardate: 2408.01.25 Captain Rivers was ordered to Starbase Geneva to give evidence for a war crimes tribunal. She was advised that she would not be returning to the command of the Rosenante and Commander Salid was promoted to the rank of Captain and given command of the USS Rosenante.&lt;br /&gt;
&lt;br /&gt;
== Mission Eight: [[Letters of Marques]]==&lt;br /&gt;
&lt;br /&gt;
After the transfer of captain Rivers to the Boudicca, Ahmed is promoted to captain of the Rosenante. &lt;br /&gt;
[[Image:APPLANET.jpg|thumb|250px|right|Arturia Prime]]&lt;br /&gt;
&lt;br /&gt;
It turns out that his first test as captain will place his ship and crew well outside the boundaries of Federation Space.&lt;br /&gt;
&lt;br /&gt;
The Mission began with a communication from Admiral Talbot of Starfleet intelligence.&lt;br /&gt;
&lt;br /&gt;
Prince [[Angor Khamal|Khamal]], the hereditary leader of the Meldovian people had been kidnapped on the eave of a peace treaty that would bring an end to a 400 year old war between the Meldovian and Arturian factions (both of the [[Cartenian]] race).&lt;br /&gt;
&lt;br /&gt;
While traveling to [[Arturia Prime]] from [[Meldovia III]] to conclude the peace treaty, Orion pirates and slavers attacked the Prince&#039;s convoy and took the Prince and many other Meldovians prisoner.&lt;br /&gt;
&lt;br /&gt;
At the request of the [[Vulcan]] Arbiter T&#039;Val, Admiral Talbot assigned the [[USS Rosenante]] to the task of locating and recovering the Prince before the peace negotiations fail.&lt;br /&gt;
&lt;br /&gt;
Salid was ordered to rendezvous with the Arbiter and take on an Arturian, Meldovian and the Vulcan delegations. He is then ordered to proceed into [[Orion]] space and locate and rescue the Prince.&lt;br /&gt;
&lt;br /&gt;
Using their untried cloaking system, the HISS system, the Rosenante slipped into Orion Space to begin their investigation at the heart of the [[Orion Syndicate]]&#039;s notorious slave markets on [[Barakos IV]].&lt;br /&gt;
&lt;br /&gt;
Three away teams are sent to the surface to procure supplies, search for clues to the Prince and gather intelligence.&lt;br /&gt;
&lt;br /&gt;
One of the away teams is tasked with the acquisition of a Orion style shuttle craft to be used in future phases of the mission. This team consisting of the first officer, Janeway, Lt. Dralar, and the CEO Lt. Paul Bird succeed in their mission, but not before Lt. Bird is killed in a senseless brawl by an individual using a poisoned blade.&lt;br /&gt;
&lt;br /&gt;
Bird is transported back to the ship, but the poison works quickly and he is not able to be revived.&lt;br /&gt;
&lt;br /&gt;
The second away team, consisting of Lt. Ro&#039;Dal, Ensign Weaver, PFC Nunez and Lt. Caskie, and Ensign T&#039;Kron search for Meldovians among the slave pens of the market. they are successful in rescuing three Meldovians and a Half-Orion/Half-[[Betazoid]] woman named Sodra, who claims to have information concerning the whereabouts of the prince.&lt;br /&gt;
&lt;br /&gt;
Sodra turns out to have no information at all, instead using her telepathic powers to pluck a few relative pieces of information from Weaver. However, she has done no harm and is restricted to quarters until such time as her disposition can be determined.&lt;br /&gt;
&lt;br /&gt;
Ro&#039;Dal and Caskie do recover three Meldovians with the aid of a new ally, Nodel, who is an amthropoid, a species not yet discovered by the UFP. Their new ally leads them directly to the last three Meldovian slaves in the marketplace.&lt;br /&gt;
&lt;br /&gt;
[[Image:Slave Market on Barakos IV.jpg|thumb|250px|right|The Slave Market on Barakos IV]]&lt;br /&gt;
&lt;br /&gt;
The third away team, consisting of Lt. Sullivan, Ensign [[Chance Raschen]], and Chief Sheridan make contact with Raschen&#039;s grandfather, a reputed Bounty hunter by the name of &amp;quot;Easy Ed&amp;quot; Raschen. They get a solid lead on whom may have the prince, an slaver named O&#039;Banyan at [[Xanadu Gothos]].&lt;br /&gt;
&lt;br /&gt;
Once all three teams have returned to the ship, the senior staff question those that were brought aboard at [[Barakos IV]].&lt;br /&gt;
&lt;br /&gt;
It rapidly becomes apparent that there was a spy within the Prince&#039;s circle of advisors, and that information, coupled with the discovery of an encrypted message into Orion space originating from the Rosenante, led to speculation that there was now an enemy spy aboard the Rosenante as well.&lt;br /&gt;
&lt;br /&gt;
Maddox and Weaver were given the task to decrypt the message in the hopes of discovering it&#039;s origins.&lt;br /&gt;
&lt;br /&gt;
With information acquired from Nodel it is determined that there was a Meldovian of some importance shipped to [[Haldor II]]. While it is unknown if this is the Prince, it is worth investigating and so the Captain orders course set and the Rosenante underway to the Haldor system.&lt;br /&gt;
&lt;br /&gt;
[[Image:Morella.jpg|thumb|left|[[Morella]] Pirate Queen]]&lt;br /&gt;
&lt;br /&gt;
En route, the Holographic marine Program, Ramirez, suddenly activates and attempts to assassinate the Captain and several other key members of the ship&#039;s senior staff.&lt;br /&gt;
&lt;br /&gt;
Chaos ensues as the crew struggle to regain control of the ship&#039;s computers and disable the hologram from operating. It quickly becomes apparent that the saboteur is responsible.&lt;br /&gt;
&lt;br /&gt;
Meanwhile Nodel confides in Ro&#039;Dal that he has heard the voice of a slaver on the ship. This voice he insists is the exact same voice that he heard near the Meldovian cells on [[Barakos IV]].&lt;br /&gt;
&lt;br /&gt;
Nodel and Ro&#039;Dal hatch a plan to potentially identify their would-be slaver and set the plan into action.&lt;br /&gt;
&lt;br /&gt;
With several of the ship&#039;s systems off-line, as a result of Ensign Weavers attempt to stop the holographic marine by disengaging the Cochrane Accelerator field in the main computer and then physically destroying the holographic buses with a hand phaser, the Rosenante takes refuge inside an asteroid belt to avoid detection while the stealth systems and other ship&#039;s critical systems are repaired.&lt;br /&gt;
&lt;br /&gt;
Once those repairs are completed, the ship continues on to [[Haldor II]], where their sensors detect the presence of a living facility protected by an environmental shield.&lt;br /&gt;
&lt;br /&gt;
With no ships in the immediate vicinity, Ahmed orders the ship into a geosynchronous orbit and tasks Lt. Sullivan, Ensign Weaver, lieutenant [[Steven Wade Matrix]] and Lieutenant [[Jennifer Caskie]] to accompany a security team to the surface with the intentions of rescuing the single Meldovian life-sign found on the planet.&lt;br /&gt;
&lt;br /&gt;
After recovering the Meldovian from the planet [[Haldor II]], it became quickly apparent that the individual that they had acquired was a traitorous captain who had been responsible for the ease of the Prince&#039;s kidnapping.&lt;br /&gt;
&lt;br /&gt;
Having no other choice the captain ordered the new prisoner interrogated and the Rosenante to set course for [[Torven III]]. The only other lead that they had to the possible whereabouts of the Prince&#039;s location.&lt;br /&gt;
&lt;br /&gt;
Once arriving in the Torven System, Salid opened negotiations with the trader [[Doyle &#039;Dogface&#039; O&#039;Banyan|Doyle O&#039;Banyan]], An [[Starfleet Marine Corps|ex-marine]] turned smuggler and slave trader. In return for a promise to aid in his rehabilitation, Salid agrees to accept O&#039;Banyan&#039;s assistance in recovering the prince. The Trader had already secretly sent an assault group against Morella in the hopes that they could acquire the Prince.&lt;br /&gt;
&lt;br /&gt;
Surprisingly, the assault works and the Prince as well as O&#039;Banyan&#039;s missing daughter is recovered, allowing the Rosenante to return back to [[Federation]] Space in time to guarantee the successful signing of the Peace between the Meldovian and Arturians and the formal formation of the Cartenian Commonwealth.&lt;br /&gt;
&lt;br /&gt;
Thier mission completed, the Rosenante heads to [[Starbase Geneva]] for some R&amp;amp;R and After action inspections.&lt;br /&gt;
&lt;br /&gt;
== Mission Nine: [[Furlough]]==&lt;br /&gt;
&lt;br /&gt;
The crew of the Rosenante is granted Furlough, while critical inspections concerning the Spiral drive are undertaken.  Captain Salid is forced to demote Lieutenant Janeway by BUPERS from the position of first officer and is assigned a newly promoted Lieutenant Commander Caskie to the position. &lt;br /&gt;
&lt;br /&gt;
The Rosenante also takes on some new senior Crew. Ahmed is reunited with [[Thomas Jackson]] with whom he served aboard the [[USS Nimitz]], in the position of Chief of Operations. Additionally the arrival of Lieutenant Nayati to fill the position of Chief Counselor and third Officer is a welcomed event.&lt;br /&gt;
&lt;br /&gt;
In other news, Salid is saddened by the transfer of Lieutenant Ro&#039;Dal who has been reassigned to the [[USS Mithrandir]].&lt;br /&gt;
&lt;br /&gt;
The Captain and his new FO go for a holographic sailing trip on the Mediterranean in a get to know you cruise, and Salid approves Sullivan&#039;s departure for the Advanced Tactical Theories Academy on [[Andoria]].&lt;br /&gt;
&lt;br /&gt;
== Mission Ten: [[Fields of Elysium]]==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Part I: The Mission&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
In Mid 2408 the [[USS Rosenante]] was assigned to explore a newly discovered region of space that exited from the Tau Sigma Flow of the Subspace River. This region had been discovered by an unmanned survey probe and opened into the [[Beltanis Stellar Nursery]].&lt;br /&gt;
&lt;br /&gt;
When the Rosenante arrived, the captain decided to move into the nebula in the hopes of exploring an undocumented phenomenon. This phenomenon turned out to be an exceptionally rare event known as a [[Subspace Bubble]]. Unfortunately, the bubble burst slamming the vessel with a Class Six [[Graviton|Gravimetric Wave]].&lt;br /&gt;
&lt;br /&gt;
The Rosenante was terribly damaged; suffering irreparable damage to the ship&#039;s Main Deflector Array and Power distribution network. With the ship&#039;s shields failing, the vessel hurriedly returned to the safe-zone at the terminus of the Subspace river.&lt;br /&gt;
&lt;br /&gt;
After a couple of days of assessment and around-the-clock repairs, it was determined that the Rosenante would not be able to return to Federation space via the [[Subspace River]], as they could not open the river terminus without the use of their [[Navigational Deflector]].&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Part II: The Distress Call&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Image:Nova_Class_4.jpg|thumb|175px|right|[[USS Epiphany]]]]&lt;br /&gt;
On their third day in the [[Beltanis Stellar Nursery|Nursery]] the Rosenante detected an automated federation Distress beacon. despite the fact that it was unlikely that any other federation starships were in the area, Captain Salid decided that the Rosenante should investigate.&lt;br /&gt;
&lt;br /&gt;
The beacons prefix identification was finally determined to belong to the the [[USS Epiphany]] a [[Nova Class]] starship registry NCC-913081, which had been declared lost with all hands on Stardate 2392.01.19 (17 years prior.)&lt;br /&gt;
&lt;br /&gt;
When the Rosenante responded, they discovered not the Epiphany, but [[The Harvester]].&lt;br /&gt;
&lt;br /&gt;
The Harvester then proceeded to lock the Rosenante in a Tractor beam like grasp, scan the vessel and transport the Rosenante into the area of the vessel known as the Bone Yard.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Part III: Inside the Harvester&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The arrival inside [[The Harvester]] was anything but accommodating. Upon their rematerialization, the Rosenante was immediately attacked by a group inhabiting the Harvester known as the [[Hur&#039;q]].  These insect-like creatures are those  once referred to in ancient Klingon History as an invader that once tried to conquer the Klingon home world of [[Qo&#039;noS]].&lt;br /&gt;
&lt;br /&gt;
The attack came in the form of a small group of raiders that took advantage of the newly arrived ship&#039;s lack of shields (disrupted by the transport into the Harvester). &lt;br /&gt;
&lt;br /&gt;
Several small groups of assault troops were beamed aboard the Rosenante and these groups managed to tag and steal several supplies from cargo bays as well as a few pieces of minor equipment before they were expelled from the ship. During the skirmish it was determined that the Hur&#039;q were immune to the heavier stun settings on Federation Phasers, and so the crew and security personnel were forced to use the higher level kill and disintegrate settings.&lt;br /&gt;
&lt;br /&gt;
The [[Engineering]] team managed to restore their ship&#039;s only moments after the Hur&#039;q retreated from the ship, although the invaders took all of their dead and it was  believed all of the Rosenante dead as well.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Part IV: The Anti-Hur&#039;q Alliance&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Image:Forest Clearing-Bastion-red.jpg|thumb|300px|right|The Bastion]]&lt;br /&gt;
&lt;br /&gt;
The Rosenante was contacted by the [[Nechani]] ship, [[NSS Oracle&#039;s Tears]] and a meeting was arranged aboard the Bastion.&lt;br /&gt;
&lt;br /&gt;
The Anti-Hur&#039;q Alliance was assembled and comprised of the leaders from the following Species as well as [[Ambassador]] [[Anna Morgan]]:&lt;br /&gt;
&lt;br /&gt;
:The [[Nechani]]&lt;br /&gt;
:The [[Sky Spirits]]&lt;br /&gt;
:The [[Kobali]]&lt;br /&gt;
:The [[Hunters]]&lt;br /&gt;
&lt;br /&gt;
The Rosenante Delegation was lead by [[rank|Commander]] [[Jennifer Caskie]] and was comprised of the following personnel.&lt;br /&gt;
&lt;br /&gt;
:[[Rank|Lieutenant]] [[T&#039;Larah Sullivan]]&lt;br /&gt;
:[[Rank|Lieutenant]] [[Chance Raschen]]&lt;br /&gt;
:[[Rank|Ensign]] [[V&#039;Shera]]&lt;br /&gt;
:[[Rank|Ensign]] [[Dorian Weaver]]&lt;br /&gt;
:[[Rank|Lieutenant]] [[Jon Nayati]]&lt;br /&gt;
:[[Rank|Lieutenant]] [[Thomas Jackson]]&lt;br /&gt;
&lt;br /&gt;
:As well as a few security personnel.&lt;br /&gt;
&lt;br /&gt;
Near the end of the negotiations the meeting was attacked by Hur&#039;q raiders who activated a Transport Inhibitor to trap the Leaders of the alliance in the Bastion. Only Ji&#039;yala had left prior to their arrival.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Part V: The Aftermath&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The aftermath of the battle on the bastion was substantial. The Rosenante Crew lost both Weaver and Sullivan who were killed by Hur&#039;q. Additionally Nayati was missing and  Raschen was critically injured. With such critical officers out of commission, killed or missing, the Rosenante crew are forced to adapt to fill their leadership positions. it later is learned that Nayati was &#039;saved&#039; by the Sky Spirit leader Chaska during the battle. &lt;br /&gt;
&lt;br /&gt;
It is also suspected that the Kobali may be responsible for the missing bodies of the dead crew.&lt;br /&gt;
&lt;br /&gt;
Unknown to the Rosenante crew, Sullivan&#039;s body has undergone the reclamation and is now a member of the Kobali race. &lt;br /&gt;
&lt;br /&gt;
Among those skilled in the battle among the non-Rosenante crew is the Sky Spirit Chief Nekawana and several hunters. Ambassador Morgan has been recovered by members of the Rosenante crew and is currently in sick bay.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Part VI: The Epiphany&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
A survey team lead by Lieutenant Marrow has beamed aboard the Epiphany to begin the survey of her systems in the hopes of reclaiming critical components and salvaging her Main Deflector. Over the course of the next month and a half the Engineering crew of the Rosenante, with assistance from their new alliance members, manage to salvage the Main deflector array and get it installed and operational aboard the USS Rosenante.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Part VII: The Alliance &amp;amp; Escape&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Escape Alliance is formed and all the various species within the Bone Yard of [[The Harvester]] are dedicated to working together to achieve escape. Lieutenant [[Alimi Morrow]] leads a mixed engineering team into the bowels of the Harvester with the goal of disabling the devices Transporters and Tractor beams. That mission is successful.&lt;br /&gt;
&lt;br /&gt;
Additionally the engineering teams work around the clock to modify the Rosenante&#039;s Spiral Warp drive to emit Phased particles.&lt;br /&gt;
&lt;br /&gt;
Using this drive and stabilizing the field with the newly restored navigational array, the Allies are able to escape the Harvester. The allies then parts ways on friendly terms.&lt;br /&gt;
&lt;br /&gt;
==Mission Ten: [[Homecoming]]==&lt;br /&gt;
&lt;br /&gt;
[[Image:Homecoming.jpg|thumb|250px|right|The Rosenante returns to Starbase Geneva]]&lt;br /&gt;
&lt;br /&gt;
After escaping from [[The Harvester]] the [[USS Rosenante]] returns to [[Geneva Station|Starbase Geneva]] for repairs and to give the crew some much needed downtime after their ordeal.&lt;br /&gt;
&lt;br /&gt;
During the three month refit, several members of the crew go on extended leave.  Among those is [[Rank|Lieutenant Commander]] [[Jennifer Caskie]] whose return to her Home in Scotland is under less than ideal circumstances. Her trip is one of necessity rather than desire. She is escorting home the body of her long dead husband Donald Caskie, who was a member of the [[USS Epiphany]] crew. Event though he had been decalred dead nearly two decades earlier, it was disovered that Donald was actually reclaimed by the [[Kobali]] aboard the Harvester. His second death too place during a failed attempt to restore himself to his former life after successfuly restoring [[Rank|Lieutenant]] [[T&#039;Larah Sullivan]] to her previous [[Vulcan]] / [[Human]] heritage after she was killed and reclaimed by the Kobali after a [[Hur&#039;q]] raid.&lt;br /&gt;
&lt;br /&gt;
Additionally, [[Chance Raschen]] and [[T&#039;Larah Sullivan]] are accompanied by Lietenant [[T&#039;Kron]] to [[Vulcan (planet)|Vulcan]] where they will participate in the ancient Vulcan ritual of [[Fal-tor-pan]]. raschen is the recipient of Sullivan&#039;s [[Katra]] after she transferred to him just prior to her death at the hand of a Hur&#039;q subcommander.&lt;br /&gt;
&lt;br /&gt;
Meanwhile back aboard the Rosenante, the ship puts on a masquarade party to help revieve some work related tensions. This party is hosted by Lieutenant [[Thomas Jackson]].  Councilor [[Jon Nayati]] ,the ship&#039;s third officer, attends as does Ensign [[Mitena Rixx]], Head nurse [[Katherine &#039;Kitty&#039; Fisher]] and Doctor [[Sam Lopez]].&lt;br /&gt;
&lt;br /&gt;
Elsewhere, Captain [[Ahmed Ibn Salid]] enjoys a nice relaxing leave on [[Bracas V]] where he enjoys some snorkling and sailing. His trip, however is cut short by a mysterious visit from a [[Dominion]] [[Vorta]] named [[Julman]] and an attending group of [[Jem&#039;Hadar]] soldiers. He isn&#039;t seriously injured although one of the Jem&#039;Hadar are less than pleasant. Other than the initial disagreement, the remainder of the meeting goes along well enough. Julman reveals a terrible peice of information to Salid.&lt;br /&gt;
&lt;br /&gt;
The content of that secret will drive him to consider taking the Rosenante off mission. Is hea leading his ship and crew into a possible Dominion trap or is there a possibility that the information that the Vorta revealed could be true. If it is true, the very future of the [[Alpha Quadrant]] may be at risk.&lt;br /&gt;
&lt;br /&gt;
A few days prior to the relaunch of the Rosenante, Sullivan is promoted to Lieutenant Commander, Raschen to Full Lieutenant and Caskie to Full Commander.&lt;br /&gt;
&lt;br /&gt;
==Mission Eleven: [[Into the Darkness, Go I]]==&lt;br /&gt;
[[Image:Battle Sunali II.jpg|thumb|right|250px|Battle of Sunali II]]&lt;br /&gt;
After his encounter with [[Julman]], [[Rank|Captain]] [[Ahmed Ibn Salid]] came to a critical decision to break his standing orders to partol the frontier between the [[Cardassian Union]] and the [[United Federation of Planets]].&lt;br /&gt;
&lt;br /&gt;
Instead he ordered the Rosenante off mission towards the [[Ikev Sector]] where indications of a conspiracy to build an [[Omega Device]] was suspected.&lt;br /&gt;
&lt;br /&gt;
En route, a distress signal from the [[Boronite]] mining facility on [[Bardon Alpha]] was intercepted. Ahmed ordered the [[USS Rosenante]] into action, but arrived too late to be of much assistance. By the time that they had arrived, the inhabitants of the facility had been slaughtered, leaving only two survivors. Unfortunately the distress signal had named the attacking starship as the Rosenante despite the fact that the ship was nowhere near the facility. &lt;br /&gt;
&lt;br /&gt;
Suspecting a set-up, Salid prepared to leave the system, but again was unable to withdraw before the arrival of the [[USS Furious]] Commanded by [[Rank|Captain]] [[Saleke]] arrived.&lt;br /&gt;
&lt;br /&gt;
knowing how the situation looked, Ahmed ordered the Rosenante to flee and the Furious pursued. Forced to investigate, Saleke engaged the Rosenante with specially modified [[quantum torpedo]]es which were equipped with [[Cloaking device|phased claoking devices]]. these torpedoes were able to get past the Rosenante&#039;s superior shielding and cause significant damage to the ship.&lt;br /&gt;
&lt;br /&gt;
Only the implementation of a new tactic, now called the [[The Salid Gambit]] allowed the Rosenante to escape into the rough asteroid fields of [[The Mill]]. Ahmed was able to cloak his ship and the furious picking up residual traces of a trail left by the original attacked set of in pursuit as Salid ordered repairs undertaken.&lt;br /&gt;
&lt;br /&gt;
Unknown to both saleke or Salid, the perpetrator in the raid on Bardon alpha was the [[Mirror Universe]] version of Ahmed. He commanded the [[ISS Rosenante]] and had set course to head to [[Hexikor Prime]], with the clear goal of capturing components critical to the completion of an [[Omega Device]].&lt;br /&gt;
&lt;br /&gt;
The ISS Rosenante arrived well before either the Furious or the USS rosenante could intercept her and conducted the raid with expected brutality. The components stolen were  a [[Paratrinic Shield|Paratrinic Shield Generator]] And a [[Class 11 Computer|Class 11 Bioneural Computer]]. The ISS Rosenante departed and headed for thier next target.&lt;br /&gt;
&lt;br /&gt;
The Furious arrived on the scene first and Saleke immediately began an investigation. While that was underway, Salid in the [[USS Rosenante]] arrived in the system under cloak.&lt;br /&gt;
&lt;br /&gt;
Determined not to have a repeat of the encounter at [[Bardon Alpha]], Captain Salid chose to neutralize the threat that the Furious posed by transporting six of their primary power buses off the Furious. These power relay buses, caused the ship to lose all primary power, rendering it unable to use weapons, shields or warp drive. Salid then ordered the surrender of the Furious but was unwilling to accept the surrender of that vessel from their First Officer Commander Erin Sloane. &lt;br /&gt;
[[Image:Omega Device.jpg|thumb|left|250px|Omega Device]]&lt;br /&gt;
Saleke was summoned and his presence was requested aboard the Rosenante. Having been convinced by the data that he had collected thus far in his investigation, Captain Saleke informed Captain Salid that he and his ship were no longer suspects in the attack, nor were they complicit in any plot to acquire and build an [[Omega Device]]. Salid had, independently, arrived at the same conclusion, that the ISS Rosenante, a ship from the Mirror universe was in fact responsible for the attacks. &lt;br /&gt;
&lt;br /&gt;
It was also clear that the Mirror Universe Rosenante was following a pattern that must have been established in their own universe. Which explained how the marauding vessel knew where to acquire the components for the creation of a new Omega Device. &lt;br /&gt;
&lt;br /&gt;
After some discussions, it was decided that the USS Furious and the USS Rosenante would need to combine forces in order to counter the tactical and homicidal threat now posed by the ISS Rosenante. &lt;br /&gt;
&lt;br /&gt;
As long range scans indicated that the Mirror Universe vessel was headed for the [[Kabor Prime|Kabor System]] The Rosenante took the Furious under tow, and using their own shields to protect them, opened a Spiral warp conduit to facilitate maneuvers while the Furious conducted the reinstallation of the power relay buses. &lt;br /&gt;
&lt;br /&gt;
A few days after the attack on the Bynar Facility in the Hexikor system, the ISS Rosenante appeared in the Kabor system. Thier target was a secret production facility known as [[Station Omega]]. The facility had been built by a secret research and development branch of Starfleet Sciences Division during the [[Admiral Doenitz|Doenitz]] regime. Thier primary function was the development of an [[Omega Device]]. &lt;br /&gt;
&lt;br /&gt;
After the end of the [[Federation Civil War]] the facility went underground. Through the actions of a small group of [[Starfleet]] [[Rank|Admirals]], all records pointing to the existence of such a facility were erased and the personnel there continued with their research. Through covert means, the facility was equipped with large Class XII phaser batteries for defense. At the heart of the facilities power center was a stabilized [[Omega Molecule]]. The first that the Station had managed to produce. &lt;br /&gt;
&lt;br /&gt;
The ISS Rosenante arrived in the system, intent on collecting the last few remaining components of the Omega device that they needed to create their own version of the weapon. As the Mirror Universe Ahmed Ibn Salid had worked at this facility in his universe, he had intimate knowledge of the facilities existence and layout. What he had not known was that the station had been armed, as in his universe, it was not protected. &lt;br /&gt;
&lt;br /&gt;
The Mirror universe ship was forced to subdue the facility by force, which cost them a great deal of time, narrowing the lead that they had on their Prime Universe Counterpart the [[USS Rosenante]] and the [[USS Furious]]. This delay would prove to be a great boon to the federation starship over the next few days. &lt;br /&gt;
[[Image:Sunali Sun Destruction.jpg|thumb|right|250px|The Destruction of the Sunali star]]&lt;br /&gt;
Despite this delay, the two [[UFP]] starships did not arrive in the system quickly enough to engage the Imperial Starship. They were however able to track it to it&#039;s next and final location, the [[Sunali II|Sunali System]].&lt;br /&gt;
&lt;br /&gt;
The [[USS Rosenante]] and the [[USS Furious]] entered the [[Sunali II|Sunali System]] to find the [[ISS Rosenante]] engaged in the wanton destruction of [[Cardassian]] merchant shipping. These ships although peaceful, had been destroyed simply because they were Cardassian.&lt;br /&gt;
&lt;br /&gt;
The USS Rosenante ordered the Imperial starship to surrender. That vessel refused.&lt;br /&gt;
&lt;br /&gt;
What followed next was a flurry of conflict, with the Stronger [[ISS Rosenante]] dealing a tremendous amount of damage to both the [[USS Rosenante]] as well as the [[USS Furious]],&lt;br /&gt;
&lt;br /&gt;
During the conflict the Furious engaged her [[Prometheus Class|Tri-vector Attack mode]] to engage the more powerful [[Mirror Universe]] vessel. The Mirror universe [[Andrew Elliot Maddox]] managed to take over the computer of one of the Furious&#039; sections named the Courageous and overload it&#039;s warp core killing all 142 hands on board. &lt;br /&gt;
&lt;br /&gt;
With the battle going against them, captain Salid came up with a plan to stop the Imperial vessel dead in it&#039;s tracks. Building off a suggestion made by [[Rank|Lieutenant]] [[Chance Raschen]], he initiated a transfer of the Omega Directive Protocols into the Imperial Starship&#039;s computer after the junior officer reeled them into communications range for the data transfer. That vessel&#039;s commander, having no experience with the [[Starfleet General Orders &amp;amp; Directives|Omega Directive]] was unable to unlock the ship&#039;s computer, which caused them to lose the battle.&lt;br /&gt;
&lt;br /&gt;
However, the ship had not been neutralized before they had managed to launch the [[Omega Device]] at the [[Sunali II|Sunali]] Sun. Unable to pursue, the Rosenante was forced to allow the [[USS Furious]] to intercept and eventually destroy the weapon.&lt;br /&gt;
&lt;br /&gt;
With the aid of [[Nathan Benoit]] the Furious and the Vigiliant (another element of the Furious), managed to shut down the [[Paratrinic Shield]] protecting the device by bypassing the operating system of the [[Class 11 Computer|Class 11 Bioneural Computer]] that controlled it. With the shields down, The Vigilant was able to destroy the device with Phaser fire just minutes before it would have detonated.&lt;br /&gt;
&lt;br /&gt;
With the battle over, Captain Salid ordered boarding parties to take possession of the [[ISS Rosenante]].&lt;br /&gt;
&lt;br /&gt;
The teams achieved their goals quickly and with little resistance, as the [[Mirror Universe]] Salid had ordered his crew not to resist.&lt;br /&gt;
&lt;br /&gt;
Meanwhile back aboard the USS Rosenante [[Alimi Morrow|Lieutenant Alimi Morrow]] fought to prevent a warp core collapse. his efforts and those of [[Jon Nayati|Lieutenant Jon Nayati]] and [[V&#039;Shera|Ensign V&#039;Shera]] managed to prevent the destruction of the federation vessel. However, it was not without cost. Morrow was seriously injured in the attempt and was treated for severe radiation poisoning. His condition was so critical that he was placed in Stasis until such time as he could receive treatment at [[Geneva Station|Starbase Geneva]]. His life was saved by the quick thinking and intervention of [[Kimiko Ichijo|Doctor Kimiko Ichijo]].&lt;br /&gt;
&lt;br /&gt;
After the Capture of the [[ISS Rosenante]] a deal was struck by which all the data concerning the [[Omega Conspiracy]] in the prime universe would be handed over to Captain Salid and Saleke in exchange for returning the Imperial ship home.  The agreement was made, after some discussion between The two Federation Commanding Officers and the Rosenante&#039;s First officer [[Jennifer Caskie]].&lt;br /&gt;
&lt;br /&gt;
A technical team was assigned to install an [[Interphasic Field Generator]] aboard the Imperial starship, which would force the ship back into it&#039;s normal universe. This same generator would then self destruct, making it impossible for the [[Imperial Union of Planets]] to recreate the devices for their use. Once the device was installed, the imperial ship was returned to the command of the [[Mirror Universe]] Salid and sent home. All indications suggest that the vessel was returned to their proper universe intact.&lt;br /&gt;
&lt;br /&gt;
The Rosenante, towing the [[USS Furious]] then returned to [[Starbase Geneva]] for repairs. &lt;br /&gt;
&lt;br /&gt;
===Mirror Universe Salid===&lt;br /&gt;
&lt;br /&gt;
Ahmed Ibn Salid of the [[Mirror Universe]] is a much different man than the one from our universe. The differences begin early on in his life. &lt;br /&gt;
&lt;br /&gt;
As a teenager, Ahmed showed a distinct aptitude for [[Engineering]]. His status was that of a child prodigy, and he was actually trained as an engineer in the hopes that he would serve in the Imperial Engineering Corps developing weapons and new technology.  He graduated from his classes with honors and was assigned to the [[ISS Templar]], Where he served as an Assistant Chief Engineer. He quickly began to make his way up the chain through deceit or assassination until he reached the rank of Lieutenant and the position of Chief Engineer.&lt;br /&gt;
&lt;br /&gt;
His career was cut short however, when it was discovered that his Father was involved in the planned assassination of the Empire&#039;s [[Klingon]] [[Regent]]. In retaliation, Salid was arrested and shipped to the [[Boronite]] mines on [[Bardon Alpha]]. It was there during his incarceration that he met the future regent [[Admiral Doenitz|Rodrigo Doentiz]]. &lt;br /&gt;
&lt;br /&gt;
Together the two men worked in the mines until the opportunity arose to escape. When that day came, the two men led a slave revolt against the penal colony&#039;s guards. The campaign was swift and brutal, and with the aid of a rebel ship captain, [[Devan Sash]], the two men escaped along with a small cadre of officers, including [[Saleke]], [[Zachary Falthgood]] and [[T&#039;Vhor]]. Later this group would eventually seize control of the leadership of the [[Human|Terran]] Rebellion and later the puppet Government of [[Earth]].&lt;br /&gt;
&lt;br /&gt;
Salid was promoted to Captain of the [[ISS Rosenante]] which became the Flag ship for the newly reformed and reorganized [[Mirror Universe|Imperial Union of Planets]]. His new role put him into direct conflict with several KCA starships, honing his abilities and reputation as an extraordinarily brutal ship commander. His complete dedication and loyalty to Regent Doenitz and the IUP guaranteed his quick rise to a position of power.&lt;br /&gt;
&lt;br /&gt;
In 2408, Ahmed was assigned the task to deploy the [[Omega Device]] against a KCA task force gathering at [[Sunali II]]. The weapon was deployed and it destroyed the enemy ships as well as the traitorous planet, which had defected to the KCA. The [[ISS Rosenante]] was thrown through a dimensional rift into the normal universe.&lt;br /&gt;
&lt;br /&gt;
==Mission Twelve: [[Equals and Opposites]]==&lt;br /&gt;
[[Image:StarbaseGeneva.jpg|thumb|right|300px|Starbase Geneva|200px]]&lt;br /&gt;
&lt;br /&gt;
With the return of the [[USS Rosenante]] and the [[USS Furious]] to [[Starbase Geneva]], refits and repairs from their encounter in the [[Sunali II|Sunali System]] began. With the work taking a great deal of the crews time and efforts, Captain Salid is repeatedly called before members of the admiralty to discuss the unsanctioned nature of his mission as well as reveal details and records of the [[Omega Conspiracy]].&lt;br /&gt;
&lt;br /&gt;
In addition to the briefings and meetings centered around the conspiracy, an official tribunal was called to inquire into the destruction of the  [[USS Furious|Courageous]] during the battle at Sunali II.&lt;br /&gt;
&lt;br /&gt;
The captain is displeased with the findings of the Tribunal, but his hands are tied as he is forced to deal with the harsh political nature of the situation.&lt;br /&gt;
&lt;br /&gt;
==Mission Thirteen: [[The Quondam Season]]==&lt;br /&gt;
[[Image:Iconia planet.jpg|thumb|right|200px|Xega III]]&lt;br /&gt;
The [[USS Rosenante]] is dispatched on a routine resupply mission for the archeological survey team located on [[Xega III]].&lt;br /&gt;
&lt;br /&gt;
The team led by Doctor [[Otto Totenkampf]] has been studying the ruins of the ancient [[Xegan]] civilization for nearly three decades.&lt;br /&gt;
&lt;br /&gt;
Among the tasks assigned to the crew of the Rosenante are standard planetary scans, launch of a pair of orbital satellites to aid the survey team, as well as assisting in planetary thermal and tectonic studies.&lt;br /&gt;
&lt;br /&gt;
Because the planet orbits an Orange giant star which constantly bombards the planet with stellar radiation, which seems to have gathered in the upper ionosphere, the use of transporters is impossible.&lt;br /&gt;
&lt;br /&gt;
The resupply, consisting of a mobile habitation unit, medical and foods supplies, as well as a replacement [[Argo Shuttle|Argo Class]] Shuttle and rover must all be undertaken by shuttlecraft.&lt;br /&gt;
&lt;br /&gt;
Shortly after arriving on the planet however, a strange energy reading is detected from a newly uncovered archeological site. This energy source is emanating from the [[Balancer Machine]], a legendary Xegan construct which was rumored to be able to prevent the planet from being ravaged by the very solar radiation that had caused the decline of the culture that created it.&lt;br /&gt;
&lt;br /&gt;
Suddenly the machine activated, perhaps for the very first time. Massive monoliths burst from the ground every feww hundred miles and rose into the planet&#039;s upper ionosphere. There they began to collect the radiation that was present and generate massive amounts of power into some unseen machine deep beneath the planet&#039;s surface.&lt;br /&gt;
&lt;br /&gt;
The crew of the Rosenante evacuated the archeological team and broke orbit to pbserve from a safer distance, as the monoliths were now creating massive storms in the planet&#039;s thin atmosphere.&lt;br /&gt;
&lt;br /&gt;
After the monoliths gathered energy for a period of roughly two standard days, a buildup was detected in one of the monoliths and a massive beam of light erupted from that monolith travelling towards the planet&#039;s sun.&lt;br /&gt;
&lt;br /&gt;
The affects of that massive energy beam, is unknown however, as at that exact moment, a massive temporal displacement wave, comprised of [[Chroniton]]s and an unidentified particle known as [[Seylerions]] entered the system moving at a speed greater than warp ten.&lt;br /&gt;
&lt;br /&gt;
The Rosenante was caught up in it and was thrust 5 years into the future.&lt;br /&gt;
&lt;br /&gt;
===The Future===&lt;br /&gt;
[[File:Balancer machine.jpg|thumb|300px|left|The Xega III Balancer Machine as seen from orbit]]&lt;br /&gt;
Once the wave had subsided, the crew of the Rosenante began to check their ship&#039;s systems, most notably their chronometers. The wave had caused some minor ships issues, the most serious of whihc was a disruption in the ship&#039;s warp drive systems.&lt;br /&gt;
&lt;br /&gt;
As the crew began repairs and went to work verifying that they had indeed been moved froward in time, Captain Salid ordered a communication sent to [[Starfleet Command]] to inform them of the event.&lt;br /&gt;
&lt;br /&gt;
He was surprised to see that the Rosenante&#039;s communications codes were invalid. At first he received no reply, but eventually, he was contacted by an admiral from command and ordered to hold position. Furthermore he was ordered to maintain a communications blackout, and to await an escort to an unknown location.&lt;br /&gt;
&lt;br /&gt;
Ever suspicious, Captain Salid complied, but prepared his ship for the worst.&lt;br /&gt;
&lt;br /&gt;
===Khitomer===&lt;br /&gt;
&lt;br /&gt;
The Rosenante was met and escorted to [[Khitomer]] by three Federation starships, one of which was a [[Rosenante Class]] vessel.&lt;br /&gt;
&lt;br /&gt;
Once they arrived, it was rather apparent that something massive had happened. A large number of [[starship]]s from the [[52nd Fleet]] had assembled here, along with an even greater number of escorts.&lt;br /&gt;
&lt;br /&gt;
[[Rank|Captain]] [[Ahmed Ibn Salid|Salid]] was ordered to beam down to [[Khitomer Conference|Camp Khitomer]] alone and await a debriefing.&lt;br /&gt;
&lt;br /&gt;
He arrived in the early morning, and was greeted by the sights and sounds of dozens of ship&#039;s commanding officers. Including those from the [[USS Mithrandir]], [[USS Spectre]], [[USS Hades]], [[USS Furious]], and [[USS Boudicca]].&lt;br /&gt;
&lt;br /&gt;
In addition to these officers, [[Rank|Admiral]] [[Robert LoDona]] was brought out of retirement to conduct the debriefing. &lt;br /&gt;
&lt;br /&gt;
Questions concerning the events which brought them here were asked and it quickly became apparent that nearly the entire [[52nd Fleet]] had been affected by the same phenomenon that had pushed the [[USS Rosenante]] forward in time.&lt;br /&gt;
&lt;br /&gt;
Further individual interviews were conducted with the Commanding Officers of the assembled starships before they were allowed to return to their vessels.&lt;br /&gt;
&lt;br /&gt;
Later Starfleet Science teams came aboard and scanned the ship, conducting a series of tests designed to verify the story that had been provided for the disappearance of the ships five years earlier.&lt;br /&gt;
&lt;br /&gt;
In addition to those teams, [[Starfleet Intelligence]] also came aboard to interview various members of the Rosenante&#039;s crew.&lt;br /&gt;
&lt;br /&gt;
After two days of studies and interviews, the rosenante was released from the Khitomer system and headed for [[Starbase Geneva]].&lt;br /&gt;
&lt;br /&gt;
There they underwent some retraining and some minor refits to bring them up to specifications with the technological and professional advances of the last five years.&lt;br /&gt;
&lt;br /&gt;
It was during this time that [[Rank|Commander]] [[Jennifer Caskie]] resigned, as she had discovered that her son Ian had gone missing during the five years prior.&lt;br /&gt;
&lt;br /&gt;
She was discharged from service.&lt;br /&gt;
&lt;br /&gt;
==Mission Fourteen: [[The Gilded Man]]==&lt;br /&gt;
[[File:Scout.jpg|thumb|400px|right| The USS Bohrs]]&lt;br /&gt;
&lt;br /&gt;
In 2314, nearly a decade after the Champlain&#039;s initial sensor readings of a Federation- style warp signature, in the [[Irlix|Irlix System]] the [[USS Bohrs]], a [[Mission Scout]] vessel, (&#039;&#039;&#039;NCC-369477&#039;&#039;&#039;) was dispatched to follow-up on those inital findings.&lt;br /&gt;
&lt;br /&gt;
The Bohrs proceeded to the Irlix system and utilizing her [[Cloaking device]] began to collect cultural and military data in an attempt to isolate the original source of the initial Federation warp signature.&lt;br /&gt;
&lt;br /&gt;
The Bohrs was on station for only a few weeks, when a computer attack shut down her cloaking device and left her vulnerable to attack by military starships belonging to the [[Rhone Union]].&lt;br /&gt;
&lt;br /&gt;
The Bohrs was captured and forced down on the [[planet]] [[Irlix]], where it was stored in the [[Seliya Facility]].&lt;br /&gt;
&lt;br /&gt;
A few days after the capture of the Bohrs, the [[USS Rosenante]] was tasked with the rescue of the crew of the Bohrs as well as the recovery and/or destruction of the starship. As a secondary objective, they were tasked with the discovery of the sudden technological boost found in Irlixian society which was inconsistent with the rest of their technological development.&lt;br /&gt;
&lt;br /&gt;
Because of a significant threat to the Rosenante, in light of the events leading up to the capture of the Bohrs, [[Rank|Captain]] [[Ahmed Ibn Salid]] decided to drop a cosmetically altered away team on the surface of the planet.&lt;br /&gt;
&lt;br /&gt;
After arriving in the Irlix system, the [[USS Rosenante]] approached the planet from a polar orbit acheived by following a very broad hyperbolic course. Once in position, the Away Team was sent down to the planet&#039;s surface, specifically to [[Khoda City]], in pairs, to minimize the chance of detection.&lt;br /&gt;
&lt;br /&gt;
The Away Team made their way to the Hotel Votul, a buisness known locally for allowing [[Irlixian|Gab]] males and [[Irlixian|Mol]] females to mingle in a social setting where they would not normally be permitted to do so. The meeting place at the hotel is marked by an interplexing communications beacon set up by [[Chance Raschen]]. The final meeting spot was a public restroom on the first floor of the hotel.&lt;br /&gt;
&lt;br /&gt;
Things get interesting when [[Mike Rosenbauer]]  shows up with [[Ios Malinae]], an [[Irlixian]] female, that he had &#039;rescued&#039; earlier from an assault and attempted rape. Ios apparently recognized Mike&#039;s blood, seeping from a broken lip as belonging to a [[Human]] rather than an Irlixian. She then revealed through an encounter with her mother, [[Sola Malinae]] that she was associated with the secret [[Seliya Facility]] where the research and development of the Alien ([[Federation]]) technology was being studied and retro-engineered.&lt;br /&gt;
&lt;br /&gt;
Taking a risk, Mike brought her to the meeting to allow [[Rank|Lieutenant Commander]] Sullivan a chance to question her and determine if she possessed any knowledge that may aid the Away Team in their mission.&lt;br /&gt;
&lt;br /&gt;
She was not, however, the only visitor to arrive at the Hotel Votul.&lt;br /&gt;
[[File:Dual moon planet.jpg|thumb|400px|left|Irlix]]&lt;br /&gt;
Senior Detective [[Vilox Nigo]], a member of the Special Police responsible for dealing with espionage inside the Rhine Union, detected the beacon and set into motion police resources in an attempt to capture the away team, which he believed were spies from one of the other major political powers on [[Irlix]].&lt;br /&gt;
&lt;br /&gt;
When the raid began, the away team put up more of a resistance than Vilox had anticipated and managed to escape although [[T&#039;Larah Sullivan|Sullivan]], [[Louis Remey]], [[Steven Wade Matrix|Steve Matrix]] and others were injured in the fighting to some degree.&lt;br /&gt;
&lt;br /&gt;
Thanks to the hard efforts of [[Sanok]], [[Thomas Jackson|Tom Jackson]] and [[Steven Wade Matrix|Steve Matrix]], the Away Team managed to escape the premises, narrowly dodging a perimeter of Police Snipers and pursuing law enforcement forces.&lt;br /&gt;
&lt;br /&gt;
While the away team found themselves in a pickle on the surface the [[USS Rosenante]] was facing difficulties of her own. under the command of [[Rank|Captain]] [[Ahmed Ibn Salid| Salid]], the Rosenante was forced to break orbit and begin a series of maneuvers to avoid detection and capture once it became apparent that the Irlixians were able in some manner to detect the cloaked [[Federation]] [[Starship]].&lt;br /&gt;
&lt;br /&gt;
As the goal was to avoid a confrontation and since the means by which the Irlixians were detecting the position of the Rosenante was unknown, the captain ordered the ship to displace frequently to delay any potential military actions between the Irlixian Fleet and the Rosenante.&lt;br /&gt;
&lt;br /&gt;
It was also interesting to note that the detection means was neither immediate nor precise and that meant that simple maneuvering whenever a course change took place among the Irlixian patrol craft happened were sufficient to keep the Rosenante safe from immediate harm.&lt;br /&gt;
&lt;br /&gt;
With the Rosenante well away from the planet, they found themselves unable to respond to the sudden appearance in the system of a Federation [[Danube Class Runabout|runabout]] without incurring significant risk to the Rosenante.&lt;br /&gt;
&lt;br /&gt;
This runabout was manned by two new recruits to the Rosenante [[Rank|Ensign Junior Grade]] [[Eian O&#039;Neill]] and Ensign Junior Grade Machaire Rabhartaigh. they had been assigned to the ship, but they had not been briefed on the nature of the Rosenante&#039;s mission and therefore found themselves entering hostile space unexpectedly. &lt;br /&gt;
&lt;br /&gt;
[[image:Irlixian Girl2.jpg|thumb|400px|right|An Irlixian Female]]&lt;br /&gt;
&lt;br /&gt;
The [[Irlixian]]s attacked. The result was the crippling of the runabout, which forced O&#039;Neill to crash land the damaged ship outside the Capital of the [[Rhone Union]], [[Khoda City]].&lt;br /&gt;
&lt;br /&gt;
Within minutes of the crash, however, the shuttle was surrounded by a small squad of Irlixian police. This prevented the immediate escape of the crash survivors.&lt;br /&gt;
&lt;br /&gt;
All hope was not lost, however, as Ensign O&#039;Neill had managed to send out a brief mayday message that alerted the away team already on the planet to their plight.&lt;br /&gt;
&lt;br /&gt;
A quick rescue and recovery mission was organized by the away team, still on the planet.The team made good speed from the safe house to the crash site where they relieved the surrounded crash victims before lead elements of the Secret police force under [[Vilox Nigo]] arrived. With the survivors recovered the extraction team returned to the safe house to await contact with the Rosenante and to continue medical treatment of the wounded.&lt;br /&gt;
&lt;br /&gt;
Meanwhile,  back aboard the Rosenante, it was becoming more difficult to avoid the ever shrinking search net of the Irlixian starships.&lt;br /&gt;
&lt;br /&gt;
It was the sudden epiphany offered up by Trade Winds Bar manager, and ex-intelligence officer T&#039;Lela, that the Rosenante was finally able to discover the means by which they were being tracked.&lt;br /&gt;
&lt;br /&gt;
The Irlixians were managing to track the automated communications data streams that all Federation starships use to connect to the [[Memory Alpha]] database as well as to navigational satellites. And while unable to disable this uplink, the deployment of some [[Stealth Buoy]]s, set to monitor the same frequency created a series of decoys that would confound the Irlixians and allow the Rosenante to slip free and return to [[Irlix]] to get an update from the away team there.&lt;br /&gt;
&lt;br /&gt;
When the Rosenante took up a standard orbit and made contact with the away team, it quickly became apparent that the initial mission parameters had no real chance of success. As a result Salid ordered the away team and their civilian adviser, Ios, beamed back aboard the Rosenante.&lt;br /&gt;
&lt;br /&gt;
While the members of the away team visited Sickbay to have the last of their injuries tended to and to have the cosmetic surgeries undone, Captain Salid was speaking with the civilian advise Ios concerning the situation. It was from that brief meeting and interview that a new plan of action was hatched.&lt;br /&gt;
&lt;br /&gt;
Once the away team was restored, and with the Rosenante managing to remain undetected at the polar orbit of the planet, Captain  Salid called a briefing where he outlined the new plan.&lt;br /&gt;
&lt;br /&gt;
He had become convinced after hearing about the history of the Rhone Union from Ios that a member of the Medea crew had managed to infiltrate the government and violated the [[Prime Directive]] for their own benefit.&lt;br /&gt;
&lt;br /&gt;
This in turn led the Captain to implement a three pronged plan of action that would achieve a variety of mission goals simultaneously.&lt;br /&gt;
&lt;br /&gt;
First Salid and [[Louis Remey]] would be making an appearance at a scheduled media conference being put forward by [[Ono Nakamura|Khoda Rhone]]. By hijacking the media feeds of the planet, Salid could insure that the message that he wanted to spread across the planet would remain uninterrupted. Remey would be responsible for running scans of the Rhone Union leadership present in an effort to ferret out the traitor in their midst.&lt;br /&gt;
[[File:Nakamara.jpg|thumb|left|300px|Ono Nakamura in 2393]]&lt;br /&gt;
While Salid and Remey acted as investigators, instigators and distraction, a second team led by [[Rank|Lieutenant]] [[Steven Wade Matrix]] and consisting of [[Marta Nunez]], [[Sanok]] and [[Robert Smith]] would conduct a raid against Rhone Union government offices in an attempt to locate information on the location of the Hostages from the [[USS Bohrs]]. Once that information was located, a third team led by [[Mike Rosenbauer]], and consisting of [[Kimiko Ichijo]], [[Sam Lopez]], and [[Eian O&#039;Neill]] would begin the operation to rescue the hostages while Matrix&#039;s team beamed to the sight of the Bohrs and prepared the ship for departure.&lt;br /&gt;
&lt;br /&gt;
Unfortunately, some parts of the plan did not quite happen as planned. Although The rescue team was deployed, matrix&#039;s team was forced to remain hidden in the government offices due to the fact that the Rosenante, Commanded by [[Rank|Commander]] [[T&#039;Larah Sullivan]], and aided by [[Rank|Lieutenant]] [[Thomas Jackson]] and [[Chance Raschen]], was forced into a military encounter with Rhone Union [[Starship]]s commanded by Fleet Commander [[Frazil]].&lt;br /&gt;
&lt;br /&gt;
Despite this setback, Rosenbauer&#039;s team managed to rescue not only the hostages from the Bohrs, but also [[Rank|Lieutenant]] [[Ben Soma]], previously of the [[USS Mithrandir]] and [[Rank|Lieutenant]] Doug Masters. The reinforced team managed to make their way to the Bohrs, and after a spectacular diversion with a damaged runabout, destroy the partially restored wreckage of the [[USS Medea]] and allow the Bohrs to escape the hanger once her systems were restored.&lt;br /&gt;
&lt;br /&gt;
While members of his crew were engaged in various levels of their portion of the operation, Captain Salid managed to cause Khoda Rhone, whom Remey had identified as [[Ono Nakamura]], previously the Chief Engineering Officer of the [[USS Medea]] to confess to his crimes.&lt;br /&gt;
&lt;br /&gt;
As expected, the [[Irlixian]]s were shocked and Khoda Rhone was ousted from power. He was taken into custody by Remey, while Salid attempted to rectify the cultural contamination that Nakamura had caused.&lt;br /&gt;
&lt;br /&gt;
After an additional eight days of negotiations, the governments of Irlix agreed to establish a provisional planetary government under the leadership of [[Ios Malinae]]. With the arrival of starships from the [[Federation Diplomatic Corps]], the USS rosenante was released from their mission.&lt;br /&gt;
&lt;br /&gt;
They aided in the repairs of the [[USS Bohrs]] before heading to [[Starbase 989]] for some much needed upgrades and R&amp;amp;R.&lt;br /&gt;
&lt;br /&gt;
==Mission Fifteen: [[Touch of the Eidolon]]==&lt;br /&gt;
[[File:Starbase 989.jpg|thumb|right|250px|Starbase 989]]&lt;br /&gt;
&lt;br /&gt;
The [[USS Rosenante]] after returning from [[Irlix]] system is long overdue for some much needed Rest and relaxation time on [[Starbase 989]].The ship put into dock and [[Rank|Captain]] [[Ahmed Ibn Salid|Salid]] held a briefing to bring his crew up to specs for the refit and resupply operations that would need to take place prior to the Rosenante&#039;s departure.For a change it looked as if everything would go well, and that the crew wouldn&#039;t be drawn into any unwanted scuffles with station personnel.It also seems that the reality of things is always different from the desired.&lt;br /&gt;
&lt;br /&gt;
Word quickly spread through the crew that the Starbase was holding the [[Alpha Quadrant|Alpha]]-[[Beta Quadrant]] wide martial arts tournament. The prize was a substantial [[latinum]] prize as well as the title of Champion of two quadrants. The following personnel from the Rosenante entered the tournament:&lt;br /&gt;
&lt;br /&gt;
*[[Kimiko Ichijo]]&lt;br /&gt;
*[[Ben Soma]]&lt;br /&gt;
*[[Eian O&#039;Neill]]&lt;br /&gt;
&lt;br /&gt;
They each competed against their respective opponents and were each in turn disappointed with the scores handed down to them by the panel of judges, which included, [[Ieko Takawa]]. However, rumor soon arose that the tournament may be fixed.  This coupled with information gathered by Soma during his investigation of Captain Taylor&#039;s murder, indicated that somehow the two could have been connected.&lt;br /&gt;
&lt;br /&gt;
[[File:Joseph Taylor.jpg|thumb|left|200px|Captain Joseph Taylor.]]&lt;br /&gt;
The day after the arrival of the [[USS Rosenante]] reports were made of the discovery of the body of [[Rank|Captain]] [[Joseph Taylor]], who was the commanding officer of [[Starbase 989]].  The captain was found dead in his quarters by a security officer from the station who had been dispatched when the Captain failed to respond to calls from his first Officer [[Rank|Lieutenant]] [[Kraal]].&lt;br /&gt;
&lt;br /&gt;
Almost immediately, Kraal contacted [[Rank|Captain]] [[Ahmed Ibn Salid]] and notified him of the grisly discovery. Citing Regulations, Salid, then assumed command of the investigation and assigned the Rosenante&#039;s own  Chief Security Officer [[Ben Soma]] to investigate.&lt;br /&gt;
&lt;br /&gt;
The body was recovered by the Rosenante team and a thorough study of the crime scene was conducted by [[Rank|Lieutenant]] [[Steven Wade Matrix]], and [[Eian O&#039;Neill]]. In addition to the survey of the crime scene, Doctor [[Kimiko Ichijo]] and Doctor [[Sam Lopez]] undertook an autopsy, to determine the cause of death.&lt;br /&gt;
&lt;br /&gt;
From the combined results of these studies clues and mysteries began to form, throwing out a number of plausible scenarios as to how the murder could have been conducted. Among the most puzzling of these mysteries was the nature of the murder weapon, a hook shaped spike that seemingly dematerialized inside the wound after the deed was done. In addition, coupled with the fact that the Captain had secured his personal quarters, the scene of the murder, with a very high level encryption that could only be overridden by other [[Starfleet]] officers of flag rank or greater, left the crew wondering who on the station had the ability to reach the obviously paranoid captain.&lt;br /&gt;
&lt;br /&gt;
To further complicate matters, the captain had no defensive wounds on his body, which would indicate that death was sudden and that the Starbase&#039;s commanding officer did not expect an attack.&lt;br /&gt;
&lt;br /&gt;
A short list of suspects was assembled, after further questioning and DNA evidence discovered that the Captain had been having an affair with two of his junior officers. Early in the investigation, there were strong indications that Captain Taylor may have been corrupt and that his murder may have been caused by a business deal going poorly.&lt;br /&gt;
&lt;br /&gt;
The chief suspects were:&lt;br /&gt;
&lt;br /&gt;
*[[Braak]]&lt;br /&gt;
*[[Pez]]&lt;br /&gt;
*[[Quol Nor]]&lt;br /&gt;
* Doctor [[Gena Harvey]]&lt;br /&gt;
* [[Rank|Lieutenant]] [[Adraa Mosul]]&lt;br /&gt;
*[[Ieko Takawa]]&lt;br /&gt;
&lt;br /&gt;
[[File:Harveq.jpg|thumb|250px|right|The Romulan freighter Harveq]]&lt;br /&gt;
The following day, a second body was discovered by a [[Starfleet]] engineer on duty on the station. He discovered the body of the [[Orion]] Cargo Master [[Nargo]]  of the [[Romulan]] [[starship|freighter]] [[Harveq]]. The ship&#039;s captain was [[T&#039;Sek]], a Romulan merchant. T&#039;Sek&#039;s grandfather is [[Chairman|Vice-Chairman]] [[Somek]] of the [[Romulan Tal Shiar]].&lt;br /&gt;
&lt;br /&gt;
Before the Station security personnel could arrive, however, T&#039;sek and some of his Orion crew recovered Nargo&#039;s body and took it aboard their ship.  When [[Ben Soma]] and his team from the Rosenante arrived, Soma was unhappy with the turn of events and planned to take action to deal with the situation.&lt;br /&gt;
&lt;br /&gt;
After some careful consideration, Soma assigned [[Sanok]] to open discussions with the Romulan ship captain. Little did they know, T&#039;Sek had full intentions of inviting them aboard the [[Harveq]]. The captain had four members f the Rosenante team transported aboard the [[Harveq]], [[Kimiko Ichijo]], [[Ben Soma]], [[Sanok]] and [[Eian O&#039;Neill]]. They were greeted by captain T&#039;Sek and an armed [[Orion]] security team. This event was initially misinterpreted by the away team as aggression, when in fact T&#039;Sek, was merely concerned with the appearance of the situation and did not wish to take a chance that the Starfleet officers were going to attempt to arrest him for interfering with their investigation.&lt;br /&gt;
&lt;br /&gt;
Once the away team was disarmed, the security detail relaxed and T&#039;Sek was amiable to the officers.&lt;br /&gt;
&lt;br /&gt;
[[Image:Holodeck empty.jpg|thumb|250px|left]]&lt;br /&gt;
Meanwhile, it was discovered that an upgrade request for the [[USS Rosenante]] to become upgraded to fully holo-capable had been filed by the new ACEO [[Eian O&#039;Neill]]. This of course, immediately set of a series of alerts, since O&#039;Neill was fully aware that the Rosenante was already completely Holo-capable. &lt;br /&gt;
&lt;br /&gt;
A quick investigation led the security team of the [[USS Rosenante]] to believe that someone had managed to steal a biometric fingerprint signature belonging to the officer.  When questioned, O&#039;Neill revealed that he had, in fact, used his finger print in two places on the station. &lt;br /&gt;
&lt;br /&gt;
The first was the Martial Arts Tournament on [[Starbase 989]]. The second was with [[Quol Nor]] when he booked [[Holodeck|Holosuite]] time on the station so that he could work on a special holoprogram to allow him to spend Christmas with his family, who were several [[Light Year]]s away.&lt;br /&gt;
&lt;br /&gt;
[[Ben Soma]] ordered O&#039;Neill to investigate.&lt;br /&gt;
&lt;br /&gt;
Those, it seemed were not the only technical difficulties facing the Rosenante. When Starbase engineers began their upgrade cycles, they managed to cause significant processing loss to the Rosenante&#039;s [[Computer Core]]s.  This caused a significant delay in the processing of the data collected at the crime scene by [[Steven Wade Matrix]]. In addition, the interlinks connecting the Rosenante to the Starbase were also damaged, meaning that the crew was unable to borrow processing time from the starbase.&lt;br /&gt;
&lt;br /&gt;
[[File:Rosk.jpg|thumb|right|200px|Doctor Rosk]]&lt;br /&gt;
Aboard the [[Harveq]], while [[Kimiko Ichijo|Doctor Ichijo]] and [[Sanok]] were meeting with [[Rosk|Doctor Rosk]] concerning the murder of [[Nargo]], [[Ben Soma]] and [[Rank|Ensign]] [[Eian O&#039;Neill]] were meeting with [[T&#039;Sek]].&lt;br /&gt;
&lt;br /&gt;
The meeting went well, with T&#039;Sek offering  a significant piece of the murder puzzle to the two officers in the form of a [[Cardassian]] [[Optolythic Data Rod]], which are renowned for their difficulty to forge.&lt;br /&gt;
&lt;br /&gt;
The data on the rod pointed firmly to the [[Ferengi]] [[Quol Nor]] as the Captain&#039;s murderer, but as the [[Romulan]] did not wish to testify, the investigation would need further evidence in order to arrest the Ferengi for the [[Rank|Captain&#039;s]] murder.&lt;br /&gt;
&lt;br /&gt;
During the second day of the tournament, Ichijo, Soma and O&#039;Neill confronted the senior judge [[Ieko Takawa]]. Their assertions caused the man to admit to his unwilling involvement in the fixing of the tournament, which indirectly had caused Taylor&#039;s death. He also directly connected  [[Quol Nor]] to the tournament, providing, for the first time a solid motive for the Ferengi. The tournament was suspended and all judgements withdrawn.&lt;br /&gt;
&lt;br /&gt;
[[File:Assassin Hologram.jpg|thumb|left| 350px|Quol Nor&#039;s Assassin Hologram]]&lt;br /&gt;
Convinced that the data was solid and needing more evidence that the [[Assassin Hologram]] was indeed connected to [[Quol Nor]] Soma, Ichijo, O&#039;Neill and Sanok devised a plan to lure the program in so that it could be neutralized and it&#039;s subroutines studied. the plan was simple in its design although rather complex in execution. After reactivating and securing the Holographic systems aboard the Rosenante, [[Eian O&#039;Neill]] prepared to isolate and neutralize the Program once it appeared on the Rosenante.&lt;br /&gt;
&lt;br /&gt;
To insure that it would appear, [[Sanok]] would activate the [[Data Cube]] that was recovered from [[Rank|Captain]] [[Joseph Taylor|Taylor&#039;s]] quarters where it had been disguised as a [[latinum]] sheathed moving sculpture.  Group gambled that the reactivation  of the data cube would alert either the program or it&#039;s [[Ferengi]] controller and that the end result would be that the program would attempt to recover the cube at all costs. With Sanok playing bait, [[Ben Soma]] and [[Kimiko Ichijo]] stood by to render assistance, while [[Eian O&#039;Neill]] would isolate the program.&lt;br /&gt;
&lt;br /&gt;
The plan was a qualified success, as the program appeared as expected. Although O&#039;Neill was quick the program was able to slightly injure both Sanok and Soma before it could be isolated completely.&lt;br /&gt;
&lt;br /&gt;
[[File:Quol Nor and Thugs.jpg|thumb|right|200px|Quol Nor and a pair of Nausicaan Enforcers]]&lt;br /&gt;
Soma, Sanok and O&#039;Neill along with a great many members of base security tracked [[Quol Nor]] down to his place of business where he was arrested by the Security team. The Ferengi threatened that Ferengi lawyers were far superior to anything that the federation possessed and that the Assassin Hologram was sentient, a claim that would later be overturned by a federation panel of experts. The program while highly sophisticated lacked the ability to adapt beyond certain pre-programmed parameters. &lt;br /&gt;
&lt;br /&gt;
The Murderer was brought to justice.&lt;br /&gt;
&lt;br /&gt;
==Mission Sixteen: [[Just Another Saturday Night]]==&lt;br /&gt;
&lt;br /&gt;
[[File:Vexarak Spoiler.png|thumb|left|200px|A Vexarak Spoiler]]&lt;br /&gt;
&lt;br /&gt;
While on shore leave aboard [[Starbase 989]] Captain Salid and the crew of the Rosenante are tied up in a crisis unlike any other that they have faced. &lt;br /&gt;
&lt;br /&gt;
The [[Tellarite]] freighter [[Moarvol]] inadvertently managed to bring a colony of [[Vexarak Spoiler]]s aboard the starbase in a shipment of &lt;br /&gt;
&lt;br /&gt;
[[Magnesite]] ore collected from the [[Zeta Draconis System]].&lt;br /&gt;
&lt;br /&gt;
These parasites consume metals and feed off of energy that they consume from it&#039;s breakdown. They are also capable of feeding from raw plasma.&lt;br /&gt;
&lt;br /&gt;
As a New Year&#039;s Party was underway on the Promenade, the Spoilers escaped their holding bin and began to ingest critical components of the starbase&#039;s power distribution system. This resulted in a cascade failure that plunged the starbase into complete power failure.&lt;br /&gt;
&lt;br /&gt;
When inhabitants of the starbase realized that the back up systems were not coming on-line they [[riot]]ed. Several members of the ship&#039;s crew along with members of the crew serving aboard the [[USS Boudicca]], were celebrating at [[The County Cork]] during the incident.&lt;br /&gt;
&lt;br /&gt;
When riots broke out, they were forced to defend themselves as well as attempt to restore orders and emergency services.&lt;br /&gt;
&lt;br /&gt;
Over the course of the next twenty-four hours, crews from both starships worked in concert to provide services, repairs and power to the starbase. Eventually, several methods were devised to deal with the infestation. Over the following weeks repairs to the starbase were conducted.&lt;br /&gt;
&lt;br /&gt;
After the incident Ahmed was asked and accepted the honor of marrying his long-time friend [[Thomas Jackson]] to [[Dahlia Jackson]] a woman that he had married earlier by [[Ferengi]] contract. The marriage was a formality to honor Jackson&#039;s [[human]] heritage. The ceremony took place at [[Rothal Chapel]] aboard [[Starbase 989]].&lt;br /&gt;
&lt;br /&gt;
==Mission Seventeen: [[Once More Into The Breach]]==&lt;br /&gt;
[[File:Dovek II.jpg|thumb|250px|right|Dovek II]]&lt;br /&gt;
After the near destruction of [[Starbase 989]], the crews of the [[USS Boudicca]] and the [[USS Rosenante]] were ordered to form a Task Force under the command of [[Rank|Captain]] [[Ahmed Ibn Salid]].&lt;br /&gt;
&lt;br /&gt;
After a flag level briefing, in which concerns over recent [[Borg]] activity in the [[Dovek II|Dovek System]], Captain Salid ordered the two ships of the task force immediately underway to the area of Borg activity for the purpose of locating the Borg forces there and determining the nature of their actions.&lt;br /&gt;
&lt;br /&gt;
Salid ordered the two ships to enter the system in such a manner as to utilize the natural formations to aid in the covert approach of the two ships. With the bulk of the Borg activity taking place in orbit around [[Dovek II]], salid and the crew of both ships begin to do research in the hopes of predetermining the potential threat of the Borg Activity.&lt;br /&gt;
&lt;br /&gt;
From the very beginning there were concerns, as a new type of Borg vessel, designated a [[Borg Pyramid]] was seen accompanying a [[Borg Tactical Cube]]. This was a strong indicator to Salid that the mission was sensitive and possibly militaristic in nature. &lt;br /&gt;
&lt;br /&gt;
When later research proved that the Dovek system had once been a part of the now extinct, but once very technologically advanced [[Tkon Empire]], Ahmed&#039;s worst fears came to the forefront.&lt;br /&gt;
&lt;br /&gt;
Upon arriving in the Dovek System, Salid ordered both ships to remain hidden behind Dovek II&#039;s only moon. From there a series of reconnaissance probes were launched in an attempt to gather information remotely. This failed due to the Borg&#039;s use of an [[Antiproton]] weapon for the purpose of large scale excavation on the planet&#039;s surface.&lt;br /&gt;
[[File:Beam attack on planet.jpg|thumb|left|300px|The Antiproton beam strikes Dovek II]]&lt;br /&gt;
Blinded due to the [[Subspace|Subspace Interference]], Salid moved forward with a plan to launch the [[Lorimar Class Runabout]] Lorimar, on an intelligence gathering mission. The runabout was performing well, apparently unheeded by the Borg [[starship]]s until [[Rank|Lieutenant]] [[Detron Trei]] managed to make contact with the [[Borg Collective]] in an attempt to cause panic amongst the [[Borg Drone]]s.&lt;br /&gt;
&lt;br /&gt;
Instead of causing panic, despite orders to not interfere, the telepathic contact made the Borg leader [[Volus]] aware of the [[Federation]] presence in the system. He ordered the Runabout attacked, and as a result the vessel crash-landed on the surface of [[Dovek II]].&lt;br /&gt;
&lt;br /&gt;
It was around this time that the Borg also uncovered their apparent goal, a [[Tkon Nanosphere]] that held incredible potential as a weapon to be used to assimilate [[Earth]].&lt;br /&gt;
&lt;br /&gt;
Now faced with a pair of problems, Salid ordered two separate missions. The first to rescue any crash survivors, while the second would cause plausible asset denial of the sphere from the Borg through the deployment of an [[antimatter]] mine.&lt;br /&gt;
[[File:Mine Detonation.jpg|thumb|250px|right|The Antimatter Mine detonating on Dovek II]]&lt;br /&gt;
With The Borg capital ship&#039;s positioned in such a way as to block any attempts at either mission, Salid ordered both the [[USS Rosenante]] and the [[USS Boudicca]] to act as a screening force against the Borg vessels in an attempt to drawn them away from the [[planet]].&lt;br /&gt;
&lt;br /&gt;
The two ships of the small task force attacked the Borg forces and successfully caused them to displace their position, which allowed the two away teams to penetrate the planet&#039;s atmosphere and carry out their missions.&lt;br /&gt;
&lt;br /&gt;
The crash survivors were rescued and the Antimatter mine deployed, and salid had thought that the Borg operations were thwarted until indications were seen that the [[Borg]] were opening a [[Temporal Vortex]]. realizing that the Collective intended to assimilate the device in the past, Salid ordered both the [[Federation]] [[starship]]s to follow and engage.&lt;br /&gt;
&lt;br /&gt;
On the other side of the vortex, the Federation ships found themselves in the Age of Makto, near the end of the [[Tkon Empire]]. They managed to destroy both the [[Borg Pyramid]] and the [[Borg Tactical Cube]], but not before both ships were boarded during the fight, and [[Borg Drone]]s sent to the surface of the planet, where assimilation of the [[Tkon Nanosphere]] began.&lt;br /&gt;
[[File:Temporal Vortex.jpg|thumb|left|300px|A Temporal Vortex]]&lt;br /&gt;
Fighting a desperate defensive action for their ships, the Federation crews were unable to prevent the [[assimilation]] of the nanosphere. As the Sphere lifted off the planet, Salid ordered one final ditch attempt to purge the two ships of Borg, using a specialized code that attacked the [[Borg]] [[Nanoprobe]]s.&lt;br /&gt;
&lt;br /&gt;
Despite an assassination attempt on his life and with both ship&#039;s free of Borg influence, and the nanosphere opening another [[Temporal Vortex]] Salid once again ordered pursuit.&lt;br /&gt;
&lt;br /&gt;
This time the two ships ended up in Earth&#039;s prehistoric past during a period called the [[Cretaceous Period]]. The two ships were unable to deal any damage to the [[Tkon]] device as long as it&#039;s shields remained operational, so Salid ordered a small elite security force to beam aboard the ship using a theoretical Transporter algorithm.&lt;br /&gt;
[[File:Chicxulub close impact.jpg|thumb|250px|right|The impact with the crust of the planet]]&lt;br /&gt;
A tremendous fight ensued and the away team was barely beamed off the sphere, before the combined firepower of the [[USS Boudicca]] and the [[USS Rosenante]] destroyed it. Along with the destruction of the sphere came that of the Borg leader [[Volus]] and the Tkon scientist [[D&#039;askto]] who had joined forces with the away team.&lt;br /&gt;
&lt;br /&gt;
Although they had destroyed the most immediate threat of assimilation in [[Earth|earth&#039;s]] ancient past, the bulk of the sphere rained down on the planet nearly wiping out all life there.  Ironically, it was this event that wiped out the dinosaurs and allowed [[Human|Humanity]] to evolve.&lt;br /&gt;
&lt;br /&gt;
After several days of repairs and hard work, The combined crews managed to activate the Borg Temporal equipment that was left behind by the Borg Occupation of their ships and used it to return home to the present.&lt;br /&gt;
&lt;br /&gt;
The two ships then limped home to a hero&#039;s welcome.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Mission Eighteen: [[Personal Logs]]==&lt;br /&gt;
With the refit of the [[USS Rosenante]] underway after the battle at [[Dovek II]], Ahmed decided to take some time off and enjoy some friendly competition in the boxing arena on [[Starbase Geneva]].  However things did not go according to plan when he was requested by the [[Rank|Admiralty]] to participate in the general mast hearings for [[Detron Trei]] and [[Andrew Elliot Maddox]], two officers that were under his command during the Dovek II incident.&lt;br /&gt;
[[File:S31.jpg|thumb|left|300px|The symbol for Section 31]]&lt;br /&gt;
He agreed, and after some deliberation a series of disciplinary actions were undertaken against both the officers. He was later to discover that [[Rank|Captain]] [[Alan Durand]] had resigned from the fleet as a result of his actions at Dovek, despite the fact that Salid and other members of the general Admiralty did not feel his performance was inadequate to the situation.&lt;br /&gt;
&lt;br /&gt;
This temporarily left Salid in command of the [[USS Boudicca]] as well as the [[USS Rosenante]] until [[Rank|Captain]] [[Calvin Capps]]  arrived to take command of the Boudicca.&lt;br /&gt;
&lt;br /&gt;
During this time, [[Rank|Commander]] [[Thomas Jackson]] was reassigned to the USS Boudicca as her first officer, displacing her prior first Officer, [[Rank|Commander]] [[Jennifer Caskie]].&lt;br /&gt;
&lt;br /&gt;
For reasons unclear, Caskie was relieved of her command position and reassigned to the Rosenante as their [[Medical Officer|Chief Medical Officer]]. Ahmed was glad to see her return to the ship.&lt;br /&gt;
&lt;br /&gt;
Also during this Ahmed found himself suddenly involved in a situation with [[Section 31]], when they kidnapped a member of his crew, [[Rank|Ensign]] [[Jessica Signos]] after [[Ahmed Ibn Salid]] had reported her dual nature to [[Starfleet Intelligence]].&lt;br /&gt;
&lt;br /&gt;
The kidnapping was actually a ploy by SFI to flush out the [[Section 31]] Operatives on [[Starbase Geneva]]. Salid became involved when he felt that his officer was placed at undue risk as a result of SFI&#039;s slow response to the affectation of her rescue.&lt;br /&gt;
[[Image:Ranger Patch.png|thumb|right|300px|The duty patch of the Starfleet Rangers]]&lt;br /&gt;
Along with [[Eian O&#039;Neill]], his father [[Liam O&#039;Neill]] of the [[USS Kelman]], [[Katherine &#039;Kitty&#039; Fisher]], and [[Chance Raschen]], Salid put together a rescue team in an attempt to affect her release and to capture or eliminate the [[Section 31]] operatives on the station.&lt;br /&gt;
&lt;br /&gt;
The location of the hostage was located in a phased portion of the starbase, and as soon as the location rejoined normal space, Salid and the others beamed in to rescue Signos.&lt;br /&gt;
&lt;br /&gt;
The operation was a success, capturing one Section 31 Operative,  and eliminating almost all of the others. Only [[George Hayden, Jr.|George Hayden]] the cells handler managed to escape the station.&lt;br /&gt;
&lt;br /&gt;
However, after having O&#039;Neill work up a psychological profile for Hayden, a plan was put into place to draw the cell handler back to [[Starbase Geneva]]. Putting himself into a position to illicit irritation and to appear smug at his victory over Hayden, Salid was able to draw the man back into the Starbase.&lt;br /&gt;
&lt;br /&gt;
Hayden however, was not sloppy. He had taken extreme measures to protect himself, and this time, he used a holodeck to mask his presence. He managed to kidnap Salid, and for a short while torture him until [[Eian O&#039;Neill]] managed to fix the Captain&#039;s location.&lt;br /&gt;
&lt;br /&gt;
An assault team [[transporter|beamed in]] to the area and captured Hayden. This operation proved to be a linch-pin for preventing any formal charges from SFI to be levied against Salid and his officers. It did unfortunately put them on Section 31&#039;s radar as potential threats, since they were now aware of their illicit existence.&lt;br /&gt;
&lt;br /&gt;
As a direct result of this operation, Salid, transferred, [[Mike Rosenbauer]] to act as his Yeoman, in an effort to provide himself with a bodyguard of some skill. It was a task for which the former [[Starfleet Rangers|Starfleet Ranger]] was well suited.&lt;br /&gt;
&lt;br /&gt;
==Mission Nineteen: [[The Third Law]]==&lt;br /&gt;
&lt;br /&gt;
While continuing on their mission to explore [[Sector 6309]], the crew of the  Rosenante discovered a rogue planet, which they later discovered was named [[Solyon]]. &lt;br /&gt;
&lt;br /&gt;
Excited about the possible history-making discovery, Captain Salid ordered three teams down to conduct scientific, geological and biological exploration of the unusual planetary body.&lt;br /&gt;
&lt;br /&gt;
While the away teams were on the planet&#039;s surface, Salid ordered the Stellar cartography department to attempt to project Solyon&#039;s course as well as extrapolate it&#039;s path of travel prior to discovery.&lt;br /&gt;
&lt;br /&gt;
Within hours, it was determined that the [[Rogue Planet]] would be passing through a [[Binary stars|binary star system]] which contained an inhabited planet, known as [[Asrai Prime]]. With the planet&#039;s inhabitants, the [[Asrai]], only at a pre-industrial level of technology, a bit of a moral issue arose. Technically, if the Asrai were unaware of other species or if they had not developed any technology akin to warp drive, then they would, under the auspices of the [[Prime Directive]] be left to their extinction.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
{| class=&amp;quot;toc color&amp;quot; style=&amp;quot;border:3px solid goldenrod;&amp;quot;align=&amp;quot;center&amp;quot;;&amp;quot;width=246px&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:black&amp;quot; align=&amp;quot;left&amp;quot; |&amp;lt;font color=goldenrod&amp;gt; &amp;lt;small&amp;gt;{{quote|As the right of each sentient being to live in accordance with its normal cultural evolution is considered sacred, no Starfleet personnel may interfere with the normal and healthy development of alien life and culture. Such interference includes introducing superior knowledge, strength, or technology to a world whose society is incapable of handling such advantages wisely. Starfleet personnel may not violate this Prime Directive, even to save their lives and/or their ships, unless they are acting to right an earlier violation or an accidental contamination of said culture. This directive takes precedence over any and all other considerations, and carries with it the highest moral obligation. |The Prime Directive}}&amp;lt;/small&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To further complicate things somewhat, the survey teams returned to the ship with evidence that Solyon had at one point been [[terraforming|terraformed]]. This caused Captain salid to order two separate missions to be undertaken. The first would travel to Asrai Prime to see if there was any evidence that would make the Asrai exempt to the conditions of the Prime Directive. The second would remain on the rogue planet in an attempt to find a means to deviate or destroy the rogue world if a means could not be found to alter it&#039;s course.&lt;br /&gt;
&lt;br /&gt;
Due to the gravity of the situation, Captain Salid led the away team to Asrai Prime while [[T&#039;Larah Sullivan]] led the mission on the rogue planet.&lt;br /&gt;
&lt;br /&gt;
On Asrai Prime the mission began to develop in a turbulent and difficult atmosphere. The inhabitants communicated as much with body postures and gestures as they did with words. because of this, the Universal translator couldn&#039;t assist them with this type of communication.&lt;br /&gt;
&lt;br /&gt;
[[File:Asrai Prime.jpg|thumb|left|500px|Asrai Prime]]&lt;br /&gt;
&lt;br /&gt;
A misunderstanding saw Salid and Fraiser imprisoned, but in so doing, it allowed the remaining members of the away team to uncover a group of outcasts that seemed to possess advanced technology. The situation quickly became clear. The leadership of the planet had created an enforced reversion in technology while maintaining their own technological advantage to make them the rulers of the world.&lt;br /&gt;
&lt;br /&gt;
This was complicated when the Survey teams from the rosenante on the Rogue planets discovered that the planet was actually an ancient colony ship that had narrowly escaped the destruction of their home world. They were headed for Asrai Prime, the last remaining colony of their ancient civilization. &lt;br /&gt;
&lt;br /&gt;
However the massive ship was badly damaged and required extensive repairs to allow it to adjust it&#039;s mass and avoid disrupting the delicate balance of Asrai Prime.  With the engineering teams working hard on that problem, Salid and Fraiser faced execution.&lt;br /&gt;
&lt;br /&gt;
However, with the discovery of the outcasts and the situation clearly no longer constrained by the Prime Directive, [[Ben Soma]] led a rescue operation and they successfully rescued Fraiser and Salid.&lt;br /&gt;
&lt;br /&gt;
meanwhile Salid and Fraiser had learned of an ancient planetary defense weapon once designed to destroy possible asteroid strikes, that was being prepared to destroy the Rogue Planet. As it was now apparent that the leader of the Asrai was aware that Solyon was actually a colony ship, and with the new information given to Salid, it was decided to prevent the destruction of the colony ship.&lt;br /&gt;
&lt;br /&gt;
In a last-ditch effort, Salid and his away team prevented the destruction of the colony ship and helped re-establish the technological society that had been stripped from the Asrai. the Diplomatic Corps opened an embassy on Asrai prime to help the new Asrai leadership re-integrate the long-neglected masses of the planet, in effect preventing the extinction of the Asrai people.&lt;br /&gt;
&lt;br /&gt;
==Mission Twenty: [[The Captain&#039;s Cotillion]]==&lt;br /&gt;
[[File:Salid-cotillion.jpg|thumb|right|500px|Captain Salid at the Cotillion, serving drinks.]]&lt;br /&gt;
&lt;br /&gt;
After the completion of the mission to save [[Asrai Prime]] the crew of the [[USS Rosenante]] moved into a support role for the new government of that planet. With the institutionalization of a new ruling system headed by the more technologically advanced Asrai from [[Solyon]], Ahmed was determined to insure  a series of programs that would help bring the remainder of the population into line with the new leaders of that planet.&lt;br /&gt;
&lt;br /&gt;
To that end, each of the departments began a program of assisting in building a knowledge infrastructure that the planet could then develop and expand on a planetary basis. To this end, medical databases, civil engineering databases and diplomatic databases have been supplied to the new government.&lt;br /&gt;
&lt;br /&gt;
With the civilization most recently believed to be under the protection of the [[Prime Directive]], which was disproven with the realization that [[Solyon]] was a warp capable colony ship, the [[Federation Diplomatic Corps]] was ordered by [[Starfleet Command]] to send special teams to aid the [[Asrai]] in their modernization efforts. &lt;br /&gt;
&lt;br /&gt;
To celebrate the new relationship and the mutual support between the [[UFP]] and the government of [[Asrai Prime]], [[Rank|Captain]] [[Ahmed Ibn Salid|Salid]] decided to implement a new tradition aboard the Rosenante in the form of a formal dance, which he dubbed the &amp;quot;Captain&#039;s Cotillion&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The affair was punctuated by the appearance of many of the ship&#039;s crew appearing in elaborate outfits, and taking a night on the town. The event filled Cargo Bays one and Two, which had been retrofitted by [[Rank|Commander]] [[Steven Wade Matrix|Matrix]], [[Rank|Lieutenant]] [[Ben Soma|Soma]], [[Rank|Lieutenant]] [[Thomas Jackson|Jackson]] and [[Rank|Lieutenant]] [[Sanok]].&lt;br /&gt;
&lt;br /&gt;
The prevent for the women of the crew took place on the holodeck, where [[Jessica Signos]] invited them all to a Japanese Bath house program for a day of pampering, gossip and spa treatments.&lt;br /&gt;
&lt;br /&gt;
Not all was well, however, as on the eve of the event, Signos and [[Eian O&#039;Neill|O&#039;Neill]] broke off their relationship due to &amp;quot;Lily&amp;quot;. A further incident took place when [[Tayla Fraiser]] inadvertently made telepathic contact with Signos, and was affected by &amp;quot;Lily&#039;s&amp;quot; presence, sending her into a panic attack that later caused her to attack [[Parker Davis]].&lt;br /&gt;
&lt;br /&gt;
This period of time saw the addition of a couple of new crew to the roster as well. [[Rank|Lieutenant]] [[Lanista]] , formerly from the [[USS Mithrandir]] and on return from a 5-year mission in [[Klingon]] space, was assigned to the [[USS Rosenante]] as their newest Chief Science Officer. Lieutenant [[Viskhard]], as a result of this new addition was reassigned to the position of Assistant Chief Science Officer. Another addition to the crew was [[Rank|Lieutenant]] [[Nayeli]], a member of the [[Starfleet Judge Advocate General Corps (JAG)|JAG Corps]]. Her purpose was to look into the possible violations of the [[Prime Directive]] on [[Asrai Prime]]. She was assigned as a standing member of the crew in reflection to Starfleet&#039;s concern over the matter. As a result, Captain Salid has no choice but to keep her aboard.&lt;br /&gt;
&lt;br /&gt;
The crew not only gained  new crew, but sadly have seen some transferred off the ship as well. [[Rank|Commander]] [[T&#039;Larah Sullivan]] was reassigned to the [[Starfleet Marine Corps]], where she assumed the rank of [[Rank|Lieutenant Colonel]]. She was joined by Lieutenant Masters. This left the position of First officer open, and [[Rank|Captain]] [[Ahmed Ibn Salid]] saw no reason not to promote his new Second and Third Officers into empty positions. As such, [[Rank|Lieutenant]] [[Ben Soma]] was promoted to First Officer and advanced in rank to [[Rank|Lieutenant Commander]], while [[Sanok]] was promoted to Second Officer. At this time Salid has not yet selected a third officer for the Rosenante.&lt;br /&gt;
&lt;br /&gt;
Not to be outdone, several members of the Rosenante&#039;s senior staff had their photograph taken for nostalgia&#039;s sake.&lt;br /&gt;
&lt;br /&gt;
==Mission Twenty-one: [[The Veil of the Sky]]==&lt;br /&gt;
[[File:Comet2.jpg|thumb|right|400px|Comet Holladay]]&lt;br /&gt;
&lt;br /&gt;
After [[The Captain&#039;s Cotillion]], the [[USS Rosenante]] was once again underway to continue her survey of [[Sector 6309]] as she had been ordered.  During this time, the crew encountered an unusual [[comets|comet]], which later became known as [[Comet Holladay]] in honor of the scientist who detected it by long-range scans.  Detailed scans and trajectory studies were underway, when an urgent message from [[Starfleet Command]] was received.&lt;br /&gt;
&lt;br /&gt;
A hostage situation had developed on the planet [[Beta Aquillia IV]] a world that supplied the [[Federation]] with a vast majority of the resources needed to rebuild their infrastructure and starships. the planetary government, led by President Kolath had been overthrown by a sudden and unexpected coup. The group responsible was a pro-isolationist group named [[Veil of the Sky]].&lt;br /&gt;
&lt;br /&gt;
During this coup, their leader, [[Habrii]] took Federation [[Ambassador]] [[Joanne Turner]] and her embassy staff hostage. The Rosenante was dispatched to negotiate her release and if possible to determine if there was outside support for the Veil.&lt;br /&gt;
&lt;br /&gt;
Upon their arrival, Salid attempted to make contact with the current government. He was at first ignored. determined to safe-guard refugees displaced by the conflict, especially those with Federation citizenship, Salid sent his crew down to the capital city of Joba to establish a safe-zone and a refugee camp to tend to the needs of the displaced.&lt;br /&gt;
&lt;br /&gt;
To make things more complicated a [[Skorr]] [[Worldripper Class]] warship named the [[Skysplitter]] arrived. it seemed that a Skorr Ambassador was also taken hostage and [[Ambassador]] [[Dralar]] had been sent to recover him. This made the situation potentially unstable.&lt;br /&gt;
&lt;br /&gt;
After the arrival of the Skorr vessel, [[Ben Soma]] led a negotiation team down to the planet with no real success. The political views of the Veil leadership made diplomacy all but impossible. However, the [[Aquillian]] ambassador, Tzorn began to make indications that he would aid the Rosenante crew in locating their ambassador in return for asylum.&lt;br /&gt;
&lt;br /&gt;
[[Chance Raschen]] and [[Mike Rosenbauer]] were assigned to covertly attempt to locate the ambassador on the planet. Mike managed to persuade a Veil member named [[Sien]] to join the Federation&#039;s cause, while chance uncovered some signs of [[Cardassian]] Involvement.&lt;br /&gt;
[[File:Atlantis Station.jpg|thumb|300px|left|Atlantis Station]]&lt;br /&gt;
&lt;br /&gt;
A series of suicide bombings at the refugee camp forced a breakdown in communication between the Veil and the Federation.  Refugee support operations became disaster relief. At Salid&#039;s request [[Dralar]] sent Skorr troops to shore up the Federation position.&lt;br /&gt;
&lt;br /&gt;
Meanwhile on [[Atlantis Station]], [[Niambh McNulty]] allowed the Rosenante&#039;s crew to establish a [[Command Control and Communications Center]]. From there the crew could more easily communicate and organize disaster relief.&lt;br /&gt;
&lt;br /&gt;
As the investigation continued, [[Steven Wade Matrix|Matrix]] and Peter Cohen discovered signs of Romulan involvement. The situation was quickly becoming murky, and it was even more unclear who was truly involved in supporting the Veil.&lt;br /&gt;
&lt;br /&gt;
When word went out that [[Alaya]] the lieutenant of the [[Veil of the Sky]] was responsible for the suicide attacks on the refugee camp, [[Habrii]] ordered her arrested. She was captured, but her escape was secured by Gul [[Matan]] of the [[Obsidian Order]]. Alaya then led a counter-coup against Habrii, capturing him and seizing control of the government.&lt;br /&gt;
&lt;br /&gt;
Meanwhile through subterfuge, the location of [[Ambassador]] Turner and the [[Skorr]] Ambassador became known. The Skorr rescued their Ambassador with the aid of [[Katherine &#039;Kitty&#039; Fisher]], while [[Jessica Signos]] led the rescue of the [[Federation]] Ambassador.&lt;br /&gt;
&lt;br /&gt;
[[File:Camp explosion.jpg|right|thumb|300px|One of the explosions at the refugee camps]]&lt;br /&gt;
&lt;br /&gt;
At the same time, [[Ben Soma]] led a team to extract the [[Aquillian]] Ambassador Tzorn as agreed. With all these actions underway, Salid was also on guard for any [[Cardassian]] or [[Romulan]] interference.&lt;br /&gt;
&lt;br /&gt;
Instead, however, he was forced to deal with the [[Veil of the Sky]] militia troops. [[Alaya]] had ordered them to assault [[Atlantis Station]] as well as the refugee camp protected by the Federation.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Salid utilized the ship&#039;s [[phaser]]s et to heavy stun to slow down the infantry assault against the camp. in addition, he used low-yield photon torpedoes to capsize the boats bombarding Atlantis Station.&lt;br /&gt;
&lt;br /&gt;
Once the refugees were evacuated, Salid recalled his crew. As his orders were to not get directly involved in the political struggle for control of the planet, the Rosenante then departed. But not before McNulty destroyed Atlantis station and the president in Exile Kolath, disappeared into the urban underground to establish a revolutionary movement to regain control of the government of Beta Aquillia IV.&lt;br /&gt;
&lt;br /&gt;
For the crew of the Rosenante, it was a bittersweet victory.&lt;br /&gt;
&lt;br /&gt;
==Mission Twenty-two: [[A Port in the Storm]]==&lt;br /&gt;
&amp;lt;strong&amp;gt;&amp;lt;font color=goldenrod&amp;gt;COMING SOON!&amp;lt;/font&amp;gt;&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Awards and Commendations: ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
image:Cross_of_Fire.gif|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded Cross of Fire: For actions above and beyond the call of duty during the battle for the MDP on stardate 2407.07.09&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
image:Combat_Action_Ribbon.gif|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded Combat Action Ribbon: For services rendered in freeing Cait Prime for the Occupation of Doentiz forces and it&#039;s illegal and immoral experiments.&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
image:Captain&#039;s_Commendation.jpg|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded Captains Commendation: For actions during and after the battle for the MDP, stardate 2407.07.09&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
image:Captain&#039;s_Commendation.jpg|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded Captains Commendation: Awarded on behalf of the Cartenian Commonwealth for Services rendered in the Rescue of Prince Khamal from the Orion Syndicate on Stardate 2408.03.15&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Image:Order_of_Unity-_Ribbon.jpg|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded The Order of Unity: Awarded in commemoration of services rendered during the Federation Civil War.&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
image:Rib19.gif|&amp;lt;small&amp;gt;Awarded Squadron Commander&#039;s Commendation: Awarded on Stardate 2414.02.14 for actions above and beyond the call of duty, critical to the success of the Mission to destroy the T&#039;Kon Sphere held by the Borg.&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
File:Rib05.gif|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded Medal of Distinction: Awarded Stardate 2414.02.16, for gallantry in the line of duty against forces hostile to the United Federation of Planets.&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Rosenante Crew Roster}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Characters]][[Category:History]][[Category:Civil War]][[Category: Mirror Universe]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Retired_staff&amp;diff=55870</id>
		<title>Retired staff</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Retired_staff&amp;diff=55870"/>
		<updated>2012-09-05T16:17:08Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* Mission Six: Picking up the Pieces. */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;toc colour&amp;quot; style=&amp;quot;margin: 0 0 1em 1em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:goldenrod&amp;quot; align=&amp;quot;center&amp;quot; |&amp;lt;font color=maroon&amp;gt;&#039;&#039;&#039;Ahmed Ibn Salid&#039;&#039;&#039;&amp;lt;br&amp;gt;&amp;lt;font color=maroon&amp;gt;Commanding Officer, USS Rosenante&amp;lt;/font&amp;gt;&amp;lt;br&amp;gt;[[File:IbnSalid.jpg|center|300px|Captain Ahmed Ibn Salid]]&amp;lt;br&amp;gt;&amp;lt;/font&amp;gt;[[File:Rosenante-Alt-2up.jpg|center|300px|USS Rosenante]]&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Vital Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Age: 38&lt;br /&gt;
**Gender: Male&lt;br /&gt;
**Birthplace: [[Cairo]], [[Egypt]], [[Earth]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Physical Information&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Eye Color: Brown&lt;br /&gt;
**Hair Color: Black&lt;br /&gt;
**Height: 5.5 feet&lt;br /&gt;
**Weight: 170 lbs&lt;br /&gt;
**Skin Color: Olive&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Career Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Rank: [[Rank|Captain]]&lt;br /&gt;
** Current Assignment: [[USS Rosenante]]&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Prior Assignments:&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
**Stardates: 2408.01.04 - 2408.01.06&lt;br /&gt;
**[[ Starbase Valhalla]] - [[Engineering|Engineering Operations Officer]]&lt;br /&gt;
**Stardates: 2407.07.09 - 2408.01.04&lt;br /&gt;
**[[USS Hypatia]] - [[First Officer]]&lt;br /&gt;
**Stardates: 2407.04.02 - 2407.07.09&lt;br /&gt;
**[[USS Champlain]] - [[First Officer]]&lt;br /&gt;
**Stardates: 2406.01.04 - 2407.01.22&lt;br /&gt;
**[[USS Nimitz]] - [[Engineering|ACEO, CEO]]&lt;br /&gt;
**Stardates: 2402.03.12 - 2406.01.04&lt;br /&gt;
**[[Starfleet Academy]] - [[Rank|Cadet]]&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;toc color&amp;quot; style=&amp;quot;border:3px solid goldenrod;&amp;quot;align=&amp;quot;center&amp;quot;;&amp;quot;width=246px&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:black&amp;quot; align=&amp;quot;center&amp;quot; |&amp;lt;font color=goldenrod&amp;gt;&amp;lt;small&amp;gt; {{quote|Being hugged by Commander Zzt isn’t that bad really...after you lose consciousness.|Ensign Junior Grade Ahmed Ibn Salid}}&amp;lt;/small&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==Childhood==&lt;br /&gt;
&lt;br /&gt;
Ahmed was born in [[Cairo]], [[Egypt]]- [[Earth]] on Stardate 2382.04.10 to Salid ibn Jaffar and Jasmine Mosatuff. At the time of his birth his father was an engineering ensign aboard the USS Roland and his mother was an artist.&lt;br /&gt;
&lt;br /&gt;
Ahmed lived in Cairo for the vast majority of his life, although he did spend a few years aboard the [[USS Roland]] and the [[USS Archimedes]] with his mother and father.&lt;br /&gt;
&lt;br /&gt;
At the age of five years, Ahmed’s parent’s divorced after Ahmed’s mother Jasmine was discovered to be having an affair, with the USS Archimedes’ Chief Counselor. Ahmed’s father, unable to raise the boy alone and without a desire to release him to his mother’s custody,sent young Ahmed back to Cairo to live with his Uncle Aamihr. Before leaving the Forrester, Ahmed’s mother gave him a necklace to remember her by. He still wears it to this day.&lt;br /&gt;
&lt;br /&gt;
Ahmed had a difficult time adjusting to his new life with his Uncle. When he reached his teens, Ahmed became rebellious and would often disobey his uncle’s wishes. In the interest of finding something to occupy his nephew’s time in a more productive manner, Ahmed’s uncle introduced the boy to [[Sailing]] and [[Boxing]].&lt;br /&gt;
&lt;br /&gt;
There were remarked improvements in Ahmed’s grades as a result of these new interests. It was discovered that he possessed a photographic memory and that he had become bored with his studies, since he could memorize the course curriculum within a few hours. Boxing and Sailing gave him physical challenges as well as mental ones, and he began to work in his uncle’s business, teaching tourists how to sail traditional Egyptian boats on the Mediterranean sea. Ahmed would often participate in unsanctioned boxing clubs in his teens.&lt;br /&gt;
&lt;br /&gt;
It was during this time that Ahmed began to take an intense interest in History. His uncle had revealed Ahmed’s rich family Lineage to the boy at the age of 17. The men in Ahmed’s family have dedicated their lives in the pursuit of Moral Justice. Ahmed began a detailed Genealogy of his male ancestors and was able to trace back his lineage to a general serving in [[Saladin|Saladin&#039;s]] army during the battles of the Crusades. He commissioned an incredible Genealogy scroll of his ancestors that is 4 feet wide and 9 feet tall. It is current displayed on the wall of his quarters aboard the [[USS Rosenante]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
On Stardate 2398.08.12 Ahmed was involved in a near fatal accident. While exploring a recently discovered Egyptian tomb in the [[Valley of the Kings]] with Doctor Sufi Mohammed Sari, a renowned Egyptologist, There was a collapse of a tunnel.&lt;br /&gt;
&lt;br /&gt;
Ahmed was badly injured. He suffered serious trauma in the form of broken bones. It took rescuers thirteen hours to free him from the rubble. As a result of these traumatic times, Ahmed suffers from a mild case of claustrophobia, although he is usually able to fight back the sense of panic that he feels.&lt;br /&gt;
&amp;lt;center&amp;gt;&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
image:Jasmine_Mosatuff_1.jpg|Jasmine Mosatuff in Syria&lt;br /&gt;
image:Salid_Ibn_Jaffar_2.jpg|Salid Ibn Jaffar&lt;br /&gt;
image:Uncle_Aamihr.jpg|Uncle Aamihr&lt;br /&gt;
&amp;lt;/Gallery&amp;gt;&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==University of Cairo==&lt;br /&gt;
&lt;br /&gt;
Ahmed enrolled in the University of Cairo on Stardate 2399.03.06 in the fields of Archeology, Ancient Medicine, and Ancient Engineering. He greatly enjoyed this area of study, but at the insistence of his professors and in messages received from his father, then the Chief Engineer aboard the [[USS Tripoli]], Ahmed finally agreed to take the [[Starfleet]] entry exams.&lt;br /&gt;
&lt;br /&gt;
He graduated with a Masters degree in Archeology from the [[University of Cairo]] on Stardate 2403.03.05.&lt;br /&gt;
&lt;br /&gt;
==Relationships of Note==&lt;br /&gt;
&lt;br /&gt;
[[image:debbie.jpg|thumb|left|&#039;&#039;&#039;Crewman Debbie Weston&#039;&#039;&#039;]][[image:Jasmin_Mohandas_1.jpg|thumb|right| &#039;&#039;&#039;Jasmin Mohandas&#039;&#039;&#039;]]&lt;br /&gt;
&lt;br /&gt;
Salid was involved in a romantic relationship with Engineer Debbie Weston while he was stationed aboard the [[USS Nimitz]] as [[Engineering|Chief Engineer]]. The relationship began to grow somewhat cool after Ahmed&#039;s participation in the Raid on [[Djorn Major XJ-003]]. &lt;br /&gt;
&lt;br /&gt;
The relationship broke up when Ahmed was promoted and assigned to the [[USS Champlain]] as [[First Officer]]. Weston and Ahmed are still friends and are on speaking terms. Ahmed visited the [[USS Hades]] after the end of the Civil War where he spoke once again with Debbie Weston. Debbie was interested in rekindling their relationship, but Ahmed resisted. His concern over maintaining a long distance relationship and his newly acquired interest in [[Jasmin Mohandas]] won out and Ahmed and Debbie agreed to end the romantic aspect of their on-again, off-again relationship.&lt;br /&gt;
&lt;br /&gt;
After the end of the [[Federation Civil War]], Ahmed returned to [[Cairo]] to visit his uncle. He was attacked by an angry mob in the city, as a result of his choice to wear his [[Starfleet]] uniform. He was beaten and struck with stones and lost consciousness. When he recovered he found himself in the home of Jasmin Mohandas. Jasmin had tended his injuries after rescuing him from the mob using a black market [[phaser]]. &lt;br /&gt;
&lt;br /&gt;
During the subsequent discussion, Ahmed discovered that she had been a [[Rank|Lieutenant]] assigned as [[Medical Officer|ACMO]] to the [[USS Pangaea]]. This vessel was a part of the [[Admiral Doenitz|Doenitz]] loyalist force that fought against the [[52nd Fleet]] at the Battle of [[Sector 001]]. Heated words were exchanged and Ahmed was asked to leave.&lt;br /&gt;
[[image:Jasmin_Mohandas_2.jpg|thumb|left| &#039;&#039;&#039;Jasmin Mohandas&#039;&#039;&#039;]]&lt;br /&gt;
&lt;br /&gt;
Several days later, Ahmed saw Jasmin in the local marketplace and apologized. He offered to make her dinner, which she accepted. The meal was terribly cooked, but Ahmed and Jasmin spoke more candidly afterwards and it was then that Ahmed learned that Jasmin was to go before a tribunal for her actions during the battle. After discussing the situation with her, he became convinced that she had done nothing to warrant a Court Martial.&lt;br /&gt;
&lt;br /&gt;
Ahmed spoke to Jasmin&#039;s JAG Officer for the defense and convinced him to allow Salid to speak as a character witness on Jasmin&#039;s behalf. After a hard-sell the counselor agreed and Ahmed was allowed to speak at the Tribunal. He gave an impassioned speech about &#039;&#039;&#039;&#039;&#039;&amp;quot;mercy&amp;quot;&#039;&#039;&#039;&#039;&#039; and &#039;&#039;&#039;&#039;&#039;&amp;quot;healing the wounds of the Federation&amp;quot;&#039;&#039;&#039;&#039;&#039;. It seemed to work, Jasmin was only reduced a single grade as a result of a guilty result of Medical Negligence, while she was found not guilty of the six charges of Murder brought against her.&lt;br /&gt;
&lt;br /&gt;
For several months, while the [[USS Hypatia]] was in Sector 001, Ahmed spent a great deal of time with Yasmin and his uncle Aamihr in Cairo. A young budding romance began between the two and despite the difficulties of a long-distance relationship, is still working.&lt;br /&gt;
&lt;br /&gt;
==[[Starfleet Academy]]==&lt;br /&gt;
&lt;br /&gt;
[[image:Stacademy.jpg|thumb|right|&#039;&#039;&#039;[[Starfleet Academy]], San Francisco, Earth&#039;&#039;&#039;]]&lt;br /&gt;
&lt;br /&gt;
Ahmed took his entry exams on Stardate 2403.06.05, just in time to manage to squeeze into the summer class. Ahmed scored the tenth highest entry exam scores in the history of the [[Starfleet Academy|Academy]], a fact for which he is extremely proud.&lt;br /&gt;
&lt;br /&gt;
He double majored at the Academy in the areas of Materials Engineering/Damage Control and Trauma Medicine. &lt;br /&gt;
&lt;br /&gt;
During his time at the academy, Ahmed joined the [[Boxing|Academy Boxing Team]], [[Sailing|Regatta]] and [[rowing]] teams. He took the Lightweight title for three of the four years that he competed at the Academy. As the captain of the Rowing team, led his crew to victory two years in a row. The Academy Regatta on [[Arctura II]] proved to be another victory for the [[Rank|Cadet]] Salid, as his crew and he took the cup in a ship named the [[Jasmine]].&lt;br /&gt;
&lt;br /&gt;
On stardate 2406.08.02 Ahmed participated in the famed [[Starfleet]] [[Academy Marathon]] on [[Danula II]]. This grueling race saw Ahmed finish 221st out of 693 competitors. While not a clear-cut victory, he was pleased that he managed to finish the 40-kilometer race.&lt;br /&gt;
&lt;br /&gt;
Prior to completing his Course studies at the Academy, Ahmed also took and completed his Bridge Certification Training, Command Staff Training and his Departmental Command Courses. The scored well in each of these additional course, a fact that would assist him later in being selected for the position of [[First Officer]] of the [[USS Champlain]].&lt;br /&gt;
&lt;br /&gt;
Ahmed graduated the Academy Class of 2407 on Stardate 2407.01.22. He ranked second in his class. It was on his graduation day that news arrived of his father’s death aboard the [[USS Tripoli]]. He had sacrificed himself to maintain the containment of the collapsing warp core during the battle of [[Cardassia]].&lt;br /&gt;
&lt;br /&gt;
==Starfleet Career==&lt;br /&gt;
&lt;br /&gt;
[[image:Nimitz.jpg|400px|thumb|right|The USS Nimitz]]&lt;br /&gt;
&lt;br /&gt;
Ahmed was commissioned as an Ensign Junior Grade pursuant to his graduation from Starfleet Academy on Stardate 2407.01.22.&lt;br /&gt;
&lt;br /&gt;
Ahmed was ordered to report to the [[USS Nimitz]], a [[Sovereign Class]] [[Starship]] (Registry NCC-75878-E) captained by Captain [[Devan Sash]].&lt;br /&gt;
&lt;br /&gt;
Ahmed was forced to take a circuitous route to reach the Nimitz due to the Civil War between the Doenitz Loyalists and the [[52nd Fleet]], the latter to which the Nimitz belonged. During his trip he witnessed the oppression of [[Andoria]] first-hand.&lt;br /&gt;
&lt;br /&gt;
He commissioned a respected smuggler and 52nd Fleet loyalist named [[Arkot]], an ex-captain of the Doenitz defeated [[Andorian]] Defense fleet. During his time aboard the Smuggler, he worked in main engineering and repaired an old Romulan cloaking device that was later used to elude a Doenitz loyal Starship.&lt;br /&gt;
&lt;br /&gt;
Ahmed arrived on Starbase [[Geneva]] on Stardate 2407.02.09 nearly a full month after his graduation from the Academy in San Francisco. Once aboard [[Starbase Geneva]] Ahmed wasted no time reporting to the Nimitz.&lt;br /&gt;
&lt;br /&gt;
==Mission One: A Taste of Hate.==&lt;br /&gt;
&lt;br /&gt;
After his arrival on Starbase [[Geneva]], Ahmed was assigned to assist in the investigation concerting an attack on the newly assigned Counselor [[Divon Lronen]]. During the course of the investigation, Ahmed was responsible for finding the weapon used in the assault on the counselor. He was reassigned to the Engineering Department to conduct repairs to the Nimitz as a result of a prior battle.&lt;br /&gt;
&lt;br /&gt;
He reported to Main Engineering and watched in Horror as the current ACEO Lieutenant Miles Davis collapsed after contracting the engineered [[Revelation Virus]] released on Geneva Station by the Terrorist Group [[Humans for Humanity]].&lt;br /&gt;
&lt;br /&gt;
Lieutenant Davis was the first member of the Nimitz crew to succumb to the virus and later died as a result of the illness.&lt;br /&gt;
&lt;br /&gt;
Once it became known what was happening, [[Starbase Geneva]] and the [[USS Nimitz]] were quarantined to prevent further spreading of the virus. The result of the lock-down left Ahmed, newly arrived on the Nimitz as the senior Engineering Officer on the Nimitz, due to Commander Zzt becoming unable to leave the Starbase.&lt;br /&gt;
&lt;br /&gt;
After Hromava, the Nimitz’s First Officer ordered all non-essential personnel to be restricted to quarters, Ahmed and Debbie Weston continued with the repairs to the Nimitz.&lt;br /&gt;
&lt;br /&gt;
Later due to the fact that the virus had been introduced to the crew of the Nimitz, special quarantine areas were established in the ship’s cargo bay, on the orders of the First Officer. It was at this time that Salid discovered an attempt by desperate members of the ship’s crew to escape from the Cargo bay and potentially seize control of the Nimitz. &lt;br /&gt;
&lt;br /&gt;
Ahmed participated in the actions to prevent a mutiny aboard ship.&lt;br /&gt;
&lt;br /&gt;
For his efforts, Captain [[Devan Sash]] promoted him to Ensign Senior grade on Stardate 2407.02.17.&lt;br /&gt;
&lt;br /&gt;
After his promotion Ahmed began a romantic relationship with Engineer Debbie Weston.&lt;br /&gt;
&lt;br /&gt;
==Mission Two: [[Djorn Major Incident|For a Friend]].==&lt;br /&gt;
&lt;br /&gt;
[[Image:VoyagerWarpCore.jpg|thumb|300px|right|Promoted to Chief Engineer]]&lt;br /&gt;
&lt;br /&gt;
On Stardate 2407.03.07 Ahmed was promoted to the position of CEO for the [[USS Nimitz]] by Captain [[Devan Sash]] after it was discovered that Lieutenant Commander Zzt was to be transferred to a Special Theoretical Engineering Unit.&lt;br /&gt;
&lt;br /&gt;
Later that same day, Ahmed would join Captain Sash and several other Nimitz Officers on an unsanctioned mission to Rescue Lieutenant Dru Tagon, a fellow Nimitzer. Tagon had been captured by Doenitz forces and sentenced to be executed. It was discovered that he was being held at [[Djorn Major XJ-003]] to await the completion of his sentence. As the [[52nd Fleet]] was stretched over a wide front in the battle against Deonitz forces, the Admiralty had decided that no vessels could be risked on the rescue. Despite orders to the contrary, Captain sash and several officers made  a rendezvous with the [[IKS Hegh’delar]] a [[Bird-of-Prey|B’rel Class]] scout and entered federation space with the intention of conducting a rescue of Dru Tagon.&lt;br /&gt;
&lt;br /&gt;
Prior to the Arrival at Djorn Major XJ-003, Ahmed spent a considerable amount of effort and time designing material aids to assist in the assault and hopefully give his small team a slight advantage against the station’s garrison. These gadgets included an armored cloaking armored EVA suit, modified from the available Klingon EVA suits, attuned to the IKS Hegh’delar’s [[Cloaking device]]; A series of portable sensor ghost generators, and a mobile handheld command net inderdiction device which later allowed the crew limited access to the station’s main computer systems. Unfortunately despite successful tests of the stealth suits aboard the Hegh’delar, the stealth features seemed to mysteriously fail once aboard the station.&lt;br /&gt;
&lt;br /&gt;
[[image:Horizon.jpg|thumb|300px|left|Djorn Major XJ-003]]&lt;br /&gt;
&lt;br /&gt;
Upon their arrival at Djorn Major XJ-003, The 1st assault team used the [[Ferengi]] assault shuttle the [[Good Deal]] to pass through a gap in the Station’s ventral shields and after An EVA mission to establish a series of transport pattern enhancers, the Crew was aboard the Station.&lt;br /&gt;
&lt;br /&gt;
Ahmed participated in the capture of the Central Computer core of the station in which action he killed a technician.  Later in an attempt to disable the stations shields and weapons, he created a powerful [[plasma]] surge through the tactical systems. The end result was the unexpected explosion of the Station’s Ventral Shield Generator, which was responsible for extensive damage to the station and an unknown number of deaths among station personnel.&lt;br /&gt;
&lt;br /&gt;
Ahmed was injured twice during the mission. Once, he was hit with a [[phaser]] blast in the back fired by station security, which forced him to discard the upper portion of his armored EVA suit. Later he was injured in hand-to-hand combat with a member of Major Julian Wells’ marine unit assigned to guard Lieutenant Tagon. The marine stabbed Ahmed in the lower left arm.&lt;br /&gt;
&lt;br /&gt;
The arrival of the Klingon assault forces from the Hegh’delar led by Doctor [[Jonas Lemar]] allowed the Nimitz crew to reach the Maximum Security Block and force Wells into an honorable ceasefire.&lt;br /&gt;
&lt;br /&gt;
Ahmed and [[Thomas Jackson]] worked together to drop the containment field holding Dru Tagon in his cell. Ahmed also managed to neutralize the explosive collar Tagon wore using the station’s [[transporter]] safety overrides. At Captain [[Devan Sash]]’s order Ahmed transported the assault team to safety, but not before [[Agent Thom Hania|Thom Hania]] had released an explosive grenade which is believed to have killed Major Julian Wells.&lt;br /&gt;
&lt;br /&gt;
The crew escaped Djorn Major and returned to [[Starbase Geneva]] with Lieutenant Tagon. Remarkably, only two members of the rescue effort were killed in action, both were members of the Hegh’delar’s Klingon Marine Contingent led by Doctor Lemar. Later Ensign Thom Hania died under mysterious circumstances prior to the return to the Nimitz. Ensign [[Harry Samuel Doorman]] had survived an apparent attempt at suicide, although later it was discovered that his actions were influenced by the [[Revelation Entity]] affecting Counselor [[Divon Lronen]]. &lt;br /&gt;
&lt;br /&gt;
Surprisingly enough, no member of the Nimitz crew was punished for the undertaking of the unsanctioned rescue of Lieutenant Tagon, Except for Captain Sash.&lt;br /&gt;
&lt;br /&gt;
For his efforts in the rescue of Lieutenant Tagon, Ahmed was promoted to the rank of Lieutenant Junior Grade on Stardate 2407.03.22&lt;br /&gt;
&lt;br /&gt;
==Mission Three: [[To Skin a Cat]].==&lt;br /&gt;
&lt;br /&gt;
On Stardate 2407.03.22 the Nimitz received orders from the Admiralty to conduct a snap raid on [[Cait|Cait Prime (Ferasa)]] with the objective of verifying the existence and destroying a Doenitz research facility believed to be developing biogenetically altered Caitians for use as Super-Soldiers. &lt;br /&gt;
&lt;br /&gt;
The [[USS Nimitz]] arrived in the Ferasa system and was surprised not to find any Doenitz Starships in orbit around the planet.&lt;br /&gt;
&lt;br /&gt;
The away team consisted of the following participants&lt;br /&gt;
[[Rank|Captain]] [[Devan Sash]]&lt;br /&gt;
CTAC [[Eric McDermott]]&lt;br /&gt;
AOPS [[Thomas Jackson]]&lt;br /&gt;
Engineer [[T&#039;Kron]]&lt;br /&gt;
Ensign Leesa Stanton&lt;br /&gt;
COUNS [[Cecilia Bruce]]&lt;br /&gt;
&lt;br /&gt;
As well as several junior members of the security, Science and Engineering departments of the Nimitz.&lt;br /&gt;
&lt;br /&gt;
Upon Arrival on the planet, The Nimitz team Linked up with members of the CLF (Caitian Liberation Front) led by an adolescent Caitian named R&#039;Aul. They also made contact with R&#039;Serrott and [[Shayhiloosh]], both of which were involved in some manner with the facility that the Nimitz crew was sent to destroy.&lt;br /&gt;
&lt;br /&gt;
[[image:Nilas III.jpg|thumb|500px|right|The USS Nimitz at Cait Prime (Ferasa)]]&lt;br /&gt;
&lt;br /&gt;
The crew spent the night with their new found allies in the Caitian Village of [[Chtarr]], where Ahmed participated in a complex and semi-violent game of [[Sarhket]], which is used in some rural areas to resolve disagreements. The game turned out to be a test of the Nimitz crew&#039;s resolve to aid the [[Caitian]]s in their struggle for liberation. Although Salid did not win, he earned the respect of the local CLF members and was accepted among them as a friend.&lt;br /&gt;
&lt;br /&gt;
The following morning the away team, bolstered by their new additions in R&#039;Serrott and Shayhiloosh and accompanied by A&#039;Rul and members of the CLF, marched to and raided an automated train depot that would allow them covert entry to the Capital City of [[Knassis]], only 30 miles away. The raid on the train depot went smoothly without incident.&lt;br /&gt;
&lt;br /&gt;
Once the train depot had been secured, The Nimitz away team hid themselves aboard the supply train and rode the conveyance to their target area. The train was stopped by members of the Local Militia when it was discovered that a trap had been set for the Nimitz team. As a result, The team was instead forced to hike into the target area undetected and assault the underground complex where [[Admiral Doenitz|Doenitz loyalists]] were conducting illegal biogenetic and telepahic manipulation.&lt;br /&gt;
&lt;br /&gt;
Once inside, the team split into two assault groups; one  led by [[Rank|Lieutenant]] Salid and the other by Captain Sash. &lt;br /&gt;
&lt;br /&gt;
The team led by Sash seized the facilities [[transporter]]s and assaulted the telepathic research facilities, While the second team under Lieutenant Salid assaulted the genetics labs and holding cells. Ahmed&#039;s group met light resistance and was able, with the help of Lieutenant Prothal, to destroy the research facilities beyond repair.&lt;br /&gt;
&lt;br /&gt;
Meanwhile, Captain Sash&#039;s team came under attack by facility security and were pinned down in a terrible crossfire. Salid&#039;s team arrived in time to relieve the captain&#039;s team and the two teams then led the assault against the primary telepathic holding facility.&lt;br /&gt;
&lt;br /&gt;
During the assault on that facility, The away team came under psychic attack, that caused some of their number to turn on their allies.  Salid and several other officers managed to fight their way out of the control of the being designated, Patient [[Delta-Seven-Nine|Delta-Seven-Nine (Δ79)]]. Δ79 killed his controller and then died of injuries inflicted upon him by the combined telepathic attacks of [[Cecilia Bruce]] and [[Eric McDermott]].&lt;br /&gt;
&lt;br /&gt;
Once the telepathic research facilities were neutralized, Sash led the remainder of his team and the rescued test subjects from the facility to the city above. &lt;br /&gt;
&lt;br /&gt;
When the word spread that there were Caitains in revolt, the entire [[planet]] rose up and threw off the yoke of the Doenitz Regime.&lt;br /&gt;
&lt;br /&gt;
For his efforts, Ahmed was awarded the Combat Action Ribbon. He was promoted to [[Rank|Lieutenant Commander]] on Stardate 2407.03.29, when it was also announced that he had been selected as [[First Officer]] of the [[USS Champlain]].&lt;br /&gt;
&lt;br /&gt;
== Mission Four: Crossroads ==&lt;br /&gt;
&lt;br /&gt;
[[Image:USSChamplainD.jpg|450px|thumb|right|USS Champlain]]&lt;br /&gt;
After the completion of the mission on Cait Prime, Ahmed was promoted to the Rank of Lieutenant Commander and assigned to the [[USS Champlain]], NCC 2170-C, A [[Galaxy Class]] variant. He reported to [[Starbase Geneva|Geneva Station]] to Captain [[Susan Rivers]], who had also just assumed command of the Champlain after the death of her Captain Edward Wolfe in a battle with the [[USS Wyvern]]. He assumed this position officially on Stardate 2407.04.02, despite the fact that the Champlain had not yet arrived at the Station as she was damaged during the battle. The Champlain was Commanded by [[Rank|Lieutenant]] Bree Frazier during the engagement with the [[USS Wyvern]], which resulted in the enemy vessel&#039;s capture thanks in no small part to the efforts of Lieutenant James Alexander and Lieutenant Jono Janeway.&lt;br /&gt;
&lt;br /&gt;
Captain Rivers advised Lieutenant Commander Salid of the impending assignment of the Champlain to participate in the final push of the [[Federation Civil War]] against [[Admiral Doenitz]] in an amassed attack on [[Sector 001]]. He was assigned to arrange drills and additional training for the crew while the ship remained in dock undergoing repairs.&lt;br /&gt;
&lt;br /&gt;
==Mission Five: [[Do Not Go Gently]]==&lt;br /&gt;
[[Image:Task Force 19 -2.jpg|thumb|300px|right| Task Force 19, of the 52nd Fleet, assembling in preparation to attack Sector 001]]&lt;br /&gt;
&lt;br /&gt;
On stardate 2407.06.25 Ahmed was advised by Captain Susan Rivers that they had finally received their orders to join the remainder of [[Task Force 19]] assembling at [[Tellar]]. The Champlain had been completely overhauled and the ship and her crew were as ready as they could possibly be for the final battle against Doenitz forces guarding sector 001&lt;br /&gt;
&lt;br /&gt;
On Stardate: 2407.07.03 Ahmed and the entire Command Staff of the USS Champlain were briefed on the plans to Attack Sector 001 and [[Earth]] in a final bid to bring an end to the bloody and tenacious Federation Civil War. This [[Task Force Nineteen Briefing|Briefing]] was conducted by Rear Admiral Sevant, Former captain of the [[USS Boudicca]] and the Task Force Commander of [[Task Force 19]], ordered to breach the famous [[Mars Defense Perimeter]] designed to hold of a [[Borg]] Invasion.&lt;br /&gt;
&lt;br /&gt;
Even as the crew of the Champlain begin gearing for the coming battle, Hundreds of [[Starship|ships]] were converging at Tellar in preparation for the massive offensive.&lt;br /&gt;
&lt;br /&gt;
The assignment given to the Champlain was simple in concept but exceptionally complex in practice. The task force was broken into four smaller battle groups and the remaining bulk of the taskforce, consisting of the [[USS Boudicca]] (commanding group B), the [[USS Champlain]] (commanding group C), the [[USS Nimitz]] (commanding Group A), The [[USS Hades]] (commanding group D). The Boudicca was tasked to breach the MDF and assault and capture [[Starbase Valhalla]] in an attempt to shut down the MDF and allow the remainder of Task Force 19 to bypass the MDF without further losses. The USS Champlain, Hades, and Nimitz were ordered to support the operation of the Boudicca, with the Champlain being specifically tasked with screening the Boudicca and her Battlegroup from enemy raiders.&lt;br /&gt;
&lt;br /&gt;
The basic flow of the battle is listed here:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;toc colour&amp;quot; style=&amp;quot;margin: 0 0 1em 1em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;Stardate: 2407.07.05&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1410 HRS&amp;lt;/font&amp;gt;: The order to &amp;quot;Cross the River Acheron&amp;quot; is given by Admiral Sevant, the [[Commanding Officer]] of Task Force 19. Lead elements of the taskforce begin their journey to [[sector 001]] and the final engagement of the civil war.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1414 HRS: Captain Rivers Orders the USS Champlain and Battle Group C to set course for Sector 001.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1415 HRS&amp;lt;/font&amp;gt;:  Battlegroup Theta commanded by  Captain Sarah Smithers orders her specialized assault group underway.&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;Stardate: 2407.07.09&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1328 HRS&amp;lt;/font&amp;gt;: The [[USS Champlain]] and her accompanying battlegroup drop out of warp and steam towards the MDF. Battle Group A consisting of 20 ships, 4 of which are [[Klingon]] [[Negh&#039;Var Class]] vessels, break formation and begin assaulting the MDF at long range. &lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1400 HRS&amp;lt;/font&amp;gt;: The enemy sends out skirmishing vessels to harass battlegroup A with mixed results.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1407 HRS&amp;lt;/font&amp;gt;: The [[USS Boudicca]] begins her run towards the MDF&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1410 HRS&amp;lt;/font&amp;gt;: Battlegroup Laredo (D) attacks the USS Champlain and her associated Battle Group. The raiders uncloak, fire a volley of modified torpedoes into the flank of the C-Group then make a strafing run. Both sides take casualties. The C-Group falls back from B-Group to protect the latter&#039;s flanks from attack.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1415 HRS&amp;lt;/font&amp;gt;: The [[USS Hades]] and [[USS Nimitz]] reach [[Sector 001]]. The Hades goes into Tri-Vector Assault mode.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1417 HRS&amp;lt;/font&amp;gt;: Group Theta arrives at Sector 001 and begins their assault on a weapons repository located just inside the MDF.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1418 HRS&amp;lt;/font&amp;gt;: Battle Group D engage enemy fighters and their support ships.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1425 HRS&amp;lt;/font&amp;gt;: Battle group Laredo makes a second attack run against C-Group then retreats from the battlefield behind the protection of the MDF&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1449 HRS&amp;lt;/font&amp;gt;: The USS Boudicca and her Battlegroup make contact with the MDF.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1455 HRS&amp;lt;/font&amp;gt;: The [[USS Spectre]] arrives in sector 001 with a [[Klingon]] Task force and a group of Ex-Doenitz ships that have defected to the [[52nd Fleet]].&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1750 HRS&amp;lt;/font&amp;gt;: The USS Boudicca and her battle group finally break through the MDF.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1755 HRS&amp;lt;/font&amp;gt;: The USS Champlain and the remnants of Battle Group C breach the MDF while being pursued by the [[USS Majesty]] and her Battle group (D)&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1800 HRS&amp;lt;/font&amp;gt;: Captain Rivers orders Battle group C to form a battle line behind  Battlegroup B to guard the Boudicca&#039;s rear flank. The C-Group turns about 180-degrees and forms a battle line to handle the Majesty and her battle group.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1815 HRS&amp;lt;/font&amp;gt;: The USS Majesty and her battlegroup form a wedge formation to better split through the battle line established by Captain Susan Rivers and the remnants of Battlegroup-C.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1820 HRS&amp;lt;/font&amp;gt;: The two battle groups led by the USS Majesty and the USS Champlain clash. The battle formations are broken and the battle devolves into complete chaos for the two battle groups.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1822 HRS&amp;lt;/font&amp;gt;: After taking fire from Negh&#039;Vars of Battlegroup-A, [[Uru Mtenga]] orders the [[USS Hercules]] and the [[USS Persephone]] to split off from the rest of his battlegroup and deal with the Klingon ships. They destroy all three remaining Ngh&#039;Vars and return to the battle with the Champlain.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1825 HRS&amp;lt;/font&amp;gt;: The [[USS Dennison]] and a small battle group arrive at Sector 001 to aid Task Force 19.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1830 HRS&amp;lt;/font&amp;gt;: The USS Boudicca realizes that they are facing the Black Watch led by Admiral Lydia Stakes as well as elements of the 53rd Heavy Assault Fleet. Captain Archibald Stakes appeals to the morality of the enemy battle group and the majority of the Night watch and the 53rd Heavy defect or stand aside. Those resisting are engaged and subdued by the remainder of Battlegroup-B.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1900 HRS&amp;lt;/font&amp;gt;: The USS Nimitz is destroyed in battle when she rams an enemy ship during a warp core breach. Several members of her crew managed to abandon ship just prior to her destruction.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1907 HRS&amp;lt;/font&amp;gt;: The battle between the Majesty and Champlain Battle groups has depleted both sides resources significantly. The [[USS Hypatia]] from the Black Watch joins the battle. Her captain convinces Captain M&#039;tega that they are still loyal to [[Admiral Doenitz]], then ambushes their former ally. The Majesty is crippled, giving the heavily damaged Champlain a short respite.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1910 HRS&amp;lt;/font&amp;gt;: The [[USS Dennison]] joins the [[USS Hades]] as a defensive screening force while the Hades reintegrates from Tri-Vector mode and begins rescue operations of the surviving Nimitz Crew.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1911 HRS&amp;lt;/font&amp;gt;: The Champlain engages the enemy [[Prometheus Class]] starship, [[USS Persephone]]. The Champlain loses her dorsal nacelle and an unstoppable warp core breach begins. Once Rivers realizes the ship is lost, she orders the abandon ship. The Persephone begins firing on the life boats from the Champlain.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1920 HRS&amp;lt;/font&amp;gt;: The USS Boudicca, press their shields against those of [[Starbase Valhalla]]. This action causes severe damage to the [[Keltoi Class]] ship, but causes the Stations dorsal shields to fail. Stakes orders the abandon ship and the crew of the Boudicca use transporters or life pods to get aboard Valhalla following the Marine assault ships.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1922 HRS&amp;lt;/font&amp;gt;: Several senior officers &amp;quot;volunteer&amp;quot; to stay aboard while the Champlain is guided towards her enemy like a massive missile. &lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1930 HRS&amp;lt;/font&amp;gt;: In an attempt to give their comrades time to get clear of the Persephone&#039;s violent onslaught, the [[USS Wyvern]] draws the larger vessel away from the dying Champlain. The Wyvern is knocked out of commission and all her crew killed.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;1949 HRS&amp;lt;/font&amp;gt;: The USS Champlain manned only by a handful of volunteers use the [[Galaxy Class]] vessel to ram the [[USS Persephone]]. Both ships are completely destroyed. The skeleton crew on the Champlain is rescued by the [[USS Hypatia]].&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;2055 HRS&amp;lt;/font&amp;gt;: The rest of [[Task Force 19]] is ordered to go &amp;quot;To Earth!&amp;quot; The offensive for the planet itself begins in earnest. [[Starbase Valhalla]] is secured by the [[52nd Fleet]].&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;Stardate: 2407.07.09&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;0127 HRS&amp;lt;/font&amp;gt;: The [[USS Dennison]] and her support ships destroy the [[USS Caesar Regnum]]&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;0130 HRS&amp;lt;/font&amp;gt;: Reports surface that ex-president and dictator Rodrigo Doenitz is captured by Resistance forces in Geneva Switzerland.&lt;br /&gt;
**&amp;lt;font color=goldenrod&amp;gt;0205 HRS&amp;lt;/font&amp;gt;: The former president of the [[United Federation of Planets]] is restored and the Civil War and the Battle for [[sector 001|Sector 001]] is finally ended.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Mission Six: [[Picking up the Pieces]].==&lt;br /&gt;
&lt;br /&gt;
[[Image: Rose Beauty2.jpg|thumb|450px|right|The USS Rosenante NCC-924650]]&lt;br /&gt;
With the civil war over and the Champlain lost, Ahmed was assigned as Acting [[First Officer]] of the [[USS Hypatia]] under the command of Acting Captain [[Susan Rivers]].&lt;br /&gt;
&lt;br /&gt;
The Hypatia underwent repairs and participated in some limited recovery work inside the [[Sol|Sol System]].&lt;br /&gt;
&lt;br /&gt;
Salid visited his uncle in [[Cairo]], where he met [[Jasmin Mohandas]]. An ex-ACMO from the [[USS Pangaea]] (a Doenitz ship from the 1st Fleet) when she saved him from a mob that attacked him because he was wearing his [[Starfleet]] uniform. Ahmed discovered that his uncle had been interred and had suffered torture at the hand of Doenitz fundamentalists as a result of his nephew&#039;s involvement with the Sedition.&lt;br /&gt;
&lt;br /&gt;
Ahmed spoke at a tribunal hearing for Lieutenant Mohandas, urging the tribunal to exercise mercy. Miss Mohandas was found innocent of all charges of murder during the battle, but was found guilty of Medical Negligence. She lost one grade in rank as a result.&lt;br /&gt;
&lt;br /&gt;
Ahmed reconciled with his uncle after the two men had an argument about his potential resignation from Starfleet to attend to his uncle&#039;s health needs. &lt;br /&gt;
&lt;br /&gt;
Salid visited his ex-shipmates from the Nimitz who had been reassigned to the [[USS Hades]]. There he and Debbie Weston spoke about the future of their past relationship and about the loss of the [[USS Nimitz]].&lt;br /&gt;
&lt;br /&gt;
After a crushing declaration by Commander Josel, Chief of Personnel for [[Sector 001]] that Ahmed was not qualified to serve in the capacity of First Officer; he was assigned to the Engineering operations Officers aboard [[Starbase Valhalla]] on Stardate 2408.01.04. This assignment did not last for long, however. Captain Susan Rivers acting on the authority of [[Rank|Admiral]] Linden, ordered Ahmed reassigned to the [[USS Rosenante]], as her First officer.&lt;br /&gt;
&lt;br /&gt;
Ahmed and Captain Rivers beamed aboard the Rosenante on stardate 2408.01.06 to assume command from the Acting CO Commander Ian MacBeth.&lt;br /&gt;
&lt;br /&gt;
== Mission Seven: [[A Fine and Private Place]]==&lt;br /&gt;
[[Image:Extrasolar-Binary.jpg|thumb|250px|right|Davros III]]&lt;br /&gt;
&lt;br /&gt;
The [[USS Rosenante]] passed her space worthiness trials without a glitch and was assigned their very first mission, to survey planets for recolonization of the survivors of the [[Colony]] of [[Ivor Prime]]. The Rosenante took on the administrator of the colony and set off for the [[Optima VII|Optima System]] in hopes of finding a planet suitable for the colonists. The Rosenante departed for her official maiden Voyage on Stardate 2408.01.15. The Ceremony was officiated by [[Rank|Admiral]] Hesper Linden.&lt;br /&gt;
&lt;br /&gt;
On Stardate 2408.01.21  the Rosenante received a disturbing [[Sky of Tomorrow Distress Call|distress signal]] from the Federation freighter the &#039;&#039;&#039;[[Sky of Tomorrow]].&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Third Officer, Olen Rhinehardt altered course and alerted the captain and crew to the situation. The Sky of Tomorrow&#039;s signal was traced to the orbit of [[Davros III]], A [[Federation]] Mining [[Colony]].&lt;br /&gt;
&lt;br /&gt;
The Rosenante arrived at the scene only three hours later. Attempts to hail the freighter were not successful. An away team was beamed aboard and to their horror uncovered signs of a violent and bloody conflict. They also encountered an animated dismembered hand. This hand was quarantined and studied upon the return of the away team to the Rosenante, where it was discovered that the hand was infested with a nanite colony derived from [[Borg]] [[nanoprobe]]s.&lt;br /&gt;
&lt;br /&gt;
Ahmed led an away team down to the planet&#039;s surface to search for survivors, when he returned to the Rosenante without three of his security team, Ahmed offered this summary to the Captain:&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;sup&amp;gt;&amp;lt;font color=goldenrod&amp;gt;&lt;br /&gt;
:&#039;&#039;Ahmed followed the Captain into the ready room.  As always the Captain was incredibly calm, ~But then again,~ Ahmed reminded himself, ~she hadn&#039;t just been chased by an indeterminable number of corpses animated by Borg nanites… Or something like that~&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Sit down, Ahmed,&amp;quot; she said, and headed for the replicator. Without asking, she ordered two cups of Ahmed&#039;s special Turkish coffee and a plate of pastries. She sat them down on the table between them and said. &amp;quot;You can talk as you eat,&amp;quot; she ordered, sliding the plate a little closer to him. &amp;quot;I can tell by your face it&#039;s not good news, so let&#039;s hear it. What did you find down there?&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;It&#039;s hard to be clear, so bear with me.&amp;quot; Ahmed said as he added a little goat&#039;s milk to his coffee and took a sip. &amp;quot;When we arrived in the town square, everything was quiet. It was just like one of those wild west ghost towns that you read about in the history books.  All it was missing was the tumble weed.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;We located the residence of doctor Lawson and there we found what appeared to the remains of a lab. It was very obvious that some of the equipment had been moved elsewhere. From that lab there were two almost parallel tunnels leading downward toward the mine. As you know that was when I ordered Lieutenant Janeway, chief fuller and a second security team down to the planet. The idea was that the two teams could each explore one of the tunnels and possibly locate any survivors or clues faster.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;He picked up one of the pastries and took a bite. The orange marmalade was exceptionally good and Ahmed then realized how hungry he really was. He took a sip of his coffee to wash it down.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;We searched for several hours without any sign at all of the miners. For a while there, I was even beginning to wonder if all 1500 of them had somehow managed to leave the planet. We came to a junction and heard what I could only describe as weapons fire. I ordered the team down the tunnel to the source as quickly as possible which opened into a cavern.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;When we arrived, there was an… individual there, a member of the Opthidian species, who was defending himself from some of the miners. It was apparent that he had killed at least ten or twelve of them already. We announced ourselves and ordered the fighting to stop, but instead of being attacked by the visitor as I had originally expected to be, it was the miner&#039;s that attacked us.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Heavy stun doesn&#039;t have much affect on them. Even the kill setting isn&#039;t very effective.  We lost Abernathy in that fight. He was infected by some sort of black ooze, which we were later informed was a nanite colony.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;The Opthidian&#039;s name is Sharott Nachook and he explained a great deal to us concerning what was happening on that colony.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;Ahmed ate some more of his pastry and drank a little more of his coffee. &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;His people encountered the Borg roughly 500 standard years ago. Apparently their physiology doesn&#039;t allow them to be assimilated by Borg Technology. They fought a war and in the end the [[Borg]] left them alone. The Opthidian scientists had dissected several Borg drones during the war and had discovered a way to modify the Borg nanoprobes for their own medical uses. This continued for some time until eventually, the Borg nanoprobes developed some sort of colony-like hive mind and became self-aware. They began to dominate living members of the Opthidian species against their will and when the realization struck, the Opthidian government tried to destroy the nanites.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;The nanites adapted again in a very grotesque manner. They began killing their hosts and maintaining the bodies after death until they were no longer viable. The [[Opthidian]] homeworld had to be biologically sterilized to prevent them from spreading. From what I can gather eventually the Opthidians captured the original colony which they refer to as the matriarch and imprisoned it pending it&#039;s destruction.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Now here&#039;s where the details get a bit sketchy.&amp;quot; Ahmed said then took another sip of his coffee. &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;At some point in the recent past, the Ferengi somehow managed to steal this imprisoned nanite colony and transport it here, where it is believed they sold it to Doctor Lawson. The good doctor is an expert on Borg nanotechnology and was living here with her young daughter, who was very ill with an incurable ailment according to Doctor Caskie&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;We can surmise that Lawson conducted some experiments, maybe even infecting her daughter either with the knowledge that these nanites were self-aware or in ignorance. Regardless of what she knew, that seems the most logical means that this infection was spread. From there, the nanites took over members of the community exponentially until every member was a member of the colony.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Mister Nachook&#039;s people tracked the Ferengi here. They claim to have destroyed the Ferengi ship and admit to attacking Mister Raschen&#039;s ship in an attempt to maintain some semblance of quarantine. It seems that after their losses in the battle, they withdrew, possibly to conduct repairs when we arrived in the system.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;They had dropped Nachook and perhaps a couple of others on the planet with the mission to find and destroy the nanite breeding pool, where apparently the matriarch lives. Mister Nachook claims that destroying her will result in the demise of all her immediate offspring as they are dependant on her for their cognitive abilities.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Just shortly after all this data was given by Nachook, Jono shows up with what is left of Beta team. He was injured and we gathered that they were surrounded and attacked by a large mass of infected miners. They lost Milano during their escape.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;Nachook advised Caskie at that time that  he carries some sort of viral weapon in his body that will wipe out the entire biosphere of the planet and make it uninhabitable for roughly 200 standard years. He is confident that the weapon will kill all the nanites present by depriving them of biological hosts and will kill anyone that should set foot there as well and prevent the nanites from managing to get off world.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;Ahmed finished his coffee and sat it on the table. &amp;quot;The catch is that Nachook was injured and some sort of biological process has started that will result in his death and the release of the virus in an uncertain amount of time. Doctor Caskie is confident that she can extract the virus, saving Nachook and that the virus can them be delivered to the planet via modified Photon torpedo, where it will destroy the biosphere and end the threat of it spreading from this planet.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;We had to fight our way out of those tunnels. We lost Hezan there. I vaporized him myself.&amp;quot; &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;Ahmed looked into River&#039;s eyes, before continuing. &amp;quot;I&#039;ve seen a lot of terrible things Captain, but I can not describe to you the sheer terror and fear that these things inspire. I am not a blood thirsty person, but these things need to be eradicated with all due prejudice.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;That said it was my assessment, after my experience on the planet, that these nanites should be treated like a biological outbreak and should be eradicated before they place millions or even billions more at risk. I have ordered Caskie to proceed with her plan after she assured me that she could prevent it from spreading across the ship should there be a mishap. I believe that we have no recourse and that we should treat these nanites as we would Borg. There is no hope of negotiation and that any encounter will result in the supplantation of one species over the other at the complete eradication of the prior.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&amp;quot;To carry through with this, I furthermore, recommend that we transport the nanite-filled hand back to the Sky of Tomorrow and that we undertake steps to destroy it and the freighter as well.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/font&amp;gt;&amp;lt;/sup&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Captain Rivers agreed with Salid&#039;s assessment and ordered the plan carried out. At 2045 hours the orders were given to deploy the viral torpedo and the planet of [[Davros III]] was sterilized. The freighter was destroyed shortly thereafter and Mister Nachook was returned to his ship. &lt;br /&gt;
&lt;br /&gt;
The Rosenante seeded five quarantine probes around the planet before departing to complete their original mission.&lt;br /&gt;
&lt;br /&gt;
On Stardate: 2408.01.25 Captain Rivers was ordered to Starbase Geneva to give evidence for a war crimes tribunal. She was advised that she would not be returning to the command of the Rosenante and Commander Salid was promoted to the rank of Captain and given command of the USS Rosenante.&lt;br /&gt;
&lt;br /&gt;
== Mission Eight: [[Letters of Marques]]==&lt;br /&gt;
&lt;br /&gt;
After the transfer of captain Rivers to the Boudicca, Ahmed is promoted to captain of the Rosenante. &lt;br /&gt;
[[Image:APPLANET.jpg|thumb|250px|right|Arturia Prime]]&lt;br /&gt;
&lt;br /&gt;
It turns out that his first test as captain will place his ship and crew well outside the boundaries of Federation Space.&lt;br /&gt;
&lt;br /&gt;
The Mission began with a communication from Admiral Talbot of Starfleet intelligence.&lt;br /&gt;
&lt;br /&gt;
Prince [[Angor Khamal|Khamal]], the hereditary leader of the Meldovian people had been kidnapped on the eave of a peace treaty that would bring an end to a 400 year old war between the Meldovian and Arturian factions (both of the [[Cartenian]] race).&lt;br /&gt;
&lt;br /&gt;
While traveling to [[Arturia Prime]] from [[Meldovia III]] to conclude the peace treaty, Orion pirates and slavers attacked the Prince&#039;s convoy and took the Prince and many other Meldovians prisoner.&lt;br /&gt;
&lt;br /&gt;
At the request of the [[Vulcan]] Arbiter T&#039;Val, Admiral Talbot assigned the [[USS Rosenante]] to the task of locating and recovering the Prince before the peace negotiations fail.&lt;br /&gt;
&lt;br /&gt;
Salid was ordered to rendezvous with the Arbiter and take on an Arturian, Meldovian and the Vulcan delegations. He is then ordered to proceed into [[Orion]] space and locate and rescue the Prince.&lt;br /&gt;
&lt;br /&gt;
Using their untried cloaking system, the HISS system, the Rosenante slipped into Orion Space to begin their investigation at the heart of the [[Orion Syndicate]]&#039;s notorious slave markets on [[Barakos IV]].&lt;br /&gt;
&lt;br /&gt;
Three away teams are sent to the surface to procure supplies, search for clues to the Prince and gather intelligence.&lt;br /&gt;
&lt;br /&gt;
One of the away teams is tasked with the acquisition of a Orion style shuttle craft to be used in future phases of the mission. This team consisting of the first officer, Janeway, Lt. Dralar, and the CEO Lt. Paul Bird succeed in their mission, but not before Lt. Bird is killed in a senseless brawl by an individual using a poisoned blade.&lt;br /&gt;
&lt;br /&gt;
Bird is transported back to the ship, but the poison works quickly and he is not able to be revived.&lt;br /&gt;
&lt;br /&gt;
The second away team, consisting of Lt. Ro&#039;Dal, Ensign Weaver, PFC Nunez and Lt. Caskie, and Ensign T&#039;Kron search for Meldovians among the slave pens of the market. they are successful in rescuing three Meldovians and a Half-Orion/Half-[[Betazoid]] woman named Sodra, who claims to have information concerning the whereabouts of the prince.&lt;br /&gt;
&lt;br /&gt;
Sodra turns out to have no information at all, instead using her telepathic powers to pluck a few relative pieces of information from Weaver. However, she has done no harm and is restricted to quarters until such time as her disposition can be determined.&lt;br /&gt;
&lt;br /&gt;
Ro&#039;Dal and Caskie do recover three Meldovians with the aid of a new ally, Nodel, who is an amthropoid, a species not yet discovered by the UFP. Their new ally leads them directly to the last three Meldovian slaves in the marketplace.&lt;br /&gt;
&lt;br /&gt;
[[Image:Slave Market on Barakos IV.jpg|thumb|250px|right|The Slave Market on Barakos IV]]&lt;br /&gt;
&lt;br /&gt;
The third away team, consisting of Lt. Sullivan, Ensign [[Chance Raschen]], and Chief Sheridan make contact with Raschen&#039;s grandfather, a reputed Bounty hunter by the name of &amp;quot;Easy Ed&amp;quot; Raschen. They get a solid lead on whom may have the prince, an slaver named O&#039;Banyan at [[Xanadu Gothos]].&lt;br /&gt;
&lt;br /&gt;
Once all three teams have returned to the ship, the senior staff question those that were brought aboard at [[Barakos IV]].&lt;br /&gt;
&lt;br /&gt;
It rapidly becomes apparent that there was a spy within the Prince&#039;s circle of advisors, and that information, coupled with the discovery of an encrypted message into Orion space originating from the Rosenante, led to speculation that there was now an enemy spy aboard the Rosenante as well.&lt;br /&gt;
&lt;br /&gt;
Maddox and Weaver were given the task to decrypt the message in the hopes of discovering it&#039;s origins.&lt;br /&gt;
&lt;br /&gt;
With information acquired from Nodel it is determined that there was a Meldovian of some importance shipped to [[Haldor II]]. While it is unknown if this is the Prince, it is worth investigating and so the Captain orders course set and the Rosenante underway to the Haldor system.&lt;br /&gt;
&lt;br /&gt;
[[Image:Morella.jpg|thumb|left|[[Morella]] Pirate Queen]]&lt;br /&gt;
&lt;br /&gt;
En route, the Holographic marine Program, Ramirez, suddenly activates and attempts to assassinate the Captain and several other key members of the ship&#039;s senior staff.&lt;br /&gt;
&lt;br /&gt;
Chaos ensues as the crew struggle to regain control of the ship&#039;s computers and disable the hologram from operating. It quickly becomes apparent that the saboteur is responsible.&lt;br /&gt;
&lt;br /&gt;
Meanwhile Nodel confides in Ro&#039;Dal that he has heard the voice of a slaver on the ship. This voice he insists is the exact same voice that he heard near the Meldovian cells on [[Barakos IV]].&lt;br /&gt;
&lt;br /&gt;
Nodel and Ro&#039;Dal hatch a plan to potentially identify their would-be slaver and set the plan into action.&lt;br /&gt;
&lt;br /&gt;
With several of the ship&#039;s systems off-line, as a result of Ensign Weavers attempt to stop the holographic marine by disengaging the Cochrane Accelerator field in the main computer and then physically destroying the holographic buses with a hand phaser, the Rosenante takes refuge inside an asteroid belt to avoid detection while the stealth systems and other ship&#039;s critical systems are repaired.&lt;br /&gt;
&lt;br /&gt;
Once those repairs are completed, the ship continues on to [[Haldor II]], where their sensors detect the presence of a living facility protected by an environmental shield.&lt;br /&gt;
&lt;br /&gt;
With no ships in the immediate vicinity, Ahmed orders the ship into a geosynchronous orbit and tasks Lt. Sullivan, Ensign Weaver, lieutenant [[Steven Wade Matrix]] and Lieutenant [[Jennifer Caskie]] to accompany a security team to the surface with the intentions of rescuing the single Meldovian life-sign found on the planet.&lt;br /&gt;
&lt;br /&gt;
After recovering the Meldovian from the planet [[Haldor II]], it became quickly apparent that the individual that they had acquired was a traitorous captain who had been responsible for the ease of the Prince&#039;s kidnapping.&lt;br /&gt;
&lt;br /&gt;
Having no other choice the captain ordered the new prisoner interrogated and the Rosenante to set course for [[Torven III]]. The only other lead that they had to the possible whereabouts of the Prince&#039;s location.&lt;br /&gt;
&lt;br /&gt;
Once arriving in the Torven System, Salid opened negotiations with the trader [[Doyle &#039;Dogface&#039; O&#039;Banyan|Doyle O&#039;Banyan]], An [[Starfleet Marine Corps|ex-marine]] turned smuggler and slave trader. In return for a promise to aid in his rehabilitation, Salid agrees to accept O&#039;Banyan&#039;s assistance in recovering the prince. The Trader had already secretly sent an assault group against Morella in the hopes that they could acquire the Prince.&lt;br /&gt;
&lt;br /&gt;
Surprisingly, the assault works and the Prince as well as O&#039;Banyan&#039;s missing daughter is recovered, allowing the Rosenante to return back to [[Federation]] Space in time to guarantee the successful signing of the Peace between the Meldovian and Arturians and the formal formation of the Cartenian Commonwealth.&lt;br /&gt;
&lt;br /&gt;
Thier mission completed, the Rosenante heads to [[Starbase Geneva]] for some R&amp;amp;R and After action inspections.&lt;br /&gt;
&lt;br /&gt;
== Mission Nine: [[Furlough]]==&lt;br /&gt;
&lt;br /&gt;
The crew of the Rosenante is granted Furlough, while critical inspections concerning the Spiral drive are undertaken.  Captain Salid is forced to demote Lieutenant Janeway by BUPERS from the position of first officer and is assigned a newly promoted Lieutenant Commander Caskie to the position. &lt;br /&gt;
&lt;br /&gt;
The Rosenante also takes on some new senior Crew. Ahmed is reunited with [[Thomas Jackson]] with whom he served aboard the [[USS Nimitz]], in the position of Chief of Operations. Additionally the arrival of Lieutenant Nayati to fill the position of Chief Counselor and third Officer is a welcomed event.&lt;br /&gt;
&lt;br /&gt;
In other news, Salid is saddened by the transfer of Lieutenant Ro&#039;Dal who has been reassigned to the [[USS Mithrandir]].&lt;br /&gt;
&lt;br /&gt;
The Captain and his new FO go for a holographic sailing trip on the Mediterranean in a get to know you cruise, and Salid approves Sullivan&#039;s departure for the Advanced Tactical Theories Academy on [[Andoria]].&lt;br /&gt;
&lt;br /&gt;
== Mission Ten: [[Fields of Elysium]]==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Part I: The Mission&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
In Mid 2408 the [[USS Rosenante]] was assigned to explore a newly discovered region of space that exited from the Tau Sigma Flow of the Subspace River. This region had been discovered by an unmanned survey probe and opened into the [[Beltanis Stellar Nursery]].&lt;br /&gt;
&lt;br /&gt;
When the Rosenante arrived, the captain decided to move into the nebula in the hopes of exploring an undocumented phenomenon. This phenomenon turned out to be an exceptionally rare event known as a [[Subspace Bubble]]. Unfortunately, the bubble burst slamming the vessel with a Class Six [[Graviton|Gravimetric Wave]].&lt;br /&gt;
&lt;br /&gt;
The Rosenante was terribly damaged; suffering irreparable damage to the ship&#039;s Main Deflector Array and Power distribution network. With the ship&#039;s shields failing, the vessel hurriedly returned to the safe-zone at the terminus of the Subspace river.&lt;br /&gt;
&lt;br /&gt;
After a couple of days of assessment and around-the-clock repairs, it was determined that the Rosenante would not be able to return to Federation space via the [[Subspace River]], as they could not open the river terminus without the use of their [[Navigational Deflector]].&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Part II: The Distress Call&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Image:Nova_Class_4.jpg|thumb|175px|right|[[USS Epiphany]]]]&lt;br /&gt;
On their third day in the [[Beltanis Stellar Nursery|Nursery]] the Rosenante detected an automated federation Distress beacon. despite the fact that it was unlikely that any other federation starships were in the area, Captain Salid decided that the Rosenante should investigate.&lt;br /&gt;
&lt;br /&gt;
The beacons prefix identification was finally determined to belong to the the [[USS Epiphany]] a [[Nova Class]] starship registry NCC-913081, which had been declared lost with all hands on Stardate 2392.01.19 (17 years prior.)&lt;br /&gt;
&lt;br /&gt;
When the Rosenante responded, they discovered not the Epiphany, but [[The Harvester]].&lt;br /&gt;
&lt;br /&gt;
The Harvester then proceeded to lock the Rosenante in a Tractor beam like grasp, scan the vessel and transport the Rosenante into the area of the vessel known as the Bone Yard.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Part III: Inside the Harvester&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The arrival inside [[The Harvester]] was anything but accommodating. Upon their rematerialization, the Rosenante was immediately attacked by a group inhabiting the Harvester known as the [[Hur&#039;q]].  These insect-like creatures are those  once referred to in ancient Klingon History as an invader that once tried to conquer the Klingon home world of [[Qo&#039;noS]].&lt;br /&gt;
&lt;br /&gt;
The attack came in the form of a small group of raiders that took advantage of the newly arrived ship&#039;s lack of shields (disrupted by the transport into the Harvester). &lt;br /&gt;
&lt;br /&gt;
Several small groups of assault troops were beamed aboard the Rosenante and these groups managed to tag and steal several supplies from cargo bays as well as a few pieces of minor equipment before they were expelled from the ship. During the skirmish it was determined that the Hur&#039;q were immune to the heavier stun settings on Federation Phasers, and so the crew and security personnel were forced to use the higher level kill and disintegrate settings.&lt;br /&gt;
&lt;br /&gt;
The [[Engineering]] team managed to restore their ship&#039;s only moments after the Hur&#039;q retreated from the ship, although the invaders took all of their dead and it was  believed all of the Rosenante dead as well.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Part IV: The Anti-Hur&#039;q Alliance&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Image:Forest Clearing-Bastion-red.jpg|thumb|300px|right|The Bastion]]&lt;br /&gt;
&lt;br /&gt;
The Rosenante was contacted by the [[Nechani]] ship, [[NSS Oracle&#039;s Tears]] and a meeting was arranged aboard the Bastion.&lt;br /&gt;
&lt;br /&gt;
The Anti-Hur&#039;q Alliance was assembled and comprised of the leaders from the following Species as well as [[Ambassador]] [[Anna Morgan]]:&lt;br /&gt;
&lt;br /&gt;
:The [[Nechani]]&lt;br /&gt;
:The [[Sky Spirits]]&lt;br /&gt;
:The [[Kobali]]&lt;br /&gt;
:The [[Hunters]]&lt;br /&gt;
&lt;br /&gt;
The Rosenante Delegation was lead by [[rank|Commander]] [[Jennifer Caskie]] and was comprised of the following personnel.&lt;br /&gt;
&lt;br /&gt;
:[[Rank|Lieutenant]] [[T&#039;Larah Sullivan]]&lt;br /&gt;
:[[Rank|Lieutenant]] [[Chance Raschen]]&lt;br /&gt;
:[[Rank|Ensign]] [[V&#039;Shera]]&lt;br /&gt;
:[[Rank|Ensign]] [[Dorian Weaver]]&lt;br /&gt;
:[[Rank|Lieutenant]] [[Jon Nayati]]&lt;br /&gt;
:[[Rank|Lieutenant]] [[Thomas Jackson]]&lt;br /&gt;
&lt;br /&gt;
:As well as a few security personnel.&lt;br /&gt;
&lt;br /&gt;
Near the end of the negotiations the meeting was attacked by Hur&#039;q raiders who activated a Transport Inhibitor to trap the Leaders of the alliance in the Bastion. Only Ji&#039;yala had left prior to their arrival.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Part V: The Aftermath&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The aftermath of the battle on the bastion was substantial. The Rosenante Crew lost both Weaver and Sullivan who were killed by Hur&#039;q. Additionally Nayati was missing and  Raschen was critically injured. With such critical officers out of commission, killed or missing, the Rosenante crew are forced to adapt to fill their leadership positions. it later is learned that Nayati was &#039;saved&#039; by the Sky Spirit leader Chaska during the battle. &lt;br /&gt;
&lt;br /&gt;
It is also suspected that the Kobali may be responsible for the missing bodies of the dead crew.&lt;br /&gt;
&lt;br /&gt;
Unknown to the Rosenante crew, Sullivan&#039;s body has undergone the reclamation and is now a member of the Kobali race. &lt;br /&gt;
&lt;br /&gt;
Among those skilled in the battle among the non-Rosenante crew is the Sky Spirit Chief Nekawana and several hunters. Ambassador Morgan has been recovered by members of the Rosenante crew and is currently in sick bay.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Part VI: The Epiphany&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
A survey team lead by Lieutenant Marrow has beamed aboard the Epiphany to begin the survey of her systems in the hopes of reclaiming critical components and salvaging her Main Deflector. Over the course of the next month and a half the Engineering crew of the Rosenante, with assistance from their new alliance members, manage to salvage the Main deflector array and get it installed and operational aboard the USS Rosenante.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Part VII: The Alliance &amp;amp; Escape&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Escape Alliance is formed and all the various species within the Bone Yard of [[The Harvester]] are dedicated to working together to achieve escape. Lieutenant [[Alimi Morrow]] leads a mixed engineering team into the bowels of the Harvester with the goal of disabling the devices Transporters and Tractor beams. That mission is successful.&lt;br /&gt;
&lt;br /&gt;
Additionally the engineering teams work around the clock to modify the Rosenante&#039;s Spiral Warp drive to emit Phased particles.&lt;br /&gt;
&lt;br /&gt;
Using this drive and stabilizing the field with the newly restored navigational array, the Allies are able to escape the Harvester. The allies then parts ways on friendly terms.&lt;br /&gt;
&lt;br /&gt;
==Mission Ten: [[Homecoming]]==&lt;br /&gt;
&lt;br /&gt;
[[Image:Homecoming.jpg|thumb|250px|right|The Rosenante returns to Starbase Geneva]]&lt;br /&gt;
&lt;br /&gt;
After escaping from [[The Harvester]] the [[USS Rosenante]] returns to [[Geneva Station|Starbase Geneva]] for repairs and to give the crew some much needed downtime after their ordeal.&lt;br /&gt;
&lt;br /&gt;
During the three month refit, several members of the crew go on extended leave.  Among those is [[Rank|Lieutenant Commander]] [[Jennifer Caskie]] whose return to her Home in Scotland is under less than ideal circumstances. Her trip is one of necessity rather than desire. She is escorting home the body of her long dead husband Donald Caskie, who was a member of the [[USS Epiphany]] crew. Event though he had been decalred dead nearly two decades earlier, it was disovered that Donald was actually reclaimed by the [[Kobali]] aboard the Harvester. His second death too place during a failed attempt to restore himself to his former life after successfuly restoring [[Rank|Lieutenant]] [[T&#039;Larah Sullivan]] to her previous [[Vulcan]] / [[Human]] heritage after she was killed and reclaimed by the Kobali after a [[Hur&#039;q]] raid.&lt;br /&gt;
&lt;br /&gt;
Additionally, [[Chance Raschen]] and [[T&#039;Larah Sullivan]] are accompanied by Lietenant [[T&#039;Kron]] to [[Vulcan (planet)|Vulcan]] where they will participate in the ancient Vulcan ritual of [[Fal-tor-pan]]. raschen is the recipient of Sullivan&#039;s [[Katra]] after she transferred to him just prior to her death at the hand of a Hur&#039;q subcommander.&lt;br /&gt;
&lt;br /&gt;
Meanwhile back aboard the Rosenante, the ship puts on a masquarade party to help revieve some work related tensions. This party is hosted by Lieutenant [[Thomas Jackson]].  Councilor [[Jon Nayati]] ,the ship&#039;s third officer, attends as does Ensign [[Mitena Rixx]], Head nurse [[Katherine &#039;Kitty&#039; Fisher]] and Doctor [[Sam Lopez]].&lt;br /&gt;
&lt;br /&gt;
Elsewhere, Captain [[Ahmed Ibn Salid]] enjoys a nice relaxing leave on [[Bracas V]] where he enjoys some snorkling and sailing. His trip, however is cut short by a mysterious visit from a [[Dominion]] [[Vorta]] named [[Julman]] and an attending group of [[Jem&#039;Hadar]] soldiers. He isn&#039;t seriously injured although one of the Jem&#039;Hadar are less than pleasant. Other than the initial disagreement, the remainder of the meeting goes along well enough. Julman reveals a terrible peice of information to Salid.&lt;br /&gt;
&lt;br /&gt;
The content of that secret will drive him to consider taking the Rosenante off mission. Is hea leading his ship and crew into a possible Dominion trap or is there a possibility that the information that the Vorta revealed could be true. If it is true, the very future of the [[Alpha Quadrant]] may be at risk.&lt;br /&gt;
&lt;br /&gt;
A few days prior to the relaunch of the Rosenante, Sullivan is promoted to Lieutenant Commander, Raschen to Full Lieutenant and Caskie to Full Commander.&lt;br /&gt;
&lt;br /&gt;
==Mission Eleven: [[Into the Darkness, Go I]]==&lt;br /&gt;
[[Image:Battle Sunali II.jpg|thumb|right|250px|Battle of Sunali II]]&lt;br /&gt;
After his encounter with [[Julman]], [[Rank|Captain]] [[Ahmed Ibn Salid]] came to a critical decision to break his standing orders to partol the frontier between the [[Cardassian Union]] and the [[United Federation of Planets]].&lt;br /&gt;
&lt;br /&gt;
Instead he ordered the Rosenante off mission towards the [[Ikev Sector]] where indications of a conspiracy to build an [[Omega Device]] was suspected.&lt;br /&gt;
&lt;br /&gt;
En route, a distress signal from the [[Boronite]] mining facility on [[Bardon Alpha]] was intercepted. Ahmed ordered the [[USS Rosenante]] into action, but arrived too late to be of much assistance. By the time that they had arrived, the inhabitants of the facility had been slaughtered, leaving only two survivors. Unfortunately the distress signal had named the attacking starship as the Rosenante despite the fact that the ship was nowhere near the facility. &lt;br /&gt;
&lt;br /&gt;
Suspecting a set-up, Salid prepared to leave the system, but again was unable to withdraw before the arrival of the [[USS Furious]] Commanded by [[Rank|Captain]] [[Saleke]] arrived.&lt;br /&gt;
&lt;br /&gt;
knowing how the situation looked, Ahmed ordered the Rosenante to flee and the Furious pursued. Forced to investigate, Saleke engaged the Rosenante with specially modified [[quantum torpedo]]es which were equipped with [[Cloaking device|phased claoking devices]]. these torpedoes were able to get past the Rosenante&#039;s superior shielding and cause significant damage to the ship.&lt;br /&gt;
&lt;br /&gt;
Only the implementation of a new tactic, now called the [[The Salid Gambit]] allowed the Rosenante to escape into the rough asteroid fields of [[The Mill]]. Ahmed was able to cloak his ship and the furious picking up residual traces of a trail left by the original attacked set of in pursuit as Salid ordered repairs undertaken.&lt;br /&gt;
&lt;br /&gt;
Unknown to both saleke or Salid, the perpetrator in the raid on Bardon alpha was the [[Mirror Universe]] version of Ahmed. He commanded the [[ISS Rosenante]] and had set course to head to [[Hexikor Prime]], with the clear goal of capturing components critical to the completion of an [[Omega Device]].&lt;br /&gt;
&lt;br /&gt;
The ISS Rosenante arrived well before either the Furious or the USS rosenante could intercept her and conducted the raid with expected brutality. The components stolen were  a [[Paratrinic Shield|Paratrinic Shield Generator]] And a [[Class 11 Computer|Class 11 Bioneural Computer]]. The ISS Rosenante departed and headed for thier next target.&lt;br /&gt;
&lt;br /&gt;
The Furious arrived on the scene first and Saleke immediately began an investigation. While that was underway, Salid in the [[USS Rosenante]] arrived in the system under cloak.&lt;br /&gt;
&lt;br /&gt;
Determined not to have a repeat of the encounter at [[Bardon Alpha]], Captain Salid chose to neutralize the threat that the Furious posed by transporting six of their primary power buses off the Furious. These power relay buses, caused the ship to lose all primary power, rendering it unable to use weapons, shields or warp drive. Salid then ordered the surrender of the Furious but was unwilling to accept the surrender of that vessel from their First Officer Commander Erin Sloane. &lt;br /&gt;
[[Image:Omega Device.jpg|thumb|left|250px|Omega Device]]&lt;br /&gt;
Saleke was summoned and his presence was requested aboard the Rosenante. Having been convinced by the data that he had collected thus far in his investigation, Captain Saleke informed Captain Salid that he and his ship were no longer suspects in the attack, nor were they complicit in any plot to acquire and build an [[Omega Device]]. Salid had, independently, arrived at the same conclusion, that the ISS Rosenante, a ship from the Mirror universe was in fact responsible for the attacks. &lt;br /&gt;
&lt;br /&gt;
It was also clear that the Mirror Universe Rosenante was following a pattern that must have been established in their own universe. Which explained how the marauding vessel knew where to acquire the components for the creation of a new Omega Device. &lt;br /&gt;
&lt;br /&gt;
After some discussions, it was decided that the USS Furious and the USS Rosenante would need to combine forces in order to counter the tactical and homicidal threat now posed by the ISS Rosenante. &lt;br /&gt;
&lt;br /&gt;
As long range scans indicated that the Mirror Universe vessel was headed for the [[Kabor Prime|Kabor System]] The Rosenante took the Furious under tow, and using their own shields to protect them, opened a Spiral warp conduit to facilitate maneuvers while the Furious conducted the reinstallation of the power relay buses. &lt;br /&gt;
&lt;br /&gt;
A few days after the attack on the Bynar Facility in the Hexikor system, the ISS Rosenante appeared in the Kabor system. Thier target was a secret production facility known as [[Station Omega]]. The facility had been built by a secret research and development branch of Starfleet Sciences Division during the [[Admiral Doenitz|Doenitz]] regime. Thier primary function was the development of an [[Omega Device]]. &lt;br /&gt;
&lt;br /&gt;
After the end of the [[Federation Civil War]] the facility went underground. Through the actions of a small group of [[Starfleet]] [[Rank|Admirals]], all records pointing to the existence of such a facility were erased and the personnel there continued with their research. Through covert means, the facility was equipped with large Class XII phaser batteries for defense. At the heart of the facilities power center was a stabilized [[Omega Molecule]]. The first that the Station had managed to produce. &lt;br /&gt;
&lt;br /&gt;
The ISS Rosenante arrived in the system, intent on collecting the last few remaining components of the Omega device that they needed to create their own version of the weapon. As the Mirror Universe Ahmed Ibn Salid had worked at this facility in his universe, he had intimate knowledge of the facilities existence and layout. What he had not known was that the station had been armed, as in his universe, it was not protected. &lt;br /&gt;
&lt;br /&gt;
The Mirror universe ship was forced to subdue the facility by force, which cost them a great deal of time, narrowing the lead that they had on their Prime Universe Counterpart the [[USS Rosenante]] and the [[USS Furious]]. This delay would prove to be a great boon to the federation starship over the next few days. &lt;br /&gt;
[[Image:Sunali Sun Destruction.jpg|thumb|right|250px|The Destruction of the Sunali star]]&lt;br /&gt;
Despite this delay, the two [[UFP]] starships did not arrive in the system quickly enough to engage the Imperial Starship. They were however able to track it to it&#039;s next and final location, the [[Sunali II|Sunali System]].&lt;br /&gt;
&lt;br /&gt;
The [[USS Rosenante]] and the [[USS Furious]] entered the [[Sunali II|Sunali System]] to find the [[ISS Rosenante]] engaged in the wanton destruction of [[Cardassian]] merchant shipping. These ships although peaceful, had been destroyed simply because they were Cardassian.&lt;br /&gt;
&lt;br /&gt;
The USS Rosenante ordered the Imperial starship to surrender. That vessel refused.&lt;br /&gt;
&lt;br /&gt;
What followed next was a flurry of conflict, with the Stronger [[ISS Rosenante]] dealing a tremendous amount of damage to both the [[USS Rosenante]] as well as the [[USS Furious]],&lt;br /&gt;
&lt;br /&gt;
During the conflict the Furious engaged her [[Prometheus Class|Tri-vector Attack mode]] to engage the more powerful [[Mirror Universe]] vessel. The Mirror universe [[Andrew Elliot Maddox]] managed to take over the computer of one of the Furious&#039; sections named the Courageous and overload it&#039;s warp core killing all 142 hands on board. &lt;br /&gt;
&lt;br /&gt;
With the battle going against them, captain Salid came up with a plan to stop the Imperial vessel dead in it&#039;s tracks. Building off a suggestion made by [[Rank|Lieutenant]] [[Chance Raschen]], he initiated a transfer of the Omega Directive Protocols into the Imperial Starship&#039;s computer after the junior officer reeled them into communications range for the data transfer. That vessel&#039;s commander, having no experience with the [[Starfleet General Orders &amp;amp; Directives|Omega Directive]] was unable to unlock the ship&#039;s computer, which caused them to lose the battle.&lt;br /&gt;
&lt;br /&gt;
However, the ship had not been neutralized before they had managed to launch the [[Omega Device]] at the [[Sunali II|Sunali]] Sun. Unable to pursue, the Rosenante was forced to allow the [[USS Furious]] to intercept and eventually destroy the weapon.&lt;br /&gt;
&lt;br /&gt;
With the aid of [[Nathan Benoit]] the Furious and the Vigiliant (another element of the Furious), managed to shut down the [[Paratrinic Shield]] protecting the device by bypassing the operating system of the [[Class 11 Computer|Class 11 Bioneural Computer]] that controlled it. With the shields down, The Vigilant was able to destroy the device with Phaser fire just minutes before it would have detonated.&lt;br /&gt;
&lt;br /&gt;
With the battle over, Captain Salid ordered boarding parties to take possession of the [[ISS Rosenante]].&lt;br /&gt;
&lt;br /&gt;
The teams achieved their goals quickly and with little resistance, as the [[Mirror Universe]] Salid had ordered his crew not to resist.&lt;br /&gt;
&lt;br /&gt;
Meanwhile back aboard the USS Rosenante [[Alimi Morrow|Lieutenant Alimi Morrow]] fought to prevent a warp core collapse. his efforts and those of [[Jon Nayati|Lieutenant Jon Nayati]] and [[V&#039;Shera|Ensign V&#039;Shera]] managed to prevent the destruction of the federation vessel. However, it was not without cost. Morrow was seriously injured in the attempt and was treated for severe radiation poisoning. His condition was so critical that he was placed in Stasis until such time as he could receive treatment at [[Geneva Station|Starbase Geneva]]. His life was saved by the quick thinking and intervention of [[Kimiko Ichijo|Doctor Kimiko Ichijo]].&lt;br /&gt;
&lt;br /&gt;
After the Capture of the [[ISS Rosenante]] a deal was struck by which all the data concerning the [[Omega Conspiracy]] in the prime universe would be handed over to Captain Salid and Saleke in exchange for returning the Imperial ship home.  The agreement was made, after some discussion between The two Federation Commanding Officers and the Rosenante&#039;s First officer [[Jennifer Caskie]].&lt;br /&gt;
&lt;br /&gt;
A technical team was assigned to install an [[Interphasic Field Generator]] aboard the Imperial starship, which would force the ship back into it&#039;s normal universe. This same generator would then self destruct, making it impossible for the [[Imperial Union of Planets]] to recreate the devices for their use. Once the device was installed, the imperial ship was returned to the command of the [[Mirror Universe]] Salid and sent home. All indications suggest that the vessel was returned to their proper universe intact.&lt;br /&gt;
&lt;br /&gt;
The Rosenante, towing the [[USS Furious]] then returned to [[Starbase Geneva]] for repairs. &lt;br /&gt;
&lt;br /&gt;
===Mirror Universe Salid===&lt;br /&gt;
&lt;br /&gt;
Ahmed Ibn Salid of the [[Mirror Universe]] is a much different man than the one from our universe. The differences begin early on in his life. &lt;br /&gt;
&lt;br /&gt;
As a teenager, Ahmed showed a distinct aptitude for [[Engineering]]. His status was that of a child prodigy, and he was actually trained as an engineer in the hopes that he would serve in the Imperial Engineering Corps developing weapons and new technology.  He graduated from his classes with honors and was assigned to the [[ISS Templar]], Where he served as an Assistant Chief Engineer. He quickly began to make his way up the chain through deceit or assassination until he reached the rank of Lieutenant and the position of Chief Engineer.&lt;br /&gt;
&lt;br /&gt;
His career was cut short however, when it was discovered that his Father was involved in the planned assassination of the Empire&#039;s [[Klingon]] [[Regent]]. In retaliation, Salid was arrested and shipped to the [[Boronite]] mines on [[Bardon Alpha]]. It was there during his incarceration that he met the future regent [[Admiral Doenitz|Rodrigo Doentiz]]. &lt;br /&gt;
&lt;br /&gt;
Together the two men worked in the mines until the opportunity arose to escape. When that day came, the two men led a slave revolt against the penal colony&#039;s guards. The campaign was swift and brutal, and with the aid of a rebel ship captain, [[Devan Sash]], the two men escaped along with a small cadre of officers, including [[Saleke]], [[Zachary Falthgood]] and [[T&#039;Vhor]]. Later this group would eventually seize control of the leadership of the [[Human|Terran]] Rebellion and later the puppet Government of [[Earth]].&lt;br /&gt;
&lt;br /&gt;
Salid was promoted to Captain of the [[ISS Rosenante]] which became the Flag ship for the newly reformed and reorganized [[Mirror Universe|Imperial Union of Planets]]. His new role put him into direct conflict with several KCA starships, honing his abilities and reputation as an extraordinarily brutal ship commander. His complete dedication and loyalty to Regent Doenitz and the IUP guaranteed his quick rise to a position of power.&lt;br /&gt;
&lt;br /&gt;
In 2408, Ahmed was assigned the task to deploy the [[Omega Device]] against a KCA task force gathering at [[Sunali II]]. The weapon was deployed and it destroyed the enemy ships as well as the traitorous planet, which had defected to the KCA. The [[ISS Rosenante]] was thrown through a dimensional rift into the normal universe.&lt;br /&gt;
&lt;br /&gt;
==Mission Twelve: [[Equals and Opposites]]==&lt;br /&gt;
[[Image:StarbaseGeneva.jpg|thumb|right|300px|Starbase Geneva|200px]]&lt;br /&gt;
&lt;br /&gt;
With the return of the [[USS Rosenante]] and the [[USS Furious]] to [[Starbase Geneva]], refits and repairs from their encounter in the [[Sunali II|Sunali System]] began. With the work taking a great deal of the crews time and efforts, Captain Salid is repeatedly called before members of the admiralty to discuss the unsanctioned nature of his mission as well as reveal details and records of the [[Omega Conspiracy]].&lt;br /&gt;
&lt;br /&gt;
In addition to the briefings and meetings centered around the conspiracy, an official tribunal was called to inquire into the destruction of the  [[USS Furious|Courageous]] during the battle at Sunali II.&lt;br /&gt;
&lt;br /&gt;
The captain is displeased with the findings of the Tribunal, but his hands are tied as he is forced to deal with the harsh political nature of the situation.&lt;br /&gt;
&lt;br /&gt;
==Mission Thirteen: [[The Quondam Season]]==&lt;br /&gt;
[[Image:Iconia planet.jpg|thumb|right|200px|Xega III]]&lt;br /&gt;
The [[USS Rosenante]] is dispatched on a routine resupply mission for the archeological survey team located on [[Xega III]].&lt;br /&gt;
&lt;br /&gt;
The team led by Doctor [[Otto Totenkampf]] has been studying the ruins of the ancient [[Xegan]] civilization for nearly three decades.&lt;br /&gt;
&lt;br /&gt;
Among the tasks assigned to the crew of the Rosenante are standard planetary scans, launch of a pair of orbital satellites to aid the survey team, as well as assisting in planetary thermal and tectonic studies.&lt;br /&gt;
&lt;br /&gt;
Because the planet orbits an Orange giant star which constantly bombards the planet with stellar radiation, which seems to have gathered in the upper ionosphere, the use of transporters is impossible.&lt;br /&gt;
&lt;br /&gt;
The resupply, consisting of a mobile habitation unit, medical and foods supplies, as well as a replacement [[Argo Shuttle|Argo Class]] Shuttle and rover must all be undertaken by shuttlecraft.&lt;br /&gt;
&lt;br /&gt;
Shortly after arriving on the planet however, a strange energy reading is detected from a newly uncovered archeological site. This energy source is emanating from the [[Balancer Machine]], a legendary Xegan construct which was rumored to be able to prevent the planet from being ravaged by the very solar radiation that had caused the decline of the culture that created it.&lt;br /&gt;
&lt;br /&gt;
Suddenly the machine activated, perhaps for the very first time. Massive monoliths burst from the ground every feww hundred miles and rose into the planet&#039;s upper ionosphere. There they began to collect the radiation that was present and generate massive amounts of power into some unseen machine deep beneath the planet&#039;s surface.&lt;br /&gt;
&lt;br /&gt;
The crew of the Rosenante evacuated the archeological team and broke orbit to pbserve from a safer distance, as the monoliths were now creating massive storms in the planet&#039;s thin atmosphere.&lt;br /&gt;
&lt;br /&gt;
After the monoliths gathered energy for a period of roughly two standard days, a buildup was detected in one of the monoliths and a massive beam of light erupted from that monolith travelling towards the planet&#039;s sun.&lt;br /&gt;
&lt;br /&gt;
The affects of that massive energy beam, is unknown however, as at that exact moment, a massive temporal displacement wave, comprised of [[Chroniton]]s and an unidentified particle known as [[Seylerions]] entered the system moving at a speed greater than warp ten.&lt;br /&gt;
&lt;br /&gt;
The Rosenante was caught up in it and was thrust 5 years into the future.&lt;br /&gt;
&lt;br /&gt;
===The Future===&lt;br /&gt;
[[File:Balancer machine.jpg|thumb|300px|left|The Xega III Balancer Machine as seen from orbit]]&lt;br /&gt;
Once the wave had subsided, the crew of the Rosenante began to check their ship&#039;s systems, most notably their chronometers. The wave had caused some minor ships issues, the most serious of whihc was a disruption in the ship&#039;s warp drive systems.&lt;br /&gt;
&lt;br /&gt;
As the crew began repairs and went to work verifying that they had indeed been moved froward in time, Captain Salid ordered a communication sent to [[Starfleet Command]] to inform them of the event.&lt;br /&gt;
&lt;br /&gt;
He was surprised to see that the Rosenante&#039;s communications codes were invalid. At first he received no reply, but eventually, he was contacted by an admiral from command and ordered to hold position. Furthermore he was ordered to maintain a communications blackout, and to await an escort to an unknown location.&lt;br /&gt;
&lt;br /&gt;
Ever suspicious, Captain Salid complied, but prepared his ship for the worst.&lt;br /&gt;
&lt;br /&gt;
===Khitomer===&lt;br /&gt;
&lt;br /&gt;
The Rosenante was met and escorted to [[Khitomer]] by three Federation starships, one of which was a [[Rosenante Class]] vessel.&lt;br /&gt;
&lt;br /&gt;
Once they arrived, it was rather apparent that something massive had happened. A large number of [[starship]]s from the [[52nd Fleet]] had assembled here, along with an even greater number of escorts.&lt;br /&gt;
&lt;br /&gt;
[[Rank|Captain]] [[Ahmed Ibn Salid|Salid]] was ordered to beam down to [[Khitomer Conference|Camp Khitomer]] alone and await a debriefing.&lt;br /&gt;
&lt;br /&gt;
He arrived in the early morning, and was greeted by the sights and sounds of dozens of ship&#039;s commanding officers. Including those from the [[USS Mithrandir]], [[USS Spectre]], [[USS Hades]], [[USS Furious]], and [[USS Boudicca]].&lt;br /&gt;
&lt;br /&gt;
In addition to these officers, [[Rank|Admiral]] [[Robert LoDona]] was brought out of retirement to conduct the debriefing. &lt;br /&gt;
&lt;br /&gt;
Questions concerning the events which brought them here were asked and it quickly became apparent that nearly the entire [[52nd Fleet]] had been affected by the same phenomenon that had pushed the [[USS Rosenante]] forward in time.&lt;br /&gt;
&lt;br /&gt;
Further individual interviews were conducted with the Commanding Officers of the assembled starships before they were allowed to return to their vessels.&lt;br /&gt;
&lt;br /&gt;
Later Starfleet Science teams came aboard and scanned the ship, conducting a series of tests designed to verify the story that had been provided for the disappearance of the ships five years earlier.&lt;br /&gt;
&lt;br /&gt;
In addition to those teams, [[Starfleet Intelligence]] also came aboard to interview various members of the Rosenante&#039;s crew.&lt;br /&gt;
&lt;br /&gt;
After two days of studies and interviews, the rosenante was released from the Khitomer system and headed for [[Starbase Geneva]].&lt;br /&gt;
&lt;br /&gt;
There they underwent some retraining and some minor refits to bring them up to specifications with the technological and professional advances of the last five years.&lt;br /&gt;
&lt;br /&gt;
It was during this time that [[Rank|Commander]] [[Jennifer Caskie]] resigned, as she had discovered that her son Ian had gone missing during the five years prior.&lt;br /&gt;
&lt;br /&gt;
She was discharged from service.&lt;br /&gt;
&lt;br /&gt;
==Mission Fourteen: [[The Gilded Man]]==&lt;br /&gt;
[[File:Scout.jpg|thumb|400px|right| The USS Bohrs]]&lt;br /&gt;
&lt;br /&gt;
In 2314, nearly a decade after the Champlain&#039;s initial sensor readings of a Federation- style warp signature, in the [[Irlix|Irlix System]] the [[USS Bohrs]], a [[Mission Scout]] vessel, (&#039;&#039;&#039;NCC-369477&#039;&#039;&#039;) was dispatched to follow-up on those inital findings.&lt;br /&gt;
&lt;br /&gt;
The Bohrs proceeded to the Irlix system and utilizing her [[Cloaking device]] began to collect cultural and military data in an attempt to isolate the original source of the initial Federation warp signature.&lt;br /&gt;
&lt;br /&gt;
The Bohrs was on station for only a few weeks, when a computer attack shut down her cloaking device and left her vulnerable to attack by military starships belonging to the [[Rhone Union]].&lt;br /&gt;
&lt;br /&gt;
The Bohrs was captured and forced down on the [[planet]] [[Irlix]], where it was stored in the [[Seliya Facility]].&lt;br /&gt;
&lt;br /&gt;
A few days after the capture of the Bohrs, the [[USS Rosenante]] was tasked with the rescue of the crew of the Bohrs as well as the recovery and/or destruction of the starship. As a secondary objective, they were tasked with the discovery of the sudden technological boost found in Irlixian society which was inconsistent with the rest of their technological development.&lt;br /&gt;
&lt;br /&gt;
Because of a significant threat to the Rosenante, in light of the events leading up to the capture of the Bohrs, [[Rank|Captain]] [[Ahmed Ibn Salid]] decided to drop a cosmetically altered away team on the surface of the planet.&lt;br /&gt;
&lt;br /&gt;
After arriving in the Irlix system, the [[USS Rosenante]] approached the planet from a polar orbit acheived by following a very broad hyperbolic course. Once in position, the Away Team was sent down to the planet&#039;s surface, specifically to [[Khoda City]], in pairs, to minimize the chance of detection.&lt;br /&gt;
&lt;br /&gt;
The Away Team made their way to the Hotel Votul, a buisness known locally for allowing [[Irlixian|Gab]] males and [[Irlixian|Mol]] females to mingle in a social setting where they would not normally be permitted to do so. The meeting place at the hotel is marked by an interplexing communications beacon set up by [[Chance Raschen]]. The final meeting spot was a public restroom on the first floor of the hotel.&lt;br /&gt;
&lt;br /&gt;
Things get interesting when [[Mike Rosenbauer]]  shows up with [[Ios Malinae]], an [[Irlixian]] female, that he had &#039;rescued&#039; earlier from an assault and attempted rape. Ios apparently recognized Mike&#039;s blood, seeping from a broken lip as belonging to a [[Human]] rather than an Irlixian. She then revealed through an encounter with her mother, [[Sola Malinae]] that she was associated with the secret [[Seliya Facility]] where the research and development of the Alien ([[Federation]]) technology was being studied and retro-engineered.&lt;br /&gt;
&lt;br /&gt;
Taking a risk, Mike brought her to the meeting to allow [[Rank|Lieutenant Commander]] Sullivan a chance to question her and determine if she possessed any knowledge that may aid the Away Team in their mission.&lt;br /&gt;
&lt;br /&gt;
She was not, however, the only visitor to arrive at the Hotel Votul.&lt;br /&gt;
[[File:Dual moon planet.jpg|thumb|400px|left|Irlix]]&lt;br /&gt;
Senior Detective [[Vilox Nigo]], a member of the Special Police responsible for dealing with espionage inside the Rhine Union, detected the beacon and set into motion police resources in an attempt to capture the away team, which he believed were spies from one of the other major political powers on [[Irlix]].&lt;br /&gt;
&lt;br /&gt;
When the raid began, the away team put up more of a resistance than Vilox had anticipated and managed to escape although [[T&#039;Larah Sullivan|Sullivan]], [[Louis Remey]], [[Steven Wade Matrix|Steve Matrix]] and others were injured in the fighting to some degree.&lt;br /&gt;
&lt;br /&gt;
Thanks to the hard efforts of [[Sanok]], [[Thomas Jackson|Tom Jackson]] and [[Steven Wade Matrix|Steve Matrix]], the Away Team managed to escape the premises, narrowly dodging a perimeter of Police Snipers and pursuing law enforcement forces.&lt;br /&gt;
&lt;br /&gt;
While the away team found themselves in a pickle on the surface the [[USS Rosenante]] was facing difficulties of her own. under the command of [[Rank|Captain]] [[Ahmed Ibn Salid| Salid]], the Rosenante was forced to break orbit and begin a series of maneuvers to avoid detection and capture once it became apparent that the Irlixians were able in some manner to detect the cloaked [[Federation]] [[Starship]].&lt;br /&gt;
&lt;br /&gt;
As the goal was to avoid a confrontation and since the means by which the Irlixians were detecting the position of the Rosenante was unknown, the captain ordered the ship to displace frequently to delay any potential military actions between the Irlixian Fleet and the Rosenante.&lt;br /&gt;
&lt;br /&gt;
It was also interesting to note that the detection means was neither immediate nor precise and that meant that simple maneuvering whenever a course change took place among the Irlixian patrol craft happened were sufficient to keep the Rosenante safe from immediate harm.&lt;br /&gt;
&lt;br /&gt;
With the Rosenante well away from the planet, they found themselves unable to respond to the sudden appearance in the system of a Federation [[Danube Class Runabout|runabout]] without incurring significant risk to the Rosenante.&lt;br /&gt;
&lt;br /&gt;
This runabout was manned by two new recruits to the Rosenante [[Rank|Ensign Junior Grade]] [[Eian O&#039;Neill]] and Ensign Junior Grade Machaire Rabhartaigh. they had been assigned to the ship, but they had not been briefed on the nature of the Rosenante&#039;s mission and therefore found themselves entering hostile space unexpectedly. &lt;br /&gt;
&lt;br /&gt;
[[image:Irlixian Girl2.jpg|thumb|400px|right|An Irlixian Female]]&lt;br /&gt;
&lt;br /&gt;
The [[Irlixian]]s attacked. The result was the crippling of the runabout, which forced O&#039;Neill to crash land the damaged ship outside the Capital of the [[Rhone Union]], [[Khoda City]].&lt;br /&gt;
&lt;br /&gt;
Within minutes of the crash, however, the shuttle was surrounded by a small squad of Irlixian police. This prevented the immediate escape of the crash survivors.&lt;br /&gt;
&lt;br /&gt;
All hope was not lost, however, as Ensign O&#039;Neill had managed to send out a brief mayday message that alerted the away team already on the planet to their plight.&lt;br /&gt;
&lt;br /&gt;
A quick rescue and recovery mission was organized by the away team, still on the planet.The team made good speed from the safe house to the crash site where they relieved the surrounded crash victims before lead elements of the Secret police force under [[Vilox Nigo]] arrived. With the survivors recovered the extraction team returned to the safe house to await contact with the Rosenante and to continue medical treatment of the wounded.&lt;br /&gt;
&lt;br /&gt;
Meanwhile,  back aboard the Rosenante, it was becoming more difficult to avoid the ever shrinking search net of the Irlixian starships.&lt;br /&gt;
&lt;br /&gt;
It was the sudden epiphany offered up by Trade Winds Bar manager, and ex-intelligence officer T&#039;Lela, that the Rosenante was finally able to discover the means by which they were being tracked.&lt;br /&gt;
&lt;br /&gt;
The Irlixians were managing to track the automated communications data streams that all Federation starships use to connect to the [[Memory Alpha]] database as well as to navigational satellites. And while unable to disable this uplink, the deployment of some [[Stealth Buoy]]s, set to monitor the same frequency created a series of decoys that would confound the Irlixians and allow the Rosenante to slip free and return to [[Irlix]] to get an update from the away team there.&lt;br /&gt;
&lt;br /&gt;
When the Rosenante took up a standard orbit and made contact with the away team, it quickly became apparent that the initial mission parameters had no real chance of success. As a result Salid ordered the away team and their civilian adviser, Ios, beamed back aboard the Rosenante.&lt;br /&gt;
&lt;br /&gt;
While the members of the away team visited Sickbay to have the last of their injuries tended to and to have the cosmetic surgeries undone, Captain Salid was speaking with the civilian advise Ios concerning the situation. It was from that brief meeting and interview that a new plan of action was hatched.&lt;br /&gt;
&lt;br /&gt;
Once the away team was restored, and with the Rosenante managing to remain undetected at the polar orbit of the planet, Captain  Salid called a briefing where he outlined the new plan.&lt;br /&gt;
&lt;br /&gt;
He had become convinced after hearing about the history of the Rhone Union from Ios that a member of the Medea crew had managed to infiltrate the government and violated the [[Prime Directive]] for their own benefit.&lt;br /&gt;
&lt;br /&gt;
This in turn led the Captain to implement a three pronged plan of action that would achieve a variety of mission goals simultaneously.&lt;br /&gt;
&lt;br /&gt;
First Salid and [[Louis Remey]] would be making an appearance at a scheduled media conference being put forward by [[Ono Nakamura|Khoda Rhone]]. By hijacking the media feeds of the planet, Salid could insure that the message that he wanted to spread across the planet would remain uninterrupted. Remey would be responsible for running scans of the Rhone Union leadership present in an effort to ferret out the traitor in their midst.&lt;br /&gt;
[[File:Nakamara.jpg|thumb|left|300px|Ono Nakamura in 2393]]&lt;br /&gt;
While Salid and Remey acted as investigators, instigators and distraction, a second team led by [[Rank|Lieutenant]] [[Steven Wade Matrix]] and consisting of [[Marta Nunez]], [[Sanok]] and [[Robert Smith]] would conduct a raid against Rhone Union government offices in an attempt to locate information on the location of the Hostages from the [[USS Bohrs]]. Once that information was located, a third team led by [[Mike Rosenbauer]], and consisting of [[Kimiko Ichijo]], [[Sam Lopez]], and [[Eian O&#039;Neill]] would begin the operation to rescue the hostages while Matrix&#039;s team beamed to the sight of the Bohrs and prepared the ship for departure.&lt;br /&gt;
&lt;br /&gt;
Unfortunately, some parts of the plan did not quite happen as planned. Although The rescue team was deployed, matrix&#039;s team was forced to remain hidden in the government offices due to the fact that the Rosenante, Commanded by [[Rank|Commander]] [[T&#039;Larah Sullivan]], and aided by [[Rank|Lieutenant]] [[Thomas Jackson]] and [[Chance Raschen]], was forced into a military encounter with Rhone Union [[Starship]]s commanded by Fleet Commander [[Frazil]].&lt;br /&gt;
&lt;br /&gt;
Despite this setback, Rosenbauer&#039;s team managed to rescue not only the hostages from the Bohrs, but also [[Rank|Lieutenant]] [[Ben Soma]], previously of the [[USS Mithrandir]] and [[Rank|Lieutenant]] Doug Masters. The reinforced team managed to make their way to the Bohrs, and after a spectacular diversion with a damaged runabout, destroy the partially restored wreckage of the [[USS Medea]] and allow the Bohrs to escape the hanger once her systems were restored.&lt;br /&gt;
&lt;br /&gt;
While members of his crew were engaged in various levels of their portion of the operation, Captain Salid managed to cause Khoda Rhone, whom Remey had identified as [[Ono Nakamura]], previously the Chief Engineering Officer of the [[USS Medea]] to confess to his crimes.&lt;br /&gt;
&lt;br /&gt;
As expected, the [[Irlixian]]s were shocked and Khoda Rhone was ousted from power. He was taken into custody by Remey, while Salid attempted to rectify the cultural contamination that Nakamura had caused.&lt;br /&gt;
&lt;br /&gt;
After an additional eight days of negotiations, the governments of Irlix agreed to establish a provisional planetary government under the leadership of [[Ios Malinae]]. With the arrival of starships from the [[Federation Diplomatic Corps]], the USS rosenante was released from their mission.&lt;br /&gt;
&lt;br /&gt;
They aided in the repairs of the [[USS Bohrs]] before heading to [[Starbase 989]] for some much needed upgrades and R&amp;amp;R.&lt;br /&gt;
&lt;br /&gt;
==Mission Fifteen: [[Touch of the Eidolon]]==&lt;br /&gt;
[[File:Starbase 989.jpg|thumb|right|250px|Starbase 989]]&lt;br /&gt;
&lt;br /&gt;
The [[USS Rosenante]] after returning from [[Irlix]] system is long overdue for some much needed Rest and relaxation time on [[Starbase 989]].The ship put into dock and [[Rank|Captain]] [[Ahmed Ibn Salid|Salid]] held a briefing to bring his crew up to specs for the refit and resupply operations that would need to take place prior to the Rosenante&#039;s departure.For a change it looked as if everything would go well, and that the crew wouldn&#039;t be drawn into any unwanted scuffles with station personnel.It also seems that the reality of things is always different from the desired.&lt;br /&gt;
&lt;br /&gt;
Word quickly spread through the crew that the Starbase was holding the [[Alpha Quadrant|Alpha]]-[[Beta Quadrant]] wide martial arts tournament. The prize was a substantial [[latinum]] prize as well as the title of Champion of two quadrants. The following personnel from the Rosenante entered the tournament:&lt;br /&gt;
&lt;br /&gt;
*[[Kimiko Ichijo]]&lt;br /&gt;
*[[Ben Soma]]&lt;br /&gt;
*[[Eian O&#039;Neill]]&lt;br /&gt;
&lt;br /&gt;
They each competed against their respective opponents and were each in turn disappointed with the scores handed down to them by the panel of judges, which included, [[Ieko Takawa]]. However, rumor soon arose that the tournament may be fixed.  This coupled with information gathered by Soma during his investigation of Captain Taylor&#039;s murder, indicated that somehow the two could have been connected.&lt;br /&gt;
&lt;br /&gt;
[[File:Joseph Taylor.jpg|thumb|left|200px|Captain Joseph Taylor.]]&lt;br /&gt;
The day after the arrival of the [[USS Rosenante]] reports were made of the discovery of the body of [[Rank|Captain]] [[Joseph Taylor]], who was the commanding officer of [[Starbase 989]].  The captain was found dead in his quarters by a security officer from the station who had been dispatched when the Captain failed to respond to calls from his first Officer [[Rank|Lieutenant]] [[Kraal]].&lt;br /&gt;
&lt;br /&gt;
Almost immediately, Kraal contacted [[Rank|Captain]] [[Ahmed Ibn Salid]] and notified him of the grisly discovery. Citing Regulations, Salid, then assumed command of the investigation and assigned the Rosenante&#039;s own  Chief Security Officer [[Ben Soma]] to investigate.&lt;br /&gt;
&lt;br /&gt;
The body was recovered by the Rosenante team and a thorough study of the crime scene was conducted by [[Rank|Lieutenant]] [[Steven Wade Matrix]], and [[Eian O&#039;Neill]]. In addition to the survey of the crime scene, Doctor [[Kimiko Ichijo]] and Doctor [[Sam Lopez]] undertook an autopsy, to determine the cause of death.&lt;br /&gt;
&lt;br /&gt;
From the combined results of these studies clues and mysteries began to form, throwing out a number of plausible scenarios as to how the murder could have been conducted. Among the most puzzling of these mysteries was the nature of the murder weapon, a hook shaped spike that seemingly dematerialized inside the wound after the deed was done. In addition, coupled with the fact that the Captain had secured his personal quarters, the scene of the murder, with a very high level encryption that could only be overridden by other [[Starfleet]] officers of flag rank or greater, left the crew wondering who on the station had the ability to reach the obviously paranoid captain.&lt;br /&gt;
&lt;br /&gt;
To further complicate matters, the captain had no defensive wounds on his body, which would indicate that death was sudden and that the Starbase&#039;s commanding officer did not expect an attack.&lt;br /&gt;
&lt;br /&gt;
A short list of suspects was assembled, after further questioning and DNA evidence discovered that the Captain had been having an affair with two of his junior officers. Early in the investigation, there were strong indications that Captain Taylor may have been corrupt and that his murder may have been caused by a business deal going poorly.&lt;br /&gt;
&lt;br /&gt;
The chief suspects were:&lt;br /&gt;
&lt;br /&gt;
*[[Braak]]&lt;br /&gt;
*[[Pez]]&lt;br /&gt;
*[[Quol Nor]]&lt;br /&gt;
* Doctor [[Gena Harvey]]&lt;br /&gt;
* [[Rank|Lieutenant]] [[Adraa Mosul]]&lt;br /&gt;
*[[Ieko Takawa]]&lt;br /&gt;
&lt;br /&gt;
[[File:Harveq.jpg|thumb|250px|right|The Romulan freighter Harveq]]&lt;br /&gt;
The following day, a second body was discovered by a [[Starfleet]] engineer on duty on the station. He discovered the body of the [[Orion]] Cargo Master [[Nargo]]  of the [[Romulan]] [[starship|freighter]] [[Harveq]]. The ship&#039;s captain was [[T&#039;Sek]], a Romulan merchant. T&#039;Sek&#039;s grandfather is [[Chairman|Vice-Chairman]] [[Somek]] of the [[Romulan Tal Shiar]].&lt;br /&gt;
&lt;br /&gt;
Before the Station security personnel could arrive, however, T&#039;sek and some of his Orion crew recovered Nargo&#039;s body and took it aboard their ship.  When [[Ben Soma]] and his team from the Rosenante arrived, Soma was unhappy with the turn of events and planned to take action to deal with the situation.&lt;br /&gt;
&lt;br /&gt;
After some careful consideration, Soma assigned [[Sanok]] to open discussions with the Romulan ship captain. Little did they know, T&#039;Sek had full intentions of inviting them aboard the [[Harveq]]. The captain had four members f the Rosenante team transported aboard the [[Harveq]], [[Kimiko Ichijo]], [[Ben Soma]], [[Sanok]] and [[Eian O&#039;Neill]]. They were greeted by captain T&#039;Sek and an armed [[Orion]] security team. This event was initially misinterpreted by the away team as aggression, when in fact T&#039;Sek, was merely concerned with the appearance of the situation and did not wish to take a chance that the Starfleet officers were going to attempt to arrest him for interfering with their investigation.&lt;br /&gt;
&lt;br /&gt;
Once the away team was disarmed, the security detail relaxed and T&#039;Sek was amiable to the officers.&lt;br /&gt;
&lt;br /&gt;
[[Image:Holodeck empty.jpg|thumb|250px|left]]&lt;br /&gt;
Meanwhile, it was discovered that an upgrade request for the [[USS Rosenante]] to become upgraded to fully holo-capable had been filed by the new ACEO [[Eian O&#039;Neill]]. This of course, immediately set of a series of alerts, since O&#039;Neill was fully aware that the Rosenante was already completely Holo-capable. &lt;br /&gt;
&lt;br /&gt;
A quick investigation led the security team of the [[USS Rosenante]] to believe that someone had managed to steal a biometric fingerprint signature belonging to the officer.  When questioned, O&#039;Neill revealed that he had, in fact, used his finger print in two places on the station. &lt;br /&gt;
&lt;br /&gt;
The first was the Martial Arts Tournament on [[Starbase 989]]. The second was with [[Quol Nor]] when he booked [[Holodeck|Holosuite]] time on the station so that he could work on a special holoprogram to allow him to spend Christmas with his family, who were several [[Light Year]]s away.&lt;br /&gt;
&lt;br /&gt;
[[Ben Soma]] ordered O&#039;Neill to investigate.&lt;br /&gt;
&lt;br /&gt;
Those, it seemed were not the only technical difficulties facing the Rosenante. When Starbase engineers began their upgrade cycles, they managed to cause significant processing loss to the Rosenante&#039;s [[Computer Core]]s.  This caused a significant delay in the processing of the data collected at the crime scene by [[Steven Wade Matrix]]. In addition, the interlinks connecting the Rosenante to the Starbase were also damaged, meaning that the crew was unable to borrow processing time from the starbase.&lt;br /&gt;
&lt;br /&gt;
[[File:Rosk.jpg|thumb|right|200px|Doctor Rosk]]&lt;br /&gt;
Aboard the [[Harveq]], while [[Kimiko Ichijo|Doctor Ichijo]] and [[Sanok]] were meeting with [[Rosk|Doctor Rosk]] concerning the murder of [[Nargo]], [[Ben Soma]] and [[Rank|Ensign]] [[Eian O&#039;Neill]] were meeting with [[T&#039;Sek]].&lt;br /&gt;
&lt;br /&gt;
The meeting went well, with T&#039;Sek offering  a significant piece of the murder puzzle to the two officers in the form of a [[Cardassian]] [[Optolythic Data Rod]], which are renowned for their difficulty to forge.&lt;br /&gt;
&lt;br /&gt;
The data on the rod pointed firmly to the [[Ferengi]] [[Quol Nor]] as the Captain&#039;s murderer, but as the [[Romulan]] did not wish to testify, the investigation would need further evidence in order to arrest the Ferengi for the [[Rank|Captain&#039;s]] murder.&lt;br /&gt;
&lt;br /&gt;
During the second day of the tournament, Ichijo, Soma and O&#039;Neill confronted the senior judge [[Ieko Takawa]]. Their assertions caused the man to admit to his unwilling involvement in the fixing of the tournament, which indirectly had caused Taylor&#039;s death. He also directly connected  [[Quol Nor]] to the tournament, providing, for the first time a solid motive for the Ferengi. The tournament was suspended and all judgements withdrawn.&lt;br /&gt;
&lt;br /&gt;
[[File:Assassin Hologram.jpg|thumb|left| 350px|Quol Nor&#039;s Assassin Hologram]]&lt;br /&gt;
Convinced that the data was solid and needing more evidence that the [[Assassin Hologram]] was indeed connected to [[Quol Nor]] Soma, Ichijo, O&#039;Neill and Sanok devised a plan to lure the program in so that it could be neutralized and it&#039;s subroutines studied. the plan was simple in its design although rather complex in execution. After reactivating and securing the Holographic systems aboard the Rosenante, [[Eian O&#039;Neill]] prepared to isolate and neutralize the Program once it appeared on the Rosenante.&lt;br /&gt;
&lt;br /&gt;
To insure that it would appear, [[Sanok]] would activate the [[Data Cube]] that was recovered from [[Rank|Captain]] [[Joseph Taylor|Taylor&#039;s]] quarters where it had been disguised as a [[latinum]] sheathed moving sculpture.  Group gambled that the reactivation  of the data cube would alert either the program or it&#039;s [[Ferengi]] controller and that the end result would be that the program would attempt to recover the cube at all costs. With Sanok playing bait, [[Ben Soma]] and [[Kimiko Ichijo]] stood by to render assistance, while [[Eian O&#039;Neill]] would isolate the program.&lt;br /&gt;
&lt;br /&gt;
The plan was a qualified success, as the program appeared as expected. Although O&#039;Neill was quick the program was able to slightly injure both Sanok and Soma before it could be isolated completely.&lt;br /&gt;
&lt;br /&gt;
[[File:Quol Nor and Thugs.jpg|thumb|right|200px|Quol Nor and a pair of Nausicaan Enforcers]]&lt;br /&gt;
Soma, Sanok and O&#039;Neill along with a great many members of base security tracked [[Quol Nor]] down to his place of business where he was arrested by the Security team. The Ferengi threatened that Ferengi lawyers were far superior to anything that the federation possessed and that the Assassin Hologram was sentient, a claim that would later be overturned by a federation panel of experts. The program while highly sophisticated lacked the ability to adapt beyond certain pre-programmed parameters. &lt;br /&gt;
&lt;br /&gt;
The Murderer was brought to justice.&lt;br /&gt;
&lt;br /&gt;
==Mission Sixteen: [[Just Another Saturday Night]]==&lt;br /&gt;
&lt;br /&gt;
[[File:Vexarak Spoiler.png|thumb|left|200px|A Vexarak Spoiler]]&lt;br /&gt;
&lt;br /&gt;
While on shore leave aboard [[Starbase 989]] Captain Salid and the crew of the Rosenante are tied up in a crisis unlike any other that they have faced. &lt;br /&gt;
&lt;br /&gt;
The [[Tellarite]] freighter [[Moarvol]] inadvertently managed to bring a colony of [[Vexarak Spoiler]]s aboard the starbase in a shipment of &lt;br /&gt;
&lt;br /&gt;
[[Magnesite]] ore collected from the [[Zeta Draconis System]].&lt;br /&gt;
&lt;br /&gt;
These parasites consume metals and feed off of energy that they consume from it&#039;s breakdown. They are also capable of feeding from raw plasma.&lt;br /&gt;
&lt;br /&gt;
As a New Year&#039;s Party was underway on the Promenade, the Spoilers escaped their holding bin and began to ingest critical components of the starbase&#039;s power distribution system. This resulted in a cascade failure that plunged the starbase into complete power failure.&lt;br /&gt;
&lt;br /&gt;
When inhabitants of the starbase realized that the back up systems were not coming on-line they [[riot]]ed. Several members of the ship&#039;s crew along with members of the crew serving aboard the [[USS Boudicca]], were celebrating at [[The County Cork]] during the incident.&lt;br /&gt;
&lt;br /&gt;
When riots broke out, they were forced to defend themselves as well as attempt to restore orders and emergency services.&lt;br /&gt;
&lt;br /&gt;
Over the course of the next twenty-four hours, crews from both starships worked in concert to provide services, repairs and power to the starbase. Eventually, several methods were devised to deal with the infestation. Over the following weeks repairs to the starbase were conducted.&lt;br /&gt;
&lt;br /&gt;
After the incident Ahmed was asked and accepted the honor of marrying his long-time friend [[Thomas Jackson]] to [[Dahlia Jackson]] a woman that he had married earlier by [[Ferengi]] contract. The marriage was a formality to honor Jackson&#039;s [[human]] heritage. The ceremony took place at [[Rothal Chapel]] aboard [[Starbase 989]].&lt;br /&gt;
&lt;br /&gt;
==Mission Seventeen: [[Once More Into The Breach]]==&lt;br /&gt;
[[File:Dovek II.jpg|thumb|250px|right|Dovek II]]&lt;br /&gt;
After the near destruction of [[Starbase 989]], the crews of the [[USS Boudicca]] and the [[USS Rosenante]] were ordered to form a Task Force under the command of [[Rank|Captain]] [[Ahmed Ibn Salid]].&lt;br /&gt;
&lt;br /&gt;
After a flag level briefing, in which concerns over recent [[Borg]] activity in the [[Dovek II|Dovek System]], Captain Salid ordered the two ships of the task force immediately underway to the area of Borg activity for the purpose of locating the Borg forces there and determining the nature of their actions.&lt;br /&gt;
&lt;br /&gt;
Salid ordered the two ships to enter the system in such a manner as to utilize the natural formations to aid in the covert approach of the two ships. With the bulk of the Borg activity taking place in orbit around [[Dovek II]], salid and the crew of both ships begin to do research in the hopes of predetermining the potential threat of the Borg Activity.&lt;br /&gt;
&lt;br /&gt;
From the very beginning there were concerns, as a new type of Borg vessel, designated a [[Borg Pyramid]] was seen accompanying a [[Borg Tactical Cube]]. This was a strong indicator to Salid that the mission was sensitive and possibly militaristic in nature. &lt;br /&gt;
&lt;br /&gt;
When later research proved that the Dovek system had once been a part of the now extinct, but once very technologically advanced [[Tkon Empire]], Ahmed&#039;s worst fears came to the forefront.&lt;br /&gt;
&lt;br /&gt;
Upon arriving in the Dovek System, Salid ordered both ships to remain hidden behind Dovek II&#039;s only moon. From there a series of reconnaissance probes were launched in an attempt to gather information remotely. This failed due to the Borg&#039;s use of an [[Antiproton]] weapon for the purpose of large scale excavation on the planet&#039;s surface.&lt;br /&gt;
[[File:Beam attack on planet.jpg|thumb|left|300px|The Antiproton beam strikes Dovek II]]&lt;br /&gt;
Blinded due to the [[Subspace|Subspace Interference]], Salid moved forward with a plan to launch the [[Lorimar Class Runabout]] Lorimar, on an intelligence gathering mission. The runabout was performing well, apparently unheeded by the Borg [[starship]]s until [[Rank|Lieutenant]] [[Detron Trei]] managed to make contact with the [[Borg Collective]] in an attempt to cause panic amongst the [[Borg Drone]]s.&lt;br /&gt;
&lt;br /&gt;
Instead of causing panic, despite orders to not interfere, the telepathic contact made the Borg leader [[Volus]] aware of the [[Federation]] presence in the system. He ordered the Runabout attacked, and as a result the vessel crash-landed on the surface of [[Dovek II]].&lt;br /&gt;
&lt;br /&gt;
It was around this time that the Borg also uncovered their apparent goal, a [[Tkon Nanosphere]] that held incredible potential as a weapon to be used to assimilate [[Earth]].&lt;br /&gt;
&lt;br /&gt;
Now faced with a pair of problems, Salid ordered two separate missions. The first to rescue any crash survivors, while the second would cause plausible asset denial of the sphere from the Borg through the deployment of an [[antimatter]] mine.&lt;br /&gt;
[[File:Mine Detonation.jpg|thumb|250px|right|The Antimatter Mine detonating on Dovek II]]&lt;br /&gt;
With The Borg capital ship&#039;s positioned in such a way as to block any attempts at either mission, Salid ordered both the [[USS Rosenante]] and the [[USS Boudicca]] to act as a screening force against the Borg vessels in an attempt to drawn them away from the [[planet]].&lt;br /&gt;
&lt;br /&gt;
The two ships of the small task force attacked the Borg forces and successfully caused them to displace their position, which allowed the two away teams to penetrate the planet&#039;s atmosphere and carry out their missions.&lt;br /&gt;
&lt;br /&gt;
The crash survivors were rescued and the Antimatter mine deployed, and salid had thought that the Borg operations were thwarted until indications were seen that the [[Borg]] were opening a [[Temporal Vortex]]. realizing that the Collective intended to assimilate the device in the past, Salid ordered both the [[Federation]] [[starship]]s to follow and engage.&lt;br /&gt;
&lt;br /&gt;
On the other side of the vortex, the Federation ships found themselves in the Age of Makto, near the end of the [[Tkon Empire]]. They managed to destroy both the [[Borg Pyramid]] and the [[Borg Tactical Cube]], but not before both ships were boarded during the fight, and [[Borg Drone]]s sent to the surface of the planet, where assimilation of the [[Tkon Nanosphere]] began.&lt;br /&gt;
[[File:Temporal Vortex.jpg|thumb|left|300px|A Temporal Vortex]]&lt;br /&gt;
Fighting a desperate defensive action for their ships, the Federation crews were unable to prevent the [[assimilation]] of the nanosphere. As the Sphere lifted off the planet, Salid ordered one final ditch attempt to purge the two ships of Borg, using a specialized code that attacked the [[Borg]] [[Nanoprobe]]s.&lt;br /&gt;
&lt;br /&gt;
Despite an assassination attempt on his life and with both ship&#039;s free of Borg influence, and the nanosphere opening another [[Temporal Vortex]] Salid once again ordered pursuit.&lt;br /&gt;
&lt;br /&gt;
This time the two ships ended up in Earth&#039;s prehistoric past during a period called the [[Cretaceous Period]]. The two ships were unable to deal any damage to the [[Tkon]] device as long as it&#039;s shields remained operational, so Salid ordered a small elite security force to beam aboard the ship using a theoretical Transporter algorithm.&lt;br /&gt;
[[File:Chicxulub close impact.jpg|thumb|250px|right|The impact with the crust of the planet]]&lt;br /&gt;
A tremendous fight ensued and the away team was barely beamed off the sphere, before the combined firepower of the [[USS Boudicca]] and the [[USS Rosenante]] destroyed it. Along with the destruction of the sphere came that of the Borg leader [[Volus]] and the Tkon scientist [[D&#039;askto]] who had joined forces with the away team.&lt;br /&gt;
&lt;br /&gt;
Although they had destroyed the most immediate threat of assimilation in [[Earth|earth&#039;s]] ancient past, the bulk of the sphere rained down on the planet nearly wiping out all life there.  Ironically, it was this event that wiped out the dinosaurs and allowed [[Human|Humanity]] to evolve.&lt;br /&gt;
&lt;br /&gt;
After several days of repairs and hard work, The combined crews managed to activate the Borg Temporal equipment that was left behind by the Borg Occupation of their ships and used it to return home to the present.&lt;br /&gt;
&lt;br /&gt;
The two ships then limped home to a hero&#039;s welcome.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Mission Eighteen: [[Personal Logs]]==&lt;br /&gt;
With the refit of the [[USS Rosenante]] underway after the battle at [[Dovek II]], Ahmed decided to take some time off and enjoy some friendly competition in the boxing arena on [[Starbase Geneva]].  However things did not go according to plan when he was requested by the [[Rank|Admiralty]] to participate in the general mast hearings for [[Detron Trei]] and [[Andrew Elliot Maddox]], two officers that were under his command during the Dovek II incident.&lt;br /&gt;
[[File:S31.jpg|thumb|left|300px|The symbol for Section 31]]&lt;br /&gt;
He agreed, and after some deliberation a series of disciplinary actions were undertaken against both the officers. He was later to discover that [[Rank|Captain]] [[Alan Durand]] had resigned from the fleet as a result of his actions at Dovek, despite the fact that Salid and other members of the general Admiralty did not feel his performance was inadequate to the situation.&lt;br /&gt;
&lt;br /&gt;
This temporarily left Salid in command of the [[USS Boudicca]] as well as the [[USS Rosenante]] until [[Rank|Captain]] [[Calvin Capps]]  arrived to take command of the Boudicca.&lt;br /&gt;
&lt;br /&gt;
During this time, [[Rank|Commander]] [[Thomas Jackson]] was reassigned to the USS Boudicca as her first officer, displacing her prior first Officer, [[Rank|Commander]] [[Jennifer Caskie]].&lt;br /&gt;
&lt;br /&gt;
For reasons unclear, Caskie was relieved of her command position and reassigned to the Rosenante as their [[Medical Officer|Chief Medical Officer]]. Ahmed was glad to see her return to the ship.&lt;br /&gt;
&lt;br /&gt;
Also during this Ahmed found himself suddenly involved in a situation with [[Section 31]], when they kidnapped a member of his crew, [[Rank|Ensign]] [[Jessica Signos]] after [[Ahmed Ibn Salid]] had reported her dual nature to [[Starfleet Intelligence]].&lt;br /&gt;
&lt;br /&gt;
The kidnapping was actually a ploy by SFI to flush out the [[Section 31]] Operatives on [[Starbase Geneva]]. Salid became involved when he felt that his officer was placed at undue risk as a result of SFI&#039;s slow response to the affectation of her rescue.&lt;br /&gt;
[[Image:Ranger Patch.png|thumb|right|300px|The duty patch of the Starfleet Rangers]]&lt;br /&gt;
Along with [[Eian O&#039;Neill]], his father [[Liam O&#039;Neill]] of the [[USS Kelman]], [[Katherine &#039;Kitty&#039; Fisher]], and [[Chance Raschen]], Salid put together a rescue team in an attempt to affect her release and to capture or eliminate the [[Section 31]] operatives on the station.&lt;br /&gt;
&lt;br /&gt;
The location of the hostage was located in a phased portion of the starbase, and as soon as the location rejoined normal space, Salid and the others beamed in to rescue Signos.&lt;br /&gt;
&lt;br /&gt;
The operation was a success, capturing one Section 31 Operative,  and eliminating almost all of the others. Only [[George Hayden, Jr.|George Hayden]] the cells handler managed to escape the station.&lt;br /&gt;
&lt;br /&gt;
However, after having O&#039;Neill work up a psychological profile for Hayden, a plan was put into place to draw the cell handler back to [[Starbase Geneva]]. Putting himself into a position to illicit irritation and to appear smug at his victory over Hayden, Salid was able to draw the man back into the Starbase.&lt;br /&gt;
&lt;br /&gt;
Hayden however, was not sloppy. He had taken extreme measures to protect himself, and this time, he used a holodeck to mask his presence. He managed to kidnap Salid, and for a short while torture him until [[Eian O&#039;Neill]] managed to fix the Captain&#039;s location.&lt;br /&gt;
&lt;br /&gt;
An assault team [[transporter|beamed in]] to the area and captured Hayden. This operation proved to be a linch-pin for preventing any formal charges from SFI to be levied against Salid and his officers. It did unfortunately put them on Section 31&#039;s radar as potential threats, since they were now aware of their illicit existence.&lt;br /&gt;
&lt;br /&gt;
As a direct result of this operation, Salid, transferred, [[Mike Rosenbauer]] to act as his Yeoman, in an effort to provide himself with a bodyguard of some skill. It was a task for which the former [[Starfleet Rangers|Starfleet Ranger]] was well suited.&lt;br /&gt;
&lt;br /&gt;
==Mission Nineteen: [[The Third Law]]==&lt;br /&gt;
&lt;br /&gt;
While continuing on their mission to explore [[Sector 6309]], the crew of the  Rosenante discovered a rogue planet, which they later discovered was named [[Solyon]]. &lt;br /&gt;
&lt;br /&gt;
Excited about the possible history-making discovery, Captain Salid ordered three teams down to conduct scientific, geological and biological exploration of the unusual planetary body.&lt;br /&gt;
&lt;br /&gt;
While the away teams were on the planet&#039;s surface, Salid ordered the Stellar cartography department to attempt to project Solyon&#039;s course as well as extrapolate it&#039;s path of travel prior to discovery.&lt;br /&gt;
&lt;br /&gt;
Within hours, it was determined that the [[Rogue Planet]] would be passing through a [[Binary stars|binary star system]] which contained an inhabited planet, known as [[Asrai Prime]]. With the planet&#039;s inhabitants, the [[Asrai]], only at a pre-industrial level of technology, a bit of a moral issue arose. Technically, if the Asrai were unaware of other species or if they had not developed any technology akin to warp drive, then they would, under the auspices of the [[Prime Directive]] be left to their extinction.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
{| class=&amp;quot;toc color&amp;quot; style=&amp;quot;border:3px solid goldenrod;&amp;quot;align=&amp;quot;center&amp;quot;;&amp;quot;width=246px&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:black&amp;quot; align=&amp;quot;left&amp;quot; |&amp;lt;font color=goldenrod&amp;gt; &amp;lt;small&amp;gt;{{quote|As the right of each sentient being to live in accordance with its normal cultural evolution is considered sacred, no Starfleet personnel may interfere with the normal and healthy development of alien life and culture. Such interference includes introducing superior knowledge, strength, or technology to a world whose society is incapable of handling such advantages wisely. Starfleet personnel may not violate this Prime Directive, even to save their lives and/or their ships, unless they are acting to right an earlier violation or an accidental contamination of said culture. This directive takes precedence over any and all other considerations, and carries with it the highest moral obligation. |The Prime Directive}}&amp;lt;/small&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To further complicate things somewhat, the survey teams returned to the ship with evidence that Solyon had at one point been [[terraforming|terraformed]]. This caused Captain salid to order two separate missions to be undertaken. The first would travel to Asrai Prime to see if there was any evidence that would make the Asrai exempt to the conditions of the Prime Directive. The second would remain on the rogue planet in an attempt to find a means to deviate or destroy the rogue world if a means could not be found to alter it&#039;s course.&lt;br /&gt;
&lt;br /&gt;
Due to the gravity of the situation, Captain Salid led the away team to Asrai Prime while [[T&#039;Larah Sullivan]] led the mission on the rogue planet.&lt;br /&gt;
&lt;br /&gt;
On Asrai Prime the mission began to develop in a turbulent and difficult atmosphere. The inhabitants communicated as much with body postures and gestures as they did with words. because of this, the Universal translator couldn&#039;t assist them with this type of communication.&lt;br /&gt;
&lt;br /&gt;
[[File:Asrai Prime.jpg|thumb|left|500px|Asrai Prime]]&lt;br /&gt;
&lt;br /&gt;
A misunderstanding saw Salid and Fraiser imprisoned, but in so doing, it allowed the remaining members of the away team to uncover a group of outcasts that seemed to possess advanced technology. The situation quickly became clear. The leadership of the planet had created an enforced reversion in technology while maintaining their own technological advantage to make them the rulers of the world.&lt;br /&gt;
&lt;br /&gt;
This was complicated when the Survey teams from the rosenante on the Rogue planets discovered that the planet was actually an ancient colony ship that had narrowly escaped the destruction of their home world. They were headed for Asrai Prime, the last remaining colony of their ancient civilization. &lt;br /&gt;
&lt;br /&gt;
However the massive ship was badly damaged and required extensive repairs to allow it to adjust it&#039;s mass and avoid disrupting the delicate balance of Asrai Prime.  With the engineering teams working hard on that problem, Salid and Fraiser faced execution.&lt;br /&gt;
&lt;br /&gt;
However, with the discovery of the outcasts and the situation clearly no longer constrained by the Prime Directive, [[Ben Soma]] led a rescue operation and they successfully rescued Fraiser and Salid.&lt;br /&gt;
&lt;br /&gt;
meanwhile Salid and Fraiser had learned of an ancient planetary defense weapon once designed to destroy possible asteroid strikes, that was being prepared to destroy the Rogue Planet. As it was now apparent that the leader of the Asrai was aware that Solyon was actually a colony ship, and with the new information given to Salid, it was decided to prevent the destruction of the colony ship.&lt;br /&gt;
&lt;br /&gt;
In a last-ditch effort, Salid and his away team prevented the destruction of the colony ship and helped re-establish the technological society that had been stripped from the Asrai. the Diplomatic Corps opened an embassy on Asrai prime to help the new Asrai leadership re-integrate the long-neglected masses of the planet, in effect preventing the extinction of the Asrai people.&lt;br /&gt;
&lt;br /&gt;
==Mission Twenty: [[The Captain&#039;s Cotillion]]==&lt;br /&gt;
[[File:Salid-cotillion.jpg|thumb|right|500px|Captain Salid at the Cotillion, serving drinks.]]&lt;br /&gt;
&lt;br /&gt;
After the completion of the mission to save [[Asrai Prime]] the crew of the [[USS Rosenante]] moved into a support role for the new government of that planet. With the institutionalization of a new ruling system headed by the more technologically advanced Asrai from [[Solyon]], Ahmed was determined to insure  a series of programs that would help bring the remainder of the population into line with the new leaders of that planet.&lt;br /&gt;
&lt;br /&gt;
To that end, each of the departments began a program of assisting in building a knowledge infrastructure that the planet could then develop and expand on a planetary basis. To this end, medical databases, civil engineering databases and diplomatic databases have been supplied to the new government.&lt;br /&gt;
&lt;br /&gt;
With the civilization most recently believed to be under the protection of the [[Prime Directive]], which was disproven with the realization that [[Solyon]] was a warp capable colony ship, the [[Federation Diplomatic Corps]] was ordered by [[Starfleet Command]] to send special teams to aid the [[Asrai]] in their modernization efforts. &lt;br /&gt;
&lt;br /&gt;
To celebrate the new relationship and the mutual support between the [[UFP]] and the government of [[Asrai Prime]], [[Rank|Captain]] [[Ahmed Ibn Salid|Salid]] decided to implement a new tradition aboard the Rosenante in the form of a formal dance, which he dubbed the &amp;quot;Captain&#039;s Cotillion&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The affair was punctuated by the appearance of many of the ship&#039;s crew appearing in elaborate outfits, and taking a night on the town. The event filled Cargo Bays one and Two, which had been retrofitted by [[Rank|Commander]] [[Steven Wade Matrix|Matrix]], [[Rank|Lieutenant]] [[Ben Soma|Soma]], [[Rank|Lieutenant]] [[Thomas Jackson|Jackson]] and [[Rank|Lieutenant]] [[Sanok]].&lt;br /&gt;
&lt;br /&gt;
The prevent for the women of the crew took place on the holodeck, where [[Jessica Signos]] invited them all to a Japanese Bath house program for a day of pampering, gossip and spa treatments.&lt;br /&gt;
&lt;br /&gt;
Not all was well, however, as on the eve of the event, Signos and [[Eian O&#039;Neill|O&#039;Neill]] broke off their relationship due to &amp;quot;Lily&amp;quot;. A further incident took place when [[Tayla Fraiser]] inadvertently made telepathic contact with Signos, and was affected by &amp;quot;Lily&#039;s&amp;quot; presence, sending her into a panic attack that later caused her to attack [[Parker Davis]].&lt;br /&gt;
&lt;br /&gt;
This period of time saw the addition of a couple of new crew to the roster as well. [[Rank|Lieutenant]] [[Lanista]] , formerly from the [[USS Mithrandir]] and on return from a 5-year mission in [[Klingon]] space, was assigned to the [[USS Rosenante]] as their newest Chief Science Officer. Lieutenant [[Viskhard]], as a result of this new addition was reassigned to the position of Assistant Chief Science Officer. Another addition to the crew was [[Rank|Lieutenant]] [[Nayeli]], a member of the [[Starfleet Judge Advocate General Corps (JAG)|JAG Corps]]. Her purpose was to look into the possible violations of the [[Prime Directive]] on [[Asrai Prime]]. She was assigned as a standing member of the crew in reflection to Starfleet&#039;s concern over the matter. As a result, Captain Salid has no choice but to keep her aboard.&lt;br /&gt;
&lt;br /&gt;
The crew not only gained  new crew, but sadly have seen some transferred off the ship as well. [[Rank|Commander]] [[T&#039;Larah Sullivan]] was reassigned to the [[Starfleet Marine Corps]], where she assumed the rank of [[Rank|Lieutenant Colonel]]. She was joined by Lieutenant Masters. This left the position of First officer open, and [[Rank|Captain]] [[Ahmed Ibn Salid]] saw no reason not to promote his new Second and Third Officers into empty positions. As such, [[Rank|Lieutenant]] [[Ben Soma]] was promoted to First Officer and advanced in rank to [[Rank|Lieutenant Commander]], while [[Sanok]] was promoted to Second Officer. At this time Salid has not yet selected a third officer for the Rosenante.&lt;br /&gt;
&lt;br /&gt;
Not to be outdone, several members of the Rosenante&#039;s senior staff had their photograph taken for nostalgia&#039;s sake.&lt;br /&gt;
&lt;br /&gt;
==Mission Twenty-one: [[The Veil of the Sky]]==&lt;br /&gt;
[[File:Comet2.jpg|thumb|right|400px|Comet Holladay]]&lt;br /&gt;
&lt;br /&gt;
After [[The Captain&#039;s Cotillion]], the [[USS Rosenante]] was once again underway to continue her survey of [[Sector 6309]] as she had been ordered.  During this time, the crew encountered an unusual [[comets|comet]], which later became known as [[Comet Holladay]] in honor of the scientist who detected it by long-range scans.  Detailed scans and trajectory studies were underway, when an urgent message from [[Starfleet Command]] was received.&lt;br /&gt;
&lt;br /&gt;
A hostage situation had developed on the planet [[Beta Aquillia IV]] a world that supplied the [[Federation]] with a vast majority of the resources needed to rebuild their infrastructure and starships. the planetary government, led by President Kolath had been overthrown by a sudden and unexpected coup. The group responsible was a pro-isolationist group named [[Veil of the Sky]].&lt;br /&gt;
&lt;br /&gt;
During this coup, their leader, [[Habrii]] took Federation [[Ambassador]] [[Joanne Turner]] and her embassy staff hostage. The Rosenante was dispatched to negotiate her release and if possible to determine if there was outside support for the Veil.&lt;br /&gt;
&lt;br /&gt;
Upon their arrival, Salid attempted to make contact with the current government. He was at first ignored. determined to safe-guard refugees displaced by the conflict, especially those with Federation citizenship, Salid sent his crew down to the capital city of Joba to establish a safe-zone and a refugee camp to tend to the needs of the displaced.&lt;br /&gt;
&lt;br /&gt;
To make things more complicated a [[Skorr]] [[Worldripper Class]] warship named the [[Skysplitter]] arrived. it seemed that a Skorr Ambassador was also taken hostage and [[Ambassador]] [[Dralar]] had been sent to recover him. This made the situation potentially unstable.&lt;br /&gt;
&lt;br /&gt;
After the arrival of the Skorr vessel, [[Ben Soma]] led a negotiation team down to the planet with no real success. The political views of the Veil leadership made diplomacy all but impossible. However, the [[Aquillian]] ambassador, Tzorn began to make indications that he would aid the Rosenante crew in locating their ambassador in return for asylum.&lt;br /&gt;
&lt;br /&gt;
[[Chance Raschen]] and [[Mike Rosenbauer]] were assigned to covertly attempt to locate the ambassador on the planet. Mike managed to persuade a Veil member named [[Sien]] to join the Federation&#039;s cause, while chance uncovered some signs of [[Cardassian]] Involvement.&lt;br /&gt;
[[File:Atlantis Station.jpg|thumb|300px|left|Atlantis Station]]&lt;br /&gt;
&lt;br /&gt;
A series of suicide bombings at the refugee camp forced a breakdown in communication between the Veil and the Federation.  Refugee support operations became disaster relief. At Salid&#039;s request [[Dralar]] sent Skorr troops to shore up the Federation position.&lt;br /&gt;
&lt;br /&gt;
Meanwhile on [[Atlantis Station]], [[Niambh McNulty]] allowed the Rosenante&#039;s crew to establish a [[Command Control and Communications Center]]. From there the crew could more easily communicate and organize disaster relief.&lt;br /&gt;
&lt;br /&gt;
As the investigation continued, [[Steven Wade Matrix|Matrix]] and Peter Cohen discovered signs of Romulan involvement. The situation was quickly becoming murky, and it was even more unclear who was truly involved in supporting the Veil.&lt;br /&gt;
&lt;br /&gt;
When word went out that [[Alaya]] the lieutenant of the [[Veil of the Sky]] was responsible for the suicide attacks on the refugee camp, [[Habrii]] ordered her arrested. She was captured, but her escape was secured by Gul [[Matan]] of the [[Obsidian Order]]. Alaya then led a counter-coup against Habrii, capturing him and seizing control of the government.&lt;br /&gt;
&lt;br /&gt;
Meanwhile through subterfuge, the location of [[Ambassador]] Turner and the [[Skorr]] Ambassador became known. The Skorr rescued their Ambassador with the aid of [[Katherine &#039;Kitty&#039; Fisher]], while [[Jessica Signos]] led the rescue of the [[Federation]] Ambassador.&lt;br /&gt;
&lt;br /&gt;
[[File:Camp explosion.jpg|right|thumb|300px|One of the explosions at the refugee camps]]&lt;br /&gt;
&lt;br /&gt;
At the same time, [[Ben Soma]] led a team to extract the [[Aquillian]] Ambassador Tzorn as agreed. With all these actions underway, Salid was also on guard for any [[Cardassian]] or [[Romulan]] interference.&lt;br /&gt;
&lt;br /&gt;
Instead, however, he was forced to deal with the [[Veil of the Sky]] militia troops. [[Alaya]] had ordered them to assault [[Atlantis Station]] as well as the refugee camp protected by the Federation.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Salid utilized the ship&#039;s [[phaser]]s et to heavy stun to slow down the infantry assault against the camp. in addition, he used low-yield photon torpedoes to capsize the boats bombarding Atlantis Station.&lt;br /&gt;
&lt;br /&gt;
Once the refugees were evacuated, Salid recalled his crew. As his orders were to not get directly involved in the political struggle for control of the planet, the Rosenante then departed. But not before McNulty destroyed Atlantis station and the president in Exile Kolath, disappeared into the urban underground to establish a revolutionary movement to regain control of the government of Beta Aquillia IV.&lt;br /&gt;
&lt;br /&gt;
For the crew of the Rosenante, it was a bittersweet victory.&lt;br /&gt;
&lt;br /&gt;
==Mission Twenty-two: [[A Port in the Storm]]==&lt;br /&gt;
&amp;lt;strong&amp;gt;&amp;lt;font color=goldenrod&amp;gt;COMING SOON!&amp;lt;/font&amp;gt;&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Awards and Commendations: ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
image:Cross_of_Fire.gif|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded Cross of Fire: For actions above and beyond the call of duty during the battle for the MDP on stardate 2407.07.09&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
image:Combat_Action_Ribbon.gif|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded Combat Action Ribbon: For services rendered in freeing Cait Prime for the Occupation of Doentiz forces and it&#039;s illegal and immoral experiments.&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
image:Captain&#039;s_Commendation.jpg|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded Captains Commendation: For actions during and after the battle for the MDP, stardate 2407.07.09&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
image:Captain&#039;s_Commendation.jpg|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded Captains Commendation: Awarded on behalf of the Cartenian Commonwealth for Services rendered in the Rescue of Prince Khamal from the Orion Syndicate on Stardate 2408.03.15&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Image:Order_of_Unity-_Ribbon.jpg|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded The Order of Unity: Awarded in commemoration of services rendered during the Federation Civil War.&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
image:Rib19.gif|&amp;lt;small&amp;gt;Awarded Squadron Commander&#039;s Commendation: Awarded on Stardate 2414.02.14 for actions above and beyond the call of duty, critical to the success of the Mission to destroy the T&#039;Kon Sphere held by the Borg.&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
File:Rib05.gif|&amp;lt;small&amp;gt;&#039;&#039;&#039;Awarded Medal of Distinction: Awarded Stardate 2414.02.16, for gallantry in the line of duty against forces hostile to the United Federation of Planets.&#039;&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Rosenante Crew Roster}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Characters]][[Category:History]][[Category:Civil War]][[Category: Mirror Universe]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Template:USS_Rosenante_Missions&amp;diff=55869</id>
		<title>Template:USS Rosenante Missions</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Template:USS_Rosenante_Missions&amp;diff=55869"/>
		<updated>2012-09-05T16:15:55Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
{| width=80% class=&amp;quot;toccolours&amp;quot; style=&amp;quot;float:center; background:black; background-color: #FFA500; border: 0 ;&amp;quot; cellspacing=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;background:black&amp;quot; align=&amp;quot;center&amp;quot; colspan=3 | &amp;lt;strong&amp;gt;&#039;&#039;USS Rosenante Missions&#039;&#039; &amp;lt;/strong&amp;gt;&lt;br /&gt;
| rowspan=4 style=&amp;quot;background:black&amp;quot; | [[Image:Rosenante-Alt-2up.jpg|120px|thumb|centre|The [[USS Rosenante]]]] &lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;font-size: 90%; background:black&amp;quot; colspan=3|&#039;&#039;&#039;Missions:&#039;&#039;&#039; [[Picking up the Pieces]] | [[A Fine and Private Place]] | [[Furlough]] | [[Letters of Marques]] | [[Fields of Elysium]] | [[Homecoming]] | [[Into the Darkness, Go I]] | [[Equals and Opposites]] | [[The Quondam Season]] | [[The Gilded Man]] | [[Touch of the Eidolon]] | [[Just Another Saturday Night]] | [[Once More Into The Breach]] | [[Personal Logs]] | [[The Third Law]] | [[The Captain&#039;s Cotillion]] | [[The Veil of the Sky]]  | [[A Port in the Storm]] | [[The Raven&#039;s Nest]] | [[Through the Looking Glass]] **Underway** [[Lest We Forget]] **Coming Soon**&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Template:USS_Rosenante_Missions&amp;diff=55868</id>
		<title>Template:USS Rosenante Missions</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Template:USS_Rosenante_Missions&amp;diff=55868"/>
		<updated>2012-09-05T16:15:44Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
{| width=80% class=&amp;quot;toccolours&amp;quot; style=&amp;quot;float:center; background:black; background-color: #FFA500; border: 0 ;&amp;quot; cellspacing=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;background:black&amp;quot; align=&amp;quot;center&amp;quot; colspan=3 | &amp;lt;strong&amp;gt;&#039;&#039;USS Rosenante Missions&#039;&#039; &amp;lt;/strong&amp;gt;&lt;br /&gt;
| rowspan=4 style=&amp;quot;background:black&amp;quot; | [[Image:Rosenante-Alt-2up.jpg|120px|thumb|centre|The [[USS Rosenante]]]] &lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;font-size: 90%; background:black&amp;quot; colspan=3|&#039;&#039;&#039;Missions:&#039;&#039;&#039; [[Picking up the Pieces]] | [[A Fine and Private Place]] | [[Furlough]] | [[Letters of Marques]] | [[Fields of Elysium]] | [[Homecoming]] | [[Into the Darkness, Go I]] | [[Equals and Opposites]] | [[The Quondam Season]] | [[The Gilded Man]] | [[Touch of the Eidolon]] | [[Just Another Saturday Night]] | [[Once More Into The Breach]] | [[Personal Logs]] | [[The Third Law]] | [[The Captain&#039;s Cotillion]] | [[The Veil of the Sky]]  | [[A Port in the Storm]] | [[The Raven&#039;s Nest]] | [[Through the Looking Glass]]**Underway** [[Lest We Forget]] **Coming Soon**&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Into_the_Darkness,_Go_I&amp;diff=55867</id>
		<title>Into the Darkness, Go I</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Into_the_Darkness,_Go_I&amp;diff=55867"/>
		<updated>2012-09-05T16:13:32Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* Act Six: Finale */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Coming Soon!&lt;br /&gt;
&lt;br /&gt;
==Act One: Teaser==&lt;br /&gt;
[[Image:Rose2.png|thumb|right|250px|ISS Rosenante]]&lt;br /&gt;
The ISS Rosenante is assigned by [[Regent]] [[Admiral Doenitz|Doenitz]] to travel to the Sunali system. Earlier in 2407 the Sunali people defected to the invading [[Klingon-Cardassian Alliance]]. The system did not put up any resistance to the invaders and as such Doenitz feared that the other members of the newly formed [[Imperial Union of Planets]] would consider following suit. This action of course would lead to the complete defeat of the IUP. With this in mind the [[ISS Rosenante]] was dispatched to make an example of the Sunali.&lt;br /&gt;
&lt;br /&gt;
[[Image:Sunali Sun Destruction.jpg|thumb|left|250px|The Destruction of the Sunali star]]&lt;br /&gt;
By the time that the Rosenante arrived  The Klingon-Cardassian Alliance had already  begun shifting a large task force into the system. This task force was preparing for a military attack into the heart of the IUP.&lt;br /&gt;
&lt;br /&gt;
The enemy vessel present in  the system were:&lt;br /&gt;
&lt;br /&gt;
Twenty-two [[Klingon]] ships:&lt;br /&gt;
*12 [[Bird-of-Prey|K&#039;Vort Class, Bird-of-Prey]]s&lt;br /&gt;
*6 [[Bird-of-Prey|B&#039;rel Class Bird-of-Prey]]s &lt;br /&gt;
*4 modified [[D7 Class Battle Cruiser]]. &lt;br /&gt;
&lt;br /&gt;
There  are also [[Cardassian]] [[starship]]s in the system.&lt;br /&gt;
&lt;br /&gt;
* 18 [[Galor Class]] &lt;br /&gt;
&lt;br /&gt;
On the Planet, [[Sunali II]] there was a population of 18 million inhabitants.&lt;br /&gt;
&lt;br /&gt;
The ISS Rosenante moved into position by passing the mine perimeter that was only partially completed by the Cardassians. The ship them activated and launched the [[Omega Device]] towards the Sunali Star.&lt;br /&gt;
&lt;br /&gt;
The Rosenante then turned, and fought it&#039;s way pasts several enemy ships and was just barely able to escape the system just as the Omega Device detonated. The resultant explosion destroyed the entire system along with the enemy task force. An unexpected side affect of the Omega affect was an interaction of the energy waves created by the [[Omega Molecule]]&#039;s destruction interacting with the [[Rosenante Class|Spiral Warp Drive ]] of the Rosenante. Somehow this interaction forced the [[Mirror Universe]] ISS Rosenante through an [[Interphasic Rift|Interphasic Tunnel]] which deposited it into the Prime Universe, just outside the Sunali System.&lt;br /&gt;
&lt;br /&gt;
==Act Two: Prologue==&lt;br /&gt;
[[Image:Rosenante-Alt-2up.jpg|thumb|right|250px|USS Rosenante]]&lt;br /&gt;
Unknown to the [[USS Rosenante]] their mirror counterpart has laid in a course to [[Bardon Alpha]]. The Rosenante&#039;s [[Rank|Captain]] [[Ahmed Ibn Salid]] holds an emergency meeting with his three senior most officers, [[Jennifer Caskie]], [[T&#039;Larah Sullivan]] and [[Jon Nayati]]. He explains to them that he has just ordered the USS Rosenante off mission to investigate some critical intelligence. He does not reveal to the the nature of this intelligence, but simply asks for their trust in this issue. Salid states that he is aware that he is breaking regulations and that he realizes that there will be consequences if he is proven to be wrong. However he states that he can not take the chance that the intelligence turns out to be accurate without investigating it. It is his belief that the intelligence he has received could threaten not only the [[United Federation of Planets]] but also the [[Alpha Quadrant]]. All three officers agree to trust Salid&#039;s judgment.&lt;br /&gt;
&lt;br /&gt;
Meanwhile back on Earth, Captain Saleke, former Commanding Officer of the [[USS Hades]] is called to a lunch with [[Rank|Vice Admiral]] [[Errol Heatherby]]. The admiral begins to explain that he has reason to believe that there may be a conspiracy inside the [[Starfleet Command|Admiralty]]. He cites the bizarre fact that several prior Doenitz supporters are now Starship captains in the border region between the [[United Federation of Planets]] and the [[Cardassian Union]]. fearing that there could well be a potential to allow conspiracy to thrive under such conditions, he orders Saleke to take command of the [[USS Furious]], a [[Prometheus Class]] [[starship]] and proceed to the [[Ikev Sector]]. He also warns Saleke that the previous Captain of the Furious was killed in a freak [[Transporter]] accident and that the [[Vulcan]] Captain should proceed with caution.&lt;br /&gt;
&lt;br /&gt;
==Act Three: [[Bardon Alpha]]==&lt;br /&gt;
[[Image:Bardon Alpha.jpg|thumb|left|250px|Bardon Alpha]]&lt;br /&gt;
&lt;br /&gt;
===The Attack===&lt;br /&gt;
&lt;br /&gt;
The ISS Rosenante arrived at the Bardon mining Facility with the intention of stealing a shipment of highly refined [[Boronite]] ore. Captain Salid opened a channel and demanded that the ore be turned over to them. When the facilities administrator, Alix Sorvex, declined, Salid ordered the facility attacked and all personnel except one killed. He ordered an away team to the surface to carry out his orders.&lt;br /&gt;
&lt;br /&gt;
The Assault team was lead by the [[Mirror Universe]] version of [[Jennifer Caskie]]. Other members of the Mirror Universe crew, including Mike Rosenbauer and Aleesa Wyler accompanied her.  Rosenbauer commanded a security team called [[Mike&#039;s Maniacs]], which consisted of  Mirror Universe versions of Sodra, Tyrone Cooper, Mosh, T&#039;Vyr and Eva Saint-Jean. There were also two disposable members of the [[ISS Rosenante]]&#039;s Science team sent along to locate the boronite. once theier job was completed, they were executed and their bodies left behind.&lt;br /&gt;
&lt;br /&gt;
During the raid, Jennifer Caskie murdered the administrator with a bladed-weapon, which seemed to be the preferred method of execution. All other members of the facility crew were killed with the exception of technician Dallas, who was seriously injured by [[Mike Rosenbauer]], and Talia Lorenzo who had managed to avoid detection by hiding inside the facility&#039;s computer core ventilation system.&lt;br /&gt;
&lt;br /&gt;
===The Distress Signal===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
While enroute to the [[Ikev Sector]] the [[USS Rosenante]] intercepted a distress communication from the Bardon Alpha Mining Facility. Captain Salid ordered an intercept course set and the Rosenante raced to respond to the signal. The signal itself was standard except for it&#039;s contents.  The signal claimed that they facility was under attack by a Federation starship, which was identified as the Rosenante. This was not possible as the Rosenante was several hours away when the attack took place.&lt;br /&gt;
&lt;br /&gt;
When the ship arrived at the Bardon Alpha system, they detected no ships and received no replies to their hails.&lt;br /&gt;
&lt;br /&gt;
Wishing to get to the bottom of the signals claim and to search for survivors, [[Rank|Captain]] Salid ordered an away team to the planet&#039;s surface to investigate.&lt;br /&gt;
&lt;br /&gt;
The away team consisted of:&lt;br /&gt;
&lt;br /&gt;
*[[Rank|Commander]] [[Jennifer Caskie]]&lt;br /&gt;
*[[Rank|Lieutenant]] [[Jon Nayati]]&lt;br /&gt;
*[[Rank|Lieutenant]] [[Thomas Jackson]]&lt;br /&gt;
*[[Rank|Ensign]] [[V&#039;Shera]]&lt;br /&gt;
*[[Rank|Ensign]] [[Mitena Rixx]]&lt;br /&gt;
*[[Rank|Ensign]] [[Robert Smith]]&lt;br /&gt;
*[[Rank|Ensign]] [[Sam Lopez]]&lt;br /&gt;
*[[Rank|Ensign]] [[M&#039;Epak]]&lt;br /&gt;
*[[Rank|Ensign]] [[Kimiko Ichijo]]&lt;br /&gt;
*[[Rank|Ensign]] [[Mike Rosenbauer]]&lt;br /&gt;
&lt;br /&gt;
The away team beamed into the facility and immedately broke into two teams.  The first two teams began searching the area for survivors, these teams were comprised of Doctors Lopez and Ichijo as well as elements of the security team. The teams did not find any survivors on their assigned search areas but Doctor Ichijo did find a pair of bodies dressed in unusual uniforms, These two corpses were beamed back to the Rosenante for analysis. They were later discovered to belong to the two science officers from the [[ISS Rosenante]]. They had been executed by under orders from the Mirror Universe [[Jennifer Caskie]] once they had located the refined Boronite.&lt;br /&gt;
&lt;br /&gt;
The second away team consisted of the operations and Engineering team. This group consisted of Lieutenant Jackson and ensigns Rixx and Smith. The team&#039;s orders were to recover tha facility&#039;s sensor logs for study. Because of the extent of the damage, this team was forced to work there way deeper into the facility until they reached the computer core. once there, they gained access to the core and began copying the data for transfer back to the ship.&lt;br /&gt;
&lt;br /&gt;
The third team consisted of Commander Caskie, Lieutenant Nayati and Ensign Rosenbauer. They made thir way to the Administration center of the facility in the hiopes of accessing the facilities shipping manifests and security tapes. While there, they encountered the seriously wounded John Dallas. Dallas injured Rosenbauer, believing him to the be the same man who had assaulted him earlier.  in fact that person had been the [[Mirror Universe]] version of the same man. Dallas was subdued and beamed to the Rosenante for medical treatment.&lt;br /&gt;
&lt;br /&gt;
Caskie and Nayati then uncovered the production manifests and the security logs for the facility. The former showed that the facility had been refining boronite to an exceptionally refined state while the latter uncovered a video image showing Rosenbauer, Caskie and Wyler complacent in the death of the administrator and the attack on the facility.&lt;br /&gt;
&lt;br /&gt;
This information coupled with the mysterious appearance of a second Rosenante class starship, which could only have been built in secret, further convinced Captain Salid that there was indeed a high-level conspiracy ongoing.&lt;br /&gt;
&lt;br /&gt;
===The Furious Arrives===&lt;br /&gt;
&lt;br /&gt;
Despite warnings that they should leave the system by his senior officers, Captain Salid decided to remain at Bardon Alpha in the hopes of gathering some information that could give him a direction of pursuit.&lt;br /&gt;
&lt;br /&gt;
Lieutenant [[Chance Raschen]] after reviewing the telemetry data from the facilities computers managed to extrapolate a possible course for the rogue vessel. However, before it could be pursued the USS furious arrived in the system.&lt;br /&gt;
&lt;br /&gt;
The [[Prometheus Class]] [[starship]] was commanded by [[Rank|Captain]] [[Saleke]]. The [[Vulcan]] CO had once been the Commanding Officer of the [[USS Hades]] during the [[Federation Civil War]], and was renowned for his tactical skill.&lt;br /&gt;
&lt;br /&gt;
Salid was surprised to see Saleke, and suspected that if he was not a willing participant in the conspiracy concerning the creation of an [[Omega Device]] that he may well be manipulated into serving the purposes of that conspiracy. Saleke ordered the surrender of the [[USS Rosenante]], but Salid, uncertain of the Captain&#039;s true loyalties declined and attempted to flee the scene in the hopes of exhonerating the names of the crew.&lt;br /&gt;
&lt;br /&gt;
Saleke engaged the Rosenante, whom he considered attempting to escape from the scene of a crime and shot&#039;s were fired. Still reluctant to destroy the Furious due the the unknown position of Captain Saleke&#039;s affiliations, Salid ordered the long-range communications of the Furious destroyed. inital stages of the battle were ineffective. For the Furious this was caused in part because of the employment of the [[The Chimera Directive|SEDIS]] and in part by the superior shielding possessed by the [[Rosenante Class]] [[Starship]].&lt;br /&gt;
&lt;br /&gt;
However, Saleke had a trick up his sleeve. Earlier, he had ordered the modification of five quantum torpedoes so that they were equipped with a [[Cloaking device|Phased Cloaking Device]]. These torpedoes when launched against the Rosenante ignored her shileds and caused significant damage to the latter vessel&#039;s Environmental Subsystems, lifeboats, secondary phaser array, forward tractor beam emitter and caused a hull breach in main Engineering. The advantage was short lived however, when Salid managed to deplete the Furious&#039; forward shields enough to cause the vessel to veer off in order to avoid a volley of concussive photon torpedoes.&lt;br /&gt;
&lt;br /&gt;
It was a manuever that would later become known as [[The Salid Gambit]]. With the Furious deviated from her pursuit. Salid managed to get the Rosenante into the [[Magnesite]] ore filled asteroid field in the Bardon system known as [[The Mill]]. It was an area familiar to [[Rank|Lieutenant]] [[Chance Raschen]], who had often used the area to avoid or lose [[Cardassian]] pursuit during the [[Cardassian]]-[[Federation]] War. Raschen had served in the [[Irregular Federation Forces]] during the [[Admiral Doenitz|Doentiz]] regieme, before defecting to the [[52nd Fleet]]. His knowledge of the area would prove invaluable to evading the Furious. The high concentration of magnesite ore prevented the use of most navigational sensors withn the confines of the Mill, thus preventing the furious from following the Rosenante. in addition, coupled with the [[The Chimera Directive|HISS]] Stealth System, the Furious was unable to detect the Rosenante from outside the field either.&lt;br /&gt;
&lt;br /&gt;
Saleke ordered the Furious at best speed course around the field in the hopes of catching the Rosenante exitting the other side in the hopes of taking advantage of the Prometheus Class&#039; Tri-vector assault mode. However, once on the other side, the furious detected the decaying signature left by the [[The Chimera Directive|Spiral warp Drive]] of the [[ISS Rosenante]]. &lt;br /&gt;
&lt;br /&gt;
Thinking that the Rosenante had already managed to clear the field and set course for [[Hexikor Prime]], Saleke ordered the Furious to pursue. Meanwhile the USS Rosenante remained in [[The Mill]] conducting repairs.&lt;br /&gt;
&lt;br /&gt;
==Act Four: [[Hexikor Prime]]==&lt;br /&gt;
[[Image:Hexikor Prime.JPG|thumb|right|250px|Hexikor Prime]]&lt;br /&gt;
The [[ISS Rosenante]] arrived at Hexikor Alpha before either the [[USS Furious]] or the [[USS Rosenante]] could intercept her. The crew of the Mirror Universe had a clear set of objectives in mind for the attack and set about capturing them with speed and efficiency. The Mirror Universe Away Team consisted of the Following personnel:&lt;br /&gt;
&lt;br /&gt;
*Commander [[Jennifer Caskie]]&lt;br /&gt;
*Lieutenant [[Jon Nayati]]&lt;br /&gt;
*Lieutenant [[Thomas Jackson]]&lt;br /&gt;
*Ensign [[Mitena Rixx]]&lt;br /&gt;
*Ensign [[Mike Rosenbauer]]&lt;br /&gt;
*Ensign [[Robert Smith]]&lt;br /&gt;
&lt;br /&gt;
This group was tasked with the objective to locate and acquire two pieces of hardware located aboard the Hexikor Alpha facility. These were a [[Paratrinic Shield|Paratrinic Shield Generator]] And a [[Class 11 Computer|Class 11 Bioneural Computer]]. These components would be essential in defining the defensive capabilities of the [[Omega Device]].&lt;br /&gt;
&lt;br /&gt;
After the away team arrived, they encountered Doctors 12 &amp;amp; 14, the [[Bynars|Bynar]] Scientists working on the Paratrinic shield project. They also encountered [[Nathan Benoit]] a recent graduate from [[Starfleet Academy]].&lt;br /&gt;
&lt;br /&gt;
In a struggle, Benoit was attacked and overpowered by the [[Mirror Universe]] Thomas Jackson. The Mirror universe away team chose to capture Doctor 12 and use him as bait. However, Doctor 14 activated the shield generator and managed to transport an unprotected Mirror universe Jackson out into the depths of space beyond the hull of the station. The ISS Rosenante&#039;s Chief of Operations had been killed.&lt;br /&gt;
&lt;br /&gt;
Meanwhile, Rixx and Smith worked to secure the devices and when they had completed their task, they beamed the equipment back to the awaiting Mirror Universe vessel.&lt;br /&gt;
&lt;br /&gt;
It was during that time that station security showed up and a very brief exchange of phaser fire took place. The Mirror Universe group evacuated the station having secured their prize and left the area unmolested. During the Raid Captain Salid had chosen to destroy both facilities long-range communications capabilities&lt;br /&gt;
&lt;br /&gt;
[[Image:Prometheus class.jpg|thumb|left|250px|USS Furious]]&lt;br /&gt;
The USS Furious arrived a little over a day behind the ISS Rosenante&#039;s departure. Captain [[Saleke]] elected to visit the facility in an effort to ferret out additional information concerning the conspiracy alluded to by the Prime Universe&#039;s Captain [[Ahmed Ibn Salid]]. During his visit to the station the Furious&#039; CSO Holis Gralen, a [[Betazoid]] interviewed Commander [[Brian Romeo]] concerning the research of the stolen equipment. Romeo provided a perfect watertight reason for the project, citing a pre-warp culture and an attempt to study a rapidly dying star from the same system. While the evidence was solid, Holis suspected that Romeo was not being entirely truthful.&lt;br /&gt;
&lt;br /&gt;
While Saleke was conducting his investigation abord the Hexikor facility, including interviewing an injured [[Nathan Benoit]], The USS Rosenante entered the Hexikor system under cloak.&lt;br /&gt;
&lt;br /&gt;
Determined not to have a repeat of the encounter at [[Bardon Alpha]], Captain Salid chose to neutralize the threat that the Furious posed by transporting six of their primary power buses off the Furious. These power relay buses, cause the ship to lose all primary power, rendering it unable to use weapons, shields or warp drive.  Salid then ordered the surrender of the Furious but was unwilling to accept the surrender of that vessel from their First Officer Commander Erin Sloane.&lt;br /&gt;
&lt;br /&gt;
Saleke was summoned and his presence was requested aboard the Rosenante. Having been convinced by the data that he had collected thus far in his investigation, Captain Saleke informed Captain Salid that he and his ship were no longer suspects in the attack, nor were the complicit in any plot to acquire and build an Omega Device.  Saleke had, independently, arrived at the same conclusion, that the ISS Rosenante, a ship from the Mirror universe was in fact responsible for the attacks. &lt;br /&gt;
&lt;br /&gt;
It was also clear that the Mirror Universe Rosenante was following a pattern that must have been established in their own universe. Which explained how the marauding vessel knew where to acquire the components for the creation of a new Omega Device.&lt;br /&gt;
&lt;br /&gt;
After some discussions, it was decided that the USS Furious and the USS Rosenante would need to combine forces in order to counter the tactical and homicidal threat now posed by the ISS Rosenante.&lt;br /&gt;
&lt;br /&gt;
As long range scans indicated that the Mirror Universe vessel was headed for the [[Kabor Prime|Kabor System]] The Rosenante took the Furious under tow, and using their own shields to protect them, opened a Spiral warp conduit to facilitate maneuvers while the Furious conducted the reinstallation of the power relay buses.&lt;br /&gt;
&lt;br /&gt;
==Act Five: [[Kabor Prime]]==&lt;br /&gt;
[[Image:Kabor Prime.jpg|thumb|right|250px|Kabor Prime]]&lt;br /&gt;
&lt;br /&gt;
A few days after the attack on the [[Bynars|Bynar]] Facility in the Hexikor system, the [[ISS Rosenante]] appeared in the Kabor system. Thier target was a secret production facility known as [[Station Omega]]. The facility had been built by a secret research and development branch of Starfleet Sciences Division during the [[Admiral Doenitz|Doenitz]] regime.  Thier primary function was the development of an [[Omega Device]]. &lt;br /&gt;
&lt;br /&gt;
After the end of the [[Federation Civil War]] the facility went underground. Through the actions of a small group of [[Starfleet]] [[Rank|Admiral]]s, all records pointing to the existence of such a facility were erased and the personnel there continued with their research. Through covert means, the facility was equipped with large Class XII phaser batteries for defense. At the heart of the facilities power center was a stabilized [[Omega Molecule]]. The first that the Station had managed to produce.&lt;br /&gt;
&lt;br /&gt;
The ISS Rosneante arrived in the system, intent on collecting the last few remaining components of the Omega device that they needed to create their own version of the weapon. As the [[Mirror Universe]] [[Ahmed Ibn Salid]] had worked at this facility in his universe, he had intimate knowledge of the facilities existence and layout. What he had not known was that the station had been armed, as in his universe, it was not protected.&lt;br /&gt;
&lt;br /&gt;
[[Image:Omega Device.jpg|thumb|left|250px|Omega Device]]&lt;br /&gt;
&lt;br /&gt;
The Mirror universe ship was forced to subdue the facility by force, which cost them a great deal of time, narrowing the lead that they had on their Prime Universe Counterpart the [[USS Rosenante]] and the [[USS Furious]]. This delay would prove to be a great boon to the federation starship over the next few days.&lt;br /&gt;
&lt;br /&gt;
With the retrieval of the components complete, Salid ordered [[Mitena Rixx]] and [[Nathan Benoit]] to begin modifications to the base components to bring them up to specifications of the original Mirror universe version of the omega device. This involved the addition of the previously stolen [[Paratrinic Shield|Paratrinic Shield Generator]] as well as the [[Class 11 Computer| Class 11 Bioneural Computer]].&lt;br /&gt;
&lt;br /&gt;
By the time that the Federation starship had arrived, the mirror universe vessel was gone and the station destroyed. Captain&#039;s Salid and [[Saleke]] wasted no time in the system, instead following the ISS Rosenante&#039;s warp trail towards the Sunali System. With time running out, they realized that they had no choice by to confront the marauding vessel and deal with it once and for all.&lt;br /&gt;
&lt;br /&gt;
==Act Six: Finale==&lt;br /&gt;
[[Image:Homecoming.jpg|thumb|right|250px|Battle of Sunali II]]&lt;br /&gt;
&lt;br /&gt;
The [[USS Rosenante]] and the [[USS Furious]] entered the [[Sunali II|Sunali System]] to find the [[ISS Rosenante]] engaged in the wanton destruction of [[Cardassian]] merchant shipping. These ships although peaceful, had been destroyed simply because they were Cardassian.&lt;br /&gt;
&lt;br /&gt;
The USS Rsoenante ordered the Imperial starship to surrender. That vessel refused.&lt;br /&gt;
&lt;br /&gt;
What followed next was a flurry of conflict, with the Stronger [[ISS Rosenante]] dealing a tremendous amount of damage to both the [[USS Rosenante]] as well as the [[USS Furious]],&lt;br /&gt;
&lt;br /&gt;
During the conflict the Furious engaged her [[Prometheus Class|Tri-vector Attack mode]] to engage the more powerful [[Mirror Universe]] vessel. The Mirror universe [[Andrew Elliot Maddox]] managed to take over the computer of one of the Furious&#039; sections named the Courageous and overload it&#039;s warp core killing all 142 hands on board. &lt;br /&gt;
&lt;br /&gt;
With the battle going against them, captain Salid came up with a plan to stop the Imperial vessel dead in it&#039;s tracks. Building off a suggestion made by [[Rank|Lieutenant]] [[Chance Raschen]], he initiated a transfer of the Omega Directive Protocols into the Imperial Starship&#039;s computer after the junior officer reeled them into communications range for the data transfer. That vessel&#039;s commander, having no experience with the [[Starfleet General Orders &amp;amp; Directives|Omega Directive]] was unable to unlock the ship&#039;s computer, which caused them to lose the battle.&lt;br /&gt;
&lt;br /&gt;
However, the ship had not been neutralized before they had managed to launch the [[Omega Device]] at the [[Sunali II|Sunali]] Sun. Unable to pursue, the Rosenante was forced to allow the [[USS Furious]] to intercept and eventually destroy the weapon.&lt;br /&gt;
&lt;br /&gt;
With the aid of [[Nathan Benoit]] the Furious and the Vigiliant (another element of the Furious), managed to shut down the [[Paratrinic Shield]] protecting the device by bypassing the operating system of the [[Class 11 Computer|Class 11 Bioneural Computer]] that controlled it. With the shields down, The Vigilant was able to destroy the device with Phaser fire just minutes before it would have detonated.&lt;br /&gt;
&lt;br /&gt;
==Act Seven: The Boarding Action==&lt;br /&gt;
&lt;br /&gt;
With the battle over, Captain Salid ordered boarding parties to take possession of the [[ISS Rosenante]].&lt;br /&gt;
&lt;br /&gt;
*Assigned to take the Bridge were [[Jennifer Caskie|Commander Jennifer Caskie]] and [[Thomas Jackson|Lieutenant Tom Jackson]]&lt;br /&gt;
&lt;br /&gt;
*Assigned to Take Engineering were [[Mitena Rixx|Ensign Mitena Rixx]], Crewman Caroline Winters and [[Mike Rosenbauer|Ensign Mike Rosenbauer]].&lt;br /&gt;
&lt;br /&gt;
*Assigned to take the Computer Core were [[T&#039;Larah Sullivan|Commander T&#039;Larah Sullivan]] and [[Robert Smith|Ensign Robert Smith]].&lt;br /&gt;
&lt;br /&gt;
*Assigned to take the Security Center was [[Chance Raschen|Lieutenant Chance Raschen]].&lt;br /&gt;
&lt;br /&gt;
*Assigned to take Sickbay was [[Sam Lopez|Doctor Sam Lopez]] and [[Marta Nunez|Ensign Marta Nunez]]&lt;br /&gt;
&lt;br /&gt;
The teams achieved their goals quickly and with little resistance, as the [[Mirror Universe]] Salid had ordered his crew not to resist.&lt;br /&gt;
&lt;br /&gt;
Meanwhile back aboard the USS Rosenante [[Alimi Morrow|Lieutenant Alimi Morrow]] fought to prevent a warp core collapse. his efforts and those of [[Jon Nayati|Lieutenant Jon Nayati]] and [[V&#039;Shera|Ensign V&#039;Shera]] managed to prevent the destruction of the federation vessel. However, it was not without cost. Morrow was seriously injured in the attempt and was treated for severe radiation poisoning. His condition was so critical that he was placed in Stasis unitl such time as he could receive treatment at [[Geneva Station|Starbase Geneva]]. His life was saved by the quick thinking and intervention of [[Kimiko Ichijo|Doctor Kimiko Ichijo]]&lt;br /&gt;
&lt;br /&gt;
==Act Eight: Homeward Bound==&lt;br /&gt;
&lt;br /&gt;
After the Capture of the [[ISS Rosenante]] a deal was struck by which all the data concerning the [[Omega Conspiracy]] in the prime universe would be handed over to Captain Salid and Saleke in exchange for returning the Imperial ship home.  The agreement was made, after some discussion between The two Federation Commanding Officers and the Rosenante&#039;s First officer [[Jennifer Caskie]].&lt;br /&gt;
&lt;br /&gt;
A technical team was assigned to install an [[Interphasic Field Generator]] aboard the Imperial starship, which would force the ship back into it&#039;s normal universe. This same generator would then self destruct, making it impossible for the [[Imperial Union of Planets]] to recreate the devices for their use. Once the device was installed, the imperial ship was returned to the command of the [[Mirror Universe]] Salid and sent home. All indications suggest that the vessel was returned to their proper universe intact.&lt;br /&gt;
&lt;br /&gt;
The Rosenante, towing the [[USS Furious]] then returned to [[Starbase Geneva]] for repairs. &lt;br /&gt;
&lt;br /&gt;
{{USS Rosenante Missions}}&lt;br /&gt;
&lt;br /&gt;
[[Category: History]][[Category: Mirror Universe]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Into_the_Darkness,_Go_I&amp;diff=55866</id>
		<title>Into the Darkness, Go I</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Into_the_Darkness,_Go_I&amp;diff=55866"/>
		<updated>2012-09-05T16:12:57Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* Act Six: Finale */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Coming Soon!&lt;br /&gt;
&lt;br /&gt;
==Act One: Teaser==&lt;br /&gt;
[[Image:Rose2.png|thumb|right|250px|ISS Rosenante]]&lt;br /&gt;
The ISS Rosenante is assigned by [[Regent]] [[Admiral Doenitz|Doenitz]] to travel to the Sunali system. Earlier in 2407 the Sunali people defected to the invading [[Klingon-Cardassian Alliance]]. The system did not put up any resistance to the invaders and as such Doenitz feared that the other members of the newly formed [[Imperial Union of Planets]] would consider following suit. This action of course would lead to the complete defeat of the IUP. With this in mind the [[ISS Rosenante]] was dispatched to make an example of the Sunali.&lt;br /&gt;
&lt;br /&gt;
[[Image:Sunali Sun Destruction.jpg|thumb|left|250px|The Destruction of the Sunali star]]&lt;br /&gt;
By the time that the Rosenante arrived  The Klingon-Cardassian Alliance had already  begun shifting a large task force into the system. This task force was preparing for a military attack into the heart of the IUP.&lt;br /&gt;
&lt;br /&gt;
The enemy vessel present in  the system were:&lt;br /&gt;
&lt;br /&gt;
Twenty-two [[Klingon]] ships:&lt;br /&gt;
*12 [[Bird-of-Prey|K&#039;Vort Class, Bird-of-Prey]]s&lt;br /&gt;
*6 [[Bird-of-Prey|B&#039;rel Class Bird-of-Prey]]s &lt;br /&gt;
*4 modified [[D7 Class Battle Cruiser]]. &lt;br /&gt;
&lt;br /&gt;
There  are also [[Cardassian]] [[starship]]s in the system.&lt;br /&gt;
&lt;br /&gt;
* 18 [[Galor Class]] &lt;br /&gt;
&lt;br /&gt;
On the Planet, [[Sunali II]] there was a population of 18 million inhabitants.&lt;br /&gt;
&lt;br /&gt;
The ISS Rosenante moved into position by passing the mine perimeter that was only partially completed by the Cardassians. The ship them activated and launched the [[Omega Device]] towards the Sunali Star.&lt;br /&gt;
&lt;br /&gt;
The Rosenante then turned, and fought it&#039;s way pasts several enemy ships and was just barely able to escape the system just as the Omega Device detonated. The resultant explosion destroyed the entire system along with the enemy task force. An unexpected side affect of the Omega affect was an interaction of the energy waves created by the [[Omega Molecule]]&#039;s destruction interacting with the [[Rosenante Class|Spiral Warp Drive ]] of the Rosenante. Somehow this interaction forced the [[Mirror Universe]] ISS Rosenante through an [[Interphasic Rift|Interphasic Tunnel]] which deposited it into the Prime Universe, just outside the Sunali System.&lt;br /&gt;
&lt;br /&gt;
==Act Two: Prologue==&lt;br /&gt;
[[Image:Rosenante-Alt-2up.jpg|thumb|right|250px|USS Rosenante]]&lt;br /&gt;
Unknown to the [[USS Rosenante]] their mirror counterpart has laid in a course to [[Bardon Alpha]]. The Rosenante&#039;s [[Rank|Captain]] [[Ahmed Ibn Salid]] holds an emergency meeting with his three senior most officers, [[Jennifer Caskie]], [[T&#039;Larah Sullivan]] and [[Jon Nayati]]. He explains to them that he has just ordered the USS Rosenante off mission to investigate some critical intelligence. He does not reveal to the the nature of this intelligence, but simply asks for their trust in this issue. Salid states that he is aware that he is breaking regulations and that he realizes that there will be consequences if he is proven to be wrong. However he states that he can not take the chance that the intelligence turns out to be accurate without investigating it. It is his belief that the intelligence he has received could threaten not only the [[United Federation of Planets]] but also the [[Alpha Quadrant]]. All three officers agree to trust Salid&#039;s judgment.&lt;br /&gt;
&lt;br /&gt;
Meanwhile back on Earth, Captain Saleke, former Commanding Officer of the [[USS Hades]] is called to a lunch with [[Rank|Vice Admiral]] [[Errol Heatherby]]. The admiral begins to explain that he has reason to believe that there may be a conspiracy inside the [[Starfleet Command|Admiralty]]. He cites the bizarre fact that several prior Doenitz supporters are now Starship captains in the border region between the [[United Federation of Planets]] and the [[Cardassian Union]]. fearing that there could well be a potential to allow conspiracy to thrive under such conditions, he orders Saleke to take command of the [[USS Furious]], a [[Prometheus Class]] [[starship]] and proceed to the [[Ikev Sector]]. He also warns Saleke that the previous Captain of the Furious was killed in a freak [[Transporter]] accident and that the [[Vulcan]] Captain should proceed with caution.&lt;br /&gt;
&lt;br /&gt;
==Act Three: [[Bardon Alpha]]==&lt;br /&gt;
[[Image:Bardon Alpha.jpg|thumb|left|250px|Bardon Alpha]]&lt;br /&gt;
&lt;br /&gt;
===The Attack===&lt;br /&gt;
&lt;br /&gt;
The ISS Rosenante arrived at the Bardon mining Facility with the intention of stealing a shipment of highly refined [[Boronite]] ore. Captain Salid opened a channel and demanded that the ore be turned over to them. When the facilities administrator, Alix Sorvex, declined, Salid ordered the facility attacked and all personnel except one killed. He ordered an away team to the surface to carry out his orders.&lt;br /&gt;
&lt;br /&gt;
The Assault team was lead by the [[Mirror Universe]] version of [[Jennifer Caskie]]. Other members of the Mirror Universe crew, including Mike Rosenbauer and Aleesa Wyler accompanied her.  Rosenbauer commanded a security team called [[Mike&#039;s Maniacs]], which consisted of  Mirror Universe versions of Sodra, Tyrone Cooper, Mosh, T&#039;Vyr and Eva Saint-Jean. There were also two disposable members of the [[ISS Rosenante]]&#039;s Science team sent along to locate the boronite. once theier job was completed, they were executed and their bodies left behind.&lt;br /&gt;
&lt;br /&gt;
During the raid, Jennifer Caskie murdered the administrator with a bladed-weapon, which seemed to be the preferred method of execution. All other members of the facility crew were killed with the exception of technician Dallas, who was seriously injured by [[Mike Rosenbauer]], and Talia Lorenzo who had managed to avoid detection by hiding inside the facility&#039;s computer core ventilation system.&lt;br /&gt;
&lt;br /&gt;
===The Distress Signal===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
While enroute to the [[Ikev Sector]] the [[USS Rosenante]] intercepted a distress communication from the Bardon Alpha Mining Facility. Captain Salid ordered an intercept course set and the Rosenante raced to respond to the signal. The signal itself was standard except for it&#039;s contents.  The signal claimed that they facility was under attack by a Federation starship, which was identified as the Rosenante. This was not possible as the Rosenante was several hours away when the attack took place.&lt;br /&gt;
&lt;br /&gt;
When the ship arrived at the Bardon Alpha system, they detected no ships and received no replies to their hails.&lt;br /&gt;
&lt;br /&gt;
Wishing to get to the bottom of the signals claim and to search for survivors, [[Rank|Captain]] Salid ordered an away team to the planet&#039;s surface to investigate.&lt;br /&gt;
&lt;br /&gt;
The away team consisted of:&lt;br /&gt;
&lt;br /&gt;
*[[Rank|Commander]] [[Jennifer Caskie]]&lt;br /&gt;
*[[Rank|Lieutenant]] [[Jon Nayati]]&lt;br /&gt;
*[[Rank|Lieutenant]] [[Thomas Jackson]]&lt;br /&gt;
*[[Rank|Ensign]] [[V&#039;Shera]]&lt;br /&gt;
*[[Rank|Ensign]] [[Mitena Rixx]]&lt;br /&gt;
*[[Rank|Ensign]] [[Robert Smith]]&lt;br /&gt;
*[[Rank|Ensign]] [[Sam Lopez]]&lt;br /&gt;
*[[Rank|Ensign]] [[M&#039;Epak]]&lt;br /&gt;
*[[Rank|Ensign]] [[Kimiko Ichijo]]&lt;br /&gt;
*[[Rank|Ensign]] [[Mike Rosenbauer]]&lt;br /&gt;
&lt;br /&gt;
The away team beamed into the facility and immedately broke into two teams.  The first two teams began searching the area for survivors, these teams were comprised of Doctors Lopez and Ichijo as well as elements of the security team. The teams did not find any survivors on their assigned search areas but Doctor Ichijo did find a pair of bodies dressed in unusual uniforms, These two corpses were beamed back to the Rosenante for analysis. They were later discovered to belong to the two science officers from the [[ISS Rosenante]]. They had been executed by under orders from the Mirror Universe [[Jennifer Caskie]] once they had located the refined Boronite.&lt;br /&gt;
&lt;br /&gt;
The second away team consisted of the operations and Engineering team. This group consisted of Lieutenant Jackson and ensigns Rixx and Smith. The team&#039;s orders were to recover tha facility&#039;s sensor logs for study. Because of the extent of the damage, this team was forced to work there way deeper into the facility until they reached the computer core. once there, they gained access to the core and began copying the data for transfer back to the ship.&lt;br /&gt;
&lt;br /&gt;
The third team consisted of Commander Caskie, Lieutenant Nayati and Ensign Rosenbauer. They made thir way to the Administration center of the facility in the hiopes of accessing the facilities shipping manifests and security tapes. While there, they encountered the seriously wounded John Dallas. Dallas injured Rosenbauer, believing him to the be the same man who had assaulted him earlier.  in fact that person had been the [[Mirror Universe]] version of the same man. Dallas was subdued and beamed to the Rosenante for medical treatment.&lt;br /&gt;
&lt;br /&gt;
Caskie and Nayati then uncovered the production manifests and the security logs for the facility. The former showed that the facility had been refining boronite to an exceptionally refined state while the latter uncovered a video image showing Rosenbauer, Caskie and Wyler complacent in the death of the administrator and the attack on the facility.&lt;br /&gt;
&lt;br /&gt;
This information coupled with the mysterious appearance of a second Rosenante class starship, which could only have been built in secret, further convinced Captain Salid that there was indeed a high-level conspiracy ongoing.&lt;br /&gt;
&lt;br /&gt;
===The Furious Arrives===&lt;br /&gt;
&lt;br /&gt;
Despite warnings that they should leave the system by his senior officers, Captain Salid decided to remain at Bardon Alpha in the hopes of gathering some information that could give him a direction of pursuit.&lt;br /&gt;
&lt;br /&gt;
Lieutenant [[Chance Raschen]] after reviewing the telemetry data from the facilities computers managed to extrapolate a possible course for the rogue vessel. However, before it could be pursued the USS furious arrived in the system.&lt;br /&gt;
&lt;br /&gt;
The [[Prometheus Class]] [[starship]] was commanded by [[Rank|Captain]] [[Saleke]]. The [[Vulcan]] CO had once been the Commanding Officer of the [[USS Hades]] during the [[Federation Civil War]], and was renowned for his tactical skill.&lt;br /&gt;
&lt;br /&gt;
Salid was surprised to see Saleke, and suspected that if he was not a willing participant in the conspiracy concerning the creation of an [[Omega Device]] that he may well be manipulated into serving the purposes of that conspiracy. Saleke ordered the surrender of the [[USS Rosenante]], but Salid, uncertain of the Captain&#039;s true loyalties declined and attempted to flee the scene in the hopes of exhonerating the names of the crew.&lt;br /&gt;
&lt;br /&gt;
Saleke engaged the Rosenante, whom he considered attempting to escape from the scene of a crime and shot&#039;s were fired. Still reluctant to destroy the Furious due the the unknown position of Captain Saleke&#039;s affiliations, Salid ordered the long-range communications of the Furious destroyed. inital stages of the battle were ineffective. For the Furious this was caused in part because of the employment of the [[The Chimera Directive|SEDIS]] and in part by the superior shielding possessed by the [[Rosenante Class]] [[Starship]].&lt;br /&gt;
&lt;br /&gt;
However, Saleke had a trick up his sleeve. Earlier, he had ordered the modification of five quantum torpedoes so that they were equipped with a [[Cloaking device|Phased Cloaking Device]]. These torpedoes when launched against the Rosenante ignored her shileds and caused significant damage to the latter vessel&#039;s Environmental Subsystems, lifeboats, secondary phaser array, forward tractor beam emitter and caused a hull breach in main Engineering. The advantage was short lived however, when Salid managed to deplete the Furious&#039; forward shields enough to cause the vessel to veer off in order to avoid a volley of concussive photon torpedoes.&lt;br /&gt;
&lt;br /&gt;
It was a manuever that would later become known as [[The Salid Gambit]]. With the Furious deviated from her pursuit. Salid managed to get the Rosenante into the [[Magnesite]] ore filled asteroid field in the Bardon system known as [[The Mill]]. It was an area familiar to [[Rank|Lieutenant]] [[Chance Raschen]], who had often used the area to avoid or lose [[Cardassian]] pursuit during the [[Cardassian]]-[[Federation]] War. Raschen had served in the [[Irregular Federation Forces]] during the [[Admiral Doenitz|Doentiz]] regieme, before defecting to the [[52nd Fleet]]. His knowledge of the area would prove invaluable to evading the Furious. The high concentration of magnesite ore prevented the use of most navigational sensors withn the confines of the Mill, thus preventing the furious from following the Rosenante. in addition, coupled with the [[The Chimera Directive|HISS]] Stealth System, the Furious was unable to detect the Rosenante from outside the field either.&lt;br /&gt;
&lt;br /&gt;
Saleke ordered the Furious at best speed course around the field in the hopes of catching the Rosenante exitting the other side in the hopes of taking advantage of the Prometheus Class&#039; Tri-vector assault mode. However, once on the other side, the furious detected the decaying signature left by the [[The Chimera Directive|Spiral warp Drive]] of the [[ISS Rosenante]]. &lt;br /&gt;
&lt;br /&gt;
Thinking that the Rosenante had already managed to clear the field and set course for [[Hexikor Prime]], Saleke ordered the Furious to pursue. Meanwhile the USS Rosenante remained in [[The Mill]] conducting repairs.&lt;br /&gt;
&lt;br /&gt;
==Act Four: [[Hexikor Prime]]==&lt;br /&gt;
[[Image:Hexikor Prime.JPG|thumb|right|250px|Hexikor Prime]]&lt;br /&gt;
The [[ISS Rosenante]] arrived at Hexikor Alpha before either the [[USS Furious]] or the [[USS Rosenante]] could intercept her. The crew of the Mirror Universe had a clear set of objectives in mind for the attack and set about capturing them with speed and efficiency. The Mirror Universe Away Team consisted of the Following personnel:&lt;br /&gt;
&lt;br /&gt;
*Commander [[Jennifer Caskie]]&lt;br /&gt;
*Lieutenant [[Jon Nayati]]&lt;br /&gt;
*Lieutenant [[Thomas Jackson]]&lt;br /&gt;
*Ensign [[Mitena Rixx]]&lt;br /&gt;
*Ensign [[Mike Rosenbauer]]&lt;br /&gt;
*Ensign [[Robert Smith]]&lt;br /&gt;
&lt;br /&gt;
This group was tasked with the objective to locate and acquire two pieces of hardware located aboard the Hexikor Alpha facility. These were a [[Paratrinic Shield|Paratrinic Shield Generator]] And a [[Class 11 Computer|Class 11 Bioneural Computer]]. These components would be essential in defining the defensive capabilities of the [[Omega Device]].&lt;br /&gt;
&lt;br /&gt;
After the away team arrived, they encountered Doctors 12 &amp;amp; 14, the [[Bynars|Bynar]] Scientists working on the Paratrinic shield project. They also encountered [[Nathan Benoit]] a recent graduate from [[Starfleet Academy]].&lt;br /&gt;
&lt;br /&gt;
In a struggle, Benoit was attacked and overpowered by the [[Mirror Universe]] Thomas Jackson. The Mirror universe away team chose to capture Doctor 12 and use him as bait. However, Doctor 14 activated the shield generator and managed to transport an unprotected Mirror universe Jackson out into the depths of space beyond the hull of the station. The ISS Rosenante&#039;s Chief of Operations had been killed.&lt;br /&gt;
&lt;br /&gt;
Meanwhile, Rixx and Smith worked to secure the devices and when they had completed their task, they beamed the equipment back to the awaiting Mirror Universe vessel.&lt;br /&gt;
&lt;br /&gt;
It was during that time that station security showed up and a very brief exchange of phaser fire took place. The Mirror Universe group evacuated the station having secured their prize and left the area unmolested. During the Raid Captain Salid had chosen to destroy both facilities long-range communications capabilities&lt;br /&gt;
&lt;br /&gt;
[[Image:Prometheus class.jpg|thumb|left|250px|USS Furious]]&lt;br /&gt;
The USS Furious arrived a little over a day behind the ISS Rosenante&#039;s departure. Captain [[Saleke]] elected to visit the facility in an effort to ferret out additional information concerning the conspiracy alluded to by the Prime Universe&#039;s Captain [[Ahmed Ibn Salid]]. During his visit to the station the Furious&#039; CSO Holis Gralen, a [[Betazoid]] interviewed Commander [[Brian Romeo]] concerning the research of the stolen equipment. Romeo provided a perfect watertight reason for the project, citing a pre-warp culture and an attempt to study a rapidly dying star from the same system. While the evidence was solid, Holis suspected that Romeo was not being entirely truthful.&lt;br /&gt;
&lt;br /&gt;
While Saleke was conducting his investigation abord the Hexikor facility, including interviewing an injured [[Nathan Benoit]], The USS Rosenante entered the Hexikor system under cloak.&lt;br /&gt;
&lt;br /&gt;
Determined not to have a repeat of the encounter at [[Bardon Alpha]], Captain Salid chose to neutralize the threat that the Furious posed by transporting six of their primary power buses off the Furious. These power relay buses, cause the ship to lose all primary power, rendering it unable to use weapons, shields or warp drive.  Salid then ordered the surrender of the Furious but was unwilling to accept the surrender of that vessel from their First Officer Commander Erin Sloane.&lt;br /&gt;
&lt;br /&gt;
Saleke was summoned and his presence was requested aboard the Rosenante. Having been convinced by the data that he had collected thus far in his investigation, Captain Saleke informed Captain Salid that he and his ship were no longer suspects in the attack, nor were the complicit in any plot to acquire and build an Omega Device.  Saleke had, independently, arrived at the same conclusion, that the ISS Rosenante, a ship from the Mirror universe was in fact responsible for the attacks. &lt;br /&gt;
&lt;br /&gt;
It was also clear that the Mirror Universe Rosenante was following a pattern that must have been established in their own universe. Which explained how the marauding vessel knew where to acquire the components for the creation of a new Omega Device.&lt;br /&gt;
&lt;br /&gt;
After some discussions, it was decided that the USS Furious and the USS Rosenante would need to combine forces in order to counter the tactical and homicidal threat now posed by the ISS Rosenante.&lt;br /&gt;
&lt;br /&gt;
As long range scans indicated that the Mirror Universe vessel was headed for the [[Kabor Prime|Kabor System]] The Rosenante took the Furious under tow, and using their own shields to protect them, opened a Spiral warp conduit to facilitate maneuvers while the Furious conducted the reinstallation of the power relay buses.&lt;br /&gt;
&lt;br /&gt;
==Act Five: [[Kabor Prime]]==&lt;br /&gt;
[[Image:Kabor Prime.jpg|thumb|right|250px|Kabor Prime]]&lt;br /&gt;
&lt;br /&gt;
A few days after the attack on the [[Bynars|Bynar]] Facility in the Hexikor system, the [[ISS Rosenante]] appeared in the Kabor system. Thier target was a secret production facility known as [[Station Omega]]. The facility had been built by a secret research and development branch of Starfleet Sciences Division during the [[Admiral Doenitz|Doenitz]] regime.  Thier primary function was the development of an [[Omega Device]]. &lt;br /&gt;
&lt;br /&gt;
After the end of the [[Federation Civil War]] the facility went underground. Through the actions of a small group of [[Starfleet]] [[Rank|Admiral]]s, all records pointing to the existence of such a facility were erased and the personnel there continued with their research. Through covert means, the facility was equipped with large Class XII phaser batteries for defense. At the heart of the facilities power center was a stabilized [[Omega Molecule]]. The first that the Station had managed to produce.&lt;br /&gt;
&lt;br /&gt;
The ISS Rosneante arrived in the system, intent on collecting the last few remaining components of the Omega device that they needed to create their own version of the weapon. As the [[Mirror Universe]] [[Ahmed Ibn Salid]] had worked at this facility in his universe, he had intimate knowledge of the facilities existence and layout. What he had not known was that the station had been armed, as in his universe, it was not protected.&lt;br /&gt;
&lt;br /&gt;
[[Image:Omega Device.jpg|thumb|left|250px|Omega Device]]&lt;br /&gt;
&lt;br /&gt;
The Mirror universe ship was forced to subdue the facility by force, which cost them a great deal of time, narrowing the lead that they had on their Prime Universe Counterpart the [[USS Rosenante]] and the [[USS Furious]]. This delay would prove to be a great boon to the federation starship over the next few days.&lt;br /&gt;
&lt;br /&gt;
With the retrieval of the components complete, Salid ordered [[Mitena Rixx]] and [[Nathan Benoit]] to begin modifications to the base components to bring them up to specifications of the original Mirror universe version of the omega device. This involved the addition of the previously stolen [[Paratrinic Shield|Paratrinic Shield Generator]] as well as the [[Class 11 Computer| Class 11 Bioneural Computer]].&lt;br /&gt;
&lt;br /&gt;
By the time that the Federation starship had arrived, the mirror universe vessel was gone and the station destroyed. Captain&#039;s Salid and [[Saleke]] wasted no time in the system, instead following the ISS Rosenante&#039;s warp trail towards the Sunali System. With time running out, they realized that they had no choice by to confront the marauding vessel and deal with it once and for all.&lt;br /&gt;
&lt;br /&gt;
==Act Six: Finale==&lt;br /&gt;
[[Image:Rose Beauty2.jpg|thumb|right|250px|Battle of Sunali II]]&lt;br /&gt;
&lt;br /&gt;
The [[USS Rosenante]] and the [[USS Furious]] entered the [[Sunali II|Sunali System]] to find the [[ISS Rosenante]] engaged in the wanton destruction of [[Cardassian]] merchant shipping. These ships although peaceful, had been destroyed simply because they were Cardassian.&lt;br /&gt;
&lt;br /&gt;
The USS Rsoenante ordered the Imperial starship to surrender. That vessel refused.&lt;br /&gt;
&lt;br /&gt;
What followed next was a flurry of conflict, with the Stronger [[ISS Rosenante]] dealing a tremendous amount of damage to both the [[USS Rosenante]] as well as the [[USS Furious]],&lt;br /&gt;
&lt;br /&gt;
During the conflict the Furious engaged her [[Prometheus Class|Tri-vector Attack mode]] to engage the more powerful [[Mirror Universe]] vessel. The Mirror universe [[Andrew Elliot Maddox]] managed to take over the computer of one of the Furious&#039; sections named the Courageous and overload it&#039;s warp core killing all 142 hands on board. &lt;br /&gt;
&lt;br /&gt;
With the battle going against them, captain Salid came up with a plan to stop the Imperial vessel dead in it&#039;s tracks. Building off a suggestion made by [[Rank|Lieutenant]] [[Chance Raschen]], he initiated a transfer of the Omega Directive Protocols into the Imperial Starship&#039;s computer after the junior officer reeled them into communications range for the data transfer. That vessel&#039;s commander, having no experience with the [[Starfleet General Orders &amp;amp; Directives|Omega Directive]] was unable to unlock the ship&#039;s computer, which caused them to lose the battle.&lt;br /&gt;
&lt;br /&gt;
However, the ship had not been neutralized before they had managed to launch the [[Omega Device]] at the [[Sunali II|Sunali]] Sun. Unable to pursue, the Rosenante was forced to allow the [[USS Furious]] to intercept and eventually destroy the weapon.&lt;br /&gt;
&lt;br /&gt;
With the aid of [[Nathan Benoit]] the Furious and the Vigiliant (another element of the Furious), managed to shut down the [[Paratrinic Shield]] protecting the device by bypassing the operating system of the [[Class 11 Computer|Class 11 Bioneural Computer]] that controlled it. With the shields down, The Vigilant was able to destroy the device with Phaser fire just minutes before it would have detonated.&lt;br /&gt;
&lt;br /&gt;
==Act Seven: The Boarding Action==&lt;br /&gt;
&lt;br /&gt;
With the battle over, Captain Salid ordered boarding parties to take possession of the [[ISS Rosenante]].&lt;br /&gt;
&lt;br /&gt;
*Assigned to take the Bridge were [[Jennifer Caskie|Commander Jennifer Caskie]] and [[Thomas Jackson|Lieutenant Tom Jackson]]&lt;br /&gt;
&lt;br /&gt;
*Assigned to Take Engineering were [[Mitena Rixx|Ensign Mitena Rixx]], Crewman Caroline Winters and [[Mike Rosenbauer|Ensign Mike Rosenbauer]].&lt;br /&gt;
&lt;br /&gt;
*Assigned to take the Computer Core were [[T&#039;Larah Sullivan|Commander T&#039;Larah Sullivan]] and [[Robert Smith|Ensign Robert Smith]].&lt;br /&gt;
&lt;br /&gt;
*Assigned to take the Security Center was [[Chance Raschen|Lieutenant Chance Raschen]].&lt;br /&gt;
&lt;br /&gt;
*Assigned to take Sickbay was [[Sam Lopez|Doctor Sam Lopez]] and [[Marta Nunez|Ensign Marta Nunez]]&lt;br /&gt;
&lt;br /&gt;
The teams achieved their goals quickly and with little resistance, as the [[Mirror Universe]] Salid had ordered his crew not to resist.&lt;br /&gt;
&lt;br /&gt;
Meanwhile back aboard the USS Rosenante [[Alimi Morrow|Lieutenant Alimi Morrow]] fought to prevent a warp core collapse. his efforts and those of [[Jon Nayati|Lieutenant Jon Nayati]] and [[V&#039;Shera|Ensign V&#039;Shera]] managed to prevent the destruction of the federation vessel. However, it was not without cost. Morrow was seriously injured in the attempt and was treated for severe radiation poisoning. His condition was so critical that he was placed in Stasis unitl such time as he could receive treatment at [[Geneva Station|Starbase Geneva]]. His life was saved by the quick thinking and intervention of [[Kimiko Ichijo|Doctor Kimiko Ichijo]]&lt;br /&gt;
&lt;br /&gt;
==Act Eight: Homeward Bound==&lt;br /&gt;
&lt;br /&gt;
After the Capture of the [[ISS Rosenante]] a deal was struck by which all the data concerning the [[Omega Conspiracy]] in the prime universe would be handed over to Captain Salid and Saleke in exchange for returning the Imperial ship home.  The agreement was made, after some discussion between The two Federation Commanding Officers and the Rosenante&#039;s First officer [[Jennifer Caskie]].&lt;br /&gt;
&lt;br /&gt;
A technical team was assigned to install an [[Interphasic Field Generator]] aboard the Imperial starship, which would force the ship back into it&#039;s normal universe. This same generator would then self destruct, making it impossible for the [[Imperial Union of Planets]] to recreate the devices for their use. Once the device was installed, the imperial ship was returned to the command of the [[Mirror Universe]] Salid and sent home. All indications suggest that the vessel was returned to their proper universe intact.&lt;br /&gt;
&lt;br /&gt;
The Rosenante, towing the [[USS Furious]] then returned to [[Starbase Geneva]] for repairs. &lt;br /&gt;
&lt;br /&gt;
{{USS Rosenante Missions}}&lt;br /&gt;
&lt;br /&gt;
[[Category: History]][[Category: Mirror Universe]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Into_the_Darkness,_Go_I&amp;diff=55865</id>
		<title>Into the Darkness, Go I</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Into_the_Darkness,_Go_I&amp;diff=55865"/>
		<updated>2012-09-05T16:12:46Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* Act Six: Finale */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Coming Soon!&lt;br /&gt;
&lt;br /&gt;
==Act One: Teaser==&lt;br /&gt;
[[Image:Rose2.png|thumb|right|250px|ISS Rosenante]]&lt;br /&gt;
The ISS Rosenante is assigned by [[Regent]] [[Admiral Doenitz|Doenitz]] to travel to the Sunali system. Earlier in 2407 the Sunali people defected to the invading [[Klingon-Cardassian Alliance]]. The system did not put up any resistance to the invaders and as such Doenitz feared that the other members of the newly formed [[Imperial Union of Planets]] would consider following suit. This action of course would lead to the complete defeat of the IUP. With this in mind the [[ISS Rosenante]] was dispatched to make an example of the Sunali.&lt;br /&gt;
&lt;br /&gt;
[[Image:Sunali Sun Destruction.jpg|thumb|left|250px|The Destruction of the Sunali star]]&lt;br /&gt;
By the time that the Rosenante arrived  The Klingon-Cardassian Alliance had already  begun shifting a large task force into the system. This task force was preparing for a military attack into the heart of the IUP.&lt;br /&gt;
&lt;br /&gt;
The enemy vessel present in  the system were:&lt;br /&gt;
&lt;br /&gt;
Twenty-two [[Klingon]] ships:&lt;br /&gt;
*12 [[Bird-of-Prey|K&#039;Vort Class, Bird-of-Prey]]s&lt;br /&gt;
*6 [[Bird-of-Prey|B&#039;rel Class Bird-of-Prey]]s &lt;br /&gt;
*4 modified [[D7 Class Battle Cruiser]]. &lt;br /&gt;
&lt;br /&gt;
There  are also [[Cardassian]] [[starship]]s in the system.&lt;br /&gt;
&lt;br /&gt;
* 18 [[Galor Class]] &lt;br /&gt;
&lt;br /&gt;
On the Planet, [[Sunali II]] there was a population of 18 million inhabitants.&lt;br /&gt;
&lt;br /&gt;
The ISS Rosenante moved into position by passing the mine perimeter that was only partially completed by the Cardassians. The ship them activated and launched the [[Omega Device]] towards the Sunali Star.&lt;br /&gt;
&lt;br /&gt;
The Rosenante then turned, and fought it&#039;s way pasts several enemy ships and was just barely able to escape the system just as the Omega Device detonated. The resultant explosion destroyed the entire system along with the enemy task force. An unexpected side affect of the Omega affect was an interaction of the energy waves created by the [[Omega Molecule]]&#039;s destruction interacting with the [[Rosenante Class|Spiral Warp Drive ]] of the Rosenante. Somehow this interaction forced the [[Mirror Universe]] ISS Rosenante through an [[Interphasic Rift|Interphasic Tunnel]] which deposited it into the Prime Universe, just outside the Sunali System.&lt;br /&gt;
&lt;br /&gt;
==Act Two: Prologue==&lt;br /&gt;
[[Image:Rosenante-Alt-2up.jpg|thumb|right|250px|USS Rosenante]]&lt;br /&gt;
Unknown to the [[USS Rosenante]] their mirror counterpart has laid in a course to [[Bardon Alpha]]. The Rosenante&#039;s [[Rank|Captain]] [[Ahmed Ibn Salid]] holds an emergency meeting with his three senior most officers, [[Jennifer Caskie]], [[T&#039;Larah Sullivan]] and [[Jon Nayati]]. He explains to them that he has just ordered the USS Rosenante off mission to investigate some critical intelligence. He does not reveal to the the nature of this intelligence, but simply asks for their trust in this issue. Salid states that he is aware that he is breaking regulations and that he realizes that there will be consequences if he is proven to be wrong. However he states that he can not take the chance that the intelligence turns out to be accurate without investigating it. It is his belief that the intelligence he has received could threaten not only the [[United Federation of Planets]] but also the [[Alpha Quadrant]]. All three officers agree to trust Salid&#039;s judgment.&lt;br /&gt;
&lt;br /&gt;
Meanwhile back on Earth, Captain Saleke, former Commanding Officer of the [[USS Hades]] is called to a lunch with [[Rank|Vice Admiral]] [[Errol Heatherby]]. The admiral begins to explain that he has reason to believe that there may be a conspiracy inside the [[Starfleet Command|Admiralty]]. He cites the bizarre fact that several prior Doenitz supporters are now Starship captains in the border region between the [[United Federation of Planets]] and the [[Cardassian Union]]. fearing that there could well be a potential to allow conspiracy to thrive under such conditions, he orders Saleke to take command of the [[USS Furious]], a [[Prometheus Class]] [[starship]] and proceed to the [[Ikev Sector]]. He also warns Saleke that the previous Captain of the Furious was killed in a freak [[Transporter]] accident and that the [[Vulcan]] Captain should proceed with caution.&lt;br /&gt;
&lt;br /&gt;
==Act Three: [[Bardon Alpha]]==&lt;br /&gt;
[[Image:Bardon Alpha.jpg|thumb|left|250px|Bardon Alpha]]&lt;br /&gt;
&lt;br /&gt;
===The Attack===&lt;br /&gt;
&lt;br /&gt;
The ISS Rosenante arrived at the Bardon mining Facility with the intention of stealing a shipment of highly refined [[Boronite]] ore. Captain Salid opened a channel and demanded that the ore be turned over to them. When the facilities administrator, Alix Sorvex, declined, Salid ordered the facility attacked and all personnel except one killed. He ordered an away team to the surface to carry out his orders.&lt;br /&gt;
&lt;br /&gt;
The Assault team was lead by the [[Mirror Universe]] version of [[Jennifer Caskie]]. Other members of the Mirror Universe crew, including Mike Rosenbauer and Aleesa Wyler accompanied her.  Rosenbauer commanded a security team called [[Mike&#039;s Maniacs]], which consisted of  Mirror Universe versions of Sodra, Tyrone Cooper, Mosh, T&#039;Vyr and Eva Saint-Jean. There were also two disposable members of the [[ISS Rosenante]]&#039;s Science team sent along to locate the boronite. once theier job was completed, they were executed and their bodies left behind.&lt;br /&gt;
&lt;br /&gt;
During the raid, Jennifer Caskie murdered the administrator with a bladed-weapon, which seemed to be the preferred method of execution. All other members of the facility crew were killed with the exception of technician Dallas, who was seriously injured by [[Mike Rosenbauer]], and Talia Lorenzo who had managed to avoid detection by hiding inside the facility&#039;s computer core ventilation system.&lt;br /&gt;
&lt;br /&gt;
===The Distress Signal===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
While enroute to the [[Ikev Sector]] the [[USS Rosenante]] intercepted a distress communication from the Bardon Alpha Mining Facility. Captain Salid ordered an intercept course set and the Rosenante raced to respond to the signal. The signal itself was standard except for it&#039;s contents.  The signal claimed that they facility was under attack by a Federation starship, which was identified as the Rosenante. This was not possible as the Rosenante was several hours away when the attack took place.&lt;br /&gt;
&lt;br /&gt;
When the ship arrived at the Bardon Alpha system, they detected no ships and received no replies to their hails.&lt;br /&gt;
&lt;br /&gt;
Wishing to get to the bottom of the signals claim and to search for survivors, [[Rank|Captain]] Salid ordered an away team to the planet&#039;s surface to investigate.&lt;br /&gt;
&lt;br /&gt;
The away team consisted of:&lt;br /&gt;
&lt;br /&gt;
*[[Rank|Commander]] [[Jennifer Caskie]]&lt;br /&gt;
*[[Rank|Lieutenant]] [[Jon Nayati]]&lt;br /&gt;
*[[Rank|Lieutenant]] [[Thomas Jackson]]&lt;br /&gt;
*[[Rank|Ensign]] [[V&#039;Shera]]&lt;br /&gt;
*[[Rank|Ensign]] [[Mitena Rixx]]&lt;br /&gt;
*[[Rank|Ensign]] [[Robert Smith]]&lt;br /&gt;
*[[Rank|Ensign]] [[Sam Lopez]]&lt;br /&gt;
*[[Rank|Ensign]] [[M&#039;Epak]]&lt;br /&gt;
*[[Rank|Ensign]] [[Kimiko Ichijo]]&lt;br /&gt;
*[[Rank|Ensign]] [[Mike Rosenbauer]]&lt;br /&gt;
&lt;br /&gt;
The away team beamed into the facility and immedately broke into two teams.  The first two teams began searching the area for survivors, these teams were comprised of Doctors Lopez and Ichijo as well as elements of the security team. The teams did not find any survivors on their assigned search areas but Doctor Ichijo did find a pair of bodies dressed in unusual uniforms, These two corpses were beamed back to the Rosenante for analysis. They were later discovered to belong to the two science officers from the [[ISS Rosenante]]. They had been executed by under orders from the Mirror Universe [[Jennifer Caskie]] once they had located the refined Boronite.&lt;br /&gt;
&lt;br /&gt;
The second away team consisted of the operations and Engineering team. This group consisted of Lieutenant Jackson and ensigns Rixx and Smith. The team&#039;s orders were to recover tha facility&#039;s sensor logs for study. Because of the extent of the damage, this team was forced to work there way deeper into the facility until they reached the computer core. once there, they gained access to the core and began copying the data for transfer back to the ship.&lt;br /&gt;
&lt;br /&gt;
The third team consisted of Commander Caskie, Lieutenant Nayati and Ensign Rosenbauer. They made thir way to the Administration center of the facility in the hiopes of accessing the facilities shipping manifests and security tapes. While there, they encountered the seriously wounded John Dallas. Dallas injured Rosenbauer, believing him to the be the same man who had assaulted him earlier.  in fact that person had been the [[Mirror Universe]] version of the same man. Dallas was subdued and beamed to the Rosenante for medical treatment.&lt;br /&gt;
&lt;br /&gt;
Caskie and Nayati then uncovered the production manifests and the security logs for the facility. The former showed that the facility had been refining boronite to an exceptionally refined state while the latter uncovered a video image showing Rosenbauer, Caskie and Wyler complacent in the death of the administrator and the attack on the facility.&lt;br /&gt;
&lt;br /&gt;
This information coupled with the mysterious appearance of a second Rosenante class starship, which could only have been built in secret, further convinced Captain Salid that there was indeed a high-level conspiracy ongoing.&lt;br /&gt;
&lt;br /&gt;
===The Furious Arrives===&lt;br /&gt;
&lt;br /&gt;
Despite warnings that they should leave the system by his senior officers, Captain Salid decided to remain at Bardon Alpha in the hopes of gathering some information that could give him a direction of pursuit.&lt;br /&gt;
&lt;br /&gt;
Lieutenant [[Chance Raschen]] after reviewing the telemetry data from the facilities computers managed to extrapolate a possible course for the rogue vessel. However, before it could be pursued the USS furious arrived in the system.&lt;br /&gt;
&lt;br /&gt;
The [[Prometheus Class]] [[starship]] was commanded by [[Rank|Captain]] [[Saleke]]. The [[Vulcan]] CO had once been the Commanding Officer of the [[USS Hades]] during the [[Federation Civil War]], and was renowned for his tactical skill.&lt;br /&gt;
&lt;br /&gt;
Salid was surprised to see Saleke, and suspected that if he was not a willing participant in the conspiracy concerning the creation of an [[Omega Device]] that he may well be manipulated into serving the purposes of that conspiracy. Saleke ordered the surrender of the [[USS Rosenante]], but Salid, uncertain of the Captain&#039;s true loyalties declined and attempted to flee the scene in the hopes of exhonerating the names of the crew.&lt;br /&gt;
&lt;br /&gt;
Saleke engaged the Rosenante, whom he considered attempting to escape from the scene of a crime and shot&#039;s were fired. Still reluctant to destroy the Furious due the the unknown position of Captain Saleke&#039;s affiliations, Salid ordered the long-range communications of the Furious destroyed. inital stages of the battle were ineffective. For the Furious this was caused in part because of the employment of the [[The Chimera Directive|SEDIS]] and in part by the superior shielding possessed by the [[Rosenante Class]] [[Starship]].&lt;br /&gt;
&lt;br /&gt;
However, Saleke had a trick up his sleeve. Earlier, he had ordered the modification of five quantum torpedoes so that they were equipped with a [[Cloaking device|Phased Cloaking Device]]. These torpedoes when launched against the Rosenante ignored her shileds and caused significant damage to the latter vessel&#039;s Environmental Subsystems, lifeboats, secondary phaser array, forward tractor beam emitter and caused a hull breach in main Engineering. The advantage was short lived however, when Salid managed to deplete the Furious&#039; forward shields enough to cause the vessel to veer off in order to avoid a volley of concussive photon torpedoes.&lt;br /&gt;
&lt;br /&gt;
It was a manuever that would later become known as [[The Salid Gambit]]. With the Furious deviated from her pursuit. Salid managed to get the Rosenante into the [[Magnesite]] ore filled asteroid field in the Bardon system known as [[The Mill]]. It was an area familiar to [[Rank|Lieutenant]] [[Chance Raschen]], who had often used the area to avoid or lose [[Cardassian]] pursuit during the [[Cardassian]]-[[Federation]] War. Raschen had served in the [[Irregular Federation Forces]] during the [[Admiral Doenitz|Doentiz]] regieme, before defecting to the [[52nd Fleet]]. His knowledge of the area would prove invaluable to evading the Furious. The high concentration of magnesite ore prevented the use of most navigational sensors withn the confines of the Mill, thus preventing the furious from following the Rosenante. in addition, coupled with the [[The Chimera Directive|HISS]] Stealth System, the Furious was unable to detect the Rosenante from outside the field either.&lt;br /&gt;
&lt;br /&gt;
Saleke ordered the Furious at best speed course around the field in the hopes of catching the Rosenante exitting the other side in the hopes of taking advantage of the Prometheus Class&#039; Tri-vector assault mode. However, once on the other side, the furious detected the decaying signature left by the [[The Chimera Directive|Spiral warp Drive]] of the [[ISS Rosenante]]. &lt;br /&gt;
&lt;br /&gt;
Thinking that the Rosenante had already managed to clear the field and set course for [[Hexikor Prime]], Saleke ordered the Furious to pursue. Meanwhile the USS Rosenante remained in [[The Mill]] conducting repairs.&lt;br /&gt;
&lt;br /&gt;
==Act Four: [[Hexikor Prime]]==&lt;br /&gt;
[[Image:Hexikor Prime.JPG|thumb|right|250px|Hexikor Prime]]&lt;br /&gt;
The [[ISS Rosenante]] arrived at Hexikor Alpha before either the [[USS Furious]] or the [[USS Rosenante]] could intercept her. The crew of the Mirror Universe had a clear set of objectives in mind for the attack and set about capturing them with speed and efficiency. The Mirror Universe Away Team consisted of the Following personnel:&lt;br /&gt;
&lt;br /&gt;
*Commander [[Jennifer Caskie]]&lt;br /&gt;
*Lieutenant [[Jon Nayati]]&lt;br /&gt;
*Lieutenant [[Thomas Jackson]]&lt;br /&gt;
*Ensign [[Mitena Rixx]]&lt;br /&gt;
*Ensign [[Mike Rosenbauer]]&lt;br /&gt;
*Ensign [[Robert Smith]]&lt;br /&gt;
&lt;br /&gt;
This group was tasked with the objective to locate and acquire two pieces of hardware located aboard the Hexikor Alpha facility. These were a [[Paratrinic Shield|Paratrinic Shield Generator]] And a [[Class 11 Computer|Class 11 Bioneural Computer]]. These components would be essential in defining the defensive capabilities of the [[Omega Device]].&lt;br /&gt;
&lt;br /&gt;
After the away team arrived, they encountered Doctors 12 &amp;amp; 14, the [[Bynars|Bynar]] Scientists working on the Paratrinic shield project. They also encountered [[Nathan Benoit]] a recent graduate from [[Starfleet Academy]].&lt;br /&gt;
&lt;br /&gt;
In a struggle, Benoit was attacked and overpowered by the [[Mirror Universe]] Thomas Jackson. The Mirror universe away team chose to capture Doctor 12 and use him as bait. However, Doctor 14 activated the shield generator and managed to transport an unprotected Mirror universe Jackson out into the depths of space beyond the hull of the station. The ISS Rosenante&#039;s Chief of Operations had been killed.&lt;br /&gt;
&lt;br /&gt;
Meanwhile, Rixx and Smith worked to secure the devices and when they had completed their task, they beamed the equipment back to the awaiting Mirror Universe vessel.&lt;br /&gt;
&lt;br /&gt;
It was during that time that station security showed up and a very brief exchange of phaser fire took place. The Mirror Universe group evacuated the station having secured their prize and left the area unmolested. During the Raid Captain Salid had chosen to destroy both facilities long-range communications capabilities&lt;br /&gt;
&lt;br /&gt;
[[Image:Prometheus class.jpg|thumb|left|250px|USS Furious]]&lt;br /&gt;
The USS Furious arrived a little over a day behind the ISS Rosenante&#039;s departure. Captain [[Saleke]] elected to visit the facility in an effort to ferret out additional information concerning the conspiracy alluded to by the Prime Universe&#039;s Captain [[Ahmed Ibn Salid]]. During his visit to the station the Furious&#039; CSO Holis Gralen, a [[Betazoid]] interviewed Commander [[Brian Romeo]] concerning the research of the stolen equipment. Romeo provided a perfect watertight reason for the project, citing a pre-warp culture and an attempt to study a rapidly dying star from the same system. While the evidence was solid, Holis suspected that Romeo was not being entirely truthful.&lt;br /&gt;
&lt;br /&gt;
While Saleke was conducting his investigation abord the Hexikor facility, including interviewing an injured [[Nathan Benoit]], The USS Rosenante entered the Hexikor system under cloak.&lt;br /&gt;
&lt;br /&gt;
Determined not to have a repeat of the encounter at [[Bardon Alpha]], Captain Salid chose to neutralize the threat that the Furious posed by transporting six of their primary power buses off the Furious. These power relay buses, cause the ship to lose all primary power, rendering it unable to use weapons, shields or warp drive.  Salid then ordered the surrender of the Furious but was unwilling to accept the surrender of that vessel from their First Officer Commander Erin Sloane.&lt;br /&gt;
&lt;br /&gt;
Saleke was summoned and his presence was requested aboard the Rosenante. Having been convinced by the data that he had collected thus far in his investigation, Captain Saleke informed Captain Salid that he and his ship were no longer suspects in the attack, nor were the complicit in any plot to acquire and build an Omega Device.  Saleke had, independently, arrived at the same conclusion, that the ISS Rosenante, a ship from the Mirror universe was in fact responsible for the attacks. &lt;br /&gt;
&lt;br /&gt;
It was also clear that the Mirror Universe Rosenante was following a pattern that must have been established in their own universe. Which explained how the marauding vessel knew where to acquire the components for the creation of a new Omega Device.&lt;br /&gt;
&lt;br /&gt;
After some discussions, it was decided that the USS Furious and the USS Rosenante would need to combine forces in order to counter the tactical and homicidal threat now posed by the ISS Rosenante.&lt;br /&gt;
&lt;br /&gt;
As long range scans indicated that the Mirror Universe vessel was headed for the [[Kabor Prime|Kabor System]] The Rosenante took the Furious under tow, and using their own shields to protect them, opened a Spiral warp conduit to facilitate maneuvers while the Furious conducted the reinstallation of the power relay buses.&lt;br /&gt;
&lt;br /&gt;
==Act Five: [[Kabor Prime]]==&lt;br /&gt;
[[Image:Kabor Prime.jpg|thumb|right|250px|Kabor Prime]]&lt;br /&gt;
&lt;br /&gt;
A few days after the attack on the [[Bynars|Bynar]] Facility in the Hexikor system, the [[ISS Rosenante]] appeared in the Kabor system. Thier target was a secret production facility known as [[Station Omega]]. The facility had been built by a secret research and development branch of Starfleet Sciences Division during the [[Admiral Doenitz|Doenitz]] regime.  Thier primary function was the development of an [[Omega Device]]. &lt;br /&gt;
&lt;br /&gt;
After the end of the [[Federation Civil War]] the facility went underground. Through the actions of a small group of [[Starfleet]] [[Rank|Admiral]]s, all records pointing to the existence of such a facility were erased and the personnel there continued with their research. Through covert means, the facility was equipped with large Class XII phaser batteries for defense. At the heart of the facilities power center was a stabilized [[Omega Molecule]]. The first that the Station had managed to produce.&lt;br /&gt;
&lt;br /&gt;
The ISS Rosneante arrived in the system, intent on collecting the last few remaining components of the Omega device that they needed to create their own version of the weapon. As the [[Mirror Universe]] [[Ahmed Ibn Salid]] had worked at this facility in his universe, he had intimate knowledge of the facilities existence and layout. What he had not known was that the station had been armed, as in his universe, it was not protected.&lt;br /&gt;
&lt;br /&gt;
[[Image:Omega Device.jpg|thumb|left|250px|Omega Device]]&lt;br /&gt;
&lt;br /&gt;
The Mirror universe ship was forced to subdue the facility by force, which cost them a great deal of time, narrowing the lead that they had on their Prime Universe Counterpart the [[USS Rosenante]] and the [[USS Furious]]. This delay would prove to be a great boon to the federation starship over the next few days.&lt;br /&gt;
&lt;br /&gt;
With the retrieval of the components complete, Salid ordered [[Mitena Rixx]] and [[Nathan Benoit]] to begin modifications to the base components to bring them up to specifications of the original Mirror universe version of the omega device. This involved the addition of the previously stolen [[Paratrinic Shield|Paratrinic Shield Generator]] as well as the [[Class 11 Computer| Class 11 Bioneural Computer]].&lt;br /&gt;
&lt;br /&gt;
By the time that the Federation starship had arrived, the mirror universe vessel was gone and the station destroyed. Captain&#039;s Salid and [[Saleke]] wasted no time in the system, instead following the ISS Rosenante&#039;s warp trail towards the Sunali System. With time running out, they realized that they had no choice by to confront the marauding vessel and deal with it once and for all.&lt;br /&gt;
&lt;br /&gt;
==Act Six: Finale==&lt;br /&gt;
[[Rose Beauty2.jpg|thumb|right|250px|Battle of Sunali II]]&lt;br /&gt;
&lt;br /&gt;
The [[USS Rosenante]] and the [[USS Furious]] entered the [[Sunali II|Sunali System]] to find the [[ISS Rosenante]] engaged in the wanton destruction of [[Cardassian]] merchant shipping. These ships although peaceful, had been destroyed simply because they were Cardassian.&lt;br /&gt;
&lt;br /&gt;
The USS Rsoenante ordered the Imperial starship to surrender. That vessel refused.&lt;br /&gt;
&lt;br /&gt;
What followed next was a flurry of conflict, with the Stronger [[ISS Rosenante]] dealing a tremendous amount of damage to both the [[USS Rosenante]] as well as the [[USS Furious]],&lt;br /&gt;
&lt;br /&gt;
During the conflict the Furious engaged her [[Prometheus Class|Tri-vector Attack mode]] to engage the more powerful [[Mirror Universe]] vessel. The Mirror universe [[Andrew Elliot Maddox]] managed to take over the computer of one of the Furious&#039; sections named the Courageous and overload it&#039;s warp core killing all 142 hands on board. &lt;br /&gt;
&lt;br /&gt;
With the battle going against them, captain Salid came up with a plan to stop the Imperial vessel dead in it&#039;s tracks. Building off a suggestion made by [[Rank|Lieutenant]] [[Chance Raschen]], he initiated a transfer of the Omega Directive Protocols into the Imperial Starship&#039;s computer after the junior officer reeled them into communications range for the data transfer. That vessel&#039;s commander, having no experience with the [[Starfleet General Orders &amp;amp; Directives|Omega Directive]] was unable to unlock the ship&#039;s computer, which caused them to lose the battle.&lt;br /&gt;
&lt;br /&gt;
However, the ship had not been neutralized before they had managed to launch the [[Omega Device]] at the [[Sunali II|Sunali]] Sun. Unable to pursue, the Rosenante was forced to allow the [[USS Furious]] to intercept and eventually destroy the weapon.&lt;br /&gt;
&lt;br /&gt;
With the aid of [[Nathan Benoit]] the Furious and the Vigiliant (another element of the Furious), managed to shut down the [[Paratrinic Shield]] protecting the device by bypassing the operating system of the [[Class 11 Computer|Class 11 Bioneural Computer]] that controlled it. With the shields down, The Vigilant was able to destroy the device with Phaser fire just minutes before it would have detonated.&lt;br /&gt;
&lt;br /&gt;
==Act Seven: The Boarding Action==&lt;br /&gt;
&lt;br /&gt;
With the battle over, Captain Salid ordered boarding parties to take possession of the [[ISS Rosenante]].&lt;br /&gt;
&lt;br /&gt;
*Assigned to take the Bridge were [[Jennifer Caskie|Commander Jennifer Caskie]] and [[Thomas Jackson|Lieutenant Tom Jackson]]&lt;br /&gt;
&lt;br /&gt;
*Assigned to Take Engineering were [[Mitena Rixx|Ensign Mitena Rixx]], Crewman Caroline Winters and [[Mike Rosenbauer|Ensign Mike Rosenbauer]].&lt;br /&gt;
&lt;br /&gt;
*Assigned to take the Computer Core were [[T&#039;Larah Sullivan|Commander T&#039;Larah Sullivan]] and [[Robert Smith|Ensign Robert Smith]].&lt;br /&gt;
&lt;br /&gt;
*Assigned to take the Security Center was [[Chance Raschen|Lieutenant Chance Raschen]].&lt;br /&gt;
&lt;br /&gt;
*Assigned to take Sickbay was [[Sam Lopez|Doctor Sam Lopez]] and [[Marta Nunez|Ensign Marta Nunez]]&lt;br /&gt;
&lt;br /&gt;
The teams achieved their goals quickly and with little resistance, as the [[Mirror Universe]] Salid had ordered his crew not to resist.&lt;br /&gt;
&lt;br /&gt;
Meanwhile back aboard the USS Rosenante [[Alimi Morrow|Lieutenant Alimi Morrow]] fought to prevent a warp core collapse. his efforts and those of [[Jon Nayati|Lieutenant Jon Nayati]] and [[V&#039;Shera|Ensign V&#039;Shera]] managed to prevent the destruction of the federation vessel. However, it was not without cost. Morrow was seriously injured in the attempt and was treated for severe radiation poisoning. His condition was so critical that he was placed in Stasis unitl such time as he could receive treatment at [[Geneva Station|Starbase Geneva]]. His life was saved by the quick thinking and intervention of [[Kimiko Ichijo|Doctor Kimiko Ichijo]]&lt;br /&gt;
&lt;br /&gt;
==Act Eight: Homeward Bound==&lt;br /&gt;
&lt;br /&gt;
After the Capture of the [[ISS Rosenante]] a deal was struck by which all the data concerning the [[Omega Conspiracy]] in the prime universe would be handed over to Captain Salid and Saleke in exchange for returning the Imperial ship home.  The agreement was made, after some discussion between The two Federation Commanding Officers and the Rosenante&#039;s First officer [[Jennifer Caskie]].&lt;br /&gt;
&lt;br /&gt;
A technical team was assigned to install an [[Interphasic Field Generator]] aboard the Imperial starship, which would force the ship back into it&#039;s normal universe. This same generator would then self destruct, making it impossible for the [[Imperial Union of Planets]] to recreate the devices for their use. Once the device was installed, the imperial ship was returned to the command of the [[Mirror Universe]] Salid and sent home. All indications suggest that the vessel was returned to their proper universe intact.&lt;br /&gt;
&lt;br /&gt;
The Rosenante, towing the [[USS Furious]] then returned to [[Starbase Geneva]] for repairs. &lt;br /&gt;
&lt;br /&gt;
{{USS Rosenante Missions}}&lt;br /&gt;
&lt;br /&gt;
[[Category: History]][[Category: Mirror Universe]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Into_the_Darkness,_Go_I&amp;diff=55864</id>
		<title>Into the Darkness, Go I</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Into_the_Darkness,_Go_I&amp;diff=55864"/>
		<updated>2012-09-05T16:12:08Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* Act One: Teaser */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Coming Soon!&lt;br /&gt;
&lt;br /&gt;
==Act One: Teaser==&lt;br /&gt;
[[Image:Rose2.png|thumb|right|250px|ISS Rosenante]]&lt;br /&gt;
The ISS Rosenante is assigned by [[Regent]] [[Admiral Doenitz|Doenitz]] to travel to the Sunali system. Earlier in 2407 the Sunali people defected to the invading [[Klingon-Cardassian Alliance]]. The system did not put up any resistance to the invaders and as such Doenitz feared that the other members of the newly formed [[Imperial Union of Planets]] would consider following suit. This action of course would lead to the complete defeat of the IUP. With this in mind the [[ISS Rosenante]] was dispatched to make an example of the Sunali.&lt;br /&gt;
&lt;br /&gt;
[[Image:Sunali Sun Destruction.jpg|thumb|left|250px|The Destruction of the Sunali star]]&lt;br /&gt;
By the time that the Rosenante arrived  The Klingon-Cardassian Alliance had already  begun shifting a large task force into the system. This task force was preparing for a military attack into the heart of the IUP.&lt;br /&gt;
&lt;br /&gt;
The enemy vessel present in  the system were:&lt;br /&gt;
&lt;br /&gt;
Twenty-two [[Klingon]] ships:&lt;br /&gt;
*12 [[Bird-of-Prey|K&#039;Vort Class, Bird-of-Prey]]s&lt;br /&gt;
*6 [[Bird-of-Prey|B&#039;rel Class Bird-of-Prey]]s &lt;br /&gt;
*4 modified [[D7 Class Battle Cruiser]]. &lt;br /&gt;
&lt;br /&gt;
There  are also [[Cardassian]] [[starship]]s in the system.&lt;br /&gt;
&lt;br /&gt;
* 18 [[Galor Class]] &lt;br /&gt;
&lt;br /&gt;
On the Planet, [[Sunali II]] there was a population of 18 million inhabitants.&lt;br /&gt;
&lt;br /&gt;
The ISS Rosenante moved into position by passing the mine perimeter that was only partially completed by the Cardassians. The ship them activated and launched the [[Omega Device]] towards the Sunali Star.&lt;br /&gt;
&lt;br /&gt;
The Rosenante then turned, and fought it&#039;s way pasts several enemy ships and was just barely able to escape the system just as the Omega Device detonated. The resultant explosion destroyed the entire system along with the enemy task force. An unexpected side affect of the Omega affect was an interaction of the energy waves created by the [[Omega Molecule]]&#039;s destruction interacting with the [[Rosenante Class|Spiral Warp Drive ]] of the Rosenante. Somehow this interaction forced the [[Mirror Universe]] ISS Rosenante through an [[Interphasic Rift|Interphasic Tunnel]] which deposited it into the Prime Universe, just outside the Sunali System.&lt;br /&gt;
&lt;br /&gt;
==Act Two: Prologue==&lt;br /&gt;
[[Image:Rosenante-Alt-2up.jpg|thumb|right|250px|USS Rosenante]]&lt;br /&gt;
Unknown to the [[USS Rosenante]] their mirror counterpart has laid in a course to [[Bardon Alpha]]. The Rosenante&#039;s [[Rank|Captain]] [[Ahmed Ibn Salid]] holds an emergency meeting with his three senior most officers, [[Jennifer Caskie]], [[T&#039;Larah Sullivan]] and [[Jon Nayati]]. He explains to them that he has just ordered the USS Rosenante off mission to investigate some critical intelligence. He does not reveal to the the nature of this intelligence, but simply asks for their trust in this issue. Salid states that he is aware that he is breaking regulations and that he realizes that there will be consequences if he is proven to be wrong. However he states that he can not take the chance that the intelligence turns out to be accurate without investigating it. It is his belief that the intelligence he has received could threaten not only the [[United Federation of Planets]] but also the [[Alpha Quadrant]]. All three officers agree to trust Salid&#039;s judgment.&lt;br /&gt;
&lt;br /&gt;
Meanwhile back on Earth, Captain Saleke, former Commanding Officer of the [[USS Hades]] is called to a lunch with [[Rank|Vice Admiral]] [[Errol Heatherby]]. The admiral begins to explain that he has reason to believe that there may be a conspiracy inside the [[Starfleet Command|Admiralty]]. He cites the bizarre fact that several prior Doenitz supporters are now Starship captains in the border region between the [[United Federation of Planets]] and the [[Cardassian Union]]. fearing that there could well be a potential to allow conspiracy to thrive under such conditions, he orders Saleke to take command of the [[USS Furious]], a [[Prometheus Class]] [[starship]] and proceed to the [[Ikev Sector]]. He also warns Saleke that the previous Captain of the Furious was killed in a freak [[Transporter]] accident and that the [[Vulcan]] Captain should proceed with caution.&lt;br /&gt;
&lt;br /&gt;
==Act Three: [[Bardon Alpha]]==&lt;br /&gt;
[[Image:Bardon Alpha.jpg|thumb|left|250px|Bardon Alpha]]&lt;br /&gt;
&lt;br /&gt;
===The Attack===&lt;br /&gt;
&lt;br /&gt;
The ISS Rosenante arrived at the Bardon mining Facility with the intention of stealing a shipment of highly refined [[Boronite]] ore. Captain Salid opened a channel and demanded that the ore be turned over to them. When the facilities administrator, Alix Sorvex, declined, Salid ordered the facility attacked and all personnel except one killed. He ordered an away team to the surface to carry out his orders.&lt;br /&gt;
&lt;br /&gt;
The Assault team was lead by the [[Mirror Universe]] version of [[Jennifer Caskie]]. Other members of the Mirror Universe crew, including Mike Rosenbauer and Aleesa Wyler accompanied her.  Rosenbauer commanded a security team called [[Mike&#039;s Maniacs]], which consisted of  Mirror Universe versions of Sodra, Tyrone Cooper, Mosh, T&#039;Vyr and Eva Saint-Jean. There were also two disposable members of the [[ISS Rosenante]]&#039;s Science team sent along to locate the boronite. once theier job was completed, they were executed and their bodies left behind.&lt;br /&gt;
&lt;br /&gt;
During the raid, Jennifer Caskie murdered the administrator with a bladed-weapon, which seemed to be the preferred method of execution. All other members of the facility crew were killed with the exception of technician Dallas, who was seriously injured by [[Mike Rosenbauer]], and Talia Lorenzo who had managed to avoid detection by hiding inside the facility&#039;s computer core ventilation system.&lt;br /&gt;
&lt;br /&gt;
===The Distress Signal===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
While enroute to the [[Ikev Sector]] the [[USS Rosenante]] intercepted a distress communication from the Bardon Alpha Mining Facility. Captain Salid ordered an intercept course set and the Rosenante raced to respond to the signal. The signal itself was standard except for it&#039;s contents.  The signal claimed that they facility was under attack by a Federation starship, which was identified as the Rosenante. This was not possible as the Rosenante was several hours away when the attack took place.&lt;br /&gt;
&lt;br /&gt;
When the ship arrived at the Bardon Alpha system, they detected no ships and received no replies to their hails.&lt;br /&gt;
&lt;br /&gt;
Wishing to get to the bottom of the signals claim and to search for survivors, [[Rank|Captain]] Salid ordered an away team to the planet&#039;s surface to investigate.&lt;br /&gt;
&lt;br /&gt;
The away team consisted of:&lt;br /&gt;
&lt;br /&gt;
*[[Rank|Commander]] [[Jennifer Caskie]]&lt;br /&gt;
*[[Rank|Lieutenant]] [[Jon Nayati]]&lt;br /&gt;
*[[Rank|Lieutenant]] [[Thomas Jackson]]&lt;br /&gt;
*[[Rank|Ensign]] [[V&#039;Shera]]&lt;br /&gt;
*[[Rank|Ensign]] [[Mitena Rixx]]&lt;br /&gt;
*[[Rank|Ensign]] [[Robert Smith]]&lt;br /&gt;
*[[Rank|Ensign]] [[Sam Lopez]]&lt;br /&gt;
*[[Rank|Ensign]] [[M&#039;Epak]]&lt;br /&gt;
*[[Rank|Ensign]] [[Kimiko Ichijo]]&lt;br /&gt;
*[[Rank|Ensign]] [[Mike Rosenbauer]]&lt;br /&gt;
&lt;br /&gt;
The away team beamed into the facility and immedately broke into two teams.  The first two teams began searching the area for survivors, these teams were comprised of Doctors Lopez and Ichijo as well as elements of the security team. The teams did not find any survivors on their assigned search areas but Doctor Ichijo did find a pair of bodies dressed in unusual uniforms, These two corpses were beamed back to the Rosenante for analysis. They were later discovered to belong to the two science officers from the [[ISS Rosenante]]. They had been executed by under orders from the Mirror Universe [[Jennifer Caskie]] once they had located the refined Boronite.&lt;br /&gt;
&lt;br /&gt;
The second away team consisted of the operations and Engineering team. This group consisted of Lieutenant Jackson and ensigns Rixx and Smith. The team&#039;s orders were to recover tha facility&#039;s sensor logs for study. Because of the extent of the damage, this team was forced to work there way deeper into the facility until they reached the computer core. once there, they gained access to the core and began copying the data for transfer back to the ship.&lt;br /&gt;
&lt;br /&gt;
The third team consisted of Commander Caskie, Lieutenant Nayati and Ensign Rosenbauer. They made thir way to the Administration center of the facility in the hiopes of accessing the facilities shipping manifests and security tapes. While there, they encountered the seriously wounded John Dallas. Dallas injured Rosenbauer, believing him to the be the same man who had assaulted him earlier.  in fact that person had been the [[Mirror Universe]] version of the same man. Dallas was subdued and beamed to the Rosenante for medical treatment.&lt;br /&gt;
&lt;br /&gt;
Caskie and Nayati then uncovered the production manifests and the security logs for the facility. The former showed that the facility had been refining boronite to an exceptionally refined state while the latter uncovered a video image showing Rosenbauer, Caskie and Wyler complacent in the death of the administrator and the attack on the facility.&lt;br /&gt;
&lt;br /&gt;
This information coupled with the mysterious appearance of a second Rosenante class starship, which could only have been built in secret, further convinced Captain Salid that there was indeed a high-level conspiracy ongoing.&lt;br /&gt;
&lt;br /&gt;
===The Furious Arrives===&lt;br /&gt;
&lt;br /&gt;
Despite warnings that they should leave the system by his senior officers, Captain Salid decided to remain at Bardon Alpha in the hopes of gathering some information that could give him a direction of pursuit.&lt;br /&gt;
&lt;br /&gt;
Lieutenant [[Chance Raschen]] after reviewing the telemetry data from the facilities computers managed to extrapolate a possible course for the rogue vessel. However, before it could be pursued the USS furious arrived in the system.&lt;br /&gt;
&lt;br /&gt;
The [[Prometheus Class]] [[starship]] was commanded by [[Rank|Captain]] [[Saleke]]. The [[Vulcan]] CO had once been the Commanding Officer of the [[USS Hades]] during the [[Federation Civil War]], and was renowned for his tactical skill.&lt;br /&gt;
&lt;br /&gt;
Salid was surprised to see Saleke, and suspected that if he was not a willing participant in the conspiracy concerning the creation of an [[Omega Device]] that he may well be manipulated into serving the purposes of that conspiracy. Saleke ordered the surrender of the [[USS Rosenante]], but Salid, uncertain of the Captain&#039;s true loyalties declined and attempted to flee the scene in the hopes of exhonerating the names of the crew.&lt;br /&gt;
&lt;br /&gt;
Saleke engaged the Rosenante, whom he considered attempting to escape from the scene of a crime and shot&#039;s were fired. Still reluctant to destroy the Furious due the the unknown position of Captain Saleke&#039;s affiliations, Salid ordered the long-range communications of the Furious destroyed. inital stages of the battle were ineffective. For the Furious this was caused in part because of the employment of the [[The Chimera Directive|SEDIS]] and in part by the superior shielding possessed by the [[Rosenante Class]] [[Starship]].&lt;br /&gt;
&lt;br /&gt;
However, Saleke had a trick up his sleeve. Earlier, he had ordered the modification of five quantum torpedoes so that they were equipped with a [[Cloaking device|Phased Cloaking Device]]. These torpedoes when launched against the Rosenante ignored her shileds and caused significant damage to the latter vessel&#039;s Environmental Subsystems, lifeboats, secondary phaser array, forward tractor beam emitter and caused a hull breach in main Engineering. The advantage was short lived however, when Salid managed to deplete the Furious&#039; forward shields enough to cause the vessel to veer off in order to avoid a volley of concussive photon torpedoes.&lt;br /&gt;
&lt;br /&gt;
It was a manuever that would later become known as [[The Salid Gambit]]. With the Furious deviated from her pursuit. Salid managed to get the Rosenante into the [[Magnesite]] ore filled asteroid field in the Bardon system known as [[The Mill]]. It was an area familiar to [[Rank|Lieutenant]] [[Chance Raschen]], who had often used the area to avoid or lose [[Cardassian]] pursuit during the [[Cardassian]]-[[Federation]] War. Raschen had served in the [[Irregular Federation Forces]] during the [[Admiral Doenitz|Doentiz]] regieme, before defecting to the [[52nd Fleet]]. His knowledge of the area would prove invaluable to evading the Furious. The high concentration of magnesite ore prevented the use of most navigational sensors withn the confines of the Mill, thus preventing the furious from following the Rosenante. in addition, coupled with the [[The Chimera Directive|HISS]] Stealth System, the Furious was unable to detect the Rosenante from outside the field either.&lt;br /&gt;
&lt;br /&gt;
Saleke ordered the Furious at best speed course around the field in the hopes of catching the Rosenante exitting the other side in the hopes of taking advantage of the Prometheus Class&#039; Tri-vector assault mode. However, once on the other side, the furious detected the decaying signature left by the [[The Chimera Directive|Spiral warp Drive]] of the [[ISS Rosenante]]. &lt;br /&gt;
&lt;br /&gt;
Thinking that the Rosenante had already managed to clear the field and set course for [[Hexikor Prime]], Saleke ordered the Furious to pursue. Meanwhile the USS Rosenante remained in [[The Mill]] conducting repairs.&lt;br /&gt;
&lt;br /&gt;
==Act Four: [[Hexikor Prime]]==&lt;br /&gt;
[[Image:Hexikor Prime.JPG|thumb|right|250px|Hexikor Prime]]&lt;br /&gt;
The [[ISS Rosenante]] arrived at Hexikor Alpha before either the [[USS Furious]] or the [[USS Rosenante]] could intercept her. The crew of the Mirror Universe had a clear set of objectives in mind for the attack and set about capturing them with speed and efficiency. The Mirror Universe Away Team consisted of the Following personnel:&lt;br /&gt;
&lt;br /&gt;
*Commander [[Jennifer Caskie]]&lt;br /&gt;
*Lieutenant [[Jon Nayati]]&lt;br /&gt;
*Lieutenant [[Thomas Jackson]]&lt;br /&gt;
*Ensign [[Mitena Rixx]]&lt;br /&gt;
*Ensign [[Mike Rosenbauer]]&lt;br /&gt;
*Ensign [[Robert Smith]]&lt;br /&gt;
&lt;br /&gt;
This group was tasked with the objective to locate and acquire two pieces of hardware located aboard the Hexikor Alpha facility. These were a [[Paratrinic Shield|Paratrinic Shield Generator]] And a [[Class 11 Computer|Class 11 Bioneural Computer]]. These components would be essential in defining the defensive capabilities of the [[Omega Device]].&lt;br /&gt;
&lt;br /&gt;
After the away team arrived, they encountered Doctors 12 &amp;amp; 14, the [[Bynars|Bynar]] Scientists working on the Paratrinic shield project. They also encountered [[Nathan Benoit]] a recent graduate from [[Starfleet Academy]].&lt;br /&gt;
&lt;br /&gt;
In a struggle, Benoit was attacked and overpowered by the [[Mirror Universe]] Thomas Jackson. The Mirror universe away team chose to capture Doctor 12 and use him as bait. However, Doctor 14 activated the shield generator and managed to transport an unprotected Mirror universe Jackson out into the depths of space beyond the hull of the station. The ISS Rosenante&#039;s Chief of Operations had been killed.&lt;br /&gt;
&lt;br /&gt;
Meanwhile, Rixx and Smith worked to secure the devices and when they had completed their task, they beamed the equipment back to the awaiting Mirror Universe vessel.&lt;br /&gt;
&lt;br /&gt;
It was during that time that station security showed up and a very brief exchange of phaser fire took place. The Mirror Universe group evacuated the station having secured their prize and left the area unmolested. During the Raid Captain Salid had chosen to destroy both facilities long-range communications capabilities&lt;br /&gt;
&lt;br /&gt;
[[Image:Prometheus class.jpg|thumb|left|250px|USS Furious]]&lt;br /&gt;
The USS Furious arrived a little over a day behind the ISS Rosenante&#039;s departure. Captain [[Saleke]] elected to visit the facility in an effort to ferret out additional information concerning the conspiracy alluded to by the Prime Universe&#039;s Captain [[Ahmed Ibn Salid]]. During his visit to the station the Furious&#039; CSO Holis Gralen, a [[Betazoid]] interviewed Commander [[Brian Romeo]] concerning the research of the stolen equipment. Romeo provided a perfect watertight reason for the project, citing a pre-warp culture and an attempt to study a rapidly dying star from the same system. While the evidence was solid, Holis suspected that Romeo was not being entirely truthful.&lt;br /&gt;
&lt;br /&gt;
While Saleke was conducting his investigation abord the Hexikor facility, including interviewing an injured [[Nathan Benoit]], The USS Rosenante entered the Hexikor system under cloak.&lt;br /&gt;
&lt;br /&gt;
Determined not to have a repeat of the encounter at [[Bardon Alpha]], Captain Salid chose to neutralize the threat that the Furious posed by transporting six of their primary power buses off the Furious. These power relay buses, cause the ship to lose all primary power, rendering it unable to use weapons, shields or warp drive.  Salid then ordered the surrender of the Furious but was unwilling to accept the surrender of that vessel from their First Officer Commander Erin Sloane.&lt;br /&gt;
&lt;br /&gt;
Saleke was summoned and his presence was requested aboard the Rosenante. Having been convinced by the data that he had collected thus far in his investigation, Captain Saleke informed Captain Salid that he and his ship were no longer suspects in the attack, nor were the complicit in any plot to acquire and build an Omega Device.  Saleke had, independently, arrived at the same conclusion, that the ISS Rosenante, a ship from the Mirror universe was in fact responsible for the attacks. &lt;br /&gt;
&lt;br /&gt;
It was also clear that the Mirror Universe Rosenante was following a pattern that must have been established in their own universe. Which explained how the marauding vessel knew where to acquire the components for the creation of a new Omega Device.&lt;br /&gt;
&lt;br /&gt;
After some discussions, it was decided that the USS Furious and the USS Rosenante would need to combine forces in order to counter the tactical and homicidal threat now posed by the ISS Rosenante.&lt;br /&gt;
&lt;br /&gt;
As long range scans indicated that the Mirror Universe vessel was headed for the [[Kabor Prime|Kabor System]] The Rosenante took the Furious under tow, and using their own shields to protect them, opened a Spiral warp conduit to facilitate maneuvers while the Furious conducted the reinstallation of the power relay buses.&lt;br /&gt;
&lt;br /&gt;
==Act Five: [[Kabor Prime]]==&lt;br /&gt;
[[Image:Kabor Prime.jpg|thumb|right|250px|Kabor Prime]]&lt;br /&gt;
&lt;br /&gt;
A few days after the attack on the [[Bynars|Bynar]] Facility in the Hexikor system, the [[ISS Rosenante]] appeared in the Kabor system. Thier target was a secret production facility known as [[Station Omega]]. The facility had been built by a secret research and development branch of Starfleet Sciences Division during the [[Admiral Doenitz|Doenitz]] regime.  Thier primary function was the development of an [[Omega Device]]. &lt;br /&gt;
&lt;br /&gt;
After the end of the [[Federation Civil War]] the facility went underground. Through the actions of a small group of [[Starfleet]] [[Rank|Admiral]]s, all records pointing to the existence of such a facility were erased and the personnel there continued with their research. Through covert means, the facility was equipped with large Class XII phaser batteries for defense. At the heart of the facilities power center was a stabilized [[Omega Molecule]]. The first that the Station had managed to produce.&lt;br /&gt;
&lt;br /&gt;
The ISS Rosneante arrived in the system, intent on collecting the last few remaining components of the Omega device that they needed to create their own version of the weapon. As the [[Mirror Universe]] [[Ahmed Ibn Salid]] had worked at this facility in his universe, he had intimate knowledge of the facilities existence and layout. What he had not known was that the station had been armed, as in his universe, it was not protected.&lt;br /&gt;
&lt;br /&gt;
[[Image:Omega Device.jpg|thumb|left|250px|Omega Device]]&lt;br /&gt;
&lt;br /&gt;
The Mirror universe ship was forced to subdue the facility by force, which cost them a great deal of time, narrowing the lead that they had on their Prime Universe Counterpart the [[USS Rosenante]] and the [[USS Furious]]. This delay would prove to be a great boon to the federation starship over the next few days.&lt;br /&gt;
&lt;br /&gt;
With the retrieval of the components complete, Salid ordered [[Mitena Rixx]] and [[Nathan Benoit]] to begin modifications to the base components to bring them up to specifications of the original Mirror universe version of the omega device. This involved the addition of the previously stolen [[Paratrinic Shield|Paratrinic Shield Generator]] as well as the [[Class 11 Computer| Class 11 Bioneural Computer]].&lt;br /&gt;
&lt;br /&gt;
By the time that the Federation starship had arrived, the mirror universe vessel was gone and the station destroyed. Captain&#039;s Salid and [[Saleke]] wasted no time in the system, instead following the ISS Rosenante&#039;s warp trail towards the Sunali System. With time running out, they realized that they had no choice by to confront the marauding vessel and deal with it once and for all.&lt;br /&gt;
&lt;br /&gt;
==Act Six: Finale==&lt;br /&gt;
[[Image:Battle Sunali II.jpg|thumb|right|250px|Battle of Sunali II]]&lt;br /&gt;
&lt;br /&gt;
The [[USS Rosenante]] and the [[USS Furious]] entered the [[Sunali II|Sunali System]] to find the [[ISS Rosenante]] engaged in the wanton destruction of [[Cardassian]] merchant shipping. These ships although peaceful, had been destroyed simply because they were Cardassian.&lt;br /&gt;
&lt;br /&gt;
The USS Rsoenante ordered the Imperial starship to surrender. That vessel refused.&lt;br /&gt;
&lt;br /&gt;
What followed next was a flurry of conflict, with the Stronger [[ISS Rosenante]] dealing a tremendous amount of damage to both the [[USS Rosenante]] as well as the [[USS Furious]],&lt;br /&gt;
&lt;br /&gt;
During the conflict the Furious engaged her [[Prometheus Class|Tri-vector Attack mode]] to engage the more powerful [[Mirror Universe]] vessel. The Mirror universe [[Andrew Elliot Maddox]] managed to take over the computer of one of the Furious&#039; sections named the Courageous and overload it&#039;s warp core killing all 142 hands on board. &lt;br /&gt;
&lt;br /&gt;
With the battle going against them, captain Salid came up with a plan to stop the Imperial vessel dead in it&#039;s tracks. Building off a suggestion made by [[Rank|Lieutenant]] [[Chance Raschen]], he initiated a transfer of the Omega Directive Protocols into the Imperial Starship&#039;s computer after the junior officer reeled them into communications range for the data transfer. That vessel&#039;s commander, having no experience with the [[Starfleet General Orders &amp;amp; Directives|Omega Directive]] was unable to unlock the ship&#039;s computer, which caused them to lose the battle.&lt;br /&gt;
&lt;br /&gt;
However, the ship had not been neutralized before they had managed to launch the [[Omega Device]] at the [[Sunali II|Sunali]] Sun. Unable to pursue, the Rosenante was forced to allow the [[USS Furious]] to intercept and eventually destroy the weapon.&lt;br /&gt;
&lt;br /&gt;
With the aid of [[Nathan Benoit]] the Furious and the Vigiliant (another element of the Furious), managed to shut down the [[Paratrinic Shield]] protecting the device by bypassing the operating system of the [[Class 11 Computer|Class 11 Bioneural Computer]] that controlled it. With the shields down, The Vigilant was able to destroy the device with Phaser fire just minutes before it would have detonated.&lt;br /&gt;
&lt;br /&gt;
==Act Seven: The Boarding Action==&lt;br /&gt;
&lt;br /&gt;
With the battle over, Captain Salid ordered boarding parties to take possession of the [[ISS Rosenante]].&lt;br /&gt;
&lt;br /&gt;
*Assigned to take the Bridge were [[Jennifer Caskie|Commander Jennifer Caskie]] and [[Thomas Jackson|Lieutenant Tom Jackson]]&lt;br /&gt;
&lt;br /&gt;
*Assigned to Take Engineering were [[Mitena Rixx|Ensign Mitena Rixx]], Crewman Caroline Winters and [[Mike Rosenbauer|Ensign Mike Rosenbauer]].&lt;br /&gt;
&lt;br /&gt;
*Assigned to take the Computer Core were [[T&#039;Larah Sullivan|Commander T&#039;Larah Sullivan]] and [[Robert Smith|Ensign Robert Smith]].&lt;br /&gt;
&lt;br /&gt;
*Assigned to take the Security Center was [[Chance Raschen|Lieutenant Chance Raschen]].&lt;br /&gt;
&lt;br /&gt;
*Assigned to take Sickbay was [[Sam Lopez|Doctor Sam Lopez]] and [[Marta Nunez|Ensign Marta Nunez]]&lt;br /&gt;
&lt;br /&gt;
The teams achieved their goals quickly and with little resistance, as the [[Mirror Universe]] Salid had ordered his crew not to resist.&lt;br /&gt;
&lt;br /&gt;
Meanwhile back aboard the USS Rosenante [[Alimi Morrow|Lieutenant Alimi Morrow]] fought to prevent a warp core collapse. his efforts and those of [[Jon Nayati|Lieutenant Jon Nayati]] and [[V&#039;Shera|Ensign V&#039;Shera]] managed to prevent the destruction of the federation vessel. However, it was not without cost. Morrow was seriously injured in the attempt and was treated for severe radiation poisoning. His condition was so critical that he was placed in Stasis unitl such time as he could receive treatment at [[Geneva Station|Starbase Geneva]]. His life was saved by the quick thinking and intervention of [[Kimiko Ichijo|Doctor Kimiko Ichijo]]&lt;br /&gt;
&lt;br /&gt;
==Act Eight: Homeward Bound==&lt;br /&gt;
&lt;br /&gt;
After the Capture of the [[ISS Rosenante]] a deal was struck by which all the data concerning the [[Omega Conspiracy]] in the prime universe would be handed over to Captain Salid and Saleke in exchange for returning the Imperial ship home.  The agreement was made, after some discussion between The two Federation Commanding Officers and the Rosenante&#039;s First officer [[Jennifer Caskie]].&lt;br /&gt;
&lt;br /&gt;
A technical team was assigned to install an [[Interphasic Field Generator]] aboard the Imperial starship, which would force the ship back into it&#039;s normal universe. This same generator would then self destruct, making it impossible for the [[Imperial Union of Planets]] to recreate the devices for their use. Once the device was installed, the imperial ship was returned to the command of the [[Mirror Universe]] Salid and sent home. All indications suggest that the vessel was returned to their proper universe intact.&lt;br /&gt;
&lt;br /&gt;
The Rosenante, towing the [[USS Furious]] then returned to [[Starbase Geneva]] for repairs. &lt;br /&gt;
&lt;br /&gt;
{{USS Rosenante Missions}}&lt;br /&gt;
&lt;br /&gt;
[[Category: History]][[Category: Mirror Universe]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=File:Rose2.png&amp;diff=55863</id>
		<title>File:Rose2.png</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=File:Rose2.png&amp;diff=55863"/>
		<updated>2012-09-05T16:11:50Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Homecoming&amp;diff=55862</id>
		<title>Homecoming</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Homecoming&amp;diff=55862"/>
		<updated>2012-09-05T16:09:55Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:Homecoming.jpg|thumb|250px|right|The Rosenante heads back to Starbase Geneva]]&lt;br /&gt;
&lt;br /&gt;
After escaping from [[The Harvester]] the [[USS Rosenante]] returns to [[Geneva Station|Starbase Geneva]] for repairs and to give the crew some much needed downtime after their ordeal.&lt;br /&gt;
&lt;br /&gt;
During the three month refit, several members of the crew go on extended leave.  Among those is [[Rank|Lieutenant Commander]] [[Jennifer Caskie]] whose return to her Home in Scotland is under less than ideal circumstances. Her trip is one of necessity rather than desire. She is escorting home the body of her long dead husband Donald Caskie, who was a member of the [[USS Epiphany]] crew. Event though he had been decalred dead nearly two decades earlier, it was disovered that Donald was actually reclaimed by the [[Kobali]] aboard the Harvester. His second death too place during a failed attempt to restore himself to his former life after successfuly restoring [[Rank|Lieutenant]] [[T&#039;Larah Sullivan]] to her previous [[Vulcan]] / [[Human]] heritage after she was killed and reclaimed by the Kobali after a [[Hur&#039;q]] raid.&lt;br /&gt;
&lt;br /&gt;
Additionally, [[Chance Raschen]] and [[T&#039;Larah Sullivan]] are accompanied by Lietenant [[T&#039;Kron]] to [[Vulcan (planet)|Vulcan]] where they will participate in the ancient Vulcan ritual of [[Fal-tor-pan]]. raschen is the recipient of Sullivan&#039;s [[Katra]] after she transferred to him just prior to her death at the hand of a Hur&#039;q subcommander.&lt;br /&gt;
&lt;br /&gt;
Meanwhile back aboard the Rosenante, the ship puts on a masquarade party to help revieve some work related tensions. This party is hosted by Lieutenant [[Thomas Jackson]].  Councilor [[Jon Nayati]] ,the ship&#039;s third officer, attends as does Ensign [[Mitena Rixx]], Head nurse [[Katherine &#039;Kitty&#039; Fisher]] and Doctor [[Sam Lopez]].&lt;br /&gt;
&lt;br /&gt;
Elsewhere, Captain [[Ahmed Ibn Salid]] enjoys a nice relaxing leave on [[Bracas V]] where he enjoys some snorkling and sailing. His trip, however is cut short by a mysterious visit from a [[Dominion]] [[Vorta]] named [[Julman]] and an attending group of [[Jem&#039;Hadar]] soldiers. He isn&#039;t seriously injured although one of the Jem&#039;Hadar are less than pleasant. Other than the initial disagreement, the remainder of the meeting goes along well enough. Julman reveals a terrible peice of information to Salid.&lt;br /&gt;
&lt;br /&gt;
The content of that secret will drive him to consider teking the Rosenante off mission. Is hea leading his ship and crew into a possible Dominion trap or is there a possibility that the information that the Vorta revealed could be true. If it is true, the very future of the [[Alpha Quadrant]] may be at risk.&lt;br /&gt;
&lt;br /&gt;
A few days prior to the relaunch of the Rosenante, Sullivan is promoted to Lieutenant Commander, Raschen to Full Lieutenant and Caskie to Full Commander.&lt;br /&gt;
&lt;br /&gt;
{{USS Rosenante Missions}}&lt;br /&gt;
&lt;br /&gt;
[[Category: History]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=File:Homecoming.jpg&amp;diff=55861</id>
		<title>File:Homecoming.jpg</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=File:Homecoming.jpg&amp;diff=55861"/>
		<updated>2012-09-05T16:09:25Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=File:Rosenante-Alt-1up.jpg&amp;diff=55860</id>
		<title>File:Rosenante-Alt-1up.jpg</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=File:Rosenante-Alt-1up.jpg&amp;diff=55860"/>
		<updated>2012-09-05T16:07:21Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: uploaded a new version of &amp;amp;quot;File:Rosenante-Alt-1up.jpg&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;alt 1 up&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Template:USS_Rosenante_Data_Box&amp;diff=55859</id>
		<title>Template:USS Rosenante Data Box</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Template:USS_Rosenante_Data_Box&amp;diff=55859"/>
		<updated>2012-09-05T15:55:10Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;toc colour&amp;quot; style=&amp;quot;margin: 0 0 1em 1em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:goldenrod&amp;quot; align=&amp;quot;center&amp;quot; |&amp;lt;font color=maroon&amp;gt;&#039;&#039;&#039;USS Rosenante&#039;&#039;&#039;&amp;lt;br&amp;gt;&amp;lt;font color=maroon&amp;gt;NCC-924650&amp;lt;/font&amp;gt;&amp;lt;br&amp;gt;Launched 2408.01.07&amp;lt;br&amp;gt;[[Image:Rosenante-Alt-2up.jpg|center|300px|The [[USS Rosenante]] NCC–924650]]&amp;lt;br&amp;gt;[[Image:RoseDedication.jpg|center|300px]]&amp;lt;br&amp;gt;&#039;&#039;&#039;Rosenante Class&#039;&#039;&#039;&amp;lt;br&amp;gt;Long-Range Explorer&amp;lt;/font&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Crew Roster&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Command Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
** [[Ben Soma|Capt. Ben Soma, Commanding Officer]]&lt;br /&gt;
**[[Sanok|Lt. Cmdr Sanok, First Officer/Csec]]&lt;br /&gt;
**[[Tom Jackson|Lt. Tom Jackson, Second Officer/COPS]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Operations Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
**[[Chance Raschen|Lt. Chance Raschen, CTAC]]&lt;br /&gt;
**[[Tollian Yalix|Lt. Tollian Yalix, Assistant Operations Officer]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Medical Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt; &lt;br /&gt;
**[[Nathan Allen Fuller|MCPO Nathan Allen Fuller, Chief Field Medic]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Counseling Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
**None Assigned&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Tactical &amp;amp; Security Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
**[[Jessica Signos|Ens. Jessica Signos, Assistant Tactical Chief]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Engineering Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
**[[Steven Wade Matrix|Lt. Cmdr. Steven Wade Matrix, Chief Engineer]]&lt;br /&gt;
**[[Tho’var Kevras| Lieutenant JG Tho’var Kevras, Assistant Chief Engineer]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Science Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
**[[Andrew Elliot Maddox|Crewman Andrew Elliot Maddox, Science Officer]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Flight Operations Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Other Starfleet Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
**[[Matthew McLaren|Lt. Cmdr. Matthew McLaren, ATTU]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Retired Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
**[[Aleesa Wyler|Lt. Aleesa Wyler, Awaiting Assignment]]&lt;br /&gt;
**[[Alimi Morrow|Lt. Alimi Morrow, Awaiting Assignment]]&lt;br /&gt;
**[[Kimiko Ichijo|Lt. JG Kimiko Ichijo, Awaiting Assignment]]&lt;br /&gt;
**[[Narvak|Ens. JG Narvak, Awaiting Assignment]]&lt;br /&gt;
**[[David Michael Tamblyn|Lt. David Tamblyn, Awaiting Assignment]]&lt;br /&gt;
**[[T&#039;Larah Sullivan|Lt. Col. T&#039;Larah Sullivan, Marine CO]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Missions&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:[[Picking up the Pieces]]&lt;br /&gt;
:[[A Fine and Private Place]] &lt;br /&gt;
:[[Furlough | Letters of Marques]]&lt;br /&gt;
:[[Fields of Elysium]]&lt;br /&gt;
:[[Homecoming]]&lt;br /&gt;
:[[Into the Darkness, Go I]]&lt;br /&gt;
:[[Equals and Opposites]]&lt;br /&gt;
:[[The Quondam Season]]&lt;br /&gt;
:[[The Gilded Man]]&lt;br /&gt;
:[[Touch of the Eidolon]]&lt;br /&gt;
:[[Just Another Saturday Night]]&lt;br /&gt;
:[[Once More Into The Breach]]&lt;br /&gt;
:[[Personal Logs]]&lt;br /&gt;
:[[The Third Law]]&lt;br /&gt;
:[[The Captain&#039;s Cotillion]]&lt;br /&gt;
:[[The Veil of the Sky]] &lt;br /&gt;
:[[A Port in the Storm]] &lt;br /&gt;
:[[The Raven&#039;s Nest]] &lt;br /&gt;
:[[Through the Looking Glass]]**Underway**&lt;br /&gt;
:[[Lest We Forget]] **Coming Soon**&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;&amp;lt;sup&amp;gt;Rosenante image from STO, Bellerophon class starship. &amp;lt;/sup&amp;gt;&amp;lt;/center&amp;gt;&lt;br /&gt;
&amp;lt;center&amp;gt;&amp;lt;sup&amp;gt;Used under fair usage rules. &amp;lt;/sup&amp;gt;&amp;lt;/center&amp;gt;&lt;br /&gt;
&amp;lt;center&amp;gt;&amp;lt;sup&amp;gt;Dedication plaque by Bosshard.&amp;lt;/sup&amp;gt;&amp;lt;/center&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;center&amp;gt;&amp;lt;sup&amp;gt;[[Template:USS Rosenante Missions|Edit Mission List]]&amp;lt;/sup&amp;gt;&amp;lt;/center&amp;gt;&lt;br /&gt;
&amp;lt;center&amp;gt;&amp;lt;sup&amp;gt;[[Template:Rosenante Crew Roster|Edit Crew Roster]]&amp;lt;/sup&amp;gt;&amp;lt;/center&amp;gt;&lt;br /&gt;
&amp;lt;center&amp;gt;&amp;lt;sup&amp;gt;[[Template:USS Rosenante Data Box|Edit Data Box]]&amp;lt;/sup&amp;gt;&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;noinclude&amp;gt;[[Category: Active Ships]]&amp;lt;/noinclude&amp;gt;&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=File:Rosenante-Alt-2up.jpg&amp;diff=55858</id>
		<title>File:Rosenante-Alt-2up.jpg</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=File:Rosenante-Alt-2up.jpg&amp;diff=55858"/>
		<updated>2012-09-05T15:53:12Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Dark_Ages&amp;diff=55451</id>
		<title>Dark Ages</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Dark_Ages&amp;diff=55451"/>
		<updated>2012-05-16T13:50:35Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Petrarch by Bargilla.jpg|thumb|300px|right|Petrarch, who conceived the idea of a European &amp;quot;Dark Age&amp;quot;. From Cycle of Famous Men and Women, Andrea di Bartolo di Bargilla, c. 1450]]&lt;br /&gt;
&lt;br /&gt;
The [[Dark Ages]] is a historical periodization emphasizing the cultural and economic deterioration that supposedly occurred in Europe following the decline of the Roman Empire on [[Earth]]. The label employs traditional light-versus-darkness imagery to contrast the &amp;quot;darkness&amp;quot; of the period with earlier and later periods of &amp;quot;light&amp;quot;. The period is characterized by a relative scarcity of historical and other written records at least for some areas of Europe, rendering it obscure to historians. The term &amp;quot;Dark Age&amp;quot; itself derives from the Latin saeculum obscurum, originally applied by Caesar Baronius in 1602 to a tumultuous period in the 10th and 11th century.&lt;br /&gt;
&lt;br /&gt;
Originally the term characterized the bulk of the Middle Ages, or roughly the 6th to 13th centuries, as a period of intellectual darkness between the extinguishing of the &amp;quot;light of Rome&amp;quot; after the end of Late Antiquity, and the rise of the Italian Renaissance in the 14th century. This definition is still found in popular usage, but increased recognition of the accomplishments of the Middle Ages since the 19th century has led to the label being restricted in application. Since the 20th century, it is frequently applied only to the earlier part of the era, the Early Middle Ages (c. 5th–10th century). However, many modern scholars who study the era tend to avoid the term altogether for its negative connotations, finding it misleading and inaccurate for any part of the Middle Ages.&lt;br /&gt;
&lt;br /&gt;
The concept of a Dark Age originated with the Italian scholar Petrarch (Francesco Petrarca) in the 1330s, and was originally intended as a sweeping criticism of the character of Late Latin literature. Petrarch regarded the post-Roman centuries as &amp;quot;dark&amp;quot; compared to the light of classical antiquity. Later historians expanded the term to refer to the transitional period between Roman times and the High Middle Ages (c. 11th–13th century), including not only the lack of Latin literature, but also a lack of contemporary written history, general demographic decline, limited building activity and material cultural achievements in general. Later historians and writers picked up the concept, and popular culture has further expanded on it as a vehicle to depict the Middle Ages as a time of backwardness, extending its pejorative use and expanding its scope.&lt;br /&gt;
&lt;br /&gt;
[[Category: Database]][[Category: History]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Dark_Ages&amp;diff=55450</id>
		<title>Dark Ages</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Dark_Ages&amp;diff=55450"/>
		<updated>2012-05-16T13:49:53Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: Created page with &amp;quot;[[File:Petrarch by Bargilla.jpg|thumb|300px|right|Petrarch, who conceived the idea of a European &amp;quot;Dark Age&amp;quot;. From Cycle of Famous Men and Women, Andrea di Bartolo di Bargilla,...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Petrarch by Bargilla.jpg|thumb|300px|right|Petrarch, who conceived the idea of a European &amp;quot;Dark Age&amp;quot;. From Cycle of Famous Men and Women, Andrea di Bartolo di Bargilla, c. 1450]]&lt;br /&gt;
&lt;br /&gt;
The [[Dark Ages]] is a historical periodization emphasizing the cultural and economic deterioration that supposedly occurred in Europe following the decline of the Roman Empire on [[Earth]]. The label employs traditional light-versus-darkness imagery to contrast the &amp;quot;darkness&amp;quot; of the period with earlier and later periods of &amp;quot;light&amp;quot;. The period is characterized by a relative scarcity of historical and other written records at least for some areas of Europe, rendering it obscure to historians. The term &amp;quot;Dark Age&amp;quot; itself derives from the Latin saeculum obscurum, originally applied by Caesar Baronius in 1602 to a tumultuous period in the 10th and 11th century.&lt;br /&gt;
&lt;br /&gt;
Originally the term characterized the bulk of the Middle Ages, or roughly the 6th to 13th centuries, as a period of intellectual darkness between the extinguishing of the &amp;quot;light of Rome&amp;quot; after the end of Late Antiquity, and the rise of the Italian Renaissance in the 14th century. This definition is still found in popular usage, but increased recognition of the accomplishments of the Middle Ages since the 19th century has led to the label being restricted in application. Since the 20th century, it is frequently applied only to the earlier part of the era, the Early Middle Ages (c. 5th–10th century). However, many modern scholars who study the era tend to avoid the term altogether for its negative connotations, finding it misleading and inaccurate for any part of the Middle Ages.&lt;br /&gt;
&lt;br /&gt;
The concept of a Dark Age originated with the Italian scholar Petrarch (Francesco Petrarca) in the 1330s, and was originally intended as a sweeping criticism of the character of Late Latin literature. Petrarch regarded the post-Roman centuries as &amp;quot;dark&amp;quot; compared to the light of classical antiquity. Later historians expanded the term to refer to the transitional period between Roman times and the High Middle Ages (c. 11th–13th century), including not only the lack of Latin literature, but also a lack of contemporary written history, general demographic decline, limited building activity and material cultural achievements in general. Later historians and writers picked up the concept, and popular culture has further expanded on it as a vehicle to depict the Middle Ages as a time of backwardness, extending its pejorative use and expanding its scope.&lt;br /&gt;
&lt;br /&gt;
[[Category: Database]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=File:Petrarch_by_Bargilla.jpg&amp;diff=55449</id>
		<title>File:Petrarch by Bargilla.jpg</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=File:Petrarch_by_Bargilla.jpg&amp;diff=55449"/>
		<updated>2012-05-16T13:49:32Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Malleus_Maleficarum&amp;diff=55448</id>
		<title>Malleus Maleficarum</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Malleus_Maleficarum&amp;diff=55448"/>
		<updated>2012-05-16T13:45:41Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: Created page with &amp;quot;[[File:Malleus.jpg|thumb|300px|right|Title page of the seventh Cologne edition of the Malleus Maleficarum, 1520 (from the University of Sydney Library). The Latin title is &amp;quot;MA...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Malleus.jpg|thumb|300px|right|Title page of the seventh Cologne edition of the Malleus Maleficarum, 1520 (from the University of Sydney Library). The Latin title is &amp;quot;MALLEUS MALEFICARUM, Maleficas, &amp;amp; earum hæresim, ut phramea potentissima conterens.&amp;quot; (English: The Hammer of Witches which destroyeth Witches and their heresy as with a two-edged sword).]]&lt;br /&gt;
&lt;br /&gt;
The [[Malleus Maleficarum]] (Latin for &amp;quot;Hammer of the Witches&amp;quot;, or &amp;quot;Der Hexenhammer&amp;quot; in German) is an infamous treatise on witches, written in 1486 by Heinrich Kramer and Jacob Sprenger, Inquisitors of the Catholic Church, and was first published in Germany in 1487. Jacob Sprenger is also often attributed as an author, but some scholars now believe that he became associated with the Malleus Maleficarum largely as a result of Kramer&#039;s wish to lend his book as much official authority as possible.&lt;br /&gt;
&lt;br /&gt;
The main purpose of the Malleus was to attempt to systematically refute arguments claiming that witchcraft does not exist, discredit those who expressed skepticism about its reality, to claim that witches were more often women than men, and to educate magistrates on the procedures that could find them out and convict them.&lt;br /&gt;
&lt;br /&gt;
==Genesis==&lt;br /&gt;
&lt;br /&gt;
The Malleus Maleficarum was published in 1487 by Heinrich Kramer (Latinised Institoris) and James Sprenger (also known as Jacob or Jakob Sprenger). Scholars have debated how much Sprenger contributed to the work. Some say his role was minor, and that the book was written almost entirely by Kramer, who used the name of Sprenger for its prestige only, while others say there is little evidence for this claim.&lt;br /&gt;
&lt;br /&gt;
In 1484 Kramer made one of the first attempts at a systematic persecution of witches in the region of Tyrol. It was not a success: Kramer was thrown out of the territory, and dismissed by the local bishop as a &amp;quot;senile old man&amp;quot;. According to Diarmaid MacCulloch, writing the book was Kramer&#039;s act of self-justification and revenge. Some scholars have suggested that following the failed efforts in Tyrol, Kramer and Sprenger requested and received a papal bull Summis desiderantes affectibus in 1484. It allegedly gave full papal approval for the Inquisition to prosecute witchcraft in general and for Kramer and Sprenger specifically. Malleus Maleficarum was written in 1484 or 1485 and the papal bull was included as part of the preface.&lt;br /&gt;
&lt;br /&gt;
The preface also includes an approbation from the University of Cologne&#039;s Faculty of Theology. The authenticity of the Cologne endorsement was first questioned by Joseph Hansen but Christopher S. Mackay rejects his theory as a misunderstanding. The university in fact condemned the book for unethical legal practices and contradicting Catholic teaching on demons. Scholarly opinion is divided on whether the Cologne endorsement was a complete forgery, but there is general agreement that even if it were genuine it was misrepresented by Kramer, and that neither the Pope nor the University of Cologne was aware of the true authorship of the book, or even of its contents. The Malleus Maleficarum drew on earlier sources such as Johannes Nider&#039;s treatise Formicarius, written 1435/37.&lt;br /&gt;
&lt;br /&gt;
The book became the handbook for secular courts throughout Renaissance Europe, but was not used by the Inquisition, which even cautioned against relying on the work. Between the years 1487 and 1520 the work was published thirteen times. It was again published between the years of 1574 to 1669 a total of sixteen times. Regardless of the authenticity of the endorsements which appear at the beginning of the book, their presence contributed to the popularity of the work.&lt;br /&gt;
&lt;br /&gt;
Folk belief in reality of witchcraft had been denied by the church in earlier centuries; Charlemagne had specifically outlawed the old practice of witch burning &amp;quot;in the manner of the pagans&amp;quot;. By the 15th century, belief in witches was once again openly accepted in European society, but they typically suffered penalties no more harsh than public penances such as a day in the stocks. Persecution of witches became more brutal following the publication of the Malleus, with witchcraft being accepted as a real and dangerous phenomenon.&lt;br /&gt;
&lt;br /&gt;
==Contents==&lt;br /&gt;
&lt;br /&gt;
The Malleus Maleficarum asserts that three elements are necessary for witchcraft: the evil-intentioned witch, the help of the Devil, and the Permission of God. The treatise is divided up into three sections. The first section tries to refute critics who deny the reality of witchcraft, thereby hindering its prosecution. The second section describes the actual forms of witchcraft and its remedies. The third section is to assist judges confronting and combating witchcraft. However, each of these three sections has the prevailing themes of what is witchcraft and who is a witch. The Malleus Maleficarum relies heavily upon earlier works such as Visconti and, most famously, Johannes Nider&#039;s Formicarius (1435).&lt;br /&gt;
==Section I==&lt;br /&gt;
Section I argues that because the Devil exists and has the power to do astounding things, witches exist to help, if done through the aid of the Devil and with the permission of God. The Devil’s power is greatest where human sexuality is concerned, for it was believed that women were more sexual than men. Libidinous women had sex with the Devil, thus paving their way to become witches. According to the Malleus “all witchcraft comes from carnal lust, which is in women insatiable.” The first section mentions using a Cruentation to find a witch or sorcerer.&lt;br /&gt;
==Section II==&lt;br /&gt;
Matters of practice and actual cases are discussed, and the powers of witches and their recruitment strategies. It states that it is mostly witches, as opposed to the Devil, who do the recruiting, by making something go wrong in the life of a respectable matron that makes her consult the knowledge of a witch, or by introducing young maidens to tempting young devils. It details how witches cast spells, and remedies that can be taken to prevent witchcraft, or help those that have been affected by it.&lt;br /&gt;
==Section III==&lt;br /&gt;
Section III is the legal part of the Malleus that describes how to prosecute a witch. The arguments are clearly laid for the lay magistrates prosecuting witches. Institoris and Sprenger offer a step-by-step guide to the conduct of a witch trial, from the method of initiating the process and assembling accusations, to the interrogation (including torture) of witnesses, and the formal charging of the accused. Women who did not cry during their trial were automatically believed to be witches.&lt;br /&gt;
==Section IV==&lt;br /&gt;
&amp;quot;Inquisition&amp;quot; or &amp;quot;Witchcraft&amp;quot; raids in the Europe mainland were mainly supported and financed by the Roman Catholic church. More women than men were subjected to indescribable torture. Many were publicly beaten to death. This textbook is still indexed and recommended for examinations of witchcraft by the Roman Catholic church.&lt;br /&gt;
==Major themes==&lt;br /&gt;
The treatise describes how women and men become inclined for witchcraft. The authors argue that women were more susceptible to demonic temptations through their manifold weaknesses of their gender. It was believed that they were weaker in faith and more carnal than men. Michael Bailey claims that most of the women accused as witches had strong personalities and were known to defy convention by overstepping the lines of proper female decorum. After the publication of the Malleus, it seems as though most of those individuals prosecuted as witches were women. Indeed, the very title of the Malleus Maleficarum is feminine, alluding to the idea that it was women who were the villains. Otherwise, it would be the Malleus Maleficorum (the masculine form of the Latin noun maleficus or malefica, &#039;witch&#039;). In Latin, the feminine &amp;quot;Maleficarum&amp;quot; would only be used for women while the masculine &amp;quot;Maleficorum&amp;quot; could be used for men alone or for both sexes if together. This assertion by Maxwell-Stewart is not definitive for it would be centuries before spelling would become standardized through the process of English-language spelling reform.&lt;br /&gt;
&lt;br /&gt;
The Malleus Maleficarum accuses male and female witches of infanticide, cannibalism and casting evil spells to harm their enemies as well as having the power to steal penises. It goes on to give accounts of witches committing these crimes.&lt;br /&gt;
&lt;br /&gt;
The ancient subjects of astronomy, philosophy, and medicine were being reintroduced to the West at this time, as well as a plethora of ancient texts being rediscovered and studied. The Malleus often makes reference to the Bible and Aristotelian thought, and it is also heavily influenced by the philosophical tenets of Neo-Platonism. It also mentions astrology and astronomy, which had recently been reintroduced to the West by the ancient works of Pythagoras.&lt;br /&gt;
==Factors stimulating widespread use==&lt;br /&gt;
The Malleus Maleficarum was able to spread throughout Europe so rapidly in the late fifteenth and the beginning of the sixteenth century because of the innovation of the printing press in the middle of the fifteenth century by Johannes Gutenberg. That printing should have been invented thirty years before the first publication of the Malleus, which instigated the fervor of witch hunting, and, in the words of Russell, &amp;quot;the swift propagation of the witch hysteria by the press was the first evidence that Gutenberg had not liberated man from original sin.&amp;quot; The Malleus is also heavily influenced by the subjects of divination, astrology, and healing rituals the Church inherited from antiquity.&lt;br /&gt;
&lt;br /&gt;
The late fifteenth century was also a period of religious turmoil, for the Protestant Reformation was but a few decades in the future. The Malleus Maleficarum and the witch craze that ensued took advantage of the increasing intolerance of the Reformation and Counter-Reformation in Europe, where the Protestant and Catholic camps, pitted against one another, each zealously strove to maintain the purity of faith.&lt;br /&gt;
==Consequences==&lt;br /&gt;
Between 1487 and 1520, twenty editions of the Malleus were published, and another sixteen editions were published between 1574 and 1669. However, there is scholarly agreement that publication of the Malleus Maleficarum was not as influential as earlier modern historians originally thought. According to MacCulloch, the Malleus was one of several key factors contributing to the witch craze, along with popular superstition and tensions created by the Reformation.&lt;br /&gt;
&lt;br /&gt;
[[Category: Database]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=File:Malleus.jpg&amp;diff=55447</id>
		<title>File:Malleus.jpg</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=File:Malleus.jpg&amp;diff=55447"/>
		<updated>2012-05-16T13:44:33Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Katherine_Knight&amp;diff=55446</id>
		<title>Katherine Knight</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Katherine_Knight&amp;diff=55446"/>
		<updated>2012-05-16T13:37:16Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Katherine Knight.jpg|thumb|right|300px|Katherine Knight]]&lt;br /&gt;
&lt;br /&gt;
[[Katherine Knight]] is the highest level research scientist currently running the project to try and find a way to use the [[Teravere]] virus as an effective weapon to aid [[Section 31]]’s current aims.&lt;br /&gt;
&lt;br /&gt;
Her life began on [[Betazed]] before she joined [[Starfleet Academy]] once turning 18. Soon after her third year in the science program, she began to realize that [[Starfleet]]’s aims were not the same as her own. Working in secret, she began to try and develop weapons using [[Borg]] [[Nanoprobe|Nanites]]. Her research project was discovered and she was court-martialed.&lt;br /&gt;
Just before her sentencing, she met with a man who was to change her life and destiny, [[Alexander Knight]]. He offered her the chance to work with a group of people that, not only shared her views on the [[Federation]] but, actively encouraged them and would give her the opportunity to carry on her work.&lt;br /&gt;
&lt;br /&gt;
Soon after joining Section 31, she became involved with Alexander Knight and soon became his wife. Now, she is Chief Scientist aboard the S31 base, [[Raven&#039;s Nest Station|Raven&#039;s Nest]], and is responsible for the creation of the [[Signos Thread]]. After loosing her main subject, [[Jessica Signos]], to Captain [[Ahmed Ibn Salid]] and his rescue party, she turned her attention to the Teravere virus.&lt;br /&gt;
&lt;br /&gt;
Realizing it’s potential as a weapon, she is currently working on a way to deploy this as a weapon.&lt;br /&gt;
&lt;br /&gt;
Katherine is 6-foot tall with long red hair and dark eyes. She is a full telepath and is dedicated to her work and her husband. She has no problems in using others to the point of destruction if it helps further her projects and is currently the only person that can control Lily, being the one that implanted the persona within Jessica&#039;s Psyche.&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;Katherine Knight was first seen in the joint [[USS Rosenante]] and [[USS Boudicca]] Mission : &#039;&#039;&#039;[[The Raven&#039;s Nest]]&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Important People]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Katherine_Knight&amp;diff=55445</id>
		<title>Katherine Knight</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Katherine_Knight&amp;diff=55445"/>
		<updated>2012-05-16T13:36:27Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Katherine Knight.jpg|thumb|right|300px|Katherine Knight]]&lt;br /&gt;
&lt;br /&gt;
[[Katherine Knight]] is the highest level research scientist currently running the project to try and find a way to use the [[Teravere]] virus as an effective weapon to aid [[Section 31]]’s current aims.&lt;br /&gt;
&lt;br /&gt;
Her life began on [[Betazed]] before she joined [[Starfleet Academy]] once turning 18. Soon after her third year in the science program, she began to realize that [[Starfleet]]’s aims were not the same as her own. Working in secret, she began to try and develop weapons using [[Borg Nanoprobe|Borg Nanites]]. Her research project was discovered and she was court-martialed.&lt;br /&gt;
Just before her sentencing, she met with a man who was to change her life and destiny, [[Alexander Knight]]. He offered her the chance to work with a group of people that, not only shared her views on the [[Federation]] but, actively encouraged them and would give her the opportunity to carry on her work.&lt;br /&gt;
&lt;br /&gt;
Soon after joining Section 31, she became involved with Alexander Knight and soon became his wife. Now, she is Chief Scientist aboard the S31 base, [[Raven&#039;s Nest Station|Raven&#039;s Nest]], and is responsible for the creation of the [[Signos Thread]]. After loosing her main subject, [[Jessica Signos]], to Captain [[Ahmed Ibn Salid]] and his rescue party, she turned her attention to the Teravere virus.&lt;br /&gt;
&lt;br /&gt;
Realizing it’s potential as a weapon, she is currently working on a way to deploy this as a weapon.&lt;br /&gt;
&lt;br /&gt;
Katherine is 6-foot tall with long red hair and dark eyes. She is a full telepath and is dedicated to her work and her husband. She has no problems in using others to the point of destruction if it helps further her projects and is currently the only person that can control Lily, being the one that implanted the persona within Jessica&#039;s Psyche.&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;Katherine Knight was first seen in the joint [[USS Rosenante]] and [[USS Boudicca]] Mission : &#039;&#039;&#039;[[The Raven&#039;s Nest]]&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Important People]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Katherine_Knight&amp;diff=55444</id>
		<title>Katherine Knight</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Katherine_Knight&amp;diff=55444"/>
		<updated>2012-05-16T13:35:39Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: Created page with &amp;quot;Katherine Knight  Katherine Knight is the highest level research scientist currently running the project to try and find a ...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Katherine Knight.jpg|thumb|right|300px|Katherine Knight]]&lt;br /&gt;
&lt;br /&gt;
[[Katherine Knight]] is the highest level research scientist currently running the project to try and find a way to use the [[Teravere]] virus as an effective weapon to aid [[Section 31]]’s current aims.&lt;br /&gt;
&lt;br /&gt;
Her life began on [[Betazed]] before she joined [[Starfleet Academy]] once turning 18. Soon after her third year in the science program, she began to realize that [[Starfleet]]’s aims were not the same as her own. Working in secret, she began to try and develop weapons using [[Borg Nanoprobe|Borg Nanites]]. Her research project was discovered and she was court-martialed.&lt;br /&gt;
Just before her sentencing, she met with a man who was to change her life and destiny, [[Alexander Knight]]. He offered her the chance to work with a group of people that, not only shared her views on the [[Federation]] but, actively encouraged them and would give her the opportunity to carry on her work.&lt;br /&gt;
&lt;br /&gt;
Soon after joining Section 31, she became involved with Alexander Knight and soon became his wife. Now, she is Chief Scientist aboard the S31 base, [[Raven’s Nest Station|Raven&#039;s Nest]], and is responsible for the creation of the [[Signos Thread]]. After loosing her main subject, [[Jessica Signos]], to Captain [[Ahmed Ibn Salid]] and his rescue party, she turned her attention to the Teravere virus.&lt;br /&gt;
&lt;br /&gt;
Realizing it’s potential as a weapon, she is currently working on a way to deploy this as a weapon.&lt;br /&gt;
&lt;br /&gt;
Katherine is 6-foot tall with long red hair and dark eyes. She is a full telepath and is dedicated to her work and her husband. She has no problems in using others to the point of destruction if it helps further her projects and is currently the only person that can control Lily, being the one that implanted the persona within Jessica&#039;s Psyche.&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;Katherine Knight was first seen in the joint [[USS Rosenante]] and [[USS Boudicca]] Mission : &#039;&#039;&#039;[[The Raven&#039;s Nest]]&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Important People]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Alexander_Knight&amp;diff=55443</id>
		<title>Alexander Knight</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Alexander_Knight&amp;diff=55443"/>
		<updated>2012-05-16T13:35:02Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Alexander Knight.jpg|thumb|right|300px|Alexander Knight]]&lt;br /&gt;
&lt;br /&gt;
*Born: October 31, 2361&lt;br /&gt;
*Birthplace: Las Vegas, Nevada, [[Earth]]&lt;br /&gt;
*Age: 53&lt;br /&gt;
*Affiliation: [[Section 31]]&lt;br /&gt;
 &lt;br /&gt;
[[Alexander Knight]] was born into section 31 following in his father&#039;s and his grandfather&#039;s foot steps .&lt;br /&gt;
&lt;br /&gt;
He learned at an young age that emotions could betray him. So he has learned through many different arts to control his emotions. He rose in the ranks of Section 31 though the interrogation wing of the agency. It was said that he knew how to get any information out of anyone. Alexander is well versed in the arts on interrogation keeping on his person a copy of the [[Malleus Maleficarum]], also know as the witches hammer, from the [[Dark Ages]] of [[Earth]].   &lt;br /&gt;
&lt;br /&gt;
At one point Alexander was embedded at the [[Federation]] [[Starfleet Academy]] as an instructor. It was there he met a inspirational young scientist that would later become his wife. Together they plotted on a way to bring Section 31 back into a position of prominence. They learned of a small child with a special genetic trait that would later become known has the [[Signos Thread]]. &lt;br /&gt;
&lt;br /&gt;
   During the [[Federation Civil War]] the experiments on the kidnapped child lead to Alexander advancing to higher ranks of Section 31. During this time he learned of a top secret installation; a battle station, known as the [[Raven&#039;s Nest Station|Raven&#039;s Nest]]. After the war and the subsequent dissolution of Section 31, Alexander moved to the station and started the rebuild of the organization placing himself at the head of the agency. Now with the firepower of the station and the backing of his wife, Section 31 now has a strong enough leader the restore the agency to it&#039;s prior glory and strive to expand their influence to new levels. The station provided a safe haven for his wife to conduct the experiments the [[Federation]] would not allow.&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;Alexander Knight was first seen in the joint [[USS Rosenante]] and [[USS Boudicca]] Mission : &#039;&#039;&#039;[[The Raven&#039;s Nest]]&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Category: Important People]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Alexander_Knight&amp;diff=55442</id>
		<title>Alexander Knight</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Alexander_Knight&amp;diff=55442"/>
		<updated>2012-05-16T13:34:25Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: Created page with &amp;quot;Alexander Knight  *Born: October 31, 2361 *Birthplace: Las Vegas, Nevada, Earth *Age: 53 *Affiliation: Section 31   [[...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Alexander Knight.jpg|thumb|right|300px|Alexander Knight]]&lt;br /&gt;
&lt;br /&gt;
*Born: October 31, 2361&lt;br /&gt;
*Birthplace: Las Vegas, Nevada, [[Earth]]&lt;br /&gt;
*Age: 53&lt;br /&gt;
*Affiliation: [[Section 31]]&lt;br /&gt;
 &lt;br /&gt;
[[Alexander Knight]] was born into section 31 following in his father&#039;s and his grandfather&#039;s foot steps .&lt;br /&gt;
&lt;br /&gt;
He learned at an young age that emotions could betray him. So he has learned through many different arts to control his emotions. He rose in the ranks of Section 31 though the interrogation wing of the agency. It was said that he knew how to get any information out of anyone. Alexander is well versed in the arts on interrogation keeping on his person a copy of the [[Malleus Maleficarum]], also know as the witches hammer, from the [[Dark Ages]] of [[Earth]].   &lt;br /&gt;
&lt;br /&gt;
At one point Alexander was embedded at the [[Federation]] [[Starfleet Academy]] as an instructor. It was there he met a inspirational young scientist that would later become his wife. Together they plotted on a way to bring Section 31 back into a position of prominence. They learned of a small child with a special genetic trait that would later become known has the [[Signos Thread]]. &lt;br /&gt;
&lt;br /&gt;
   During the [[Federation Civil War]] the experiments on the kidnapped child lead to Alexander advancing to higher ranks of Section 31. During this time he learned of a top secret installation; a battle station, known as the [[Raven&#039;s Nest]]. After the war and the subsequent dissolution of Section 31, Alexander moved to the station and started the rebuild of the organization placing himself at the head of the agency. Now with the firepower of the station and the backing of his wife, Section 31 now has a strong enough leader the restore the agency to it&#039;s prior glory and strive to expand their influence to new levels. The station provided a safe haven for his wife to conduct the experiments the [[Federation]] would not allow.&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;Alexander Knight was first seen in the joint [[USS Rosenante]] and [[USS Boudicca]] Mission : &#039;&#039;&#039;[[The Raven&#039;s Nest]]&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Category: Important People]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=SS_Lalo&amp;diff=55441</id>
		<title>SS Lalo</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=SS_Lalo&amp;diff=55441"/>
		<updated>2012-05-16T13:33:30Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;toc colour&amp;quot; style=&amp;quot;margin: 0 0 1em 1em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:goldenrod&amp;quot; align=&amp;quot;center&amp;quot; |[[File:Edmund Fitzgerald Class freighter.jpg|center|350px|The SS Lalo]]&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;The SS Lalo&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
** Affiliation: [[United Federation of Planets]]&lt;br /&gt;
**Type: Freighter&lt;br /&gt;
**Overall Length: 2,216.75 meters&lt;br /&gt;
**Overall Beam: 110.35 meters&lt;br /&gt;
**Overall Draft: 453.9 meters&lt;br /&gt;
**Decks: 12&lt;br /&gt;
**Displacement Mass: 5,873.44 metric tons&lt;br /&gt;
**Crew: 22, 2 command, 20 general crew&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Power Systems&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
**1 JP-2998 Warp reactors&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Propulsion Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
**Impulse Speeds: .66c&lt;br /&gt;
**Atmospheric Cruise: N/A&lt;br /&gt;
**Atmospheric Max: N/A&lt;br /&gt;
**Normal Warp Cruise: Warp 6.2&lt;br /&gt;
**Maximum Warp: Warp 6.5&lt;br /&gt;
**Emergency Warp: Warp 6.8 (10 minutes)&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Defensive Systems&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
**Phasers: 4 Type VI (180-degree arc, dorsal, Ventral, port, starboard)&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Shields and Armor&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
**Armor: Standard Class III Civil Hull plating&lt;br /&gt;
**Primary Shielding: DEA Class VIII Shields&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
The [[SS Lalo]] is a warp-capable [[Federation]] freighter of the [[Edmund Fitzgerald Class]] Freighter. The vessels are a fairly new design, that utilizes a sleek, high speed hull. Designed to be operated entirely in micro-to-null gravity, the class cannot operate inside any significant gravity well.&lt;br /&gt;
&lt;br /&gt;
The ship is capable of hauling a massive amount of cargo, ranging from raw ores, to finished products. The individual cargo compartments can be set to varying environments, thus allowing for the transport of temperature or humidity sensitive cargoes as well as live cargo such as livestock. &lt;br /&gt;
&lt;br /&gt;
The vessel is 2200 meters long, making her longer than every other ship in the entire Federation fleet. There are currently only 12 operational Edmund Fitzgerald class freighters in operation.&lt;br /&gt;
&lt;br /&gt;
The vessels shape is more reminiscent of a missile rather than a Federation starship, and it&#039;s singular axis design, marks a distinct departure from standard federation [[starship]] design. The vessel&#039;s numbers cargo containers are modular and are accessible for loading and unloading or replacement along the length of this ship&#039;s spine.  beneath the cargo space, is the single warp nacelle that permits the vessel to achieve a maximum cruising speed of warp 6.2. The nacelle is integrated into the vessel&#039;s ensign for added stability and added protection against possible pirate attacks.&lt;br /&gt;
&lt;br /&gt;
The ship is armed with four type VI phaser strips, one along each of the longitudinal axises (Dorsal, Ventral, Port, Starboard), as a result the ship is fairly well defended for a cargo ship, although it has a distinct weakness at the bow and stern, where blind spots form naturally as a result of the ship&#039;s weapons arrangement.&lt;br /&gt;
&lt;br /&gt;
The crew and common areas are located forward and are considered well-appointed, especially for the type of vessel. The rooms are large for cargo ships, and the automation means that there are a small number of crew required to operate the vessel efficiently. As an emergency backup, there is a second bridge and an emergency crew shelter located near the rear of the vessel. The ship has no shuttle hangers, and depends upon either hard docking or transporters to move personnel. The primary docking junction is located on the port side forward nose.&lt;br /&gt;
&lt;br /&gt;
The vessel  is equipped with a very efficient impulse and maneuvering thruster system that makes the need for tugs almost non-existent.&lt;br /&gt;
&lt;br /&gt;
in 2414, the [[USS Boudicca]] and the [[USS Rosenante]] detected the seemingly abandoned Lalo, in [[Sector 6309]]. The vessel had been reported seized by a group of militant separatists from a port while re-provisioning.  &lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;The Lalo was first seen in the joint [[USS Rosenante]] and [[USS Boudicca]] Mission : &#039;&#039;&#039;[[The Raven&#039;s Nest]]&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Federation Support Craft]][[Category: Other Starships]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=File:Alexander_Knight.jpg&amp;diff=55440</id>
		<title>File:Alexander Knight.jpg</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=File:Alexander_Knight.jpg&amp;diff=55440"/>
		<updated>2012-05-16T13:31:56Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=File:Katherine_Knight.jpg&amp;diff=55439</id>
		<title>File:Katherine Knight.jpg</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=File:Katherine_Knight.jpg&amp;diff=55439"/>
		<updated>2012-05-16T13:30:41Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=The_Raven%27s_Nest&amp;diff=55438</id>
		<title>The Raven&#039;s Nest</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=The_Raven%27s_Nest&amp;diff=55438"/>
		<updated>2012-05-16T13:30:04Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;----&lt;br /&gt;
&amp;lt;strong&amp;gt;&amp;lt;font color= Goldenrod&amp;gt; COMING SOON!&amp;lt;/font&amp;gt;&amp;lt;/strong&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
*[[Raven&#039;s Nest Station]]&lt;br /&gt;
*[[Raven Fighter]]&lt;br /&gt;
*[[Section 31]]&lt;br /&gt;
*[[Teravere]]&lt;br /&gt;
*[[Signos Thread]]&lt;br /&gt;
*[[General Deen M&#039;locha]]&lt;br /&gt;
*[[Aquarii]]&lt;br /&gt;
*[[SS Lalo]]&lt;br /&gt;
*[[Edmund Fitzgerald Class]]&lt;br /&gt;
*[[Alexander Knight]]&lt;br /&gt;
*[[Katherine Knight]]&lt;br /&gt;
&lt;br /&gt;
[[Category: History]]&lt;br /&gt;
{{USS Rosenante Missions}}&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Soldarin_Archives&amp;diff=55405</id>
		<title>Soldarin Archives</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Soldarin_Archives&amp;diff=55405"/>
		<updated>2012-05-09T23:51:31Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: Undo revision 35349 by 178.239.58.143 (talk)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Soldarin Archives.jpg|thumb|right|300px|The Soldarin Archives]]&lt;br /&gt;
The [[Soldarin Archives]] were a repository of knowledge built by the [[Soldarin]] race. It was fundamentally a massive biological library containing the memories and knowledge of hundreds of thousands of species, whose data had been collected by the [[Soldarin Archive Probe]].&lt;br /&gt;
&lt;br /&gt;
In 2414, the [[USS Rosenante]] encountered the probe outside the [[Omicron Persei System]] in the [[Beta Quadrant]]. As a result the memories and minds of some of the ship&#039;s crew were captured and deposited here.&lt;br /&gt;
&lt;br /&gt;
The Archive created a complex Holographic program that allowed it&#039;s collected consciences to mingle and communicate with each other, since they were going to be living virtually forever. It was through this medium that the captured members of the Rosenante crew were capable of communicating with an away team from their ship.&lt;br /&gt;
&lt;br /&gt;
The Archive was located on the moon [[Kadyl]] also known as &#039;&#039;Omicron Persei Ia&#039;&#039;.  Within the confines of the Archives was  the [[Soldarin Memory Extraction Machine]].&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;The Soldarin Archives were first seen in the [[USS Rosenante]] Mission &#039;&#039;&#039;[[Lest We Forget]]&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Category: Artifacts and Probes]][[Category: Locations]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Sector_6309&amp;diff=55404</id>
		<title>Sector 6309</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Sector_6309&amp;diff=55404"/>
		<updated>2012-05-09T23:47:20Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* Species native to Sector 6309 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Starmap-sector 6309.jpg|thumb|right|400px|Sector 6309]]&lt;br /&gt;
&lt;br /&gt;
[[Sector 6309]] is a sector of space located adjacent to the borders of three political territories. The sector spans into the [[Alpha Quadrant|Alpha]], [[Beta Quadrant|Beta]], and [[Gamma Quadrant]]s. The sector is of political and strategic interest to the [[United Federation of Planets]], the [[Romulan Star Empire]] and the [[Cardassian Union]]. Each sees it as an area that is resource rich, strategically important and suitable for expansion and colonization. In addition to being located near these critical powers, the sector also contains the [[planet]]s [[Beta Aquillia IV]], [[Kozan-Kozana|Kozan]], [[Kozan-Kozana|Kozana]] and [[Dovek II]].&lt;br /&gt;
&lt;br /&gt;
In anticipation of establishing future colonies in this region, the Federation Council and [[Starfleet]] have ordered the [[USS Rosenante]] to conduct long-term strategic, resource and scientific surveys of the sector. The Rosenante was given the task of establishing strategic remote monitoring posts in the region for the purpose of monitoring the activities of the RSE and the CU in the area.&lt;br /&gt;
&lt;br /&gt;
Within a few weeks of their arrival into the sector, the Rosenante has discovered the [[Rogue Planet]] [[Solyon]], as well as a previously unmet civilization in the [[Asrai]].&lt;br /&gt;
&lt;br /&gt;
As survey information becomes available this data page will be updated to reflect the most current data.&lt;br /&gt;
&lt;br /&gt;
==Areas of Interest==&lt;br /&gt;
*[[Asrai Prime]]&lt;br /&gt;
*[[Beta Aquillia IV]]&lt;br /&gt;
*[[Dovek II]]&lt;br /&gt;
*[[Kozan-Kozana|Kozan and Kozana]]&lt;br /&gt;
*[[Solyon]]&lt;br /&gt;
&lt;br /&gt;
==Species Native to Sector 6309==&lt;br /&gt;
*[[Aquillian]]&lt;br /&gt;
*[[Asrai]]&lt;br /&gt;
*[[Kozani]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;Sector 6309 was first seen in the [[USS Rosenante]] Mission &#039;&#039;&#039;[[The Third Law]]&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{{USS Rosenante Missions}}&lt;br /&gt;
[[Category: Locations]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Sector_6309&amp;diff=55403</id>
		<title>Sector 6309</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Sector_6309&amp;diff=55403"/>
		<updated>2012-05-09T23:46:31Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Starmap-sector 6309.jpg|thumb|right|400px|Sector 6309]]&lt;br /&gt;
&lt;br /&gt;
[[Sector 6309]] is a sector of space located adjacent to the borders of three political territories. The sector spans into the [[Alpha Quadrant|Alpha]], [[Beta Quadrant|Beta]], and [[Gamma Quadrant]]s. The sector is of political and strategic interest to the [[United Federation of Planets]], the [[Romulan Star Empire]] and the [[Cardassian Union]]. Each sees it as an area that is resource rich, strategically important and suitable for expansion and colonization. In addition to being located near these critical powers, the sector also contains the [[planet]]s [[Beta Aquillia IV]], [[Kozan-Kozana|Kozan]], [[Kozan-Kozana|Kozana]] and [[Dovek II]].&lt;br /&gt;
&lt;br /&gt;
In anticipation of establishing future colonies in this region, the Federation Council and [[Starfleet]] have ordered the [[USS Rosenante]] to conduct long-term strategic, resource and scientific surveys of the sector. The Rosenante was given the task of establishing strategic remote monitoring posts in the region for the purpose of monitoring the activities of the RSE and the CU in the area.&lt;br /&gt;
&lt;br /&gt;
Within a few weeks of their arrival into the sector, the Rosenante has discovered the [[Rogue Planet]] [[Solyon]], as well as a previously unmet civilization in the [[Asrai]].&lt;br /&gt;
&lt;br /&gt;
As survey information becomes available this data page will be updated to reflect the most current data.&lt;br /&gt;
&lt;br /&gt;
==Areas of Interest==&lt;br /&gt;
*[[Asrai Prime]]&lt;br /&gt;
*[[Beta Aquillia IV]]&lt;br /&gt;
*[[Dovek II]]&lt;br /&gt;
*[[Kozan-Kozana|Kozan and Kozana]]&lt;br /&gt;
*[[Solyon]]&lt;br /&gt;
&lt;br /&gt;
==Species native to Sector 6309==&lt;br /&gt;
*[[Aquillian]]&lt;br /&gt;
*[[Asrai]]&lt;br /&gt;
*[[Kozani]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;Sector 6309 was first seen in the [[USS Rosenante]] Mission &#039;&#039;&#039;[[The Third Law]]&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{{USS Rosenante Missions}}&lt;br /&gt;
[[Category: Locations]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Sector_6309&amp;diff=55402</id>
		<title>Sector 6309</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Sector_6309&amp;diff=55402"/>
		<updated>2012-05-09T23:44:38Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Starmap-sector 6309.jpg|thumb|right|400px|Sector 6309]]&lt;br /&gt;
&lt;br /&gt;
[[Sector 6309]] is a sector of space located adjacent to the borders of three political territories. The sector spans into the [[Alpha Quadrant|Alpha]], [[Beta Quadrant|Beta]], and [[Gamma Quadrant]]s. The sector is of political and strategic interest to the [[United Federation of Planets]], the [[Romulan Star Empire]] and the [[Cardassian Union]]. Each sees it as an area that is resource rich, strategically important and suitable for expansion and colonization. In addition to being located near these critical powers, the sector also contains the [[planet]]s [[Beta Aquillia IV]], [[Kozan-Kozana|Kozan]], [[Kozan-Kozana|Kozana]] and [[Dovek II]].&lt;br /&gt;
&lt;br /&gt;
In anticipation of establishing future colonies in this region, the Federation Council and [[Starfleet]] have ordered the [[USS Rosenante]] to conduct long-term strategic, resource and scientific surveys of the sector. The Rosenante was given the task of establishing strategic remote monitoring posts in the region for the purpose of monitoring the activities of the RSE and the CU in the area.&lt;br /&gt;
&lt;br /&gt;
Within a few weeks of their arrival into the sector, the Rosenante has discovered the [[Rogue Planet]] [[Solyon]], as well as a previously unmet civilization in the [[Asrai]].&lt;br /&gt;
&lt;br /&gt;
As survey information becomes available this data page will be updated to reflect the most current data.&lt;br /&gt;
&lt;br /&gt;
==Areas of Interest==&lt;br /&gt;
*[[Asrai Prime]]&lt;br /&gt;
*[[Beta Aquillia IV]]&lt;br /&gt;
*[[Dovek II]]&lt;br /&gt;
*[[Kozan-Kozana|Kozan and Kozana]]&lt;br /&gt;
*[[Solyon]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;Sector 6309 was first seen in the [[USS Rosenante]] Mission &#039;&#039;&#039;[[The Third Law]]&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{{USS Rosenante Missions}}&lt;br /&gt;
[[Category: Locations]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Sector_6309&amp;diff=55401</id>
		<title>Sector 6309</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Sector_6309&amp;diff=55401"/>
		<updated>2012-05-09T23:43:24Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Starmap-sector 6309.jpg|thumb|right|400px|Sector 6309]]&lt;br /&gt;
&lt;br /&gt;
[[Sector 6309]] is a sector of space located adjacent to the borders of three political territories. The sector spans into the [[Alpha Quadrant|Alpha]], [[Beta Quadrant|Beta]], and [[Gamma Quadrant]]s. The sector is of political and strategic interest to the [[United Federation of Planets]], the [[Romulan Star Empire]] and the [[Cardassian Union]]. Each sees it as an area that is resource rich, strategically important and suitable for expansion and colonization. In addition to being located near these critical powers, the sector also contains the [[planet]]s [[Beta Aquillia IV]] and [[Dovek II]].&lt;br /&gt;
&lt;br /&gt;
In anticipation of establishing future colonies in this region, the Federation Council and [[Starfleet]] have ordered the [[USS Rosenante]] to conduct long-term strategic, resource and scientific surveys of the sector. The Rosenante was given the task of establishing strategic remote monitoring posts in the region for the purpose of monitoring the activities of the RSE and the CU in the area.&lt;br /&gt;
&lt;br /&gt;
Within a few weeks of their arrival into the sector, the Rosenante has discovered the [[Rogue Planet]] [[Solyon]], as well as a previously unmet civilization in the [[Asrai]].&lt;br /&gt;
&lt;br /&gt;
As survey information becomes available this data page will be updated to reflect the most current data.&lt;br /&gt;
&lt;br /&gt;
==Areas of Interest==&lt;br /&gt;
*[[Asrai Prime]]&lt;br /&gt;
*[[Beta Aquillia IV]]&lt;br /&gt;
*[[Dovek II]]&lt;br /&gt;
*[[Kozan-Kozana|Kozan and Kozana]]&lt;br /&gt;
*[[Solyon]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;Sector 6309 was first seen in the [[USS Rosenante]] Mission &#039;&#039;&#039;[[The Third Law]]&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{{USS Rosenante Missions}}&lt;br /&gt;
[[Category: Locations]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=SS_Lalo&amp;diff=55400</id>
		<title>SS Lalo</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=SS_Lalo&amp;diff=55400"/>
		<updated>2012-05-09T23:41:43Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;toc colour&amp;quot; style=&amp;quot;margin: 0 0 1em 1em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:goldenrod&amp;quot; align=&amp;quot;center&amp;quot; |[[File:Edmund Fitzgerald Class freighter.jpg|center|350px|The SS Lalo]]&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;The SS Lalo&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
** Affiliation: [[United Federation of Planets]]&lt;br /&gt;
**Type: Freighter&lt;br /&gt;
**Overall Length: 2,216.75 meters&lt;br /&gt;
**Overall Beam: 110.35 meters&lt;br /&gt;
**Overall Draft: 453.9 meters&lt;br /&gt;
**Decks: 12&lt;br /&gt;
**Displacement Mass: 5,873.44 metric tons&lt;br /&gt;
**Crew: 22, 2 command, 20 general crew&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Power Systems&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
**1 JP-2998 Warp reactors&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Propulsion Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
**Impulse Speeds: .66c&lt;br /&gt;
**Atmospheric Cruise: N/A&lt;br /&gt;
**Atmospheric Max: N/A&lt;br /&gt;
**Normal Warp Cruise: Warp 6.2&lt;br /&gt;
**Maximum Warp: Warp 6.5&lt;br /&gt;
**Emergency Warp: Warp 6.8 (10 minutes)&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Defensive Systems&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
**Phasers: 4 Type VI (180-degree arc, dorsal, Ventral, port, starboard)&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Shields and Armor&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
**Armor: Standard Class III Civil Hull plating&lt;br /&gt;
**Primary Shielding: DEA Class VIII Shields&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
The [[SS Lalo]] is a warp-capable [[Federation]] freighter of the [[Edmund Fitzgerald Class]] Freighter. The vessels are a fairly new design, that utilizes a sleek, high speed hull. Designed to be operated entirely in micro-to-null gravity, the class cannot operate inside any significant gravity well.&lt;br /&gt;
&lt;br /&gt;
The ship is capable of hauling a massive amount of cargo, ranging from raw ores, to finished products. The individual cargo compartments can be set to varying environments, thus allowing for the transport of temperature or humidity sensitive cargos as well as live cargo such as livestock. &lt;br /&gt;
&lt;br /&gt;
The vessel is 2200 meters long, making her longer than every other ship in the entire Federation fleet. There are currently only 12 operational Edmund Fitzgerald class freighters in operation.&lt;br /&gt;
&lt;br /&gt;
The vessels shape is more reminiscent of a missile rather than a Federation starship, and it&#039;s singular axis design, marks a distinct departure from standard federation [[starship]] design. The vessel&#039;s numbers cargo containers are modular and are accessible for loading and unloading or replacement along the length of this ship&#039;s spine.  beneath the cargo space, is the single warp nacelle that permits the vessel to achieve a maximum cruising speed of warp 6.2. The nacelle is integrated into the vessel&#039;s ensign for added stability and added protection against possible pirate attacks.&lt;br /&gt;
&lt;br /&gt;
The ship is armed with four type VI phaser strips, one along each of the longitudinal axises (Dorsal, Ventral, Port, Starboard), as a result the ship is fairly well defended for a cargo ship, although it has a distinct weakness at the bow and stern, where blind spots form naturally as a result of the ship&#039;s weapons arrangement.&lt;br /&gt;
&lt;br /&gt;
The crew and common areas are located forward and are considered well-appointed, especially for the type of vessel. The rooms are large for cargo ships, and the automation means that there are a small number of crew required to operate the vessel efficiently. As an emergency backup, there is a second bridge and an emergency crew shelter located near the rear of the vessel. The ship has no shuttle hangers, and depends upon either hard docking or transporters to move personnel. The primary docking junction is located on the port side forward nose.&lt;br /&gt;
&lt;br /&gt;
The vessel  is equipped with a very efficient impulse and maneuvering thruster system that makes the need for tugs almost non-existent.&lt;br /&gt;
&lt;br /&gt;
in 2414, the [[USS Boudicca]] and the [[USS Rosenante]] detected the seemingly abandoned Lalo, in [[Sector 6309]]. The vessel had been reported seized by a group of militant separatists from a port while re-provisioning.  &lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;The Lalo was first seen in the joint [[USS Rosenante]] and [[USS Boudicca]] Mission : &#039;&#039;&#039;[[The Raven&#039;s Nest]]&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Federation Support Craft]][[Category: Other Starships]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Edmund_Fitzgerald_Class&amp;diff=55399</id>
		<title>Edmund Fitzgerald Class</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Edmund_Fitzgerald_Class&amp;diff=55399"/>
		<updated>2012-05-09T23:41:15Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;toc colour&amp;quot; style=&amp;quot;margin: 0 0 1em 1em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:goldenrod&amp;quot; align=&amp;quot;center&amp;quot; |[[File:Edmund Fitzgerald Class freighter.jpg |center|350px|]]&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;Edmund Fitzgerald Class Freighter.&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
** Affiliation: [[United Federation of Planets]]&lt;br /&gt;
**Type: Freighter&lt;br /&gt;
**Overall Length: 2,216.75 meters&lt;br /&gt;
**Overall Beam: 110.35 meters&lt;br /&gt;
**Overall Draft: 453.9 meters&lt;br /&gt;
**Decks: 12&lt;br /&gt;
**Displacement Mass: 5,873.44 metric tons&lt;br /&gt;
**Crew: 22, 2 command, 20 general crew&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Power Systems&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
**1 JP-2998 Warp reactors&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Propulsion Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
**Impulse Speeds: .66c&lt;br /&gt;
**Atmospheric Cruise: N/A&lt;br /&gt;
**Atmospheric Max: N/A&lt;br /&gt;
**Normal Warp Cruise: Warp 6.2&lt;br /&gt;
**Maximum Warp: Warp 6.5&lt;br /&gt;
**Emergency Warp: Warp 6.8 (10 minutes)&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Defensive Systems&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
**Phasers: 4 Type VI (180-degree arc, dorsal, Ventral, port, starboard)&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Shields and Armor&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
**Armor: Standard Class III Civil Hull plating&lt;br /&gt;
**Primary Shielding: DEA Class VIII Shields&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
The [[Edmund Fitzgerald Class]] is a warp-capable [[Federation]] freighter. The vessels are a fairly new design, that utilizes a sleek, high speed hull. Designed to be operated entirely in micro-to-null gravity, the class cannot operate inside any significant gravity well.&lt;br /&gt;
&lt;br /&gt;
The ship is capable of hauling a massive amount of cargo, ranging from raw ores, to finished products. The individual cargo compartments can be set to varying environments, thus allowing for the transport of temperature or humidity sensitive cargos as well as live cargo such as livestock. &lt;br /&gt;
&lt;br /&gt;
The vessel is 2200 meters long, making her longer than every other ship in the entire Federation fleet. There are currently only 12 operational Edmund Fitzgerald class freighters in operation.&lt;br /&gt;
&lt;br /&gt;
The vessels shape is more reminiscent of a missile rather than a Federation starship, and it&#039;s singular axis design, marks a distinct departure from standard federation [[starship]] design. The vessel&#039;s numbers cargo containers are modular and are accessible for loading and unloading or replacement along the length of this ship&#039;s spine.  beneath the cargo space, is the single warp nacelle that permits the vessel to achieve a maximum cruising speed of warp 6.2. The nacelle is integrated into the vessel&#039;s ensign for added stability and added protection against possible pirate attacks.&lt;br /&gt;
&lt;br /&gt;
The ship is armed with four type VI phaser strips, one along each of the longitudinal axises (Dorsal, Ventral, Port, Starboard), as a result the ship is fairly well defended for a cargo ship, although it has a distinct weakness at the bow and stern, where blind spots form naturally as a result of the ship&#039;s weapons arrangement.&lt;br /&gt;
&lt;br /&gt;
The crew and common areas are located forward and are considered well-appointed, especially for the type of vessel. The rooms are large for cargo ships, and the automation means that there are a small number of crew required to operate the vessel efficiently. As an emergency backup, there is a second bridge and an emergency crew shelter located near the rear of the vessel. The ship has no shuttle hangers, and depends upon either hard docking or transporters to move personnel. The primary docking junction is located on the port side forward nose.&lt;br /&gt;
&lt;br /&gt;
The vessel  is equipped with a very efficient impulse and maneuvering thruster system that makes the need for tugs almost non-existent.&lt;br /&gt;
&lt;br /&gt;
A ship of this class, the [[SS Lalo]] was encountered by the [[USS Boudicca]] and the [[USS Rosenante]], in 2414. It appeared to have been abandoned and was located in [[Sector 6309]].&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;The Edmund Fitzgerald Class freighter was first seen in the joint [[USS Rosenante]] and [[USS Boudicca]] Mission : &#039;&#039;&#039;[[The Raven&#039;s Nest]]&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Federation Support Craft]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=The_Chimera_Directive&amp;diff=55398</id>
		<title>The Chimera Directive</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=The_Chimera_Directive&amp;diff=55398"/>
		<updated>2012-05-09T23:20:59Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* 10.0 Sensor Displacement System */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;  &lt;br /&gt;
  &lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
== 1.0	CHIMERA DIRECTIVE INTRODUCTION ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-1up.jpg|thumb|500px|The Rosenante Class Starship]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1.1 MISSION OBJECTIVES FOR ROSENANTÉ CLASS PROJECT&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Starfleet has long been charged with a broad spectrum of responsibilities to the citizens of the Federation and to the lifeforms of the Galaxy at large. As the volume of explored space continues to grow, and with it the Federation itself, so do Starfleet&#039;s duties. &lt;br /&gt;
&lt;br /&gt;
These duties range from relatively mundane domestic and civil missions, to cultural contact and diplomacy, to defense, to our primary mission of exploration and research. Many of these responsibilities are best carried out with relatively small, specialized ships. Yet there continues to be an ongoing need for an even narrower role vessel to protect the Federation against enemies that would use espionage and subversion to wage war against the Federation.&lt;br /&gt;
&lt;br /&gt;
This particular threat to Federation security is further complicated by political and economic restraints placed upon the Federation caused by the demands of maintaining an active war first against the Cardassian Union and then a Civil War between Doenitz Loyalists and 52nd Fleet seditionists. The Federation had suddenly found itself pressed on many fronts at various levels of engagement, often ill-prepared or incapable of information gathering against potential interior and exterior threats to the continued existence of the Federation.&lt;br /&gt;
&lt;br /&gt;
In response to the alarming number of intelligence related activities conducted against Federation projects, personnel, and equipment by exterior Intelligence Organizations, such as the Tal Shiar, the Dominion Shapeshifters, and The Cardassian Obsidian Order, Starfleet Intelligence has found itself grossly outnumbered, and under-appreciated by Starfleet Command. This lack of interdepartmental cooperation was only strengthened by Starfleet Intelligence&#039;s inability to detect and detain several pro-Revolutionary agents that had managed to infiltrate Starfleet Command, the Council of the President, and several other critical posts within the governmental structure of the Federation. The agents proved to be the first signs of the coming Civil war that would shake the foundations of the United Federation of Planets over the next several years.&lt;br /&gt;
&lt;br /&gt;
These breeches of critical security protocol within the government provided the critics of Starfleet Intelligence with ammunition to pressure Starfleet Command to tighten its control on the Intelligence Department. In late 2390s, with the Cardassian Union pressing their offensive against the Federation, Starfleet Intelligence learned of other threats to the Federation&#039;s continuing existence, as reports began to come into Starfleet Intelligence&#039;s Romulan desk reporting a large number of Romulan Infiltrators had somehow managed to concentrate themselves on the Federation Starships patrolling the Neutral Zone. With reports indicating that the Tal Shiar compromised a large majority of Starships patrolling the Neutral Zone, and with SFI fearing a Romulan Invasion, a massive counter Intelligence operation began. This operation, dubbed Sword and Shield, inserted several dozen Starfleet counterintelligence Specialists onboard the suspected Starships. For the better part of a year, these operatives played a deadly game of cloak and dagger against the expectant Tal Shiar operatives. This massive undertaking resulted in the largest capture of external espionage operatives in Starfleet history, 38 Starfleet officers (including 2 Ship Captains) and 12 Enlisted Starfleet personnel were arrested and charged with espionage against the Federation. 6 Starfleet Intelligence operatives lost their lives in this operation. &lt;br /&gt;
&lt;br /&gt;
It was to this threat that Admiral Rodrigo Doenitz would propose a solution. That solution came in the form of a Starship, dedicated completely to the tasks of espionage and interdiction operations. The vessel would be operated entirely independently of Starfleet command. Only Starfleet Intelligence would have any command authority over the vessel and its missions. This proposal created a scandalous outcry by Starfleet Command Officers, with the end result becoming less than favorable to the Doenitz cause.&lt;br /&gt;
&lt;br /&gt;
However, the dramatic success of Sword and Shield eased the tension against Starfleet Intelligence, and by the end of the War with the Cardassian Union in 2398; Starfleet Command realized the inability of SFI to conduct operations in hostile space, or to operate independently without the immediate assistance of Starship under Starfleet Command authority. It was in August of that year that Admiral Talbot, with the support of Admiral Doenitz proposed the idea of creating a new class of Starship capable of supporting Intelligence operations in hostile space, while simultaneously capable of performing signal, traffic and visual surveillance of facilities, ship movements and communications. Admiral Talbot argued that if SFI were equipped with such a vessel during the War, that the effectiveness of the Cardassian attack against the UFP would have been greatly reduced, if not altogether neutralized. Additionally, Talbot argued, such a ship working in Romulan space would have been priceless in determining the intentions and movements of the Tal Shiar during Operation Sword and Shield.&lt;br /&gt;
&lt;br /&gt;
Admiral Talbot’s conceptual Starship was deemed impossible to build, and also in violation of Starfleet Intelligence Command’s charter and the project was immediately disapproved. But that was not the end of the situation. &lt;br /&gt;
&lt;br /&gt;
Admiral Talbot, through secret channels with the complete support of Admiral Rodrigo Doenitz established a secret construction facility. Through various nefarious means, funds were funneled into the project and experienced Starfleet ship engineers were tasked to assist in developing a new class of Starship that could function efficiently within the confines established by the joint visions held by the two admirals.&lt;br /&gt;
&lt;br /&gt;
A special Starfleet Intelligence Operation was begun in a secret shipyard facility around early 2397. SFI operatives assigned to the operation interviewed and recruited Starship designers from across the Federation, purposely avoiding any designer that had ever worked on a Starship Project for the Federation in the past. These designers, assisted by the technical and personal experiences, of selected Starship Engineers laid down the design parameters for the project.&lt;br /&gt;
&lt;br /&gt;
After Admiral Doenitz’s successful coup, the project would prove to outlive many of its critics. With the full power of the office of the president of the Federation, Doenitz fast tracked his project making it an official Presidential Directive. This Directive was codenamed the Chimera Directive.&lt;br /&gt;
&lt;br /&gt;
The Rosenanté Class Starship designed by the Chimera Directive represents the most advanced design and systems innovations in the Federation. The basic design concept was developed around the Sovereign class and is considered the most advanced evolution of Starfleet Ship design to date.&lt;br /&gt;
&lt;br /&gt;
==Design Objectives==&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;&#039;&#039;Pursuant to Starfleet Intelligence Directive 1045.35, the following objectives have been established for the Rosenanté Class Starship development project:&#039;&#039;&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*	Provide a mobile platform for a wide range of ongoing intelligence and counterintelligence projects.&lt;br /&gt;
*	Provide autonomous capability for full execution of Starfleet Intelligence policy and directive options in hostile areas of space.&lt;br /&gt;
*	Incorporate recent advances in technology and protocols.&lt;br /&gt;
&lt;br /&gt;
To provide for these objectives, the Designers recommended that the Rosenanté class starship meets or exceeds the design goals in the following specification Categories;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Propulsion&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Sustainable cruise Velocity of Warp Factor 9.4. Ability to maintain speeds of up to Warp Factor 9.7 for periods of up to 12 Hours.&lt;br /&gt;
*	Sixth-phase dilithium controlled matter/antimatter reactor for primary power. Sustainable field output to exceed 1, 650 cochranes, peak transitional surge reserve to exceed 4,225% of nominal output. (170ns phase)&lt;br /&gt;
*	Warp Driver coils efficiency to meet or exceed 98% at speeds up to Warp 8.0. Minimum efficiency of 68% to be maintained through Warp 9.4. Life cycle of all primary coil elements to meet or exceed 1,200,000 cochrane-hours between neutron purge refurbishment. Secondary coil elements to meet or exceed 2,000,000 cochrane-hours between neutron purge refurbishment.&lt;br /&gt;
*	Warp field geometry to incorporate modified 85° Z-axis compression characteristics on forward warp lobe for increased peak transitional efficiency at high warp. Warp Nacelle centerlines to conform to 2.56: 1.1 ratio of separation to maximize field strength.&lt;br /&gt;
*	Secondary (impulse) propulsion systems to provide sub-light velocities up to and including .92 light speed (c). Engine systems of choice to include but not limited to at least two YPS 8063 fusion drive motors. All units to be equipped with subspace drive accelerators, field output not less than 180 millicochranes at 1.02 X l0³K. Reactor Modules to be field replaceable.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Mission&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Ability to operate independent of Starbase refurbishment for moderate periods of time. Independent operation mode capability of 1 Standard years at nominal Warp 6. Ability to execute deep-space exploration missions including charting and mapping, hostile contact scenarios, intelligence gathering and infiltration missions, full technical, biological and ecological studies.&lt;br /&gt;
*	Ability to support a wide range of mission-related ongoing research and other projects without impact on primary mission operations.&lt;br /&gt;
*	&#039;Full Spectrum EM, optical, subspace flux, Gravimetric, particle, and quark population analysis sensor capability. Multimode neutrino interferometery instrumentation. Wide band life sciences analysis capability. 2 twelve-meter interphasic field focused telescopes.&lt;br /&gt;
*	Upgradeable experiment and sensor array design. Ability to support on-board and probe mounted science and intelligence instrumentation.&lt;br /&gt;
*	Support facilities for auxiliary spacecraft and instrumented probes for short-range operations to include at least 1 independent launch, resupply, and repair bays.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Environment/Crew&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Environmental systems to conform to Starfleet Regulatory Agency (SFRA)- standard 102.9 for Class M compatible oxygen breathing personnel. All life-critical systems to be triply redundant. Life support modules to be replaceable at major Starbase layover to permit vehicle-wide adaptation to Class H, K or L environmental conditions.&lt;br /&gt;
*	Ability to support up to 200 non-crew personnel for mission related operations.&lt;br /&gt;
*	Facilities to support Class M environmental range in all individual living quarters, provisions for 2% of living quarters to be equipped to support Class H, K and L environmental conditions. Additional 1% of living quarters volume to be equipped for Class N and N (2) environmental adaptation.&lt;br /&gt;
*	All habitable volumes to be protected to SFRA-standard 347.3(a) levels for EM and radiation. Subspace flux differential to be maintained within 0.02 millicochranes.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Tactical&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Defensive Shielding to exceed 9.85 X 103 kW primary energy dissipation rate. All tactical Shielding to have full redundancy, with auxiliary system able to provide 75% of primary rating.&lt;br /&gt;
*	Tactical systems to include full array of Type XII phaser bank elements on hull capable of 6.1MW maximum single emitter output. 6 Photon Torpedo launchers required for ship defensive capabilities.&lt;br /&gt;
*	Tactical systems to include anti-detection components capable of defeating sensor and optical scan.&lt;br /&gt;
*	Tactical systems to include variable decreased emissions systems affecting primary and secondary drive systems.&lt;br /&gt;
*	Tactical systems to include components to reproduce or produce false sensor signatures at displaced coordinates in vessel reference.&lt;br /&gt;
*	Tactical systems to include components to produce ambient radiation and gravitational energies consistent with surrounding spatial occurrences.&lt;br /&gt;
*	Tactical systems to include variable EM field dampening systems to reduce or eliminate vessel EM fields and signatures.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Design Life&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Space frame design life of approximately 100 years, assuming approximately 5 major ship- wide system swap outs and upgrades at average intervals of 20 years. Such upgrades help ensure the continuing usefulness of the ship even though significant advances in technology are anticipated during that time. Minor refurbishment and upgrade to occur at approximately one- to five year intervals, depending on specific mission requirements and hardware availability.&lt;br /&gt;
&lt;br /&gt;
==2.0 General Overview==&lt;br /&gt;
&lt;br /&gt;
The Rosenanté class of Starship was originally categorized as an intelligence-gathering vessel. The Rosenanté class is only the second starship class created by Starfleet command to receive this designation. The other is the Spectre Class. While most starships may be adapted for many different mission types, the Rosenanté class starship is designed primarily to perform a single type of mission objective, in effect limiting her overall flexibility within a more generalized Starfleet. Seen from a comfortable distance of two or three kilometres, the starship takes on the resemblance of the more familiar Sovereign class explorers. Upon closer inspection however, one can see that the engineering hull is more sleek, lending a highly manoeuvrable appearance to the Rosenanté class of starship. The engineering hull actually extends both above and below the saucer section, lowering the overall silhouette of the class. Additionally, the saucer section itself boasts a number of changes that are easily noticed even by the most novice of observers. This divorce from standard Starfleet design protocols is both advantageous and disadvantageous for this class of starship. The unique hull design allows an immediate reduction in stresses generated by high warp speeds, while allowing greater manoeuvrability at sub-light speeds. This hull design concept has its drawbacks however, as high speed warp manoeuvrability is reduced in favour of speed. The exterior hull material is stronger, lighter and more durable than that used in standard starship production. This reduces the need for otherwise necessary supports and braces, leaving a greater interior volume for habitation. This material used on the ship&#039;s hull is more difficult to reproduce and repair, as specialized facilities must be implemented to perform these functions.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;2.1 Physical Arrangement&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-2up.jpg|right|300px]]&lt;br /&gt;
&lt;br /&gt;
The hull, remarkably birdlike in its strong, hollow construction, is reinforced against flight stresses by active energy fields that tighten and flex where required to compensate for natural and artificial internal and external forces. Structures integrated into the hull allow for a variety of necessary functions. &lt;br /&gt;
&lt;br /&gt;
The bridge consolidates the command positions for the rest of the starship, windows allow crewmembers needed vistas while in space, phaser arrays and photon torpedoes provide offence and defence against hostile forces, and a specialized communications system allows interaction with other worlds and their ships.&lt;br /&gt;
&lt;br /&gt;
Lifeboats allow for escape in dire emergencies, transporter emitters afford reliable near instant movement of crew and gear, navigational sensors and deflectors give the starship distant vision and a method for clearing obstacles, and powerful warp engines propel the starship at amazing speeds.&lt;br /&gt;
&lt;br /&gt;
The twenty-eight decks are internally divided among major load-bearing structures. A great many systems, especially the habitation sections are suspended within the open spaces, essentially &amp;quot;floating&amp;quot; on flexible ligaments to minimize mechanical, thermal, and conductive radiation shocks.&lt;br /&gt;
&lt;br /&gt;
The living areas of the starship have been designed for maximum comfort and safety while the crew is conducting a mission. Long-term studies of humanoid cultures have revealed that as each race embarked upon permanent occupation of space, large personal living spaces had to be established, especially on early sub-light missions. The Rosenanté class starship allows for some 120 square meters of living space per person, in addition to community space and areas allotted to purely working functions.&lt;br /&gt;
&lt;br /&gt;
==3.0 Spacecraft Structure==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.1 Main Skeletal Structure&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The primary space frame of the Rosenanté class starship is fabricated from an interlocking series of Terminium/Tritium microfilament truss frames. These members average l.05m² in cross section and are capable of bearing the same load as the standard Tritanium/Duranium truss averaging l.27m² in cross section used in standard starship construction. These truss frames are located an average of 20 meters across the ship&#039;s exterior, while the standard trusses would be located every 25 meters along a ships exterior. The tightening of the trusses allows the vessel to withstand greater stress imposed upon it by warp travel, while still producing a lighter space frame.&lt;br /&gt;
&lt;br /&gt;
As with other starship designs, larger numbers of these trusses are located integral to the main impulse engine sections, the warp nacelle pylons, docking interface latches, and along the centerline of the hull structure. Smaller Trusses averaging 0.35m² in cross section are located every five meters on average, and also provide internal supports within the deck and core structure of the spacecraft interior.&lt;br /&gt;
&lt;br /&gt;
A mechanical framework provides physical integrity to the vehicle while at rest. A parallel series of aluminum crystal foam stringers are phase transition bonded to the primary trusses, providing low frequency vibration attenuation across the main truss structure, as well as support for certain utility conduits.&lt;br /&gt;
&lt;br /&gt;
Also attached to these stringers are various conformal devices built into the hulls structure, including elements of the deflector shield grid, H.l.S.S. components, as well as subspace radio antennas, which are incorporated into the skin of the spacecraft.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.2 Secondary Framework&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mounted to the primary space frame is a secondary framework of micro-extruded Terminium trusses to which the inner hull of the structure is directly attached. The secondary framework is mounted by means of 3.2 cm diameter X 5.1 centimeter long semi rigid polydurinide support rods, permitting a limited amount of mechanical isolation from the primary space frame for purposes of strain relief, plus sound and vibration isolation. Secondary space frame segments are also separated from each other (although mechanically attached) to permit replacement of inner hull segments and associated utilities infrastructure during major Starbase layover.&lt;br /&gt;
&lt;br /&gt;
Structural integrity during powered flight is provided by a series of forcefields that reinforce the physical framework. This structural integrity field (SIP) is distributed through a network of molybdenum-jacketed wave-guides, which in turn distribute SIF energy into ceramic-polymer conductive elements throughout the space frame. Without the structural integrity field, the vehicle would be unable to withstand accelerations greater than 3l.4 m/s² without significant deformation, or greater than 49.18 m/s² without unrecoverable structural damage.&lt;br /&gt;
&lt;br /&gt;
Exterior hull substrate is joined to the primary load bearing trusses by means of 4.8-cm diameter electron-bonded duranium pins at 1.01-meter intervals. These pins are slip-fitted into an insulating AGP ceramic fiber jacket that provides thermal insulation between the space frame and the exterior hull. The pins, jacketing, and hull segments are gamma welded together.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.3 Hull Layers&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The exterior of the spacecraft consists of multiple layers, which afford structural and atmospheric integrity for the space frame, integral wave-guides and field conductive members for the structural Integrity Field (SIP) and H.I.S.S components, and pathways for other utilities (including deflector grids), as well as resistance to radiation and thermal energy.&lt;br /&gt;
The exterior shell substrate is composed of interlaced micro-foam duranium filaments. These filaments are gamma welded into a series of contiguous composite segments that are 4.7 cm thick and are typically 2 meters in width. The substrate segments are electron-bonded to three reinforcing layers of 1.2- cm biaxially stressed terranium fabric, which provide additional torsion strength.&lt;br /&gt;
&lt;br /&gt;
In areas immediately adjacent to major structural members, four layers of 2.3-cm fabric are used. The substrate layer is attached to major structural members by electron-bonded duranium fasteners at 2.5-cm intervals. The substrate segments are not intended to be replaceable, except by phase-transition bonding using a transporter assembly jig during major Starbase layovers.&lt;br /&gt;
Two 3.76-cm layers of low-density expanded ceramic-polyrner composites provide thermal insulation and secondary SIP and H.I.S.S. conductivity. These layers are separated by an 8.7-cm multiaxis triennium truss framework, which provides additional thermal insulation and a pass through for fixed utility conduits.&lt;br /&gt;
&lt;br /&gt;
A 4.2-cm layer of monocrystal beryllium silicate infused with somniferous polycarbonate whiskers provides radiation attenuation. This layer is networked with a series of 2.3-cm X 0.85-cm molybdenum-jacketed conduits. These conduits, which occur at 1.3-m intervals, serve as triphase wave-guides for the secondary structural integrity field. Conductive tritium rods penetrate the wave-guides at l0-cm intervals and transfer SIF energy into the ceramic-polymer conductive layer.&lt;br /&gt;
The outermost hull layer is composed of a 1.6-cm sheet of AGP ablative ceramic fabric chemically bonded onto a substrate of 0.15-cm triermium foil. This material is formed into segments approximately 3.7m² and is attached to the radiation attenuation layer by a series of duranium fasteners, which allows individual segments to be replaced as necessary. (Micrometeor erosion is kept to a minimum by the deflector system, but is sufficient to warrant replacement of 30% of the leading edge on the average of every 7.2 standard years.) Individual outer hull segments are machined to a tolerance of ±0.05-mm to allow for minimum drag through the interstellar medium. Joints between segments are manufactured to a tolerance of ±0.025-mm.&lt;br /&gt;
&lt;br /&gt;
Also incorporated into the outermost hull layer is a series of super conducting molybdenum-jacketed wave-guide conduits, which serve to absorb and disperse sensor emission energy that interacts with the hull. Segmented sections of this network serve as housings for the unique DECS components, responsible for producing the ship’s tactical deflector. Unlike a standard starship, there are no thermal regulating assemblies built into the skin of the starship. Instead this duty is regulated through a series of intercoolers and radiators housed inside the interior of the Bussard Collector Assembly.&lt;br /&gt;
&lt;br /&gt;
==4.0 Command Systems==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.1 The Bridge&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Bridge, located on Deck 1, provides primary operational control of the Rosenanté class starship. The bridge directly supervises all primary mission operations and coordinates all departmental activities. These activities are handled through the individual command consoles located in various positions on the bridge. These workstations are modular and can be interchanged, removed, or added as necessary to fulfill specialized mission requirements. At any one time there can be up to 12 workstations installed. The standard bridge design calls for 2 Science Stations, 1 Operations Station, 1 Flight Control Station, l Auxiliary Engineering Station, 1 Tactical station, 1 Communications/ H.I.S.S. station, 1 Internal Security Station, and 2 Command Stations, one each for the ship’s commander, and the First Officer.&lt;br /&gt;
Other facilities located on Deck 1 include Astrogation, the captain&#039;s ready room and head, the crew head, and a small mission briefing room.&lt;br /&gt;
Major connections to the bridge include a pair of Turbolift shafts, four electron-plasma power distribution wave-guide conduits; four environmental support plenum groups, nine primary and two back-up optical data network trunks, two replicator wave-guide conduits, and three service crawlways. As an interesting side note, a tertiary backup power distribution system consisting of hardwired nonreactive, conductive ceramic-polymer relays are also in place.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.2 Display Panels&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The display panels on the bridge and through out the ship are constructed and operated the same as those on any other Federation starship. The layouts and reactivity of the panels are augmented and display properties shown in a different manner. The coloration of the interaction displays is altered to create a different aesthetic affect, while also allowing a variant-programming matrix to be utilized. This new language utilizes advances in Holoprogramming to create three-dimensional matrix strings; this in turn allows a more efficient and quicker computer response time. Critical internal components of the display panels are mapped to the molecular level allowing a replication driven pro-holographic matrix damage control system to repair damaged components. The components necessary to facilitate this activity are collectively known as the &#039;&#039;&#039;Se&#039;&#039;&#039;lf-&#039;&#039;&#039;Re&#039;&#039;&#039;plicating &#039;&#039;&#039;Da&#039;&#039;&#039;mage &#039;&#039;&#039;C&#039;&#039;&#039;ontrol &#039;&#039;&#039;S&#039;&#039;&#039;ystem (&#039;&#039;&#039;SERDACS&#039;&#039;&#039;). The &#039;&#039;&#039;SERDACS&#039;&#039;&#039; components are present in all non-integrity dependant systems throughout the ship. &lt;br /&gt;
&lt;br /&gt;
In addition to the standard anchored display consoles located throughout the ship, a series of Holoemitters have been seeded throughout the vessel to allow ship&#039;s personnel to utilize a holographic interface to tie directly into the ships computer regardless of the location of the crewmember. These emitters also allow the EMH to be activated in any compartment in the ship, and also allow for the construction of holographic crewmembers to fill non-critical positions on the ship. These holoemitters are capable of creating non-electronic tools for emergency use, and in conjunction with replication systems could produce vital simplified component reproduction anywhere aboard ship.&lt;br /&gt;
&lt;br /&gt;
==4.3 Bridge Stations==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.1 Flight Control (CONN)&#039;&#039;&#039; &amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the actual piloting and navigation of the ship. From this station all SIF and IDF systems are monitored, as well as navigational deflectors, and their subsequent systems. This console performs the same functions as it would on board any other Federation starship.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.2 Operations Management (OPS)&#039;&#039;&#039; &amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for power maintenance and resource allocation. This console dictates priority status of all shipboard systems and operations. They coordinate activities between departments and between the ship and away missions. This console performs the same functions as it would on board any other Federation starship.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.3 Tactical Operations (TACOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the operation, monitoring and maintenance of the ship&#039;s tactical systems. These systems include the phaser arrays, the photon torpedo deployment systems, probe	deployment systems, H.I.S.S. system, Signal displacement system, tractor beams, and Tactical deflector systems. The Tactical station aboard the Rosenanté class starship differs from those of standard Federation starships. The main difference is the divorce of the ship&#039;s tactical systems from the internal security systems of the ship. This allows the tactical officer the ability to concentrate on the tactical aspects of the ship without the need to also monitor the internal security status of the ship. Another major difference in the Rosenanté class starship is the addition of a sensor array specifically for use by the tactical officer.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.4 Security Operations (SECOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the monitoring and operation of internal ship security systems. The Operator of this console is responsible for the deployment of ship&#039;s security personnel aboard the ship. This console controls the internal security containment fields, internal ship&#039;s sensors. The SECOPS officer can monitor the security status, security systems and personnel deployment for the entire ship. They can control door mechanisms, containment fields, the turbolift car, and weapons settings of all Federation weaponry on the ship. In addition, security can control personnel access to restricted areas, and utilize sight-to-sight onboard transporters.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.5 Communications (COMMOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the encryption and decryption of intercepted communications, for the transmission of communications, maintaining the Emissions Control Protocols, and the operation of specialized communications interception equipment. The Communications officer is often called upon to triangulate communications sources, decipher enemy transmissions, and encrypt outgoing communications. They often assist in Traffic Analysis of enemy troop deployment, and maintain secure communications with away teams.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.6 Science Stations I &amp;amp; II&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
These consoles are responsible for data collections, primary and lateral sensor operations, and database referencing. It is the responsibility of the science officer to operate the ship&#039;s sensors, teleoptical systems, and imaging systems. They observe, record and document data important to shipboard mission objectives. These stations can be utilized together or separately. This station also acts as the primary database access terminal for the Federation database carried aboard all Federation starships. Both passive and active sensors are controlled from this station.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.7 Auxiliary Engineering Station&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This station is responsible for maintaining and monitoring shipboard systems. This console works in conjunction with main engineering, and is capable of performing the same functions as the computer in that section of the ship. From this station the warp fields can be tuned, altered or monitored, as can all primary and secondary shipboard systems. This station is not always manned.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.8 Command Stations I &amp;amp; II&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
These consoles are responsible for the maintenance and monitoring of the ship&#039;s computer and all primary and secondary systems. Only the commanding and executive officer have access to these consoles. From these consoles the commanding officers can display data concerning ship&#039;s systems, status, condition, position, speed, heading, and power management distribution. These consoles can access the database, and has priority authority over all computer functions. These consoles are the only terminals capable of activating the ship&#039;s self-destruct mechanism. Any officer in command of the starship may utilize these consoles, although some functions may be unavailable.&lt;br /&gt;
&lt;br /&gt;
==5.0 The Computer System==&lt;br /&gt;
The computer system aboard the Rosenanté class starship is identical in construction to the computers used on other Federation Starships. They utilize the same back up and failsafe hardware and communicate through the same methods as the standard starship computer. The computer system of the Rosenanté class starship is composed of 2 synchronized computer cores, identical to those used in the Galaxy Class starship. The only differences between the standard Federation computers and those aboard the Rosenanté are the storage medium and programming language that the system uses to communicate.&lt;br /&gt;
The storage of data and processing networks of a standard Federation computer system depend upon isolinear chips. On the Rosenanté a new type of data storage chip, the Hololinear chip is introduced. Taking advantage of new replication and holographic programming breakthroughs, the new Hololinear chips, or HL chips, allow data to be stored in a four-dimensional, subspace format. A new programming language known a &#039;&#039;&#039;B&#039;&#039;&#039;ilinear &#039;&#039;&#039;U&#039;&#039;&#039;nilateral &#039;&#039;&#039;N&#039;&#039;&#039;etworking &#039;&#039;&#039;C&#039;&#039;&#039;ode (&#039;&#039;&#039;BUNC&#039;&#039;&#039;) allows data to be stored in a temprometric tagged holographic string, thereby allowing data to be stacked almost exponentially upon other data, linked by temprometric strings of associated data. Retrieval time is decreased as the data can be read from any point along its data string, rather than starting at a specified point as is required by the standard isolinear chip design.&lt;br /&gt;
&lt;br /&gt;
==6.0 Warp Propulsion Systems==&lt;br /&gt;
The Warp propulsion system in the Rosenanté class starship is radically different from Those used in other starships. The majority of the system is developed to utilize existing warp technology and materials. There is however a few major changes in the system. All warp engineers are familiar with the laws of warp transition, which dictates that warp geometry and power requirements dictate a vessel&#039;s ability to achieve various levels of warp speed. This same law also dictates that a warp field must be balanced in order to achieve maximum efficiency to make a warp transition.&lt;br /&gt;
&lt;br /&gt;
The Graph below represents the transition energy requirements for the Galaxy Class Starship design and also for that of the Rosenanté class starship.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:RWC.jpg|thumb|center|800px|Warp transition chart]]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
ln the chart above the Cochrane values are represented over the white bar for the Rosenanté Class starship. At lower warps (below Warp 6) there is an actual decrease in warp efficiency, although at higher warp there is a worthwhile increase in efficiency, where the differences in efficiency matter most. It is important to note that a Galaxy class starship is incapable of traveling at Warp 9.97, and thus the numbers represented for that class is theoretical.&lt;br /&gt;
&lt;br /&gt;
The ability to sustain warp 9.97 is a result of multiple warp engines working in synchronization and a natural by-product of the embedded nacelle design. The synchronization of the dual warp drive is accomplished through the use of a &#039;&#039;&#039;W&#039;&#039;&#039;arp &#039;&#039;&#039;E&#039;&#039;&#039;nergy &#039;&#039;&#039;Sy&#039;&#039;&#039;nchronization &#039;&#039;&#039;R&#039;&#039;&#039;outer, or &#039;&#039;&#039;WESYR&#039;&#039;&#039;. The &#039;&#039;&#039;WESYR&#039;&#039;&#039; unit is highly classified, but its basic function is to synchronize otherwise out of synch Waveforms created within two near identical meshed Tuned Plasma Streams. Because of the additional energy that this system produces, a higher capacity EPS Power Tap and Series Relays were developed to handle the additional power loads. A dual bypass system allows any single Warp drive to power ships functions, at a significant reduction in overall power. Also a major redesign feature of the upgraded power system resulted in the addition of a second Port and Starboard Power conduit assembly and relay subassembly. This allows the power delivery system to function more efficiently.&lt;br /&gt;
&lt;br /&gt;
Interestingly enough, a bizarre natural byproduct of running a dual synchronized Warp Field is the creation of a &amp;quot;double&amp;quot; warp bubble. These warp bubbles are divided by 2.3-mnm (micronanometers) and help produce the effect of the change of reduction caused when making Warp Transitions. As subspace resistance passes through the Outer shield it is reduced as normal, then again as the remaining resistance passes through the inner bubble, it is further reduced. This causes the starship to experience less resistance and shearing warp stress associated with high rate warp travel and maneuvering.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Spiral Warp Drive&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In addition to the standard warp drive used by all federation starships, the Rosenanté class is also equipped with an experimental Spiral Warp Drive. This drive creates a subspace &amp;quot;tunnel&amp;quot; or &amp;quot;wormhole&amp;quot;  through which the Rosenanté may then travel. The tunnel integrity is maintained by the main deflector dish. The tunnel basically allows the ship to drop into subspace, effectively disappearing from normal space for a short period of time. The speeds that are achieved through the use of this drive are akin to those used by the Borg when using transwarp conduits. Unlike transwarp conduits, however,the tunnel being opened by the Rosenanté would dissipate as soon as the ship moves through it. In a similar manner, the spiral drive can only be used to travel in straight lines. This means that the vessel may make a periodic series of short hops to correct course when using this system.&lt;br /&gt;
&lt;br /&gt;
==7.0 Deflector Emitter Cluster System (DECS) ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-3up.jpg|thumb|left|500px|]]&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;D&#039;&#039;&#039;eflector &#039;&#039;&#039;E&#039;&#039;&#039;mitter &#039;&#039;&#039;C&#039;&#039;&#039;luster &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;DECS&#039;&#039;&#039;, represents the newest Federation breakthroughs in Federation tactical shield technology. This innovative new system utilizes a convex “honeycombed&amp;quot; arrangement of octagonal emitters offset slightly to produce a unified, overlapping tactical field. This primary tactical system allows a tighter tactical shield to be produced, thus resulting in a lessened tactical shield cross section, which in turn reduces starship detectability.&lt;br /&gt;
&lt;br /&gt;
Whereas the Rosenanté class of starship possesses the standard &#039;&#039;&#039;D&#039;&#039;&#039;eflector &#039;&#039;&#039;E&#039;&#039;&#039;mitter &#039;&#039;&#039;A&#039;&#039;&#039;rray (&#039;&#039;&#039;DEA&#039;&#039;&#039;) that all Federation starships do, they use that particular system as a primary shielding system. The &#039;&#039;&#039;DECS&#039;&#039;&#039; assembly operates by producing several smaller polyhedral segments of shield interdependability, rather than creating a &amp;quot;shell&amp;quot; segment standard to all other Federation starships. The &#039;&#039;&#039;DECS&#039;&#039;&#039; requires more power than standard tactical &#039;&#039;&#039;DEA&#039;&#039;&#039; systems, but yields a 20% increase in shield output. The &#039;&#039;&#039;DECS&#039;&#039;&#039; is calibrated to respond and recalibrate the loss of a single emitter or emitter cluster, resulting in a greater overall performance and defensive capability of ship systems. The standard &#039;&#039;&#039;DECS&#039;&#039;&#039; system is installed to provide tactical shielding whenever the starship is experiencing &#039;&#039;&#039;DEA&#039;&#039;&#039; failure, or power requirements do not allow the use of the &#039;&#039;&#039;DEA&#039;&#039;&#039;. Another advantage of the DECS over the standard DEA is its modular design. It is quick and efficient to repair or replace in the field whereas the replacement of the DEA system requires a major overhaul at a Starbase.&lt;br /&gt;
&lt;br /&gt;
==8.0 Hull Integrated Stealth System. ==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;H&#039;&#039;&#039;ull &#039;&#039;&#039;I&#039;&#039;&#039;ntegrated &#039;&#039;&#039;S&#039;&#039;&#039;tealth &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;HISS&#039;&#039;&#039;, is a series of alterations to the ships exterior hull and systems to create a reduced sensor and visual silhouette. The details of the &#039;&#039;&#039;HISS&#039;&#039;&#039; are highly classified, although the general concepts behind its incorporation are not. A network of specialized integrated hull webbing allows the hull to emit energies that effectively allow light waves to pass through it and its contents. In addition to visual bands of radiation, the specially designed ablative hull absorbs sensor energy, while emitting the same energy signature as the starship&#039;s surrounding space. Thus, the vessel becomes virtually undetectable either through detection or complete omission of detection. In addition to this, specialized hull features act as complex Magnetic field disruptors, reducing the EM field of the vessel, and also neutralize radioactive emissions through a complex series of intercoolers and sheathed cowlings. The ship&#039;s Impulse, Thruster and Bussard collection systems are incorporated to nearly negate all detectable signs of their use. When the HISS is active and used in conjunction with strict Emissions protocols, the ship vanishes from visual and sensor detection.&lt;br /&gt;
&lt;br /&gt;
==9.0 Advanced Sensors Systems==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;I&#039;&#039;&#039;mproved &#039;&#039;&#039;S&#039;&#039;&#039;ensor &#039;&#039;&#039;I&#039;&#039;&#039;ntegrated &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;ISIS&#039;&#039;&#039;, is a modified high yield Federation sensor array. The &#039;&#039;&#039;ISIS&#039;&#039;&#039; utilizes the newest development in sensor technology to quantum phase the active and passive ship&#039;s sensors to greatly reduce detectability. These new sensors are more powerful, and almost impossible to detect without performing extensive and time consuming alterations to a starship&#039;s sensor array, which then is useless to detecting other aspects of its surrounding. Some of this technology is loosely based on cloaking principles.&lt;br /&gt;
&lt;br /&gt;
==10.0 Sensor Displacement System==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Se&#039;&#039;&#039;nsor &#039;&#039;&#039;Di&#039;&#039;&#039;splacement &#039;&#039;&#039;S&#039;&#039;&#039;ystem, Or &#039;&#039;&#039;SEDIS&#039;&#039;&#039;, allows the Rosenanté class of starship to offset its actual energy signature, and even produce an additional energy signature. This is designed to improve the starships ability to prevent &amp;quot;true&amp;quot; detection, or to act as a decoy system in the event that the starship is detected. This system is capable of operating within a 6000Km range of the vessel.&lt;br /&gt;
&lt;br /&gt;
==11.0 Displaced Communications System==&lt;br /&gt;
The &#039;&#039;&#039;Di&#039;&#039;&#039;splaced &#039;&#039;&#039;Comm&#039;&#039;&#039;unications &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;DICOMMS&#039;&#039;&#039;, is based on the same technology as the &#039;&#039;&#039;ISIS&#039;&#039;&#039;. This energy is used to send nearly undetectable communications. The Rosenanté class starship is equipped with standard Federation communications systems as well.&lt;br /&gt;
&lt;br /&gt;
==12.0 Interior Systems Modifications==&lt;br /&gt;
There have been a variety of interior alterations to the interior, habitable areas of the Rosenanté class starship. The most apparent alterations are in the functionality of the corridor and turbolift systems. The oversized personnel quarters offer the most luxurious and spacious accommodations aboard any Starfleet posting, while unique interaction software insures crewmembers peace of mind.&lt;br /&gt;
&lt;br /&gt;
Many Starfleet admirals believe that the Tactical and Scientific Equipment carried by a Starship to be the most important asset to any Starfleet facility or starship. The designers of the Rosenanté class of Starship also felt that crew morale would also serve a very integral role in the operation of the starship. To these ends the interactive systems and habitations were designed to provide a reassuring and relaxing environment for the ships crew.&lt;br /&gt;
&lt;br /&gt;
==12.1 Safety Systems==&lt;br /&gt;
The most paramount function of any Starship is the maintenance of its crew in adverse conditions. Integral to this school of thought is the ability to protect the crew under hostile threats. To these ends, the designers of the Rosenanté class starship developed a series of counterinsurgency systems to minimize crew contact with alien forces boarding the vessel.&lt;br /&gt;
&lt;br /&gt;
==12.1.1 Isolation Field Systems==&lt;br /&gt;
The &#039;&#039;&#039;I&#039;&#039;&#039;solation &#039;&#039;&#039;F&#039;&#039;&#039;ield &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;IFS&#039;&#039;&#039;, was designed with the intent to isolate hostile alien forces that boarded the vessel for the crew. This function is considered vitally important when consideration is given to the fact that the Rosenanté class starship possesses a very highly trained crew. The &#039;&#039;&#039;IFS&#039;&#039;&#039; fundamentally isolates the threat through the use of perpetual containment fields, reinforced by miniature shield defenses for the IFS emitter assembly. The &#039;&#039;&#039;IFS&#039;&#039;&#039; is always active, limiting the mobility of non-authorized personnel, securing sensitive sectors of the ship, and effectively hindering the process of any hostile aliens that may manage to board the vessel. The ship&#039;s computer monitors the movements of every official member of the ship&#039;s crew at all times. In this manner, the computer is able to activate or deactivate the &#039;&#039;&#039;IFS&#039;&#039;&#039; screens on an individual basis as needed. This allows authorized crewmembers access to shipboard systems and compartments as needed. The &#039;&#039;&#039;IFS&#039;&#039;&#039; consists of a series of Level 8 containment fields spaced an even 12.5-meters along the corridors of the vessel. In addition to these, an &#039;&#039;&#039;IFS&#039;&#039;&#039; field also isolates each access portal and hatch. In the event that a commbadge should be captured, or fail, that badge is automatically removed from all access rosters, until security can investigate the occurrence.&lt;br /&gt;
&lt;br /&gt;
As a benefit of the perpetually active IFIS fields, studies indicate that shipboard damage caused by fire and/or decompression was drastically reduced. The fields prevented large area decompression, and also limited the range of fire dispersion radically.&lt;br /&gt;
&lt;br /&gt;
Although in larger compartments the &#039;&#039;&#039;IFS&#039;&#039;&#039; system is not perpetual; all compartments are equipped with the capacity to further &amp;quot;compartmentalize&amp;quot; these large open areas. The computer is capable of assessing threats to the crew and equipment of the vessel, and can respond using the &#039;&#039;&#039;IFS&#039;&#039;&#039; system, nearly instantly. The &#039;&#039;&#039;IFS&#039;&#039;&#039; system was designed to operate independently of the ships main power supply when necessary. Each &#039;&#039;&#039;IFS&#039;&#039;&#039; emitter and processor assembly is equipped with an independent high-yield Sodium Kelleride power system. This power cell is further treated with a Potassium Unified catalyst. This allows the production of oxygen as a by-product whenever the secondary power system is operated. This allows a crewmember to be compartmentalized in an otherwise decompressed area to survive asphyxiation and loss of pressure. This secondary power system will allow the full yield operation of the &#039;&#039;&#039;IFS&#039;&#039;&#039; emitter in question for a period of 4 standard hours. Setting the emitter to a lower containment setting can extend this time.&lt;br /&gt;
&lt;br /&gt;
==12.1.2 Fire Suppression Systems==&lt;br /&gt;
&lt;br /&gt;
Although the &#039;&#039;&#039;IFS&#039;&#039;&#039; system hinders the progress of a shipboard fire, it will not necessarily extinguish it. To facilitate this a hybrid field emitter, environmental suppression system was developed. This system isolates the flame from its fuel source using advanced forcefield emissions systems, while simultaneously adjusting the environment around the fire to assist in its suppression. A functional &#039;&#039;&#039;IFS&#039;&#039;&#039; contained area further supports the adjustments, as a smaller area of the ship need be adjusted at any one time. There are certain types of plasma fires that could be unaffected by environmental conditions and or can not be contained in this manner. It is in those situations that the fire suppression systems remove the fire and all affected material through use of the ships sight-to-sight transporters. If this cannot be performed due to a greater risk being imposed on the crew, more conventional methods of fire suppression must be performed.&lt;br /&gt;
&lt;br /&gt;
==12.1.3 Internal Ballistics Dampening Fields==&lt;br /&gt;
In key areas where materials stored aboard ship have the potential to be propelled through sections of the ship, a series of &#039;&#039;&#039;I&#039;&#039;&#039;nternal &#039;&#039;&#039;Ba&#039;&#039;&#039;llistics &#039;&#039;&#039;D&#039;&#039;&#039;ampening Fields, or &#039;&#039;&#039;I-BAD&#039;&#039;&#039; Fields, have been implemented. These fields are found primarily in the armory, cargo bays, Shuttle Bays, storage bays, and personnel quarters. The &#039;&#039;&#039;I-BAD&#039;&#039;&#039; system uses advanced internal sensing equipment specialized to calculate mass and velocity of non-anchored materials. In the event that these materials should be propelled at a speed that the computer should indicate hazardous to crew, then a series of inertial Dampening Fields are erected to reduce the velocity of the offending object. The IDF relays cannot stop a propelled item, although it can shorten its travel distance and relative speed considerably. The sensing systems ignore the movements of personnel. The &#039;&#039;&#039;I-BAD&#039;&#039;&#039; emitters in no way affect the reduction of stresses upon the vessel caused by acceleration, deceleration, or maneuvering.&lt;br /&gt;
&lt;br /&gt;
==12.1.4 Advanced Ergonomics==&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-4up.jpg|thumb|right|500px|]]&lt;br /&gt;
&lt;br /&gt;
Throughout the vessel, specialized memory seating systems have been implemented. These systems monitor the stresses upon the body of the crewmember presently utilizing them and adjust the contact points with the crewmember to minimize physical stresses. All station seating and this material affects standard seating in personnel quarters. The design is such that is can self adjust to allow for non-humanoid crewmembers. The standard bedding and medical bio beds are also adjusted in this manner. This has proven to reduce fatigue and discomfort resulting from prolonged duty shifts. The conceptualization of advanced ergonomic design is further implemented in the layouts and design of the personnel quarters on the ship. Each individual’s quarters are ergonomically designed to his or her unique specifications. The height and shape of interactive systems, the design of the shelving and storage facilities, and the layout of the waste management system are all adjusted to the unique requirements of the compartment owner. Even habitation shape and colour are carefully implemented to create an environment in harmony with its occupant.&lt;br /&gt;
&lt;br /&gt;
==12.1.5 Tactical Sight-to-Sight Transport==&lt;br /&gt;
The ship&#039;s computer possesses the ability to assess tactical breaches in to the vessel&#039;s security. When appropriate, the computer may implement tactical redistribution of security personnel to facilitate the disarmament of tactical threats. The computer determines the size of any aggressive and/or threatening force on the ship, and then determines logical methods of containing and overcoming this threat. The computer is capable of briefing shipboard security personnel on the state of a threat, operating IFIS units, and evacuating non-essential personnel from potential or actual combat areas. The computer can deploy security personnel using sight-to-sight transporters and tactical deployment subroutines. In addition to automatic response to internal tactical threats, the ship&#039;s computer can suggest tactical deployment options for security personnel, utilizing data stored in its memory. This tactical deployment data is only suggested when asked for, and is prepared for planetoid deployment, boarding actions, counter-boarding actions, and sight security. When a medical situation presents itself the same sight-to-sight transporter system can be utilized to transport critical patients to the sickbay.&lt;br /&gt;
&lt;br /&gt;
==12.1.6 Emergency Medical Hologram==&lt;br /&gt;
The Emergency Medical Hologram, as standard to all Federation starships, is also present on the Rosenanté class starship. A series of modifications allows the EMH system to be activated in any habitable portion of the vessel. This function is performed by a series of specialized emitters seeded throughout the ship. Each emitter is equipped with an array of medical scanners and programmed with trauma and first aid protocols. Each emitter assembly is capable of independent operation in the event that power systems become unavailable. The Sodium Kelleride power source can maintain EMH use for 1 hour before expending its charge. When operating normally, the EMH can access the ship&#039;s medical database. When operating independently, only the trauma and first aid subroutines may be accessed. While operating on ship&#039;s systems no more than three EMH programs may be running at any one time. Independent operation is possible among any number of EMH emitters.&lt;br /&gt;
&lt;br /&gt;
==12.1.7 Emergency Replication System==&lt;br /&gt;
The &#039;&#039;&#039;E&#039;&#039;&#039;mergency &#039;&#039;&#039;R&#039;&#039;&#039;eplication &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;ERS&#039;&#039;&#039;, is a series of secondary replicators that operate completely independent of the ships systems. The &#039;&#039;&#039;ERS&#039;&#039;&#039; units are located aft and fore of the starship, two per deck. They are always inert until activated. The &#039;&#039;&#039;ERS&#039;&#039;&#039; system is &amp;quot;hidden&amp;quot; behind corridor paneling, and consists of a single equipment replicator, a single food replicator, an atmospheric condenser, a single medical tricorder, a standard tricorder, and a pair of Class I Phasers. A high-yield Sodium Kelleride Battery that allows light use of the replicators, for a period of 3 days, powers the &#039;&#039;&#039;ERS&#039;&#039;&#039; units. The Tricorders and Phasers are pre-powered, and can be recharged once, using the supplied connections. Accessing the ERS panel will alert security. The Class I phasers require a personal authorization code to be activated. The computer monitors the &#039;&#039;&#039;ERS&#039;&#039;&#039; system very closely, immediately notifying engineering if a problem is detected.&lt;br /&gt;
Although the &#039;&#039;&#039;ERS&#039;&#039;&#039; is a fully functional Replication system, it is programmed to create materials that require very little energy to reproduce. Thus, the food replicators produce only a single nutrient rich disk for consumption. The Tool replicator is limited to equipment that possesses simple physical structures, such as hand tools and only simple electronics materials. Neither replicator system can reproduce power sources, or advanced electronics.&lt;br /&gt;
&lt;br /&gt;
==12.1.8 Emergency Transporters==&lt;br /&gt;
The Rosenanté class starship is equipped with 2 emergency transporters. These transporters are located centrally along the berth and length of the vessel on decks 5 and 15. The emergency transporters are integrated into the primary corridor on the aforementioned decks. All transporter hardware is stowed in the surrounding corridor structures. 20 high-yield Sodium Kelleride Batteries independently power the control operation panel and the emergency transport systems. Each Emergency transporter is also equipped with its own short-range sensor array, for destination determination. The control panel is &amp;quot;hidden&amp;quot; behind the corridor paneling, and floor paneling hides the transporter pad. In order to operate the transporter this floor paneling must be removed. The emergency transporters are each capable of transporting 60 personnel.&lt;br /&gt;
After that there is no power remaining to continue transporter functions. Preparing the Emergency transporters for use alerts security.&lt;br /&gt;
&lt;br /&gt;
==12.2 Medical Bay==&lt;br /&gt;
Due to the number of personnel stationed aboard the Rosenanté class starship, the standard&lt;br /&gt;
Medical Bay arrangement was not utilized. Instead a specialized medical bay was designed to maximize space, while still attending to the variable needs of the ship&#039;s crew. To this end, the sickbay possesses a complete quarantine ward, a single surgical ward, and the central sickbay. A office allows for the CMO to perform administrative tasks without interruption.&lt;br /&gt;
In the surgical area, all the equipment necessary to perform any level of surgery is present. Specialized negative pressure systems allow operations to continue upon contaminated personnel without worry of integrity loss.&lt;br /&gt;
The central medical area is equipped with the newest and most efficient systems that general practice has to offer. A multitude of sensors and medical dedicated processors facilitate medical data gathering, while advanced holographic modeling systems allow hands-off data model construction. Forty Biobeds are located in the Sickbay, which studies indicate was the most efficient number of patients to treat at one time. &lt;br /&gt;
&lt;br /&gt;
In addition to the standard biobeds and Infirmary treatment bay, There are also two dedicated Medical Laboratories, One General Practice Clinical Ward and Three configurable Bays, which can be changed to meet the specific requirements of the medical needs of the vessel.&lt;br /&gt;
&lt;br /&gt;
The Quarantine area is equipped with a series of Biocide units capable of detecting, isolating and destroying over three hundred billion contagions. Negative pressure atmospheric systems, ionic decontamination systems, and bio-phased containment fields guarantee the isolation of harmful contagions. All containment systems in the sickbay are maintained by secondary and tertiary power systems. A medical dedicated replication system allows the creation of any replicable pharmaceutical known to Starfleet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&amp;lt;small&amp;gt;All images compliments of Roger Wackowski&amp;lt;br&amp;gt;Spiral Drive concepts by Anthony Keen&amp;lt;br&amp;gt;All other technical aspects, created, written and designed by Daniel Greene&amp;lt;/small&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
[[Category: Engineering]][[Category: Database]][[Category: Active Ships]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=USS_Rosenante&amp;diff=55397</id>
		<title>USS Rosenante</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=USS_Rosenante&amp;diff=55397"/>
		<updated>2012-05-09T21:25:01Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* Fleet Update */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Rosenante crew line up.jpg|thumb|1255px|center|&amp;lt;center&amp;gt;&amp;lt;small&amp;gt;&amp;lt;font color=goldenrod&amp;gt; 2414 Rosenante Crew Silhouettes by Frank Truelove&amp;lt;br&amp;gt;From Left to Right:  Salid, Soma, Sanok, Caskie, Fisher, Davis, Fraiser, O&#039;Ren, Fuller, Nunez, Signos, Matrix, O&#039;Neill, Viskhard, Lanista, Maddox, McLaren, Sullivan, Jackson, Raschen, Talix, Dralar, Xim, Rosenbauer, Nayeli&amp;lt;/font&amp;gt;&amp;lt;/small&amp;gt;&amp;lt;/center&amp;gt;]]&lt;br /&gt;
{{USS Rosenante Data Box}}&lt;br /&gt;
&lt;br /&gt;
The [[USS Rosenante]] is a [[starship]] currently serving in the [[Starfleet]] of the [[United Federation of Planets]]. The ship was launched in 2408, and at the time was the only ship of the [[Rosenante Class]]. She is currently assigned to the [[52nd Fleet]]. Her Original design was as a privateer, and she was initally to be deployed by [[Admiral Doenitz]] to be used against those that opposed him. However the vessel could not be deployed before the end of the [[Federation Civil War]]. As a result the Rosenante was captured at [[Utopia Planitia]] immediately after the Battle of [[Sector 001]]. She has since been refitted and reclassified as a long-range Explorer. Her original designs specifications were part of the controversial [[The Chimera Directive|Chimera Directive]].  The vessel&#039;s core design encompasses 28 decks. [[USS Rosenante Deck Plans]] are available to those with appropriate security clearance.&lt;br /&gt;
&lt;br /&gt;
The crew of the USS Rosenante is considered to be one of the most diversely crewed ships in the fleet. The Officers who serve aboard her come from a wide variety of backgrounds and worlds, each bringing their own unique perspectives and experiences to the overall performance of the ship. There are personnel both old and new aboard ship who all strive together to overcome the challenges and risks that the universe throws at them. They are explorers, lovers and warriors all dedicated to the betterment of the [[United Federation of Planets]] and it&#039;s principles.  &lt;br /&gt;
&lt;br /&gt;
The Rosenante is currently undertaking a 5-year survey mission in [[Sector 6309]], which is considered strategically crucial for the potential expansion of the [[United Federation of Planets]]. This mission is reminiscent of the 5-year survey missions conducted by the [[Constitution Class]] starships of the 2200&#039;s.&lt;br /&gt;
&lt;br /&gt;
==Fleet Update==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
{| class=&amp;quot;toc color&amp;quot; style=&amp;quot;border:3px solid goldenrod;&amp;quot;align=&amp;quot;center&amp;quot;;&amp;quot;width=246px&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:black&amp;quot; align=&amp;quot;left&amp;quot; |&amp;lt;font color=goldenrod&amp;gt; &amp;lt;small&amp;gt;{{quote|My lord, I will tell you what the case was. I was coming up within a league of the Dutchman, and some of my men were making a mutiny about taking her, and my gunner told the people he could put the captain in a way to take the ship, and be safe.|Captain William Kidd}}&amp;lt;/small&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mission: The Raven&#039;s Nest&amp;lt;br&amp;gt;&lt;br /&gt;
Day: 1&amp;lt;br&amp;gt;&lt;br /&gt;
Stardate: 2414.06.01&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Captain&#039;s Log Supplemental&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Things have been moving along normally since we left the Kozani shipyards. We have been extra vigilant in watching for the spontaneous plasma field storms that caused us such trouble recently, but we have also been certain to continue with our survey of sector 6309.&amp;lt;br&amp;gt;&lt;br /&gt;
Recently we detected a freighter at long range scan, which appears to be unmanned. As the vessel has since been identified as the [[SS Lalo]], a ship which was stolen by a group of separatists, we have decided to investigate.&amp;lt;br&amp;gt;&lt;br /&gt;
However, it does not appear that we are the only Starfleet vessel in the area, as we have now also made contact with the [[USS Boudicca]]. I have to ask myself what strange auspices are aligning here for two of the core ships of the 52nd fleet to come together at a single seemingly abandoned vessel as the Lalo. I hope that we can get to the bottom of the mystery, sooner rather than later.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;Small&amp;gt;Daniel Greene &amp;lt;br&amp;gt;&lt;br /&gt;
Captain Ahmed Ibn Salid&amp;lt;br&amp;gt;&lt;br /&gt;
CO, USS Rosenante&amp;lt;br&amp;gt;&lt;br /&gt;
www.startrekfreedom.com&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Starship}}&lt;br /&gt;
[[Category: Active Ships]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Tho%E2%80%99var_Kevras&amp;diff=55396</id>
		<title>Tho’var Kevras</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Tho%E2%80%99var_Kevras&amp;diff=55396"/>
		<updated>2012-05-09T20:54:46Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* Starfleet History */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;toc colour&amp;quot; style=&amp;quot;margin: 0 0 1em 1em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:goldenrod&amp;quot; align=&amp;quot;center&amp;quot; |&amp;lt;font color=maroon&amp;gt;&#039;&#039;&#039;tho&#039;var Kevras&#039;&#039;&#039;&amp;lt;br&amp;gt;&amp;lt;font color=maroon&amp;gt;Assistant Chief Engineer&amp;lt;/font&amp;gt;&amp;lt;br&amp;gt;[[File:noone.jpg|center|300px|]]&amp;lt;br&amp;gt;&amp;lt;/font&amp;gt;[[Image:Rosenante-Alt-2up.jpg|center|300px|USS Rosenante]]&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Vital Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Age: 31&lt;br /&gt;
**Gender: Male&lt;br /&gt;
**Birthplace: [[Andoria]], stardate 2383.05.18&lt;br /&gt;
**Species: 3/8ths [[Andorian]] - 5/8ths [[Andorian|Aenar]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Physical Information&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Eye Color: Blue White&lt;br /&gt;
**Hair Color: White&lt;br /&gt;
**Height: 5&#039;8 feet&lt;br /&gt;
**Weight: 150 lbs&lt;br /&gt;
**Skin Color: Greenish blue&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Career Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Rank: [[Rank|Lieutenant JG]]&lt;br /&gt;
** Current Assignment:  [[USS Rosenante]]&lt;br /&gt;
|-&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
==Physical Description==&lt;br /&gt;
Tho’var look like Aenars and Andorians, with the only difference his skin is a little greener.  &lt;br /&gt;
&lt;br /&gt;
Because he is 5/8 Aenar, Tho’var is partially blind. He has almost no peripheral vision and the little he sees in front of him is slightly blurred. However, as most Aenar, his antennas and great telepathic abilities allow him to do his duty without any impediment. In fact, the fact he rely very little on sight and a lot on the other sensations make him as efficient in the dark than in the light. &lt;br /&gt;
&lt;br /&gt;
Tho’var has also inherited the passion of Andorian. He is strongly impulsive. However, he still has some of the calm of the Aenar. &lt;br /&gt;
&lt;br /&gt;
He has great telepathic abilities, but since he is only 5/8 Aenar, it is not as acute as Aenars. &lt;br /&gt;
&lt;br /&gt;
==Background== &lt;br /&gt;
Tho’var is the older son of Shorel (Aenar), and Thavin(Andorian). Thavin grand-father was himself an Aenar (which explain why Tho’var is 5/8 Aenar), and the family lived mostly among the Aenar. Thavin was a spaceflight operator on Andoria while Shorev was a judge. Tho’var has also one sister, Sevel. Shorev and Tho’var has been very respectful to the Aenar culture, prefering pacifism and trying to avoid war and conflict as much as they could. Family was also very important. Both Tho’var and Sevel have been raised with those values of peace and kindness.&lt;br /&gt;
&lt;br /&gt;
At 17, Tho’var was accepted in physics at Andor Academy. He graduated and started to work at a research facility on Andoria, but after only six months, he did not like it. He wanted something more challenging. In fact, he was interested in going to Starfleet Academy, but knowing his parents would not like it considering Starfleet was a military division, he chose to go to Andor instead. It is only afterwards that he realized he was not doing what he wanted to do, and rather decided to disappoint his parents and join Starfleet. At first, his parents disagreed, but they rather surprisingly accepted and supported Tho’var’s decision.&lt;br /&gt;
&lt;br /&gt;
Tho’var went to Starfleet Academy at 20. Having already learned physics, he perfected is knowledge of warp theory and physics to become an engineer. He graduated during the Civil War and was assigned to a ship in Doenitz fleet. Tho’var was in the brig when his ship and Doenitz launched the attack on Andoria. Helped by the inside, he was able to escape, but failed to prevent the genocide.&lt;br /&gt;
&lt;br /&gt;
Filled with anger and hatred, all he had in mind was to avenge his species. Not trusting anyone in the Federation anymore, he was convinced to join the Maquis.&lt;br /&gt;
&lt;br /&gt;
==Pre-Starfleet History==&lt;br /&gt;
&lt;br /&gt;
Once the Civil War was over, there was no enemy to hate. He remained a few months with the Maquis but, remembering the pacific philosophy of his parent, he decided that he could not live eternally in anger and hatred. In 2409, he left the Maquis and returned to his homeworld only to learn that his parent and most of his family died in the genocide, and her sister had disappeared.&lt;br /&gt;
 &lt;br /&gt;
Looking again for a new home, Tho’var was accepted on Ba’ku. The pacific and untechnological nature of their specie allowed him to find new interest, and forget about the war and the genocide. However, after a year, it was entirely what he was looking for and moved somewhere else.&lt;br /&gt;
&lt;br /&gt;
In 2410, Tho’var decided to move to P’Jem, a colony close to Andoria where both Andorian and Vulcans lived. It was a first step towards moving back to Andoria. His contact with Vulcans helped him a lot, especially the meditation he was taught. He also made friends with some other Andorians that survived the attack. &lt;br /&gt;
&lt;br /&gt;
After a successful year, Tho’var make the big step and settled back to his homeworld Andoria. Almost everything was destroyed, and Andoria were mostly just ruins of what was before an incredibly rich culture. All Andorians and Aenars knew that their species was almost instinct and it was now imperative that they focused on rebuilding and reproducing.  For a bit more than a year, Tho’var helped his specie (or what left of them) settling back. His skills as engineers and the botanist skills he learned on Ba’ku were very useful. However, he was here more because of the obligation he had for his species...much more than because he really wanted to be here. He wanted to leave and do something else, but for long, he thought it would be abandoning his own kind. Surprisingly however, his species were very understanding and allowed him to leave his own kind and live his life. &lt;br /&gt;
&lt;br /&gt;
==Starfleet History==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;[2407-2408]&amp;lt;/strong&amp;gt;&amp;lt;/font&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Tho’var graduated in 2407, at the beginning of the cold war. Not really knowing what was going on, he was assigned on one of Doenitz ship as engineer.  The Civil War make him unease, but as he was a rookie, he accepted the difficult orders his ships were given. He even, for a moment, believed Doenitz propaganda against admiral Lodona. However, he soon realized that Doenitz was antidemocratic. He refused once to obey an order and was sent to the brig for thirty days. He was reintegrated afterwards, but after only one week of resuming service, he was again put into the brig, for no reason this time. He then learned by his crewmates and friends who were coerce to follow orders, that Doenitz had taken power and was about to launch an attack on Andoria. Hopefully, some of his friends helped him to escape with a shuttle.  It was a difficult moment. While escaping, he saw Doenitz fleet bombarding his planet. He wanted to help them, but he knew he could not do anything. His shuttle was heavily damaged during his escape attempt, but he managed to go to warp. To make the repairs, he hid into a planet ring in a neighbour system. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;[After 2412]&amp;lt;/strong&amp;gt;&amp;lt;/font&amp;gt; &amp;lt;br&amp;gt;&amp;lt;br&amp;gt; In 2412, Tho’var decided, not without great doubts and remorse, to return to Starfleet. He was promoted to full ensign and served on two ships..... In 2414, he was promoted to Lieutenant and assigned to the USS Rosenante.&lt;br /&gt;
&lt;br /&gt;
==Education==&lt;br /&gt;
:Degree in physics at Andor Academy (2400-2403)&lt;br /&gt;
:Starfleet Academy, engineer (2403-2407)&lt;br /&gt;
==Medical History==&lt;br /&gt;
The Andorian and Aenar genocide had been a tragedy. Tho’var has had great difficulty accepting it. He still try to avoid the emotions. The anger and frustration, as well as the feeling of loss that was acutely felt in the first four years and explain greatly why he was unable to really settle anywhere for the following four years. Since, Tho’var’s anger has decreased considerably and he has started to regain a certain sense of balance and purpose. &lt;br /&gt;
&lt;br /&gt;
{{Rosenante Crew Roster}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Characters]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Tho%E2%80%99var_Kevras&amp;diff=55395</id>
		<title>Tho’var Kevras</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Tho%E2%80%99var_Kevras&amp;diff=55395"/>
		<updated>2012-05-09T20:54:14Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;toc colour&amp;quot; style=&amp;quot;margin: 0 0 1em 1em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:goldenrod&amp;quot; align=&amp;quot;center&amp;quot; |&amp;lt;font color=maroon&amp;gt;&#039;&#039;&#039;tho&#039;var Kevras&#039;&#039;&#039;&amp;lt;br&amp;gt;&amp;lt;font color=maroon&amp;gt;Assistant Chief Engineer&amp;lt;/font&amp;gt;&amp;lt;br&amp;gt;[[File:noone.jpg|center|300px|]]&amp;lt;br&amp;gt;&amp;lt;/font&amp;gt;[[Image:Rosenante-Alt-2up.jpg|center|300px|USS Rosenante]]&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Vital Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Age: 31&lt;br /&gt;
**Gender: Male&lt;br /&gt;
**Birthplace: [[Andoria]], stardate 2383.05.18&lt;br /&gt;
**Species: 3/8ths [[Andorian]] - 5/8ths [[Andorian|Aenar]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Physical Information&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Eye Color: Blue White&lt;br /&gt;
**Hair Color: White&lt;br /&gt;
**Height: 5&#039;8 feet&lt;br /&gt;
**Weight: 150 lbs&lt;br /&gt;
**Skin Color: Greenish blue&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Career Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Rank: [[Rank|Lieutenant JG]]&lt;br /&gt;
** Current Assignment:  [[USS Rosenante]]&lt;br /&gt;
|-&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
==Physical Description==&lt;br /&gt;
Tho’var look like Aenars and Andorians, with the only difference his skin is a little greener.  &lt;br /&gt;
&lt;br /&gt;
Because he is 5/8 Aenar, Tho’var is partially blind. He has almost no peripheral vision and the little he sees in front of him is slightly blurred. However, as most Aenar, his antennas and great telepathic abilities allow him to do his duty without any impediment. In fact, the fact he rely very little on sight and a lot on the other sensations make him as efficient in the dark than in the light. &lt;br /&gt;
&lt;br /&gt;
Tho’var has also inherited the passion of Andorian. He is strongly impulsive. However, he still has some of the calm of the Aenar. &lt;br /&gt;
&lt;br /&gt;
He has great telepathic abilities, but since he is only 5/8 Aenar, it is not as acute as Aenars. &lt;br /&gt;
&lt;br /&gt;
==Background== &lt;br /&gt;
Tho’var is the older son of Shorel (Aenar), and Thavin(Andorian). Thavin grand-father was himself an Aenar (which explain why Tho’var is 5/8 Aenar), and the family lived mostly among the Aenar. Thavin was a spaceflight operator on Andoria while Shorev was a judge. Tho’var has also one sister, Sevel. Shorev and Tho’var has been very respectful to the Aenar culture, prefering pacifism and trying to avoid war and conflict as much as they could. Family was also very important. Both Tho’var and Sevel have been raised with those values of peace and kindness.&lt;br /&gt;
&lt;br /&gt;
At 17, Tho’var was accepted in physics at Andor Academy. He graduated and started to work at a research facility on Andoria, but after only six months, he did not like it. He wanted something more challenging. In fact, he was interested in going to Starfleet Academy, but knowing his parents would not like it considering Starfleet was a military division, he chose to go to Andor instead. It is only afterwards that he realized he was not doing what he wanted to do, and rather decided to disappoint his parents and join Starfleet. At first, his parents disagreed, but they rather surprisingly accepted and supported Tho’var’s decision.&lt;br /&gt;
&lt;br /&gt;
Tho’var went to Starfleet Academy at 20. Having already learned physics, he perfected is knowledge of warp theory and physics to become an engineer. He graduated during the Civil War and was assigned to a ship in Doenitz fleet. Tho’var was in the brig when his ship and Doenitz launched the attack on Andoria. Helped by the inside, he was able to escape, but failed to prevent the genocide.&lt;br /&gt;
&lt;br /&gt;
Filled with anger and hatred, all he had in mind was to avenge his species. Not trusting anyone in the Federation anymore, he was convinced to join the Maquis.&lt;br /&gt;
&lt;br /&gt;
==Pre-Starfleet History==&lt;br /&gt;
&lt;br /&gt;
Once the Civil War was over, there was no enemy to hate. He remained a few months with the Maquis but, remembering the pacific philosophy of his parent, he decided that he could not live eternally in anger and hatred. In 2409, he left the Maquis and returned to his homeworld only to learn that his parent and most of his family died in the genocide, and her sister had disappeared.&lt;br /&gt;
 &lt;br /&gt;
Looking again for a new home, Tho’var was accepted on Ba’ku. The pacific and untechnological nature of their specie allowed him to find new interest, and forget about the war and the genocide. However, after a year, it was entirely what he was looking for and moved somewhere else.&lt;br /&gt;
&lt;br /&gt;
In 2410, Tho’var decided to move to P’Jem, a colony close to Andoria where both Andorian and Vulcans lived. It was a first step towards moving back to Andoria. His contact with Vulcans helped him a lot, especially the meditation he was taught. He also made friends with some other Andorians that survived the attack. &lt;br /&gt;
&lt;br /&gt;
After a successful year, Tho’var make the big step and settled back to his homeworld Andoria. Almost everything was destroyed, and Andoria were mostly just ruins of what was before an incredibly rich culture. All Andorians and Aenars knew that their species was almost instinct and it was now imperative that they focused on rebuilding and reproducing.  For a bit more than a year, Tho’var helped his specie (or what left of them) settling back. His skills as engineers and the botanist skills he learned on Ba’ku were very useful. However, he was here more because of the obligation he had for his species...much more than because he really wanted to be here. He wanted to leave and do something else, but for long, he thought it would be abandoning his own kind. Surprisingly however, his species were very understanding and allowed him to leave his own kind and live his life. &lt;br /&gt;
&lt;br /&gt;
==Starfleet History==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;[2407-2408]&amp;lt;/font&amp;gt;&amp;lt;/strong&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Tho’var graduated in 2407, at the beginning of the cold war. Not really knowing what was going on, he was assigned on one of Doenitz ship as engineer.  The Civil War make him unease, but as he was a rookie, he accepted the difficult orders his ships were given. He even, for a moment, believed Doenitz propaganda against admiral Lodona. However, he soon realized that Doenitz was antidemocratic. He refused once to obey an order and was sent to the brig for thirty days. He was reintegrated afterwards, but after only one week of resuming service, he was again put into the brig, for no reason this time. He then learned by his crewmates and friends who were coerce to follow orders, that Doenitz had taken power and was about to launch an attack on Andoria. Hopefully, some of his friends helped him to escape with a shuttle.  It was a difficult moment. While escaping, he saw Doenitz fleet bombarding his planet. He wanted to help them, but he knew he could not do anything. His shuttle was heavily damaged during his escape attempt, but he managed to go to warp. To make the repairs, he hid into a planet ring in a neighbour system. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;[After 2412]&amp;lt;/font&amp;gt;&amp;lt;/strong&amp;gt; &amp;lt;br&amp;gt;&amp;lt;br&amp;gt; In 2412, Tho’var decided, not without great doubts and remorse, to return to Starfleet. He was promoted to full ensign and served on two ships..... In 2414, he was promoted to Lieutenant and assigned to the USS Rosenante. &lt;br /&gt;
&lt;br /&gt;
==Education==&lt;br /&gt;
:Degree in physics at Andor Academy (2400-2403)&lt;br /&gt;
:Starfleet Academy, engineer (2403-2407)&lt;br /&gt;
==Medical History==&lt;br /&gt;
The Andorian and Aenar genocide had been a tragedy. Tho’var has had great difficulty accepting it. He still try to avoid the emotions. The anger and frustration, as well as the feeling of loss that was acutely felt in the first four years and explain greatly why he was unable to really settle anywhere for the following four years. Since, Tho’var’s anger has decreased considerably and he has started to regain a certain sense of balance and purpose. &lt;br /&gt;
&lt;br /&gt;
{{Rosenante Crew Roster}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Characters]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Tho%E2%80%99var_Kevras&amp;diff=55394</id>
		<title>Tho’var Kevras</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Tho%E2%80%99var_Kevras&amp;diff=55394"/>
		<updated>2012-05-09T20:53:46Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: Created page with &amp;quot;{| class=&amp;quot;toc colour&amp;quot; style=&amp;quot;margin: 0 0 1em 1em;&amp;quot; align=&amp;quot;right&amp;quot; ! style=&amp;quot;background:goldenrod&amp;quot; align=&amp;quot;center&amp;quot; |&amp;lt;font color=maroon&amp;gt;&amp;#039;&amp;#039;&amp;#039;tho&amp;#039;var Kevras&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&amp;lt;font color=maroon&amp;gt;A...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;toc colour&amp;quot; style=&amp;quot;margin: 0 0 1em 1em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:goldenrod&amp;quot; align=&amp;quot;center&amp;quot; |&amp;lt;font color=maroon&amp;gt;&#039;&#039;&#039;tho&#039;var Kevras&#039;&#039;&#039;&amp;lt;br&amp;gt;&amp;lt;font color=maroon&amp;gt;Assistant Chief Engineer&amp;lt;/font&amp;gt;&amp;lt;br&amp;gt;[[File:noone.jpg|center|300px|]]&amp;lt;br&amp;gt;&amp;lt;/font&amp;gt;[[Image:Rosenante-Alt-2up.jpg|center|300px|USS Rosenante]]&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Vital Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Age: 31&lt;br /&gt;
**Gender: Male&lt;br /&gt;
**Birthplace: [[Andoria]], stardate 2383.05.18&lt;br /&gt;
**Species: 3/8ths [[Andorian]]/ 5/8ths [[Aenar]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Physical Information&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Eye Color: Blue White&lt;br /&gt;
**Hair Color: White&lt;br /&gt;
**Height: 5&#039;8 feet&lt;br /&gt;
**Weight: 150 lbs&lt;br /&gt;
**Skin Color: Greenish blue&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Career Statistics&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
** Rank: [[Rank|Lieutenant JG]]&lt;br /&gt;
** Current Assignment:  [[USS Rosenante]]&lt;br /&gt;
|-&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
==Physical Description==&lt;br /&gt;
Tho’var look like Aenars and Andorians, with the only difference his skin is a little greener.  &lt;br /&gt;
&lt;br /&gt;
Because he is 5/8 Aenar, Tho’var is partially blind. He has almost no peripheral vision and the little he sees in front of him is slightly blurred. However, as most Aenar, his antennas and great telepathic abilities allow him to do his duty without any impediment. In fact, the fact he rely very little on sight and a lot on the other sensations make him as efficient in the dark than in the light. &lt;br /&gt;
&lt;br /&gt;
Tho’var has also inherited the passion of Andorian. He is strongly impulsive. However, he still has some of the calm of the Aenar. &lt;br /&gt;
&lt;br /&gt;
He has great telepathic abilities, but since he is only 5/8 Aenar, it is not as acute as Aenars. &lt;br /&gt;
&lt;br /&gt;
==Background== &lt;br /&gt;
Tho’var is the older son of Shorel (Aenar), and Thavin(Andorian). Thavin grand-father was himself an Aenar (which explain why Tho’var is 5/8 Aenar), and the family lived mostly among the Aenar. Thavin was a spaceflight operator on Andoria while Shorev was a judge. Tho’var has also one sister, Sevel. Shorev and Tho’var has been very respectful to the Aenar culture, prefering pacifism and trying to avoid war and conflict as much as they could. Family was also very important. Both Tho’var and Sevel have been raised with those values of peace and kindness.&lt;br /&gt;
&lt;br /&gt;
At 17, Tho’var was accepted in physics at Andor Academy. He graduated and started to work at a research facility on Andoria, but after only six months, he did not like it. He wanted something more challenging. In fact, he was interested in going to Starfleet Academy, but knowing his parents would not like it considering Starfleet was a military division, he chose to go to Andor instead. It is only afterwards that he realized he was not doing what he wanted to do, and rather decided to disappoint his parents and join Starfleet. At first, his parents disagreed, but they rather surprisingly accepted and supported Tho’var’s decision.&lt;br /&gt;
&lt;br /&gt;
Tho’var went to Starfleet Academy at 20. Having already learned physics, he perfected is knowledge of warp theory and physics to become an engineer. He graduated during the Civil War and was assigned to a ship in Doenitz fleet. Tho’var was in the brig when his ship and Doenitz launched the attack on Andoria. Helped by the inside, he was able to escape, but failed to prevent the genocide.&lt;br /&gt;
&lt;br /&gt;
Filled with anger and hatred, all he had in mind was to avenge his species. Not trusting anyone in the Federation anymore, he was convinced to join the Maquis.&lt;br /&gt;
&lt;br /&gt;
==Pre-Starfleet History==&lt;br /&gt;
&lt;br /&gt;
Once the Civil War was over, there was no enemy to hate. He remained a few months with the Maquis but, remembering the pacific philosophy of his parent, he decided that he could not live eternally in anger and hatred. In 2409, he left the Maquis and returned to his homeworld only to learn that his parent and most of his family died in the genocide, and her sister had disappeared.&lt;br /&gt;
 &lt;br /&gt;
Looking again for a new home, Tho’var was accepted on Ba’ku. The pacific and untechnological nature of their specie allowed him to find new interest, and forget about the war and the genocide. However, after a year, it was entirely what he was looking for and moved somewhere else.&lt;br /&gt;
&lt;br /&gt;
In 2410, Tho’var decided to move to P’Jem, a colony close to Andoria where both Andorian and Vulcans lived. It was a first step towards moving back to Andoria. His contact with Vulcans helped him a lot, especially the meditation he was taught. He also made friends with some other Andorians that survived the attack. &lt;br /&gt;
&lt;br /&gt;
After a successful year, Tho’var make the big step and settled back to his homeworld Andoria. Almost everything was destroyed, and Andoria were mostly just ruins of what was before an incredibly rich culture. All Andorians and Aenars knew that their species was almost instinct and it was now imperative that they focused on rebuilding and reproducing.  For a bit more than a year, Tho’var helped his specie (or what left of them) settling back. His skills as engineers and the botanist skills he learned on Ba’ku were very useful. However, he was here more because of the obligation he had for his species...much more than because he really wanted to be here. He wanted to leave and do something else, but for long, he thought it would be abandoning his own kind. Surprisingly however, his species were very understanding and allowed him to leave his own kind and live his life. &lt;br /&gt;
&lt;br /&gt;
==Starfleet History==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;[2407-2408]&amp;lt;/font&amp;gt;&amp;lt;/strong&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Tho’var graduated in 2407, at the beginning of the cold war. Not really knowing what was going on, he was assigned on one of Doenitz ship as engineer.  The Civil War make him unease, but as he was a rookie, he accepted the difficult orders his ships were given. He even, for a moment, believed Doenitz propaganda against admiral Lodona. However, he soon realized that Doenitz was antidemocratic. He refused once to obey an order and was sent to the brig for thirty days. He was reintegrated afterwards, but after only one week of resuming service, he was again put into the brig, for no reason this time. He then learned by his crewmates and friends who were coerce to follow orders, that Doenitz had taken power and was about to launch an attack on Andoria. Hopefully, some of his friends helped him to escape with a shuttle.  It was a difficult moment. While escaping, he saw Doenitz fleet bombarding his planet. He wanted to help them, but he knew he could not do anything. His shuttle was heavily damaged during his escape attempt, but he managed to go to warp. To make the repairs, he hid into a planet ring in a neighbour system. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;[After 2412]&amp;lt;/font&amp;gt;&amp;lt;/strong&amp;gt; &amp;lt;br&amp;gt;&amp;lt;br&amp;gt; In 2412, Tho’var decided, not without great doubts and remorse, to return to Starfleet. He was promoted to full ensign and served on two ships..... In 2414, he was promoted to Lieutenant and assigned to the USS Rosenante. &lt;br /&gt;
&lt;br /&gt;
==Education==&lt;br /&gt;
:Degree in physics at Andor Academy (2400-2403)&lt;br /&gt;
:Starfleet Academy, engineer (2403-2407)&lt;br /&gt;
==Medical History==&lt;br /&gt;
The Andorian and Aenar genocide had been a tragedy. Tho’var has had great difficulty accepting it. He still try to avoid the emotions. The anger and frustration, as well as the feeling of loss that was acutely felt in the first four years and explain greatly why he was unable to really settle anywhere for the following four years. Since, Tho’var’s anger has decreased considerably and he has started to regain a certain sense of balance and purpose. &lt;br /&gt;
&lt;br /&gt;
{{Rosenante Crew Roster}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Characters]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Template:USS_Rosenante_Data_Box&amp;diff=55393</id>
		<title>Template:USS Rosenante Data Box</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Template:USS_Rosenante_Data_Box&amp;diff=55393"/>
		<updated>2012-05-09T20:35:33Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;toc colour&amp;quot; style=&amp;quot;margin: 0 0 1em 1em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
! style=&amp;quot;background:goldenrod&amp;quot; align=&amp;quot;center&amp;quot; |&amp;lt;font color=maroon&amp;gt;&#039;&#039;&#039;USS Rosenante&#039;&#039;&#039;&amp;lt;br&amp;gt;&amp;lt;font color=maroon&amp;gt;NCC-924650&amp;lt;/font&amp;gt;&amp;lt;br&amp;gt;Launched 2408.01.07&amp;lt;br&amp;gt;[[Image:Rosenante-Alt-2up.jpg|center|300px|The [[USS Rosenante]] NCC–924650]]&amp;lt;br&amp;gt;[[Image:RoseDedication.jpg|center|300px]]&amp;lt;br&amp;gt;&#039;&#039;&#039;Rosenante Class&#039;&#039;&#039;&amp;lt;br&amp;gt;Long-Range Explorer&amp;lt;/font&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;font-size: 90%&amp;quot; |&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Crew Roster&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Command Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
** [[Ahmed Ibn Salid|Capt. Ahmed Ibn Salid, Commanding Officer]]&lt;br /&gt;
**[[Ben Soma|Lt. Ben Soma, First Officer]]&lt;br /&gt;
**[[Sanok|Lt. Sanok, Second Officer/Security Chief]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Operations Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
**[[Thomas Jackson|Lt. Thomas Jackson, Chief of Operations]]&lt;br /&gt;
**[[Chance Raschen|Lt. Chance Raschen, Strategic Operations/Quartermaster]]&lt;br /&gt;
**[[Tollian Yalix|Lt. Tollian Yalix, Assistant Operations Officer]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Medical Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
**[[Jennifer Caskie|Cmdr. Jennifer Caskie, CMO]]&lt;br /&gt;
**[[Tayla Fraiser|Lt. JG Tayla Fraiser, ACMO]] &lt;br /&gt;
**[[Katherine &#039;Kitty&#039; Fisher|Lt. Kitty Fisher, Medical Officer]]&lt;br /&gt;
**[[Nathan Allen Fuller|MCPO Nathan Allen Fuller, Chief Field Medic]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Counseling Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
**None Assigned&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Tactical &amp;amp; Security Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
**[[Sanok|Lt. Sanok, Second Officer/Security Chief]]&lt;br /&gt;
**[[Marta Nunez|Lt. JG Marta Nunez, Assistant Security Chief]]&lt;br /&gt;
**[[Jessica Signos|Ens. Jessica Signos, Assistant Tactical Chief]]&lt;br /&gt;
**[[Mike Rosenbauer|Lt. JG Mike Rosenbauer, Security Officer]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Engineering Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
**[[Steven Wade Matrix|Lt. Cmdr. Steven Wade Matrix, Chief Engineer]]&lt;br /&gt;
**[[Tho’var Kevras| Lieutenant JG Tho’var Kevras, Assistant Chief Engineer]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Science Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
**[[Viskhard|Lt. JG Viskhard, Acting Chief Science Officer]]&lt;br /&gt;
**[[Andrew Elliot Maddox|Crewman Andrew Elliot Maddox, Science Officer]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Flight Operations Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
**[[Dralar|Lt. Dralar, CONN Officer]] &lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Other Starfleet Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
**[[Matthew McLaren|Lt. Cmdr. Matthew McLaren, ATTU]]&lt;br /&gt;
**[[Xim|Lt. Xim, Gamma Shift Leader]]&lt;br /&gt;
**[[Nayeli|Lt. Nayeli, JAG Supervisor]]&lt;br /&gt;
**[[Sien|Sien, Civilian]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Retired Staff&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&lt;br /&gt;
**[[Aleesa Wyler|Lt. Aleesa Wyler, Awaiting Assignment]]&lt;br /&gt;
**[[Alimi Morrow|Lt. Alimi Morrow, Awaiting Assignment]]&lt;br /&gt;
**[[Kimiko Ichijo|Lt. JG Kimiko Ichijo, Awaiting Assignment]]&lt;br /&gt;
**[[Narvak|Ens. JG Narvak, Awaiting Assignment]]&lt;br /&gt;
**[[David Michael Tamblyn|Lt. David Tamblyn, Awaiting Assignment]]&lt;br /&gt;
**[[T&#039;Larah Sullivan|Lt. Col. T&#039;Larah Sullivan, Marine CO]]&lt;br /&gt;
**[[Lanista|Lt. Lanista, Chief Science Officer]]&lt;br /&gt;
* &amp;lt;font color=goldenrod&amp;gt;&amp;lt;center&amp;gt;&amp;lt;strong&amp;gt;&#039;&#039;&#039;Missions&#039;&#039;&#039;&amp;lt;/strong&amp;gt;&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:[[Picking up the Pieces]]&lt;br /&gt;
:[[A Fine and Private Place]] &lt;br /&gt;
:[[Furlough | Letters of Marques]]&lt;br /&gt;
:[[Fields of Elysium]]&lt;br /&gt;
:[[Homecoming]]&lt;br /&gt;
:[[Into the Darkness, Go I]]&lt;br /&gt;
:[[Equals and Opposites]]&lt;br /&gt;
:[[The Quondam Season]]&lt;br /&gt;
:[[The Gilded Man]]&lt;br /&gt;
:[[Touch of the Eidolon]]&lt;br /&gt;
:[[Just Another Saturday Night]]&lt;br /&gt;
:[[Once More Into The Breach]]&lt;br /&gt;
:[[Personal Logs]]&lt;br /&gt;
:[[The Third Law]]&lt;br /&gt;
:[[The Captain&#039;s Cotillion]]&lt;br /&gt;
:[[The Veil of the Sky]] &lt;br /&gt;
:[[A Port in the Storm]] &lt;br /&gt;
:[[The Raven&#039;s Nest]] **Underway**&lt;br /&gt;
:[[Lest We Forget]] **Coming Soon**&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;&amp;lt;sup&amp;gt;Rosenante image compliments of Roger Wackowski.&amp;lt;/sup&amp;gt;&amp;lt;/center&amp;gt;&lt;br /&gt;
&amp;lt;center&amp;gt;&amp;lt;sup&amp;gt;Dedication plaque by Bosshard.&amp;lt;/sup&amp;gt;&amp;lt;/center&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;center&amp;gt;&amp;lt;sup&amp;gt;[[Template:USS Rosenante Missions|Edit Mission List]]&amp;lt;/sup&amp;gt;&amp;lt;/center&amp;gt;&lt;br /&gt;
&amp;lt;center&amp;gt;&amp;lt;sup&amp;gt;[[Template:Rosenante Crew Roster|Edit Crew Roster]]&amp;lt;/sup&amp;gt;&amp;lt;/center&amp;gt;&lt;br /&gt;
&amp;lt;center&amp;gt;&amp;lt;sup&amp;gt;[[Template:USS Rosenante Data Box|Edit Data Box]]&amp;lt;/sup&amp;gt;&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;noinclude&amp;gt;[[Category: Active Ships]]&amp;lt;/noinclude&amp;gt;&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=Template:Rosenante_Crew_Roster&amp;diff=55392</id>
		<title>Template:Rosenante Crew Roster</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=Template:Rosenante_Crew_Roster&amp;diff=55392"/>
		<updated>2012-05-09T20:34:48Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
{| width=80% class=&amp;quot;toccolours&amp;quot; style=&amp;quot;float:center; background:black; background-color: #FFA500; border: 0 ;&amp;quot; cellspacing=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;background:black&amp;quot; align=&amp;quot;center&amp;quot; colspan=3 | &#039;&#039;&#039;Crew of the [[USS Rosenante]]&#039;&#039;&#039; &lt;br /&gt;
| rowspan=4 style=&amp;quot;background:black&amp;quot; | [[Image:52ndfleet.jpg|centre|120px|52nd Fleet Logo]]&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;font-size: 90%; background:black&amp;quot; colspan=3|&#039;&#039;&#039;Command Staff:&#039;&#039;&#039; [[Ahmed Ibn Salid|Captain Ahmed Ibn Salid, CO]] |  [[Ben Soma|Lt. Ben Soma, FO]] |[[Sanok| Lt. Sanok, 2O/CSEC]] &lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;font-size: 90%; background:black&amp;quot; colspan=3|&#039;&#039;&#039;Operations Staff:&#039;&#039;&#039; [[Thomas Jackson|Lt. Thomas Jackson, Chief of Operations]] | [[Chance Raschen|Lt. Chance Raschen, Strategic Operations/Quartermaster]] | [[Tollian Yalix|Lt. Tollian Yalix, AOPs]] |  &lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;font-size: 90%; background:black&amp;quot; colspan=3|&#039;&#039;&#039;Medical Staff:&#039;&#039;&#039; [[Jennifer Caskie|Cmdr. Jennifer Caskie, CMO]] | [[Tayla Fraiser |Lt. JG Tayla Fraiser, ACMO]] | [[Katherine &#039;Kitty&#039; Fisher|Lt. Kitty Fisher, MO]] | [[Nathan Allen Fuller|MCPO Nathan Allen Fuller, Chief Field Medic]] &lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;font-size: 90%; background:black&amp;quot; colspan=3|&#039;&#039;&#039;Counseling Staff:&#039;&#039;&#039; None Assigned |&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;font-size: 90%; background:black&amp;quot; colspan=3|&#039;&#039;&#039;Tactical &amp;amp; Security Staff:&#039;&#039;&#039;  [[Sanok| Lt. Sanok, 2O/CSEC]] | [[Marta Nunez|Lt. JG Marta Nunez, ASEC]] | [[Blake Turner| Ensign. JG Blake Turner, SO]] | [[Jessica Signos|Ens. Jessica Signos, ATAC]] | [[Mike Rosenbauer|Lt. JG Mike Rosenbauer, SO]]&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;font-size: 90%; background:black&amp;quot; colspan=3|&#039;&#039;&#039;Engineering Staff:&#039;&#039;&#039;  [[Steven Wade Matrix|Lt. Cmdr. Steven Wade Matrix, CEO]] | [[Tho’var Kevras|Lt JG Tho’var Kevras, ACEO]]&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;font-size: 90%; background:black&amp;quot; colspan=3|&#039;&#039;&#039;Science Staff:&#039;&#039;&#039;   [[Viskhard|Lt. JG Viskhard, Acting CSO]] | [[Andrew Elliot Maddox|Crewman Andrew Elliot Maddox, SO]]&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;font-size: 90%; background:black&amp;quot; colspan=3|&#039;&#039;&#039;Flight Operations Staff:&#039;&#039;&#039; [[Dralar|Lt. Dralar, CONN]]&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;font-size: 90%; background:black&amp;quot; colspan=3|&#039;&#039;&#039;Other Starfleet Staff:&#039;&#039;&#039; [[Matthew McLaren|Lt. Cmdr. Matthew McLaren, ATTU]] | [[Xim|Lt. Xim, Gamma Shift Leader]] | [[Nayeli|Lt. Nayeli, JAG Supervisor]] | [[Sien|Sien, Civilian]]&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;left&amp;quot; style=&amp;quot;font-size: 90%; background:black&amp;quot; colspan=3|&#039;&#039;&#039;Retired Staff:&#039;&#039;&#039;  [[Lanista|Lt. Lanista, CSO]] | [[Aleesa Wyler|Lt. Aleesa Wyler, CMO- Awaiting Assignment]] | [[Alimi Morrow|Lt. Alimi Morrow, CEO- Awaiting Assignment]] | [[Kimiko Ichijo|Lt. JG Kimiko Ichijo, Awaiting Assignment]], [[Narvak|Ens. JG Narvak, Awaiting Assignment]] | [[Aleesa Wyler|Lt. Aleesa Wyler, CMO- Awaiting Assignment]] | [[Alimi Morrow|Lt. Alimi Morrow, CEO- Awaiting Assignment]] | [[Kimiko Ichijo|Lt. JG Kimiko Ichijo, Awaiting Assignment]], [[Narvak|Ens. JG Narvak, Awaiting Assignment]] | [[M&#039;Epak|Ens. M&#039;Epak, Nurse]] |[[T&#039;Larah Sullivan|Cmdr. T&#039;Larah Sullivan, MCO]] |&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=The_Chimera_Directive&amp;diff=55391</id>
		<title>The Chimera Directive</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=The_Chimera_Directive&amp;diff=55391"/>
		<updated>2012-05-09T16:22:56Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* 6.0 Warp Propulsion Systems */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;  &lt;br /&gt;
  &lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
== 1.0	CHIMERA DIRECTIVE INTRODUCTION ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-1up.jpg|thumb|500px|The Rosenante Class Starship]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1.1 MISSION OBJECTIVES FOR ROSENANTÉ CLASS PROJECT&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Starfleet has long been charged with a broad spectrum of responsibilities to the citizens of the Federation and to the lifeforms of the Galaxy at large. As the volume of explored space continues to grow, and with it the Federation itself, so do Starfleet&#039;s duties. &lt;br /&gt;
&lt;br /&gt;
These duties range from relatively mundane domestic and civil missions, to cultural contact and diplomacy, to defense, to our primary mission of exploration and research. Many of these responsibilities are best carried out with relatively small, specialized ships. Yet there continues to be an ongoing need for an even narrower role vessel to protect the Federation against enemies that would use espionage and subversion to wage war against the Federation.&lt;br /&gt;
&lt;br /&gt;
This particular threat to Federation security is further complicated by political and economic restraints placed upon the Federation caused by the demands of maintaining an active war first against the Cardassian Union and then a Civil War between Doenitz Loyalists and 52nd Fleet seditionists. The Federation had suddenly found itself pressed on many fronts at various levels of engagement, often ill-prepared or incapable of information gathering against potential interior and exterior threats to the continued existence of the Federation.&lt;br /&gt;
&lt;br /&gt;
In response to the alarming number of intelligence related activities conducted against Federation projects, personnel, and equipment by exterior Intelligence Organizations, such as the Tal Shiar, the Dominion Shapeshifters, and The Cardassian Obsidian Order, Starfleet Intelligence has found itself grossly outnumbered, and under-appreciated by Starfleet Command. This lack of interdepartmental cooperation was only strengthened by Starfleet Intelligence&#039;s inability to detect and detain several pro-Revolutionary agents that had managed to infiltrate Starfleet Command, the Council of the President, and several other critical posts within the governmental structure of the Federation. The agents proved to be the first signs of the coming Civil war that would shake the foundations of the United Federation of Planets over the next several years.&lt;br /&gt;
&lt;br /&gt;
These breeches of critical security protocol within the government provided the critics of Starfleet Intelligence with ammunition to pressure Starfleet Command to tighten its control on the Intelligence Department. In late 2390s, with the Cardassian Union pressing their offensive against the Federation, Starfleet Intelligence learned of other threats to the Federation&#039;s continuing existence, as reports began to come into Starfleet Intelligence&#039;s Romulan desk reporting a large number of Romulan Infiltrators had somehow managed to concentrate themselves on the Federation Starships patrolling the Neutral Zone. With reports indicating that the Tal Shiar compromised a large majority of Starships patrolling the Neutral Zone, and with SFI fearing a Romulan Invasion, a massive counter Intelligence operation began. This operation, dubbed Sword and Shield, inserted several dozen Starfleet counterintelligence Specialists onboard the suspected Starships. For the better part of a year, these operatives played a deadly game of cloak and dagger against the expectant Tal Shiar operatives. This massive undertaking resulted in the largest capture of external espionage operatives in Starfleet history, 38 Starfleet officers (including 2 Ship Captains) and 12 Enlisted Starfleet personnel were arrested and charged with espionage against the Federation. 6 Starfleet Intelligence operatives lost their lives in this operation. &lt;br /&gt;
&lt;br /&gt;
It was to this threat that Admiral Rodrigo Doenitz would propose a solution. That solution came in the form of a Starship, dedicated completely to the tasks of espionage and interdiction operations. The vessel would be operated entirely independently of Starfleet command. Only Starfleet Intelligence would have any command authority over the vessel and its missions. This proposal created a scandalous outcry by Starfleet Command Officers, with the end result becoming less than favorable to the Doenitz cause.&lt;br /&gt;
&lt;br /&gt;
However, the dramatic success of Sword and Shield eased the tension against Starfleet Intelligence, and by the end of the War with the Cardassian Union in 2398; Starfleet Command realized the inability of SFI to conduct operations in hostile space, or to operate independently without the immediate assistance of Starship under Starfleet Command authority. It was in August of that year that Admiral Talbot, with the support of Admiral Doenitz proposed the idea of creating a new class of Starship capable of supporting Intelligence operations in hostile space, while simultaneously capable of performing signal, traffic and visual surveillance of facilities, ship movements and communications. Admiral Talbot argued that if SFI were equipped with such a vessel during the War, that the effectiveness of the Cardassian attack against the UFP would have been greatly reduced, if not altogether neutralized. Additionally, Talbot argued, such a ship working in Romulan space would have been priceless in determining the intentions and movements of the Tal Shiar during Operation Sword and Shield.&lt;br /&gt;
&lt;br /&gt;
Admiral Talbot’s conceptual Starship was deemed impossible to build, and also in violation of Starfleet Intelligence Command’s charter and the project was immediately disapproved. But that was not the end of the situation. &lt;br /&gt;
&lt;br /&gt;
Admiral Talbot, through secret channels with the complete support of Admiral Rodrigo Doenitz established a secret construction facility. Through various nefarious means, funds were funneled into the project and experienced Starfleet ship engineers were tasked to assist in developing a new class of Starship that could function efficiently within the confines established by the joint visions held by the two admirals.&lt;br /&gt;
&lt;br /&gt;
A special Starfleet Intelligence Operation was begun in a secret shipyard facility around early 2397. SFI operatives assigned to the operation interviewed and recruited Starship designers from across the Federation, purposely avoiding any designer that had ever worked on a Starship Project for the Federation in the past. These designers, assisted by the technical and personal experiences, of selected Starship Engineers laid down the design parameters for the project.&lt;br /&gt;
&lt;br /&gt;
After Admiral Doenitz’s successful coup, the project would prove to outlive many of its critics. With the full power of the office of the president of the Federation, Doenitz fast tracked his project making it an official Presidential Directive. This Directive was codenamed the Chimera Directive.&lt;br /&gt;
&lt;br /&gt;
The Rosenanté Class Starship designed by the Chimera Directive represents the most advanced design and systems innovations in the Federation. The basic design concept was developed around the Sovereign class and is considered the most advanced evolution of Starfleet Ship design to date.&lt;br /&gt;
&lt;br /&gt;
==Design Objectives==&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;&#039;&#039;Pursuant to Starfleet Intelligence Directive 1045.35, the following objectives have been established for the Rosenanté Class Starship development project:&#039;&#039;&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*	Provide a mobile platform for a wide range of ongoing intelligence and counterintelligence projects.&lt;br /&gt;
*	Provide autonomous capability for full execution of Starfleet Intelligence policy and directive options in hostile areas of space.&lt;br /&gt;
*	Incorporate recent advances in technology and protocols.&lt;br /&gt;
&lt;br /&gt;
To provide for these objectives, the Designers recommended that the Rosenanté class starship meets or exceeds the design goals in the following specification Categories;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Propulsion&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Sustainable cruise Velocity of Warp Factor 9.4. Ability to maintain speeds of up to Warp Factor 9.7 for periods of up to 12 Hours.&lt;br /&gt;
*	Sixth-phase dilithium controlled matter/antimatter reactor for primary power. Sustainable field output to exceed 1, 650 cochranes, peak transitional surge reserve to exceed 4,225% of nominal output. (170ns phase)&lt;br /&gt;
*	Warp Driver coils efficiency to meet or exceed 98% at speeds up to Warp 8.0. Minimum efficiency of 68% to be maintained through Warp 9.4. Life cycle of all primary coil elements to meet or exceed 1,200,000 cochrane-hours between neutron purge refurbishment. Secondary coil elements to meet or exceed 2,000,000 cochrane-hours between neutron purge refurbishment.&lt;br /&gt;
*	Warp field geometry to incorporate modified 85° Z-axis compression characteristics on forward warp lobe for increased peak transitional efficiency at high warp. Warp Nacelle centerlines to conform to 2.56: 1.1 ratio of separation to maximize field strength.&lt;br /&gt;
*	Secondary (impulse) propulsion systems to provide sub-light velocities up to and including .92 light speed (c). Engine systems of choice to include but not limited to at least two YPS 8063 fusion drive motors. All units to be equipped with subspace drive accelerators, field output not less than 180 millicochranes at 1.02 X l0³K. Reactor Modules to be field replaceable.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Mission&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Ability to operate independent of Starbase refurbishment for moderate periods of time. Independent operation mode capability of 1 Standard years at nominal Warp 6. Ability to execute deep-space exploration missions including charting and mapping, hostile contact scenarios, intelligence gathering and infiltration missions, full technical, biological and ecological studies.&lt;br /&gt;
*	Ability to support a wide range of mission-related ongoing research and other projects without impact on primary mission operations.&lt;br /&gt;
*	&#039;Full Spectrum EM, optical, subspace flux, Gravimetric, particle, and quark population analysis sensor capability. Multimode neutrino interferometery instrumentation. Wide band life sciences analysis capability. 2 twelve-meter interphasic field focused telescopes.&lt;br /&gt;
*	Upgradeable experiment and sensor array design. Ability to support on-board and probe mounted science and intelligence instrumentation.&lt;br /&gt;
*	Support facilities for auxiliary spacecraft and instrumented probes for short-range operations to include at least 1 independent launch, resupply, and repair bays.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Environment/Crew&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Environmental systems to conform to Starfleet Regulatory Agency (SFRA)- standard 102.9 for Class M compatible oxygen breathing personnel. All life-critical systems to be triply redundant. Life support modules to be replaceable at major Starbase layover to permit vehicle-wide adaptation to Class H, K or L environmental conditions.&lt;br /&gt;
*	Ability to support up to 200 non-crew personnel for mission related operations.&lt;br /&gt;
*	Facilities to support Class M environmental range in all individual living quarters, provisions for 2% of living quarters to be equipped to support Class H, K and L environmental conditions. Additional 1% of living quarters volume to be equipped for Class N and N (2) environmental adaptation.&lt;br /&gt;
*	All habitable volumes to be protected to SFRA-standard 347.3(a) levels for EM and radiation. Subspace flux differential to be maintained within 0.02 millicochranes.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Tactical&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Defensive Shielding to exceed 9.85 X 103 kW primary energy dissipation rate. All tactical Shielding to have full redundancy, with auxiliary system able to provide 75% of primary rating.&lt;br /&gt;
*	Tactical systems to include full array of Type XII phaser bank elements on hull capable of 6.1MW maximum single emitter output. 6 Photon Torpedo launchers required for ship defensive capabilities.&lt;br /&gt;
*	Tactical systems to include anti-detection components capable of defeating sensor and optical scan.&lt;br /&gt;
*	Tactical systems to include variable decreased emissions systems affecting primary and secondary drive systems.&lt;br /&gt;
*	Tactical systems to include components to reproduce or produce false sensor signatures at displaced coordinates in vessel reference.&lt;br /&gt;
*	Tactical systems to include components to produce ambient radiation and gravitational energies consistent with surrounding spatial occurrences.&lt;br /&gt;
*	Tactical systems to include variable EM field dampening systems to reduce or eliminate vessel EM fields and signatures.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Design Life&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Space frame design life of approximately 100 years, assuming approximately 5 major ship- wide system swap outs and upgrades at average intervals of 20 years. Such upgrades help ensure the continuing usefulness of the ship even though significant advances in technology are anticipated during that time. Minor refurbishment and upgrade to occur at approximately one- to five year intervals, depending on specific mission requirements and hardware availability.&lt;br /&gt;
&lt;br /&gt;
==2.0 General Overview==&lt;br /&gt;
&lt;br /&gt;
The Rosenanté class of Starship was originally categorized as an intelligence-gathering vessel. The Rosenanté class is only the second starship class created by Starfleet command to receive this designation. The other is the Spectre Class. While most starships may be adapted for many different mission types, the Rosenanté class starship is designed primarily to perform a single type of mission objective, in effect limiting her overall flexibility within a more generalized Starfleet. Seen from a comfortable distance of two or three kilometres, the starship takes on the resemblance of the more familiar Sovereign class explorers. Upon closer inspection however, one can see that the engineering hull is more sleek, lending a highly manoeuvrable appearance to the Rosenanté class of starship. The engineering hull actually extends both above and below the saucer section, lowering the overall silhouette of the class. Additionally, the saucer section itself boasts a number of changes that are easily noticed even by the most novice of observers. This divorce from standard Starfleet design protocols is both advantageous and disadvantageous for this class of starship. The unique hull design allows an immediate reduction in stresses generated by high warp speeds, while allowing greater manoeuvrability at sub-light speeds. This hull design concept has its drawbacks however, as high speed warp manoeuvrability is reduced in favour of speed. The exterior hull material is stronger, lighter and more durable than that used in standard starship production. This reduces the need for otherwise necessary supports and braces, leaving a greater interior volume for habitation. This material used on the ship&#039;s hull is more difficult to reproduce and repair, as specialized facilities must be implemented to perform these functions.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;2.1 Physical Arrangement&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-2up.jpg|right|300px]]&lt;br /&gt;
&lt;br /&gt;
The hull, remarkably birdlike in its strong, hollow construction, is reinforced against flight stresses by active energy fields that tighten and flex where required to compensate for natural and artificial internal and external forces. Structures integrated into the hull allow for a variety of necessary functions. &lt;br /&gt;
&lt;br /&gt;
The bridge consolidates the command positions for the rest of the starship, windows allow crewmembers needed vistas while in space, phaser arrays and photon torpedoes provide offence and defence against hostile forces, and a specialized communications system allows interaction with other worlds and their ships.&lt;br /&gt;
&lt;br /&gt;
Lifeboats allow for escape in dire emergencies, transporter emitters afford reliable near instant movement of crew and gear, navigational sensors and deflectors give the starship distant vision and a method for clearing obstacles, and powerful warp engines propel the starship at amazing speeds.&lt;br /&gt;
&lt;br /&gt;
The twenty-eight decks are internally divided among major load-bearing structures. A great many systems, especially the habitation sections are suspended within the open spaces, essentially &amp;quot;floating&amp;quot; on flexible ligaments to minimize mechanical, thermal, and conductive radiation shocks.&lt;br /&gt;
&lt;br /&gt;
The living areas of the starship have been designed for maximum comfort and safety while the crew is conducting a mission. Long-term studies of humanoid cultures have revealed that as each race embarked upon permanent occupation of space, large personal living spaces had to be established, especially on early sub-light missions. The Rosenanté class starship allows for some 120 square meters of living space per person, in addition to community space and areas allotted to purely working functions.&lt;br /&gt;
&lt;br /&gt;
==3.0 Spacecraft Structure==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.1 Main Skeletal Structure&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The primary space frame of the Rosenanté class starship is fabricated from an interlocking series of Terminium/Tritium microfilament truss frames. These members average l.05m² in cross section and are capable of bearing the same load as the standard Tritanium/Duranium truss averaging l.27m² in cross section used in standard starship construction. These truss frames are located an average of 20 meters across the ship&#039;s exterior, while the standard trusses would be located every 25 meters along a ships exterior. The tightening of the trusses allows the vessel to withstand greater stress imposed upon it by warp travel, while still producing a lighter space frame.&lt;br /&gt;
&lt;br /&gt;
As with other starship designs, larger numbers of these trusses are located integral to the main impulse engine sections, the warp nacelle pylons, docking interface latches, and along the centerline of the hull structure. Smaller Trusses averaging 0.35m² in cross section are located every five meters on average, and also provide internal supports within the deck and core structure of the spacecraft interior.&lt;br /&gt;
&lt;br /&gt;
A mechanical framework provides physical integrity to the vehicle while at rest. A parallel series of aluminum crystal foam stringers are phase transition bonded to the primary trusses, providing low frequency vibration attenuation across the main truss structure, as well as support for certain utility conduits.&lt;br /&gt;
&lt;br /&gt;
Also attached to these stringers are various conformal devices built into the hulls structure, including elements of the deflector shield grid, H.l.S.S. components, as well as subspace radio antennas, which are incorporated into the skin of the spacecraft.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.2 Secondary Framework&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mounted to the primary space frame is a secondary framework of micro-extruded Terminium trusses to which the inner hull of the structure is directly attached. The secondary framework is mounted by means of 3.2 cm diameter X 5.1 centimeter long semi rigid polydurinide support rods, permitting a limited amount of mechanical isolation from the primary space frame for purposes of strain relief, plus sound and vibration isolation. Secondary space frame segments are also separated from each other (although mechanically attached) to permit replacement of inner hull segments and associated utilities infrastructure during major Starbase layover.&lt;br /&gt;
&lt;br /&gt;
Structural integrity during powered flight is provided by a series of forcefields that reinforce the physical framework. This structural integrity field (SIP) is distributed through a network of molybdenum-jacketed wave-guides, which in turn distribute SIF energy into ceramic-polymer conductive elements throughout the space frame. Without the structural integrity field, the vehicle would be unable to withstand accelerations greater than 3l.4 m/s² without significant deformation, or greater than 49.18 m/s² without unrecoverable structural damage.&lt;br /&gt;
&lt;br /&gt;
Exterior hull substrate is joined to the primary load bearing trusses by means of 4.8-cm diameter electron-bonded duranium pins at 1.01-meter intervals. These pins are slip-fitted into an insulating AGP ceramic fiber jacket that provides thermal insulation between the space frame and the exterior hull. The pins, jacketing, and hull segments are gamma welded together.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.3 Hull Layers&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The exterior of the spacecraft consists of multiple layers, which afford structural and atmospheric integrity for the space frame, integral wave-guides and field conductive members for the structural Integrity Field (SIP) and H.I.S.S components, and pathways for other utilities (including deflector grids), as well as resistance to radiation and thermal energy.&lt;br /&gt;
The exterior shell substrate is composed of interlaced micro-foam duranium filaments. These filaments are gamma welded into a series of contiguous composite segments that are 4.7 cm thick and are typically 2 meters in width. The substrate segments are electron-bonded to three reinforcing layers of 1.2- cm biaxially stressed terranium fabric, which provide additional torsion strength.&lt;br /&gt;
&lt;br /&gt;
In areas immediately adjacent to major structural members, four layers of 2.3-cm fabric are used. The substrate layer is attached to major structural members by electron-bonded duranium fasteners at 2.5-cm intervals. The substrate segments are not intended to be replaceable, except by phase-transition bonding using a transporter assembly jig during major Starbase layovers.&lt;br /&gt;
Two 3.76-cm layers of low-density expanded ceramic-polyrner composites provide thermal insulation and secondary SIP and H.I.S.S. conductivity. These layers are separated by an 8.7-cm multiaxis triennium truss framework, which provides additional thermal insulation and a pass through for fixed utility conduits.&lt;br /&gt;
&lt;br /&gt;
A 4.2-cm layer of monocrystal beryllium silicate infused with somniferous polycarbonate whiskers provides radiation attenuation. This layer is networked with a series of 2.3-cm X 0.85-cm molybdenum-jacketed conduits. These conduits, which occur at 1.3-m intervals, serve as triphase wave-guides for the secondary structural integrity field. Conductive tritium rods penetrate the wave-guides at l0-cm intervals and transfer SIF energy into the ceramic-polymer conductive layer.&lt;br /&gt;
The outermost hull layer is composed of a 1.6-cm sheet of AGP ablative ceramic fabric chemically bonded onto a substrate of 0.15-cm triermium foil. This material is formed into segments approximately 3.7m² and is attached to the radiation attenuation layer by a series of duranium fasteners, which allows individual segments to be replaced as necessary. (Micrometeor erosion is kept to a minimum by the deflector system, but is sufficient to warrant replacement of 30% of the leading edge on the average of every 7.2 standard years.) Individual outer hull segments are machined to a tolerance of ±0.05-mm to allow for minimum drag through the interstellar medium. Joints between segments are manufactured to a tolerance of ±0.025-mm.&lt;br /&gt;
&lt;br /&gt;
Also incorporated into the outermost hull layer is a series of super conducting molybdenum-jacketed wave-guide conduits, which serve to absorb and disperse sensor emission energy that interacts with the hull. Segmented sections of this network serve as housings for the unique DECS components, responsible for producing the ship’s tactical deflector. Unlike a standard starship, there are no thermal regulating assemblies built into the skin of the starship. Instead this duty is regulated through a series of intercoolers and radiators housed inside the interior of the Bussard Collector Assembly.&lt;br /&gt;
&lt;br /&gt;
==4.0 Command Systems==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.1 The Bridge&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Bridge, located on Deck 1, provides primary operational control of the Rosenanté class starship. The bridge directly supervises all primary mission operations and coordinates all departmental activities. These activities are handled through the individual command consoles located in various positions on the bridge. These workstations are modular and can be interchanged, removed, or added as necessary to fulfill specialized mission requirements. At any one time there can be up to 12 workstations installed. The standard bridge design calls for 2 Science Stations, 1 Operations Station, 1 Flight Control Station, l Auxiliary Engineering Station, 1 Tactical station, 1 Communications/ H.I.S.S. station, 1 Internal Security Station, and 2 Command Stations, one each for the ship’s commander, and the First Officer.&lt;br /&gt;
Other facilities located on Deck 1 include Astrogation, the captain&#039;s ready room and head, the crew head, and a small mission briefing room.&lt;br /&gt;
Major connections to the bridge include a pair of Turbolift shafts, four electron-plasma power distribution wave-guide conduits; four environmental support plenum groups, nine primary and two back-up optical data network trunks, two replicator wave-guide conduits, and three service crawlways. As an interesting side note, a tertiary backup power distribution system consisting of hardwired nonreactive, conductive ceramic-polymer relays are also in place.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.2 Display Panels&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The display panels on the bridge and through out the ship are constructed and operated the same as those on any other Federation starship. The layouts and reactivity of the panels are augmented and display properties shown in a different manner. The coloration of the interaction displays is altered to create a different aesthetic affect, while also allowing a variant-programming matrix to be utilized. This new language utilizes advances in Holoprogramming to create three-dimensional matrix strings; this in turn allows a more efficient and quicker computer response time. Critical internal components of the display panels are mapped to the molecular level allowing a replication driven pro-holographic matrix damage control system to repair damaged components. The components necessary to facilitate this activity are collectively known as the &#039;&#039;&#039;Se&#039;&#039;&#039;lf-&#039;&#039;&#039;Re&#039;&#039;&#039;plicating &#039;&#039;&#039;Da&#039;&#039;&#039;mage &#039;&#039;&#039;C&#039;&#039;&#039;ontrol &#039;&#039;&#039;S&#039;&#039;&#039;ystem (&#039;&#039;&#039;SERDACS&#039;&#039;&#039;). The &#039;&#039;&#039;SERDACS&#039;&#039;&#039; components are present in all non-integrity dependant systems throughout the ship. &lt;br /&gt;
&lt;br /&gt;
In addition to the standard anchored display consoles located throughout the ship, a series of Holoemitters have been seeded throughout the vessel to allow ship&#039;s personnel to utilize a holographic interface to tie directly into the ships computer regardless of the location of the crewmember. These emitters also allow the EMH to be activated in any compartment in the ship, and also allow for the construction of holographic crewmembers to fill non-critical positions on the ship. These holoemitters are capable of creating non-electronic tools for emergency use, and in conjunction with replication systems could produce vital simplified component reproduction anywhere aboard ship.&lt;br /&gt;
&lt;br /&gt;
==4.3 Bridge Stations==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.1 Flight Control (CONN)&#039;&#039;&#039; &amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the actual piloting and navigation of the ship. From this station all SIF and IDF systems are monitored, as well as navigational deflectors, and their subsequent systems. This console performs the same functions as it would on board any other Federation starship.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.2 Operations Management (OPS)&#039;&#039;&#039; &amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for power maintenance and resource allocation. This console dictates priority status of all shipboard systems and operations. They coordinate activities between departments and between the ship and away missions. This console performs the same functions as it would on board any other Federation starship.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.3 Tactical Operations (TACOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the operation, monitoring and maintenance of the ship&#039;s tactical systems. These systems include the phaser arrays, the photon torpedo deployment systems, probe	deployment systems, H.I.S.S. system, Signal displacement system, tractor beams, and Tactical deflector systems. The Tactical station aboard the Rosenanté class starship differs from those of standard Federation starships. The main difference is the divorce of the ship&#039;s tactical systems from the internal security systems of the ship. This allows the tactical officer the ability to concentrate on the tactical aspects of the ship without the need to also monitor the internal security status of the ship. Another major difference in the Rosenanté class starship is the addition of a sensor array specifically for use by the tactical officer.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.4 Security Operations (SECOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the monitoring and operation of internal ship security systems. The Operator of this console is responsible for the deployment of ship&#039;s security personnel aboard the ship. This console controls the internal security containment fields, internal ship&#039;s sensors. The SECOPS officer can monitor the security status, security systems and personnel deployment for the entire ship. They can control door mechanisms, containment fields, the turbolift car, and weapons settings of all Federation weaponry on the ship. In addition, security can control personnel access to restricted areas, and utilize sight-to-sight onboard transporters.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.5 Communications (COMMOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the encryption and decryption of intercepted communications, for the transmission of communications, maintaining the Emissions Control Protocols, and the operation of specialized communications interception equipment. The Communications officer is often called upon to triangulate communications sources, decipher enemy transmissions, and encrypt outgoing communications. They often assist in Traffic Analysis of enemy troop deployment, and maintain secure communications with away teams.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.6 Science Stations I &amp;amp; II&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
These consoles are responsible for data collections, primary and lateral sensor operations, and database referencing. It is the responsibility of the science officer to operate the ship&#039;s sensors, teleoptical systems, and imaging systems. They observe, record and document data important to shipboard mission objectives. These stations can be utilized together or separately. This station also acts as the primary database access terminal for the Federation database carried aboard all Federation starships. Both passive and active sensors are controlled from this station.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.7 Auxiliary Engineering Station&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This station is responsible for maintaining and monitoring shipboard systems. This console works in conjunction with main engineering, and is capable of performing the same functions as the computer in that section of the ship. From this station the warp fields can be tuned, altered or monitored, as can all primary and secondary shipboard systems. This station is not always manned.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.8 Command Stations I &amp;amp; II&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
These consoles are responsible for the maintenance and monitoring of the ship&#039;s computer and all primary and secondary systems. Only the commanding and executive officer have access to these consoles. From these consoles the commanding officers can display data concerning ship&#039;s systems, status, condition, position, speed, heading, and power management distribution. These consoles can access the database, and has priority authority over all computer functions. These consoles are the only terminals capable of activating the ship&#039;s self-destruct mechanism. Any officer in command of the starship may utilize these consoles, although some functions may be unavailable.&lt;br /&gt;
&lt;br /&gt;
==5.0 The Computer System==&lt;br /&gt;
The computer system aboard the Rosenanté class starship is identical in construction to the computers used on other Federation Starships. They utilize the same back up and failsafe hardware and communicate through the same methods as the standard starship computer. The computer system of the Rosenanté class starship is composed of 2 synchronized computer cores, identical to those used in the Galaxy Class starship. The only differences between the standard Federation computers and those aboard the Rosenanté are the storage medium and programming language that the system uses to communicate.&lt;br /&gt;
The storage of data and processing networks of a standard Federation computer system depend upon isolinear chips. On the Rosenanté a new type of data storage chip, the Hololinear chip is introduced. Taking advantage of new replication and holographic programming breakthroughs, the new Hololinear chips, or HL chips, allow data to be stored in a four-dimensional, subspace format. A new programming language known a &#039;&#039;&#039;B&#039;&#039;&#039;ilinear &#039;&#039;&#039;U&#039;&#039;&#039;nilateral &#039;&#039;&#039;N&#039;&#039;&#039;etworking &#039;&#039;&#039;C&#039;&#039;&#039;ode (&#039;&#039;&#039;BUNC&#039;&#039;&#039;) allows data to be stored in a temprometric tagged holographic string, thereby allowing data to be stacked almost exponentially upon other data, linked by temprometric strings of associated data. Retrieval time is decreased as the data can be read from any point along its data string, rather than starting at a specified point as is required by the standard isolinear chip design.&lt;br /&gt;
&lt;br /&gt;
==6.0 Warp Propulsion Systems==&lt;br /&gt;
The Warp propulsion system in the Rosenanté class starship is radically different from Those used in other starships. The majority of the system is developed to utilize existing warp technology and materials. There is however a few major changes in the system. All warp engineers are familiar with the laws of warp transition, which dictates that warp geometry and power requirements dictate a vessel&#039;s ability to achieve various levels of warp speed. This same law also dictates that a warp field must be balanced in order to achieve maximum efficiency to make a warp transition.&lt;br /&gt;
&lt;br /&gt;
The Graph below represents the transition energy requirements for the Galaxy Class Starship design and also for that of the Rosenanté class starship.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:RWC.jpg|thumb|center|800px|Warp transition chart]]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
ln the chart above the Cochrane values are represented over the white bar for the Rosenanté Class starship. At lower warps (below Warp 6) there is an actual decrease in warp efficiency, although at higher warp there is a worthwhile increase in efficiency, where the differences in efficiency matter most. It is important to note that a Galaxy class starship is incapable of traveling at Warp 9.97, and thus the numbers represented for that class is theoretical.&lt;br /&gt;
&lt;br /&gt;
The ability to sustain warp 9.97 is a result of multiple warp engines working in synchronization and a natural by-product of the embedded nacelle design. The synchronization of the dual warp drive is accomplished through the use of a &#039;&#039;&#039;W&#039;&#039;&#039;arp &#039;&#039;&#039;E&#039;&#039;&#039;nergy &#039;&#039;&#039;Sy&#039;&#039;&#039;nchronization &#039;&#039;&#039;R&#039;&#039;&#039;outer, or &#039;&#039;&#039;WESYR&#039;&#039;&#039;. The &#039;&#039;&#039;WESYR&#039;&#039;&#039; unit is highly classified, but its basic function is to synchronize otherwise out of synch Waveforms created within two near identical meshed Tuned Plasma Streams. Because of the additional energy that this system produces, a higher capacity EPS Power Tap and Series Relays were developed to handle the additional power loads. A dual bypass system allows any single Warp drive to power ships functions, at a significant reduction in overall power. Also a major redesign feature of the upgraded power system resulted in the addition of a second Port and Starboard Power conduit assembly and relay subassembly. This allows the power delivery system to function more efficiently.&lt;br /&gt;
&lt;br /&gt;
Interestingly enough, a bizarre natural byproduct of running a dual synchronized Warp Field is the creation of a &amp;quot;double&amp;quot; warp bubble. These warp bubbles are divided by 2.3-mnm (micronanometers) and help produce the effect of the change of reduction caused when making Warp Transitions. As subspace resistance passes through the Outer shield it is reduced as normal, then again as the remaining resistance passes through the inner bubble, it is further reduced. This causes the starship to experience less resistance and shearing warp stress associated with high rate warp travel and maneuvering.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Spiral Warp Drive&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In addition to the standard warp drive used by all federation starships, the Rosenanté class is also equipped with an experimental Spiral Warp Drive. This drive creates a subspace &amp;quot;tunnel&amp;quot; or &amp;quot;wormhole&amp;quot;  through which the Rosenanté may then travel. The tunnel integrity is maintained by the main deflector dish. The tunnel basically allows the ship to drop into subspace, effectively disappearing from normal space for a short period of time. The speeds that are achieved through the use of this drive are akin to those used by the Borg when using transwarp conduits. Unlike transwarp conduits, however,the tunnel being opened by the Rosenanté would dissipate as soon as the ship moves through it. In a similar manner, the spiral drive can only be used to travel in straight lines. This means that the vessel may make a periodic series of short hops to correct course when using this system.&lt;br /&gt;
&lt;br /&gt;
==7.0 Deflector Emitter Cluster System (DECS) ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-3up.jpg|thumb|left|500px|]]&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;D&#039;&#039;&#039;eflector &#039;&#039;&#039;E&#039;&#039;&#039;mitter &#039;&#039;&#039;C&#039;&#039;&#039;luster &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;DECS&#039;&#039;&#039;, represents the newest Federation breakthroughs in Federation tactical shield technology. This innovative new system utilizes a convex “honeycombed&amp;quot; arrangement of octagonal emitters offset slightly to produce a unified, overlapping tactical field. This primary tactical system allows a tighter tactical shield to be produced, thus resulting in a lessened tactical shield cross section, which in turn reduces starship detectability.&lt;br /&gt;
&lt;br /&gt;
Whereas the Rosenanté class of starship possesses the standard &#039;&#039;&#039;D&#039;&#039;&#039;eflector &#039;&#039;&#039;E&#039;&#039;&#039;mitter &#039;&#039;&#039;A&#039;&#039;&#039;rray (&#039;&#039;&#039;DEA&#039;&#039;&#039;) that all Federation starships do, they use that particular system as a primary shielding system. The &#039;&#039;&#039;DECS&#039;&#039;&#039; assembly operates by producing several smaller polyhedral segments of shield interdependability, rather than creating a &amp;quot;shell&amp;quot; segment standard to all other Federation starships. The &#039;&#039;&#039;DECS&#039;&#039;&#039; requires more power than standard tactical &#039;&#039;&#039;DEA&#039;&#039;&#039; systems, but yields a 20% increase in shield output. The &#039;&#039;&#039;DECS&#039;&#039;&#039; is calibrated to respond and recalibrate the loss of a single emitter or emitter cluster, resulting in a greater overall performance and defensive capability of ship systems. The standard &#039;&#039;&#039;DECS&#039;&#039;&#039; system is installed to provide tactical shielding whenever the starship is experiencing &#039;&#039;&#039;DEA&#039;&#039;&#039; failure, or power requirements do not allow the use of the &#039;&#039;&#039;DEA&#039;&#039;&#039;. Another advantage of the DECS over the standard DEA is its modular design. It is quick and efficient to repair or replace in the field whereas the replacement of the DEA system requires a major overhaul at a Starbase.&lt;br /&gt;
&lt;br /&gt;
==8.0 Hull Integrated Stealth System. ==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;H&#039;&#039;&#039;ull &#039;&#039;&#039;I&#039;&#039;&#039;ntegrated &#039;&#039;&#039;S&#039;&#039;&#039;tealth &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;HISS&#039;&#039;&#039;, is a series of alterations to the ships exterior hull and systems to create a reduced sensor and visual silhouette. The details of the &#039;&#039;&#039;HISS&#039;&#039;&#039; are highly classified, although the general concepts behind its incorporation are not. A network of specialized integrated hull webbing allows the hull to emit energies that effectively allow light waves to pass through it and its contents. In addition to visual bands of radiation, the specially designed ablative hull absorbs sensor energy, while emitting the same energy signature as the starship&#039;s surrounding space. Thus, the vessel becomes virtually undetectable either through detection or complete omission of detection. In addition to this, specialized hull features act as complex Magnetic field disruptors, reducing the EM field of the vessel, and also neutralize radioactive emissions through a complex series of intercoolers and sheathed cowlings. The ship&#039;s Impulse, Thruster and Bussard collection systems are incorporated to nearly negate all detectable signs of their use. When the HISS is active and used in conjunction with strict Emissions protocols, the ship vanishes from visual and sensor detection.&lt;br /&gt;
&lt;br /&gt;
==9.0 Advanced Sensors Systems==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;I&#039;&#039;&#039;mproved &#039;&#039;&#039;S&#039;&#039;&#039;ensor &#039;&#039;&#039;I&#039;&#039;&#039;ntegrated &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;ISIS&#039;&#039;&#039;, is a modified high yield Federation sensor array. The &#039;&#039;&#039;ISIS&#039;&#039;&#039; utilizes the newest development in sensor technology to quantum phase the active and passive ship&#039;s sensors to greatly reduce detectability. These new sensors are more powerful, and almost impossible to detect without performing extensive and time consuming alterations to a starship&#039;s sensor array, which then is useless to detecting other aspects of its surrounding. Some of this technology is loosely based on cloaking principles.&lt;br /&gt;
&lt;br /&gt;
==10.0 Sensor Displacement System==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Se&#039;&#039;&#039;nsor &#039;&#039;&#039;Di&#039;&#039;&#039;splacement &#039;&#039;&#039;S&#039;&#039;&#039;ystem, Or &#039;&#039;&#039;SEDIS&#039;&#039;&#039;, allows the Rosenanté class of starship to offset its actual energy signature, and even produce an additional energy signature. This is designed to improve the starships ability to prevent &amp;quot;true&amp;quot; detection, or to act as a decoy system in the event that the starship is detected. This system is capable of operating within a 60OKm range of the vessel.&lt;br /&gt;
&lt;br /&gt;
==11.0 Displaced Communications System==&lt;br /&gt;
The &#039;&#039;&#039;Di&#039;&#039;&#039;splaced &#039;&#039;&#039;Comm&#039;&#039;&#039;unications &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;DICOMMS&#039;&#039;&#039;, is based on the same technology as the &#039;&#039;&#039;ISIS&#039;&#039;&#039;. This energy is used to send nearly undetectable communications. The Rosenanté class starship is equipped with standard Federation communications systems as well.&lt;br /&gt;
&lt;br /&gt;
==12.0 Interior Systems Modifications==&lt;br /&gt;
There have been a variety of interior alterations to the interior, habitable areas of the Rosenanté class starship. The most apparent alterations are in the functionality of the corridor and turbolift systems. The oversized personnel quarters offer the most luxurious and spacious accommodations aboard any Starfleet posting, while unique interaction software insures crewmembers peace of mind.&lt;br /&gt;
&lt;br /&gt;
Many Starfleet admirals believe that the Tactical and Scientific Equipment carried by a Starship to be the most important asset to any Starfleet facility or starship. The designers of the Rosenanté class of Starship also felt that crew morale would also serve a very integral role in the operation of the starship. To these ends the interactive systems and habitations were designed to provide a reassuring and relaxing environment for the ships crew.&lt;br /&gt;
&lt;br /&gt;
==12.1 Safety Systems==&lt;br /&gt;
The most paramount function of any Starship is the maintenance of its crew in adverse conditions. Integral to this school of thought is the ability to protect the crew under hostile threats. To these ends, the designers of the Rosenanté class starship developed a series of counterinsurgency systems to minimize crew contact with alien forces boarding the vessel.&lt;br /&gt;
&lt;br /&gt;
==12.1.1 Isolation Field Systems==&lt;br /&gt;
The &#039;&#039;&#039;I&#039;&#039;&#039;solation &#039;&#039;&#039;F&#039;&#039;&#039;ield &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;IFS&#039;&#039;&#039;, was designed with the intent to isolate hostile alien forces that boarded the vessel for the crew. This function is considered vitally important when consideration is given to the fact that the Rosenanté class starship possesses a very highly trained crew. The &#039;&#039;&#039;IFS&#039;&#039;&#039; fundamentally isolates the threat through the use of perpetual containment fields, reinforced by miniature shield defenses for the IFS emitter assembly. The &#039;&#039;&#039;IFS&#039;&#039;&#039; is always active, limiting the mobility of non-authorized personnel, securing sensitive sectors of the ship, and effectively hindering the process of any hostile aliens that may manage to board the vessel. The ship&#039;s computer monitors the movements of every official member of the ship&#039;s crew at all times. In this manner, the computer is able to activate or deactivate the &#039;&#039;&#039;IFS&#039;&#039;&#039; screens on an individual basis as needed. This allows authorized crewmembers access to shipboard systems and compartments as needed. The &#039;&#039;&#039;IFS&#039;&#039;&#039; consists of a series of Level 8 containment fields spaced an even 12.5-meters along the corridors of the vessel. In addition to these, an &#039;&#039;&#039;IFS&#039;&#039;&#039; field also isolates each access portal and hatch. In the event that a commbadge should be captured, or fail, that badge is automatically removed from all access rosters, until security can investigate the occurrence.&lt;br /&gt;
&lt;br /&gt;
As a benefit of the perpetually active IFIS fields, studies indicate that shipboard damage caused by fire and/or decompression was drastically reduced. The fields prevented large area decompression, and also limited the range of fire dispersion radically.&lt;br /&gt;
&lt;br /&gt;
Although in larger compartments the &#039;&#039;&#039;IFS&#039;&#039;&#039; system is not perpetual; all compartments are equipped with the capacity to further &amp;quot;compartmentalize&amp;quot; these large open areas. The computer is capable of assessing threats to the crew and equipment of the vessel, and can respond using the &#039;&#039;&#039;IFS&#039;&#039;&#039; system, nearly instantly. The &#039;&#039;&#039;IFS&#039;&#039;&#039; system was designed to operate independently of the ships main power supply when necessary. Each &#039;&#039;&#039;IFS&#039;&#039;&#039; emitter and processor assembly is equipped with an independent high-yield Sodium Kelleride power system. This power cell is further treated with a Potassium Unified catalyst. This allows the production of oxygen as a by-product whenever the secondary power system is operated. This allows a crewmember to be compartmentalized in an otherwise decompressed area to survive asphyxiation and loss of pressure. This secondary power system will allow the full yield operation of the &#039;&#039;&#039;IFS&#039;&#039;&#039; emitter in question for a period of 4 standard hours. Setting the emitter to a lower containment setting can extend this time.&lt;br /&gt;
&lt;br /&gt;
==12.1.2 Fire Suppression Systems==&lt;br /&gt;
&lt;br /&gt;
Although the &#039;&#039;&#039;IFS&#039;&#039;&#039; system hinders the progress of a shipboard fire, it will not necessarily extinguish it. To facilitate this a hybrid field emitter, environmental suppression system was developed. This system isolates the flame from its fuel source using advanced forcefield emissions systems, while simultaneously adjusting the environment around the fire to assist in its suppression. A functional &#039;&#039;&#039;IFS&#039;&#039;&#039; contained area further supports the adjustments, as a smaller area of the ship need be adjusted at any one time. There are certain types of plasma fires that could be unaffected by environmental conditions and or can not be contained in this manner. It is in those situations that the fire suppression systems remove the fire and all affected material through use of the ships sight-to-sight transporters. If this cannot be performed due to a greater risk being imposed on the crew, more conventional methods of fire suppression must be performed.&lt;br /&gt;
&lt;br /&gt;
==12.1.3 Internal Ballistics Dampening Fields==&lt;br /&gt;
In key areas where materials stored aboard ship have the potential to be propelled through sections of the ship, a series of &#039;&#039;&#039;I&#039;&#039;&#039;nternal &#039;&#039;&#039;Ba&#039;&#039;&#039;llistics &#039;&#039;&#039;D&#039;&#039;&#039;ampening Fields, or &#039;&#039;&#039;I-BAD&#039;&#039;&#039; Fields, have been implemented. These fields are found primarily in the armory, cargo bays, Shuttle Bays, storage bays, and personnel quarters. The &#039;&#039;&#039;I-BAD&#039;&#039;&#039; system uses advanced internal sensing equipment specialized to calculate mass and velocity of non-anchored materials. In the event that these materials should be propelled at a speed that the computer should indicate hazardous to crew, then a series of inertial Dampening Fields are erected to reduce the velocity of the offending object. The IDF relays cannot stop a propelled item, although it can shorten its travel distance and relative speed considerably. The sensing systems ignore the movements of personnel. The &#039;&#039;&#039;I-BAD&#039;&#039;&#039; emitters in no way affect the reduction of stresses upon the vessel caused by acceleration, deceleration, or maneuvering.&lt;br /&gt;
&lt;br /&gt;
==12.1.4 Advanced Ergonomics==&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-4up.jpg|thumb|right|500px|]]&lt;br /&gt;
&lt;br /&gt;
Throughout the vessel, specialized memory seating systems have been implemented. These systems monitor the stresses upon the body of the crewmember presently utilizing them and adjust the contact points with the crewmember to minimize physical stresses. All station seating and this material affects standard seating in personnel quarters. The design is such that is can self adjust to allow for non-humanoid crewmembers. The standard bedding and medical bio beds are also adjusted in this manner. This has proven to reduce fatigue and discomfort resulting from prolonged duty shifts. The conceptualization of advanced ergonomic design is further implemented in the layouts and design of the personnel quarters on the ship. Each individual’s quarters are ergonomically designed to his or her unique specifications. The height and shape of interactive systems, the design of the shelving and storage facilities, and the layout of the waste management system are all adjusted to the unique requirements of the compartment owner. Even habitation shape and colour are carefully implemented to create an environment in harmony with its occupant.&lt;br /&gt;
&lt;br /&gt;
==12.1.5 Tactical Sight-to-Sight Transport==&lt;br /&gt;
The ship&#039;s computer possesses the ability to assess tactical breaches in to the vessel&#039;s security. When appropriate, the computer may implement tactical redistribution of security personnel to facilitate the disarmament of tactical threats. The computer determines the size of any aggressive and/or threatening force on the ship, and then determines logical methods of containing and overcoming this threat. The computer is capable of briefing shipboard security personnel on the state of a threat, operating IFIS units, and evacuating non-essential personnel from potential or actual combat areas. The computer can deploy security personnel using sight-to-sight transporters and tactical deployment subroutines. In addition to automatic response to internal tactical threats, the ship&#039;s computer can suggest tactical deployment options for security personnel, utilizing data stored in its memory. This tactical deployment data is only suggested when asked for, and is prepared for planetoid deployment, boarding actions, counter-boarding actions, and sight security. When a medical situation presents itself the same sight-to-sight transporter system can be utilized to transport critical patients to the sickbay.&lt;br /&gt;
&lt;br /&gt;
==12.1.6 Emergency Medical Hologram==&lt;br /&gt;
The Emergency Medical Hologram, as standard to all Federation starships, is also present on the Rosenanté class starship. A series of modifications allows the EMH system to be activated in any habitable portion of the vessel. This function is performed by a series of specialized emitters seeded throughout the ship. Each emitter is equipped with an array of medical scanners and programmed with trauma and first aid protocols. Each emitter assembly is capable of independent operation in the event that power systems become unavailable. The Sodium Kelleride power source can maintain EMH use for 1 hour before expending its charge. When operating normally, the EMH can access the ship&#039;s medical database. When operating independently, only the trauma and first aid subroutines may be accessed. While operating on ship&#039;s systems no more than three EMH programs may be running at any one time. Independent operation is possible among any number of EMH emitters.&lt;br /&gt;
&lt;br /&gt;
==12.1.7 Emergency Replication System==&lt;br /&gt;
The &#039;&#039;&#039;E&#039;&#039;&#039;mergency &#039;&#039;&#039;R&#039;&#039;&#039;eplication &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;ERS&#039;&#039;&#039;, is a series of secondary replicators that operate completely independent of the ships systems. The &#039;&#039;&#039;ERS&#039;&#039;&#039; units are located aft and fore of the starship, two per deck. They are always inert until activated. The &#039;&#039;&#039;ERS&#039;&#039;&#039; system is &amp;quot;hidden&amp;quot; behind corridor paneling, and consists of a single equipment replicator, a single food replicator, an atmospheric condenser, a single medical tricorder, a standard tricorder, and a pair of Class I Phasers. A high-yield Sodium Kelleride Battery that allows light use of the replicators, for a period of 3 days, powers the &#039;&#039;&#039;ERS&#039;&#039;&#039; units. The Tricorders and Phasers are pre-powered, and can be recharged once, using the supplied connections. Accessing the ERS panel will alert security. The Class I phasers require a personal authorization code to be activated. The computer monitors the &#039;&#039;&#039;ERS&#039;&#039;&#039; system very closely, immediately notifying engineering if a problem is detected.&lt;br /&gt;
Although the &#039;&#039;&#039;ERS&#039;&#039;&#039; is a fully functional Replication system, it is programmed to create materials that require very little energy to reproduce. Thus, the food replicators produce only a single nutrient rich disk for consumption. The Tool replicator is limited to equipment that possesses simple physical structures, such as hand tools and only simple electronics materials. Neither replicator system can reproduce power sources, or advanced electronics.&lt;br /&gt;
&lt;br /&gt;
==12.1.8 Emergency Transporters==&lt;br /&gt;
The Rosenanté class starship is equipped with 2 emergency transporters. These transporters are located centrally along the berth and length of the vessel on decks 5 and 15. The emergency transporters are integrated into the primary corridor on the aforementioned decks. All transporter hardware is stowed in the surrounding corridor structures. 20 high-yield Sodium Kelleride Batteries independently power the control operation panel and the emergency transport systems. Each Emergency transporter is also equipped with its own short-range sensor array, for destination determination. The control panel is &amp;quot;hidden&amp;quot; behind the corridor paneling, and floor paneling hides the transporter pad. In order to operate the transporter this floor paneling must be removed. The emergency transporters are each capable of transporting 60 personnel.&lt;br /&gt;
After that there is no power remaining to continue transporter functions. Preparing the Emergency transporters for use alerts security.&lt;br /&gt;
&lt;br /&gt;
==12.2 Medical Bay==&lt;br /&gt;
Due to the number of personnel stationed aboard the Rosenanté class starship, the standard&lt;br /&gt;
Medical Bay arrangement was not utilized. Instead a specialized medical bay was designed to maximize space, while still attending to the variable needs of the ship&#039;s crew. To this end, the sickbay possesses a complete quarantine ward, a single surgical ward, and the central sickbay. A office allows for the CMO to perform administrative tasks without interruption.&lt;br /&gt;
In the surgical area, all the equipment necessary to perform any level of surgery is present. Specialized negative pressure systems allow operations to continue upon contaminated personnel without worry of integrity loss.&lt;br /&gt;
The central medical area is equipped with the newest and most efficient systems that general practice has to offer. A multitude of sensors and medical dedicated processors facilitate medical data gathering, while advanced holographic modeling systems allow hands-off data model construction. Forty Biobeds are located in the Sickbay, which studies indicate was the most efficient number of patients to treat at one time. &lt;br /&gt;
&lt;br /&gt;
In addition to the standard biobeds and Infirmary treatment bay, There are also two dedicated Medical Laboratories, One General Practice Clinical Ward and Three configurable Bays, which can be changed to meet the specific requirements of the medical needs of the vessel.&lt;br /&gt;
&lt;br /&gt;
The Quarantine area is equipped with a series of Biocide units capable of detecting, isolating and destroying over three hundred billion contagions. Negative pressure atmospheric systems, ionic decontamination systems, and bio-phased containment fields guarantee the isolation of harmful contagions. All containment systems in the sickbay are maintained by secondary and tertiary power systems. A medical dedicated replication system allows the creation of any replicable pharmaceutical known to Starfleet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&amp;lt;small&amp;gt;All images compliments of Roger Wackowski&amp;lt;br&amp;gt;Spiral Drive concepts by Anthony Keen&amp;lt;br&amp;gt;All other technical aspects, created, written and designed by Daniel Greene&amp;lt;/small&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
[[Category: Engineering]][[Category: Database]][[Category: Active Ships]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=The_Chimera_Directive&amp;diff=55390</id>
		<title>The Chimera Directive</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=The_Chimera_Directive&amp;diff=55390"/>
		<updated>2012-05-09T16:22:47Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* 6.0 Warp Propulsion Systems */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;  &lt;br /&gt;
  &lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
== 1.0	CHIMERA DIRECTIVE INTRODUCTION ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-1up.jpg|thumb|500px|The Rosenante Class Starship]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1.1 MISSION OBJECTIVES FOR ROSENANTÉ CLASS PROJECT&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Starfleet has long been charged with a broad spectrum of responsibilities to the citizens of the Federation and to the lifeforms of the Galaxy at large. As the volume of explored space continues to grow, and with it the Federation itself, so do Starfleet&#039;s duties. &lt;br /&gt;
&lt;br /&gt;
These duties range from relatively mundane domestic and civil missions, to cultural contact and diplomacy, to defense, to our primary mission of exploration and research. Many of these responsibilities are best carried out with relatively small, specialized ships. Yet there continues to be an ongoing need for an even narrower role vessel to protect the Federation against enemies that would use espionage and subversion to wage war against the Federation.&lt;br /&gt;
&lt;br /&gt;
This particular threat to Federation security is further complicated by political and economic restraints placed upon the Federation caused by the demands of maintaining an active war first against the Cardassian Union and then a Civil War between Doenitz Loyalists and 52nd Fleet seditionists. The Federation had suddenly found itself pressed on many fronts at various levels of engagement, often ill-prepared or incapable of information gathering against potential interior and exterior threats to the continued existence of the Federation.&lt;br /&gt;
&lt;br /&gt;
In response to the alarming number of intelligence related activities conducted against Federation projects, personnel, and equipment by exterior Intelligence Organizations, such as the Tal Shiar, the Dominion Shapeshifters, and The Cardassian Obsidian Order, Starfleet Intelligence has found itself grossly outnumbered, and under-appreciated by Starfleet Command. This lack of interdepartmental cooperation was only strengthened by Starfleet Intelligence&#039;s inability to detect and detain several pro-Revolutionary agents that had managed to infiltrate Starfleet Command, the Council of the President, and several other critical posts within the governmental structure of the Federation. The agents proved to be the first signs of the coming Civil war that would shake the foundations of the United Federation of Planets over the next several years.&lt;br /&gt;
&lt;br /&gt;
These breeches of critical security protocol within the government provided the critics of Starfleet Intelligence with ammunition to pressure Starfleet Command to tighten its control on the Intelligence Department. In late 2390s, with the Cardassian Union pressing their offensive against the Federation, Starfleet Intelligence learned of other threats to the Federation&#039;s continuing existence, as reports began to come into Starfleet Intelligence&#039;s Romulan desk reporting a large number of Romulan Infiltrators had somehow managed to concentrate themselves on the Federation Starships patrolling the Neutral Zone. With reports indicating that the Tal Shiar compromised a large majority of Starships patrolling the Neutral Zone, and with SFI fearing a Romulan Invasion, a massive counter Intelligence operation began. This operation, dubbed Sword and Shield, inserted several dozen Starfleet counterintelligence Specialists onboard the suspected Starships. For the better part of a year, these operatives played a deadly game of cloak and dagger against the expectant Tal Shiar operatives. This massive undertaking resulted in the largest capture of external espionage operatives in Starfleet history, 38 Starfleet officers (including 2 Ship Captains) and 12 Enlisted Starfleet personnel were arrested and charged with espionage against the Federation. 6 Starfleet Intelligence operatives lost their lives in this operation. &lt;br /&gt;
&lt;br /&gt;
It was to this threat that Admiral Rodrigo Doenitz would propose a solution. That solution came in the form of a Starship, dedicated completely to the tasks of espionage and interdiction operations. The vessel would be operated entirely independently of Starfleet command. Only Starfleet Intelligence would have any command authority over the vessel and its missions. This proposal created a scandalous outcry by Starfleet Command Officers, with the end result becoming less than favorable to the Doenitz cause.&lt;br /&gt;
&lt;br /&gt;
However, the dramatic success of Sword and Shield eased the tension against Starfleet Intelligence, and by the end of the War with the Cardassian Union in 2398; Starfleet Command realized the inability of SFI to conduct operations in hostile space, or to operate independently without the immediate assistance of Starship under Starfleet Command authority. It was in August of that year that Admiral Talbot, with the support of Admiral Doenitz proposed the idea of creating a new class of Starship capable of supporting Intelligence operations in hostile space, while simultaneously capable of performing signal, traffic and visual surveillance of facilities, ship movements and communications. Admiral Talbot argued that if SFI were equipped with such a vessel during the War, that the effectiveness of the Cardassian attack against the UFP would have been greatly reduced, if not altogether neutralized. Additionally, Talbot argued, such a ship working in Romulan space would have been priceless in determining the intentions and movements of the Tal Shiar during Operation Sword and Shield.&lt;br /&gt;
&lt;br /&gt;
Admiral Talbot’s conceptual Starship was deemed impossible to build, and also in violation of Starfleet Intelligence Command’s charter and the project was immediately disapproved. But that was not the end of the situation. &lt;br /&gt;
&lt;br /&gt;
Admiral Talbot, through secret channels with the complete support of Admiral Rodrigo Doenitz established a secret construction facility. Through various nefarious means, funds were funneled into the project and experienced Starfleet ship engineers were tasked to assist in developing a new class of Starship that could function efficiently within the confines established by the joint visions held by the two admirals.&lt;br /&gt;
&lt;br /&gt;
A special Starfleet Intelligence Operation was begun in a secret shipyard facility around early 2397. SFI operatives assigned to the operation interviewed and recruited Starship designers from across the Federation, purposely avoiding any designer that had ever worked on a Starship Project for the Federation in the past. These designers, assisted by the technical and personal experiences, of selected Starship Engineers laid down the design parameters for the project.&lt;br /&gt;
&lt;br /&gt;
After Admiral Doenitz’s successful coup, the project would prove to outlive many of its critics. With the full power of the office of the president of the Federation, Doenitz fast tracked his project making it an official Presidential Directive. This Directive was codenamed the Chimera Directive.&lt;br /&gt;
&lt;br /&gt;
The Rosenanté Class Starship designed by the Chimera Directive represents the most advanced design and systems innovations in the Federation. The basic design concept was developed around the Sovereign class and is considered the most advanced evolution of Starfleet Ship design to date.&lt;br /&gt;
&lt;br /&gt;
==Design Objectives==&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;&#039;&#039;Pursuant to Starfleet Intelligence Directive 1045.35, the following objectives have been established for the Rosenanté Class Starship development project:&#039;&#039;&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*	Provide a mobile platform for a wide range of ongoing intelligence and counterintelligence projects.&lt;br /&gt;
*	Provide autonomous capability for full execution of Starfleet Intelligence policy and directive options in hostile areas of space.&lt;br /&gt;
*	Incorporate recent advances in technology and protocols.&lt;br /&gt;
&lt;br /&gt;
To provide for these objectives, the Designers recommended that the Rosenanté class starship meets or exceeds the design goals in the following specification Categories;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Propulsion&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Sustainable cruise Velocity of Warp Factor 9.4. Ability to maintain speeds of up to Warp Factor 9.7 for periods of up to 12 Hours.&lt;br /&gt;
*	Sixth-phase dilithium controlled matter/antimatter reactor for primary power. Sustainable field output to exceed 1, 650 cochranes, peak transitional surge reserve to exceed 4,225% of nominal output. (170ns phase)&lt;br /&gt;
*	Warp Driver coils efficiency to meet or exceed 98% at speeds up to Warp 8.0. Minimum efficiency of 68% to be maintained through Warp 9.4. Life cycle of all primary coil elements to meet or exceed 1,200,000 cochrane-hours between neutron purge refurbishment. Secondary coil elements to meet or exceed 2,000,000 cochrane-hours between neutron purge refurbishment.&lt;br /&gt;
*	Warp field geometry to incorporate modified 85° Z-axis compression characteristics on forward warp lobe for increased peak transitional efficiency at high warp. Warp Nacelle centerlines to conform to 2.56: 1.1 ratio of separation to maximize field strength.&lt;br /&gt;
*	Secondary (impulse) propulsion systems to provide sub-light velocities up to and including .92 light speed (c). Engine systems of choice to include but not limited to at least two YPS 8063 fusion drive motors. All units to be equipped with subspace drive accelerators, field output not less than 180 millicochranes at 1.02 X l0³K. Reactor Modules to be field replaceable.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Mission&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Ability to operate independent of Starbase refurbishment for moderate periods of time. Independent operation mode capability of 1 Standard years at nominal Warp 6. Ability to execute deep-space exploration missions including charting and mapping, hostile contact scenarios, intelligence gathering and infiltration missions, full technical, biological and ecological studies.&lt;br /&gt;
*	Ability to support a wide range of mission-related ongoing research and other projects without impact on primary mission operations.&lt;br /&gt;
*	&#039;Full Spectrum EM, optical, subspace flux, Gravimetric, particle, and quark population analysis sensor capability. Multimode neutrino interferometery instrumentation. Wide band life sciences analysis capability. 2 twelve-meter interphasic field focused telescopes.&lt;br /&gt;
*	Upgradeable experiment and sensor array design. Ability to support on-board and probe mounted science and intelligence instrumentation.&lt;br /&gt;
*	Support facilities for auxiliary spacecraft and instrumented probes for short-range operations to include at least 1 independent launch, resupply, and repair bays.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Environment/Crew&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Environmental systems to conform to Starfleet Regulatory Agency (SFRA)- standard 102.9 for Class M compatible oxygen breathing personnel. All life-critical systems to be triply redundant. Life support modules to be replaceable at major Starbase layover to permit vehicle-wide adaptation to Class H, K or L environmental conditions.&lt;br /&gt;
*	Ability to support up to 200 non-crew personnel for mission related operations.&lt;br /&gt;
*	Facilities to support Class M environmental range in all individual living quarters, provisions for 2% of living quarters to be equipped to support Class H, K and L environmental conditions. Additional 1% of living quarters volume to be equipped for Class N and N (2) environmental adaptation.&lt;br /&gt;
*	All habitable volumes to be protected to SFRA-standard 347.3(a) levels for EM and radiation. Subspace flux differential to be maintained within 0.02 millicochranes.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Tactical&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Defensive Shielding to exceed 9.85 X 103 kW primary energy dissipation rate. All tactical Shielding to have full redundancy, with auxiliary system able to provide 75% of primary rating.&lt;br /&gt;
*	Tactical systems to include full array of Type XII phaser bank elements on hull capable of 6.1MW maximum single emitter output. 6 Photon Torpedo launchers required for ship defensive capabilities.&lt;br /&gt;
*	Tactical systems to include anti-detection components capable of defeating sensor and optical scan.&lt;br /&gt;
*	Tactical systems to include variable decreased emissions systems affecting primary and secondary drive systems.&lt;br /&gt;
*	Tactical systems to include components to reproduce or produce false sensor signatures at displaced coordinates in vessel reference.&lt;br /&gt;
*	Tactical systems to include components to produce ambient radiation and gravitational energies consistent with surrounding spatial occurrences.&lt;br /&gt;
*	Tactical systems to include variable EM field dampening systems to reduce or eliminate vessel EM fields and signatures.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Design Life&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Space frame design life of approximately 100 years, assuming approximately 5 major ship- wide system swap outs and upgrades at average intervals of 20 years. Such upgrades help ensure the continuing usefulness of the ship even though significant advances in technology are anticipated during that time. Minor refurbishment and upgrade to occur at approximately one- to five year intervals, depending on specific mission requirements and hardware availability.&lt;br /&gt;
&lt;br /&gt;
==2.0 General Overview==&lt;br /&gt;
&lt;br /&gt;
The Rosenanté class of Starship was originally categorized as an intelligence-gathering vessel. The Rosenanté class is only the second starship class created by Starfleet command to receive this designation. The other is the Spectre Class. While most starships may be adapted for many different mission types, the Rosenanté class starship is designed primarily to perform a single type of mission objective, in effect limiting her overall flexibility within a more generalized Starfleet. Seen from a comfortable distance of two or three kilometres, the starship takes on the resemblance of the more familiar Sovereign class explorers. Upon closer inspection however, one can see that the engineering hull is more sleek, lending a highly manoeuvrable appearance to the Rosenanté class of starship. The engineering hull actually extends both above and below the saucer section, lowering the overall silhouette of the class. Additionally, the saucer section itself boasts a number of changes that are easily noticed even by the most novice of observers. This divorce from standard Starfleet design protocols is both advantageous and disadvantageous for this class of starship. The unique hull design allows an immediate reduction in stresses generated by high warp speeds, while allowing greater manoeuvrability at sub-light speeds. This hull design concept has its drawbacks however, as high speed warp manoeuvrability is reduced in favour of speed. The exterior hull material is stronger, lighter and more durable than that used in standard starship production. This reduces the need for otherwise necessary supports and braces, leaving a greater interior volume for habitation. This material used on the ship&#039;s hull is more difficult to reproduce and repair, as specialized facilities must be implemented to perform these functions.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;2.1 Physical Arrangement&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-2up.jpg|right|300px]]&lt;br /&gt;
&lt;br /&gt;
The hull, remarkably birdlike in its strong, hollow construction, is reinforced against flight stresses by active energy fields that tighten and flex where required to compensate for natural and artificial internal and external forces. Structures integrated into the hull allow for a variety of necessary functions. &lt;br /&gt;
&lt;br /&gt;
The bridge consolidates the command positions for the rest of the starship, windows allow crewmembers needed vistas while in space, phaser arrays and photon torpedoes provide offence and defence against hostile forces, and a specialized communications system allows interaction with other worlds and their ships.&lt;br /&gt;
&lt;br /&gt;
Lifeboats allow for escape in dire emergencies, transporter emitters afford reliable near instant movement of crew and gear, navigational sensors and deflectors give the starship distant vision and a method for clearing obstacles, and powerful warp engines propel the starship at amazing speeds.&lt;br /&gt;
&lt;br /&gt;
The twenty-eight decks are internally divided among major load-bearing structures. A great many systems, especially the habitation sections are suspended within the open spaces, essentially &amp;quot;floating&amp;quot; on flexible ligaments to minimize mechanical, thermal, and conductive radiation shocks.&lt;br /&gt;
&lt;br /&gt;
The living areas of the starship have been designed for maximum comfort and safety while the crew is conducting a mission. Long-term studies of humanoid cultures have revealed that as each race embarked upon permanent occupation of space, large personal living spaces had to be established, especially on early sub-light missions. The Rosenanté class starship allows for some 120 square meters of living space per person, in addition to community space and areas allotted to purely working functions.&lt;br /&gt;
&lt;br /&gt;
==3.0 Spacecraft Structure==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.1 Main Skeletal Structure&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The primary space frame of the Rosenanté class starship is fabricated from an interlocking series of Terminium/Tritium microfilament truss frames. These members average l.05m² in cross section and are capable of bearing the same load as the standard Tritanium/Duranium truss averaging l.27m² in cross section used in standard starship construction. These truss frames are located an average of 20 meters across the ship&#039;s exterior, while the standard trusses would be located every 25 meters along a ships exterior. The tightening of the trusses allows the vessel to withstand greater stress imposed upon it by warp travel, while still producing a lighter space frame.&lt;br /&gt;
&lt;br /&gt;
As with other starship designs, larger numbers of these trusses are located integral to the main impulse engine sections, the warp nacelle pylons, docking interface latches, and along the centerline of the hull structure. Smaller Trusses averaging 0.35m² in cross section are located every five meters on average, and also provide internal supports within the deck and core structure of the spacecraft interior.&lt;br /&gt;
&lt;br /&gt;
A mechanical framework provides physical integrity to the vehicle while at rest. A parallel series of aluminum crystal foam stringers are phase transition bonded to the primary trusses, providing low frequency vibration attenuation across the main truss structure, as well as support for certain utility conduits.&lt;br /&gt;
&lt;br /&gt;
Also attached to these stringers are various conformal devices built into the hulls structure, including elements of the deflector shield grid, H.l.S.S. components, as well as subspace radio antennas, which are incorporated into the skin of the spacecraft.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.2 Secondary Framework&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mounted to the primary space frame is a secondary framework of micro-extruded Terminium trusses to which the inner hull of the structure is directly attached. The secondary framework is mounted by means of 3.2 cm diameter X 5.1 centimeter long semi rigid polydurinide support rods, permitting a limited amount of mechanical isolation from the primary space frame for purposes of strain relief, plus sound and vibration isolation. Secondary space frame segments are also separated from each other (although mechanically attached) to permit replacement of inner hull segments and associated utilities infrastructure during major Starbase layover.&lt;br /&gt;
&lt;br /&gt;
Structural integrity during powered flight is provided by a series of forcefields that reinforce the physical framework. This structural integrity field (SIP) is distributed through a network of molybdenum-jacketed wave-guides, which in turn distribute SIF energy into ceramic-polymer conductive elements throughout the space frame. Without the structural integrity field, the vehicle would be unable to withstand accelerations greater than 3l.4 m/s² without significant deformation, or greater than 49.18 m/s² without unrecoverable structural damage.&lt;br /&gt;
&lt;br /&gt;
Exterior hull substrate is joined to the primary load bearing trusses by means of 4.8-cm diameter electron-bonded duranium pins at 1.01-meter intervals. These pins are slip-fitted into an insulating AGP ceramic fiber jacket that provides thermal insulation between the space frame and the exterior hull. The pins, jacketing, and hull segments are gamma welded together.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.3 Hull Layers&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The exterior of the spacecraft consists of multiple layers, which afford structural and atmospheric integrity for the space frame, integral wave-guides and field conductive members for the structural Integrity Field (SIP) and H.I.S.S components, and pathways for other utilities (including deflector grids), as well as resistance to radiation and thermal energy.&lt;br /&gt;
The exterior shell substrate is composed of interlaced micro-foam duranium filaments. These filaments are gamma welded into a series of contiguous composite segments that are 4.7 cm thick and are typically 2 meters in width. The substrate segments are electron-bonded to three reinforcing layers of 1.2- cm biaxially stressed terranium fabric, which provide additional torsion strength.&lt;br /&gt;
&lt;br /&gt;
In areas immediately adjacent to major structural members, four layers of 2.3-cm fabric are used. The substrate layer is attached to major structural members by electron-bonded duranium fasteners at 2.5-cm intervals. The substrate segments are not intended to be replaceable, except by phase-transition bonding using a transporter assembly jig during major Starbase layovers.&lt;br /&gt;
Two 3.76-cm layers of low-density expanded ceramic-polyrner composites provide thermal insulation and secondary SIP and H.I.S.S. conductivity. These layers are separated by an 8.7-cm multiaxis triennium truss framework, which provides additional thermal insulation and a pass through for fixed utility conduits.&lt;br /&gt;
&lt;br /&gt;
A 4.2-cm layer of monocrystal beryllium silicate infused with somniferous polycarbonate whiskers provides radiation attenuation. This layer is networked with a series of 2.3-cm X 0.85-cm molybdenum-jacketed conduits. These conduits, which occur at 1.3-m intervals, serve as triphase wave-guides for the secondary structural integrity field. Conductive tritium rods penetrate the wave-guides at l0-cm intervals and transfer SIF energy into the ceramic-polymer conductive layer.&lt;br /&gt;
The outermost hull layer is composed of a 1.6-cm sheet of AGP ablative ceramic fabric chemically bonded onto a substrate of 0.15-cm triermium foil. This material is formed into segments approximately 3.7m² and is attached to the radiation attenuation layer by a series of duranium fasteners, which allows individual segments to be replaced as necessary. (Micrometeor erosion is kept to a minimum by the deflector system, but is sufficient to warrant replacement of 30% of the leading edge on the average of every 7.2 standard years.) Individual outer hull segments are machined to a tolerance of ±0.05-mm to allow for minimum drag through the interstellar medium. Joints between segments are manufactured to a tolerance of ±0.025-mm.&lt;br /&gt;
&lt;br /&gt;
Also incorporated into the outermost hull layer is a series of super conducting molybdenum-jacketed wave-guide conduits, which serve to absorb and disperse sensor emission energy that interacts with the hull. Segmented sections of this network serve as housings for the unique DECS components, responsible for producing the ship’s tactical deflector. Unlike a standard starship, there are no thermal regulating assemblies built into the skin of the starship. Instead this duty is regulated through a series of intercoolers and radiators housed inside the interior of the Bussard Collector Assembly.&lt;br /&gt;
&lt;br /&gt;
==4.0 Command Systems==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.1 The Bridge&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Bridge, located on Deck 1, provides primary operational control of the Rosenanté class starship. The bridge directly supervises all primary mission operations and coordinates all departmental activities. These activities are handled through the individual command consoles located in various positions on the bridge. These workstations are modular and can be interchanged, removed, or added as necessary to fulfill specialized mission requirements. At any one time there can be up to 12 workstations installed. The standard bridge design calls for 2 Science Stations, 1 Operations Station, 1 Flight Control Station, l Auxiliary Engineering Station, 1 Tactical station, 1 Communications/ H.I.S.S. station, 1 Internal Security Station, and 2 Command Stations, one each for the ship’s commander, and the First Officer.&lt;br /&gt;
Other facilities located on Deck 1 include Astrogation, the captain&#039;s ready room and head, the crew head, and a small mission briefing room.&lt;br /&gt;
Major connections to the bridge include a pair of Turbolift shafts, four electron-plasma power distribution wave-guide conduits; four environmental support plenum groups, nine primary and two back-up optical data network trunks, two replicator wave-guide conduits, and three service crawlways. As an interesting side note, a tertiary backup power distribution system consisting of hardwired nonreactive, conductive ceramic-polymer relays are also in place.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.2 Display Panels&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The display panels on the bridge and through out the ship are constructed and operated the same as those on any other Federation starship. The layouts and reactivity of the panels are augmented and display properties shown in a different manner. The coloration of the interaction displays is altered to create a different aesthetic affect, while also allowing a variant-programming matrix to be utilized. This new language utilizes advances in Holoprogramming to create three-dimensional matrix strings; this in turn allows a more efficient and quicker computer response time. Critical internal components of the display panels are mapped to the molecular level allowing a replication driven pro-holographic matrix damage control system to repair damaged components. The components necessary to facilitate this activity are collectively known as the &#039;&#039;&#039;Se&#039;&#039;&#039;lf-&#039;&#039;&#039;Re&#039;&#039;&#039;plicating &#039;&#039;&#039;Da&#039;&#039;&#039;mage &#039;&#039;&#039;C&#039;&#039;&#039;ontrol &#039;&#039;&#039;S&#039;&#039;&#039;ystem (&#039;&#039;&#039;SERDACS&#039;&#039;&#039;). The &#039;&#039;&#039;SERDACS&#039;&#039;&#039; components are present in all non-integrity dependant systems throughout the ship. &lt;br /&gt;
&lt;br /&gt;
In addition to the standard anchored display consoles located throughout the ship, a series of Holoemitters have been seeded throughout the vessel to allow ship&#039;s personnel to utilize a holographic interface to tie directly into the ships computer regardless of the location of the crewmember. These emitters also allow the EMH to be activated in any compartment in the ship, and also allow for the construction of holographic crewmembers to fill non-critical positions on the ship. These holoemitters are capable of creating non-electronic tools for emergency use, and in conjunction with replication systems could produce vital simplified component reproduction anywhere aboard ship.&lt;br /&gt;
&lt;br /&gt;
==4.3 Bridge Stations==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.1 Flight Control (CONN)&#039;&#039;&#039; &amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the actual piloting and navigation of the ship. From this station all SIF and IDF systems are monitored, as well as navigational deflectors, and their subsequent systems. This console performs the same functions as it would on board any other Federation starship.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.2 Operations Management (OPS)&#039;&#039;&#039; &amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for power maintenance and resource allocation. This console dictates priority status of all shipboard systems and operations. They coordinate activities between departments and between the ship and away missions. This console performs the same functions as it would on board any other Federation starship.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.3 Tactical Operations (TACOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the operation, monitoring and maintenance of the ship&#039;s tactical systems. These systems include the phaser arrays, the photon torpedo deployment systems, probe	deployment systems, H.I.S.S. system, Signal displacement system, tractor beams, and Tactical deflector systems. The Tactical station aboard the Rosenanté class starship differs from those of standard Federation starships. The main difference is the divorce of the ship&#039;s tactical systems from the internal security systems of the ship. This allows the tactical officer the ability to concentrate on the tactical aspects of the ship without the need to also monitor the internal security status of the ship. Another major difference in the Rosenanté class starship is the addition of a sensor array specifically for use by the tactical officer.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.4 Security Operations (SECOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the monitoring and operation of internal ship security systems. The Operator of this console is responsible for the deployment of ship&#039;s security personnel aboard the ship. This console controls the internal security containment fields, internal ship&#039;s sensors. The SECOPS officer can monitor the security status, security systems and personnel deployment for the entire ship. They can control door mechanisms, containment fields, the turbolift car, and weapons settings of all Federation weaponry on the ship. In addition, security can control personnel access to restricted areas, and utilize sight-to-sight onboard transporters.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.5 Communications (COMMOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the encryption and decryption of intercepted communications, for the transmission of communications, maintaining the Emissions Control Protocols, and the operation of specialized communications interception equipment. The Communications officer is often called upon to triangulate communications sources, decipher enemy transmissions, and encrypt outgoing communications. They often assist in Traffic Analysis of enemy troop deployment, and maintain secure communications with away teams.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.6 Science Stations I &amp;amp; II&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
These consoles are responsible for data collections, primary and lateral sensor operations, and database referencing. It is the responsibility of the science officer to operate the ship&#039;s sensors, teleoptical systems, and imaging systems. They observe, record and document data important to shipboard mission objectives. These stations can be utilized together or separately. This station also acts as the primary database access terminal for the Federation database carried aboard all Federation starships. Both passive and active sensors are controlled from this station.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.7 Auxiliary Engineering Station&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This station is responsible for maintaining and monitoring shipboard systems. This console works in conjunction with main engineering, and is capable of performing the same functions as the computer in that section of the ship. From this station the warp fields can be tuned, altered or monitored, as can all primary and secondary shipboard systems. This station is not always manned.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.8 Command Stations I &amp;amp; II&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
These consoles are responsible for the maintenance and monitoring of the ship&#039;s computer and all primary and secondary systems. Only the commanding and executive officer have access to these consoles. From these consoles the commanding officers can display data concerning ship&#039;s systems, status, condition, position, speed, heading, and power management distribution. These consoles can access the database, and has priority authority over all computer functions. These consoles are the only terminals capable of activating the ship&#039;s self-destruct mechanism. Any officer in command of the starship may utilize these consoles, although some functions may be unavailable.&lt;br /&gt;
&lt;br /&gt;
==5.0 The Computer System==&lt;br /&gt;
The computer system aboard the Rosenanté class starship is identical in construction to the computers used on other Federation Starships. They utilize the same back up and failsafe hardware and communicate through the same methods as the standard starship computer. The computer system of the Rosenanté class starship is composed of 2 synchronized computer cores, identical to those used in the Galaxy Class starship. The only differences between the standard Federation computers and those aboard the Rosenanté are the storage medium and programming language that the system uses to communicate.&lt;br /&gt;
The storage of data and processing networks of a standard Federation computer system depend upon isolinear chips. On the Rosenanté a new type of data storage chip, the Hololinear chip is introduced. Taking advantage of new replication and holographic programming breakthroughs, the new Hololinear chips, or HL chips, allow data to be stored in a four-dimensional, subspace format. A new programming language known a &#039;&#039;&#039;B&#039;&#039;&#039;ilinear &#039;&#039;&#039;U&#039;&#039;&#039;nilateral &#039;&#039;&#039;N&#039;&#039;&#039;etworking &#039;&#039;&#039;C&#039;&#039;&#039;ode (&#039;&#039;&#039;BUNC&#039;&#039;&#039;) allows data to be stored in a temprometric tagged holographic string, thereby allowing data to be stacked almost exponentially upon other data, linked by temprometric strings of associated data. Retrieval time is decreased as the data can be read from any point along its data string, rather than starting at a specified point as is required by the standard isolinear chip design.&lt;br /&gt;
&lt;br /&gt;
==6.0 Warp Propulsion Systems==&lt;br /&gt;
The Warp propulsion system in the Rosenanté class starship is radically different from Those used in other starships. The majority of the system is developed to utilize existing warp technology and materials. There is however a few major changes in the system. All warp engineers are familiar with the laws of warp transition, which dictates that warp geometry and power requirements dictate a vessel&#039;s ability to achieve various levels of warp speed. This same law also dictates that a warp field must be balanced in order to achieve maximum efficiency to make a warp transition.&lt;br /&gt;
&lt;br /&gt;
The Graph below represents the transition energy requirements for the Galaxy Class Starship design and also for that of the Rosenanté class starship.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:RWC.jpg|thumb|Center|800px|Warp transition chart]]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
ln the chart above the Cochrane values are represented over the white bar for the Rosenanté Class starship. At lower warps (below Warp 6) there is an actual decrease in warp efficiency, although at higher warp there is a worthwhile increase in efficiency, where the differences in efficiency matter most. It is important to note that a Galaxy class starship is incapable of traveling at Warp 9.97, and thus the numbers represented for that class is theoretical.&lt;br /&gt;
&lt;br /&gt;
The ability to sustain warp 9.97 is a result of multiple warp engines working in synchronization and a natural by-product of the embedded nacelle design. The synchronization of the dual warp drive is accomplished through the use of a &#039;&#039;&#039;W&#039;&#039;&#039;arp &#039;&#039;&#039;E&#039;&#039;&#039;nergy &#039;&#039;&#039;Sy&#039;&#039;&#039;nchronization &#039;&#039;&#039;R&#039;&#039;&#039;outer, or &#039;&#039;&#039;WESYR&#039;&#039;&#039;. The &#039;&#039;&#039;WESYR&#039;&#039;&#039; unit is highly classified, but its basic function is to synchronize otherwise out of synch Waveforms created within two near identical meshed Tuned Plasma Streams. Because of the additional energy that this system produces, a higher capacity EPS Power Tap and Series Relays were developed to handle the additional power loads. A dual bypass system allows any single Warp drive to power ships functions, at a significant reduction in overall power. Also a major redesign feature of the upgraded power system resulted in the addition of a second Port and Starboard Power conduit assembly and relay subassembly. This allows the power delivery system to function more efficiently.&lt;br /&gt;
&lt;br /&gt;
Interestingly enough, a bizarre natural byproduct of running a dual synchronized Warp Field is the creation of a &amp;quot;double&amp;quot; warp bubble. These warp bubbles are divided by 2.3-mnm (micronanometers) and help produce the effect of the change of reduction caused when making Warp Transitions. As subspace resistance passes through the Outer shield it is reduced as normal, then again as the remaining resistance passes through the inner bubble, it is further reduced. This causes the starship to experience less resistance and shearing warp stress associated with high rate warp travel and maneuvering.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Spiral Warp Drive&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In addition to the standard warp drive used by all federation starships, the Rosenanté class is also equipped with an experimental Spiral Warp Drive. This drive creates a subspace &amp;quot;tunnel&amp;quot; or &amp;quot;wormhole&amp;quot;  through which the Rosenanté may then travel. The tunnel integrity is maintained by the main deflector dish. The tunnel basically allows the ship to drop into subspace, effectively disappearing from normal space for a short period of time. The speeds that are achieved through the use of this drive are akin to those used by the Borg when using transwarp conduits. Unlike transwarp conduits, however,the tunnel being opened by the Rosenanté would dissipate as soon as the ship moves through it. In a similar manner, the spiral drive can only be used to travel in straight lines. This means that the vessel may make a periodic series of short hops to correct course when using this system.&lt;br /&gt;
&lt;br /&gt;
==7.0 Deflector Emitter Cluster System (DECS) ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-3up.jpg|thumb|left|500px|]]&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;D&#039;&#039;&#039;eflector &#039;&#039;&#039;E&#039;&#039;&#039;mitter &#039;&#039;&#039;C&#039;&#039;&#039;luster &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;DECS&#039;&#039;&#039;, represents the newest Federation breakthroughs in Federation tactical shield technology. This innovative new system utilizes a convex “honeycombed&amp;quot; arrangement of octagonal emitters offset slightly to produce a unified, overlapping tactical field. This primary tactical system allows a tighter tactical shield to be produced, thus resulting in a lessened tactical shield cross section, which in turn reduces starship detectability.&lt;br /&gt;
&lt;br /&gt;
Whereas the Rosenanté class of starship possesses the standard &#039;&#039;&#039;D&#039;&#039;&#039;eflector &#039;&#039;&#039;E&#039;&#039;&#039;mitter &#039;&#039;&#039;A&#039;&#039;&#039;rray (&#039;&#039;&#039;DEA&#039;&#039;&#039;) that all Federation starships do, they use that particular system as a primary shielding system. The &#039;&#039;&#039;DECS&#039;&#039;&#039; assembly operates by producing several smaller polyhedral segments of shield interdependability, rather than creating a &amp;quot;shell&amp;quot; segment standard to all other Federation starships. The &#039;&#039;&#039;DECS&#039;&#039;&#039; requires more power than standard tactical &#039;&#039;&#039;DEA&#039;&#039;&#039; systems, but yields a 20% increase in shield output. The &#039;&#039;&#039;DECS&#039;&#039;&#039; is calibrated to respond and recalibrate the loss of a single emitter or emitter cluster, resulting in a greater overall performance and defensive capability of ship systems. The standard &#039;&#039;&#039;DECS&#039;&#039;&#039; system is installed to provide tactical shielding whenever the starship is experiencing &#039;&#039;&#039;DEA&#039;&#039;&#039; failure, or power requirements do not allow the use of the &#039;&#039;&#039;DEA&#039;&#039;&#039;. Another advantage of the DECS over the standard DEA is its modular design. It is quick and efficient to repair or replace in the field whereas the replacement of the DEA system requires a major overhaul at a Starbase.&lt;br /&gt;
&lt;br /&gt;
==8.0 Hull Integrated Stealth System. ==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;H&#039;&#039;&#039;ull &#039;&#039;&#039;I&#039;&#039;&#039;ntegrated &#039;&#039;&#039;S&#039;&#039;&#039;tealth &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;HISS&#039;&#039;&#039;, is a series of alterations to the ships exterior hull and systems to create a reduced sensor and visual silhouette. The details of the &#039;&#039;&#039;HISS&#039;&#039;&#039; are highly classified, although the general concepts behind its incorporation are not. A network of specialized integrated hull webbing allows the hull to emit energies that effectively allow light waves to pass through it and its contents. In addition to visual bands of radiation, the specially designed ablative hull absorbs sensor energy, while emitting the same energy signature as the starship&#039;s surrounding space. Thus, the vessel becomes virtually undetectable either through detection or complete omission of detection. In addition to this, specialized hull features act as complex Magnetic field disruptors, reducing the EM field of the vessel, and also neutralize radioactive emissions through a complex series of intercoolers and sheathed cowlings. The ship&#039;s Impulse, Thruster and Bussard collection systems are incorporated to nearly negate all detectable signs of their use. When the HISS is active and used in conjunction with strict Emissions protocols, the ship vanishes from visual and sensor detection.&lt;br /&gt;
&lt;br /&gt;
==9.0 Advanced Sensors Systems==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;I&#039;&#039;&#039;mproved &#039;&#039;&#039;S&#039;&#039;&#039;ensor &#039;&#039;&#039;I&#039;&#039;&#039;ntegrated &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;ISIS&#039;&#039;&#039;, is a modified high yield Federation sensor array. The &#039;&#039;&#039;ISIS&#039;&#039;&#039; utilizes the newest development in sensor technology to quantum phase the active and passive ship&#039;s sensors to greatly reduce detectability. These new sensors are more powerful, and almost impossible to detect without performing extensive and time consuming alterations to a starship&#039;s sensor array, which then is useless to detecting other aspects of its surrounding. Some of this technology is loosely based on cloaking principles.&lt;br /&gt;
&lt;br /&gt;
==10.0 Sensor Displacement System==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Se&#039;&#039;&#039;nsor &#039;&#039;&#039;Di&#039;&#039;&#039;splacement &#039;&#039;&#039;S&#039;&#039;&#039;ystem, Or &#039;&#039;&#039;SEDIS&#039;&#039;&#039;, allows the Rosenanté class of starship to offset its actual energy signature, and even produce an additional energy signature. This is designed to improve the starships ability to prevent &amp;quot;true&amp;quot; detection, or to act as a decoy system in the event that the starship is detected. This system is capable of operating within a 60OKm range of the vessel.&lt;br /&gt;
&lt;br /&gt;
==11.0 Displaced Communications System==&lt;br /&gt;
The &#039;&#039;&#039;Di&#039;&#039;&#039;splaced &#039;&#039;&#039;Comm&#039;&#039;&#039;unications &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;DICOMMS&#039;&#039;&#039;, is based on the same technology as the &#039;&#039;&#039;ISIS&#039;&#039;&#039;. This energy is used to send nearly undetectable communications. The Rosenanté class starship is equipped with standard Federation communications systems as well.&lt;br /&gt;
&lt;br /&gt;
==12.0 Interior Systems Modifications==&lt;br /&gt;
There have been a variety of interior alterations to the interior, habitable areas of the Rosenanté class starship. The most apparent alterations are in the functionality of the corridor and turbolift systems. The oversized personnel quarters offer the most luxurious and spacious accommodations aboard any Starfleet posting, while unique interaction software insures crewmembers peace of mind.&lt;br /&gt;
&lt;br /&gt;
Many Starfleet admirals believe that the Tactical and Scientific Equipment carried by a Starship to be the most important asset to any Starfleet facility or starship. The designers of the Rosenanté class of Starship also felt that crew morale would also serve a very integral role in the operation of the starship. To these ends the interactive systems and habitations were designed to provide a reassuring and relaxing environment for the ships crew.&lt;br /&gt;
&lt;br /&gt;
==12.1 Safety Systems==&lt;br /&gt;
The most paramount function of any Starship is the maintenance of its crew in adverse conditions. Integral to this school of thought is the ability to protect the crew under hostile threats. To these ends, the designers of the Rosenanté class starship developed a series of counterinsurgency systems to minimize crew contact with alien forces boarding the vessel.&lt;br /&gt;
&lt;br /&gt;
==12.1.1 Isolation Field Systems==&lt;br /&gt;
The &#039;&#039;&#039;I&#039;&#039;&#039;solation &#039;&#039;&#039;F&#039;&#039;&#039;ield &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;IFS&#039;&#039;&#039;, was designed with the intent to isolate hostile alien forces that boarded the vessel for the crew. This function is considered vitally important when consideration is given to the fact that the Rosenanté class starship possesses a very highly trained crew. The &#039;&#039;&#039;IFS&#039;&#039;&#039; fundamentally isolates the threat through the use of perpetual containment fields, reinforced by miniature shield defenses for the IFS emitter assembly. The &#039;&#039;&#039;IFS&#039;&#039;&#039; is always active, limiting the mobility of non-authorized personnel, securing sensitive sectors of the ship, and effectively hindering the process of any hostile aliens that may manage to board the vessel. The ship&#039;s computer monitors the movements of every official member of the ship&#039;s crew at all times. In this manner, the computer is able to activate or deactivate the &#039;&#039;&#039;IFS&#039;&#039;&#039; screens on an individual basis as needed. This allows authorized crewmembers access to shipboard systems and compartments as needed. The &#039;&#039;&#039;IFS&#039;&#039;&#039; consists of a series of Level 8 containment fields spaced an even 12.5-meters along the corridors of the vessel. In addition to these, an &#039;&#039;&#039;IFS&#039;&#039;&#039; field also isolates each access portal and hatch. In the event that a commbadge should be captured, or fail, that badge is automatically removed from all access rosters, until security can investigate the occurrence.&lt;br /&gt;
&lt;br /&gt;
As a benefit of the perpetually active IFIS fields, studies indicate that shipboard damage caused by fire and/or decompression was drastically reduced. The fields prevented large area decompression, and also limited the range of fire dispersion radically.&lt;br /&gt;
&lt;br /&gt;
Although in larger compartments the &#039;&#039;&#039;IFS&#039;&#039;&#039; system is not perpetual; all compartments are equipped with the capacity to further &amp;quot;compartmentalize&amp;quot; these large open areas. The computer is capable of assessing threats to the crew and equipment of the vessel, and can respond using the &#039;&#039;&#039;IFS&#039;&#039;&#039; system, nearly instantly. The &#039;&#039;&#039;IFS&#039;&#039;&#039; system was designed to operate independently of the ships main power supply when necessary. Each &#039;&#039;&#039;IFS&#039;&#039;&#039; emitter and processor assembly is equipped with an independent high-yield Sodium Kelleride power system. This power cell is further treated with a Potassium Unified catalyst. This allows the production of oxygen as a by-product whenever the secondary power system is operated. This allows a crewmember to be compartmentalized in an otherwise decompressed area to survive asphyxiation and loss of pressure. This secondary power system will allow the full yield operation of the &#039;&#039;&#039;IFS&#039;&#039;&#039; emitter in question for a period of 4 standard hours. Setting the emitter to a lower containment setting can extend this time.&lt;br /&gt;
&lt;br /&gt;
==12.1.2 Fire Suppression Systems==&lt;br /&gt;
&lt;br /&gt;
Although the &#039;&#039;&#039;IFS&#039;&#039;&#039; system hinders the progress of a shipboard fire, it will not necessarily extinguish it. To facilitate this a hybrid field emitter, environmental suppression system was developed. This system isolates the flame from its fuel source using advanced forcefield emissions systems, while simultaneously adjusting the environment around the fire to assist in its suppression. A functional &#039;&#039;&#039;IFS&#039;&#039;&#039; contained area further supports the adjustments, as a smaller area of the ship need be adjusted at any one time. There are certain types of plasma fires that could be unaffected by environmental conditions and or can not be contained in this manner. It is in those situations that the fire suppression systems remove the fire and all affected material through use of the ships sight-to-sight transporters. If this cannot be performed due to a greater risk being imposed on the crew, more conventional methods of fire suppression must be performed.&lt;br /&gt;
&lt;br /&gt;
==12.1.3 Internal Ballistics Dampening Fields==&lt;br /&gt;
In key areas where materials stored aboard ship have the potential to be propelled through sections of the ship, a series of &#039;&#039;&#039;I&#039;&#039;&#039;nternal &#039;&#039;&#039;Ba&#039;&#039;&#039;llistics &#039;&#039;&#039;D&#039;&#039;&#039;ampening Fields, or &#039;&#039;&#039;I-BAD&#039;&#039;&#039; Fields, have been implemented. These fields are found primarily in the armory, cargo bays, Shuttle Bays, storage bays, and personnel quarters. The &#039;&#039;&#039;I-BAD&#039;&#039;&#039; system uses advanced internal sensing equipment specialized to calculate mass and velocity of non-anchored materials. In the event that these materials should be propelled at a speed that the computer should indicate hazardous to crew, then a series of inertial Dampening Fields are erected to reduce the velocity of the offending object. The IDF relays cannot stop a propelled item, although it can shorten its travel distance and relative speed considerably. The sensing systems ignore the movements of personnel. The &#039;&#039;&#039;I-BAD&#039;&#039;&#039; emitters in no way affect the reduction of stresses upon the vessel caused by acceleration, deceleration, or maneuvering.&lt;br /&gt;
&lt;br /&gt;
==12.1.4 Advanced Ergonomics==&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-4up.jpg|thumb|right|500px|]]&lt;br /&gt;
&lt;br /&gt;
Throughout the vessel, specialized memory seating systems have been implemented. These systems monitor the stresses upon the body of the crewmember presently utilizing them and adjust the contact points with the crewmember to minimize physical stresses. All station seating and this material affects standard seating in personnel quarters. The design is such that is can self adjust to allow for non-humanoid crewmembers. The standard bedding and medical bio beds are also adjusted in this manner. This has proven to reduce fatigue and discomfort resulting from prolonged duty shifts. The conceptualization of advanced ergonomic design is further implemented in the layouts and design of the personnel quarters on the ship. Each individual’s quarters are ergonomically designed to his or her unique specifications. The height and shape of interactive systems, the design of the shelving and storage facilities, and the layout of the waste management system are all adjusted to the unique requirements of the compartment owner. Even habitation shape and colour are carefully implemented to create an environment in harmony with its occupant.&lt;br /&gt;
&lt;br /&gt;
==12.1.5 Tactical Sight-to-Sight Transport==&lt;br /&gt;
The ship&#039;s computer possesses the ability to assess tactical breaches in to the vessel&#039;s security. When appropriate, the computer may implement tactical redistribution of security personnel to facilitate the disarmament of tactical threats. The computer determines the size of any aggressive and/or threatening force on the ship, and then determines logical methods of containing and overcoming this threat. The computer is capable of briefing shipboard security personnel on the state of a threat, operating IFIS units, and evacuating non-essential personnel from potential or actual combat areas. The computer can deploy security personnel using sight-to-sight transporters and tactical deployment subroutines. In addition to automatic response to internal tactical threats, the ship&#039;s computer can suggest tactical deployment options for security personnel, utilizing data stored in its memory. This tactical deployment data is only suggested when asked for, and is prepared for planetoid deployment, boarding actions, counter-boarding actions, and sight security. When a medical situation presents itself the same sight-to-sight transporter system can be utilized to transport critical patients to the sickbay.&lt;br /&gt;
&lt;br /&gt;
==12.1.6 Emergency Medical Hologram==&lt;br /&gt;
The Emergency Medical Hologram, as standard to all Federation starships, is also present on the Rosenanté class starship. A series of modifications allows the EMH system to be activated in any habitable portion of the vessel. This function is performed by a series of specialized emitters seeded throughout the ship. Each emitter is equipped with an array of medical scanners and programmed with trauma and first aid protocols. Each emitter assembly is capable of independent operation in the event that power systems become unavailable. The Sodium Kelleride power source can maintain EMH use for 1 hour before expending its charge. When operating normally, the EMH can access the ship&#039;s medical database. When operating independently, only the trauma and first aid subroutines may be accessed. While operating on ship&#039;s systems no more than three EMH programs may be running at any one time. Independent operation is possible among any number of EMH emitters.&lt;br /&gt;
&lt;br /&gt;
==12.1.7 Emergency Replication System==&lt;br /&gt;
The &#039;&#039;&#039;E&#039;&#039;&#039;mergency &#039;&#039;&#039;R&#039;&#039;&#039;eplication &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;ERS&#039;&#039;&#039;, is a series of secondary replicators that operate completely independent of the ships systems. The &#039;&#039;&#039;ERS&#039;&#039;&#039; units are located aft and fore of the starship, two per deck. They are always inert until activated. The &#039;&#039;&#039;ERS&#039;&#039;&#039; system is &amp;quot;hidden&amp;quot; behind corridor paneling, and consists of a single equipment replicator, a single food replicator, an atmospheric condenser, a single medical tricorder, a standard tricorder, and a pair of Class I Phasers. A high-yield Sodium Kelleride Battery that allows light use of the replicators, for a period of 3 days, powers the &#039;&#039;&#039;ERS&#039;&#039;&#039; units. The Tricorders and Phasers are pre-powered, and can be recharged once, using the supplied connections. Accessing the ERS panel will alert security. The Class I phasers require a personal authorization code to be activated. The computer monitors the &#039;&#039;&#039;ERS&#039;&#039;&#039; system very closely, immediately notifying engineering if a problem is detected.&lt;br /&gt;
Although the &#039;&#039;&#039;ERS&#039;&#039;&#039; is a fully functional Replication system, it is programmed to create materials that require very little energy to reproduce. Thus, the food replicators produce only a single nutrient rich disk for consumption. The Tool replicator is limited to equipment that possesses simple physical structures, such as hand tools and only simple electronics materials. Neither replicator system can reproduce power sources, or advanced electronics.&lt;br /&gt;
&lt;br /&gt;
==12.1.8 Emergency Transporters==&lt;br /&gt;
The Rosenanté class starship is equipped with 2 emergency transporters. These transporters are located centrally along the berth and length of the vessel on decks 5 and 15. The emergency transporters are integrated into the primary corridor on the aforementioned decks. All transporter hardware is stowed in the surrounding corridor structures. 20 high-yield Sodium Kelleride Batteries independently power the control operation panel and the emergency transport systems. Each Emergency transporter is also equipped with its own short-range sensor array, for destination determination. The control panel is &amp;quot;hidden&amp;quot; behind the corridor paneling, and floor paneling hides the transporter pad. In order to operate the transporter this floor paneling must be removed. The emergency transporters are each capable of transporting 60 personnel.&lt;br /&gt;
After that there is no power remaining to continue transporter functions. Preparing the Emergency transporters for use alerts security.&lt;br /&gt;
&lt;br /&gt;
==12.2 Medical Bay==&lt;br /&gt;
Due to the number of personnel stationed aboard the Rosenanté class starship, the standard&lt;br /&gt;
Medical Bay arrangement was not utilized. Instead a specialized medical bay was designed to maximize space, while still attending to the variable needs of the ship&#039;s crew. To this end, the sickbay possesses a complete quarantine ward, a single surgical ward, and the central sickbay. A office allows for the CMO to perform administrative tasks without interruption.&lt;br /&gt;
In the surgical area, all the equipment necessary to perform any level of surgery is present. Specialized negative pressure systems allow operations to continue upon contaminated personnel without worry of integrity loss.&lt;br /&gt;
The central medical area is equipped with the newest and most efficient systems that general practice has to offer. A multitude of sensors and medical dedicated processors facilitate medical data gathering, while advanced holographic modeling systems allow hands-off data model construction. Forty Biobeds are located in the Sickbay, which studies indicate was the most efficient number of patients to treat at one time. &lt;br /&gt;
&lt;br /&gt;
In addition to the standard biobeds and Infirmary treatment bay, There are also two dedicated Medical Laboratories, One General Practice Clinical Ward and Three configurable Bays, which can be changed to meet the specific requirements of the medical needs of the vessel.&lt;br /&gt;
&lt;br /&gt;
The Quarantine area is equipped with a series of Biocide units capable of detecting, isolating and destroying over three hundred billion contagions. Negative pressure atmospheric systems, ionic decontamination systems, and bio-phased containment fields guarantee the isolation of harmful contagions. All containment systems in the sickbay are maintained by secondary and tertiary power systems. A medical dedicated replication system allows the creation of any replicable pharmaceutical known to Starfleet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&amp;lt;small&amp;gt;All images compliments of Roger Wackowski&amp;lt;br&amp;gt;Spiral Drive concepts by Anthony Keen&amp;lt;br&amp;gt;All other technical aspects, created, written and designed by Daniel Greene&amp;lt;/small&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
[[Category: Engineering]][[Category: Database]][[Category: Active Ships]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=The_Chimera_Directive&amp;diff=55389</id>
		<title>The Chimera Directive</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=The_Chimera_Directive&amp;diff=55389"/>
		<updated>2012-05-09T16:22:36Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* 6.0 Warp Propulsion Systems */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;  &lt;br /&gt;
  &lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
== 1.0	CHIMERA DIRECTIVE INTRODUCTION ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-1up.jpg|thumb|500px|The Rosenante Class Starship]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1.1 MISSION OBJECTIVES FOR ROSENANTÉ CLASS PROJECT&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Starfleet has long been charged with a broad spectrum of responsibilities to the citizens of the Federation and to the lifeforms of the Galaxy at large. As the volume of explored space continues to grow, and with it the Federation itself, so do Starfleet&#039;s duties. &lt;br /&gt;
&lt;br /&gt;
These duties range from relatively mundane domestic and civil missions, to cultural contact and diplomacy, to defense, to our primary mission of exploration and research. Many of these responsibilities are best carried out with relatively small, specialized ships. Yet there continues to be an ongoing need for an even narrower role vessel to protect the Federation against enemies that would use espionage and subversion to wage war against the Federation.&lt;br /&gt;
&lt;br /&gt;
This particular threat to Federation security is further complicated by political and economic restraints placed upon the Federation caused by the demands of maintaining an active war first against the Cardassian Union and then a Civil War between Doenitz Loyalists and 52nd Fleet seditionists. The Federation had suddenly found itself pressed on many fronts at various levels of engagement, often ill-prepared or incapable of information gathering against potential interior and exterior threats to the continued existence of the Federation.&lt;br /&gt;
&lt;br /&gt;
In response to the alarming number of intelligence related activities conducted against Federation projects, personnel, and equipment by exterior Intelligence Organizations, such as the Tal Shiar, the Dominion Shapeshifters, and The Cardassian Obsidian Order, Starfleet Intelligence has found itself grossly outnumbered, and under-appreciated by Starfleet Command. This lack of interdepartmental cooperation was only strengthened by Starfleet Intelligence&#039;s inability to detect and detain several pro-Revolutionary agents that had managed to infiltrate Starfleet Command, the Council of the President, and several other critical posts within the governmental structure of the Federation. The agents proved to be the first signs of the coming Civil war that would shake the foundations of the United Federation of Planets over the next several years.&lt;br /&gt;
&lt;br /&gt;
These breeches of critical security protocol within the government provided the critics of Starfleet Intelligence with ammunition to pressure Starfleet Command to tighten its control on the Intelligence Department. In late 2390s, with the Cardassian Union pressing their offensive against the Federation, Starfleet Intelligence learned of other threats to the Federation&#039;s continuing existence, as reports began to come into Starfleet Intelligence&#039;s Romulan desk reporting a large number of Romulan Infiltrators had somehow managed to concentrate themselves on the Federation Starships patrolling the Neutral Zone. With reports indicating that the Tal Shiar compromised a large majority of Starships patrolling the Neutral Zone, and with SFI fearing a Romulan Invasion, a massive counter Intelligence operation began. This operation, dubbed Sword and Shield, inserted several dozen Starfleet counterintelligence Specialists onboard the suspected Starships. For the better part of a year, these operatives played a deadly game of cloak and dagger against the expectant Tal Shiar operatives. This massive undertaking resulted in the largest capture of external espionage operatives in Starfleet history, 38 Starfleet officers (including 2 Ship Captains) and 12 Enlisted Starfleet personnel were arrested and charged with espionage against the Federation. 6 Starfleet Intelligence operatives lost their lives in this operation. &lt;br /&gt;
&lt;br /&gt;
It was to this threat that Admiral Rodrigo Doenitz would propose a solution. That solution came in the form of a Starship, dedicated completely to the tasks of espionage and interdiction operations. The vessel would be operated entirely independently of Starfleet command. Only Starfleet Intelligence would have any command authority over the vessel and its missions. This proposal created a scandalous outcry by Starfleet Command Officers, with the end result becoming less than favorable to the Doenitz cause.&lt;br /&gt;
&lt;br /&gt;
However, the dramatic success of Sword and Shield eased the tension against Starfleet Intelligence, and by the end of the War with the Cardassian Union in 2398; Starfleet Command realized the inability of SFI to conduct operations in hostile space, or to operate independently without the immediate assistance of Starship under Starfleet Command authority. It was in August of that year that Admiral Talbot, with the support of Admiral Doenitz proposed the idea of creating a new class of Starship capable of supporting Intelligence operations in hostile space, while simultaneously capable of performing signal, traffic and visual surveillance of facilities, ship movements and communications. Admiral Talbot argued that if SFI were equipped with such a vessel during the War, that the effectiveness of the Cardassian attack against the UFP would have been greatly reduced, if not altogether neutralized. Additionally, Talbot argued, such a ship working in Romulan space would have been priceless in determining the intentions and movements of the Tal Shiar during Operation Sword and Shield.&lt;br /&gt;
&lt;br /&gt;
Admiral Talbot’s conceptual Starship was deemed impossible to build, and also in violation of Starfleet Intelligence Command’s charter and the project was immediately disapproved. But that was not the end of the situation. &lt;br /&gt;
&lt;br /&gt;
Admiral Talbot, through secret channels with the complete support of Admiral Rodrigo Doenitz established a secret construction facility. Through various nefarious means, funds were funneled into the project and experienced Starfleet ship engineers were tasked to assist in developing a new class of Starship that could function efficiently within the confines established by the joint visions held by the two admirals.&lt;br /&gt;
&lt;br /&gt;
A special Starfleet Intelligence Operation was begun in a secret shipyard facility around early 2397. SFI operatives assigned to the operation interviewed and recruited Starship designers from across the Federation, purposely avoiding any designer that had ever worked on a Starship Project for the Federation in the past. These designers, assisted by the technical and personal experiences, of selected Starship Engineers laid down the design parameters for the project.&lt;br /&gt;
&lt;br /&gt;
After Admiral Doenitz’s successful coup, the project would prove to outlive many of its critics. With the full power of the office of the president of the Federation, Doenitz fast tracked his project making it an official Presidential Directive. This Directive was codenamed the Chimera Directive.&lt;br /&gt;
&lt;br /&gt;
The Rosenanté Class Starship designed by the Chimera Directive represents the most advanced design and systems innovations in the Federation. The basic design concept was developed around the Sovereign class and is considered the most advanced evolution of Starfleet Ship design to date.&lt;br /&gt;
&lt;br /&gt;
==Design Objectives==&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;&#039;&#039;Pursuant to Starfleet Intelligence Directive 1045.35, the following objectives have been established for the Rosenanté Class Starship development project:&#039;&#039;&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*	Provide a mobile platform for a wide range of ongoing intelligence and counterintelligence projects.&lt;br /&gt;
*	Provide autonomous capability for full execution of Starfleet Intelligence policy and directive options in hostile areas of space.&lt;br /&gt;
*	Incorporate recent advances in technology and protocols.&lt;br /&gt;
&lt;br /&gt;
To provide for these objectives, the Designers recommended that the Rosenanté class starship meets or exceeds the design goals in the following specification Categories;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Propulsion&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Sustainable cruise Velocity of Warp Factor 9.4. Ability to maintain speeds of up to Warp Factor 9.7 for periods of up to 12 Hours.&lt;br /&gt;
*	Sixth-phase dilithium controlled matter/antimatter reactor for primary power. Sustainable field output to exceed 1, 650 cochranes, peak transitional surge reserve to exceed 4,225% of nominal output. (170ns phase)&lt;br /&gt;
*	Warp Driver coils efficiency to meet or exceed 98% at speeds up to Warp 8.0. Minimum efficiency of 68% to be maintained through Warp 9.4. Life cycle of all primary coil elements to meet or exceed 1,200,000 cochrane-hours between neutron purge refurbishment. Secondary coil elements to meet or exceed 2,000,000 cochrane-hours between neutron purge refurbishment.&lt;br /&gt;
*	Warp field geometry to incorporate modified 85° Z-axis compression characteristics on forward warp lobe for increased peak transitional efficiency at high warp. Warp Nacelle centerlines to conform to 2.56: 1.1 ratio of separation to maximize field strength.&lt;br /&gt;
*	Secondary (impulse) propulsion systems to provide sub-light velocities up to and including .92 light speed (c). Engine systems of choice to include but not limited to at least two YPS 8063 fusion drive motors. All units to be equipped with subspace drive accelerators, field output not less than 180 millicochranes at 1.02 X l0³K. Reactor Modules to be field replaceable.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Mission&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Ability to operate independent of Starbase refurbishment for moderate periods of time. Independent operation mode capability of 1 Standard years at nominal Warp 6. Ability to execute deep-space exploration missions including charting and mapping, hostile contact scenarios, intelligence gathering and infiltration missions, full technical, biological and ecological studies.&lt;br /&gt;
*	Ability to support a wide range of mission-related ongoing research and other projects without impact on primary mission operations.&lt;br /&gt;
*	&#039;Full Spectrum EM, optical, subspace flux, Gravimetric, particle, and quark population analysis sensor capability. Multimode neutrino interferometery instrumentation. Wide band life sciences analysis capability. 2 twelve-meter interphasic field focused telescopes.&lt;br /&gt;
*	Upgradeable experiment and sensor array design. Ability to support on-board and probe mounted science and intelligence instrumentation.&lt;br /&gt;
*	Support facilities for auxiliary spacecraft and instrumented probes for short-range operations to include at least 1 independent launch, resupply, and repair bays.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Environment/Crew&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Environmental systems to conform to Starfleet Regulatory Agency (SFRA)- standard 102.9 for Class M compatible oxygen breathing personnel. All life-critical systems to be triply redundant. Life support modules to be replaceable at major Starbase layover to permit vehicle-wide adaptation to Class H, K or L environmental conditions.&lt;br /&gt;
*	Ability to support up to 200 non-crew personnel for mission related operations.&lt;br /&gt;
*	Facilities to support Class M environmental range in all individual living quarters, provisions for 2% of living quarters to be equipped to support Class H, K and L environmental conditions. Additional 1% of living quarters volume to be equipped for Class N and N (2) environmental adaptation.&lt;br /&gt;
*	All habitable volumes to be protected to SFRA-standard 347.3(a) levels for EM and radiation. Subspace flux differential to be maintained within 0.02 millicochranes.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Tactical&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Defensive Shielding to exceed 9.85 X 103 kW primary energy dissipation rate. All tactical Shielding to have full redundancy, with auxiliary system able to provide 75% of primary rating.&lt;br /&gt;
*	Tactical systems to include full array of Type XII phaser bank elements on hull capable of 6.1MW maximum single emitter output. 6 Photon Torpedo launchers required for ship defensive capabilities.&lt;br /&gt;
*	Tactical systems to include anti-detection components capable of defeating sensor and optical scan.&lt;br /&gt;
*	Tactical systems to include variable decreased emissions systems affecting primary and secondary drive systems.&lt;br /&gt;
*	Tactical systems to include components to reproduce or produce false sensor signatures at displaced coordinates in vessel reference.&lt;br /&gt;
*	Tactical systems to include components to produce ambient radiation and gravitational energies consistent with surrounding spatial occurrences.&lt;br /&gt;
*	Tactical systems to include variable EM field dampening systems to reduce or eliminate vessel EM fields and signatures.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Design Life&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Space frame design life of approximately 100 years, assuming approximately 5 major ship- wide system swap outs and upgrades at average intervals of 20 years. Such upgrades help ensure the continuing usefulness of the ship even though significant advances in technology are anticipated during that time. Minor refurbishment and upgrade to occur at approximately one- to five year intervals, depending on specific mission requirements and hardware availability.&lt;br /&gt;
&lt;br /&gt;
==2.0 General Overview==&lt;br /&gt;
&lt;br /&gt;
The Rosenanté class of Starship was originally categorized as an intelligence-gathering vessel. The Rosenanté class is only the second starship class created by Starfleet command to receive this designation. The other is the Spectre Class. While most starships may be adapted for many different mission types, the Rosenanté class starship is designed primarily to perform a single type of mission objective, in effect limiting her overall flexibility within a more generalized Starfleet. Seen from a comfortable distance of two or three kilometres, the starship takes on the resemblance of the more familiar Sovereign class explorers. Upon closer inspection however, one can see that the engineering hull is more sleek, lending a highly manoeuvrable appearance to the Rosenanté class of starship. The engineering hull actually extends both above and below the saucer section, lowering the overall silhouette of the class. Additionally, the saucer section itself boasts a number of changes that are easily noticed even by the most novice of observers. This divorce from standard Starfleet design protocols is both advantageous and disadvantageous for this class of starship. The unique hull design allows an immediate reduction in stresses generated by high warp speeds, while allowing greater manoeuvrability at sub-light speeds. This hull design concept has its drawbacks however, as high speed warp manoeuvrability is reduced in favour of speed. The exterior hull material is stronger, lighter and more durable than that used in standard starship production. This reduces the need for otherwise necessary supports and braces, leaving a greater interior volume for habitation. This material used on the ship&#039;s hull is more difficult to reproduce and repair, as specialized facilities must be implemented to perform these functions.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;2.1 Physical Arrangement&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-2up.jpg|right|300px]]&lt;br /&gt;
&lt;br /&gt;
The hull, remarkably birdlike in its strong, hollow construction, is reinforced against flight stresses by active energy fields that tighten and flex where required to compensate for natural and artificial internal and external forces. Structures integrated into the hull allow for a variety of necessary functions. &lt;br /&gt;
&lt;br /&gt;
The bridge consolidates the command positions for the rest of the starship, windows allow crewmembers needed vistas while in space, phaser arrays and photon torpedoes provide offence and defence against hostile forces, and a specialized communications system allows interaction with other worlds and their ships.&lt;br /&gt;
&lt;br /&gt;
Lifeboats allow for escape in dire emergencies, transporter emitters afford reliable near instant movement of crew and gear, navigational sensors and deflectors give the starship distant vision and a method for clearing obstacles, and powerful warp engines propel the starship at amazing speeds.&lt;br /&gt;
&lt;br /&gt;
The twenty-eight decks are internally divided among major load-bearing structures. A great many systems, especially the habitation sections are suspended within the open spaces, essentially &amp;quot;floating&amp;quot; on flexible ligaments to minimize mechanical, thermal, and conductive radiation shocks.&lt;br /&gt;
&lt;br /&gt;
The living areas of the starship have been designed for maximum comfort and safety while the crew is conducting a mission. Long-term studies of humanoid cultures have revealed that as each race embarked upon permanent occupation of space, large personal living spaces had to be established, especially on early sub-light missions. The Rosenanté class starship allows for some 120 square meters of living space per person, in addition to community space and areas allotted to purely working functions.&lt;br /&gt;
&lt;br /&gt;
==3.0 Spacecraft Structure==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.1 Main Skeletal Structure&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The primary space frame of the Rosenanté class starship is fabricated from an interlocking series of Terminium/Tritium microfilament truss frames. These members average l.05m² in cross section and are capable of bearing the same load as the standard Tritanium/Duranium truss averaging l.27m² in cross section used in standard starship construction. These truss frames are located an average of 20 meters across the ship&#039;s exterior, while the standard trusses would be located every 25 meters along a ships exterior. The tightening of the trusses allows the vessel to withstand greater stress imposed upon it by warp travel, while still producing a lighter space frame.&lt;br /&gt;
&lt;br /&gt;
As with other starship designs, larger numbers of these trusses are located integral to the main impulse engine sections, the warp nacelle pylons, docking interface latches, and along the centerline of the hull structure. Smaller Trusses averaging 0.35m² in cross section are located every five meters on average, and also provide internal supports within the deck and core structure of the spacecraft interior.&lt;br /&gt;
&lt;br /&gt;
A mechanical framework provides physical integrity to the vehicle while at rest. A parallel series of aluminum crystal foam stringers are phase transition bonded to the primary trusses, providing low frequency vibration attenuation across the main truss structure, as well as support for certain utility conduits.&lt;br /&gt;
&lt;br /&gt;
Also attached to these stringers are various conformal devices built into the hulls structure, including elements of the deflector shield grid, H.l.S.S. components, as well as subspace radio antennas, which are incorporated into the skin of the spacecraft.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.2 Secondary Framework&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mounted to the primary space frame is a secondary framework of micro-extruded Terminium trusses to which the inner hull of the structure is directly attached. The secondary framework is mounted by means of 3.2 cm diameter X 5.1 centimeter long semi rigid polydurinide support rods, permitting a limited amount of mechanical isolation from the primary space frame for purposes of strain relief, plus sound and vibration isolation. Secondary space frame segments are also separated from each other (although mechanically attached) to permit replacement of inner hull segments and associated utilities infrastructure during major Starbase layover.&lt;br /&gt;
&lt;br /&gt;
Structural integrity during powered flight is provided by a series of forcefields that reinforce the physical framework. This structural integrity field (SIP) is distributed through a network of molybdenum-jacketed wave-guides, which in turn distribute SIF energy into ceramic-polymer conductive elements throughout the space frame. Without the structural integrity field, the vehicle would be unable to withstand accelerations greater than 3l.4 m/s² without significant deformation, or greater than 49.18 m/s² without unrecoverable structural damage.&lt;br /&gt;
&lt;br /&gt;
Exterior hull substrate is joined to the primary load bearing trusses by means of 4.8-cm diameter electron-bonded duranium pins at 1.01-meter intervals. These pins are slip-fitted into an insulating AGP ceramic fiber jacket that provides thermal insulation between the space frame and the exterior hull. The pins, jacketing, and hull segments are gamma welded together.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.3 Hull Layers&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The exterior of the spacecraft consists of multiple layers, which afford structural and atmospheric integrity for the space frame, integral wave-guides and field conductive members for the structural Integrity Field (SIP) and H.I.S.S components, and pathways for other utilities (including deflector grids), as well as resistance to radiation and thermal energy.&lt;br /&gt;
The exterior shell substrate is composed of interlaced micro-foam duranium filaments. These filaments are gamma welded into a series of contiguous composite segments that are 4.7 cm thick and are typically 2 meters in width. The substrate segments are electron-bonded to three reinforcing layers of 1.2- cm biaxially stressed terranium fabric, which provide additional torsion strength.&lt;br /&gt;
&lt;br /&gt;
In areas immediately adjacent to major structural members, four layers of 2.3-cm fabric are used. The substrate layer is attached to major structural members by electron-bonded duranium fasteners at 2.5-cm intervals. The substrate segments are not intended to be replaceable, except by phase-transition bonding using a transporter assembly jig during major Starbase layovers.&lt;br /&gt;
Two 3.76-cm layers of low-density expanded ceramic-polyrner composites provide thermal insulation and secondary SIP and H.I.S.S. conductivity. These layers are separated by an 8.7-cm multiaxis triennium truss framework, which provides additional thermal insulation and a pass through for fixed utility conduits.&lt;br /&gt;
&lt;br /&gt;
A 4.2-cm layer of monocrystal beryllium silicate infused with somniferous polycarbonate whiskers provides radiation attenuation. This layer is networked with a series of 2.3-cm X 0.85-cm molybdenum-jacketed conduits. These conduits, which occur at 1.3-m intervals, serve as triphase wave-guides for the secondary structural integrity field. Conductive tritium rods penetrate the wave-guides at l0-cm intervals and transfer SIF energy into the ceramic-polymer conductive layer.&lt;br /&gt;
The outermost hull layer is composed of a 1.6-cm sheet of AGP ablative ceramic fabric chemically bonded onto a substrate of 0.15-cm triermium foil. This material is formed into segments approximately 3.7m² and is attached to the radiation attenuation layer by a series of duranium fasteners, which allows individual segments to be replaced as necessary. (Micrometeor erosion is kept to a minimum by the deflector system, but is sufficient to warrant replacement of 30% of the leading edge on the average of every 7.2 standard years.) Individual outer hull segments are machined to a tolerance of ±0.05-mm to allow for minimum drag through the interstellar medium. Joints between segments are manufactured to a tolerance of ±0.025-mm.&lt;br /&gt;
&lt;br /&gt;
Also incorporated into the outermost hull layer is a series of super conducting molybdenum-jacketed wave-guide conduits, which serve to absorb and disperse sensor emission energy that interacts with the hull. Segmented sections of this network serve as housings for the unique DECS components, responsible for producing the ship’s tactical deflector. Unlike a standard starship, there are no thermal regulating assemblies built into the skin of the starship. Instead this duty is regulated through a series of intercoolers and radiators housed inside the interior of the Bussard Collector Assembly.&lt;br /&gt;
&lt;br /&gt;
==4.0 Command Systems==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.1 The Bridge&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Bridge, located on Deck 1, provides primary operational control of the Rosenanté class starship. The bridge directly supervises all primary mission operations and coordinates all departmental activities. These activities are handled through the individual command consoles located in various positions on the bridge. These workstations are modular and can be interchanged, removed, or added as necessary to fulfill specialized mission requirements. At any one time there can be up to 12 workstations installed. The standard bridge design calls for 2 Science Stations, 1 Operations Station, 1 Flight Control Station, l Auxiliary Engineering Station, 1 Tactical station, 1 Communications/ H.I.S.S. station, 1 Internal Security Station, and 2 Command Stations, one each for the ship’s commander, and the First Officer.&lt;br /&gt;
Other facilities located on Deck 1 include Astrogation, the captain&#039;s ready room and head, the crew head, and a small mission briefing room.&lt;br /&gt;
Major connections to the bridge include a pair of Turbolift shafts, four electron-plasma power distribution wave-guide conduits; four environmental support plenum groups, nine primary and two back-up optical data network trunks, two replicator wave-guide conduits, and three service crawlways. As an interesting side note, a tertiary backup power distribution system consisting of hardwired nonreactive, conductive ceramic-polymer relays are also in place.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.2 Display Panels&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The display panels on the bridge and through out the ship are constructed and operated the same as those on any other Federation starship. The layouts and reactivity of the panels are augmented and display properties shown in a different manner. The coloration of the interaction displays is altered to create a different aesthetic affect, while also allowing a variant-programming matrix to be utilized. This new language utilizes advances in Holoprogramming to create three-dimensional matrix strings; this in turn allows a more efficient and quicker computer response time. Critical internal components of the display panels are mapped to the molecular level allowing a replication driven pro-holographic matrix damage control system to repair damaged components. The components necessary to facilitate this activity are collectively known as the &#039;&#039;&#039;Se&#039;&#039;&#039;lf-&#039;&#039;&#039;Re&#039;&#039;&#039;plicating &#039;&#039;&#039;Da&#039;&#039;&#039;mage &#039;&#039;&#039;C&#039;&#039;&#039;ontrol &#039;&#039;&#039;S&#039;&#039;&#039;ystem (&#039;&#039;&#039;SERDACS&#039;&#039;&#039;). The &#039;&#039;&#039;SERDACS&#039;&#039;&#039; components are present in all non-integrity dependant systems throughout the ship. &lt;br /&gt;
&lt;br /&gt;
In addition to the standard anchored display consoles located throughout the ship, a series of Holoemitters have been seeded throughout the vessel to allow ship&#039;s personnel to utilize a holographic interface to tie directly into the ships computer regardless of the location of the crewmember. These emitters also allow the EMH to be activated in any compartment in the ship, and also allow for the construction of holographic crewmembers to fill non-critical positions on the ship. These holoemitters are capable of creating non-electronic tools for emergency use, and in conjunction with replication systems could produce vital simplified component reproduction anywhere aboard ship.&lt;br /&gt;
&lt;br /&gt;
==4.3 Bridge Stations==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.1 Flight Control (CONN)&#039;&#039;&#039; &amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the actual piloting and navigation of the ship. From this station all SIF and IDF systems are monitored, as well as navigational deflectors, and their subsequent systems. This console performs the same functions as it would on board any other Federation starship.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.2 Operations Management (OPS)&#039;&#039;&#039; &amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for power maintenance and resource allocation. This console dictates priority status of all shipboard systems and operations. They coordinate activities between departments and between the ship and away missions. This console performs the same functions as it would on board any other Federation starship.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.3 Tactical Operations (TACOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the operation, monitoring and maintenance of the ship&#039;s tactical systems. These systems include the phaser arrays, the photon torpedo deployment systems, probe	deployment systems, H.I.S.S. system, Signal displacement system, tractor beams, and Tactical deflector systems. The Tactical station aboard the Rosenanté class starship differs from those of standard Federation starships. The main difference is the divorce of the ship&#039;s tactical systems from the internal security systems of the ship. This allows the tactical officer the ability to concentrate on the tactical aspects of the ship without the need to also monitor the internal security status of the ship. Another major difference in the Rosenanté class starship is the addition of a sensor array specifically for use by the tactical officer.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.4 Security Operations (SECOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the monitoring and operation of internal ship security systems. The Operator of this console is responsible for the deployment of ship&#039;s security personnel aboard the ship. This console controls the internal security containment fields, internal ship&#039;s sensors. The SECOPS officer can monitor the security status, security systems and personnel deployment for the entire ship. They can control door mechanisms, containment fields, the turbolift car, and weapons settings of all Federation weaponry on the ship. In addition, security can control personnel access to restricted areas, and utilize sight-to-sight onboard transporters.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.5 Communications (COMMOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the encryption and decryption of intercepted communications, for the transmission of communications, maintaining the Emissions Control Protocols, and the operation of specialized communications interception equipment. The Communications officer is often called upon to triangulate communications sources, decipher enemy transmissions, and encrypt outgoing communications. They often assist in Traffic Analysis of enemy troop deployment, and maintain secure communications with away teams.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.6 Science Stations I &amp;amp; II&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
These consoles are responsible for data collections, primary and lateral sensor operations, and database referencing. It is the responsibility of the science officer to operate the ship&#039;s sensors, teleoptical systems, and imaging systems. They observe, record and document data important to shipboard mission objectives. These stations can be utilized together or separately. This station also acts as the primary database access terminal for the Federation database carried aboard all Federation starships. Both passive and active sensors are controlled from this station.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.7 Auxiliary Engineering Station&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This station is responsible for maintaining and monitoring shipboard systems. This console works in conjunction with main engineering, and is capable of performing the same functions as the computer in that section of the ship. From this station the warp fields can be tuned, altered or monitored, as can all primary and secondary shipboard systems. This station is not always manned.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.8 Command Stations I &amp;amp; II&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
These consoles are responsible for the maintenance and monitoring of the ship&#039;s computer and all primary and secondary systems. Only the commanding and executive officer have access to these consoles. From these consoles the commanding officers can display data concerning ship&#039;s systems, status, condition, position, speed, heading, and power management distribution. These consoles can access the database, and has priority authority over all computer functions. These consoles are the only terminals capable of activating the ship&#039;s self-destruct mechanism. Any officer in command of the starship may utilize these consoles, although some functions may be unavailable.&lt;br /&gt;
&lt;br /&gt;
==5.0 The Computer System==&lt;br /&gt;
The computer system aboard the Rosenanté class starship is identical in construction to the computers used on other Federation Starships. They utilize the same back up and failsafe hardware and communicate through the same methods as the standard starship computer. The computer system of the Rosenanté class starship is composed of 2 synchronized computer cores, identical to those used in the Galaxy Class starship. The only differences between the standard Federation computers and those aboard the Rosenanté are the storage medium and programming language that the system uses to communicate.&lt;br /&gt;
The storage of data and processing networks of a standard Federation computer system depend upon isolinear chips. On the Rosenanté a new type of data storage chip, the Hololinear chip is introduced. Taking advantage of new replication and holographic programming breakthroughs, the new Hololinear chips, or HL chips, allow data to be stored in a four-dimensional, subspace format. A new programming language known a &#039;&#039;&#039;B&#039;&#039;&#039;ilinear &#039;&#039;&#039;U&#039;&#039;&#039;nilateral &#039;&#039;&#039;N&#039;&#039;&#039;etworking &#039;&#039;&#039;C&#039;&#039;&#039;ode (&#039;&#039;&#039;BUNC&#039;&#039;&#039;) allows data to be stored in a temprometric tagged holographic string, thereby allowing data to be stacked almost exponentially upon other data, linked by temprometric strings of associated data. Retrieval time is decreased as the data can be read from any point along its data string, rather than starting at a specified point as is required by the standard isolinear chip design.&lt;br /&gt;
&lt;br /&gt;
==6.0 Warp Propulsion Systems==&lt;br /&gt;
The Warp propulsion system in the Rosenanté class starship is radically different from Those used in other starships. The majority of the system is developed to utilize existing warp technology and materials. There is however a few major changes in the system. All warp engineers are familiar with the laws of warp transition, which dictates that warp geometry and power requirements dictate a vessel&#039;s ability to achieve various levels of warp speed. This same law also dictates that a warp field must be balanced in order to achieve maximum efficiency to make a warp transition.&lt;br /&gt;
&lt;br /&gt;
The Graph below represents the transition energy requirements for the Galaxy Class Starship design and also for that of the Rosenanté class starship.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:RWC.jpg|Thumb|Center|800px|Warp transition chart]]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
ln the chart above the Cochrane values are represented over the white bar for the Rosenanté Class starship. At lower warps (below Warp 6) there is an actual decrease in warp efficiency, although at higher warp there is a worthwhile increase in efficiency, where the differences in efficiency matter most. It is important to note that a Galaxy class starship is incapable of traveling at Warp 9.97, and thus the numbers represented for that class is theoretical.&lt;br /&gt;
&lt;br /&gt;
The ability to sustain warp 9.97 is a result of multiple warp engines working in synchronization and a natural by-product of the embedded nacelle design. The synchronization of the dual warp drive is accomplished through the use of a &#039;&#039;&#039;W&#039;&#039;&#039;arp &#039;&#039;&#039;E&#039;&#039;&#039;nergy &#039;&#039;&#039;Sy&#039;&#039;&#039;nchronization &#039;&#039;&#039;R&#039;&#039;&#039;outer, or &#039;&#039;&#039;WESYR&#039;&#039;&#039;. The &#039;&#039;&#039;WESYR&#039;&#039;&#039; unit is highly classified, but its basic function is to synchronize otherwise out of synch Waveforms created within two near identical meshed Tuned Plasma Streams. Because of the additional energy that this system produces, a higher capacity EPS Power Tap and Series Relays were developed to handle the additional power loads. A dual bypass system allows any single Warp drive to power ships functions, at a significant reduction in overall power. Also a major redesign feature of the upgraded power system resulted in the addition of a second Port and Starboard Power conduit assembly and relay subassembly. This allows the power delivery system to function more efficiently.&lt;br /&gt;
&lt;br /&gt;
Interestingly enough, a bizarre natural byproduct of running a dual synchronized Warp Field is the creation of a &amp;quot;double&amp;quot; warp bubble. These warp bubbles are divided by 2.3-mnm (micronanometers) and help produce the effect of the change of reduction caused when making Warp Transitions. As subspace resistance passes through the Outer shield it is reduced as normal, then again as the remaining resistance passes through the inner bubble, it is further reduced. This causes the starship to experience less resistance and shearing warp stress associated with high rate warp travel and maneuvering.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Spiral Warp Drive&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In addition to the standard warp drive used by all federation starships, the Rosenanté class is also equipped with an experimental Spiral Warp Drive. This drive creates a subspace &amp;quot;tunnel&amp;quot; or &amp;quot;wormhole&amp;quot;  through which the Rosenanté may then travel. The tunnel integrity is maintained by the main deflector dish. The tunnel basically allows the ship to drop into subspace, effectively disappearing from normal space for a short period of time. The speeds that are achieved through the use of this drive are akin to those used by the Borg when using transwarp conduits. Unlike transwarp conduits, however,the tunnel being opened by the Rosenanté would dissipate as soon as the ship moves through it. In a similar manner, the spiral drive can only be used to travel in straight lines. This means that the vessel may make a periodic series of short hops to correct course when using this system.&lt;br /&gt;
&lt;br /&gt;
==7.0 Deflector Emitter Cluster System (DECS) ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-3up.jpg|thumb|left|500px|]]&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;D&#039;&#039;&#039;eflector &#039;&#039;&#039;E&#039;&#039;&#039;mitter &#039;&#039;&#039;C&#039;&#039;&#039;luster &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;DECS&#039;&#039;&#039;, represents the newest Federation breakthroughs in Federation tactical shield technology. This innovative new system utilizes a convex “honeycombed&amp;quot; arrangement of octagonal emitters offset slightly to produce a unified, overlapping tactical field. This primary tactical system allows a tighter tactical shield to be produced, thus resulting in a lessened tactical shield cross section, which in turn reduces starship detectability.&lt;br /&gt;
&lt;br /&gt;
Whereas the Rosenanté class of starship possesses the standard &#039;&#039;&#039;D&#039;&#039;&#039;eflector &#039;&#039;&#039;E&#039;&#039;&#039;mitter &#039;&#039;&#039;A&#039;&#039;&#039;rray (&#039;&#039;&#039;DEA&#039;&#039;&#039;) that all Federation starships do, they use that particular system as a primary shielding system. The &#039;&#039;&#039;DECS&#039;&#039;&#039; assembly operates by producing several smaller polyhedral segments of shield interdependability, rather than creating a &amp;quot;shell&amp;quot; segment standard to all other Federation starships. The &#039;&#039;&#039;DECS&#039;&#039;&#039; requires more power than standard tactical &#039;&#039;&#039;DEA&#039;&#039;&#039; systems, but yields a 20% increase in shield output. The &#039;&#039;&#039;DECS&#039;&#039;&#039; is calibrated to respond and recalibrate the loss of a single emitter or emitter cluster, resulting in a greater overall performance and defensive capability of ship systems. The standard &#039;&#039;&#039;DECS&#039;&#039;&#039; system is installed to provide tactical shielding whenever the starship is experiencing &#039;&#039;&#039;DEA&#039;&#039;&#039; failure, or power requirements do not allow the use of the &#039;&#039;&#039;DEA&#039;&#039;&#039;. Another advantage of the DECS over the standard DEA is its modular design. It is quick and efficient to repair or replace in the field whereas the replacement of the DEA system requires a major overhaul at a Starbase.&lt;br /&gt;
&lt;br /&gt;
==8.0 Hull Integrated Stealth System. ==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;H&#039;&#039;&#039;ull &#039;&#039;&#039;I&#039;&#039;&#039;ntegrated &#039;&#039;&#039;S&#039;&#039;&#039;tealth &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;HISS&#039;&#039;&#039;, is a series of alterations to the ships exterior hull and systems to create a reduced sensor and visual silhouette. The details of the &#039;&#039;&#039;HISS&#039;&#039;&#039; are highly classified, although the general concepts behind its incorporation are not. A network of specialized integrated hull webbing allows the hull to emit energies that effectively allow light waves to pass through it and its contents. In addition to visual bands of radiation, the specially designed ablative hull absorbs sensor energy, while emitting the same energy signature as the starship&#039;s surrounding space. Thus, the vessel becomes virtually undetectable either through detection or complete omission of detection. In addition to this, specialized hull features act as complex Magnetic field disruptors, reducing the EM field of the vessel, and also neutralize radioactive emissions through a complex series of intercoolers and sheathed cowlings. The ship&#039;s Impulse, Thruster and Bussard collection systems are incorporated to nearly negate all detectable signs of their use. When the HISS is active and used in conjunction with strict Emissions protocols, the ship vanishes from visual and sensor detection.&lt;br /&gt;
&lt;br /&gt;
==9.0 Advanced Sensors Systems==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;I&#039;&#039;&#039;mproved &#039;&#039;&#039;S&#039;&#039;&#039;ensor &#039;&#039;&#039;I&#039;&#039;&#039;ntegrated &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;ISIS&#039;&#039;&#039;, is a modified high yield Federation sensor array. The &#039;&#039;&#039;ISIS&#039;&#039;&#039; utilizes the newest development in sensor technology to quantum phase the active and passive ship&#039;s sensors to greatly reduce detectability. These new sensors are more powerful, and almost impossible to detect without performing extensive and time consuming alterations to a starship&#039;s sensor array, which then is useless to detecting other aspects of its surrounding. Some of this technology is loosely based on cloaking principles.&lt;br /&gt;
&lt;br /&gt;
==10.0 Sensor Displacement System==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Se&#039;&#039;&#039;nsor &#039;&#039;&#039;Di&#039;&#039;&#039;splacement &#039;&#039;&#039;S&#039;&#039;&#039;ystem, Or &#039;&#039;&#039;SEDIS&#039;&#039;&#039;, allows the Rosenanté class of starship to offset its actual energy signature, and even produce an additional energy signature. This is designed to improve the starships ability to prevent &amp;quot;true&amp;quot; detection, or to act as a decoy system in the event that the starship is detected. This system is capable of operating within a 60OKm range of the vessel.&lt;br /&gt;
&lt;br /&gt;
==11.0 Displaced Communications System==&lt;br /&gt;
The &#039;&#039;&#039;Di&#039;&#039;&#039;splaced &#039;&#039;&#039;Comm&#039;&#039;&#039;unications &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;DICOMMS&#039;&#039;&#039;, is based on the same technology as the &#039;&#039;&#039;ISIS&#039;&#039;&#039;. This energy is used to send nearly undetectable communications. The Rosenanté class starship is equipped with standard Federation communications systems as well.&lt;br /&gt;
&lt;br /&gt;
==12.0 Interior Systems Modifications==&lt;br /&gt;
There have been a variety of interior alterations to the interior, habitable areas of the Rosenanté class starship. The most apparent alterations are in the functionality of the corridor and turbolift systems. The oversized personnel quarters offer the most luxurious and spacious accommodations aboard any Starfleet posting, while unique interaction software insures crewmembers peace of mind.&lt;br /&gt;
&lt;br /&gt;
Many Starfleet admirals believe that the Tactical and Scientific Equipment carried by a Starship to be the most important asset to any Starfleet facility or starship. The designers of the Rosenanté class of Starship also felt that crew morale would also serve a very integral role in the operation of the starship. To these ends the interactive systems and habitations were designed to provide a reassuring and relaxing environment for the ships crew.&lt;br /&gt;
&lt;br /&gt;
==12.1 Safety Systems==&lt;br /&gt;
The most paramount function of any Starship is the maintenance of its crew in adverse conditions. Integral to this school of thought is the ability to protect the crew under hostile threats. To these ends, the designers of the Rosenanté class starship developed a series of counterinsurgency systems to minimize crew contact with alien forces boarding the vessel.&lt;br /&gt;
&lt;br /&gt;
==12.1.1 Isolation Field Systems==&lt;br /&gt;
The &#039;&#039;&#039;I&#039;&#039;&#039;solation &#039;&#039;&#039;F&#039;&#039;&#039;ield &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;IFS&#039;&#039;&#039;, was designed with the intent to isolate hostile alien forces that boarded the vessel for the crew. This function is considered vitally important when consideration is given to the fact that the Rosenanté class starship possesses a very highly trained crew. The &#039;&#039;&#039;IFS&#039;&#039;&#039; fundamentally isolates the threat through the use of perpetual containment fields, reinforced by miniature shield defenses for the IFS emitter assembly. The &#039;&#039;&#039;IFS&#039;&#039;&#039; is always active, limiting the mobility of non-authorized personnel, securing sensitive sectors of the ship, and effectively hindering the process of any hostile aliens that may manage to board the vessel. The ship&#039;s computer monitors the movements of every official member of the ship&#039;s crew at all times. In this manner, the computer is able to activate or deactivate the &#039;&#039;&#039;IFS&#039;&#039;&#039; screens on an individual basis as needed. This allows authorized crewmembers access to shipboard systems and compartments as needed. The &#039;&#039;&#039;IFS&#039;&#039;&#039; consists of a series of Level 8 containment fields spaced an even 12.5-meters along the corridors of the vessel. In addition to these, an &#039;&#039;&#039;IFS&#039;&#039;&#039; field also isolates each access portal and hatch. In the event that a commbadge should be captured, or fail, that badge is automatically removed from all access rosters, until security can investigate the occurrence.&lt;br /&gt;
&lt;br /&gt;
As a benefit of the perpetually active IFIS fields, studies indicate that shipboard damage caused by fire and/or decompression was drastically reduced. The fields prevented large area decompression, and also limited the range of fire dispersion radically.&lt;br /&gt;
&lt;br /&gt;
Although in larger compartments the &#039;&#039;&#039;IFS&#039;&#039;&#039; system is not perpetual; all compartments are equipped with the capacity to further &amp;quot;compartmentalize&amp;quot; these large open areas. The computer is capable of assessing threats to the crew and equipment of the vessel, and can respond using the &#039;&#039;&#039;IFS&#039;&#039;&#039; system, nearly instantly. The &#039;&#039;&#039;IFS&#039;&#039;&#039; system was designed to operate independently of the ships main power supply when necessary. Each &#039;&#039;&#039;IFS&#039;&#039;&#039; emitter and processor assembly is equipped with an independent high-yield Sodium Kelleride power system. This power cell is further treated with a Potassium Unified catalyst. This allows the production of oxygen as a by-product whenever the secondary power system is operated. This allows a crewmember to be compartmentalized in an otherwise decompressed area to survive asphyxiation and loss of pressure. This secondary power system will allow the full yield operation of the &#039;&#039;&#039;IFS&#039;&#039;&#039; emitter in question for a period of 4 standard hours. Setting the emitter to a lower containment setting can extend this time.&lt;br /&gt;
&lt;br /&gt;
==12.1.2 Fire Suppression Systems==&lt;br /&gt;
&lt;br /&gt;
Although the &#039;&#039;&#039;IFS&#039;&#039;&#039; system hinders the progress of a shipboard fire, it will not necessarily extinguish it. To facilitate this a hybrid field emitter, environmental suppression system was developed. This system isolates the flame from its fuel source using advanced forcefield emissions systems, while simultaneously adjusting the environment around the fire to assist in its suppression. A functional &#039;&#039;&#039;IFS&#039;&#039;&#039; contained area further supports the adjustments, as a smaller area of the ship need be adjusted at any one time. There are certain types of plasma fires that could be unaffected by environmental conditions and or can not be contained in this manner. It is in those situations that the fire suppression systems remove the fire and all affected material through use of the ships sight-to-sight transporters. If this cannot be performed due to a greater risk being imposed on the crew, more conventional methods of fire suppression must be performed.&lt;br /&gt;
&lt;br /&gt;
==12.1.3 Internal Ballistics Dampening Fields==&lt;br /&gt;
In key areas where materials stored aboard ship have the potential to be propelled through sections of the ship, a series of &#039;&#039;&#039;I&#039;&#039;&#039;nternal &#039;&#039;&#039;Ba&#039;&#039;&#039;llistics &#039;&#039;&#039;D&#039;&#039;&#039;ampening Fields, or &#039;&#039;&#039;I-BAD&#039;&#039;&#039; Fields, have been implemented. These fields are found primarily in the armory, cargo bays, Shuttle Bays, storage bays, and personnel quarters. The &#039;&#039;&#039;I-BAD&#039;&#039;&#039; system uses advanced internal sensing equipment specialized to calculate mass and velocity of non-anchored materials. In the event that these materials should be propelled at a speed that the computer should indicate hazardous to crew, then a series of inertial Dampening Fields are erected to reduce the velocity of the offending object. The IDF relays cannot stop a propelled item, although it can shorten its travel distance and relative speed considerably. The sensing systems ignore the movements of personnel. The &#039;&#039;&#039;I-BAD&#039;&#039;&#039; emitters in no way affect the reduction of stresses upon the vessel caused by acceleration, deceleration, or maneuvering.&lt;br /&gt;
&lt;br /&gt;
==12.1.4 Advanced Ergonomics==&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-4up.jpg|thumb|right|500px|]]&lt;br /&gt;
&lt;br /&gt;
Throughout the vessel, specialized memory seating systems have been implemented. These systems monitor the stresses upon the body of the crewmember presently utilizing them and adjust the contact points with the crewmember to minimize physical stresses. All station seating and this material affects standard seating in personnel quarters. The design is such that is can self adjust to allow for non-humanoid crewmembers. The standard bedding and medical bio beds are also adjusted in this manner. This has proven to reduce fatigue and discomfort resulting from prolonged duty shifts. The conceptualization of advanced ergonomic design is further implemented in the layouts and design of the personnel quarters on the ship. Each individual’s quarters are ergonomically designed to his or her unique specifications. The height and shape of interactive systems, the design of the shelving and storage facilities, and the layout of the waste management system are all adjusted to the unique requirements of the compartment owner. Even habitation shape and colour are carefully implemented to create an environment in harmony with its occupant.&lt;br /&gt;
&lt;br /&gt;
==12.1.5 Tactical Sight-to-Sight Transport==&lt;br /&gt;
The ship&#039;s computer possesses the ability to assess tactical breaches in to the vessel&#039;s security. When appropriate, the computer may implement tactical redistribution of security personnel to facilitate the disarmament of tactical threats. The computer determines the size of any aggressive and/or threatening force on the ship, and then determines logical methods of containing and overcoming this threat. The computer is capable of briefing shipboard security personnel on the state of a threat, operating IFIS units, and evacuating non-essential personnel from potential or actual combat areas. The computer can deploy security personnel using sight-to-sight transporters and tactical deployment subroutines. In addition to automatic response to internal tactical threats, the ship&#039;s computer can suggest tactical deployment options for security personnel, utilizing data stored in its memory. This tactical deployment data is only suggested when asked for, and is prepared for planetoid deployment, boarding actions, counter-boarding actions, and sight security. When a medical situation presents itself the same sight-to-sight transporter system can be utilized to transport critical patients to the sickbay.&lt;br /&gt;
&lt;br /&gt;
==12.1.6 Emergency Medical Hologram==&lt;br /&gt;
The Emergency Medical Hologram, as standard to all Federation starships, is also present on the Rosenanté class starship. A series of modifications allows the EMH system to be activated in any habitable portion of the vessel. This function is performed by a series of specialized emitters seeded throughout the ship. Each emitter is equipped with an array of medical scanners and programmed with trauma and first aid protocols. Each emitter assembly is capable of independent operation in the event that power systems become unavailable. The Sodium Kelleride power source can maintain EMH use for 1 hour before expending its charge. When operating normally, the EMH can access the ship&#039;s medical database. When operating independently, only the trauma and first aid subroutines may be accessed. While operating on ship&#039;s systems no more than three EMH programs may be running at any one time. Independent operation is possible among any number of EMH emitters.&lt;br /&gt;
&lt;br /&gt;
==12.1.7 Emergency Replication System==&lt;br /&gt;
The &#039;&#039;&#039;E&#039;&#039;&#039;mergency &#039;&#039;&#039;R&#039;&#039;&#039;eplication &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;ERS&#039;&#039;&#039;, is a series of secondary replicators that operate completely independent of the ships systems. The &#039;&#039;&#039;ERS&#039;&#039;&#039; units are located aft and fore of the starship, two per deck. They are always inert until activated. The &#039;&#039;&#039;ERS&#039;&#039;&#039; system is &amp;quot;hidden&amp;quot; behind corridor paneling, and consists of a single equipment replicator, a single food replicator, an atmospheric condenser, a single medical tricorder, a standard tricorder, and a pair of Class I Phasers. A high-yield Sodium Kelleride Battery that allows light use of the replicators, for a period of 3 days, powers the &#039;&#039;&#039;ERS&#039;&#039;&#039; units. The Tricorders and Phasers are pre-powered, and can be recharged once, using the supplied connections. Accessing the ERS panel will alert security. The Class I phasers require a personal authorization code to be activated. The computer monitors the &#039;&#039;&#039;ERS&#039;&#039;&#039; system very closely, immediately notifying engineering if a problem is detected.&lt;br /&gt;
Although the &#039;&#039;&#039;ERS&#039;&#039;&#039; is a fully functional Replication system, it is programmed to create materials that require very little energy to reproduce. Thus, the food replicators produce only a single nutrient rich disk for consumption. The Tool replicator is limited to equipment that possesses simple physical structures, such as hand tools and only simple electronics materials. Neither replicator system can reproduce power sources, or advanced electronics.&lt;br /&gt;
&lt;br /&gt;
==12.1.8 Emergency Transporters==&lt;br /&gt;
The Rosenanté class starship is equipped with 2 emergency transporters. These transporters are located centrally along the berth and length of the vessel on decks 5 and 15. The emergency transporters are integrated into the primary corridor on the aforementioned decks. All transporter hardware is stowed in the surrounding corridor structures. 20 high-yield Sodium Kelleride Batteries independently power the control operation panel and the emergency transport systems. Each Emergency transporter is also equipped with its own short-range sensor array, for destination determination. The control panel is &amp;quot;hidden&amp;quot; behind the corridor paneling, and floor paneling hides the transporter pad. In order to operate the transporter this floor paneling must be removed. The emergency transporters are each capable of transporting 60 personnel.&lt;br /&gt;
After that there is no power remaining to continue transporter functions. Preparing the Emergency transporters for use alerts security.&lt;br /&gt;
&lt;br /&gt;
==12.2 Medical Bay==&lt;br /&gt;
Due to the number of personnel stationed aboard the Rosenanté class starship, the standard&lt;br /&gt;
Medical Bay arrangement was not utilized. Instead a specialized medical bay was designed to maximize space, while still attending to the variable needs of the ship&#039;s crew. To this end, the sickbay possesses a complete quarantine ward, a single surgical ward, and the central sickbay. A office allows for the CMO to perform administrative tasks without interruption.&lt;br /&gt;
In the surgical area, all the equipment necessary to perform any level of surgery is present. Specialized negative pressure systems allow operations to continue upon contaminated personnel without worry of integrity loss.&lt;br /&gt;
The central medical area is equipped with the newest and most efficient systems that general practice has to offer. A multitude of sensors and medical dedicated processors facilitate medical data gathering, while advanced holographic modeling systems allow hands-off data model construction. Forty Biobeds are located in the Sickbay, which studies indicate was the most efficient number of patients to treat at one time. &lt;br /&gt;
&lt;br /&gt;
In addition to the standard biobeds and Infirmary treatment bay, There are also two dedicated Medical Laboratories, One General Practice Clinical Ward and Three configurable Bays, which can be changed to meet the specific requirements of the medical needs of the vessel.&lt;br /&gt;
&lt;br /&gt;
The Quarantine area is equipped with a series of Biocide units capable of detecting, isolating and destroying over three hundred billion contagions. Negative pressure atmospheric systems, ionic decontamination systems, and bio-phased containment fields guarantee the isolation of harmful contagions. All containment systems in the sickbay are maintained by secondary and tertiary power systems. A medical dedicated replication system allows the creation of any replicable pharmaceutical known to Starfleet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&amp;lt;small&amp;gt;All images compliments of Roger Wackowski&amp;lt;br&amp;gt;Spiral Drive concepts by Anthony Keen&amp;lt;br&amp;gt;All other technical aspects, created, written and designed by Daniel Greene&amp;lt;/small&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
[[Category: Engineering]][[Category: Database]][[Category: Active Ships]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=The_Chimera_Directive&amp;diff=55388</id>
		<title>The Chimera Directive</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=The_Chimera_Directive&amp;diff=55388"/>
		<updated>2012-05-09T16:21:52Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* 7.0 Deflector Emitter Cluster System (DECS) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;  &lt;br /&gt;
  &lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
== 1.0	CHIMERA DIRECTIVE INTRODUCTION ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-1up.jpg|thumb|500px|The Rosenante Class Starship]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1.1 MISSION OBJECTIVES FOR ROSENANTÉ CLASS PROJECT&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Starfleet has long been charged with a broad spectrum of responsibilities to the citizens of the Federation and to the lifeforms of the Galaxy at large. As the volume of explored space continues to grow, and with it the Federation itself, so do Starfleet&#039;s duties. &lt;br /&gt;
&lt;br /&gt;
These duties range from relatively mundane domestic and civil missions, to cultural contact and diplomacy, to defense, to our primary mission of exploration and research. Many of these responsibilities are best carried out with relatively small, specialized ships. Yet there continues to be an ongoing need for an even narrower role vessel to protect the Federation against enemies that would use espionage and subversion to wage war against the Federation.&lt;br /&gt;
&lt;br /&gt;
This particular threat to Federation security is further complicated by political and economic restraints placed upon the Federation caused by the demands of maintaining an active war first against the Cardassian Union and then a Civil War between Doenitz Loyalists and 52nd Fleet seditionists. The Federation had suddenly found itself pressed on many fronts at various levels of engagement, often ill-prepared or incapable of information gathering against potential interior and exterior threats to the continued existence of the Federation.&lt;br /&gt;
&lt;br /&gt;
In response to the alarming number of intelligence related activities conducted against Federation projects, personnel, and equipment by exterior Intelligence Organizations, such as the Tal Shiar, the Dominion Shapeshifters, and The Cardassian Obsidian Order, Starfleet Intelligence has found itself grossly outnumbered, and under-appreciated by Starfleet Command. This lack of interdepartmental cooperation was only strengthened by Starfleet Intelligence&#039;s inability to detect and detain several pro-Revolutionary agents that had managed to infiltrate Starfleet Command, the Council of the President, and several other critical posts within the governmental structure of the Federation. The agents proved to be the first signs of the coming Civil war that would shake the foundations of the United Federation of Planets over the next several years.&lt;br /&gt;
&lt;br /&gt;
These breeches of critical security protocol within the government provided the critics of Starfleet Intelligence with ammunition to pressure Starfleet Command to tighten its control on the Intelligence Department. In late 2390s, with the Cardassian Union pressing their offensive against the Federation, Starfleet Intelligence learned of other threats to the Federation&#039;s continuing existence, as reports began to come into Starfleet Intelligence&#039;s Romulan desk reporting a large number of Romulan Infiltrators had somehow managed to concentrate themselves on the Federation Starships patrolling the Neutral Zone. With reports indicating that the Tal Shiar compromised a large majority of Starships patrolling the Neutral Zone, and with SFI fearing a Romulan Invasion, a massive counter Intelligence operation began. This operation, dubbed Sword and Shield, inserted several dozen Starfleet counterintelligence Specialists onboard the suspected Starships. For the better part of a year, these operatives played a deadly game of cloak and dagger against the expectant Tal Shiar operatives. This massive undertaking resulted in the largest capture of external espionage operatives in Starfleet history, 38 Starfleet officers (including 2 Ship Captains) and 12 Enlisted Starfleet personnel were arrested and charged with espionage against the Federation. 6 Starfleet Intelligence operatives lost their lives in this operation. &lt;br /&gt;
&lt;br /&gt;
It was to this threat that Admiral Rodrigo Doenitz would propose a solution. That solution came in the form of a Starship, dedicated completely to the tasks of espionage and interdiction operations. The vessel would be operated entirely independently of Starfleet command. Only Starfleet Intelligence would have any command authority over the vessel and its missions. This proposal created a scandalous outcry by Starfleet Command Officers, with the end result becoming less than favorable to the Doenitz cause.&lt;br /&gt;
&lt;br /&gt;
However, the dramatic success of Sword and Shield eased the tension against Starfleet Intelligence, and by the end of the War with the Cardassian Union in 2398; Starfleet Command realized the inability of SFI to conduct operations in hostile space, or to operate independently without the immediate assistance of Starship under Starfleet Command authority. It was in August of that year that Admiral Talbot, with the support of Admiral Doenitz proposed the idea of creating a new class of Starship capable of supporting Intelligence operations in hostile space, while simultaneously capable of performing signal, traffic and visual surveillance of facilities, ship movements and communications. Admiral Talbot argued that if SFI were equipped with such a vessel during the War, that the effectiveness of the Cardassian attack against the UFP would have been greatly reduced, if not altogether neutralized. Additionally, Talbot argued, such a ship working in Romulan space would have been priceless in determining the intentions and movements of the Tal Shiar during Operation Sword and Shield.&lt;br /&gt;
&lt;br /&gt;
Admiral Talbot’s conceptual Starship was deemed impossible to build, and also in violation of Starfleet Intelligence Command’s charter and the project was immediately disapproved. But that was not the end of the situation. &lt;br /&gt;
&lt;br /&gt;
Admiral Talbot, through secret channels with the complete support of Admiral Rodrigo Doenitz established a secret construction facility. Through various nefarious means, funds were funneled into the project and experienced Starfleet ship engineers were tasked to assist in developing a new class of Starship that could function efficiently within the confines established by the joint visions held by the two admirals.&lt;br /&gt;
&lt;br /&gt;
A special Starfleet Intelligence Operation was begun in a secret shipyard facility around early 2397. SFI operatives assigned to the operation interviewed and recruited Starship designers from across the Federation, purposely avoiding any designer that had ever worked on a Starship Project for the Federation in the past. These designers, assisted by the technical and personal experiences, of selected Starship Engineers laid down the design parameters for the project.&lt;br /&gt;
&lt;br /&gt;
After Admiral Doenitz’s successful coup, the project would prove to outlive many of its critics. With the full power of the office of the president of the Federation, Doenitz fast tracked his project making it an official Presidential Directive. This Directive was codenamed the Chimera Directive.&lt;br /&gt;
&lt;br /&gt;
The Rosenanté Class Starship designed by the Chimera Directive represents the most advanced design and systems innovations in the Federation. The basic design concept was developed around the Sovereign class and is considered the most advanced evolution of Starfleet Ship design to date.&lt;br /&gt;
&lt;br /&gt;
==Design Objectives==&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;&#039;&#039;Pursuant to Starfleet Intelligence Directive 1045.35, the following objectives have been established for the Rosenanté Class Starship development project:&#039;&#039;&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*	Provide a mobile platform for a wide range of ongoing intelligence and counterintelligence projects.&lt;br /&gt;
*	Provide autonomous capability for full execution of Starfleet Intelligence policy and directive options in hostile areas of space.&lt;br /&gt;
*	Incorporate recent advances in technology and protocols.&lt;br /&gt;
&lt;br /&gt;
To provide for these objectives, the Designers recommended that the Rosenanté class starship meets or exceeds the design goals in the following specification Categories;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Propulsion&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Sustainable cruise Velocity of Warp Factor 9.4. Ability to maintain speeds of up to Warp Factor 9.7 for periods of up to 12 Hours.&lt;br /&gt;
*	Sixth-phase dilithium controlled matter/antimatter reactor for primary power. Sustainable field output to exceed 1, 650 cochranes, peak transitional surge reserve to exceed 4,225% of nominal output. (170ns phase)&lt;br /&gt;
*	Warp Driver coils efficiency to meet or exceed 98% at speeds up to Warp 8.0. Minimum efficiency of 68% to be maintained through Warp 9.4. Life cycle of all primary coil elements to meet or exceed 1,200,000 cochrane-hours between neutron purge refurbishment. Secondary coil elements to meet or exceed 2,000,000 cochrane-hours between neutron purge refurbishment.&lt;br /&gt;
*	Warp field geometry to incorporate modified 85° Z-axis compression characteristics on forward warp lobe for increased peak transitional efficiency at high warp. Warp Nacelle centerlines to conform to 2.56: 1.1 ratio of separation to maximize field strength.&lt;br /&gt;
*	Secondary (impulse) propulsion systems to provide sub-light velocities up to and including .92 light speed (c). Engine systems of choice to include but not limited to at least two YPS 8063 fusion drive motors. All units to be equipped with subspace drive accelerators, field output not less than 180 millicochranes at 1.02 X l0³K. Reactor Modules to be field replaceable.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Mission&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Ability to operate independent of Starbase refurbishment for moderate periods of time. Independent operation mode capability of 1 Standard years at nominal Warp 6. Ability to execute deep-space exploration missions including charting and mapping, hostile contact scenarios, intelligence gathering and infiltration missions, full technical, biological and ecological studies.&lt;br /&gt;
*	Ability to support a wide range of mission-related ongoing research and other projects without impact on primary mission operations.&lt;br /&gt;
*	&#039;Full Spectrum EM, optical, subspace flux, Gravimetric, particle, and quark population analysis sensor capability. Multimode neutrino interferometery instrumentation. Wide band life sciences analysis capability. 2 twelve-meter interphasic field focused telescopes.&lt;br /&gt;
*	Upgradeable experiment and sensor array design. Ability to support on-board and probe mounted science and intelligence instrumentation.&lt;br /&gt;
*	Support facilities for auxiliary spacecraft and instrumented probes for short-range operations to include at least 1 independent launch, resupply, and repair bays.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Environment/Crew&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Environmental systems to conform to Starfleet Regulatory Agency (SFRA)- standard 102.9 for Class M compatible oxygen breathing personnel. All life-critical systems to be triply redundant. Life support modules to be replaceable at major Starbase layover to permit vehicle-wide adaptation to Class H, K or L environmental conditions.&lt;br /&gt;
*	Ability to support up to 200 non-crew personnel for mission related operations.&lt;br /&gt;
*	Facilities to support Class M environmental range in all individual living quarters, provisions for 2% of living quarters to be equipped to support Class H, K and L environmental conditions. Additional 1% of living quarters volume to be equipped for Class N and N (2) environmental adaptation.&lt;br /&gt;
*	All habitable volumes to be protected to SFRA-standard 347.3(a) levels for EM and radiation. Subspace flux differential to be maintained within 0.02 millicochranes.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Tactical&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Defensive Shielding to exceed 9.85 X 103 kW primary energy dissipation rate. All tactical Shielding to have full redundancy, with auxiliary system able to provide 75% of primary rating.&lt;br /&gt;
*	Tactical systems to include full array of Type XII phaser bank elements on hull capable of 6.1MW maximum single emitter output. 6 Photon Torpedo launchers required for ship defensive capabilities.&lt;br /&gt;
*	Tactical systems to include anti-detection components capable of defeating sensor and optical scan.&lt;br /&gt;
*	Tactical systems to include variable decreased emissions systems affecting primary and secondary drive systems.&lt;br /&gt;
*	Tactical systems to include components to reproduce or produce false sensor signatures at displaced coordinates in vessel reference.&lt;br /&gt;
*	Tactical systems to include components to produce ambient radiation and gravitational energies consistent with surrounding spatial occurrences.&lt;br /&gt;
*	Tactical systems to include variable EM field dampening systems to reduce or eliminate vessel EM fields and signatures.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Design Life&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Space frame design life of approximately 100 years, assuming approximately 5 major ship- wide system swap outs and upgrades at average intervals of 20 years. Such upgrades help ensure the continuing usefulness of the ship even though significant advances in technology are anticipated during that time. Minor refurbishment and upgrade to occur at approximately one- to five year intervals, depending on specific mission requirements and hardware availability.&lt;br /&gt;
&lt;br /&gt;
==2.0 General Overview==&lt;br /&gt;
&lt;br /&gt;
The Rosenanté class of Starship was originally categorized as an intelligence-gathering vessel. The Rosenanté class is only the second starship class created by Starfleet command to receive this designation. The other is the Spectre Class. While most starships may be adapted for many different mission types, the Rosenanté class starship is designed primarily to perform a single type of mission objective, in effect limiting her overall flexibility within a more generalized Starfleet. Seen from a comfortable distance of two or three kilometres, the starship takes on the resemblance of the more familiar Sovereign class explorers. Upon closer inspection however, one can see that the engineering hull is more sleek, lending a highly manoeuvrable appearance to the Rosenanté class of starship. The engineering hull actually extends both above and below the saucer section, lowering the overall silhouette of the class. Additionally, the saucer section itself boasts a number of changes that are easily noticed even by the most novice of observers. This divorce from standard Starfleet design protocols is both advantageous and disadvantageous for this class of starship. The unique hull design allows an immediate reduction in stresses generated by high warp speeds, while allowing greater manoeuvrability at sub-light speeds. This hull design concept has its drawbacks however, as high speed warp manoeuvrability is reduced in favour of speed. The exterior hull material is stronger, lighter and more durable than that used in standard starship production. This reduces the need for otherwise necessary supports and braces, leaving a greater interior volume for habitation. This material used on the ship&#039;s hull is more difficult to reproduce and repair, as specialized facilities must be implemented to perform these functions.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;2.1 Physical Arrangement&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-2up.jpg|right|300px]]&lt;br /&gt;
&lt;br /&gt;
The hull, remarkably birdlike in its strong, hollow construction, is reinforced against flight stresses by active energy fields that tighten and flex where required to compensate for natural and artificial internal and external forces. Structures integrated into the hull allow for a variety of necessary functions. &lt;br /&gt;
&lt;br /&gt;
The bridge consolidates the command positions for the rest of the starship, windows allow crewmembers needed vistas while in space, phaser arrays and photon torpedoes provide offence and defence against hostile forces, and a specialized communications system allows interaction with other worlds and their ships.&lt;br /&gt;
&lt;br /&gt;
Lifeboats allow for escape in dire emergencies, transporter emitters afford reliable near instant movement of crew and gear, navigational sensors and deflectors give the starship distant vision and a method for clearing obstacles, and powerful warp engines propel the starship at amazing speeds.&lt;br /&gt;
&lt;br /&gt;
The twenty-eight decks are internally divided among major load-bearing structures. A great many systems, especially the habitation sections are suspended within the open spaces, essentially &amp;quot;floating&amp;quot; on flexible ligaments to minimize mechanical, thermal, and conductive radiation shocks.&lt;br /&gt;
&lt;br /&gt;
The living areas of the starship have been designed for maximum comfort and safety while the crew is conducting a mission. Long-term studies of humanoid cultures have revealed that as each race embarked upon permanent occupation of space, large personal living spaces had to be established, especially on early sub-light missions. The Rosenanté class starship allows for some 120 square meters of living space per person, in addition to community space and areas allotted to purely working functions.&lt;br /&gt;
&lt;br /&gt;
==3.0 Spacecraft Structure==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.1 Main Skeletal Structure&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The primary space frame of the Rosenanté class starship is fabricated from an interlocking series of Terminium/Tritium microfilament truss frames. These members average l.05m² in cross section and are capable of bearing the same load as the standard Tritanium/Duranium truss averaging l.27m² in cross section used in standard starship construction. These truss frames are located an average of 20 meters across the ship&#039;s exterior, while the standard trusses would be located every 25 meters along a ships exterior. The tightening of the trusses allows the vessel to withstand greater stress imposed upon it by warp travel, while still producing a lighter space frame.&lt;br /&gt;
&lt;br /&gt;
As with other starship designs, larger numbers of these trusses are located integral to the main impulse engine sections, the warp nacelle pylons, docking interface latches, and along the centerline of the hull structure. Smaller Trusses averaging 0.35m² in cross section are located every five meters on average, and also provide internal supports within the deck and core structure of the spacecraft interior.&lt;br /&gt;
&lt;br /&gt;
A mechanical framework provides physical integrity to the vehicle while at rest. A parallel series of aluminum crystal foam stringers are phase transition bonded to the primary trusses, providing low frequency vibration attenuation across the main truss structure, as well as support for certain utility conduits.&lt;br /&gt;
&lt;br /&gt;
Also attached to these stringers are various conformal devices built into the hulls structure, including elements of the deflector shield grid, H.l.S.S. components, as well as subspace radio antennas, which are incorporated into the skin of the spacecraft.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.2 Secondary Framework&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mounted to the primary space frame is a secondary framework of micro-extruded Terminium trusses to which the inner hull of the structure is directly attached. The secondary framework is mounted by means of 3.2 cm diameter X 5.1 centimeter long semi rigid polydurinide support rods, permitting a limited amount of mechanical isolation from the primary space frame for purposes of strain relief, plus sound and vibration isolation. Secondary space frame segments are also separated from each other (although mechanically attached) to permit replacement of inner hull segments and associated utilities infrastructure during major Starbase layover.&lt;br /&gt;
&lt;br /&gt;
Structural integrity during powered flight is provided by a series of forcefields that reinforce the physical framework. This structural integrity field (SIP) is distributed through a network of molybdenum-jacketed wave-guides, which in turn distribute SIF energy into ceramic-polymer conductive elements throughout the space frame. Without the structural integrity field, the vehicle would be unable to withstand accelerations greater than 3l.4 m/s² without significant deformation, or greater than 49.18 m/s² without unrecoverable structural damage.&lt;br /&gt;
&lt;br /&gt;
Exterior hull substrate is joined to the primary load bearing trusses by means of 4.8-cm diameter electron-bonded duranium pins at 1.01-meter intervals. These pins are slip-fitted into an insulating AGP ceramic fiber jacket that provides thermal insulation between the space frame and the exterior hull. The pins, jacketing, and hull segments are gamma welded together.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.3 Hull Layers&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The exterior of the spacecraft consists of multiple layers, which afford structural and atmospheric integrity for the space frame, integral wave-guides and field conductive members for the structural Integrity Field (SIP) and H.I.S.S components, and pathways for other utilities (including deflector grids), as well as resistance to radiation and thermal energy.&lt;br /&gt;
The exterior shell substrate is composed of interlaced micro-foam duranium filaments. These filaments are gamma welded into a series of contiguous composite segments that are 4.7 cm thick and are typically 2 meters in width. The substrate segments are electron-bonded to three reinforcing layers of 1.2- cm biaxially stressed terranium fabric, which provide additional torsion strength.&lt;br /&gt;
&lt;br /&gt;
In areas immediately adjacent to major structural members, four layers of 2.3-cm fabric are used. The substrate layer is attached to major structural members by electron-bonded duranium fasteners at 2.5-cm intervals. The substrate segments are not intended to be replaceable, except by phase-transition bonding using a transporter assembly jig during major Starbase layovers.&lt;br /&gt;
Two 3.76-cm layers of low-density expanded ceramic-polyrner composites provide thermal insulation and secondary SIP and H.I.S.S. conductivity. These layers are separated by an 8.7-cm multiaxis triennium truss framework, which provides additional thermal insulation and a pass through for fixed utility conduits.&lt;br /&gt;
&lt;br /&gt;
A 4.2-cm layer of monocrystal beryllium silicate infused with somniferous polycarbonate whiskers provides radiation attenuation. This layer is networked with a series of 2.3-cm X 0.85-cm molybdenum-jacketed conduits. These conduits, which occur at 1.3-m intervals, serve as triphase wave-guides for the secondary structural integrity field. Conductive tritium rods penetrate the wave-guides at l0-cm intervals and transfer SIF energy into the ceramic-polymer conductive layer.&lt;br /&gt;
The outermost hull layer is composed of a 1.6-cm sheet of AGP ablative ceramic fabric chemically bonded onto a substrate of 0.15-cm triermium foil. This material is formed into segments approximately 3.7m² and is attached to the radiation attenuation layer by a series of duranium fasteners, which allows individual segments to be replaced as necessary. (Micrometeor erosion is kept to a minimum by the deflector system, but is sufficient to warrant replacement of 30% of the leading edge on the average of every 7.2 standard years.) Individual outer hull segments are machined to a tolerance of ±0.05-mm to allow for minimum drag through the interstellar medium. Joints between segments are manufactured to a tolerance of ±0.025-mm.&lt;br /&gt;
&lt;br /&gt;
Also incorporated into the outermost hull layer is a series of super conducting molybdenum-jacketed wave-guide conduits, which serve to absorb and disperse sensor emission energy that interacts with the hull. Segmented sections of this network serve as housings for the unique DECS components, responsible for producing the ship’s tactical deflector. Unlike a standard starship, there are no thermal regulating assemblies built into the skin of the starship. Instead this duty is regulated through a series of intercoolers and radiators housed inside the interior of the Bussard Collector Assembly.&lt;br /&gt;
&lt;br /&gt;
==4.0 Command Systems==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.1 The Bridge&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Bridge, located on Deck 1, provides primary operational control of the Rosenanté class starship. The bridge directly supervises all primary mission operations and coordinates all departmental activities. These activities are handled through the individual command consoles located in various positions on the bridge. These workstations are modular and can be interchanged, removed, or added as necessary to fulfill specialized mission requirements. At any one time there can be up to 12 workstations installed. The standard bridge design calls for 2 Science Stations, 1 Operations Station, 1 Flight Control Station, l Auxiliary Engineering Station, 1 Tactical station, 1 Communications/ H.I.S.S. station, 1 Internal Security Station, and 2 Command Stations, one each for the ship’s commander, and the First Officer.&lt;br /&gt;
Other facilities located on Deck 1 include Astrogation, the captain&#039;s ready room and head, the crew head, and a small mission briefing room.&lt;br /&gt;
Major connections to the bridge include a pair of Turbolift shafts, four electron-plasma power distribution wave-guide conduits; four environmental support plenum groups, nine primary and two back-up optical data network trunks, two replicator wave-guide conduits, and three service crawlways. As an interesting side note, a tertiary backup power distribution system consisting of hardwired nonreactive, conductive ceramic-polymer relays are also in place.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.2 Display Panels&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The display panels on the bridge and through out the ship are constructed and operated the same as those on any other Federation starship. The layouts and reactivity of the panels are augmented and display properties shown in a different manner. The coloration of the interaction displays is altered to create a different aesthetic affect, while also allowing a variant-programming matrix to be utilized. This new language utilizes advances in Holoprogramming to create three-dimensional matrix strings; this in turn allows a more efficient and quicker computer response time. Critical internal components of the display panels are mapped to the molecular level allowing a replication driven pro-holographic matrix damage control system to repair damaged components. The components necessary to facilitate this activity are collectively known as the &#039;&#039;&#039;Se&#039;&#039;&#039;lf-&#039;&#039;&#039;Re&#039;&#039;&#039;plicating &#039;&#039;&#039;Da&#039;&#039;&#039;mage &#039;&#039;&#039;C&#039;&#039;&#039;ontrol &#039;&#039;&#039;S&#039;&#039;&#039;ystem (&#039;&#039;&#039;SERDACS&#039;&#039;&#039;). The &#039;&#039;&#039;SERDACS&#039;&#039;&#039; components are present in all non-integrity dependant systems throughout the ship. &lt;br /&gt;
&lt;br /&gt;
In addition to the standard anchored display consoles located throughout the ship, a series of Holoemitters have been seeded throughout the vessel to allow ship&#039;s personnel to utilize a holographic interface to tie directly into the ships computer regardless of the location of the crewmember. These emitters also allow the EMH to be activated in any compartment in the ship, and also allow for the construction of holographic crewmembers to fill non-critical positions on the ship. These holoemitters are capable of creating non-electronic tools for emergency use, and in conjunction with replication systems could produce vital simplified component reproduction anywhere aboard ship.&lt;br /&gt;
&lt;br /&gt;
==4.3 Bridge Stations==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.1 Flight Control (CONN)&#039;&#039;&#039; &amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the actual piloting and navigation of the ship. From this station all SIF and IDF systems are monitored, as well as navigational deflectors, and their subsequent systems. This console performs the same functions as it would on board any other Federation starship.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.2 Operations Management (OPS)&#039;&#039;&#039; &amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for power maintenance and resource allocation. This console dictates priority status of all shipboard systems and operations. They coordinate activities between departments and between the ship and away missions. This console performs the same functions as it would on board any other Federation starship.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.3 Tactical Operations (TACOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the operation, monitoring and maintenance of the ship&#039;s tactical systems. These systems include the phaser arrays, the photon torpedo deployment systems, probe	deployment systems, H.I.S.S. system, Signal displacement system, tractor beams, and Tactical deflector systems. The Tactical station aboard the Rosenanté class starship differs from those of standard Federation starships. The main difference is the divorce of the ship&#039;s tactical systems from the internal security systems of the ship. This allows the tactical officer the ability to concentrate on the tactical aspects of the ship without the need to also monitor the internal security status of the ship. Another major difference in the Rosenanté class starship is the addition of a sensor array specifically for use by the tactical officer.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.4 Security Operations (SECOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the monitoring and operation of internal ship security systems. The Operator of this console is responsible for the deployment of ship&#039;s security personnel aboard the ship. This console controls the internal security containment fields, internal ship&#039;s sensors. The SECOPS officer can monitor the security status, security systems and personnel deployment for the entire ship. They can control door mechanisms, containment fields, the turbolift car, and weapons settings of all Federation weaponry on the ship. In addition, security can control personnel access to restricted areas, and utilize sight-to-sight onboard transporters.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.5 Communications (COMMOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the encryption and decryption of intercepted communications, for the transmission of communications, maintaining the Emissions Control Protocols, and the operation of specialized communications interception equipment. The Communications officer is often called upon to triangulate communications sources, decipher enemy transmissions, and encrypt outgoing communications. They often assist in Traffic Analysis of enemy troop deployment, and maintain secure communications with away teams.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.6 Science Stations I &amp;amp; II&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
These consoles are responsible for data collections, primary and lateral sensor operations, and database referencing. It is the responsibility of the science officer to operate the ship&#039;s sensors, teleoptical systems, and imaging systems. They observe, record and document data important to shipboard mission objectives. These stations can be utilized together or separately. This station also acts as the primary database access terminal for the Federation database carried aboard all Federation starships. Both passive and active sensors are controlled from this station.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.7 Auxiliary Engineering Station&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This station is responsible for maintaining and monitoring shipboard systems. This console works in conjunction with main engineering, and is capable of performing the same functions as the computer in that section of the ship. From this station the warp fields can be tuned, altered or monitored, as can all primary and secondary shipboard systems. This station is not always manned.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.8 Command Stations I &amp;amp; II&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
These consoles are responsible for the maintenance and monitoring of the ship&#039;s computer and all primary and secondary systems. Only the commanding and executive officer have access to these consoles. From these consoles the commanding officers can display data concerning ship&#039;s systems, status, condition, position, speed, heading, and power management distribution. These consoles can access the database, and has priority authority over all computer functions. These consoles are the only terminals capable of activating the ship&#039;s self-destruct mechanism. Any officer in command of the starship may utilize these consoles, although some functions may be unavailable.&lt;br /&gt;
&lt;br /&gt;
==5.0 The Computer System==&lt;br /&gt;
The computer system aboard the Rosenanté class starship is identical in construction to the computers used on other Federation Starships. They utilize the same back up and failsafe hardware and communicate through the same methods as the standard starship computer. The computer system of the Rosenanté class starship is composed of 2 synchronized computer cores, identical to those used in the Galaxy Class starship. The only differences between the standard Federation computers and those aboard the Rosenanté are the storage medium and programming language that the system uses to communicate.&lt;br /&gt;
The storage of data and processing networks of a standard Federation computer system depend upon isolinear chips. On the Rosenanté a new type of data storage chip, the Hololinear chip is introduced. Taking advantage of new replication and holographic programming breakthroughs, the new Hololinear chips, or HL chips, allow data to be stored in a four-dimensional, subspace format. A new programming language known a &#039;&#039;&#039;B&#039;&#039;&#039;ilinear &#039;&#039;&#039;U&#039;&#039;&#039;nilateral &#039;&#039;&#039;N&#039;&#039;&#039;etworking &#039;&#039;&#039;C&#039;&#039;&#039;ode (&#039;&#039;&#039;BUNC&#039;&#039;&#039;) allows data to be stored in a temprometric tagged holographic string, thereby allowing data to be stacked almost exponentially upon other data, linked by temprometric strings of associated data. Retrieval time is decreased as the data can be read from any point along its data string, rather than starting at a specified point as is required by the standard isolinear chip design.&lt;br /&gt;
&lt;br /&gt;
==6.0 Warp Propulsion Systems==&lt;br /&gt;
The Warp propulsion system in the Rosenanté class starship is radically different from Those used in other starships. The majority of the system is developed to utilize existing warp technology and materials. There is however a few major changes in the system. All warp engineers are familiar with the laws of warp transition, which dictates that warp geometry and power requirements dictate a vessel&#039;s ability to achieve various levels of warp speed. This same law also dictates that a warp field must be balanced in order to achieve maximum efficiency to make a warp transition.&lt;br /&gt;
&lt;br /&gt;
The Graph below represents the transition energy requirements for the Galaxy Class Starship design and also for that of the Rosenanté class starship.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:RWC.jpg|Center|400px]]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
ln the chart above the Cochrane values are represented over the white bar for the Rosenanté Class starship. At lower warps (below Warp 6) there is an actual decrease in warp efficiency, although at higher warp there is a worthwhile increase in efficiency, where the differences in efficiency matter most. It is important to note that a Galaxy class starship is incapable of traveling at Warp 9.97, and thus the numbers represented for that class is theoretical.&lt;br /&gt;
&lt;br /&gt;
The ability to sustain warp 9.97 is a result of multiple warp engines working in synchronization and a natural by-product of the embedded nacelle design. The synchronization of the dual warp drive is accomplished through the use of a &#039;&#039;&#039;W&#039;&#039;&#039;arp &#039;&#039;&#039;E&#039;&#039;&#039;nergy &#039;&#039;&#039;Sy&#039;&#039;&#039;nchronization &#039;&#039;&#039;R&#039;&#039;&#039;outer, or &#039;&#039;&#039;WESYR&#039;&#039;&#039;. The &#039;&#039;&#039;WESYR&#039;&#039;&#039; unit is highly classified, but its basic function is to synchronize otherwise out of synch Waveforms created within two near identical meshed Tuned Plasma Streams. Because of the additional energy that this system produces, a higher capacity EPS Power Tap and Series Relays were developed to handle the additional power loads. A dual bypass system allows any single Warp drive to power ships functions, at a significant reduction in overall power. Also a major redesign feature of the upgraded power system resulted in the addition of a second Port and Starboard Power conduit assembly and relay subassembly. This allows the power delivery system to function more efficiently.&lt;br /&gt;
&lt;br /&gt;
Interestingly enough, a bizarre natural byproduct of running a dual synchronized Warp Field is the creation of a &amp;quot;double&amp;quot; warp bubble. These warp bubbles are divided by 2.3-mnm (micronanometers) and help produce the effect of the change of reduction caused when making Warp Transitions. As subspace resistance passes through the Outer shield it is reduced as normal, then again as the remaining resistance passes through the inner bubble, it is further reduced. This causes the starship to experience less resistance and shearing warp stress associated with high rate warp travel and maneuvering.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Spiral Warp Drive&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In addition to the standard warp drive used by all federation starships, the Rosenanté class is also equipped with an experimental Spiral Warp Drive. This drive creates a subspace &amp;quot;tunnel&amp;quot; or &amp;quot;wormhole&amp;quot;  through which the Rosenanté may then travel. The tunnel integrity is maintained by the main deflector dish. The tunnel basically allows the ship to drop into subspace, effectively disappearing from normal space for a short period of time. The speeds that are achieved through the use of this drive are akin to those used by the Borg when using transwarp conduits. Unlike transwarp conduits, however,the tunnel being opened by the Rosenanté would dissipate as soon as the ship moves through it. In a similar manner, the spiral drive can only be used to travel in straight lines. This means that the vessel may make a periodic series of short hops to correct course when using this system.&lt;br /&gt;
&lt;br /&gt;
==7.0 Deflector Emitter Cluster System (DECS) ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-3up.jpg|thumb|left|500px|]]&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;D&#039;&#039;&#039;eflector &#039;&#039;&#039;E&#039;&#039;&#039;mitter &#039;&#039;&#039;C&#039;&#039;&#039;luster &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;DECS&#039;&#039;&#039;, represents the newest Federation breakthroughs in Federation tactical shield technology. This innovative new system utilizes a convex “honeycombed&amp;quot; arrangement of octagonal emitters offset slightly to produce a unified, overlapping tactical field. This primary tactical system allows a tighter tactical shield to be produced, thus resulting in a lessened tactical shield cross section, which in turn reduces starship detectability.&lt;br /&gt;
&lt;br /&gt;
Whereas the Rosenanté class of starship possesses the standard &#039;&#039;&#039;D&#039;&#039;&#039;eflector &#039;&#039;&#039;E&#039;&#039;&#039;mitter &#039;&#039;&#039;A&#039;&#039;&#039;rray (&#039;&#039;&#039;DEA&#039;&#039;&#039;) that all Federation starships do, they use that particular system as a primary shielding system. The &#039;&#039;&#039;DECS&#039;&#039;&#039; assembly operates by producing several smaller polyhedral segments of shield interdependability, rather than creating a &amp;quot;shell&amp;quot; segment standard to all other Federation starships. The &#039;&#039;&#039;DECS&#039;&#039;&#039; requires more power than standard tactical &#039;&#039;&#039;DEA&#039;&#039;&#039; systems, but yields a 20% increase in shield output. The &#039;&#039;&#039;DECS&#039;&#039;&#039; is calibrated to respond and recalibrate the loss of a single emitter or emitter cluster, resulting in a greater overall performance and defensive capability of ship systems. The standard &#039;&#039;&#039;DECS&#039;&#039;&#039; system is installed to provide tactical shielding whenever the starship is experiencing &#039;&#039;&#039;DEA&#039;&#039;&#039; failure, or power requirements do not allow the use of the &#039;&#039;&#039;DEA&#039;&#039;&#039;. Another advantage of the DECS over the standard DEA is its modular design. It is quick and efficient to repair or replace in the field whereas the replacement of the DEA system requires a major overhaul at a Starbase.&lt;br /&gt;
&lt;br /&gt;
==8.0 Hull Integrated Stealth System. ==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;H&#039;&#039;&#039;ull &#039;&#039;&#039;I&#039;&#039;&#039;ntegrated &#039;&#039;&#039;S&#039;&#039;&#039;tealth &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;HISS&#039;&#039;&#039;, is a series of alterations to the ships exterior hull and systems to create a reduced sensor and visual silhouette. The details of the &#039;&#039;&#039;HISS&#039;&#039;&#039; are highly classified, although the general concepts behind its incorporation are not. A network of specialized integrated hull webbing allows the hull to emit energies that effectively allow light waves to pass through it and its contents. In addition to visual bands of radiation, the specially designed ablative hull absorbs sensor energy, while emitting the same energy signature as the starship&#039;s surrounding space. Thus, the vessel becomes virtually undetectable either through detection or complete omission of detection. In addition to this, specialized hull features act as complex Magnetic field disruptors, reducing the EM field of the vessel, and also neutralize radioactive emissions through a complex series of intercoolers and sheathed cowlings. The ship&#039;s Impulse, Thruster and Bussard collection systems are incorporated to nearly negate all detectable signs of their use. When the HISS is active and used in conjunction with strict Emissions protocols, the ship vanishes from visual and sensor detection.&lt;br /&gt;
&lt;br /&gt;
==9.0 Advanced Sensors Systems==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;I&#039;&#039;&#039;mproved &#039;&#039;&#039;S&#039;&#039;&#039;ensor &#039;&#039;&#039;I&#039;&#039;&#039;ntegrated &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;ISIS&#039;&#039;&#039;, is a modified high yield Federation sensor array. The &#039;&#039;&#039;ISIS&#039;&#039;&#039; utilizes the newest development in sensor technology to quantum phase the active and passive ship&#039;s sensors to greatly reduce detectability. These new sensors are more powerful, and almost impossible to detect without performing extensive and time consuming alterations to a starship&#039;s sensor array, which then is useless to detecting other aspects of its surrounding. Some of this technology is loosely based on cloaking principles.&lt;br /&gt;
&lt;br /&gt;
==10.0 Sensor Displacement System==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Se&#039;&#039;&#039;nsor &#039;&#039;&#039;Di&#039;&#039;&#039;splacement &#039;&#039;&#039;S&#039;&#039;&#039;ystem, Or &#039;&#039;&#039;SEDIS&#039;&#039;&#039;, allows the Rosenanté class of starship to offset its actual energy signature, and even produce an additional energy signature. This is designed to improve the starships ability to prevent &amp;quot;true&amp;quot; detection, or to act as a decoy system in the event that the starship is detected. This system is capable of operating within a 60OKm range of the vessel.&lt;br /&gt;
&lt;br /&gt;
==11.0 Displaced Communications System==&lt;br /&gt;
The &#039;&#039;&#039;Di&#039;&#039;&#039;splaced &#039;&#039;&#039;Comm&#039;&#039;&#039;unications &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;DICOMMS&#039;&#039;&#039;, is based on the same technology as the &#039;&#039;&#039;ISIS&#039;&#039;&#039;. This energy is used to send nearly undetectable communications. The Rosenanté class starship is equipped with standard Federation communications systems as well.&lt;br /&gt;
&lt;br /&gt;
==12.0 Interior Systems Modifications==&lt;br /&gt;
There have been a variety of interior alterations to the interior, habitable areas of the Rosenanté class starship. The most apparent alterations are in the functionality of the corridor and turbolift systems. The oversized personnel quarters offer the most luxurious and spacious accommodations aboard any Starfleet posting, while unique interaction software insures crewmembers peace of mind.&lt;br /&gt;
&lt;br /&gt;
Many Starfleet admirals believe that the Tactical and Scientific Equipment carried by a Starship to be the most important asset to any Starfleet facility or starship. The designers of the Rosenanté class of Starship also felt that crew morale would also serve a very integral role in the operation of the starship. To these ends the interactive systems and habitations were designed to provide a reassuring and relaxing environment for the ships crew.&lt;br /&gt;
&lt;br /&gt;
==12.1 Safety Systems==&lt;br /&gt;
The most paramount function of any Starship is the maintenance of its crew in adverse conditions. Integral to this school of thought is the ability to protect the crew under hostile threats. To these ends, the designers of the Rosenanté class starship developed a series of counterinsurgency systems to minimize crew contact with alien forces boarding the vessel.&lt;br /&gt;
&lt;br /&gt;
==12.1.1 Isolation Field Systems==&lt;br /&gt;
The &#039;&#039;&#039;I&#039;&#039;&#039;solation &#039;&#039;&#039;F&#039;&#039;&#039;ield &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;IFS&#039;&#039;&#039;, was designed with the intent to isolate hostile alien forces that boarded the vessel for the crew. This function is considered vitally important when consideration is given to the fact that the Rosenanté class starship possesses a very highly trained crew. The &#039;&#039;&#039;IFS&#039;&#039;&#039; fundamentally isolates the threat through the use of perpetual containment fields, reinforced by miniature shield defenses for the IFS emitter assembly. The &#039;&#039;&#039;IFS&#039;&#039;&#039; is always active, limiting the mobility of non-authorized personnel, securing sensitive sectors of the ship, and effectively hindering the process of any hostile aliens that may manage to board the vessel. The ship&#039;s computer monitors the movements of every official member of the ship&#039;s crew at all times. In this manner, the computer is able to activate or deactivate the &#039;&#039;&#039;IFS&#039;&#039;&#039; screens on an individual basis as needed. This allows authorized crewmembers access to shipboard systems and compartments as needed. The &#039;&#039;&#039;IFS&#039;&#039;&#039; consists of a series of Level 8 containment fields spaced an even 12.5-meters along the corridors of the vessel. In addition to these, an &#039;&#039;&#039;IFS&#039;&#039;&#039; field also isolates each access portal and hatch. In the event that a commbadge should be captured, or fail, that badge is automatically removed from all access rosters, until security can investigate the occurrence.&lt;br /&gt;
&lt;br /&gt;
As a benefit of the perpetually active IFIS fields, studies indicate that shipboard damage caused by fire and/or decompression was drastically reduced. The fields prevented large area decompression, and also limited the range of fire dispersion radically.&lt;br /&gt;
&lt;br /&gt;
Although in larger compartments the &#039;&#039;&#039;IFS&#039;&#039;&#039; system is not perpetual; all compartments are equipped with the capacity to further &amp;quot;compartmentalize&amp;quot; these large open areas. The computer is capable of assessing threats to the crew and equipment of the vessel, and can respond using the &#039;&#039;&#039;IFS&#039;&#039;&#039; system, nearly instantly. The &#039;&#039;&#039;IFS&#039;&#039;&#039; system was designed to operate independently of the ships main power supply when necessary. Each &#039;&#039;&#039;IFS&#039;&#039;&#039; emitter and processor assembly is equipped with an independent high-yield Sodium Kelleride power system. This power cell is further treated with a Potassium Unified catalyst. This allows the production of oxygen as a by-product whenever the secondary power system is operated. This allows a crewmember to be compartmentalized in an otherwise decompressed area to survive asphyxiation and loss of pressure. This secondary power system will allow the full yield operation of the &#039;&#039;&#039;IFS&#039;&#039;&#039; emitter in question for a period of 4 standard hours. Setting the emitter to a lower containment setting can extend this time.&lt;br /&gt;
&lt;br /&gt;
==12.1.2 Fire Suppression Systems==&lt;br /&gt;
&lt;br /&gt;
Although the &#039;&#039;&#039;IFS&#039;&#039;&#039; system hinders the progress of a shipboard fire, it will not necessarily extinguish it. To facilitate this a hybrid field emitter, environmental suppression system was developed. This system isolates the flame from its fuel source using advanced forcefield emissions systems, while simultaneously adjusting the environment around the fire to assist in its suppression. A functional &#039;&#039;&#039;IFS&#039;&#039;&#039; contained area further supports the adjustments, as a smaller area of the ship need be adjusted at any one time. There are certain types of plasma fires that could be unaffected by environmental conditions and or can not be contained in this manner. It is in those situations that the fire suppression systems remove the fire and all affected material through use of the ships sight-to-sight transporters. If this cannot be performed due to a greater risk being imposed on the crew, more conventional methods of fire suppression must be performed.&lt;br /&gt;
&lt;br /&gt;
==12.1.3 Internal Ballistics Dampening Fields==&lt;br /&gt;
In key areas where materials stored aboard ship have the potential to be propelled through sections of the ship, a series of &#039;&#039;&#039;I&#039;&#039;&#039;nternal &#039;&#039;&#039;Ba&#039;&#039;&#039;llistics &#039;&#039;&#039;D&#039;&#039;&#039;ampening Fields, or &#039;&#039;&#039;I-BAD&#039;&#039;&#039; Fields, have been implemented. These fields are found primarily in the armory, cargo bays, Shuttle Bays, storage bays, and personnel quarters. The &#039;&#039;&#039;I-BAD&#039;&#039;&#039; system uses advanced internal sensing equipment specialized to calculate mass and velocity of non-anchored materials. In the event that these materials should be propelled at a speed that the computer should indicate hazardous to crew, then a series of inertial Dampening Fields are erected to reduce the velocity of the offending object. The IDF relays cannot stop a propelled item, although it can shorten its travel distance and relative speed considerably. The sensing systems ignore the movements of personnel. The &#039;&#039;&#039;I-BAD&#039;&#039;&#039; emitters in no way affect the reduction of stresses upon the vessel caused by acceleration, deceleration, or maneuvering.&lt;br /&gt;
&lt;br /&gt;
==12.1.4 Advanced Ergonomics==&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-4up.jpg|thumb|right|500px|]]&lt;br /&gt;
&lt;br /&gt;
Throughout the vessel, specialized memory seating systems have been implemented. These systems monitor the stresses upon the body of the crewmember presently utilizing them and adjust the contact points with the crewmember to minimize physical stresses. All station seating and this material affects standard seating in personnel quarters. The design is such that is can self adjust to allow for non-humanoid crewmembers. The standard bedding and medical bio beds are also adjusted in this manner. This has proven to reduce fatigue and discomfort resulting from prolonged duty shifts. The conceptualization of advanced ergonomic design is further implemented in the layouts and design of the personnel quarters on the ship. Each individual’s quarters are ergonomically designed to his or her unique specifications. The height and shape of interactive systems, the design of the shelving and storage facilities, and the layout of the waste management system are all adjusted to the unique requirements of the compartment owner. Even habitation shape and colour are carefully implemented to create an environment in harmony with its occupant.&lt;br /&gt;
&lt;br /&gt;
==12.1.5 Tactical Sight-to-Sight Transport==&lt;br /&gt;
The ship&#039;s computer possesses the ability to assess tactical breaches in to the vessel&#039;s security. When appropriate, the computer may implement tactical redistribution of security personnel to facilitate the disarmament of tactical threats. The computer determines the size of any aggressive and/or threatening force on the ship, and then determines logical methods of containing and overcoming this threat. The computer is capable of briefing shipboard security personnel on the state of a threat, operating IFIS units, and evacuating non-essential personnel from potential or actual combat areas. The computer can deploy security personnel using sight-to-sight transporters and tactical deployment subroutines. In addition to automatic response to internal tactical threats, the ship&#039;s computer can suggest tactical deployment options for security personnel, utilizing data stored in its memory. This tactical deployment data is only suggested when asked for, and is prepared for planetoid deployment, boarding actions, counter-boarding actions, and sight security. When a medical situation presents itself the same sight-to-sight transporter system can be utilized to transport critical patients to the sickbay.&lt;br /&gt;
&lt;br /&gt;
==12.1.6 Emergency Medical Hologram==&lt;br /&gt;
The Emergency Medical Hologram, as standard to all Federation starships, is also present on the Rosenanté class starship. A series of modifications allows the EMH system to be activated in any habitable portion of the vessel. This function is performed by a series of specialized emitters seeded throughout the ship. Each emitter is equipped with an array of medical scanners and programmed with trauma and first aid protocols. Each emitter assembly is capable of independent operation in the event that power systems become unavailable. The Sodium Kelleride power source can maintain EMH use for 1 hour before expending its charge. When operating normally, the EMH can access the ship&#039;s medical database. When operating independently, only the trauma and first aid subroutines may be accessed. While operating on ship&#039;s systems no more than three EMH programs may be running at any one time. Independent operation is possible among any number of EMH emitters.&lt;br /&gt;
&lt;br /&gt;
==12.1.7 Emergency Replication System==&lt;br /&gt;
The &#039;&#039;&#039;E&#039;&#039;&#039;mergency &#039;&#039;&#039;R&#039;&#039;&#039;eplication &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;ERS&#039;&#039;&#039;, is a series of secondary replicators that operate completely independent of the ships systems. The &#039;&#039;&#039;ERS&#039;&#039;&#039; units are located aft and fore of the starship, two per deck. They are always inert until activated. The &#039;&#039;&#039;ERS&#039;&#039;&#039; system is &amp;quot;hidden&amp;quot; behind corridor paneling, and consists of a single equipment replicator, a single food replicator, an atmospheric condenser, a single medical tricorder, a standard tricorder, and a pair of Class I Phasers. A high-yield Sodium Kelleride Battery that allows light use of the replicators, for a period of 3 days, powers the &#039;&#039;&#039;ERS&#039;&#039;&#039; units. The Tricorders and Phasers are pre-powered, and can be recharged once, using the supplied connections. Accessing the ERS panel will alert security. The Class I phasers require a personal authorization code to be activated. The computer monitors the &#039;&#039;&#039;ERS&#039;&#039;&#039; system very closely, immediately notifying engineering if a problem is detected.&lt;br /&gt;
Although the &#039;&#039;&#039;ERS&#039;&#039;&#039; is a fully functional Replication system, it is programmed to create materials that require very little energy to reproduce. Thus, the food replicators produce only a single nutrient rich disk for consumption. The Tool replicator is limited to equipment that possesses simple physical structures, such as hand tools and only simple electronics materials. Neither replicator system can reproduce power sources, or advanced electronics.&lt;br /&gt;
&lt;br /&gt;
==12.1.8 Emergency Transporters==&lt;br /&gt;
The Rosenanté class starship is equipped with 2 emergency transporters. These transporters are located centrally along the berth and length of the vessel on decks 5 and 15. The emergency transporters are integrated into the primary corridor on the aforementioned decks. All transporter hardware is stowed in the surrounding corridor structures. 20 high-yield Sodium Kelleride Batteries independently power the control operation panel and the emergency transport systems. Each Emergency transporter is also equipped with its own short-range sensor array, for destination determination. The control panel is &amp;quot;hidden&amp;quot; behind the corridor paneling, and floor paneling hides the transporter pad. In order to operate the transporter this floor paneling must be removed. The emergency transporters are each capable of transporting 60 personnel.&lt;br /&gt;
After that there is no power remaining to continue transporter functions. Preparing the Emergency transporters for use alerts security.&lt;br /&gt;
&lt;br /&gt;
==12.2 Medical Bay==&lt;br /&gt;
Due to the number of personnel stationed aboard the Rosenanté class starship, the standard&lt;br /&gt;
Medical Bay arrangement was not utilized. Instead a specialized medical bay was designed to maximize space, while still attending to the variable needs of the ship&#039;s crew. To this end, the sickbay possesses a complete quarantine ward, a single surgical ward, and the central sickbay. A office allows for the CMO to perform administrative tasks without interruption.&lt;br /&gt;
In the surgical area, all the equipment necessary to perform any level of surgery is present. Specialized negative pressure systems allow operations to continue upon contaminated personnel without worry of integrity loss.&lt;br /&gt;
The central medical area is equipped with the newest and most efficient systems that general practice has to offer. A multitude of sensors and medical dedicated processors facilitate medical data gathering, while advanced holographic modeling systems allow hands-off data model construction. Forty Biobeds are located in the Sickbay, which studies indicate was the most efficient number of patients to treat at one time. &lt;br /&gt;
&lt;br /&gt;
In addition to the standard biobeds and Infirmary treatment bay, There are also two dedicated Medical Laboratories, One General Practice Clinical Ward and Three configurable Bays, which can be changed to meet the specific requirements of the medical needs of the vessel.&lt;br /&gt;
&lt;br /&gt;
The Quarantine area is equipped with a series of Biocide units capable of detecting, isolating and destroying over three hundred billion contagions. Negative pressure atmospheric systems, ionic decontamination systems, and bio-phased containment fields guarantee the isolation of harmful contagions. All containment systems in the sickbay are maintained by secondary and tertiary power systems. A medical dedicated replication system allows the creation of any replicable pharmaceutical known to Starfleet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&amp;lt;small&amp;gt;All images compliments of Roger Wackowski&amp;lt;br&amp;gt;Spiral Drive concepts by Anthony Keen&amp;lt;br&amp;gt;All other technical aspects, created, written and designed by Daniel Greene&amp;lt;/small&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
[[Category: Engineering]][[Category: Database]][[Category: Active Ships]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=The_Chimera_Directive&amp;diff=55387</id>
		<title>The Chimera Directive</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=The_Chimera_Directive&amp;diff=55387"/>
		<updated>2012-05-09T16:21:26Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* 12.1.4 Advanced Ergonomics */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;  &lt;br /&gt;
  &lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
== 1.0	CHIMERA DIRECTIVE INTRODUCTION ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-1up.jpg|thumb|500px|The Rosenante Class Starship]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1.1 MISSION OBJECTIVES FOR ROSENANTÉ CLASS PROJECT&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Starfleet has long been charged with a broad spectrum of responsibilities to the citizens of the Federation and to the lifeforms of the Galaxy at large. As the volume of explored space continues to grow, and with it the Federation itself, so do Starfleet&#039;s duties. &lt;br /&gt;
&lt;br /&gt;
These duties range from relatively mundane domestic and civil missions, to cultural contact and diplomacy, to defense, to our primary mission of exploration and research. Many of these responsibilities are best carried out with relatively small, specialized ships. Yet there continues to be an ongoing need for an even narrower role vessel to protect the Federation against enemies that would use espionage and subversion to wage war against the Federation.&lt;br /&gt;
&lt;br /&gt;
This particular threat to Federation security is further complicated by political and economic restraints placed upon the Federation caused by the demands of maintaining an active war first against the Cardassian Union and then a Civil War between Doenitz Loyalists and 52nd Fleet seditionists. The Federation had suddenly found itself pressed on many fronts at various levels of engagement, often ill-prepared or incapable of information gathering against potential interior and exterior threats to the continued existence of the Federation.&lt;br /&gt;
&lt;br /&gt;
In response to the alarming number of intelligence related activities conducted against Federation projects, personnel, and equipment by exterior Intelligence Organizations, such as the Tal Shiar, the Dominion Shapeshifters, and The Cardassian Obsidian Order, Starfleet Intelligence has found itself grossly outnumbered, and under-appreciated by Starfleet Command. This lack of interdepartmental cooperation was only strengthened by Starfleet Intelligence&#039;s inability to detect and detain several pro-Revolutionary agents that had managed to infiltrate Starfleet Command, the Council of the President, and several other critical posts within the governmental structure of the Federation. The agents proved to be the first signs of the coming Civil war that would shake the foundations of the United Federation of Planets over the next several years.&lt;br /&gt;
&lt;br /&gt;
These breeches of critical security protocol within the government provided the critics of Starfleet Intelligence with ammunition to pressure Starfleet Command to tighten its control on the Intelligence Department. In late 2390s, with the Cardassian Union pressing their offensive against the Federation, Starfleet Intelligence learned of other threats to the Federation&#039;s continuing existence, as reports began to come into Starfleet Intelligence&#039;s Romulan desk reporting a large number of Romulan Infiltrators had somehow managed to concentrate themselves on the Federation Starships patrolling the Neutral Zone. With reports indicating that the Tal Shiar compromised a large majority of Starships patrolling the Neutral Zone, and with SFI fearing a Romulan Invasion, a massive counter Intelligence operation began. This operation, dubbed Sword and Shield, inserted several dozen Starfleet counterintelligence Specialists onboard the suspected Starships. For the better part of a year, these operatives played a deadly game of cloak and dagger against the expectant Tal Shiar operatives. This massive undertaking resulted in the largest capture of external espionage operatives in Starfleet history, 38 Starfleet officers (including 2 Ship Captains) and 12 Enlisted Starfleet personnel were arrested and charged with espionage against the Federation. 6 Starfleet Intelligence operatives lost their lives in this operation. &lt;br /&gt;
&lt;br /&gt;
It was to this threat that Admiral Rodrigo Doenitz would propose a solution. That solution came in the form of a Starship, dedicated completely to the tasks of espionage and interdiction operations. The vessel would be operated entirely independently of Starfleet command. Only Starfleet Intelligence would have any command authority over the vessel and its missions. This proposal created a scandalous outcry by Starfleet Command Officers, with the end result becoming less than favorable to the Doenitz cause.&lt;br /&gt;
&lt;br /&gt;
However, the dramatic success of Sword and Shield eased the tension against Starfleet Intelligence, and by the end of the War with the Cardassian Union in 2398; Starfleet Command realized the inability of SFI to conduct operations in hostile space, or to operate independently without the immediate assistance of Starship under Starfleet Command authority. It was in August of that year that Admiral Talbot, with the support of Admiral Doenitz proposed the idea of creating a new class of Starship capable of supporting Intelligence operations in hostile space, while simultaneously capable of performing signal, traffic and visual surveillance of facilities, ship movements and communications. Admiral Talbot argued that if SFI were equipped with such a vessel during the War, that the effectiveness of the Cardassian attack against the UFP would have been greatly reduced, if not altogether neutralized. Additionally, Talbot argued, such a ship working in Romulan space would have been priceless in determining the intentions and movements of the Tal Shiar during Operation Sword and Shield.&lt;br /&gt;
&lt;br /&gt;
Admiral Talbot’s conceptual Starship was deemed impossible to build, and also in violation of Starfleet Intelligence Command’s charter and the project was immediately disapproved. But that was not the end of the situation. &lt;br /&gt;
&lt;br /&gt;
Admiral Talbot, through secret channels with the complete support of Admiral Rodrigo Doenitz established a secret construction facility. Through various nefarious means, funds were funneled into the project and experienced Starfleet ship engineers were tasked to assist in developing a new class of Starship that could function efficiently within the confines established by the joint visions held by the two admirals.&lt;br /&gt;
&lt;br /&gt;
A special Starfleet Intelligence Operation was begun in a secret shipyard facility around early 2397. SFI operatives assigned to the operation interviewed and recruited Starship designers from across the Federation, purposely avoiding any designer that had ever worked on a Starship Project for the Federation in the past. These designers, assisted by the technical and personal experiences, of selected Starship Engineers laid down the design parameters for the project.&lt;br /&gt;
&lt;br /&gt;
After Admiral Doenitz’s successful coup, the project would prove to outlive many of its critics. With the full power of the office of the president of the Federation, Doenitz fast tracked his project making it an official Presidential Directive. This Directive was codenamed the Chimera Directive.&lt;br /&gt;
&lt;br /&gt;
The Rosenanté Class Starship designed by the Chimera Directive represents the most advanced design and systems innovations in the Federation. The basic design concept was developed around the Sovereign class and is considered the most advanced evolution of Starfleet Ship design to date.&lt;br /&gt;
&lt;br /&gt;
==Design Objectives==&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;&#039;&#039;Pursuant to Starfleet Intelligence Directive 1045.35, the following objectives have been established for the Rosenanté Class Starship development project:&#039;&#039;&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*	Provide a mobile platform for a wide range of ongoing intelligence and counterintelligence projects.&lt;br /&gt;
*	Provide autonomous capability for full execution of Starfleet Intelligence policy and directive options in hostile areas of space.&lt;br /&gt;
*	Incorporate recent advances in technology and protocols.&lt;br /&gt;
&lt;br /&gt;
To provide for these objectives, the Designers recommended that the Rosenanté class starship meets or exceeds the design goals in the following specification Categories;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Propulsion&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Sustainable cruise Velocity of Warp Factor 9.4. Ability to maintain speeds of up to Warp Factor 9.7 for periods of up to 12 Hours.&lt;br /&gt;
*	Sixth-phase dilithium controlled matter/antimatter reactor for primary power. Sustainable field output to exceed 1, 650 cochranes, peak transitional surge reserve to exceed 4,225% of nominal output. (170ns phase)&lt;br /&gt;
*	Warp Driver coils efficiency to meet or exceed 98% at speeds up to Warp 8.0. Minimum efficiency of 68% to be maintained through Warp 9.4. Life cycle of all primary coil elements to meet or exceed 1,200,000 cochrane-hours between neutron purge refurbishment. Secondary coil elements to meet or exceed 2,000,000 cochrane-hours between neutron purge refurbishment.&lt;br /&gt;
*	Warp field geometry to incorporate modified 85° Z-axis compression characteristics on forward warp lobe for increased peak transitional efficiency at high warp. Warp Nacelle centerlines to conform to 2.56: 1.1 ratio of separation to maximize field strength.&lt;br /&gt;
*	Secondary (impulse) propulsion systems to provide sub-light velocities up to and including .92 light speed (c). Engine systems of choice to include but not limited to at least two YPS 8063 fusion drive motors. All units to be equipped with subspace drive accelerators, field output not less than 180 millicochranes at 1.02 X l0³K. Reactor Modules to be field replaceable.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Mission&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Ability to operate independent of Starbase refurbishment for moderate periods of time. Independent operation mode capability of 1 Standard years at nominal Warp 6. Ability to execute deep-space exploration missions including charting and mapping, hostile contact scenarios, intelligence gathering and infiltration missions, full technical, biological and ecological studies.&lt;br /&gt;
*	Ability to support a wide range of mission-related ongoing research and other projects without impact on primary mission operations.&lt;br /&gt;
*	&#039;Full Spectrum EM, optical, subspace flux, Gravimetric, particle, and quark population analysis sensor capability. Multimode neutrino interferometery instrumentation. Wide band life sciences analysis capability. 2 twelve-meter interphasic field focused telescopes.&lt;br /&gt;
*	Upgradeable experiment and sensor array design. Ability to support on-board and probe mounted science and intelligence instrumentation.&lt;br /&gt;
*	Support facilities for auxiliary spacecraft and instrumented probes for short-range operations to include at least 1 independent launch, resupply, and repair bays.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Environment/Crew&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Environmental systems to conform to Starfleet Regulatory Agency (SFRA)- standard 102.9 for Class M compatible oxygen breathing personnel. All life-critical systems to be triply redundant. Life support modules to be replaceable at major Starbase layover to permit vehicle-wide adaptation to Class H, K or L environmental conditions.&lt;br /&gt;
*	Ability to support up to 200 non-crew personnel for mission related operations.&lt;br /&gt;
*	Facilities to support Class M environmental range in all individual living quarters, provisions for 2% of living quarters to be equipped to support Class H, K and L environmental conditions. Additional 1% of living quarters volume to be equipped for Class N and N (2) environmental adaptation.&lt;br /&gt;
*	All habitable volumes to be protected to SFRA-standard 347.3(a) levels for EM and radiation. Subspace flux differential to be maintained within 0.02 millicochranes.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Tactical&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Defensive Shielding to exceed 9.85 X 103 kW primary energy dissipation rate. All tactical Shielding to have full redundancy, with auxiliary system able to provide 75% of primary rating.&lt;br /&gt;
*	Tactical systems to include full array of Type XII phaser bank elements on hull capable of 6.1MW maximum single emitter output. 6 Photon Torpedo launchers required for ship defensive capabilities.&lt;br /&gt;
*	Tactical systems to include anti-detection components capable of defeating sensor and optical scan.&lt;br /&gt;
*	Tactical systems to include variable decreased emissions systems affecting primary and secondary drive systems.&lt;br /&gt;
*	Tactical systems to include components to reproduce or produce false sensor signatures at displaced coordinates in vessel reference.&lt;br /&gt;
*	Tactical systems to include components to produce ambient radiation and gravitational energies consistent with surrounding spatial occurrences.&lt;br /&gt;
*	Tactical systems to include variable EM field dampening systems to reduce or eliminate vessel EM fields and signatures.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Design Life&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Space frame design life of approximately 100 years, assuming approximately 5 major ship- wide system swap outs and upgrades at average intervals of 20 years. Such upgrades help ensure the continuing usefulness of the ship even though significant advances in technology are anticipated during that time. Minor refurbishment and upgrade to occur at approximately one- to five year intervals, depending on specific mission requirements and hardware availability.&lt;br /&gt;
&lt;br /&gt;
==2.0 General Overview==&lt;br /&gt;
&lt;br /&gt;
The Rosenanté class of Starship was originally categorized as an intelligence-gathering vessel. The Rosenanté class is only the second starship class created by Starfleet command to receive this designation. The other is the Spectre Class. While most starships may be adapted for many different mission types, the Rosenanté class starship is designed primarily to perform a single type of mission objective, in effect limiting her overall flexibility within a more generalized Starfleet. Seen from a comfortable distance of two or three kilometres, the starship takes on the resemblance of the more familiar Sovereign class explorers. Upon closer inspection however, one can see that the engineering hull is more sleek, lending a highly manoeuvrable appearance to the Rosenanté class of starship. The engineering hull actually extends both above and below the saucer section, lowering the overall silhouette of the class. Additionally, the saucer section itself boasts a number of changes that are easily noticed even by the most novice of observers. This divorce from standard Starfleet design protocols is both advantageous and disadvantageous for this class of starship. The unique hull design allows an immediate reduction in stresses generated by high warp speeds, while allowing greater manoeuvrability at sub-light speeds. This hull design concept has its drawbacks however, as high speed warp manoeuvrability is reduced in favour of speed. The exterior hull material is stronger, lighter and more durable than that used in standard starship production. This reduces the need for otherwise necessary supports and braces, leaving a greater interior volume for habitation. This material used on the ship&#039;s hull is more difficult to reproduce and repair, as specialized facilities must be implemented to perform these functions.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;2.1 Physical Arrangement&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-2up.jpg|right|300px]]&lt;br /&gt;
&lt;br /&gt;
The hull, remarkably birdlike in its strong, hollow construction, is reinforced against flight stresses by active energy fields that tighten and flex where required to compensate for natural and artificial internal and external forces. Structures integrated into the hull allow for a variety of necessary functions. &lt;br /&gt;
&lt;br /&gt;
The bridge consolidates the command positions for the rest of the starship, windows allow crewmembers needed vistas while in space, phaser arrays and photon torpedoes provide offence and defence against hostile forces, and a specialized communications system allows interaction with other worlds and their ships.&lt;br /&gt;
&lt;br /&gt;
Lifeboats allow for escape in dire emergencies, transporter emitters afford reliable near instant movement of crew and gear, navigational sensors and deflectors give the starship distant vision and a method for clearing obstacles, and powerful warp engines propel the starship at amazing speeds.&lt;br /&gt;
&lt;br /&gt;
The twenty-eight decks are internally divided among major load-bearing structures. A great many systems, especially the habitation sections are suspended within the open spaces, essentially &amp;quot;floating&amp;quot; on flexible ligaments to minimize mechanical, thermal, and conductive radiation shocks.&lt;br /&gt;
&lt;br /&gt;
The living areas of the starship have been designed for maximum comfort and safety while the crew is conducting a mission. Long-term studies of humanoid cultures have revealed that as each race embarked upon permanent occupation of space, large personal living spaces had to be established, especially on early sub-light missions. The Rosenanté class starship allows for some 120 square meters of living space per person, in addition to community space and areas allotted to purely working functions.&lt;br /&gt;
&lt;br /&gt;
==3.0 Spacecraft Structure==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.1 Main Skeletal Structure&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The primary space frame of the Rosenanté class starship is fabricated from an interlocking series of Terminium/Tritium microfilament truss frames. These members average l.05m² in cross section and are capable of bearing the same load as the standard Tritanium/Duranium truss averaging l.27m² in cross section used in standard starship construction. These truss frames are located an average of 20 meters across the ship&#039;s exterior, while the standard trusses would be located every 25 meters along a ships exterior. The tightening of the trusses allows the vessel to withstand greater stress imposed upon it by warp travel, while still producing a lighter space frame.&lt;br /&gt;
&lt;br /&gt;
As with other starship designs, larger numbers of these trusses are located integral to the main impulse engine sections, the warp nacelle pylons, docking interface latches, and along the centerline of the hull structure. Smaller Trusses averaging 0.35m² in cross section are located every five meters on average, and also provide internal supports within the deck and core structure of the spacecraft interior.&lt;br /&gt;
&lt;br /&gt;
A mechanical framework provides physical integrity to the vehicle while at rest. A parallel series of aluminum crystal foam stringers are phase transition bonded to the primary trusses, providing low frequency vibration attenuation across the main truss structure, as well as support for certain utility conduits.&lt;br /&gt;
&lt;br /&gt;
Also attached to these stringers are various conformal devices built into the hulls structure, including elements of the deflector shield grid, H.l.S.S. components, as well as subspace radio antennas, which are incorporated into the skin of the spacecraft.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.2 Secondary Framework&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mounted to the primary space frame is a secondary framework of micro-extruded Terminium trusses to which the inner hull of the structure is directly attached. The secondary framework is mounted by means of 3.2 cm diameter X 5.1 centimeter long semi rigid polydurinide support rods, permitting a limited amount of mechanical isolation from the primary space frame for purposes of strain relief, plus sound and vibration isolation. Secondary space frame segments are also separated from each other (although mechanically attached) to permit replacement of inner hull segments and associated utilities infrastructure during major Starbase layover.&lt;br /&gt;
&lt;br /&gt;
Structural integrity during powered flight is provided by a series of forcefields that reinforce the physical framework. This structural integrity field (SIP) is distributed through a network of molybdenum-jacketed wave-guides, which in turn distribute SIF energy into ceramic-polymer conductive elements throughout the space frame. Without the structural integrity field, the vehicle would be unable to withstand accelerations greater than 3l.4 m/s² without significant deformation, or greater than 49.18 m/s² without unrecoverable structural damage.&lt;br /&gt;
&lt;br /&gt;
Exterior hull substrate is joined to the primary load bearing trusses by means of 4.8-cm diameter electron-bonded duranium pins at 1.01-meter intervals. These pins are slip-fitted into an insulating AGP ceramic fiber jacket that provides thermal insulation between the space frame and the exterior hull. The pins, jacketing, and hull segments are gamma welded together.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.3 Hull Layers&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The exterior of the spacecraft consists of multiple layers, which afford structural and atmospheric integrity for the space frame, integral wave-guides and field conductive members for the structural Integrity Field (SIP) and H.I.S.S components, and pathways for other utilities (including deflector grids), as well as resistance to radiation and thermal energy.&lt;br /&gt;
The exterior shell substrate is composed of interlaced micro-foam duranium filaments. These filaments are gamma welded into a series of contiguous composite segments that are 4.7 cm thick and are typically 2 meters in width. The substrate segments are electron-bonded to three reinforcing layers of 1.2- cm biaxially stressed terranium fabric, which provide additional torsion strength.&lt;br /&gt;
&lt;br /&gt;
In areas immediately adjacent to major structural members, four layers of 2.3-cm fabric are used. The substrate layer is attached to major structural members by electron-bonded duranium fasteners at 2.5-cm intervals. The substrate segments are not intended to be replaceable, except by phase-transition bonding using a transporter assembly jig during major Starbase layovers.&lt;br /&gt;
Two 3.76-cm layers of low-density expanded ceramic-polyrner composites provide thermal insulation and secondary SIP and H.I.S.S. conductivity. These layers are separated by an 8.7-cm multiaxis triennium truss framework, which provides additional thermal insulation and a pass through for fixed utility conduits.&lt;br /&gt;
&lt;br /&gt;
A 4.2-cm layer of monocrystal beryllium silicate infused with somniferous polycarbonate whiskers provides radiation attenuation. This layer is networked with a series of 2.3-cm X 0.85-cm molybdenum-jacketed conduits. These conduits, which occur at 1.3-m intervals, serve as triphase wave-guides for the secondary structural integrity field. Conductive tritium rods penetrate the wave-guides at l0-cm intervals and transfer SIF energy into the ceramic-polymer conductive layer.&lt;br /&gt;
The outermost hull layer is composed of a 1.6-cm sheet of AGP ablative ceramic fabric chemically bonded onto a substrate of 0.15-cm triermium foil. This material is formed into segments approximately 3.7m² and is attached to the radiation attenuation layer by a series of duranium fasteners, which allows individual segments to be replaced as necessary. (Micrometeor erosion is kept to a minimum by the deflector system, but is sufficient to warrant replacement of 30% of the leading edge on the average of every 7.2 standard years.) Individual outer hull segments are machined to a tolerance of ±0.05-mm to allow for minimum drag through the interstellar medium. Joints between segments are manufactured to a tolerance of ±0.025-mm.&lt;br /&gt;
&lt;br /&gt;
Also incorporated into the outermost hull layer is a series of super conducting molybdenum-jacketed wave-guide conduits, which serve to absorb and disperse sensor emission energy that interacts with the hull. Segmented sections of this network serve as housings for the unique DECS components, responsible for producing the ship’s tactical deflector. Unlike a standard starship, there are no thermal regulating assemblies built into the skin of the starship. Instead this duty is regulated through a series of intercoolers and radiators housed inside the interior of the Bussard Collector Assembly.&lt;br /&gt;
&lt;br /&gt;
==4.0 Command Systems==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.1 The Bridge&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Bridge, located on Deck 1, provides primary operational control of the Rosenanté class starship. The bridge directly supervises all primary mission operations and coordinates all departmental activities. These activities are handled through the individual command consoles located in various positions on the bridge. These workstations are modular and can be interchanged, removed, or added as necessary to fulfill specialized mission requirements. At any one time there can be up to 12 workstations installed. The standard bridge design calls for 2 Science Stations, 1 Operations Station, 1 Flight Control Station, l Auxiliary Engineering Station, 1 Tactical station, 1 Communications/ H.I.S.S. station, 1 Internal Security Station, and 2 Command Stations, one each for the ship’s commander, and the First Officer.&lt;br /&gt;
Other facilities located on Deck 1 include Astrogation, the captain&#039;s ready room and head, the crew head, and a small mission briefing room.&lt;br /&gt;
Major connections to the bridge include a pair of Turbolift shafts, four electron-plasma power distribution wave-guide conduits; four environmental support plenum groups, nine primary and two back-up optical data network trunks, two replicator wave-guide conduits, and three service crawlways. As an interesting side note, a tertiary backup power distribution system consisting of hardwired nonreactive, conductive ceramic-polymer relays are also in place.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.2 Display Panels&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The display panels on the bridge and through out the ship are constructed and operated the same as those on any other Federation starship. The layouts and reactivity of the panels are augmented and display properties shown in a different manner. The coloration of the interaction displays is altered to create a different aesthetic affect, while also allowing a variant-programming matrix to be utilized. This new language utilizes advances in Holoprogramming to create three-dimensional matrix strings; this in turn allows a more efficient and quicker computer response time. Critical internal components of the display panels are mapped to the molecular level allowing a replication driven pro-holographic matrix damage control system to repair damaged components. The components necessary to facilitate this activity are collectively known as the &#039;&#039;&#039;Se&#039;&#039;&#039;lf-&#039;&#039;&#039;Re&#039;&#039;&#039;plicating &#039;&#039;&#039;Da&#039;&#039;&#039;mage &#039;&#039;&#039;C&#039;&#039;&#039;ontrol &#039;&#039;&#039;S&#039;&#039;&#039;ystem (&#039;&#039;&#039;SERDACS&#039;&#039;&#039;). The &#039;&#039;&#039;SERDACS&#039;&#039;&#039; components are present in all non-integrity dependant systems throughout the ship. &lt;br /&gt;
&lt;br /&gt;
In addition to the standard anchored display consoles located throughout the ship, a series of Holoemitters have been seeded throughout the vessel to allow ship&#039;s personnel to utilize a holographic interface to tie directly into the ships computer regardless of the location of the crewmember. These emitters also allow the EMH to be activated in any compartment in the ship, and also allow for the construction of holographic crewmembers to fill non-critical positions on the ship. These holoemitters are capable of creating non-electronic tools for emergency use, and in conjunction with replication systems could produce vital simplified component reproduction anywhere aboard ship.&lt;br /&gt;
&lt;br /&gt;
==4.3 Bridge Stations==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.1 Flight Control (CONN)&#039;&#039;&#039; &amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the actual piloting and navigation of the ship. From this station all SIF and IDF systems are monitored, as well as navigational deflectors, and their subsequent systems. This console performs the same functions as it would on board any other Federation starship.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.2 Operations Management (OPS)&#039;&#039;&#039; &amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for power maintenance and resource allocation. This console dictates priority status of all shipboard systems and operations. They coordinate activities between departments and between the ship and away missions. This console performs the same functions as it would on board any other Federation starship.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.3 Tactical Operations (TACOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the operation, monitoring and maintenance of the ship&#039;s tactical systems. These systems include the phaser arrays, the photon torpedo deployment systems, probe	deployment systems, H.I.S.S. system, Signal displacement system, tractor beams, and Tactical deflector systems. The Tactical station aboard the Rosenanté class starship differs from those of standard Federation starships. The main difference is the divorce of the ship&#039;s tactical systems from the internal security systems of the ship. This allows the tactical officer the ability to concentrate on the tactical aspects of the ship without the need to also monitor the internal security status of the ship. Another major difference in the Rosenanté class starship is the addition of a sensor array specifically for use by the tactical officer.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.4 Security Operations (SECOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the monitoring and operation of internal ship security systems. The Operator of this console is responsible for the deployment of ship&#039;s security personnel aboard the ship. This console controls the internal security containment fields, internal ship&#039;s sensors. The SECOPS officer can monitor the security status, security systems and personnel deployment for the entire ship. They can control door mechanisms, containment fields, the turbolift car, and weapons settings of all Federation weaponry on the ship. In addition, security can control personnel access to restricted areas, and utilize sight-to-sight onboard transporters.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.5 Communications (COMMOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the encryption and decryption of intercepted communications, for the transmission of communications, maintaining the Emissions Control Protocols, and the operation of specialized communications interception equipment. The Communications officer is often called upon to triangulate communications sources, decipher enemy transmissions, and encrypt outgoing communications. They often assist in Traffic Analysis of enemy troop deployment, and maintain secure communications with away teams.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.6 Science Stations I &amp;amp; II&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
These consoles are responsible for data collections, primary and lateral sensor operations, and database referencing. It is the responsibility of the science officer to operate the ship&#039;s sensors, teleoptical systems, and imaging systems. They observe, record and document data important to shipboard mission objectives. These stations can be utilized together or separately. This station also acts as the primary database access terminal for the Federation database carried aboard all Federation starships. Both passive and active sensors are controlled from this station.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.7 Auxiliary Engineering Station&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This station is responsible for maintaining and monitoring shipboard systems. This console works in conjunction with main engineering, and is capable of performing the same functions as the computer in that section of the ship. From this station the warp fields can be tuned, altered or monitored, as can all primary and secondary shipboard systems. This station is not always manned.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.8 Command Stations I &amp;amp; II&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
These consoles are responsible for the maintenance and monitoring of the ship&#039;s computer and all primary and secondary systems. Only the commanding and executive officer have access to these consoles. From these consoles the commanding officers can display data concerning ship&#039;s systems, status, condition, position, speed, heading, and power management distribution. These consoles can access the database, and has priority authority over all computer functions. These consoles are the only terminals capable of activating the ship&#039;s self-destruct mechanism. Any officer in command of the starship may utilize these consoles, although some functions may be unavailable.&lt;br /&gt;
&lt;br /&gt;
==5.0 The Computer System==&lt;br /&gt;
The computer system aboard the Rosenanté class starship is identical in construction to the computers used on other Federation Starships. They utilize the same back up and failsafe hardware and communicate through the same methods as the standard starship computer. The computer system of the Rosenanté class starship is composed of 2 synchronized computer cores, identical to those used in the Galaxy Class starship. The only differences between the standard Federation computers and those aboard the Rosenanté are the storage medium and programming language that the system uses to communicate.&lt;br /&gt;
The storage of data and processing networks of a standard Federation computer system depend upon isolinear chips. On the Rosenanté a new type of data storage chip, the Hololinear chip is introduced. Taking advantage of new replication and holographic programming breakthroughs, the new Hololinear chips, or HL chips, allow data to be stored in a four-dimensional, subspace format. A new programming language known a &#039;&#039;&#039;B&#039;&#039;&#039;ilinear &#039;&#039;&#039;U&#039;&#039;&#039;nilateral &#039;&#039;&#039;N&#039;&#039;&#039;etworking &#039;&#039;&#039;C&#039;&#039;&#039;ode (&#039;&#039;&#039;BUNC&#039;&#039;&#039;) allows data to be stored in a temprometric tagged holographic string, thereby allowing data to be stacked almost exponentially upon other data, linked by temprometric strings of associated data. Retrieval time is decreased as the data can be read from any point along its data string, rather than starting at a specified point as is required by the standard isolinear chip design.&lt;br /&gt;
&lt;br /&gt;
==6.0 Warp Propulsion Systems==&lt;br /&gt;
The Warp propulsion system in the Rosenanté class starship is radically different from Those used in other starships. The majority of the system is developed to utilize existing warp technology and materials. There is however a few major changes in the system. All warp engineers are familiar with the laws of warp transition, which dictates that warp geometry and power requirements dictate a vessel&#039;s ability to achieve various levels of warp speed. This same law also dictates that a warp field must be balanced in order to achieve maximum efficiency to make a warp transition.&lt;br /&gt;
&lt;br /&gt;
The Graph below represents the transition energy requirements for the Galaxy Class Starship design and also for that of the Rosenanté class starship.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:RWC.jpg|Center|400px]]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
ln the chart above the Cochrane values are represented over the white bar for the Rosenanté Class starship. At lower warps (below Warp 6) there is an actual decrease in warp efficiency, although at higher warp there is a worthwhile increase in efficiency, where the differences in efficiency matter most. It is important to note that a Galaxy class starship is incapable of traveling at Warp 9.97, and thus the numbers represented for that class is theoretical.&lt;br /&gt;
&lt;br /&gt;
The ability to sustain warp 9.97 is a result of multiple warp engines working in synchronization and a natural by-product of the embedded nacelle design. The synchronization of the dual warp drive is accomplished through the use of a &#039;&#039;&#039;W&#039;&#039;&#039;arp &#039;&#039;&#039;E&#039;&#039;&#039;nergy &#039;&#039;&#039;Sy&#039;&#039;&#039;nchronization &#039;&#039;&#039;R&#039;&#039;&#039;outer, or &#039;&#039;&#039;WESYR&#039;&#039;&#039;. The &#039;&#039;&#039;WESYR&#039;&#039;&#039; unit is highly classified, but its basic function is to synchronize otherwise out of synch Waveforms created within two near identical meshed Tuned Plasma Streams. Because of the additional energy that this system produces, a higher capacity EPS Power Tap and Series Relays were developed to handle the additional power loads. A dual bypass system allows any single Warp drive to power ships functions, at a significant reduction in overall power. Also a major redesign feature of the upgraded power system resulted in the addition of a second Port and Starboard Power conduit assembly and relay subassembly. This allows the power delivery system to function more efficiently.&lt;br /&gt;
&lt;br /&gt;
Interestingly enough, a bizarre natural byproduct of running a dual synchronized Warp Field is the creation of a &amp;quot;double&amp;quot; warp bubble. These warp bubbles are divided by 2.3-mnm (micronanometers) and help produce the effect of the change of reduction caused when making Warp Transitions. As subspace resistance passes through the Outer shield it is reduced as normal, then again as the remaining resistance passes through the inner bubble, it is further reduced. This causes the starship to experience less resistance and shearing warp stress associated with high rate warp travel and maneuvering.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Spiral Warp Drive&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In addition to the standard warp drive used by all federation starships, the Rosenanté class is also equipped with an experimental Spiral Warp Drive. This drive creates a subspace &amp;quot;tunnel&amp;quot; or &amp;quot;wormhole&amp;quot;  through which the Rosenanté may then travel. The tunnel integrity is maintained by the main deflector dish. The tunnel basically allows the ship to drop into subspace, effectively disappearing from normal space for a short period of time. The speeds that are achieved through the use of this drive are akin to those used by the Borg when using transwarp conduits. Unlike transwarp conduits, however,the tunnel being opened by the Rosenanté would dissipate as soon as the ship moves through it. In a similar manner, the spiral drive can only be used to travel in straight lines. This means that the vessel may make a periodic series of short hops to correct course when using this system.&lt;br /&gt;
&lt;br /&gt;
==7.0 Deflector Emitter Cluster System (DECS) ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-3up.jpg|left|200px]]&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;D&#039;&#039;&#039;eflector &#039;&#039;&#039;E&#039;&#039;&#039;mitter &#039;&#039;&#039;C&#039;&#039;&#039;luster &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;DECS&#039;&#039;&#039;, represents the newest Federation breakthroughs in Federation tactical shield technology. This innovative new system utilizes a convex “honeycombed&amp;quot; arrangement of octagonal emitters offset slightly to produce a unified, overlapping tactical field. This primary tactical system allows a tighter tactical shield to be produced, thus resulting in a lessened tactical shield cross section, which in turn reduces starship detectability.&lt;br /&gt;
&lt;br /&gt;
Whereas the Rosenanté class of starship possesses the standard &#039;&#039;&#039;D&#039;&#039;&#039;eflector &#039;&#039;&#039;E&#039;&#039;&#039;mitter &#039;&#039;&#039;A&#039;&#039;&#039;rray (&#039;&#039;&#039;DEA&#039;&#039;&#039;) that all Federation starships do, they use that particular system as a primary shielding system. The &#039;&#039;&#039;DECS&#039;&#039;&#039; assembly operates by producing several smaller polyhedral segments of shield interdependability, rather than creating a &amp;quot;shell&amp;quot; segment standard to all other Federation starships. The &#039;&#039;&#039;DECS&#039;&#039;&#039; requires more power than standard tactical &#039;&#039;&#039;DEA&#039;&#039;&#039; systems, but yields a 20% increase in shield output. The &#039;&#039;&#039;DECS&#039;&#039;&#039; is calibrated to respond and recalibrate the loss of a single emitter or emitter cluster, resulting in a greater overall performance and defensive capability of ship systems. The standard &#039;&#039;&#039;DECS&#039;&#039;&#039; system is installed to provide tactical shielding whenever the starship is experiencing &#039;&#039;&#039;DEA&#039;&#039;&#039; failure, or power requirements do not allow the use of the &#039;&#039;&#039;DEA&#039;&#039;&#039;. Another advantage of the DECS over the standard DEA is its modular design. It is quick and efficient to repair or replace in the field whereas the replacement of the DEA system requires a major overhaul at a Starbase.&lt;br /&gt;
&lt;br /&gt;
==8.0 Hull Integrated Stealth System. ==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;H&#039;&#039;&#039;ull &#039;&#039;&#039;I&#039;&#039;&#039;ntegrated &#039;&#039;&#039;S&#039;&#039;&#039;tealth &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;HISS&#039;&#039;&#039;, is a series of alterations to the ships exterior hull and systems to create a reduced sensor and visual silhouette. The details of the &#039;&#039;&#039;HISS&#039;&#039;&#039; are highly classified, although the general concepts behind its incorporation are not. A network of specialized integrated hull webbing allows the hull to emit energies that effectively allow light waves to pass through it and its contents. In addition to visual bands of radiation, the specially designed ablative hull absorbs sensor energy, while emitting the same energy signature as the starship&#039;s surrounding space. Thus, the vessel becomes virtually undetectable either through detection or complete omission of detection. In addition to this, specialized hull features act as complex Magnetic field disruptors, reducing the EM field of the vessel, and also neutralize radioactive emissions through a complex series of intercoolers and sheathed cowlings. The ship&#039;s Impulse, Thruster and Bussard collection systems are incorporated to nearly negate all detectable signs of their use. When the HISS is active and used in conjunction with strict Emissions protocols, the ship vanishes from visual and sensor detection.&lt;br /&gt;
&lt;br /&gt;
==9.0 Advanced Sensors Systems==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;I&#039;&#039;&#039;mproved &#039;&#039;&#039;S&#039;&#039;&#039;ensor &#039;&#039;&#039;I&#039;&#039;&#039;ntegrated &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;ISIS&#039;&#039;&#039;, is a modified high yield Federation sensor array. The &#039;&#039;&#039;ISIS&#039;&#039;&#039; utilizes the newest development in sensor technology to quantum phase the active and passive ship&#039;s sensors to greatly reduce detectability. These new sensors are more powerful, and almost impossible to detect without performing extensive and time consuming alterations to a starship&#039;s sensor array, which then is useless to detecting other aspects of its surrounding. Some of this technology is loosely based on cloaking principles.&lt;br /&gt;
&lt;br /&gt;
==10.0 Sensor Displacement System==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Se&#039;&#039;&#039;nsor &#039;&#039;&#039;Di&#039;&#039;&#039;splacement &#039;&#039;&#039;S&#039;&#039;&#039;ystem, Or &#039;&#039;&#039;SEDIS&#039;&#039;&#039;, allows the Rosenanté class of starship to offset its actual energy signature, and even produce an additional energy signature. This is designed to improve the starships ability to prevent &amp;quot;true&amp;quot; detection, or to act as a decoy system in the event that the starship is detected. This system is capable of operating within a 60OKm range of the vessel.&lt;br /&gt;
&lt;br /&gt;
==11.0 Displaced Communications System==&lt;br /&gt;
The &#039;&#039;&#039;Di&#039;&#039;&#039;splaced &#039;&#039;&#039;Comm&#039;&#039;&#039;unications &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;DICOMMS&#039;&#039;&#039;, is based on the same technology as the &#039;&#039;&#039;ISIS&#039;&#039;&#039;. This energy is used to send nearly undetectable communications. The Rosenanté class starship is equipped with standard Federation communications systems as well.&lt;br /&gt;
&lt;br /&gt;
==12.0 Interior Systems Modifications==&lt;br /&gt;
There have been a variety of interior alterations to the interior, habitable areas of the Rosenanté class starship. The most apparent alterations are in the functionality of the corridor and turbolift systems. The oversized personnel quarters offer the most luxurious and spacious accommodations aboard any Starfleet posting, while unique interaction software insures crewmembers peace of mind.&lt;br /&gt;
&lt;br /&gt;
Many Starfleet admirals believe that the Tactical and Scientific Equipment carried by a Starship to be the most important asset to any Starfleet facility or starship. The designers of the Rosenanté class of Starship also felt that crew morale would also serve a very integral role in the operation of the starship. To these ends the interactive systems and habitations were designed to provide a reassuring and relaxing environment for the ships crew.&lt;br /&gt;
&lt;br /&gt;
==12.1 Safety Systems==&lt;br /&gt;
The most paramount function of any Starship is the maintenance of its crew in adverse conditions. Integral to this school of thought is the ability to protect the crew under hostile threats. To these ends, the designers of the Rosenanté class starship developed a series of counterinsurgency systems to minimize crew contact with alien forces boarding the vessel.&lt;br /&gt;
&lt;br /&gt;
==12.1.1 Isolation Field Systems==&lt;br /&gt;
The &#039;&#039;&#039;I&#039;&#039;&#039;solation &#039;&#039;&#039;F&#039;&#039;&#039;ield &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;IFS&#039;&#039;&#039;, was designed with the intent to isolate hostile alien forces that boarded the vessel for the crew. This function is considered vitally important when consideration is given to the fact that the Rosenanté class starship possesses a very highly trained crew. The &#039;&#039;&#039;IFS&#039;&#039;&#039; fundamentally isolates the threat through the use of perpetual containment fields, reinforced by miniature shield defenses for the IFS emitter assembly. The &#039;&#039;&#039;IFS&#039;&#039;&#039; is always active, limiting the mobility of non-authorized personnel, securing sensitive sectors of the ship, and effectively hindering the process of any hostile aliens that may manage to board the vessel. The ship&#039;s computer monitors the movements of every official member of the ship&#039;s crew at all times. In this manner, the computer is able to activate or deactivate the &#039;&#039;&#039;IFS&#039;&#039;&#039; screens on an individual basis as needed. This allows authorized crewmembers access to shipboard systems and compartments as needed. The &#039;&#039;&#039;IFS&#039;&#039;&#039; consists of a series of Level 8 containment fields spaced an even 12.5-meters along the corridors of the vessel. In addition to these, an &#039;&#039;&#039;IFS&#039;&#039;&#039; field also isolates each access portal and hatch. In the event that a commbadge should be captured, or fail, that badge is automatically removed from all access rosters, until security can investigate the occurrence.&lt;br /&gt;
&lt;br /&gt;
As a benefit of the perpetually active IFIS fields, studies indicate that shipboard damage caused by fire and/or decompression was drastically reduced. The fields prevented large area decompression, and also limited the range of fire dispersion radically.&lt;br /&gt;
&lt;br /&gt;
Although in larger compartments the &#039;&#039;&#039;IFS&#039;&#039;&#039; system is not perpetual; all compartments are equipped with the capacity to further &amp;quot;compartmentalize&amp;quot; these large open areas. The computer is capable of assessing threats to the crew and equipment of the vessel, and can respond using the &#039;&#039;&#039;IFS&#039;&#039;&#039; system, nearly instantly. The &#039;&#039;&#039;IFS&#039;&#039;&#039; system was designed to operate independently of the ships main power supply when necessary. Each &#039;&#039;&#039;IFS&#039;&#039;&#039; emitter and processor assembly is equipped with an independent high-yield Sodium Kelleride power system. This power cell is further treated with a Potassium Unified catalyst. This allows the production of oxygen as a by-product whenever the secondary power system is operated. This allows a crewmember to be compartmentalized in an otherwise decompressed area to survive asphyxiation and loss of pressure. This secondary power system will allow the full yield operation of the &#039;&#039;&#039;IFS&#039;&#039;&#039; emitter in question for a period of 4 standard hours. Setting the emitter to a lower containment setting can extend this time.&lt;br /&gt;
&lt;br /&gt;
==12.1.2 Fire Suppression Systems==&lt;br /&gt;
&lt;br /&gt;
Although the &#039;&#039;&#039;IFS&#039;&#039;&#039; system hinders the progress of a shipboard fire, it will not necessarily extinguish it. To facilitate this a hybrid field emitter, environmental suppression system was developed. This system isolates the flame from its fuel source using advanced forcefield emissions systems, while simultaneously adjusting the environment around the fire to assist in its suppression. A functional &#039;&#039;&#039;IFS&#039;&#039;&#039; contained area further supports the adjustments, as a smaller area of the ship need be adjusted at any one time. There are certain types of plasma fires that could be unaffected by environmental conditions and or can not be contained in this manner. It is in those situations that the fire suppression systems remove the fire and all affected material through use of the ships sight-to-sight transporters. If this cannot be performed due to a greater risk being imposed on the crew, more conventional methods of fire suppression must be performed.&lt;br /&gt;
&lt;br /&gt;
==12.1.3 Internal Ballistics Dampening Fields==&lt;br /&gt;
In key areas where materials stored aboard ship have the potential to be propelled through sections of the ship, a series of &#039;&#039;&#039;I&#039;&#039;&#039;nternal &#039;&#039;&#039;Ba&#039;&#039;&#039;llistics &#039;&#039;&#039;D&#039;&#039;&#039;ampening Fields, or &#039;&#039;&#039;I-BAD&#039;&#039;&#039; Fields, have been implemented. These fields are found primarily in the armory, cargo bays, Shuttle Bays, storage bays, and personnel quarters. The &#039;&#039;&#039;I-BAD&#039;&#039;&#039; system uses advanced internal sensing equipment specialized to calculate mass and velocity of non-anchored materials. In the event that these materials should be propelled at a speed that the computer should indicate hazardous to crew, then a series of inertial Dampening Fields are erected to reduce the velocity of the offending object. The IDF relays cannot stop a propelled item, although it can shorten its travel distance and relative speed considerably. The sensing systems ignore the movements of personnel. The &#039;&#039;&#039;I-BAD&#039;&#039;&#039; emitters in no way affect the reduction of stresses upon the vessel caused by acceleration, deceleration, or maneuvering.&lt;br /&gt;
&lt;br /&gt;
==12.1.4 Advanced Ergonomics==&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-4up.jpg|thumb|right|500px|]]&lt;br /&gt;
&lt;br /&gt;
Throughout the vessel, specialized memory seating systems have been implemented. These systems monitor the stresses upon the body of the crewmember presently utilizing them and adjust the contact points with the crewmember to minimize physical stresses. All station seating and this material affects standard seating in personnel quarters. The design is such that is can self adjust to allow for non-humanoid crewmembers. The standard bedding and medical bio beds are also adjusted in this manner. This has proven to reduce fatigue and discomfort resulting from prolonged duty shifts. The conceptualization of advanced ergonomic design is further implemented in the layouts and design of the personnel quarters on the ship. Each individual’s quarters are ergonomically designed to his or her unique specifications. The height and shape of interactive systems, the design of the shelving and storage facilities, and the layout of the waste management system are all adjusted to the unique requirements of the compartment owner. Even habitation shape and colour are carefully implemented to create an environment in harmony with its occupant.&lt;br /&gt;
&lt;br /&gt;
==12.1.5 Tactical Sight-to-Sight Transport==&lt;br /&gt;
The ship&#039;s computer possesses the ability to assess tactical breaches in to the vessel&#039;s security. When appropriate, the computer may implement tactical redistribution of security personnel to facilitate the disarmament of tactical threats. The computer determines the size of any aggressive and/or threatening force on the ship, and then determines logical methods of containing and overcoming this threat. The computer is capable of briefing shipboard security personnel on the state of a threat, operating IFIS units, and evacuating non-essential personnel from potential or actual combat areas. The computer can deploy security personnel using sight-to-sight transporters and tactical deployment subroutines. In addition to automatic response to internal tactical threats, the ship&#039;s computer can suggest tactical deployment options for security personnel, utilizing data stored in its memory. This tactical deployment data is only suggested when asked for, and is prepared for planetoid deployment, boarding actions, counter-boarding actions, and sight security. When a medical situation presents itself the same sight-to-sight transporter system can be utilized to transport critical patients to the sickbay.&lt;br /&gt;
&lt;br /&gt;
==12.1.6 Emergency Medical Hologram==&lt;br /&gt;
The Emergency Medical Hologram, as standard to all Federation starships, is also present on the Rosenanté class starship. A series of modifications allows the EMH system to be activated in any habitable portion of the vessel. This function is performed by a series of specialized emitters seeded throughout the ship. Each emitter is equipped with an array of medical scanners and programmed with trauma and first aid protocols. Each emitter assembly is capable of independent operation in the event that power systems become unavailable. The Sodium Kelleride power source can maintain EMH use for 1 hour before expending its charge. When operating normally, the EMH can access the ship&#039;s medical database. When operating independently, only the trauma and first aid subroutines may be accessed. While operating on ship&#039;s systems no more than three EMH programs may be running at any one time. Independent operation is possible among any number of EMH emitters.&lt;br /&gt;
&lt;br /&gt;
==12.1.7 Emergency Replication System==&lt;br /&gt;
The &#039;&#039;&#039;E&#039;&#039;&#039;mergency &#039;&#039;&#039;R&#039;&#039;&#039;eplication &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;ERS&#039;&#039;&#039;, is a series of secondary replicators that operate completely independent of the ships systems. The &#039;&#039;&#039;ERS&#039;&#039;&#039; units are located aft and fore of the starship, two per deck. They are always inert until activated. The &#039;&#039;&#039;ERS&#039;&#039;&#039; system is &amp;quot;hidden&amp;quot; behind corridor paneling, and consists of a single equipment replicator, a single food replicator, an atmospheric condenser, a single medical tricorder, a standard tricorder, and a pair of Class I Phasers. A high-yield Sodium Kelleride Battery that allows light use of the replicators, for a period of 3 days, powers the &#039;&#039;&#039;ERS&#039;&#039;&#039; units. The Tricorders and Phasers are pre-powered, and can be recharged once, using the supplied connections. Accessing the ERS panel will alert security. The Class I phasers require a personal authorization code to be activated. The computer monitors the &#039;&#039;&#039;ERS&#039;&#039;&#039; system very closely, immediately notifying engineering if a problem is detected.&lt;br /&gt;
Although the &#039;&#039;&#039;ERS&#039;&#039;&#039; is a fully functional Replication system, it is programmed to create materials that require very little energy to reproduce. Thus, the food replicators produce only a single nutrient rich disk for consumption. The Tool replicator is limited to equipment that possesses simple physical structures, such as hand tools and only simple electronics materials. Neither replicator system can reproduce power sources, or advanced electronics.&lt;br /&gt;
&lt;br /&gt;
==12.1.8 Emergency Transporters==&lt;br /&gt;
The Rosenanté class starship is equipped with 2 emergency transporters. These transporters are located centrally along the berth and length of the vessel on decks 5 and 15. The emergency transporters are integrated into the primary corridor on the aforementioned decks. All transporter hardware is stowed in the surrounding corridor structures. 20 high-yield Sodium Kelleride Batteries independently power the control operation panel and the emergency transport systems. Each Emergency transporter is also equipped with its own short-range sensor array, for destination determination. The control panel is &amp;quot;hidden&amp;quot; behind the corridor paneling, and floor paneling hides the transporter pad. In order to operate the transporter this floor paneling must be removed. The emergency transporters are each capable of transporting 60 personnel.&lt;br /&gt;
After that there is no power remaining to continue transporter functions. Preparing the Emergency transporters for use alerts security.&lt;br /&gt;
&lt;br /&gt;
==12.2 Medical Bay==&lt;br /&gt;
Due to the number of personnel stationed aboard the Rosenanté class starship, the standard&lt;br /&gt;
Medical Bay arrangement was not utilized. Instead a specialized medical bay was designed to maximize space, while still attending to the variable needs of the ship&#039;s crew. To this end, the sickbay possesses a complete quarantine ward, a single surgical ward, and the central sickbay. A office allows for the CMO to perform administrative tasks without interruption.&lt;br /&gt;
In the surgical area, all the equipment necessary to perform any level of surgery is present. Specialized negative pressure systems allow operations to continue upon contaminated personnel without worry of integrity loss.&lt;br /&gt;
The central medical area is equipped with the newest and most efficient systems that general practice has to offer. A multitude of sensors and medical dedicated processors facilitate medical data gathering, while advanced holographic modeling systems allow hands-off data model construction. Forty Biobeds are located in the Sickbay, which studies indicate was the most efficient number of patients to treat at one time. &lt;br /&gt;
&lt;br /&gt;
In addition to the standard biobeds and Infirmary treatment bay, There are also two dedicated Medical Laboratories, One General Practice Clinical Ward and Three configurable Bays, which can be changed to meet the specific requirements of the medical needs of the vessel.&lt;br /&gt;
&lt;br /&gt;
The Quarantine area is equipped with a series of Biocide units capable of detecting, isolating and destroying over three hundred billion contagions. Negative pressure atmospheric systems, ionic decontamination systems, and bio-phased containment fields guarantee the isolation of harmful contagions. All containment systems in the sickbay are maintained by secondary and tertiary power systems. A medical dedicated replication system allows the creation of any replicable pharmaceutical known to Starfleet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&amp;lt;small&amp;gt;All images compliments of Roger Wackowski&amp;lt;br&amp;gt;Spiral Drive concepts by Anthony Keen&amp;lt;br&amp;gt;All other technical aspects, created, written and designed by Daniel Greene&amp;lt;/small&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
[[Category: Engineering]][[Category: Database]][[Category: Active Ships]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=The_Chimera_Directive&amp;diff=55386</id>
		<title>The Chimera Directive</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=The_Chimera_Directive&amp;diff=55386"/>
		<updated>2012-05-09T16:20:58Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* 12.2 Medical Bay */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;  &lt;br /&gt;
  &lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
== 1.0	CHIMERA DIRECTIVE INTRODUCTION ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-1up.jpg|thumb|500px|The Rosenante Class Starship]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1.1 MISSION OBJECTIVES FOR ROSENANTÉ CLASS PROJECT&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Starfleet has long been charged with a broad spectrum of responsibilities to the citizens of the Federation and to the lifeforms of the Galaxy at large. As the volume of explored space continues to grow, and with it the Federation itself, so do Starfleet&#039;s duties. &lt;br /&gt;
&lt;br /&gt;
These duties range from relatively mundane domestic and civil missions, to cultural contact and diplomacy, to defense, to our primary mission of exploration and research. Many of these responsibilities are best carried out with relatively small, specialized ships. Yet there continues to be an ongoing need for an even narrower role vessel to protect the Federation against enemies that would use espionage and subversion to wage war against the Federation.&lt;br /&gt;
&lt;br /&gt;
This particular threat to Federation security is further complicated by political and economic restraints placed upon the Federation caused by the demands of maintaining an active war first against the Cardassian Union and then a Civil War between Doenitz Loyalists and 52nd Fleet seditionists. The Federation had suddenly found itself pressed on many fronts at various levels of engagement, often ill-prepared or incapable of information gathering against potential interior and exterior threats to the continued existence of the Federation.&lt;br /&gt;
&lt;br /&gt;
In response to the alarming number of intelligence related activities conducted against Federation projects, personnel, and equipment by exterior Intelligence Organizations, such as the Tal Shiar, the Dominion Shapeshifters, and The Cardassian Obsidian Order, Starfleet Intelligence has found itself grossly outnumbered, and under-appreciated by Starfleet Command. This lack of interdepartmental cooperation was only strengthened by Starfleet Intelligence&#039;s inability to detect and detain several pro-Revolutionary agents that had managed to infiltrate Starfleet Command, the Council of the President, and several other critical posts within the governmental structure of the Federation. The agents proved to be the first signs of the coming Civil war that would shake the foundations of the United Federation of Planets over the next several years.&lt;br /&gt;
&lt;br /&gt;
These breeches of critical security protocol within the government provided the critics of Starfleet Intelligence with ammunition to pressure Starfleet Command to tighten its control on the Intelligence Department. In late 2390s, with the Cardassian Union pressing their offensive against the Federation, Starfleet Intelligence learned of other threats to the Federation&#039;s continuing existence, as reports began to come into Starfleet Intelligence&#039;s Romulan desk reporting a large number of Romulan Infiltrators had somehow managed to concentrate themselves on the Federation Starships patrolling the Neutral Zone. With reports indicating that the Tal Shiar compromised a large majority of Starships patrolling the Neutral Zone, and with SFI fearing a Romulan Invasion, a massive counter Intelligence operation began. This operation, dubbed Sword and Shield, inserted several dozen Starfleet counterintelligence Specialists onboard the suspected Starships. For the better part of a year, these operatives played a deadly game of cloak and dagger against the expectant Tal Shiar operatives. This massive undertaking resulted in the largest capture of external espionage operatives in Starfleet history, 38 Starfleet officers (including 2 Ship Captains) and 12 Enlisted Starfleet personnel were arrested and charged with espionage against the Federation. 6 Starfleet Intelligence operatives lost their lives in this operation. &lt;br /&gt;
&lt;br /&gt;
It was to this threat that Admiral Rodrigo Doenitz would propose a solution. That solution came in the form of a Starship, dedicated completely to the tasks of espionage and interdiction operations. The vessel would be operated entirely independently of Starfleet command. Only Starfleet Intelligence would have any command authority over the vessel and its missions. This proposal created a scandalous outcry by Starfleet Command Officers, with the end result becoming less than favorable to the Doenitz cause.&lt;br /&gt;
&lt;br /&gt;
However, the dramatic success of Sword and Shield eased the tension against Starfleet Intelligence, and by the end of the War with the Cardassian Union in 2398; Starfleet Command realized the inability of SFI to conduct operations in hostile space, or to operate independently without the immediate assistance of Starship under Starfleet Command authority. It was in August of that year that Admiral Talbot, with the support of Admiral Doenitz proposed the idea of creating a new class of Starship capable of supporting Intelligence operations in hostile space, while simultaneously capable of performing signal, traffic and visual surveillance of facilities, ship movements and communications. Admiral Talbot argued that if SFI were equipped with such a vessel during the War, that the effectiveness of the Cardassian attack against the UFP would have been greatly reduced, if not altogether neutralized. Additionally, Talbot argued, such a ship working in Romulan space would have been priceless in determining the intentions and movements of the Tal Shiar during Operation Sword and Shield.&lt;br /&gt;
&lt;br /&gt;
Admiral Talbot’s conceptual Starship was deemed impossible to build, and also in violation of Starfleet Intelligence Command’s charter and the project was immediately disapproved. But that was not the end of the situation. &lt;br /&gt;
&lt;br /&gt;
Admiral Talbot, through secret channels with the complete support of Admiral Rodrigo Doenitz established a secret construction facility. Through various nefarious means, funds were funneled into the project and experienced Starfleet ship engineers were tasked to assist in developing a new class of Starship that could function efficiently within the confines established by the joint visions held by the two admirals.&lt;br /&gt;
&lt;br /&gt;
A special Starfleet Intelligence Operation was begun in a secret shipyard facility around early 2397. SFI operatives assigned to the operation interviewed and recruited Starship designers from across the Federation, purposely avoiding any designer that had ever worked on a Starship Project for the Federation in the past. These designers, assisted by the technical and personal experiences, of selected Starship Engineers laid down the design parameters for the project.&lt;br /&gt;
&lt;br /&gt;
After Admiral Doenitz’s successful coup, the project would prove to outlive many of its critics. With the full power of the office of the president of the Federation, Doenitz fast tracked his project making it an official Presidential Directive. This Directive was codenamed the Chimera Directive.&lt;br /&gt;
&lt;br /&gt;
The Rosenanté Class Starship designed by the Chimera Directive represents the most advanced design and systems innovations in the Federation. The basic design concept was developed around the Sovereign class and is considered the most advanced evolution of Starfleet Ship design to date.&lt;br /&gt;
&lt;br /&gt;
==Design Objectives==&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;&#039;&#039;Pursuant to Starfleet Intelligence Directive 1045.35, the following objectives have been established for the Rosenanté Class Starship development project:&#039;&#039;&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*	Provide a mobile platform for a wide range of ongoing intelligence and counterintelligence projects.&lt;br /&gt;
*	Provide autonomous capability for full execution of Starfleet Intelligence policy and directive options in hostile areas of space.&lt;br /&gt;
*	Incorporate recent advances in technology and protocols.&lt;br /&gt;
&lt;br /&gt;
To provide for these objectives, the Designers recommended that the Rosenanté class starship meets or exceeds the design goals in the following specification Categories;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Propulsion&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Sustainable cruise Velocity of Warp Factor 9.4. Ability to maintain speeds of up to Warp Factor 9.7 for periods of up to 12 Hours.&lt;br /&gt;
*	Sixth-phase dilithium controlled matter/antimatter reactor for primary power. Sustainable field output to exceed 1, 650 cochranes, peak transitional surge reserve to exceed 4,225% of nominal output. (170ns phase)&lt;br /&gt;
*	Warp Driver coils efficiency to meet or exceed 98% at speeds up to Warp 8.0. Minimum efficiency of 68% to be maintained through Warp 9.4. Life cycle of all primary coil elements to meet or exceed 1,200,000 cochrane-hours between neutron purge refurbishment. Secondary coil elements to meet or exceed 2,000,000 cochrane-hours between neutron purge refurbishment.&lt;br /&gt;
*	Warp field geometry to incorporate modified 85° Z-axis compression characteristics on forward warp lobe for increased peak transitional efficiency at high warp. Warp Nacelle centerlines to conform to 2.56: 1.1 ratio of separation to maximize field strength.&lt;br /&gt;
*	Secondary (impulse) propulsion systems to provide sub-light velocities up to and including .92 light speed (c). Engine systems of choice to include but not limited to at least two YPS 8063 fusion drive motors. All units to be equipped with subspace drive accelerators, field output not less than 180 millicochranes at 1.02 X l0³K. Reactor Modules to be field replaceable.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Mission&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Ability to operate independent of Starbase refurbishment for moderate periods of time. Independent operation mode capability of 1 Standard years at nominal Warp 6. Ability to execute deep-space exploration missions including charting and mapping, hostile contact scenarios, intelligence gathering and infiltration missions, full technical, biological and ecological studies.&lt;br /&gt;
*	Ability to support a wide range of mission-related ongoing research and other projects without impact on primary mission operations.&lt;br /&gt;
*	&#039;Full Spectrum EM, optical, subspace flux, Gravimetric, particle, and quark population analysis sensor capability. Multimode neutrino interferometery instrumentation. Wide band life sciences analysis capability. 2 twelve-meter interphasic field focused telescopes.&lt;br /&gt;
*	Upgradeable experiment and sensor array design. Ability to support on-board and probe mounted science and intelligence instrumentation.&lt;br /&gt;
*	Support facilities for auxiliary spacecraft and instrumented probes for short-range operations to include at least 1 independent launch, resupply, and repair bays.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Environment/Crew&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Environmental systems to conform to Starfleet Regulatory Agency (SFRA)- standard 102.9 for Class M compatible oxygen breathing personnel. All life-critical systems to be triply redundant. Life support modules to be replaceable at major Starbase layover to permit vehicle-wide adaptation to Class H, K or L environmental conditions.&lt;br /&gt;
*	Ability to support up to 200 non-crew personnel for mission related operations.&lt;br /&gt;
*	Facilities to support Class M environmental range in all individual living quarters, provisions for 2% of living quarters to be equipped to support Class H, K and L environmental conditions. Additional 1% of living quarters volume to be equipped for Class N and N (2) environmental adaptation.&lt;br /&gt;
*	All habitable volumes to be protected to SFRA-standard 347.3(a) levels for EM and radiation. Subspace flux differential to be maintained within 0.02 millicochranes.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Tactical&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Defensive Shielding to exceed 9.85 X 103 kW primary energy dissipation rate. All tactical Shielding to have full redundancy, with auxiliary system able to provide 75% of primary rating.&lt;br /&gt;
*	Tactical systems to include full array of Type XII phaser bank elements on hull capable of 6.1MW maximum single emitter output. 6 Photon Torpedo launchers required for ship defensive capabilities.&lt;br /&gt;
*	Tactical systems to include anti-detection components capable of defeating sensor and optical scan.&lt;br /&gt;
*	Tactical systems to include variable decreased emissions systems affecting primary and secondary drive systems.&lt;br /&gt;
*	Tactical systems to include components to reproduce or produce false sensor signatures at displaced coordinates in vessel reference.&lt;br /&gt;
*	Tactical systems to include components to produce ambient radiation and gravitational energies consistent with surrounding spatial occurrences.&lt;br /&gt;
*	Tactical systems to include variable EM field dampening systems to reduce or eliminate vessel EM fields and signatures.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Design Life&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Space frame design life of approximately 100 years, assuming approximately 5 major ship- wide system swap outs and upgrades at average intervals of 20 years. Such upgrades help ensure the continuing usefulness of the ship even though significant advances in technology are anticipated during that time. Minor refurbishment and upgrade to occur at approximately one- to five year intervals, depending on specific mission requirements and hardware availability.&lt;br /&gt;
&lt;br /&gt;
==2.0 General Overview==&lt;br /&gt;
&lt;br /&gt;
The Rosenanté class of Starship was originally categorized as an intelligence-gathering vessel. The Rosenanté class is only the second starship class created by Starfleet command to receive this designation. The other is the Spectre Class. While most starships may be adapted for many different mission types, the Rosenanté class starship is designed primarily to perform a single type of mission objective, in effect limiting her overall flexibility within a more generalized Starfleet. Seen from a comfortable distance of two or three kilometres, the starship takes on the resemblance of the more familiar Sovereign class explorers. Upon closer inspection however, one can see that the engineering hull is more sleek, lending a highly manoeuvrable appearance to the Rosenanté class of starship. The engineering hull actually extends both above and below the saucer section, lowering the overall silhouette of the class. Additionally, the saucer section itself boasts a number of changes that are easily noticed even by the most novice of observers. This divorce from standard Starfleet design protocols is both advantageous and disadvantageous for this class of starship. The unique hull design allows an immediate reduction in stresses generated by high warp speeds, while allowing greater manoeuvrability at sub-light speeds. This hull design concept has its drawbacks however, as high speed warp manoeuvrability is reduced in favour of speed. The exterior hull material is stronger, lighter and more durable than that used in standard starship production. This reduces the need for otherwise necessary supports and braces, leaving a greater interior volume for habitation. This material used on the ship&#039;s hull is more difficult to reproduce and repair, as specialized facilities must be implemented to perform these functions.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;2.1 Physical Arrangement&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-2up.jpg|right|300px]]&lt;br /&gt;
&lt;br /&gt;
The hull, remarkably birdlike in its strong, hollow construction, is reinforced against flight stresses by active energy fields that tighten and flex where required to compensate for natural and artificial internal and external forces. Structures integrated into the hull allow for a variety of necessary functions. &lt;br /&gt;
&lt;br /&gt;
The bridge consolidates the command positions for the rest of the starship, windows allow crewmembers needed vistas while in space, phaser arrays and photon torpedoes provide offence and defence against hostile forces, and a specialized communications system allows interaction with other worlds and their ships.&lt;br /&gt;
&lt;br /&gt;
Lifeboats allow for escape in dire emergencies, transporter emitters afford reliable near instant movement of crew and gear, navigational sensors and deflectors give the starship distant vision and a method for clearing obstacles, and powerful warp engines propel the starship at amazing speeds.&lt;br /&gt;
&lt;br /&gt;
The twenty-eight decks are internally divided among major load-bearing structures. A great many systems, especially the habitation sections are suspended within the open spaces, essentially &amp;quot;floating&amp;quot; on flexible ligaments to minimize mechanical, thermal, and conductive radiation shocks.&lt;br /&gt;
&lt;br /&gt;
The living areas of the starship have been designed for maximum comfort and safety while the crew is conducting a mission. Long-term studies of humanoid cultures have revealed that as each race embarked upon permanent occupation of space, large personal living spaces had to be established, especially on early sub-light missions. The Rosenanté class starship allows for some 120 square meters of living space per person, in addition to community space and areas allotted to purely working functions.&lt;br /&gt;
&lt;br /&gt;
==3.0 Spacecraft Structure==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.1 Main Skeletal Structure&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The primary space frame of the Rosenanté class starship is fabricated from an interlocking series of Terminium/Tritium microfilament truss frames. These members average l.05m² in cross section and are capable of bearing the same load as the standard Tritanium/Duranium truss averaging l.27m² in cross section used in standard starship construction. These truss frames are located an average of 20 meters across the ship&#039;s exterior, while the standard trusses would be located every 25 meters along a ships exterior. The tightening of the trusses allows the vessel to withstand greater stress imposed upon it by warp travel, while still producing a lighter space frame.&lt;br /&gt;
&lt;br /&gt;
As with other starship designs, larger numbers of these trusses are located integral to the main impulse engine sections, the warp nacelle pylons, docking interface latches, and along the centerline of the hull structure. Smaller Trusses averaging 0.35m² in cross section are located every five meters on average, and also provide internal supports within the deck and core structure of the spacecraft interior.&lt;br /&gt;
&lt;br /&gt;
A mechanical framework provides physical integrity to the vehicle while at rest. A parallel series of aluminum crystal foam stringers are phase transition bonded to the primary trusses, providing low frequency vibration attenuation across the main truss structure, as well as support for certain utility conduits.&lt;br /&gt;
&lt;br /&gt;
Also attached to these stringers are various conformal devices built into the hulls structure, including elements of the deflector shield grid, H.l.S.S. components, as well as subspace radio antennas, which are incorporated into the skin of the spacecraft.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.2 Secondary Framework&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mounted to the primary space frame is a secondary framework of micro-extruded Terminium trusses to which the inner hull of the structure is directly attached. The secondary framework is mounted by means of 3.2 cm diameter X 5.1 centimeter long semi rigid polydurinide support rods, permitting a limited amount of mechanical isolation from the primary space frame for purposes of strain relief, plus sound and vibration isolation. Secondary space frame segments are also separated from each other (although mechanically attached) to permit replacement of inner hull segments and associated utilities infrastructure during major Starbase layover.&lt;br /&gt;
&lt;br /&gt;
Structural integrity during powered flight is provided by a series of forcefields that reinforce the physical framework. This structural integrity field (SIP) is distributed through a network of molybdenum-jacketed wave-guides, which in turn distribute SIF energy into ceramic-polymer conductive elements throughout the space frame. Without the structural integrity field, the vehicle would be unable to withstand accelerations greater than 3l.4 m/s² without significant deformation, or greater than 49.18 m/s² without unrecoverable structural damage.&lt;br /&gt;
&lt;br /&gt;
Exterior hull substrate is joined to the primary load bearing trusses by means of 4.8-cm diameter electron-bonded duranium pins at 1.01-meter intervals. These pins are slip-fitted into an insulating AGP ceramic fiber jacket that provides thermal insulation between the space frame and the exterior hull. The pins, jacketing, and hull segments are gamma welded together.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.3 Hull Layers&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The exterior of the spacecraft consists of multiple layers, which afford structural and atmospheric integrity for the space frame, integral wave-guides and field conductive members for the structural Integrity Field (SIP) and H.I.S.S components, and pathways for other utilities (including deflector grids), as well as resistance to radiation and thermal energy.&lt;br /&gt;
The exterior shell substrate is composed of interlaced micro-foam duranium filaments. These filaments are gamma welded into a series of contiguous composite segments that are 4.7 cm thick and are typically 2 meters in width. The substrate segments are electron-bonded to three reinforcing layers of 1.2- cm biaxially stressed terranium fabric, which provide additional torsion strength.&lt;br /&gt;
&lt;br /&gt;
In areas immediately adjacent to major structural members, four layers of 2.3-cm fabric are used. The substrate layer is attached to major structural members by electron-bonded duranium fasteners at 2.5-cm intervals. The substrate segments are not intended to be replaceable, except by phase-transition bonding using a transporter assembly jig during major Starbase layovers.&lt;br /&gt;
Two 3.76-cm layers of low-density expanded ceramic-polyrner composites provide thermal insulation and secondary SIP and H.I.S.S. conductivity. These layers are separated by an 8.7-cm multiaxis triennium truss framework, which provides additional thermal insulation and a pass through for fixed utility conduits.&lt;br /&gt;
&lt;br /&gt;
A 4.2-cm layer of monocrystal beryllium silicate infused with somniferous polycarbonate whiskers provides radiation attenuation. This layer is networked with a series of 2.3-cm X 0.85-cm molybdenum-jacketed conduits. These conduits, which occur at 1.3-m intervals, serve as triphase wave-guides for the secondary structural integrity field. Conductive tritium rods penetrate the wave-guides at l0-cm intervals and transfer SIF energy into the ceramic-polymer conductive layer.&lt;br /&gt;
The outermost hull layer is composed of a 1.6-cm sheet of AGP ablative ceramic fabric chemically bonded onto a substrate of 0.15-cm triermium foil. This material is formed into segments approximately 3.7m² and is attached to the radiation attenuation layer by a series of duranium fasteners, which allows individual segments to be replaced as necessary. (Micrometeor erosion is kept to a minimum by the deflector system, but is sufficient to warrant replacement of 30% of the leading edge on the average of every 7.2 standard years.) Individual outer hull segments are machined to a tolerance of ±0.05-mm to allow for minimum drag through the interstellar medium. Joints between segments are manufactured to a tolerance of ±0.025-mm.&lt;br /&gt;
&lt;br /&gt;
Also incorporated into the outermost hull layer is a series of super conducting molybdenum-jacketed wave-guide conduits, which serve to absorb and disperse sensor emission energy that interacts with the hull. Segmented sections of this network serve as housings for the unique DECS components, responsible for producing the ship’s tactical deflector. Unlike a standard starship, there are no thermal regulating assemblies built into the skin of the starship. Instead this duty is regulated through a series of intercoolers and radiators housed inside the interior of the Bussard Collector Assembly.&lt;br /&gt;
&lt;br /&gt;
==4.0 Command Systems==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.1 The Bridge&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Bridge, located on Deck 1, provides primary operational control of the Rosenanté class starship. The bridge directly supervises all primary mission operations and coordinates all departmental activities. These activities are handled through the individual command consoles located in various positions on the bridge. These workstations are modular and can be interchanged, removed, or added as necessary to fulfill specialized mission requirements. At any one time there can be up to 12 workstations installed. The standard bridge design calls for 2 Science Stations, 1 Operations Station, 1 Flight Control Station, l Auxiliary Engineering Station, 1 Tactical station, 1 Communications/ H.I.S.S. station, 1 Internal Security Station, and 2 Command Stations, one each for the ship’s commander, and the First Officer.&lt;br /&gt;
Other facilities located on Deck 1 include Astrogation, the captain&#039;s ready room and head, the crew head, and a small mission briefing room.&lt;br /&gt;
Major connections to the bridge include a pair of Turbolift shafts, four electron-plasma power distribution wave-guide conduits; four environmental support plenum groups, nine primary and two back-up optical data network trunks, two replicator wave-guide conduits, and three service crawlways. As an interesting side note, a tertiary backup power distribution system consisting of hardwired nonreactive, conductive ceramic-polymer relays are also in place.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.2 Display Panels&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The display panels on the bridge and through out the ship are constructed and operated the same as those on any other Federation starship. The layouts and reactivity of the panels are augmented and display properties shown in a different manner. The coloration of the interaction displays is altered to create a different aesthetic affect, while also allowing a variant-programming matrix to be utilized. This new language utilizes advances in Holoprogramming to create three-dimensional matrix strings; this in turn allows a more efficient and quicker computer response time. Critical internal components of the display panels are mapped to the molecular level allowing a replication driven pro-holographic matrix damage control system to repair damaged components. The components necessary to facilitate this activity are collectively known as the &#039;&#039;&#039;Se&#039;&#039;&#039;lf-&#039;&#039;&#039;Re&#039;&#039;&#039;plicating &#039;&#039;&#039;Da&#039;&#039;&#039;mage &#039;&#039;&#039;C&#039;&#039;&#039;ontrol &#039;&#039;&#039;S&#039;&#039;&#039;ystem (&#039;&#039;&#039;SERDACS&#039;&#039;&#039;). The &#039;&#039;&#039;SERDACS&#039;&#039;&#039; components are present in all non-integrity dependant systems throughout the ship. &lt;br /&gt;
&lt;br /&gt;
In addition to the standard anchored display consoles located throughout the ship, a series of Holoemitters have been seeded throughout the vessel to allow ship&#039;s personnel to utilize a holographic interface to tie directly into the ships computer regardless of the location of the crewmember. These emitters also allow the EMH to be activated in any compartment in the ship, and also allow for the construction of holographic crewmembers to fill non-critical positions on the ship. These holoemitters are capable of creating non-electronic tools for emergency use, and in conjunction with replication systems could produce vital simplified component reproduction anywhere aboard ship.&lt;br /&gt;
&lt;br /&gt;
==4.3 Bridge Stations==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.1 Flight Control (CONN)&#039;&#039;&#039; &amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the actual piloting and navigation of the ship. From this station all SIF and IDF systems are monitored, as well as navigational deflectors, and their subsequent systems. This console performs the same functions as it would on board any other Federation starship.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.2 Operations Management (OPS)&#039;&#039;&#039; &amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for power maintenance and resource allocation. This console dictates priority status of all shipboard systems and operations. They coordinate activities between departments and between the ship and away missions. This console performs the same functions as it would on board any other Federation starship.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.3 Tactical Operations (TACOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the operation, monitoring and maintenance of the ship&#039;s tactical systems. These systems include the phaser arrays, the photon torpedo deployment systems, probe	deployment systems, H.I.S.S. system, Signal displacement system, tractor beams, and Tactical deflector systems. The Tactical station aboard the Rosenanté class starship differs from those of standard Federation starships. The main difference is the divorce of the ship&#039;s tactical systems from the internal security systems of the ship. This allows the tactical officer the ability to concentrate on the tactical aspects of the ship without the need to also monitor the internal security status of the ship. Another major difference in the Rosenanté class starship is the addition of a sensor array specifically for use by the tactical officer.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.4 Security Operations (SECOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the monitoring and operation of internal ship security systems. The Operator of this console is responsible for the deployment of ship&#039;s security personnel aboard the ship. This console controls the internal security containment fields, internal ship&#039;s sensors. The SECOPS officer can monitor the security status, security systems and personnel deployment for the entire ship. They can control door mechanisms, containment fields, the turbolift car, and weapons settings of all Federation weaponry on the ship. In addition, security can control personnel access to restricted areas, and utilize sight-to-sight onboard transporters.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.5 Communications (COMMOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the encryption and decryption of intercepted communications, for the transmission of communications, maintaining the Emissions Control Protocols, and the operation of specialized communications interception equipment. The Communications officer is often called upon to triangulate communications sources, decipher enemy transmissions, and encrypt outgoing communications. They often assist in Traffic Analysis of enemy troop deployment, and maintain secure communications with away teams.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.6 Science Stations I &amp;amp; II&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
These consoles are responsible for data collections, primary and lateral sensor operations, and database referencing. It is the responsibility of the science officer to operate the ship&#039;s sensors, teleoptical systems, and imaging systems. They observe, record and document data important to shipboard mission objectives. These stations can be utilized together or separately. This station also acts as the primary database access terminal for the Federation database carried aboard all Federation starships. Both passive and active sensors are controlled from this station.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.7 Auxiliary Engineering Station&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This station is responsible for maintaining and monitoring shipboard systems. This console works in conjunction with main engineering, and is capable of performing the same functions as the computer in that section of the ship. From this station the warp fields can be tuned, altered or monitored, as can all primary and secondary shipboard systems. This station is not always manned.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.8 Command Stations I &amp;amp; II&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
These consoles are responsible for the maintenance and monitoring of the ship&#039;s computer and all primary and secondary systems. Only the commanding and executive officer have access to these consoles. From these consoles the commanding officers can display data concerning ship&#039;s systems, status, condition, position, speed, heading, and power management distribution. These consoles can access the database, and has priority authority over all computer functions. These consoles are the only terminals capable of activating the ship&#039;s self-destruct mechanism. Any officer in command of the starship may utilize these consoles, although some functions may be unavailable.&lt;br /&gt;
&lt;br /&gt;
==5.0 The Computer System==&lt;br /&gt;
The computer system aboard the Rosenanté class starship is identical in construction to the computers used on other Federation Starships. They utilize the same back up and failsafe hardware and communicate through the same methods as the standard starship computer. The computer system of the Rosenanté class starship is composed of 2 synchronized computer cores, identical to those used in the Galaxy Class starship. The only differences between the standard Federation computers and those aboard the Rosenanté are the storage medium and programming language that the system uses to communicate.&lt;br /&gt;
The storage of data and processing networks of a standard Federation computer system depend upon isolinear chips. On the Rosenanté a new type of data storage chip, the Hololinear chip is introduced. Taking advantage of new replication and holographic programming breakthroughs, the new Hololinear chips, or HL chips, allow data to be stored in a four-dimensional, subspace format. A new programming language known a &#039;&#039;&#039;B&#039;&#039;&#039;ilinear &#039;&#039;&#039;U&#039;&#039;&#039;nilateral &#039;&#039;&#039;N&#039;&#039;&#039;etworking &#039;&#039;&#039;C&#039;&#039;&#039;ode (&#039;&#039;&#039;BUNC&#039;&#039;&#039;) allows data to be stored in a temprometric tagged holographic string, thereby allowing data to be stacked almost exponentially upon other data, linked by temprometric strings of associated data. Retrieval time is decreased as the data can be read from any point along its data string, rather than starting at a specified point as is required by the standard isolinear chip design.&lt;br /&gt;
&lt;br /&gt;
==6.0 Warp Propulsion Systems==&lt;br /&gt;
The Warp propulsion system in the Rosenanté class starship is radically different from Those used in other starships. The majority of the system is developed to utilize existing warp technology and materials. There is however a few major changes in the system. All warp engineers are familiar with the laws of warp transition, which dictates that warp geometry and power requirements dictate a vessel&#039;s ability to achieve various levels of warp speed. This same law also dictates that a warp field must be balanced in order to achieve maximum efficiency to make a warp transition.&lt;br /&gt;
&lt;br /&gt;
The Graph below represents the transition energy requirements for the Galaxy Class Starship design and also for that of the Rosenanté class starship.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:RWC.jpg|Center|400px]]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
ln the chart above the Cochrane values are represented over the white bar for the Rosenanté Class starship. At lower warps (below Warp 6) there is an actual decrease in warp efficiency, although at higher warp there is a worthwhile increase in efficiency, where the differences in efficiency matter most. It is important to note that a Galaxy class starship is incapable of traveling at Warp 9.97, and thus the numbers represented for that class is theoretical.&lt;br /&gt;
&lt;br /&gt;
The ability to sustain warp 9.97 is a result of multiple warp engines working in synchronization and a natural by-product of the embedded nacelle design. The synchronization of the dual warp drive is accomplished through the use of a &#039;&#039;&#039;W&#039;&#039;&#039;arp &#039;&#039;&#039;E&#039;&#039;&#039;nergy &#039;&#039;&#039;Sy&#039;&#039;&#039;nchronization &#039;&#039;&#039;R&#039;&#039;&#039;outer, or &#039;&#039;&#039;WESYR&#039;&#039;&#039;. The &#039;&#039;&#039;WESYR&#039;&#039;&#039; unit is highly classified, but its basic function is to synchronize otherwise out of synch Waveforms created within two near identical meshed Tuned Plasma Streams. Because of the additional energy that this system produces, a higher capacity EPS Power Tap and Series Relays were developed to handle the additional power loads. A dual bypass system allows any single Warp drive to power ships functions, at a significant reduction in overall power. Also a major redesign feature of the upgraded power system resulted in the addition of a second Port and Starboard Power conduit assembly and relay subassembly. This allows the power delivery system to function more efficiently.&lt;br /&gt;
&lt;br /&gt;
Interestingly enough, a bizarre natural byproduct of running a dual synchronized Warp Field is the creation of a &amp;quot;double&amp;quot; warp bubble. These warp bubbles are divided by 2.3-mnm (micronanometers) and help produce the effect of the change of reduction caused when making Warp Transitions. As subspace resistance passes through the Outer shield it is reduced as normal, then again as the remaining resistance passes through the inner bubble, it is further reduced. This causes the starship to experience less resistance and shearing warp stress associated with high rate warp travel and maneuvering.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Spiral Warp Drive&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In addition to the standard warp drive used by all federation starships, the Rosenanté class is also equipped with an experimental Spiral Warp Drive. This drive creates a subspace &amp;quot;tunnel&amp;quot; or &amp;quot;wormhole&amp;quot;  through which the Rosenanté may then travel. The tunnel integrity is maintained by the main deflector dish. The tunnel basically allows the ship to drop into subspace, effectively disappearing from normal space for a short period of time. The speeds that are achieved through the use of this drive are akin to those used by the Borg when using transwarp conduits. Unlike transwarp conduits, however,the tunnel being opened by the Rosenanté would dissipate as soon as the ship moves through it. In a similar manner, the spiral drive can only be used to travel in straight lines. This means that the vessel may make a periodic series of short hops to correct course when using this system.&lt;br /&gt;
&lt;br /&gt;
==7.0 Deflector Emitter Cluster System (DECS) ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-3up.jpg|left|200px]]&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;D&#039;&#039;&#039;eflector &#039;&#039;&#039;E&#039;&#039;&#039;mitter &#039;&#039;&#039;C&#039;&#039;&#039;luster &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;DECS&#039;&#039;&#039;, represents the newest Federation breakthroughs in Federation tactical shield technology. This innovative new system utilizes a convex “honeycombed&amp;quot; arrangement of octagonal emitters offset slightly to produce a unified, overlapping tactical field. This primary tactical system allows a tighter tactical shield to be produced, thus resulting in a lessened tactical shield cross section, which in turn reduces starship detectability.&lt;br /&gt;
&lt;br /&gt;
Whereas the Rosenanté class of starship possesses the standard &#039;&#039;&#039;D&#039;&#039;&#039;eflector &#039;&#039;&#039;E&#039;&#039;&#039;mitter &#039;&#039;&#039;A&#039;&#039;&#039;rray (&#039;&#039;&#039;DEA&#039;&#039;&#039;) that all Federation starships do, they use that particular system as a primary shielding system. The &#039;&#039;&#039;DECS&#039;&#039;&#039; assembly operates by producing several smaller polyhedral segments of shield interdependability, rather than creating a &amp;quot;shell&amp;quot; segment standard to all other Federation starships. The &#039;&#039;&#039;DECS&#039;&#039;&#039; requires more power than standard tactical &#039;&#039;&#039;DEA&#039;&#039;&#039; systems, but yields a 20% increase in shield output. The &#039;&#039;&#039;DECS&#039;&#039;&#039; is calibrated to respond and recalibrate the loss of a single emitter or emitter cluster, resulting in a greater overall performance and defensive capability of ship systems. The standard &#039;&#039;&#039;DECS&#039;&#039;&#039; system is installed to provide tactical shielding whenever the starship is experiencing &#039;&#039;&#039;DEA&#039;&#039;&#039; failure, or power requirements do not allow the use of the &#039;&#039;&#039;DEA&#039;&#039;&#039;. Another advantage of the DECS over the standard DEA is its modular design. It is quick and efficient to repair or replace in the field whereas the replacement of the DEA system requires a major overhaul at a Starbase.&lt;br /&gt;
&lt;br /&gt;
==8.0 Hull Integrated Stealth System. ==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;H&#039;&#039;&#039;ull &#039;&#039;&#039;I&#039;&#039;&#039;ntegrated &#039;&#039;&#039;S&#039;&#039;&#039;tealth &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;HISS&#039;&#039;&#039;, is a series of alterations to the ships exterior hull and systems to create a reduced sensor and visual silhouette. The details of the &#039;&#039;&#039;HISS&#039;&#039;&#039; are highly classified, although the general concepts behind its incorporation are not. A network of specialized integrated hull webbing allows the hull to emit energies that effectively allow light waves to pass through it and its contents. In addition to visual bands of radiation, the specially designed ablative hull absorbs sensor energy, while emitting the same energy signature as the starship&#039;s surrounding space. Thus, the vessel becomes virtually undetectable either through detection or complete omission of detection. In addition to this, specialized hull features act as complex Magnetic field disruptors, reducing the EM field of the vessel, and also neutralize radioactive emissions through a complex series of intercoolers and sheathed cowlings. The ship&#039;s Impulse, Thruster and Bussard collection systems are incorporated to nearly negate all detectable signs of their use. When the HISS is active and used in conjunction with strict Emissions protocols, the ship vanishes from visual and sensor detection.&lt;br /&gt;
&lt;br /&gt;
==9.0 Advanced Sensors Systems==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;I&#039;&#039;&#039;mproved &#039;&#039;&#039;S&#039;&#039;&#039;ensor &#039;&#039;&#039;I&#039;&#039;&#039;ntegrated &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;ISIS&#039;&#039;&#039;, is a modified high yield Federation sensor array. The &#039;&#039;&#039;ISIS&#039;&#039;&#039; utilizes the newest development in sensor technology to quantum phase the active and passive ship&#039;s sensors to greatly reduce detectability. These new sensors are more powerful, and almost impossible to detect without performing extensive and time consuming alterations to a starship&#039;s sensor array, which then is useless to detecting other aspects of its surrounding. Some of this technology is loosely based on cloaking principles.&lt;br /&gt;
&lt;br /&gt;
==10.0 Sensor Displacement System==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Se&#039;&#039;&#039;nsor &#039;&#039;&#039;Di&#039;&#039;&#039;splacement &#039;&#039;&#039;S&#039;&#039;&#039;ystem, Or &#039;&#039;&#039;SEDIS&#039;&#039;&#039;, allows the Rosenanté class of starship to offset its actual energy signature, and even produce an additional energy signature. This is designed to improve the starships ability to prevent &amp;quot;true&amp;quot; detection, or to act as a decoy system in the event that the starship is detected. This system is capable of operating within a 60OKm range of the vessel.&lt;br /&gt;
&lt;br /&gt;
==11.0 Displaced Communications System==&lt;br /&gt;
The &#039;&#039;&#039;Di&#039;&#039;&#039;splaced &#039;&#039;&#039;Comm&#039;&#039;&#039;unications &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;DICOMMS&#039;&#039;&#039;, is based on the same technology as the &#039;&#039;&#039;ISIS&#039;&#039;&#039;. This energy is used to send nearly undetectable communications. The Rosenanté class starship is equipped with standard Federation communications systems as well.&lt;br /&gt;
&lt;br /&gt;
==12.0 Interior Systems Modifications==&lt;br /&gt;
There have been a variety of interior alterations to the interior, habitable areas of the Rosenanté class starship. The most apparent alterations are in the functionality of the corridor and turbolift systems. The oversized personnel quarters offer the most luxurious and spacious accommodations aboard any Starfleet posting, while unique interaction software insures crewmembers peace of mind.&lt;br /&gt;
&lt;br /&gt;
Many Starfleet admirals believe that the Tactical and Scientific Equipment carried by a Starship to be the most important asset to any Starfleet facility or starship. The designers of the Rosenanté class of Starship also felt that crew morale would also serve a very integral role in the operation of the starship. To these ends the interactive systems and habitations were designed to provide a reassuring and relaxing environment for the ships crew.&lt;br /&gt;
&lt;br /&gt;
==12.1 Safety Systems==&lt;br /&gt;
The most paramount function of any Starship is the maintenance of its crew in adverse conditions. Integral to this school of thought is the ability to protect the crew under hostile threats. To these ends, the designers of the Rosenanté class starship developed a series of counterinsurgency systems to minimize crew contact with alien forces boarding the vessel.&lt;br /&gt;
&lt;br /&gt;
==12.1.1 Isolation Field Systems==&lt;br /&gt;
The &#039;&#039;&#039;I&#039;&#039;&#039;solation &#039;&#039;&#039;F&#039;&#039;&#039;ield &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;IFS&#039;&#039;&#039;, was designed with the intent to isolate hostile alien forces that boarded the vessel for the crew. This function is considered vitally important when consideration is given to the fact that the Rosenanté class starship possesses a very highly trained crew. The &#039;&#039;&#039;IFS&#039;&#039;&#039; fundamentally isolates the threat through the use of perpetual containment fields, reinforced by miniature shield defenses for the IFS emitter assembly. The &#039;&#039;&#039;IFS&#039;&#039;&#039; is always active, limiting the mobility of non-authorized personnel, securing sensitive sectors of the ship, and effectively hindering the process of any hostile aliens that may manage to board the vessel. The ship&#039;s computer monitors the movements of every official member of the ship&#039;s crew at all times. In this manner, the computer is able to activate or deactivate the &#039;&#039;&#039;IFS&#039;&#039;&#039; screens on an individual basis as needed. This allows authorized crewmembers access to shipboard systems and compartments as needed. The &#039;&#039;&#039;IFS&#039;&#039;&#039; consists of a series of Level 8 containment fields spaced an even 12.5-meters along the corridors of the vessel. In addition to these, an &#039;&#039;&#039;IFS&#039;&#039;&#039; field also isolates each access portal and hatch. In the event that a commbadge should be captured, or fail, that badge is automatically removed from all access rosters, until security can investigate the occurrence.&lt;br /&gt;
&lt;br /&gt;
As a benefit of the perpetually active IFIS fields, studies indicate that shipboard damage caused by fire and/or decompression was drastically reduced. The fields prevented large area decompression, and also limited the range of fire dispersion radically.&lt;br /&gt;
&lt;br /&gt;
Although in larger compartments the &#039;&#039;&#039;IFS&#039;&#039;&#039; system is not perpetual; all compartments are equipped with the capacity to further &amp;quot;compartmentalize&amp;quot; these large open areas. The computer is capable of assessing threats to the crew and equipment of the vessel, and can respond using the &#039;&#039;&#039;IFS&#039;&#039;&#039; system, nearly instantly. The &#039;&#039;&#039;IFS&#039;&#039;&#039; system was designed to operate independently of the ships main power supply when necessary. Each &#039;&#039;&#039;IFS&#039;&#039;&#039; emitter and processor assembly is equipped with an independent high-yield Sodium Kelleride power system. This power cell is further treated with a Potassium Unified catalyst. This allows the production of oxygen as a by-product whenever the secondary power system is operated. This allows a crewmember to be compartmentalized in an otherwise decompressed area to survive asphyxiation and loss of pressure. This secondary power system will allow the full yield operation of the &#039;&#039;&#039;IFS&#039;&#039;&#039; emitter in question for a period of 4 standard hours. Setting the emitter to a lower containment setting can extend this time.&lt;br /&gt;
&lt;br /&gt;
==12.1.2 Fire Suppression Systems==&lt;br /&gt;
&lt;br /&gt;
Although the &#039;&#039;&#039;IFS&#039;&#039;&#039; system hinders the progress of a shipboard fire, it will not necessarily extinguish it. To facilitate this a hybrid field emitter, environmental suppression system was developed. This system isolates the flame from its fuel source using advanced forcefield emissions systems, while simultaneously adjusting the environment around the fire to assist in its suppression. A functional &#039;&#039;&#039;IFS&#039;&#039;&#039; contained area further supports the adjustments, as a smaller area of the ship need be adjusted at any one time. There are certain types of plasma fires that could be unaffected by environmental conditions and or can not be contained in this manner. It is in those situations that the fire suppression systems remove the fire and all affected material through use of the ships sight-to-sight transporters. If this cannot be performed due to a greater risk being imposed on the crew, more conventional methods of fire suppression must be performed.&lt;br /&gt;
&lt;br /&gt;
==12.1.3 Internal Ballistics Dampening Fields==&lt;br /&gt;
In key areas where materials stored aboard ship have the potential to be propelled through sections of the ship, a series of &#039;&#039;&#039;I&#039;&#039;&#039;nternal &#039;&#039;&#039;Ba&#039;&#039;&#039;llistics &#039;&#039;&#039;D&#039;&#039;&#039;ampening Fields, or &#039;&#039;&#039;I-BAD&#039;&#039;&#039; Fields, have been implemented. These fields are found primarily in the armory, cargo bays, Shuttle Bays, storage bays, and personnel quarters. The &#039;&#039;&#039;I-BAD&#039;&#039;&#039; system uses advanced internal sensing equipment specialized to calculate mass and velocity of non-anchored materials. In the event that these materials should be propelled at a speed that the computer should indicate hazardous to crew, then a series of inertial Dampening Fields are erected to reduce the velocity of the offending object. The IDF relays cannot stop a propelled item, although it can shorten its travel distance and relative speed considerably. The sensing systems ignore the movements of personnel. The &#039;&#039;&#039;I-BAD&#039;&#039;&#039; emitters in no way affect the reduction of stresses upon the vessel caused by acceleration, deceleration, or maneuvering.&lt;br /&gt;
&lt;br /&gt;
==12.1.4 Advanced Ergonomics==&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-4up.jpg|right|200px]]&lt;br /&gt;
&lt;br /&gt;
Throughout the vessel, specialized memory seating systems have been implemented. These systems monitor the stresses upon the body of the crewmember presently utilizing them and adjust the contact points with the crewmember to minimize physical stresses. All station seating and this material affects standard seating in personnel quarters. The design is such that is can self adjust to allow for non-humanoid crewmembers. The standard bedding and medical bio beds are also adjusted in this manner. This has proven to reduce fatigue and discomfort resulting from prolonged duty shifts. The conceptualization of advanced ergonomic design is further implemented in the layouts and design of the personnel quarters on the ship. Each individual’s quarters are ergonomically designed to his or her unique specifications. The height and shape of interactive systems, the design of the shelving and storage facilities, and the layout of the waste management system are all adjusted to the unique requirements of the compartment owner. Even habitation shape and colour are carefully implemented to create an environment in harmony with its occupant.&lt;br /&gt;
&lt;br /&gt;
==12.1.5 Tactical Sight-to-Sight Transport==&lt;br /&gt;
The ship&#039;s computer possesses the ability to assess tactical breaches in to the vessel&#039;s security. When appropriate, the computer may implement tactical redistribution of security personnel to facilitate the disarmament of tactical threats. The computer determines the size of any aggressive and/or threatening force on the ship, and then determines logical methods of containing and overcoming this threat. The computer is capable of briefing shipboard security personnel on the state of a threat, operating IFIS units, and evacuating non-essential personnel from potential or actual combat areas. The computer can deploy security personnel using sight-to-sight transporters and tactical deployment subroutines. In addition to automatic response to internal tactical threats, the ship&#039;s computer can suggest tactical deployment options for security personnel, utilizing data stored in its memory. This tactical deployment data is only suggested when asked for, and is prepared for planetoid deployment, boarding actions, counter-boarding actions, and sight security. When a medical situation presents itself the same sight-to-sight transporter system can be utilized to transport critical patients to the sickbay.&lt;br /&gt;
&lt;br /&gt;
==12.1.6 Emergency Medical Hologram==&lt;br /&gt;
The Emergency Medical Hologram, as standard to all Federation starships, is also present on the Rosenanté class starship. A series of modifications allows the EMH system to be activated in any habitable portion of the vessel. This function is performed by a series of specialized emitters seeded throughout the ship. Each emitter is equipped with an array of medical scanners and programmed with trauma and first aid protocols. Each emitter assembly is capable of independent operation in the event that power systems become unavailable. The Sodium Kelleride power source can maintain EMH use for 1 hour before expending its charge. When operating normally, the EMH can access the ship&#039;s medical database. When operating independently, only the trauma and first aid subroutines may be accessed. While operating on ship&#039;s systems no more than three EMH programs may be running at any one time. Independent operation is possible among any number of EMH emitters.&lt;br /&gt;
&lt;br /&gt;
==12.1.7 Emergency Replication System==&lt;br /&gt;
The &#039;&#039;&#039;E&#039;&#039;&#039;mergency &#039;&#039;&#039;R&#039;&#039;&#039;eplication &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;ERS&#039;&#039;&#039;, is a series of secondary replicators that operate completely independent of the ships systems. The &#039;&#039;&#039;ERS&#039;&#039;&#039; units are located aft and fore of the starship, two per deck. They are always inert until activated. The &#039;&#039;&#039;ERS&#039;&#039;&#039; system is &amp;quot;hidden&amp;quot; behind corridor paneling, and consists of a single equipment replicator, a single food replicator, an atmospheric condenser, a single medical tricorder, a standard tricorder, and a pair of Class I Phasers. A high-yield Sodium Kelleride Battery that allows light use of the replicators, for a period of 3 days, powers the &#039;&#039;&#039;ERS&#039;&#039;&#039; units. The Tricorders and Phasers are pre-powered, and can be recharged once, using the supplied connections. Accessing the ERS panel will alert security. The Class I phasers require a personal authorization code to be activated. The computer monitors the &#039;&#039;&#039;ERS&#039;&#039;&#039; system very closely, immediately notifying engineering if a problem is detected.&lt;br /&gt;
Although the &#039;&#039;&#039;ERS&#039;&#039;&#039; is a fully functional Replication system, it is programmed to create materials that require very little energy to reproduce. Thus, the food replicators produce only a single nutrient rich disk for consumption. The Tool replicator is limited to equipment that possesses simple physical structures, such as hand tools and only simple electronics materials. Neither replicator system can reproduce power sources, or advanced electronics.&lt;br /&gt;
&lt;br /&gt;
==12.1.8 Emergency Transporters==&lt;br /&gt;
The Rosenanté class starship is equipped with 2 emergency transporters. These transporters are located centrally along the berth and length of the vessel on decks 5 and 15. The emergency transporters are integrated into the primary corridor on the aforementioned decks. All transporter hardware is stowed in the surrounding corridor structures. 20 high-yield Sodium Kelleride Batteries independently power the control operation panel and the emergency transport systems. Each Emergency transporter is also equipped with its own short-range sensor array, for destination determination. The control panel is &amp;quot;hidden&amp;quot; behind the corridor paneling, and floor paneling hides the transporter pad. In order to operate the transporter this floor paneling must be removed. The emergency transporters are each capable of transporting 60 personnel.&lt;br /&gt;
After that there is no power remaining to continue transporter functions. Preparing the Emergency transporters for use alerts security.&lt;br /&gt;
&lt;br /&gt;
==12.2 Medical Bay==&lt;br /&gt;
Due to the number of personnel stationed aboard the Rosenanté class starship, the standard&lt;br /&gt;
Medical Bay arrangement was not utilized. Instead a specialized medical bay was designed to maximize space, while still attending to the variable needs of the ship&#039;s crew. To this end, the sickbay possesses a complete quarantine ward, a single surgical ward, and the central sickbay. A office allows for the CMO to perform administrative tasks without interruption.&lt;br /&gt;
In the surgical area, all the equipment necessary to perform any level of surgery is present. Specialized negative pressure systems allow operations to continue upon contaminated personnel without worry of integrity loss.&lt;br /&gt;
The central medical area is equipped with the newest and most efficient systems that general practice has to offer. A multitude of sensors and medical dedicated processors facilitate medical data gathering, while advanced holographic modeling systems allow hands-off data model construction. Forty Biobeds are located in the Sickbay, which studies indicate was the most efficient number of patients to treat at one time. &lt;br /&gt;
&lt;br /&gt;
In addition to the standard biobeds and Infirmary treatment bay, There are also two dedicated Medical Laboratories, One General Practice Clinical Ward and Three configurable Bays, which can be changed to meet the specific requirements of the medical needs of the vessel.&lt;br /&gt;
&lt;br /&gt;
The Quarantine area is equipped with a series of Biocide units capable of detecting, isolating and destroying over three hundred billion contagions. Negative pressure atmospheric systems, ionic decontamination systems, and bio-phased containment fields guarantee the isolation of harmful contagions. All containment systems in the sickbay are maintained by secondary and tertiary power systems. A medical dedicated replication system allows the creation of any replicable pharmaceutical known to Starfleet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&amp;lt;small&amp;gt;All images compliments of Roger Wackowski&amp;lt;br&amp;gt;Spiral Drive concepts by Anthony Keen&amp;lt;br&amp;gt;All other technical aspects, created, written and designed by Daniel Greene&amp;lt;/small&amp;gt;&amp;lt;/font&amp;gt;&lt;br /&gt;
[[Category: Engineering]][[Category: Database]][[Category: Active Ships]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
	<entry>
		<id>https://www.stf-wiki.com/index.php?title=The_Chimera_Directive&amp;diff=55385</id>
		<title>The Chimera Directive</title>
		<link rel="alternate" type="text/html" href="https://www.stf-wiki.com/index.php?title=The_Chimera_Directive&amp;diff=55385"/>
		<updated>2012-05-09T16:20:29Z</updated>

		<summary type="html">&lt;p&gt;Nicesociety: /* Credits */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;  &lt;br /&gt;
  &lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
== 1.0	CHIMERA DIRECTIVE INTRODUCTION ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-1up.jpg|thumb|500px|The Rosenante Class Starship]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1.1 MISSION OBJECTIVES FOR ROSENANTÉ CLASS PROJECT&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Starfleet has long been charged with a broad spectrum of responsibilities to the citizens of the Federation and to the lifeforms of the Galaxy at large. As the volume of explored space continues to grow, and with it the Federation itself, so do Starfleet&#039;s duties. &lt;br /&gt;
&lt;br /&gt;
These duties range from relatively mundane domestic and civil missions, to cultural contact and diplomacy, to defense, to our primary mission of exploration and research. Many of these responsibilities are best carried out with relatively small, specialized ships. Yet there continues to be an ongoing need for an even narrower role vessel to protect the Federation against enemies that would use espionage and subversion to wage war against the Federation.&lt;br /&gt;
&lt;br /&gt;
This particular threat to Federation security is further complicated by political and economic restraints placed upon the Federation caused by the demands of maintaining an active war first against the Cardassian Union and then a Civil War between Doenitz Loyalists and 52nd Fleet seditionists. The Federation had suddenly found itself pressed on many fronts at various levels of engagement, often ill-prepared or incapable of information gathering against potential interior and exterior threats to the continued existence of the Federation.&lt;br /&gt;
&lt;br /&gt;
In response to the alarming number of intelligence related activities conducted against Federation projects, personnel, and equipment by exterior Intelligence Organizations, such as the Tal Shiar, the Dominion Shapeshifters, and The Cardassian Obsidian Order, Starfleet Intelligence has found itself grossly outnumbered, and under-appreciated by Starfleet Command. This lack of interdepartmental cooperation was only strengthened by Starfleet Intelligence&#039;s inability to detect and detain several pro-Revolutionary agents that had managed to infiltrate Starfleet Command, the Council of the President, and several other critical posts within the governmental structure of the Federation. The agents proved to be the first signs of the coming Civil war that would shake the foundations of the United Federation of Planets over the next several years.&lt;br /&gt;
&lt;br /&gt;
These breeches of critical security protocol within the government provided the critics of Starfleet Intelligence with ammunition to pressure Starfleet Command to tighten its control on the Intelligence Department. In late 2390s, with the Cardassian Union pressing their offensive against the Federation, Starfleet Intelligence learned of other threats to the Federation&#039;s continuing existence, as reports began to come into Starfleet Intelligence&#039;s Romulan desk reporting a large number of Romulan Infiltrators had somehow managed to concentrate themselves on the Federation Starships patrolling the Neutral Zone. With reports indicating that the Tal Shiar compromised a large majority of Starships patrolling the Neutral Zone, and with SFI fearing a Romulan Invasion, a massive counter Intelligence operation began. This operation, dubbed Sword and Shield, inserted several dozen Starfleet counterintelligence Specialists onboard the suspected Starships. For the better part of a year, these operatives played a deadly game of cloak and dagger against the expectant Tal Shiar operatives. This massive undertaking resulted in the largest capture of external espionage operatives in Starfleet history, 38 Starfleet officers (including 2 Ship Captains) and 12 Enlisted Starfleet personnel were arrested and charged with espionage against the Federation. 6 Starfleet Intelligence operatives lost their lives in this operation. &lt;br /&gt;
&lt;br /&gt;
It was to this threat that Admiral Rodrigo Doenitz would propose a solution. That solution came in the form of a Starship, dedicated completely to the tasks of espionage and interdiction operations. The vessel would be operated entirely independently of Starfleet command. Only Starfleet Intelligence would have any command authority over the vessel and its missions. This proposal created a scandalous outcry by Starfleet Command Officers, with the end result becoming less than favorable to the Doenitz cause.&lt;br /&gt;
&lt;br /&gt;
However, the dramatic success of Sword and Shield eased the tension against Starfleet Intelligence, and by the end of the War with the Cardassian Union in 2398; Starfleet Command realized the inability of SFI to conduct operations in hostile space, or to operate independently without the immediate assistance of Starship under Starfleet Command authority. It was in August of that year that Admiral Talbot, with the support of Admiral Doenitz proposed the idea of creating a new class of Starship capable of supporting Intelligence operations in hostile space, while simultaneously capable of performing signal, traffic and visual surveillance of facilities, ship movements and communications. Admiral Talbot argued that if SFI were equipped with such a vessel during the War, that the effectiveness of the Cardassian attack against the UFP would have been greatly reduced, if not altogether neutralized. Additionally, Talbot argued, such a ship working in Romulan space would have been priceless in determining the intentions and movements of the Tal Shiar during Operation Sword and Shield.&lt;br /&gt;
&lt;br /&gt;
Admiral Talbot’s conceptual Starship was deemed impossible to build, and also in violation of Starfleet Intelligence Command’s charter and the project was immediately disapproved. But that was not the end of the situation. &lt;br /&gt;
&lt;br /&gt;
Admiral Talbot, through secret channels with the complete support of Admiral Rodrigo Doenitz established a secret construction facility. Through various nefarious means, funds were funneled into the project and experienced Starfleet ship engineers were tasked to assist in developing a new class of Starship that could function efficiently within the confines established by the joint visions held by the two admirals.&lt;br /&gt;
&lt;br /&gt;
A special Starfleet Intelligence Operation was begun in a secret shipyard facility around early 2397. SFI operatives assigned to the operation interviewed and recruited Starship designers from across the Federation, purposely avoiding any designer that had ever worked on a Starship Project for the Federation in the past. These designers, assisted by the technical and personal experiences, of selected Starship Engineers laid down the design parameters for the project.&lt;br /&gt;
&lt;br /&gt;
After Admiral Doenitz’s successful coup, the project would prove to outlive many of its critics. With the full power of the office of the president of the Federation, Doenitz fast tracked his project making it an official Presidential Directive. This Directive was codenamed the Chimera Directive.&lt;br /&gt;
&lt;br /&gt;
The Rosenanté Class Starship designed by the Chimera Directive represents the most advanced design and systems innovations in the Federation. The basic design concept was developed around the Sovereign class and is considered the most advanced evolution of Starfleet Ship design to date.&lt;br /&gt;
&lt;br /&gt;
==Design Objectives==&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;&#039;&#039;Pursuant to Starfleet Intelligence Directive 1045.35, the following objectives have been established for the Rosenanté Class Starship development project:&#039;&#039;&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*	Provide a mobile platform for a wide range of ongoing intelligence and counterintelligence projects.&lt;br /&gt;
*	Provide autonomous capability for full execution of Starfleet Intelligence policy and directive options in hostile areas of space.&lt;br /&gt;
*	Incorporate recent advances in technology and protocols.&lt;br /&gt;
&lt;br /&gt;
To provide for these objectives, the Designers recommended that the Rosenanté class starship meets or exceeds the design goals in the following specification Categories;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Propulsion&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Sustainable cruise Velocity of Warp Factor 9.4. Ability to maintain speeds of up to Warp Factor 9.7 for periods of up to 12 Hours.&lt;br /&gt;
*	Sixth-phase dilithium controlled matter/antimatter reactor for primary power. Sustainable field output to exceed 1, 650 cochranes, peak transitional surge reserve to exceed 4,225% of nominal output. (170ns phase)&lt;br /&gt;
*	Warp Driver coils efficiency to meet or exceed 98% at speeds up to Warp 8.0. Minimum efficiency of 68% to be maintained through Warp 9.4. Life cycle of all primary coil elements to meet or exceed 1,200,000 cochrane-hours between neutron purge refurbishment. Secondary coil elements to meet or exceed 2,000,000 cochrane-hours between neutron purge refurbishment.&lt;br /&gt;
*	Warp field geometry to incorporate modified 85° Z-axis compression characteristics on forward warp lobe for increased peak transitional efficiency at high warp. Warp Nacelle centerlines to conform to 2.56: 1.1 ratio of separation to maximize field strength.&lt;br /&gt;
*	Secondary (impulse) propulsion systems to provide sub-light velocities up to and including .92 light speed (c). Engine systems of choice to include but not limited to at least two YPS 8063 fusion drive motors. All units to be equipped with subspace drive accelerators, field output not less than 180 millicochranes at 1.02 X l0³K. Reactor Modules to be field replaceable.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Mission&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Ability to operate independent of Starbase refurbishment for moderate periods of time. Independent operation mode capability of 1 Standard years at nominal Warp 6. Ability to execute deep-space exploration missions including charting and mapping, hostile contact scenarios, intelligence gathering and infiltration missions, full technical, biological and ecological studies.&lt;br /&gt;
*	Ability to support a wide range of mission-related ongoing research and other projects without impact on primary mission operations.&lt;br /&gt;
*	&#039;Full Spectrum EM, optical, subspace flux, Gravimetric, particle, and quark population analysis sensor capability. Multimode neutrino interferometery instrumentation. Wide band life sciences analysis capability. 2 twelve-meter interphasic field focused telescopes.&lt;br /&gt;
*	Upgradeable experiment and sensor array design. Ability to support on-board and probe mounted science and intelligence instrumentation.&lt;br /&gt;
*	Support facilities for auxiliary spacecraft and instrumented probes for short-range operations to include at least 1 independent launch, resupply, and repair bays.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Environment/Crew&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Environmental systems to conform to Starfleet Regulatory Agency (SFRA)- standard 102.9 for Class M compatible oxygen breathing personnel. All life-critical systems to be triply redundant. Life support modules to be replaceable at major Starbase layover to permit vehicle-wide adaptation to Class H, K or L environmental conditions.&lt;br /&gt;
*	Ability to support up to 200 non-crew personnel for mission related operations.&lt;br /&gt;
*	Facilities to support Class M environmental range in all individual living quarters, provisions for 2% of living quarters to be equipped to support Class H, K and L environmental conditions. Additional 1% of living quarters volume to be equipped for Class N and N (2) environmental adaptation.&lt;br /&gt;
*	All habitable volumes to be protected to SFRA-standard 347.3(a) levels for EM and radiation. Subspace flux differential to be maintained within 0.02 millicochranes.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Tactical&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Defensive Shielding to exceed 9.85 X 103 kW primary energy dissipation rate. All tactical Shielding to have full redundancy, with auxiliary system able to provide 75% of primary rating.&lt;br /&gt;
*	Tactical systems to include full array of Type XII phaser bank elements on hull capable of 6.1MW maximum single emitter output. 6 Photon Torpedo launchers required for ship defensive capabilities.&lt;br /&gt;
*	Tactical systems to include anti-detection components capable of defeating sensor and optical scan.&lt;br /&gt;
*	Tactical systems to include variable decreased emissions systems affecting primary and secondary drive systems.&lt;br /&gt;
*	Tactical systems to include components to reproduce or produce false sensor signatures at displaced coordinates in vessel reference.&lt;br /&gt;
*	Tactical systems to include components to produce ambient radiation and gravitational energies consistent with surrounding spatial occurrences.&lt;br /&gt;
*	Tactical systems to include variable EM field dampening systems to reduce or eliminate vessel EM fields and signatures.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Design Life&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
*	Space frame design life of approximately 100 years, assuming approximately 5 major ship- wide system swap outs and upgrades at average intervals of 20 years. Such upgrades help ensure the continuing usefulness of the ship even though significant advances in technology are anticipated during that time. Minor refurbishment and upgrade to occur at approximately one- to five year intervals, depending on specific mission requirements and hardware availability.&lt;br /&gt;
&lt;br /&gt;
==2.0 General Overview==&lt;br /&gt;
&lt;br /&gt;
The Rosenanté class of Starship was originally categorized as an intelligence-gathering vessel. The Rosenanté class is only the second starship class created by Starfleet command to receive this designation. The other is the Spectre Class. While most starships may be adapted for many different mission types, the Rosenanté class starship is designed primarily to perform a single type of mission objective, in effect limiting her overall flexibility within a more generalized Starfleet. Seen from a comfortable distance of two or three kilometres, the starship takes on the resemblance of the more familiar Sovereign class explorers. Upon closer inspection however, one can see that the engineering hull is more sleek, lending a highly manoeuvrable appearance to the Rosenanté class of starship. The engineering hull actually extends both above and below the saucer section, lowering the overall silhouette of the class. Additionally, the saucer section itself boasts a number of changes that are easily noticed even by the most novice of observers. This divorce from standard Starfleet design protocols is both advantageous and disadvantageous for this class of starship. The unique hull design allows an immediate reduction in stresses generated by high warp speeds, while allowing greater manoeuvrability at sub-light speeds. This hull design concept has its drawbacks however, as high speed warp manoeuvrability is reduced in favour of speed. The exterior hull material is stronger, lighter and more durable than that used in standard starship production. This reduces the need for otherwise necessary supports and braces, leaving a greater interior volume for habitation. This material used on the ship&#039;s hull is more difficult to reproduce and repair, as specialized facilities must be implemented to perform these functions.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;2.1 Physical Arrangement&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-2up.jpg|right|300px]]&lt;br /&gt;
&lt;br /&gt;
The hull, remarkably birdlike in its strong, hollow construction, is reinforced against flight stresses by active energy fields that tighten and flex where required to compensate for natural and artificial internal and external forces. Structures integrated into the hull allow for a variety of necessary functions. &lt;br /&gt;
&lt;br /&gt;
The bridge consolidates the command positions for the rest of the starship, windows allow crewmembers needed vistas while in space, phaser arrays and photon torpedoes provide offence and defence against hostile forces, and a specialized communications system allows interaction with other worlds and their ships.&lt;br /&gt;
&lt;br /&gt;
Lifeboats allow for escape in dire emergencies, transporter emitters afford reliable near instant movement of crew and gear, navigational sensors and deflectors give the starship distant vision and a method for clearing obstacles, and powerful warp engines propel the starship at amazing speeds.&lt;br /&gt;
&lt;br /&gt;
The twenty-eight decks are internally divided among major load-bearing structures. A great many systems, especially the habitation sections are suspended within the open spaces, essentially &amp;quot;floating&amp;quot; on flexible ligaments to minimize mechanical, thermal, and conductive radiation shocks.&lt;br /&gt;
&lt;br /&gt;
The living areas of the starship have been designed for maximum comfort and safety while the crew is conducting a mission. Long-term studies of humanoid cultures have revealed that as each race embarked upon permanent occupation of space, large personal living spaces had to be established, especially on early sub-light missions. The Rosenanté class starship allows for some 120 square meters of living space per person, in addition to community space and areas allotted to purely working functions.&lt;br /&gt;
&lt;br /&gt;
==3.0 Spacecraft Structure==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.1 Main Skeletal Structure&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The primary space frame of the Rosenanté class starship is fabricated from an interlocking series of Terminium/Tritium microfilament truss frames. These members average l.05m² in cross section and are capable of bearing the same load as the standard Tritanium/Duranium truss averaging l.27m² in cross section used in standard starship construction. These truss frames are located an average of 20 meters across the ship&#039;s exterior, while the standard trusses would be located every 25 meters along a ships exterior. The tightening of the trusses allows the vessel to withstand greater stress imposed upon it by warp travel, while still producing a lighter space frame.&lt;br /&gt;
&lt;br /&gt;
As with other starship designs, larger numbers of these trusses are located integral to the main impulse engine sections, the warp nacelle pylons, docking interface latches, and along the centerline of the hull structure. Smaller Trusses averaging 0.35m² in cross section are located every five meters on average, and also provide internal supports within the deck and core structure of the spacecraft interior.&lt;br /&gt;
&lt;br /&gt;
A mechanical framework provides physical integrity to the vehicle while at rest. A parallel series of aluminum crystal foam stringers are phase transition bonded to the primary trusses, providing low frequency vibration attenuation across the main truss structure, as well as support for certain utility conduits.&lt;br /&gt;
&lt;br /&gt;
Also attached to these stringers are various conformal devices built into the hulls structure, including elements of the deflector shield grid, H.l.S.S. components, as well as subspace radio antennas, which are incorporated into the skin of the spacecraft.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.2 Secondary Framework&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mounted to the primary space frame is a secondary framework of micro-extruded Terminium trusses to which the inner hull of the structure is directly attached. The secondary framework is mounted by means of 3.2 cm diameter X 5.1 centimeter long semi rigid polydurinide support rods, permitting a limited amount of mechanical isolation from the primary space frame for purposes of strain relief, plus sound and vibration isolation. Secondary space frame segments are also separated from each other (although mechanically attached) to permit replacement of inner hull segments and associated utilities infrastructure during major Starbase layover.&lt;br /&gt;
&lt;br /&gt;
Structural integrity during powered flight is provided by a series of forcefields that reinforce the physical framework. This structural integrity field (SIP) is distributed through a network of molybdenum-jacketed wave-guides, which in turn distribute SIF energy into ceramic-polymer conductive elements throughout the space frame. Without the structural integrity field, the vehicle would be unable to withstand accelerations greater than 3l.4 m/s² without significant deformation, or greater than 49.18 m/s² without unrecoverable structural damage.&lt;br /&gt;
&lt;br /&gt;
Exterior hull substrate is joined to the primary load bearing trusses by means of 4.8-cm diameter electron-bonded duranium pins at 1.01-meter intervals. These pins are slip-fitted into an insulating AGP ceramic fiber jacket that provides thermal insulation between the space frame and the exterior hull. The pins, jacketing, and hull segments are gamma welded together.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;3.3 Hull Layers&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The exterior of the spacecraft consists of multiple layers, which afford structural and atmospheric integrity for the space frame, integral wave-guides and field conductive members for the structural Integrity Field (SIP) and H.I.S.S components, and pathways for other utilities (including deflector grids), as well as resistance to radiation and thermal energy.&lt;br /&gt;
The exterior shell substrate is composed of interlaced micro-foam duranium filaments. These filaments are gamma welded into a series of contiguous composite segments that are 4.7 cm thick and are typically 2 meters in width. The substrate segments are electron-bonded to three reinforcing layers of 1.2- cm biaxially stressed terranium fabric, which provide additional torsion strength.&lt;br /&gt;
&lt;br /&gt;
In areas immediately adjacent to major structural members, four layers of 2.3-cm fabric are used. The substrate layer is attached to major structural members by electron-bonded duranium fasteners at 2.5-cm intervals. The substrate segments are not intended to be replaceable, except by phase-transition bonding using a transporter assembly jig during major Starbase layovers.&lt;br /&gt;
Two 3.76-cm layers of low-density expanded ceramic-polyrner composites provide thermal insulation and secondary SIP and H.I.S.S. conductivity. These layers are separated by an 8.7-cm multiaxis triennium truss framework, which provides additional thermal insulation and a pass through for fixed utility conduits.&lt;br /&gt;
&lt;br /&gt;
A 4.2-cm layer of monocrystal beryllium silicate infused with somniferous polycarbonate whiskers provides radiation attenuation. This layer is networked with a series of 2.3-cm X 0.85-cm molybdenum-jacketed conduits. These conduits, which occur at 1.3-m intervals, serve as triphase wave-guides for the secondary structural integrity field. Conductive tritium rods penetrate the wave-guides at l0-cm intervals and transfer SIF energy into the ceramic-polymer conductive layer.&lt;br /&gt;
The outermost hull layer is composed of a 1.6-cm sheet of AGP ablative ceramic fabric chemically bonded onto a substrate of 0.15-cm triermium foil. This material is formed into segments approximately 3.7m² and is attached to the radiation attenuation layer by a series of duranium fasteners, which allows individual segments to be replaced as necessary. (Micrometeor erosion is kept to a minimum by the deflector system, but is sufficient to warrant replacement of 30% of the leading edge on the average of every 7.2 standard years.) Individual outer hull segments are machined to a tolerance of ±0.05-mm to allow for minimum drag through the interstellar medium. Joints between segments are manufactured to a tolerance of ±0.025-mm.&lt;br /&gt;
&lt;br /&gt;
Also incorporated into the outermost hull layer is a series of super conducting molybdenum-jacketed wave-guide conduits, which serve to absorb and disperse sensor emission energy that interacts with the hull. Segmented sections of this network serve as housings for the unique DECS components, responsible for producing the ship’s tactical deflector. Unlike a standard starship, there are no thermal regulating assemblies built into the skin of the starship. Instead this duty is regulated through a series of intercoolers and radiators housed inside the interior of the Bussard Collector Assembly.&lt;br /&gt;
&lt;br /&gt;
==4.0 Command Systems==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.1 The Bridge&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Bridge, located on Deck 1, provides primary operational control of the Rosenanté class starship. The bridge directly supervises all primary mission operations and coordinates all departmental activities. These activities are handled through the individual command consoles located in various positions on the bridge. These workstations are modular and can be interchanged, removed, or added as necessary to fulfill specialized mission requirements. At any one time there can be up to 12 workstations installed. The standard bridge design calls for 2 Science Stations, 1 Operations Station, 1 Flight Control Station, l Auxiliary Engineering Station, 1 Tactical station, 1 Communications/ H.I.S.S. station, 1 Internal Security Station, and 2 Command Stations, one each for the ship’s commander, and the First Officer.&lt;br /&gt;
Other facilities located on Deck 1 include Astrogation, the captain&#039;s ready room and head, the crew head, and a small mission briefing room.&lt;br /&gt;
Major connections to the bridge include a pair of Turbolift shafts, four electron-plasma power distribution wave-guide conduits; four environmental support plenum groups, nine primary and two back-up optical data network trunks, two replicator wave-guide conduits, and three service crawlways. As an interesting side note, a tertiary backup power distribution system consisting of hardwired nonreactive, conductive ceramic-polymer relays are also in place.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.2 Display Panels&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The display panels on the bridge and through out the ship are constructed and operated the same as those on any other Federation starship. The layouts and reactivity of the panels are augmented and display properties shown in a different manner. The coloration of the interaction displays is altered to create a different aesthetic affect, while also allowing a variant-programming matrix to be utilized. This new language utilizes advances in Holoprogramming to create three-dimensional matrix strings; this in turn allows a more efficient and quicker computer response time. Critical internal components of the display panels are mapped to the molecular level allowing a replication driven pro-holographic matrix damage control system to repair damaged components. The components necessary to facilitate this activity are collectively known as the &#039;&#039;&#039;Se&#039;&#039;&#039;lf-&#039;&#039;&#039;Re&#039;&#039;&#039;plicating &#039;&#039;&#039;Da&#039;&#039;&#039;mage &#039;&#039;&#039;C&#039;&#039;&#039;ontrol &#039;&#039;&#039;S&#039;&#039;&#039;ystem (&#039;&#039;&#039;SERDACS&#039;&#039;&#039;). The &#039;&#039;&#039;SERDACS&#039;&#039;&#039; components are present in all non-integrity dependant systems throughout the ship. &lt;br /&gt;
&lt;br /&gt;
In addition to the standard anchored display consoles located throughout the ship, a series of Holoemitters have been seeded throughout the vessel to allow ship&#039;s personnel to utilize a holographic interface to tie directly into the ships computer regardless of the location of the crewmember. These emitters also allow the EMH to be activated in any compartment in the ship, and also allow for the construction of holographic crewmembers to fill non-critical positions on the ship. These holoemitters are capable of creating non-electronic tools for emergency use, and in conjunction with replication systems could produce vital simplified component reproduction anywhere aboard ship.&lt;br /&gt;
&lt;br /&gt;
==4.3 Bridge Stations==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.1 Flight Control (CONN)&#039;&#039;&#039; &amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the actual piloting and navigation of the ship. From this station all SIF and IDF systems are monitored, as well as navigational deflectors, and their subsequent systems. This console performs the same functions as it would on board any other Federation starship.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.2 Operations Management (OPS)&#039;&#039;&#039; &amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for power maintenance and resource allocation. This console dictates priority status of all shipboard systems and operations. They coordinate activities between departments and between the ship and away missions. This console performs the same functions as it would on board any other Federation starship.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.3 Tactical Operations (TACOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the operation, monitoring and maintenance of the ship&#039;s tactical systems. These systems include the phaser arrays, the photon torpedo deployment systems, probe	deployment systems, H.I.S.S. system, Signal displacement system, tractor beams, and Tactical deflector systems. The Tactical station aboard the Rosenanté class starship differs from those of standard Federation starships. The main difference is the divorce of the ship&#039;s tactical systems from the internal security systems of the ship. This allows the tactical officer the ability to concentrate on the tactical aspects of the ship without the need to also monitor the internal security status of the ship. Another major difference in the Rosenanté class starship is the addition of a sensor array specifically for use by the tactical officer.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.4 Security Operations (SECOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the monitoring and operation of internal ship security systems. The Operator of this console is responsible for the deployment of ship&#039;s security personnel aboard the ship. This console controls the internal security containment fields, internal ship&#039;s sensors. The SECOPS officer can monitor the security status, security systems and personnel deployment for the entire ship. They can control door mechanisms, containment fields, the turbolift car, and weapons settings of all Federation weaponry on the ship. In addition, security can control personnel access to restricted areas, and utilize sight-to-sight onboard transporters.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.5 Communications (COMMOPS)&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This console is responsible for the encryption and decryption of intercepted communications, for the transmission of communications, maintaining the Emissions Control Protocols, and the operation of specialized communications interception equipment. The Communications officer is often called upon to triangulate communications sources, decipher enemy transmissions, and encrypt outgoing communications. They often assist in Traffic Analysis of enemy troop deployment, and maintain secure communications with away teams.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.6 Science Stations I &amp;amp; II&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
These consoles are responsible for data collections, primary and lateral sensor operations, and database referencing. It is the responsibility of the science officer to operate the ship&#039;s sensors, teleoptical systems, and imaging systems. They observe, record and document data important to shipboard mission objectives. These stations can be utilized together or separately. This station also acts as the primary database access terminal for the Federation database carried aboard all Federation starships. Both passive and active sensors are controlled from this station.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.7 Auxiliary Engineering Station&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
This station is responsible for maintaining and monitoring shipboard systems. This console works in conjunction with main engineering, and is capable of performing the same functions as the computer in that section of the ship. From this station the warp fields can be tuned, altered or monitored, as can all primary and secondary shipboard systems. This station is not always manned.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;4.3.8 Command Stations I &amp;amp; II&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
These consoles are responsible for the maintenance and monitoring of the ship&#039;s computer and all primary and secondary systems. Only the commanding and executive officer have access to these consoles. From these consoles the commanding officers can display data concerning ship&#039;s systems, status, condition, position, speed, heading, and power management distribution. These consoles can access the database, and has priority authority over all computer functions. These consoles are the only terminals capable of activating the ship&#039;s self-destruct mechanism. Any officer in command of the starship may utilize these consoles, although some functions may be unavailable.&lt;br /&gt;
&lt;br /&gt;
==5.0 The Computer System==&lt;br /&gt;
The computer system aboard the Rosenanté class starship is identical in construction to the computers used on other Federation Starships. They utilize the same back up and failsafe hardware and communicate through the same methods as the standard starship computer. The computer system of the Rosenanté class starship is composed of 2 synchronized computer cores, identical to those used in the Galaxy Class starship. The only differences between the standard Federation computers and those aboard the Rosenanté are the storage medium and programming language that the system uses to communicate.&lt;br /&gt;
The storage of data and processing networks of a standard Federation computer system depend upon isolinear chips. On the Rosenanté a new type of data storage chip, the Hololinear chip is introduced. Taking advantage of new replication and holographic programming breakthroughs, the new Hololinear chips, or HL chips, allow data to be stored in a four-dimensional, subspace format. A new programming language known a &#039;&#039;&#039;B&#039;&#039;&#039;ilinear &#039;&#039;&#039;U&#039;&#039;&#039;nilateral &#039;&#039;&#039;N&#039;&#039;&#039;etworking &#039;&#039;&#039;C&#039;&#039;&#039;ode (&#039;&#039;&#039;BUNC&#039;&#039;&#039;) allows data to be stored in a temprometric tagged holographic string, thereby allowing data to be stacked almost exponentially upon other data, linked by temprometric strings of associated data. Retrieval time is decreased as the data can be read from any point along its data string, rather than starting at a specified point as is required by the standard isolinear chip design.&lt;br /&gt;
&lt;br /&gt;
==6.0 Warp Propulsion Systems==&lt;br /&gt;
The Warp propulsion system in the Rosenanté class starship is radically different from Those used in other starships. The majority of the system is developed to utilize existing warp technology and materials. There is however a few major changes in the system. All warp engineers are familiar with the laws of warp transition, which dictates that warp geometry and power requirements dictate a vessel&#039;s ability to achieve various levels of warp speed. This same law also dictates that a warp field must be balanced in order to achieve maximum efficiency to make a warp transition.&lt;br /&gt;
&lt;br /&gt;
The Graph below represents the transition energy requirements for the Galaxy Class Starship design and also for that of the Rosenanté class starship.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:RWC.jpg|Center|400px]]&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
ln the chart above the Cochrane values are represented over the white bar for the Rosenanté Class starship. At lower warps (below Warp 6) there is an actual decrease in warp efficiency, although at higher warp there is a worthwhile increase in efficiency, where the differences in efficiency matter most. It is important to note that a Galaxy class starship is incapable of traveling at Warp 9.97, and thus the numbers represented for that class is theoretical.&lt;br /&gt;
&lt;br /&gt;
The ability to sustain warp 9.97 is a result of multiple warp engines working in synchronization and a natural by-product of the embedded nacelle design. The synchronization of the dual warp drive is accomplished through the use of a &#039;&#039;&#039;W&#039;&#039;&#039;arp &#039;&#039;&#039;E&#039;&#039;&#039;nergy &#039;&#039;&#039;Sy&#039;&#039;&#039;nchronization &#039;&#039;&#039;R&#039;&#039;&#039;outer, or &#039;&#039;&#039;WESYR&#039;&#039;&#039;. The &#039;&#039;&#039;WESYR&#039;&#039;&#039; unit is highly classified, but its basic function is to synchronize otherwise out of synch Waveforms created within two near identical meshed Tuned Plasma Streams. Because of the additional energy that this system produces, a higher capacity EPS Power Tap and Series Relays were developed to handle the additional power loads. A dual bypass system allows any single Warp drive to power ships functions, at a significant reduction in overall power. Also a major redesign feature of the upgraded power system resulted in the addition of a second Port and Starboard Power conduit assembly and relay subassembly. This allows the power delivery system to function more efficiently.&lt;br /&gt;
&lt;br /&gt;
Interestingly enough, a bizarre natural byproduct of running a dual synchronized Warp Field is the creation of a &amp;quot;double&amp;quot; warp bubble. These warp bubbles are divided by 2.3-mnm (micronanometers) and help produce the effect of the change of reduction caused when making Warp Transitions. As subspace resistance passes through the Outer shield it is reduced as normal, then again as the remaining resistance passes through the inner bubble, it is further reduced. This causes the starship to experience less resistance and shearing warp stress associated with high rate warp travel and maneuvering.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=goldenrod&amp;gt;&#039;&#039;&#039;Spiral Warp Drive&#039;&#039;&#039;&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In addition to the standard warp drive used by all federation starships, the Rosenanté class is also equipped with an experimental Spiral Warp Drive. This drive creates a subspace &amp;quot;tunnel&amp;quot; or &amp;quot;wormhole&amp;quot;  through which the Rosenanté may then travel. The tunnel integrity is maintained by the main deflector dish. The tunnel basically allows the ship to drop into subspace, effectively disappearing from normal space for a short period of time. The speeds that are achieved through the use of this drive are akin to those used by the Borg when using transwarp conduits. Unlike transwarp conduits, however,the tunnel being opened by the Rosenanté would dissipate as soon as the ship moves through it. In a similar manner, the spiral drive can only be used to travel in straight lines. This means that the vessel may make a periodic series of short hops to correct course when using this system.&lt;br /&gt;
&lt;br /&gt;
==7.0 Deflector Emitter Cluster System (DECS) ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-3up.jpg|left|200px]]&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;D&#039;&#039;&#039;eflector &#039;&#039;&#039;E&#039;&#039;&#039;mitter &#039;&#039;&#039;C&#039;&#039;&#039;luster &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;DECS&#039;&#039;&#039;, represents the newest Federation breakthroughs in Federation tactical shield technology. This innovative new system utilizes a convex “honeycombed&amp;quot; arrangement of octagonal emitters offset slightly to produce a unified, overlapping tactical field. This primary tactical system allows a tighter tactical shield to be produced, thus resulting in a lessened tactical shield cross section, which in turn reduces starship detectability.&lt;br /&gt;
&lt;br /&gt;
Whereas the Rosenanté class of starship possesses the standard &#039;&#039;&#039;D&#039;&#039;&#039;eflector &#039;&#039;&#039;E&#039;&#039;&#039;mitter &#039;&#039;&#039;A&#039;&#039;&#039;rray (&#039;&#039;&#039;DEA&#039;&#039;&#039;) that all Federation starships do, they use that particular system as a primary shielding system. The &#039;&#039;&#039;DECS&#039;&#039;&#039; assembly operates by producing several smaller polyhedral segments of shield interdependability, rather than creating a &amp;quot;shell&amp;quot; segment standard to all other Federation starships. The &#039;&#039;&#039;DECS&#039;&#039;&#039; requires more power than standard tactical &#039;&#039;&#039;DEA&#039;&#039;&#039; systems, but yields a 20% increase in shield output. The &#039;&#039;&#039;DECS&#039;&#039;&#039; is calibrated to respond and recalibrate the loss of a single emitter or emitter cluster, resulting in a greater overall performance and defensive capability of ship systems. The standard &#039;&#039;&#039;DECS&#039;&#039;&#039; system is installed to provide tactical shielding whenever the starship is experiencing &#039;&#039;&#039;DEA&#039;&#039;&#039; failure, or power requirements do not allow the use of the &#039;&#039;&#039;DEA&#039;&#039;&#039;. Another advantage of the DECS over the standard DEA is its modular design. It is quick and efficient to repair or replace in the field whereas the replacement of the DEA system requires a major overhaul at a Starbase.&lt;br /&gt;
&lt;br /&gt;
==8.0 Hull Integrated Stealth System. ==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;H&#039;&#039;&#039;ull &#039;&#039;&#039;I&#039;&#039;&#039;ntegrated &#039;&#039;&#039;S&#039;&#039;&#039;tealth &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;HISS&#039;&#039;&#039;, is a series of alterations to the ships exterior hull and systems to create a reduced sensor and visual silhouette. The details of the &#039;&#039;&#039;HISS&#039;&#039;&#039; are highly classified, although the general concepts behind its incorporation are not. A network of specialized integrated hull webbing allows the hull to emit energies that effectively allow light waves to pass through it and its contents. In addition to visual bands of radiation, the specially designed ablative hull absorbs sensor energy, while emitting the same energy signature as the starship&#039;s surrounding space. Thus, the vessel becomes virtually undetectable either through detection or complete omission of detection. In addition to this, specialized hull features act as complex Magnetic field disruptors, reducing the EM field of the vessel, and also neutralize radioactive emissions through a complex series of intercoolers and sheathed cowlings. The ship&#039;s Impulse, Thruster and Bussard collection systems are incorporated to nearly negate all detectable signs of their use. When the HISS is active and used in conjunction with strict Emissions protocols, the ship vanishes from visual and sensor detection.&lt;br /&gt;
&lt;br /&gt;
==9.0 Advanced Sensors Systems==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;I&#039;&#039;&#039;mproved &#039;&#039;&#039;S&#039;&#039;&#039;ensor &#039;&#039;&#039;I&#039;&#039;&#039;ntegrated &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;ISIS&#039;&#039;&#039;, is a modified high yield Federation sensor array. The &#039;&#039;&#039;ISIS&#039;&#039;&#039; utilizes the newest development in sensor technology to quantum phase the active and passive ship&#039;s sensors to greatly reduce detectability. These new sensors are more powerful, and almost impossible to detect without performing extensive and time consuming alterations to a starship&#039;s sensor array, which then is useless to detecting other aspects of its surrounding. Some of this technology is loosely based on cloaking principles.&lt;br /&gt;
&lt;br /&gt;
==10.0 Sensor Displacement System==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Se&#039;&#039;&#039;nsor &#039;&#039;&#039;Di&#039;&#039;&#039;splacement &#039;&#039;&#039;S&#039;&#039;&#039;ystem, Or &#039;&#039;&#039;SEDIS&#039;&#039;&#039;, allows the Rosenanté class of starship to offset its actual energy signature, and even produce an additional energy signature. This is designed to improve the starships ability to prevent &amp;quot;true&amp;quot; detection, or to act as a decoy system in the event that the starship is detected. This system is capable of operating within a 60OKm range of the vessel.&lt;br /&gt;
&lt;br /&gt;
==11.0 Displaced Communications System==&lt;br /&gt;
The &#039;&#039;&#039;Di&#039;&#039;&#039;splaced &#039;&#039;&#039;Comm&#039;&#039;&#039;unications &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;DICOMMS&#039;&#039;&#039;, is based on the same technology as the &#039;&#039;&#039;ISIS&#039;&#039;&#039;. This energy is used to send nearly undetectable communications. The Rosenanté class starship is equipped with standard Federation communications systems as well.&lt;br /&gt;
&lt;br /&gt;
==12.0 Interior Systems Modifications==&lt;br /&gt;
There have been a variety of interior alterations to the interior, habitable areas of the Rosenanté class starship. The most apparent alterations are in the functionality of the corridor and turbolift systems. The oversized personnel quarters offer the most luxurious and spacious accommodations aboard any Starfleet posting, while unique interaction software insures crewmembers peace of mind.&lt;br /&gt;
&lt;br /&gt;
Many Starfleet admirals believe that the Tactical and Scientific Equipment carried by a Starship to be the most important asset to any Starfleet facility or starship. The designers of the Rosenanté class of Starship also felt that crew morale would also serve a very integral role in the operation of the starship. To these ends the interactive systems and habitations were designed to provide a reassuring and relaxing environment for the ships crew.&lt;br /&gt;
&lt;br /&gt;
==12.1 Safety Systems==&lt;br /&gt;
The most paramount function of any Starship is the maintenance of its crew in adverse conditions. Integral to this school of thought is the ability to protect the crew under hostile threats. To these ends, the designers of the Rosenanté class starship developed a series of counterinsurgency systems to minimize crew contact with alien forces boarding the vessel.&lt;br /&gt;
&lt;br /&gt;
==12.1.1 Isolation Field Systems==&lt;br /&gt;
The &#039;&#039;&#039;I&#039;&#039;&#039;solation &#039;&#039;&#039;F&#039;&#039;&#039;ield &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;IFS&#039;&#039;&#039;, was designed with the intent to isolate hostile alien forces that boarded the vessel for the crew. This function is considered vitally important when consideration is given to the fact that the Rosenanté class starship possesses a very highly trained crew. The &#039;&#039;&#039;IFS&#039;&#039;&#039; fundamentally isolates the threat through the use of perpetual containment fields, reinforced by miniature shield defenses for the IFS emitter assembly. The &#039;&#039;&#039;IFS&#039;&#039;&#039; is always active, limiting the mobility of non-authorized personnel, securing sensitive sectors of the ship, and effectively hindering the process of any hostile aliens that may manage to board the vessel. The ship&#039;s computer monitors the movements of every official member of the ship&#039;s crew at all times. In this manner, the computer is able to activate or deactivate the &#039;&#039;&#039;IFS&#039;&#039;&#039; screens on an individual basis as needed. This allows authorized crewmembers access to shipboard systems and compartments as needed. The &#039;&#039;&#039;IFS&#039;&#039;&#039; consists of a series of Level 8 containment fields spaced an even 12.5-meters along the corridors of the vessel. In addition to these, an &#039;&#039;&#039;IFS&#039;&#039;&#039; field also isolates each access portal and hatch. In the event that a commbadge should be captured, or fail, that badge is automatically removed from all access rosters, until security can investigate the occurrence.&lt;br /&gt;
&lt;br /&gt;
As a benefit of the perpetually active IFIS fields, studies indicate that shipboard damage caused by fire and/or decompression was drastically reduced. The fields prevented large area decompression, and also limited the range of fire dispersion radically.&lt;br /&gt;
&lt;br /&gt;
Although in larger compartments the &#039;&#039;&#039;IFS&#039;&#039;&#039; system is not perpetual; all compartments are equipped with the capacity to further &amp;quot;compartmentalize&amp;quot; these large open areas. The computer is capable of assessing threats to the crew and equipment of the vessel, and can respond using the &#039;&#039;&#039;IFS&#039;&#039;&#039; system, nearly instantly. The &#039;&#039;&#039;IFS&#039;&#039;&#039; system was designed to operate independently of the ships main power supply when necessary. Each &#039;&#039;&#039;IFS&#039;&#039;&#039; emitter and processor assembly is equipped with an independent high-yield Sodium Kelleride power system. This power cell is further treated with a Potassium Unified catalyst. This allows the production of oxygen as a by-product whenever the secondary power system is operated. This allows a crewmember to be compartmentalized in an otherwise decompressed area to survive asphyxiation and loss of pressure. This secondary power system will allow the full yield operation of the &#039;&#039;&#039;IFS&#039;&#039;&#039; emitter in question for a period of 4 standard hours. Setting the emitter to a lower containment setting can extend this time.&lt;br /&gt;
&lt;br /&gt;
==12.1.2 Fire Suppression Systems==&lt;br /&gt;
&lt;br /&gt;
Although the &#039;&#039;&#039;IFS&#039;&#039;&#039; system hinders the progress of a shipboard fire, it will not necessarily extinguish it. To facilitate this a hybrid field emitter, environmental suppression system was developed. This system isolates the flame from its fuel source using advanced forcefield emissions systems, while simultaneously adjusting the environment around the fire to assist in its suppression. A functional &#039;&#039;&#039;IFS&#039;&#039;&#039; contained area further supports the adjustments, as a smaller area of the ship need be adjusted at any one time. There are certain types of plasma fires that could be unaffected by environmental conditions and or can not be contained in this manner. It is in those situations that the fire suppression systems remove the fire and all affected material through use of the ships sight-to-sight transporters. If this cannot be performed due to a greater risk being imposed on the crew, more conventional methods of fire suppression must be performed.&lt;br /&gt;
&lt;br /&gt;
==12.1.3 Internal Ballistics Dampening Fields==&lt;br /&gt;
In key areas where materials stored aboard ship have the potential to be propelled through sections of the ship, a series of &#039;&#039;&#039;I&#039;&#039;&#039;nternal &#039;&#039;&#039;Ba&#039;&#039;&#039;llistics &#039;&#039;&#039;D&#039;&#039;&#039;ampening Fields, or &#039;&#039;&#039;I-BAD&#039;&#039;&#039; Fields, have been implemented. These fields are found primarily in the armory, cargo bays, Shuttle Bays, storage bays, and personnel quarters. The &#039;&#039;&#039;I-BAD&#039;&#039;&#039; system uses advanced internal sensing equipment specialized to calculate mass and velocity of non-anchored materials. In the event that these materials should be propelled at a speed that the computer should indicate hazardous to crew, then a series of inertial Dampening Fields are erected to reduce the velocity of the offending object. The IDF relays cannot stop a propelled item, although it can shorten its travel distance and relative speed considerably. The sensing systems ignore the movements of personnel. The &#039;&#039;&#039;I-BAD&#039;&#039;&#039; emitters in no way affect the reduction of stresses upon the vessel caused by acceleration, deceleration, or maneuvering.&lt;br /&gt;
&lt;br /&gt;
==12.1.4 Advanced Ergonomics==&lt;br /&gt;
&lt;br /&gt;
[[Image: Rosenante-Alt-4up.jpg|right|200px]]&lt;br /&gt;
&lt;br /&gt;
Throughout the vessel, specialized memory seating systems have been implemented. These systems monitor the stresses upon the body of the crewmember presently utilizing them and adjust the contact points with the crewmember to minimize physical stresses. All station seating and this material affects standard seating in personnel quarters. The design is such that is can self adjust to allow for non-humanoid crewmembers. The standard bedding and medical bio beds are also adjusted in this manner. This has proven to reduce fatigue and discomfort resulting from prolonged duty shifts. The conceptualization of advanced ergonomic design is further implemented in the layouts and design of the personnel quarters on the ship. Each individual’s quarters are ergonomically designed to his or her unique specifications. The height and shape of interactive systems, the design of the shelving and storage facilities, and the layout of the waste management system are all adjusted to the unique requirements of the compartment owner. Even habitation shape and colour are carefully implemented to create an environment in harmony with its occupant.&lt;br /&gt;
&lt;br /&gt;
==12.1.5 Tactical Sight-to-Sight Transport==&lt;br /&gt;
The ship&#039;s computer possesses the ability to assess tactical breaches in to the vessel&#039;s security. When appropriate, the computer may implement tactical redistribution of security personnel to facilitate the disarmament of tactical threats. The computer determines the size of any aggressive and/or threatening force on the ship, and then determines logical methods of containing and overcoming this threat. The computer is capable of briefing shipboard security personnel on the state of a threat, operating IFIS units, and evacuating non-essential personnel from potential or actual combat areas. The computer can deploy security personnel using sight-to-sight transporters and tactical deployment subroutines. In addition to automatic response to internal tactical threats, the ship&#039;s computer can suggest tactical deployment options for security personnel, utilizing data stored in its memory. This tactical deployment data is only suggested when asked for, and is prepared for planetoid deployment, boarding actions, counter-boarding actions, and sight security. When a medical situation presents itself the same sight-to-sight transporter system can be utilized to transport critical patients to the sickbay.&lt;br /&gt;
&lt;br /&gt;
==12.1.6 Emergency Medical Hologram==&lt;br /&gt;
The Emergency Medical Hologram, as standard to all Federation starships, is also present on the Rosenanté class starship. A series of modifications allows the EMH system to be activated in any habitable portion of the vessel. This function is performed by a series of specialized emitters seeded throughout the ship. Each emitter is equipped with an array of medical scanners and programmed with trauma and first aid protocols. Each emitter assembly is capable of independent operation in the event that power systems become unavailable. The Sodium Kelleride power source can maintain EMH use for 1 hour before expending its charge. When operating normally, the EMH can access the ship&#039;s medical database. When operating independently, only the trauma and first aid subroutines may be accessed. While operating on ship&#039;s systems no more than three EMH programs may be running at any one time. Independent operation is possible among any number of EMH emitters.&lt;br /&gt;
&lt;br /&gt;
==12.1.7 Emergency Replication System==&lt;br /&gt;
The &#039;&#039;&#039;E&#039;&#039;&#039;mergency &#039;&#039;&#039;R&#039;&#039;&#039;eplication &#039;&#039;&#039;S&#039;&#039;&#039;ystem, or &#039;&#039;&#039;ERS&#039;&#039;&#039;, is a series of secondary replicators that operate completely independent of the ships systems. The &#039;&#039;&#039;ERS&#039;&#039;&#039; units are located aft and fore of the starship, two per deck. They are always inert until activated. The &#039;&#039;&#039;ERS&#039;&#039;&#039; system is &amp;quot;hidden&amp;quot; behind corridor paneling, and consists of a single equipment replicator, a single food replicator, an atmospheric condenser, a single medical tricorder, a standard tricorder, and a pair of Class I Phasers. A high-yield Sodium Kelleride Battery that allows light use of the replicators, for a period of 3 days, powers the &#039;&#039;&#039;ERS&#039;&#039;&#039; units. The Tricorders and Phasers are pre-powered, and can be recharged once, using the supplied connections. Accessing the ERS panel will alert security. The Class I phasers require a personal authorization code to be activated. The computer monitors the &#039;&#039;&#039;ERS&#039;&#039;&#039; system very closely, immediately notifying engineering if a problem is detected.&lt;br /&gt;
Although the &#039;&#039;&#039;ERS&#039;&#039;&#039; is a fully functional Replication system, it is programmed to create materials that require very little energy to reproduce. Thus, the food replicators produce only a single nutrient rich disk for consumption. The Tool replicator is limited to equipment that possesses simple physical structures, such as hand tools and only simple electronics materials. Neither replicator system can reproduce power sources, or advanced electronics.&lt;br /&gt;
&lt;br /&gt;
==12.1.8 Emergency Transporters==&lt;br /&gt;
The Rosenanté class starship is equipped with 2 emergency transporters. These transporters are located centrally along the berth and length of the vessel on decks 5 and 15. The emergency transporters are integrated into the primary corridor on the aforementioned decks. All transporter hardware is stowed in the surrounding corridor structures. 20 high-yield Sodium Kelleride Batteries independently power the control operation panel and the emergency transport systems. Each Emergency transporter is also equipped with its own short-range sensor array, for destination determination. The control panel is &amp;quot;hidden&amp;quot; behind the corridor paneling, and floor paneling hides the transporter pad. In order to operate the transporter this floor paneling must be removed. The emergency transporters are each capable of transporting 60 personnel.&lt;br /&gt;
After that there is no power remaining to continue transporter functions. Preparing the Emergency transporters for use alerts security.&lt;br /&gt;
&lt;br /&gt;
==12.2 Medical Bay==&lt;br /&gt;
Due to the number of personnel stationed aboard the Rosenanté class starship, the standard&lt;br /&gt;
Medical Bay arrangement was not utilized. Instead a specialized medical bay was designed to maximize space, while still attending to the variable needs of the ship&#039;s crew. To this end, the sickbay possesses a complete quarantine ward, a single surgical ward, and the central sickbay. A office allows for the CMO to perform administrative tasks without interruption.&lt;br /&gt;
In the surgical area, all the equipment necessary to perform any level of surgery is present. Specialized negative pressure systems allow operations to continue upon contaminated personnel without worry of integrity loss.&lt;br /&gt;
The central medical area is equipped with the newest and most efficient systems that general practice has to offer. A multitude of sensors and medical dedicated processors facilitate medical data gathering, while advanced holographic modeling systems allow hands-off data model construction. Forty Biobeds are located in the Sickbay, which studies indicate was the most efficient number of patients to treat at one time. &lt;br /&gt;
&lt;br /&gt;
In addition to the standard biobeds and Infirmary treatment bay, There are also two dedicated Medical Laboratories, One General Practice Clinical Ward and Three configurable Bays, which can be changed to meet the specific requirements of the medical needs of the vessel.&lt;br /&gt;
&lt;br /&gt;
The Quarantine area is equipped with a series of Biocide units capable of detecting, isolating and destroying over three hundred billion contagions. Negative pressure atmospheric systems, ionic decontamination systems, and bio-phased containment fields guarantee the isolation of harmful contagions. All containment systems in the sickbay are maintained by secondary and tertiary power systems. A medical dedicated replication system allows the creation of any replicable pharmaceutical known to Starfleet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;small&amp;gt;All images compliments of Roger Wackowski&amp;lt;br&amp;gt;Spiral Drive concepts by Anthony Keen&amp;lt;br&amp;gt;All other technical aspects, created, written and designed by Daniel Greene&amp;lt;/small&amp;gt;&lt;br /&gt;
[[Category: Engineering]][[Category: Database]][[Category: Active Ships]]&lt;/div&gt;</summary>
		<author><name>Nicesociety</name></author>
	</entry>
</feed>