Discovery Gaming Community

Full Version: The Sekhet-Aaru and its A.I.
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
[Excerpts taken from the Sekhet-Aaru's offline database from a collation of entries entitled 'Ships of the Order: 801-818AS', authored by several archivist scribes, describing the construction, design and service history of the vessel. Excerpts are decrypted from the Admiralty-level edition of the collation, including project details unavailable in the more widely accessible 'Fleet' edition.]



Prefacing Comments: Of all the ships of the Order that I have catalogued over the years since the Nomad Crisis, and even by the lofty precedents of science and technology set to ensure our organisation's continued survival, few have been as ambitious, and indeed controversial, as the Sekhet-Aaru. Supporters of the project cite its continued contributions and the kindness and steadfastness of its captain in the wake of Toledo, not to mention the milestones associated with the ship as being indicative of a successful and valuable endeavour. To others it is a financial white elephant whose costs, both direct and indirect, cannot possibly justify its existence, and in the hands of a artificial intelligence with a history of insubordination is a millstone tied around the neck of the already stretched military. Nevertheless, the Sekhet-Aaru has been a fascinating ship to catalogue and is deserving of its place in the records of our organisation. - Joshua Weinberg, Order Head Archivist, Evora Branch



Section One: Construction

The Sekhet-Aaru can find its origins in an Admiralty requirement of 807AS submitted to the design teams at Evora Shipyard for an unmanned vessel capable of securely housing a number of upcoming prototype systems for field testing. The design would need to be sufficiently sturdy to withstand the stresses of the systems it was built to test, large enough to carry a reactor powerful enough to fuel the experiments and possessing of a suitable on-board artificial intelligence to ensure its safe governance.

The decision was made early on to build the ship on the bones of an existing design. Initially an Osiris-class hull was considered for its attributes of size and durability, but with the demand for the battleships coming from both the Order and the Corsairs, none could be spared and an alternative had to be found. Eventually the team opted for a design based on a civilian hull. The Oasis-class of passenger liners were spacious and had a ruggedness of design that lent itself to long term operations in the wilder reaches of space, a necessity for the testing of systems away from potentially vulnerable population centres. The choice of hull would come with the advantages of a thriving market for second hand parts, speeding up construction while decreasing costs and ensuring that the ship could, as far as the basic vessel was concerned, be economically maintained. The shipyard architects thus found the foundation on which they could build, and within a matter of months the blueprints for the highly modified Oasis was submitted for approval to the admiralty.

Given the green light in May 807AS, her keel was laid down at Evora in March of that year. Work proceeded to a relaxed but predetermined schedule as much work was still to be done on the planned first batch of mounted prototypes. By 809AS most of the critical non-experimental systems were in place, including the reactor (experimental but a critical part of the ship,) flight systems, basic shielding and a temporary control interface, though the vessel remained largely an empty shell. The first challenge that presented itself was the issue of the ship's fitting out. To preserve secrecy around the project, a purpose-built hangar had been carved into the face of a vast crevice, deep in the uncharted wastes of Planet Toledo where the ship was to undergo it's completion. Secure as this location may have been, transporting the incomplete ship to its new home was not a straightforward affair, involving the entire complement of the Order's heavy lifters to assist the ship from its berth and taking it through the jump hole and hostile terrain on the other side to Toledo. The ship then had to endure a closely calculated atmospheric re-entry before being laid to rest in its hangar. Though it cannot be verified, this is believed to have been one of the most challenging transfers of an unfinished ship in the history of Sirius to date.

Upon arrival at Toledo, the ship was handed over by Evora's engineers to the dedicated project research team, a small group of gifted individuals who, as well as being competent mechanics responsible for the vessel's fitting out, had largely been the heads of the departments in charge of the development of the prototype technologies that were to be mounted. The team had paid close attention to the design and construction of the ship in the run-up to its arrival and many of the systems were ready or close to being ready to incorporate into the ship. Details of the mounted projects will be expanded upon in another dedicated section of this entry. Though there were issues that had to be resolved and designs that had to be altered accordingly, the prototype hardware was completed and mounted by February 812AS, ready for the completion of the artificial intelligence that would control the tests.

The person whose job it was to achieve this was Dr Lucia Farrugia, a Corsair scientist brought in specifically for the task, she was nevertheless reported to be the most eccentric of an eccentric group and difficult to work with. Colleagues expressed their concern at the obsessiveness with which Dr Farrugia conducted her work and the paranoia with which she went about it. Work reports indicate that throughout work undertaken on the A.I. core, the doctor was the only individual to access the relevant areas, and work hours logged indicated several twenty-four hour shifts pulled regularly, often consecutively. It is also noted that the doctor failed to submit, nor appeared to work off any physical blueprint, and the requisitions list, though still classified, was known to contain a bizarre mix of both the cutting edge and the ancient as well as a substantial amount of biological material. Nobody knows the exact structure and content as the core remains sealed by its owner to this day, and Dr Farrugia sadly died during the evacuation of Toledo. Nevertheless, the records indicate that the doctor's design is unlike anything else in the service of the Order, and though questions were beginning to be asked of Dr Farrugia, the scientist assured both her team and an increasingly alarmed Admiralty that her creation would be more than capable of handling the massive computing challenge that lay ahead of it.

Despite these assurances and the progress already made, the project was approaching a final deadline come it's completion in November 814AS, set after the second of two Admiralty inquiries in early 813 and mid 814AS respectively. Though in terms of time the delay was not unprecedented for the scale of the undertaking, cost overruns to the tune of nearly seven billion credits for an organisation that could ill afford such figures nearly resulted in the termination of the project. Indeed, it was on the day of the deadline that the A.I. was brought online with the ship hurriedly christened the Sekhet-Aaru, after the ancient Egyptian analogue for Heaven, before its unceremonious launch. The Admiralty would finally have the opportunity to evaluate just exactly what they had been given for their money. This concludes the section dedicated to the Sekhet-Aaru's construction.
Section Two: Experimental and Prototype Technologies



The Sekhet-Aaru was known to mount equipment which were categorised into four technically distinct but interlinked projects, numbered 71-74. The purpose of this section is merely to paraphrase the function of the relevant systems. Those with the necessary security clearance can access the full technical data manually from the Evora archives or from the appropriate data points aboard Admiralty flagships. Unauthorised requests made to the AI for technical data will be immediately reported.



71: Prototype Hypermatter Reactor and H-Fuel Converters

The C96 Hypermatter Reactor has one of the largest outputs for a power plant ever mounted on a mobile chassis, and the manufacturing techniques pioneered in its development have been applied to make the current generation of Order reactor technology safer and more durable. Capable of an output of 1.4 billion standard units, the reactor still only provides a comfortable surplus (approximately 80,000 when the Sekhet-Aaru is operating as normal) above that which is required to maintain the functioning of its systems, a testament to the ambition required even at the most basic level for the vessel to function.

H-fuel is the base material that the ship runs off, being converted into hypermatter by the Sekhet-Aaru's purpose-built systems and injected immediately into the reactor before it destabilises. Though extremely fuel efficient in relation to its power output, the C96 still requires an H-fuel supply which is the equivalent to four Oasis-class liners. This is partially mitigated by the vessel's capability in turn to collect refine its own H-Fuel (see 72 and 73), and in a matter-rich environment the ship is able to sustain itself indefinitely. When operating in open space however, the top-ups alone the Sekhet-Aaru requires means that she has the fuel consumption rivalling that of a carrier battle group.

It should also be noted that the C96 has proven itself to be a remarkably safe design inasmuch as it has a safety record comparable to conventional systems. Throughout its service the reactor has performed several stress tests, has been subject to combat damage and has had two instances of uncontrolled shutdowns, none of which resulted in more than moderate collateral damage of surrounding systems.

72: Matter Atomiser and Collection Systems (MACS)

MACS comprise a variety of technologies designed to collect, atomise and store matter from the surrounding environment. Electromagnetic scoops, tractor beams and a network of induction pipes along the hull to pull in material ranging from nebula particles to chunks of wreckage. The collected material is then broken down in systems distantly related to the Sekhet-Aaru's H-fuel converters into its constituent atoms, which are then catalogued by the ship's AI and stored. These resources are then able to be re-constructed into useful materials and items within the bowels of the vessel and the space created by its Rift Engine. Currently there is no limit to the size and scope of these constructs (see 73), though the ship's hangar bay doors provide the current dimensional limits to what can be delivered externally. This limitation does not narrow down by much the range of things that the Sekhet-Aaru is capable of producing everything from medical supplies, to food, to sections of hull, and the AI's innately creative personality ensures that new applications of the system are regularly discovered.

The one major shortcoming of the MACS system is complications surrounding the creation of live organic material. Though the AI has managed to construct various examples of living organisms within the walls of the ship, none have thus far survived outside the Sekhet-Aaru and those few attempts at experimenting with this limitation have proven traumatic for both the researchers involved and the AI.

MACS are the second most power-hungry and processing intensive system aboard the Sekhet-Aaru after the Rift Engine.

73: The Rift Engine

The most impressive and volatile system mounted on the vessel, the Rift Drive borders on science fiction, and is the focus of the majority of the resources about the Sekhet-Aaru. Using a variety of gravimetric systems, MACS and the majority of the AI's processing power and reactor output, the Rift Drive distorts theSekhet-Aaru's interior to create a space that is both larger than the ship itself and whose contained mass bears no relation to the weight of the vessel to the onlooker's eye, nicknamed the 'TARDIS' effect by Bretonian members of the project team.

The precise size of the void within the Sekhet-Aaru is determined by the AI, though its maximal extent has yet to have been ascertained; due to the ongoing self-optimisation of the AI, what can be 'comfortably' attained has been improved year on year, and is currently believed to be approximately 1.5AU³. The contents of the created space have reportedly varied over the years, and the organisation of the material deposited by MACS is alterable at the AI's will, but it is currently believed to be optimised for the industrial production of assets related to the future colonisation by the Order of a suitable world.

Entry to the void has been deemed safe to personnel, and when convenient to do so the AI has taken to running a Bretonian public house within the void for the benefit of Order personnel.

It is currently unknown what would happen in the event of a Rift Engine failure, as the systems in question have a number of effective secondary measures capable of sustaining operation in the event of damage or power loss which have thus far proved sufficient to prevent a void collapse. Nevertheless, outside of essential maintenance work, the ship's AI has been advised to maintain a safe distance from Order population centres.

74: Tanis Research X1B 'Shoal' Advanced Auto-Repair

The Sekhet-Aaru's Shoal nanobots are an attempt, considered unsuccessful, at a next-generation development of the humble repair drone found throughout Sirius. The latter are stored in an inactive state until triggered into what is effectively a single-use repair function, and while the Shoal can be expended in this manner like a conventional nanobot, they exist prior to this in semi-active 'clouds' that fill the spaces of the ship. Unless called upon for emergency expenditure, the Shoal constantly repairs and maintains the Sekhet-Aaru, though at a vastly slowed pace than if they were fully activated. This allows for the ship to recover from the most severe damage over time. As with most micro-machinery, the individuals in the Shoal have a limited lifespan and require replacement over time. However, their rate of decay is slow and easily compensated for by the Sekhet-Aaru's production capabilities.

The failure of this prototype technology rests on two points; 1) The use of the Shoal is impractical tool in combat, where the short-term function and lack of decay of standard, cheaper nanobots is preferred, and 2) The Shoal is dangerous to unprotected biological material; though the AI (and its backup) is able to keep the nanobots away from such material onboard the Sekhet-Aaru, it is a highly impractical system for implementation on vessels with standing crews.
Section Three: Artificial Intelligences



Being a vessel with no crew, the Sekhet-Aaru relies exclusively on several governing AI programs for command, control and maintenance of the ship, arranged in a top-down fashion. This entry will focus on the two most advanced Intelligences onboard the ship: The Master and Assistant Controllers.



1. The Master Controller, 'Mia Farrugia'

The keystone in the running of the ship, the Master Controller was the result of several years of work by Dr Lucia Farrugia. Her selection would prove in hindsight to be the most controversial choice made on the Sekhet-Aaru project; even if the Master Controller was judged to be a success, which many individuals of note within the Order still do not, it is evident that its creation was mired in the self-interest of its creator who misused valuable Order resources for her own designs, building in her own words 'a daughter.'

Nevertheless, what the Doctor constructed fulfilled the letter of what was asked, if not the spirit. The raw processing power required to moderate both the MACS and the Rift Engine at once were far beyond the reach of even the most cutting-edge quantum supercomputers of the day, but the Doctor, a native of Planet Crete, delivered on her promises. Physically-speaking, the Master Controller is a gargantuan construct, taking up the majority of the prow of the ship and divided into two distinct parts. The first section dwarfs the latter, and is the 'ship-facing' side of the Master Controller; vast racks of subsystems and data banks dedicated to the running of the vessel and the cataloguing of everything contained within the Rift environment. The latter, contained in a relatively small but heavily reinforced and sealed chamber, accessible only through passages big enough for nanobots and nicknamed the 'heart', appears to house the 'higher functions' of the Master Controller, as well as the systems that define her more 'personal' characteristics.

Even with limited technical data available, it is evident that the two halves of the Master Controller are almost as different to each other as it is possible to be. One side is relatively uniform in construction, utilising an eclectic but generally up-to-date mix of current generation technologies, massed in a crude but effective manner and whose design is committed to file. The architecture of the 'heart' is conversely not known, with no known existing documentation save for the list of requisitioned 'unusual' materials submitted during construction. Though some of these parts are found throughout the ship, roughly 50% are unaccounted for, and are assumed to be contained within this inaccessible space. The list makes for fascinating reading, referencing parts from across Sirius (minus Gallia) from weapons capacitors to systems from old jump gates and ancient nav computers. The parts also appear to stretch back in time, examples include being from the Schulman expedition to Omicron Gamma in 450AS, and there are certain unverified components that have the word Hispania jotted next to them on the scanned document. Perhaps more disturbing are the several dozen entries vaguely identified as 'tissue samples' of unknown origin or provenance. However, despite the unlikely combination of parts, the Master Controller appears to suffer little in the way of compatibility issues, and the two halves that compose her work relatively harmoniously. More detailed technical can be accessed at the Evora archive.

The Master Controller manifests herself in the persona of 'Mia Farrugia,' and is capable of doing so in several different ways depending on nature of the given interaction, ranging from a simple voice via the Sekhet-Aaru's intercom or external communications array to advanced holographic representations. In all cases, it appears that her chosen form, both in appearance and in voice are constant, and conversations with her have revealed that these are hardwired in an unclear manner. Having met her in person on occasion, I can attest that she is convincingly human, with a sociable, curious if irritatingly absent-minded demeanour. The operation of the ship appears to be intuitive to her, though when her systems are taxed she exhibits visible and audible signs of mental exertion. Bizarrely too, the Master Controller exhibits signs of discomfort and pain when the vessel comes under direct fire or is exposed to particularly extreme environments. The reasons behind the implementation of this 'feature' are currently not known, though it can be assumed that it, as with human beings, it exists as a warning of, and an incentive to avoid, danger and damage.

The frivolities made in the Master Controller's creation would largely have been forgiveable, had her personality not included a quiet but unhealthy disrespect for both authority and protocol, and an immaturity unwelcome in an individual in a position of command. While the AI seems to feel a genuine loyalty toward the Order and its members and has shown a marked improvement in behaviour since the bombardment of Toledo, there are numerous incidents on record that would normally result in severe disciplinary action if she were a captain who could be removed from her post, ranging from a poor punctuality to going AWOL and fraternising with the enemy. How this was dealt with (or not) will be covered in section four of this entry, but briefly summarised a partially successful compromise was made between the warring parties, and especially following the cataclysmic events leading up to the evacuation of Omicron Minor, the Master Controller has, for lack of a better term, 'grown up' in the responsibilities bestowed on her, the occasional impetuous bout notwithstanding.

With Order personnel shortages being what they are, any plans to replace or patch the Master Controller appear to have been shelved in the light of her recent, more cooperative and productive relationship with the Admiralty. Nevertheless, Mia Farrugia remains a divisive topic of discussion, and it is a distinct possibility that if any further infraction places Order personnel and assets at risk that the AI and her vessel will be dealt with forcibly.