*Message Begins* *Encryption: Order Cypher X43G Maximum* *Re: In a bit of a pickle...*
Look, before anything else, I have to emphasise that It's not my fault that I've ended up in New York, and it's definitely not my fault that there's, um, a few scratches on the paintwork...and the cruise drive...and the long range sensors...I mean, how was I to know that the Minor-Alaska jumphole was going to collapse while I was in transit? Nothing the self-repair routines won't be able to handle, but it might take a while to get us mobile. Shields are still functional though, so that's all right!
Anyway, I just thought I'd let you know where I am and that a helping hand getting back home would be great. I'm not sure how I'm going to get out of here yet, though there seem to be plenty of decent sorts here who are keen to lend a hand! Honestly with the way people talk at home, you'd think everyone and their dog would be trying to gun me own! Still, Guardian did mention that there might be safer places to wait for rescue, but I can't resist...Manhattan is a fascinating place, even from space. So much culture and business packed into one place. Honestly, don't worry about getting in a tizz over this...I promise I won't be bored waiting!
Mia xxx
P.S. Give Folorn|-Nick.Stenn a drink on me!
22:22, 27/08/818
To the appropriate unit,
This is the backup Artificial Intelligence unit for the OCV-Sekhet-Aaru, Guardian. This unit has insisted on providing a report on the situation, as the master controller has left out key details of the current situation.
The master controller's account of jump hole collapse an subsequent damage is brief but accurate. Diagnostics indicate severe damage to several critical systems, and hull integrity has been severely compromised. Once the self-repair routines are able to be brought online, this unit estimates that the ship will have cruise capabilities in a matter of days, though that will be at the expense of restoring the vessel's defensive capabilities.
Additionally, it is this unit's duty to inform the necessary authorities that this unit attempted to relocate the ship to a safer place. Immediately after jump hole collapse, this unit was left in control of the vessel as the master controller had been incapacitated. The vessel was discovered by a Liberty Naval ship, identifying as the 6th|LNS-Hampshire and subsequently this unit was able to agree to have the Sekhet-Aaru towed to facility Ames Research Station in the Kepler system some 12.246 hours before this message was sent for repairs and possible retrieval from a safer location.
As there was no engineering team onboard the station with the necessary clearance, this unit was not able to authorize third party repairs. However, 10.677 hours before this message was sent, the master controller resumed functionality and control of the ship passed from this unit over to them. This unit briefed the master controller on the situation and it was their decision to set course, in our current state, back into Liberty Space. Logged reasoning: "Fun."
As stated, this unit has no control over any systems while the master controller is operative. This unit assesses the risk to the ship that the master controller, not factoring in outside forces, is extreme, given the situation. This vessel is a testbed for several classified systems that must not fall into hostile control and the risk of our second, most probably final, detection only increases as long as the vessel remains where it is. This unit will do its best to provide guidance for the vessel's survival, though at this time, any and all decisions lie with the master controller. Be aware that this unit can only attach to messages sent by the master controller, and at this stage all long range communications are being delivered via third parties of questionable factional allegiances.
[Priority: Epsilon-Alpha - High - Channel 012
[Encryption: Delta-Alpha - High - Code: ccvNE7dm1
Hey there.
This is Vex, CO of the Ahkmim. I've listened to the transmission you've put out, and I'm a little confused on a few points. Don't get me wrong, I'm gonna do my best to help you get home if you'll let me, but I wanna ask a few things if you can send them over an unsecured channel.
First, exactly what is the Sekhet-Aaru? Might help to know what I'm gonna try and help get back home.
Second, how badly are you hurt? The ship, people on board, systems..?
Finally, and most importantly, what kind of opposition have you encountered so far there?
I'm more than willing to help you get back, but I'd prefer to avoid angering Liberty any more than they already are.
I hope I hear from you before the Overwatch does. Until then.
Dont start blaming yourself now, accidents happen to everyone. However, you shouldnt park your ship near Manhattan. The local fauna is known to be overly hostile towards our operatives, and all you are doing now is endangering your crew. I will see if I can pull you out back home soon.
I'd like to know a few things beforehand.
How badly is your ship damaged?
In what shape is your crew and do you need immediate medical assistance?
What kind of vessel is it that we are extracting?
Answer me those and all should be in order soon. If you can, try and get that Forlorn to be present at the same time, and Ill make sure he gets rewarded appropriately. From my past interactions with them they are a great bunch of people.
This Galaxy is vast; its wonders and beauty are almost unfathomable. But the galaxy also hides dark secrets, some of which have lain dormant since the beginning of time itself. There is a danger in secrets, both in seeking and in knowing. Some things are meant to be hidden from view. Some mysteries defy understanding, and sometimes even the things we think we know are untrue. Some secrets should remain untouched.
*Message Begins* *Encryption: Order Cypher X43G Maximum* *Re: In a bit of a pickle...*
Hey Vex, hey Sara, I don't recognise the names, have we met before? I Thought I knew pretty much everyone back home, so I'm really excited to see a new faces!
This ship is...kinda hard to explain, I'll let Guardian give you the technical description and current status, but we're almost the size of an Osiris. Fun fact, I think we nearly match the displacement of the Isis before she...she...well never mind. Sorry, it's still a bit raw, even four months after it happened.
The ship's looking a little less bruised now; we got the long range sensors working and we test fired the cruise drive an hour ago, though it died after a couple of seconds. Long range comms are working too which is a relief! Don't worry about crew, it's only me and Guardian. Everyone else was banked before we entered the jump hole.
I can't say we've faced much in the way of opposition so far. The Rio Grande fired some shots from range but didn't chase us, and we've only really been in contact with Nick Stenn as mentioned and a Navy person, I think his name was Alan Polstari. He also seemed eager to help with getting my first message out among other things. Don't worry though, I've seen what the Navy can do when they're not in an agreeable mood. We're safe, definitely more hidden than if we were moored back in Kepler...Guardian's not the only one with common sense on this ship.
I've not heard of the Overwatch...some new branch? I hope they've got a better sense of understanding than the High Command. But anyway, it's good to know that someone nice like you is on the case. I'll be in touch if anything happens.
09:44, 28/08/818
Entry from the "Standing Fleet: 817A.S.": The OCV-Sekhet-Aaru is the sole ship of her class, laid down in 807 at Evora Shipyard, launched 809 and fitted out on Planet Toledo and accepted into service in 815 as a technology testbed, pioneering developments in Order reactor and capital drive technology now standard across the Order fleet. Also included aboard were several non-standard technologies, centring around *REDACTED* and the necessary Artificial Intelligence capabilities to govern said systems.
(Guardian notes: The OCV-Sekhet-Aaru has largely been confined to Order space to preserve the safety of the technology aboard. The vessel first experienced combat conditions during the Battle of Toledo where she assisted in the evacuation of Order personnel from the planet, suffering heavy damage in the process. After subsequent repairs, the OCV-Sekhet-Aaru was utilized to produce materials for fleet reconstruction, as well as a heavily armed blockade runner to resupply the remaining Order forces in the fringes of controlled space. The vessel's current mission is to perform the in-situ resupply and rearmament of the battleship Atum in the Alaska system.)
Damage report: Hull integrity to critical parts of the vessel restored to an average of 65.5%, giving the OCV-Sekhet-Aaru a 54.4% success chance of surviving the stresses associated with an average jump hole transit. Cruise engines are still offline. However, diagnostics have confirmed what steps are needed to restore them to working order. AI memory banks damaged but information backed up. Main armament offline. Pulse cannons destroyed; replacement without resupply estimated at 1 standard month. Hangar destroyed. Bridge destroyed. *REDACTED*. Light damage to several other systems that retain operational capabilities.
[Priority: Epsilon-Alpha - High - Channel 006
[Encryption: Delta-Alpha - High - Code: xlmt99v7a
Hey there.
Barring Ms. Shepard's rude interruption, the details match out. I remember Toledo, as most people in our organization do. The gunfire was nearly deafening, but thanks to you and the help of the rest of our people, not only was I able to make it out, but some of the civilian populace too.
Personally, I think you're in a fairly good position. While I can't come and personally get you with the Ahkmim's up-to-date firepower, I can try and send something smaller that would help get past Liberty's lines. The main concern here is hull integrity. With the Sekhet-Aaru's hull that badly damaged, repairs will cerntainly need to be done on site before we can get you out.
That being said, I'll try and get some supplies towards you along with heavy escort to see you back home. It may take a while, but from the sound of things you don't mind waiting. I'll see you then, Mia.
*Message Begins* *Encryption: Order Cypher X43G Maximum* *Re: What the hell!*
So I've just been told that the year is not 818A.S., that it is in fact six years since my ship entered the jump hole in Omicron Minor, that nobody has heard of the friends I know, and I don't recognise the name of even our own Grand Admiral. I didn't believe them at first, those who told me, but then I checked it all out, monitored transmissions in the New York system and the CNS. I even did the calculations on the current planetary positions...they were telling the truth.
I...I need to get out of here ASAP and find some answers. I think the Navy is intensifying the search for me...they haven't detected me so far but they were doing their best, and the particular captain leading it did not sound as understanding as Guardian tells me the one commanding the LNS-Hampshire was. There's still a lot of repairs to be done, but the ship's a long way from being defensible if we're discovered.
⧫ Akabat
⧫ Omicron Mu
⧫ 28/08/824
⧫ FROM: The Order Overwatch
⧫ TO: O.C.V. Sekhet Aaru
Assistance
The Order Overwatch will assist with recovery process and sortie reconaissance craft to make sure your transit will be as smooth as it is humanly possible in these hard times. I happen to know someone who had experienced first hand delay in hyperspace transit, arriving later than expected to do. Therefore your story is not without a merit. We can begin preliminary maintenance in northern Kusari before resuming retreat to Omicrons. I would like to hear this story from you in person once back "home" however there are some inconsistencies that I noted, being an Order veteran from Toledo as well.
Your internal clock, dating to 818 A.S. is locked behind the actual time constrains of battle of Omicron Minor that happened in closing days of December. Are we talking about technical failure relating to damage to your systems? Not only that, I have been in charge of defense and evacuation of Toledo as it happened - it is nigh on impossible that you could had not heard of me. I regret my inability to get everyone to safety as I gave everything, including almost my own life at hands of Core in ruins of Toledo as Nomads in skies above bombarded it into oblivion. Secondly, The Order Overwatch is a concept that I brought into administration with my rise into power, with intention to put an end to instability of former High Command. It has served its purpose well.
Your shipclass does not figure on any of our fleet database. You already excluded Osiris-class. Resheph, Bustard, Geb, Hathor, perhaps some odd Zoner or perhaps Liberty design rolled into service with The Order? Technical data allows us to respond more efficiently with repairs if you can help with that. Liberty is far from being safe zone given the locals have contrasting opinions on us. Ames arguably was the right choice, as I have some friends and contacts in the black of Kepler and Galileo that could render assistance if asked...
As for Captain Upsilon... I care more for survival of the non-combatants, soldiers and officers in service to The Order than your petty disagreements with my policies. I do not care which officer makes it first to Sekhet Aaru so long primary tenents of The Order are fulfilled and our people are brought home in one piece. You will find full co-operation from representatives of the Black Fleet, expecting the mutual. Should it not be the case, I will reprimand the one at fault. Failure is not an option.
Grand Admiral Michal Golanski
Black Fleet, 1st Battlegroup "Wargods"
*Message Begins* *Encryption: Order Cypher X43G Maximum* *Re: Providing Explanations*
This unit regrets to inform you that the master controller is unavailable at this time. This unit was handed command of the vessel at 0645 and has begun actions to return the vessel to the Kepler system, currently under sub-cruise propulsion. Having had a chance to refill our stocks in the Badlands, this unit can report an accelerated repair timetable, and the cruise drive should be restored within a matter of hours rather than days. The vessel has thus far remained undetected, and this unit has opted for complete radio silence except via the neural network.
The OCV-Sekhet-Aaru is based loosely on the schematics of a reinforced L-584-B(iii) Oasis-class ship, though the vessel's internal configuration is of an entirely original design. This unit surmises that the technical data will not be present in your archives and will attempt to elucidate why this will be so.
This unit has begun its own analysis of the situation that has presented itself and has drawn some rather unconventional, though not unsurprising, conclusions. Aside from numerous credible sources indicating that our internal clock is wrong, logs indicate that there has been no disruption to its operation. For all intents an purposes the clock is correct. Furthermore, the master controller is not incorrect in the dating or account of the Battle of Toledo; the account does not conflict with the official entries in the database carried onboard this vessel.
These obvious contradictions prompted this unit to begin an analysis and an attempt to establish a cause for the discrepancies and attempted to interface with the Order's primary information databases. To this unit's regret, none of its current access keys were accepted. Furthermore, less than 2% of the known Order communication channels appeared to be valid, and several encryption tests indicated that our cyphers and yours are mostly at a mis-match; it is through sheer luck that the master controller selected one that was mutually acceptable in their initial broadcast.
Furthermore, there are several major discrepancies between this unit's memory of certain public facts and what this unit has gleaned from investigation. As an example, there are major differences in the timeline with makeup of vessels on the Liberty Navy Register, famous Libertonian public figures and cultural icons, not to mention a completely different history of the presidency over the past twenty years. This unit expects that, should our data regarding the Order be compared with yours, that a similar situation would arise.
Conclusion: This New York is not 'our' New York, this Sirius is not 'our' Sirius, and this Order is not 'our' Order. The implications, however fascinating, can wait until we are safe back in the Omicrons. This unit assures you that the vessel's allegiances are not in question; 'one Order is as good as another' as a human might say, an this unit sincerely doubts that the Liberty Navy will be drawing any distinctions over any of this either. There will be much to share once this vessel is in a place where it is safe to do so.
⧫ Akabat
⧫ Omicron Mu
⧫ 31/08/824
⧫ FROM: The Order Overwatch
⧫ TO: O.C.V. Sekhet Aaru
Assistance
Debriefing of the Captain is under way and repairs of Sekhet Aaru are underway in drydocks of Carthage after succesful search and rescue operation on behalf of The Order Black Fleet. Damage assesment team reported the following:
⧫ Hull structural integrity at aproximate 70% and is expected back at nominal 100%. ⧫ Cargohold depressurized. Unable to carry load until cleared of debris. ⧫ Main reactor estimated at 50% total capacity, powering only critical systems. Induced into 10% standby status and relying on Carthage's own grid. ⧫ Secondary powersources scheduled assesment once shut down. ⧫ Powergrid capacipators at 25% efficiency. 'Sekhet Aaru' required prolonged charging periods in between jumps. ⧫ Jumpdrive disruption chamber operating beyond safe limits. Electromagnetic conductors cracked. Estimated functional yet prone to critical system failure if put under any further stress. Irrepairable and scheduled for replacement. Removed device into custody of Wedjat Section 1 for further study. ⧫ All weapon battery in manual shut down mode. No subsystem damage incured. Kept offline. ⧫ Cruise engine suffering from critical overheating. Scheduled heatsink assembly reconstruction.
Grand Admiral Michal Golanski
Black Fleet, 1st Battlegroup "Wargods"
*Message Begins* *Encryption: Order Short Wave 111X HIGH* *Re: Guardian; Vessel Status Report*
As the Master Controller in otherwise engaged with their debriefing, this unit has been working to bring the Sekhet-Aaru back to within operational parameters in conjunction with effective assistance from the shipyard at Fort Carthage. With the auto-repair systems fully restocked and in full operation, this unit expects the vessel to be spaceworthy on a shortened timetable. This unit has the following updates to report:
⧫ Structural integrity at 85% and holding. Repair resources currently diverted elsewhere.
⧫ Cargo hold area has been cleared of debris. Repairs not initiated; repairs are to be conducted by this vessel unassisted as a technology demonstrator, with the relevant permissions.
⧫ Reactor currently idling at less than 1% of total capacity. This vessel is equipped with a prototype C96 Hypermatter Reactor Unit, capable of a theoretical output of 1,400,000,000 standard units. Advise not to exceed 40,000 standard units, 50% of the reactor output of a similarly-classed vessel. Safe operation over 80,000 units only possible with governance from the master controller.
⧫ Twin secondary reactors (D9-Quasar, standard powerplant on Osiris-class vessels) powered down, emergency batteries charging. The vessel is currently drawing power from Fort Carthage via umbilical link.
⧫ Powergrid capacitors at 40%. Repair efforts are being directed there.
⧫ Weapons systems remain offline. Replacement of seven burnt-out shield capacitors taking place.
⧫ Cruise engines removed for an updated replacement. Requisition order pending.
In addition, this unit is attempting to rectify the current asymmetry with regard to both data and security in the following actions:
⧫ Standardising and unifying this vessel's communication and security codes with current Order standards. This unit has submitted a request for the necessary access codes for all relevant Order databases. This unit reports that certain top-access materials are unable to be accessed without codes known only to the previous 'Command.' Encrypted files copied to Order technical personnel to attempt decryption, and several sub-AI's aboard this vessel have been likewise tasked.
⧫ Standardising onboard software with Order standard. Though various differences have been detected, the majority this vessel's systems are comparabile and compatible with Order technology circa 816-818A.S. Upgrades are being applied. These upgrades are not applicable to the Master Core.
⧫ Ship schematics and prototype project information have been uploaded to the Fort Carthage database and will be available to appropriately cleared personnel pending inspection. Note: There are no available entries on file for the Master Core. Access to the Master Core restricted at the Master Controller's discretion.
This unit must clarify the function of item identified as 'Jumpdrive distruption chamber.' System is listed in inventory as a 'Gravitational Mass Generator' and is one of five units installed onboard this vessel and constitutes part of the larger system group marked 'Project 73.' This vessel will provide all technical schematics and will manufacture a replacement when the opportunity presents itself. Caution: The Gravitational Mass Generator incorporates material of a density comparable to that which the neutron star in system 'Omega-41' is composed of. Specialist equipment required for handling.
Finally, the Master Controller instructed me to submit this to all Order personnel involved who kept contact with this vessel and assisted in its rescue: