The Talocan and Sleeper Connection


IC icon.png

This article is written from an in-character/roleplay perspective. If you wish to contribute to this page, please refrain from making out-of-character (OOC) references.

Author: Unit XS365BT


The theories behind the disappearance of both the Talocans and 'Sleeper' species are generally in line with the theories on the Jove, specifically that they moved on; however we do not believe that this is the case.

Several references within sleeper constructed databases mention research into Talocan technologies, and research into viruses.

This information has led us to a startling and wide reaching theory concerning the Talocans, Sleepers and Rogue drone populations, and the potential links between them.

To explain we should start at the beginning.

Firstly, we believe that the Sleepers were originally the Talocan equivalent of the capsuleer.

Instead of being physically attached to their vessel via a capsule however, they were remotely linked to it, while their physical forms lay in a Talocan structure. In essence, they were a form of expendable military force, controlled from afar and used for scouting and defensive matters.

During the early development of these remote drones, it was decided that, due to their expendable nature, some form of failsafe would need to be employed, in case a Talocan 'capsuleer' decided to take actions against the will of the Talocan leadership (the CONCORD of Talocans in effect). This failsafe is still in place, as can be seen with the warp-drive detonator incorporated into every sleeper drone.

As can be seen from the tensions between capsuleers today and the baseline human population, those who do not possess the power and prestige of capsuleer status can be fearful, or even directly violent towards capsuleers. A war between these two groups is possible.

Translated into the past, with Talocan and Sleeper entities, this tension could have resulted in war.

The first acts of the Sleeper populations would have been to repurpose the Sleeper drone failsafe as a self-destruct. Removing control of the device from the Talocans, and find a method to fully transcend their physical form, becoming infomorphic instead of biological.

The transition to infomorphs was required as the 'sleeping' controllers of the drones would be incredibly susceptible to Talocan counter-assault. Whereas infomorphic data can be transmitted prior to the destruction of a 'drone' and re-incorporated into the next drone to be built.

The war between these two advanced species appears to have ravaged both sides. However it is apparent that the Sleepers gained the upper hand. It is at this time that we believe the Talocans released a morphic AI-virus into the Sleeper population, in a last ditch attempt to save themselves. While this failed, it caused the sleepers to slowly degenerate into the drones we now meet, instead of the advanced infomorphic society they became. It appears that this was a slow process however; as they had sufficient time to create whole new structures in Anoikis that appear to be primarily designed for function rather than aesthetics (though they are still interesting to look at).

This leads us to two specific headings in the site known as ‘The Mirror’.

Triage - This is where the sleepers examined damaged infomorphic data, to discern the cause of the damage,

Quarantine - This is where virally infected infomorphic data was placed prior to transmission to a Virus Vault of some form (all anti-viral programs available today use this principle. Quarantining suspected files until a decision or diagnosis is completed regarding their status).

It is our theory, at this time, that the sleepers, when they had isolated virally infected infomorphs, and diagnosed them as 'unrecoverable' that they transmitted these infomorphs to a distant region of space, far from their homes, in the hope of removing the viral taint from their species.

This leads us to Operation Spectrum Breach. (OSB)

While the potential remains that the 6 named drones from the Code Aria report were responsible for the event that caused this operation's failure, we believe that the aforementioned drones were involved in other activities at this time.

It is our theory that the worker drones within the OSB area of operations uncovered the secure data storage device that contained the damaged infomorphic data sent to this region of space by the sleepers. The speed of infection amongst the drones across 8 linked regions of space appears to be far in advance of New Eden technology of the time, therefore it is a feasible assumption that some outside influence was at work.

this theory would explain both the speed of OSB drone infection and the current apparent link between the supposed awakened sleeper infomorph known only as 'Awakened Infomorph' and the Rogue drone forces that have recently appeared within the Eve constellation.

it would also explain why in several locations throughout the cluster, there are rogue drone elements that do not follow the standard practices of the rogue drones that are most commonly encountered within the cluster.

It is these discrepancies that we believe the 'named' drones from the Code Aria reports were actively working upon during the time of the OSB event.

To Arek'Jaalan: Ancient Races
http://wiki.eveonline.com/en/wiki/The_Talocan_and_Sleeper_Connection
wiki.eveonline.com
crawl=CC-MAIN-2013-20
22649
application/http; msgtype=response
sha1:MNH5IT4SSR4YE4WCT2NWOCSU4YEMXHGD
<urn:uuid:d0e5bf19-0e8d-4c30-9bc5-9c72668323d2>
2013-05-24T22:00:46Z
87.237.39.208
sha1:K35ETSXTTB6E2L46LLNL6DC2FDYL6UOC
<urn:uuid:a241e518-15a9-4131-b96b-efe617847322>
http://wiki.eveonline.com/en/wiki/The_Talocan_and_Sleeper_Connection
response
<urn:uuid:18214f44-bb17-4167-aacb-3bb4502b9a4a>
robots: classic
hostname: ip-10-60-113-184.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2013-20
operator: CommonCrawl Admin
description: Wide crawl of the web with URLs provided by Blekko for Spring 2013
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf