Artificial Existence Facts : V.2

Posted 6 years, 2 months ago by Ledokol

  Artificial Existence Facts :: Version 2  


               Originally I got the inspiration to turn armaments into humanoid OCs from the Japanese online game Kancolle. However, as time went by and I got down to seriously contemplate how I want to make my own plot differ from the game, I made a decision that many of their characteristics are more suitable for androids than being flesh and blood humans like Kancolle. (in Kancolle concept the warship girls can bleed when they're injured but weirdly become healthy again after they take a repair in a form of 'hot bath' :/ This sexualized aspect of Kancolle is certainly one thing I want to stay far away from)

               This revise isn't the complete final version, I expect to continuously improve and add more details - maybe write the version 3 some time in the future if this version 2  has become to outdated. If there is any topic which isn't clear enough or some topic you wish to know that I didn't cover here, feel free to comment and let me know!



  SETTING EXPLANATION  

varyagframe_by_colorlessocean-dc1j4tp.pn

  Genres

               The main genres of this plot can be divided into four types; slice of life, comedy, drama and semi-historical. The plot is main concentrated on progression of events in Russia and not mentioning about other countries.

               Although some of these genres can move dangerously close to risky topics like politics, nationalism, religions and the more intolerant opinions toward LGBTQA+, I'm going to keep my plot free of those divisive subjects Those topics will be kept away from the plot and some political situations will only be mentioned in passing without going into detail whether it's right or wrong. The OCs can appear to be quite ignorant to some of these subjects because they don't really understand them in the same way humans do. Thus, please keep in mind that their view of something (i.e. feeling overly wary of national affair with other countries) shouldn't be taken seriously.

              And there is a possibility that I will make ocs of warships belong to other nations beside Russia. These OCs will be minor characters though, for example US Navy ships based at the Yokosuka naval base in Japan may occasionally pop a visit to the Pacific Fleet in Vladivostok (in RL these visits had happened quite a few times until...recently). They're unlikely to have their own plot but only appear in a plot that one way or another related to the Russian counterparts.


               Slice of life  :: Focusing on the OCs' everyday life on the bases they belong to. Various sub plots will discover the relationships between warships and submarines(the biggest group of OCs), sometimes venture out to the cross-forces relationship i.e. Su-33 (who despite being an aircraft android, actually belongs to the navy) and his family who work for the air force. Occasionally there will be fictions or roleplay logs about certain events in fleet (i.e. how Nevskiy causes disturbance in the Kamchatka base or when Kulakov returned to Severomorsk after almost two decades). Several plots will also provide a look at the locality their bases are located, of local geography, climate, history and culture.


               Comedy  :: Either a new sub plot idea created especially for comedic effect (i.e how Panteleyev always tries to hide his stash of junk food from Shaposhnikov who wants to get rid of them at all cost) or twisting the fact from real history / real life happening into a more humorous take (i.e. how Su-33's 2005 accident of falling into the sea is from Kuznetsov's own doing by cutting the arresting cable so it would snap on landing attempt)


               Drama  :: There are a few subjects which I based on as dramatic sub plots. The majority of them are based in real history of unfortunate incidents from 1980 hence I want to keep them minimal and not as the main genre for this plot. These incident serves as important landmarks in the plot timeline - 

  • The ammo storage explosion in Severomorsk in 1984
  • The Chernobyl accident in 1986
  • The sinking of nuclear submarine K-278 Komsomolets in 1989
  • The collapsing of the USSR in 1991 which triggered a massive abandonment of both warships in active duty and those in the middle of construction
  • The 1995 accident of Russikye Vityazi in Vietnam 
  • And the sinking of K-141 Kursk in August 2000.

  IMPORTANT  

           Concerning the last incident of K-141 Kursk sinking; because this incident was a major tragedy in Russia and many Russians are still grieving over it, even though I do have a plan for Kursk OC - he will NEVER be used to portray the event when his fatal accident happened. In fact, the entire event will never be created in any way; drawing, fiction or roleplay log. Kursk will appear only as a minor character in the flashback of K-150 Tomsk's memories when he spent the time in the Northern Fleet where he was temporarily assigned to. Kursk's timeline will end when Tomsk made his transfer to the Pacific Fleet in late August 1998, almost two years prior the accident.


               Semi-historical  :: Although the main idea behind the plot is based from real history (mostly since 1980), starting from the year 2006 only selective events from real history will be chosen to incorporate into the plot. This is due to political factors and undesirable real life events which I'd rather not have them tangled with my plot and world building. Please see the clarification below for more details.


slavaframe_by_colorlessocean-dc1j77r.png

  'Semi historical' clarification

              At the time when I conceived this idea of a universe for armaments-turn-humanoids plot it was May 2015. And as we all know by that time the conflict between Russian and Ukraine has already gotten into its second year. While between these two countries I have more interest on Russia, that doesn't mean I support Russia in this conflict with Ukraine. And previously, there was also the Russo-Georgian War in 2008 where the real life counterpart of Moskva participated in blockade and inflicting damage on the Georgian Naval Force. Again, although I'm neutral toward Georgia, I find the idea of including this conflict into the plot extremely awkward and inconsiderate to Georgians.

               In keeping with the mentioned conditions in the genres topic concern not incorporating politics view, nationalism, religions into the focus of the plot and entire universe, I've decided to alter some details of this world which differs from the real life as following:

  • In this world, the Crimean Peninsula belongs to Ukraine and the Russian Black Sea Fleet still renting the base from Ukraine.
  • As the result, the entire conflict between Russia and Ukraine which started since 2014 DOES NOT EXIST in this universe. Both countries are in cordial term.
  • Similarly, the Russo-Georgian War in 2008 also didn't occur. South Ossetia and Abkhazia do not exist as separated parts from Georgia.
  • Finally, the Syrian War, IS situations and the Russian intervention in Syria do not happen in this universe. There will be events that some Russian warship OCs visit the Syrian port of Tartus but it has nothing to do with the aforementioned conflict. Tartus has been a friendly port to Russian Navy since the USSR era and historically the Soviet naval ships called port in Tartus regularly.
  • Though it doesn't have much to do with Russia, if possible I'd prefer to omit the 9/11, too.


               Also, I'd like to clarify about the opinions regarding neighboring countries of Russia possessed by a few OCs. Their opinions do not reflect my own stance, as the creator, toward the these countries. These opinions were formed in them for various reasons according to what they experienced, many of which even among their fellow androids do not share the same opinion. Once again, please do not take these opinions seriously. As of the moment I'm writing this facts revision, the troublesome ones are:

  • 548 Admiral Pantelyev - had a negative opinion to the independence of Lithuania because in doing so, Kaliningrad was suddenly cut off from the rest of the USSR. As he was rather inexperienced back then, he didn't understand that just because Lithuania became independent from the USSR didn't mean that Lithuania suddenly turned into an enemy of his home region. At present he already discarded such opinion and views Lithuania more favorable but such thought is still mentioned in his back story.
  • 011 Varyag / 055 Marshal Ustinov / 063 Admiral Kuznetsov / 121 Moskva - they were all affected by the declaration of independence by Ukraine, as their youngest siblings were still incomplete, hence stuck in the Ukrainian territory. Their opinions mostly lean toward questioning of the independence because they do not understand how different Ukrainians are from Russians and certainly do not know about Holodomor. Nowadays they mostly accept the independence of Ukraine but feel estrange that, aside from Moskva, they can never return to their birthplace any longer. Moskva also feels weird that he's still serving on the Ukrainian territory but the nation he's serving in not Ukraine but Russia which is a descendant state to the USSR.
  • 'Borislav' - I have to admit he's the most problematic one because the historical facts of what happened to him generated a very negative feeling for him toward independent Ukraine. His bitterness is somewhat exaggerating by his own desire to get out from Mykolaiv, thus blinding him from acknowledging decent things the Ukrainians tried to do for him.
  • Warships belong to the Black Sea Fleet - Generally they accept the independence of Ukraine, though feel odd to some degree. Certain ships, B-871 Alrosa in particular, feels more wary toward Ukraine because he was one of the ships that was disputed over the commanding during the time when the Russian Navy and Ukrainian Navy still couldn't come to an agreement of dividing ships belonged to the USSR Black Sea Fleet.
  • Warships belong to the Baltic Fleet - Accepted the independence of Lithuania, Latvia and Estonia, though sometime still moan about the lose of a few bases in Klaipeda, Liepāja and Tallinn
  • Admiral Tributs and Marshal Shaposhnikov - Transferred to the Pacific Fleet at the same time in 1987, when the relationship between the USSR and China was still not all that friendly. They both grew the habit of being overly wary of China even though in recent years Russia and China have become a lot more friendly. Toward Japan, there is still the ongoing diplomatic disagreement regarding the Kuril Islands which prevents the two countries to officially sign a peace treaty since WWII.

kolyaframe_by_colorlessocean-dc1j66r.png

  World situation 

               There is no major arms conflict anywhere. The world is at peace and Russian is in friendly or at least neutral term with the rest of the world. It might sound too idealistic, but after all even though the OCs are based on armaments, wars and arms conflicts aren't supposed to take the center stage in this plot.

               For reference, the territory of Russia in this universe is according to this map: (wikicommon link)

800px-Map_of_Russian_subjects%2C_2008-03


petyaframe_by_colorlessocean-dc1j6dw.png

   Android basic explanation

               At the moment, the majority of armament androids OCs are comprised of warship OCs (both surface ships and submarines). There is a plan to introduce more aircraft androids than just Sidor (Su-33) and Kuzma (Ka-27) but currently I'm having a difficulty designing armament/equipment for the other types of aircraft. The androids belong to ground force (battle tanks, missiles and armored vehicle) can take even longer to appear as they're the type of armaments I'm not familiar with the most. For the complete list of both existing and planned OCs, please check this spreadsheet.


        Definition 

               As the warfare technology advanced and weapons are getting more and more destructive, many nations start contemplating the idea of building armaments with human characteristic, turning them into androids to conduct the warfare battles in place of the more 'fragile' humans. Due to the conflict in concepts with a couple of warship humanoid OCs whose constructions exceeded the beginning of WWI, I can't pinpoint the exact period in the plot timeline yet when the first warfare androids were created successfully.

               By given armaments humanoid shape, they can easily blend with ordinary humans for covert missions and harder to pinpoint as targets by the enemy's long-range attack. It also makes easier for humans to transport these armaments and their mobility increased significantly, especially for the warships and battle tanks. Their physical appearances match the typical genetics of the USSR's population, though during the USSR era there was a dominating trend of creating androids with Slavic appearance to assert the position of the European part of the state. Only after the collapse of the USSR that finally androids with less Slavic appearance began to emerge as the creator institutions gain more freedom on the appearance design to represent the non-Slavic population of Russia.


               Generally, the outward appearance of andrids allow them to blend easily with ordinary humans as following:

  •      Height :: From 150 centimeters (4'10) to 190 centimeters (roughly 6'3)
  •      Weight :: Varied from 100 kilograms (220 lbs.) for the lightest aircraft androids, 250 kilograms (550 lbs) for smallest tank androids to 1,500 kilograms (1.5 ton or 3300 lbs.) for large warship androids like Pyotr Velikiy and Admiral Kuznetsov
  •      Hair and eye colors :: Matching what available naturally for humans (black, brown, reddish tones and blond hair and brown, green, grey and blue eyes), only 011 Varyag has an 'unnatural' bright red hair due to unorthodox 'experiment' of the engineers who participated in his creation.



        Conceptual difference between warship androids / aircraft androids / 'ground' androids 

                The first major difference between the warships and the other two types of androids is mainly that warship androids are created on the basis of "one ship/submarine = one individual OC" while the other two are under condition of "one type / class of aircraft / armament = one individual OC". The only exception outside of the warships category which allowed multiple humanoid OCs of one class of aircraft are the aerobatic teams Russkiye Vityazi and Strizhi, six OCs for each team respectively. 

                While in the main plot there is only a single OC for a certain type of aircraft / battle tank / other non-ship armaments, this doesn't mean that each one of them is the sole embodiment of that type of armament existed in the entire Russia. For example, there will be only one OC for the Su-34 fighter/bomber jet who will be used regular in the plot but there are some more 'dummy / extra' humanoid Su-34 scattering all over several bases within Russia that won't get mentioned about except in a rare occasion, which they will still be mentioned as 'nameless' Su-34s.


               Physically, warship androids are stranger than the other types. They also tend to be more powerful, weigh more and take much longer time to complete their construction. However, when it comes to vitality, the other types of androids, being that they're based on "one type / class of aircraft / armament = one individual OC" concept, are easier to get damages but not always to the point that they will be completely written-off (equivalent to death) because it's more convenient to build hundreds of spare parts for them in comparison to the warships. Therefore, using Su-33 for example, he once suffered a crash in 2001 but still lived on after receiving extensive repair using several spare parts. 

               Meanwhile the warships, though harder to suffer extensive damage, once such level of damage is reached, often too late to save and sink to their death. Despite their nature of operating on water, the surface ship type of androids are more vulnerable - their structure cannot seal off water as good as the submarine type if they sink beneath the surface. Sometime they can be saved if they are rushed to the repair facility before water can damage their inner electronics permanently, but most of the time such scenario can hardly achieve amidst the battles. Another uniqueness in the warships case, sometimes cannibalization do happen (cannibalization = choosing a ship from a certain class to dismantle and use the disassembled parts as spare parts for ships in the same class). Moskva was close to having this done on him to complete 'Borislav' and there's a possibility of Admiral Spiridonov has been cannibalized for the four Fregat androids in the Pacific Fleet as well.


sidorframe_by_colorlessocean-dc1j531.png

Concepts regarding 'birth' / 'awaken'(launching) / 'death'

       Aircraft 


               BIRTH  -- Aircraft androids are rather a complicated type in this aspect. A 'perfect, ready for real combat' android is created after going through several prototype 'test androids', which after the conclusion of experiment stage, are disposed and collected data from their inorganic brain to programming into the new inorganic brain for the 'complete' android. Test androids sometime could be lost in an accident during testing period, hence the engineers prefer not to work on constructing 'complete' android just to go through the experiment. Test androids are more simple to create; they aren't capable to think on their own in most situations, only act on orders and only during the experiments they can make a decision based on data on their inorganic brain to correct the approaching speed/angle or abort landing attempt.

  •           Taking example from Su-33 who is developed exclusively to use on aircraft carrier, this was what his creation process went through;
          The USSR first commenced the development of Su-33 in late 80's by using an android based on the scheme of Su-27 android. This test android then went under several modifications through out the experiment period during the late 80's to early 90's. This test subject android, known as Su-27K, commenced the first landing on Admiral Kuznetsov's floating platform in November 1989. This data later was transferred and programmed into Sidor's inorganic brain, which explains the strange phenomenon that Sidor sometimes will mention that "he has the memory of first landing on Kolya's platform before the USSR collapses, but it wasn't he himself who did that."


          The first test android then ceased his existence around 1991, replaced by the second test android whose physique was more closely resembling what Sidor is in height, weight and body shape to further collect data and experimenting. But even so, although there is a data of landing speed, angle and acceptable speed of crosswind in his inorganic brain, Sidor still needed to practice to make sure he can 'physically' land and take off from Kolya's platform. If not, he will suffer from a kind of 'deja-vu delusion', as name by the sensation of feeling like he has already experienced something when in reality he doesn't because it was a memory transferred from the test subject android.


          Sidor himself was created around 1997, went through a period of 'unofficial' deployment on land to examine any defect or incompatible of data in his inorganic brain and his physique. He was officially 'introduced' to deploy as a part of carried team led by Kolya in 31st August, 1998 - which considered as his 'birthday'. Although he basically 'born' from the scheme of Su-27, he doesn't consider Su-27 as what humans would call 'father', instead he views Su-27 as older brother.


               AWAKENING  -- Although their inorganic brain is programmed with necessary data and their bodily structure are completed, these type of android will only be activate - equivalent to 'awakening' when they're ready to be test out before actual deployment in army. This process normally takes 2-6 months to complete.

              DEATH-- Mainly by three causes; sinking into water, the lack of repair and scrapping/dismantling


  1.           Death by water - Most aircraft androids are constructed in a way that their structure cannot seal off water well if they fall into any kind of water body. In most circumstance, the water will get into their inner structure and ruin the intricate electronics inside. Coupling with the fact that they cannot swim, this is mostly a sure kill for them unless rescued very quickly, which is oftentimes difficult to achieve unless large submarine androids, which is the only type of androids able to withstand the water pressure to dive beneath the surface, are available nearby.
  2.           Death by the lack of repair - If aircraft androids suffer an extensive damage from accident or shot down in battle and there isn't a friendly facility which could provide spare parts for repair, then they can die. One sample case was when 3 of the Russkiye Vityazi androids suffered an accident in Vietnam in 1995. Because the accident site was in foreign territory far from Russia, it was decided that it would be too much hassle to take them back to repair.
  3.           Death by scrapping/dismantling - The most common cause of death in all type of androids. Their inorganic brain will be deactivated for the final time, after that the body structure will be disassembled.


        'Ground' androids  (battle tanks and other ground-based androids which lack ability to either fly or float on water)


               BIRTH  -- Since these 'ground' androids face much less risks of damaging/losing during the experiments prior real deployment, they tend to be created then gradually being modified according to the result from the experiments.

               AWAKENING -- Like the aircraft type, they will be activated once they're ready to conduct experiments before making changes to finalize their capability prior entering real deployment in the ground force. Many of this type of androids had experiences in them as test androids to conduct various testing before being permitted to use in real combat.

              DEATH  -- Again, with abundant supply of spare parts they can be repaired back to working condition in many scenarios. Their causes of death mostly comprise of; sinking into water, killed in battle, the lack of repair and scrapping/dismantling


  1.           Death by water - Ground androids are typical heavier than aircraft androids of the similar size. Although both of them possess inability to swim, the sink rate of ground androids is much faster than that of the aircraft androids. For example, aircraft android like Sidor has a sink rate of 2 meters / second when he falls into the water while for Vasiliy (T-72 tank android) has a sink rate of 5 meters / second.
  2.           Death in combat - Because this type of androids is practically a target of the enemy fire themselves, even though they're built to be rather robust they can be killed in battle by direct artillery hits.
  3.           Death by the lack of repair - Like the cause above, if the artillery fire doesn't instantly kill them, it can still cause them a severe damage. And similar to the aircraft androids' case, sometimes the humans just decided that taking the damaged androids out of battlefield and back to repair is too much of a burden. Thus they could be left to die (aka until their inorganic brain couldn't operate anymore / run out of energy) - such scenario certainly has happened before in some battle, in particular the Soviet-Afghan War in the 80's.
  4.         Death by scrapping/dismantling - The most common cause of death in all type of androids. Their inorganic brain will be deactivated for the final time, after that the body structure will be disassembled.



        Warships 


               BIRTH -- Because warship androids are complicated in part that there aren't as many androids in the same class/project built as the first two types (i.e. at most around twenty-something vs over a hundred), creating each one is a challenge in itself. The first of each series can serve as both 'complete' version and a test subject to make further improvement in the next order androids. Their construction time also lengthened significantly in comparison to both aircraft and ground androids due to strengthened structure, more sensor controls needed to interact with higher number of armaments and radars, and in the case of those which use nuclear energy to operate, more complex internal components concerning their fuel system.

               AWAKENING -- 'Awakening' is when the newly built android was activated to conduct test on their balance while using equipment to stay afloat on water or get used to water in general. This process is what distinguishes them from the aircraft and 'ground' androids as the latter two have an instinctively fear of large water body, something which needs to be completely eliminated in the naval androids. The process goes on from training them to balance themselves on water surface in their 'empty' form (without armament and other equipment which will add weight on their body) to learning to balance themselves with armaments and other equipment added. The submarine type will learn to utilize their built-in equipment which assists them in 'swimming' in the water and surfacing above water.

                     At the same time, when they are not conducting the balance training, they start learning several bodily skills and undergo more experiments to strengthen what has been programmed into their inorganic brain prior which will aid them in their future deployment. During this period is their first opportunity to learn social interacting with both their own kind and ordinary humans. This process noticeably needs a longer amount of time for the warship androids to be completely prepared for their deployment and usually takes from one year to 4-5 years in most cases.

  NOTE 

           There was a couple of extraordinary cases in recent history that an android 'awakened' before the scheduled date. This could only possibly occur in the androids that use nuclear reactor as their source of energy, as their reactor was activated to test out their functioning from early period. In both cases, which involved the nuclear-powered submarine androids K-535 Yuriy Dolgorukiy and K-561 Severodvinsk, the 'sleep mode' which was the default command to their inorganic brain at the time involuntarily disengaged as their construction dragged on longer than it should have been due to economic trouble. It took a few minutes before the engineers realized that the sleep mode had disengaged and they submitted a new command to reactivate it. Both of them retained the memory that they have 'woken up' in the facility where androids undergo fundamental bodily structure construction but they could hardly recall much detail as they were put back to sleep soon afterward.


               DEATH -- The most notable 'massive die out' occurred during the 90's after the collapse of the USSR. Warship androids require considerable funding for maintenance per unit in comparison to the aircraft and ground androids. Therefore, even though many warship androids weren't considered obsolete in technological capability at the time, were selectively abandoned and left to 'die' from the lack of maintenance. Aside from that notable incident, the other causes of death are: suffering extensive damage which leads to sinking and scrapping/dismantling.


  1.      Death by sinking - The surface ship type of warship androids possess the lower structural resistance to the pressure underwater then the submarine type, some of which can dive down to the depth of 600 meters. If the surface ship type sinks deeper than 100 meters, the possibility of retrieving them for a repair is impossible as the structure will collapse from the weight of the water and thus internal electronics are ruined by sea water that leak inside. Meanwhile, for submarine androids, their structure limit depends on the design of the class each of them belong to.
  2.      Death by scrapping/dismantling - The most common cause of death in all type of androids. Their inorganic brain will be deactivated for the final time, after that the body structure will be disassembled.


               All in all, because this plot focuses more on the other aspects of these androids' existence which don't involve them being used in war, the chances are the characters will continue to live on. The only exception is the warship androids, which their life span in the plot tied closely to their real life counterpart. If somehow their real life counterpart cease their existence, then in this plot they will cease their existence as well. By 'ceasing their existence' means that their timeline will conclude in the year their real life counterpart sinks or sends to dismantle; for example 'Borislav' will only play a role between 1983 (when his creation started) until 2017 as his real life counterpart was demilitarized and confirmed to be dismantling in March 2017. He might be drawn or written in fiction again on 2018 and later years but it will strictly revolve around his past from 1983 to 2017.



boryushkaframe_by_colorlessocean-dc1j52d

About emotions imitation

               Most of the emotions displayed in the androids' behaviors are nothing short of imitation of what human behavioral data programmed into their inorganic brain. Basically, they rely on such data to interact with humans in an appropriate response to situations. How deep an android can comprehend emotions depends on how each individual android examine and interact with the data in their inorganic brain. Although prior their deployment to the arm forces, there will always be a test to see how well the android interact with humans using the data programmed into their inorganic brain.

                Some of the USSR era androids prefer to discard such data and interact in a strict, emotion-void communication (i.e. TK-208 Dmitriy Donskoy, Vice-Admiral Kulakov and K-223 Podolsk). There have been some notes on the differences that androids whose deployment began after the collapse of the USSR tend to be more expressive and at ease with using the emotion imitation to the highest efficiency. Observances informed that some androids chose certain type of emotions as their 'default' mode in personality aspect. 


zhenyaframe_by_colorlessocean-dc1j738.pn

About being asexual / aromantic and no genitalia

                Learning from experiences among ordinary humans, romantic type of love and sexual desires are deemed as being the causes of unnecessary troubles. Decisively, the engineers concluded that giving those qualities to androids will result in more harm than good. Platonic type of love instead being viewed as more appropriate for androids to experience and encouraged them to engage in platonic bonding of different levels (friends, siblings).

               By default, androids are classified as both asexual and aromantic as the information about such topics are being intentionally excluded from their inorganic brain's database. The majority of them are clueless of how to respond when being approached with romantic and sexual intention. Some may know a bit more from imitating what they see on humans and 'fake' an appropriate response. However, once being pressed on, they will eventually discontinue such behavior. From observations, other forms of response toward unwanted romantic and sexual intention can vary from indifferently unresponsive by politely turning down the approach  to negative reactions like imitating anger to ward off the unwanted intention or openly protesting.

android_anatomey_by_colorlessocean-dc4b0

               As a safeguard measure to protect the androids from being lured into engaging sexual activities with humans, their bodily structure is built without genitalia. Although there is a bulge shape which imitated the realistic pubic area of human male, it only appears that way because the metal piece which made up the pubic 'bone' area is moulded into a thicker shape in order to follow human's anatomy.


tomskframe_by_colorlessocean-dc1j97j.png

About 'sibling/familial bond'

               Fearing that if the androids are treated solely as machine that has nothing in common with humans, they can easily turn dangerous by perceiving humans as weak and undesirable. The engineers then decided to add information of human's familial bond into the androids' inorganic brain and introduce such bonding to the androids of the same project/class or originated from the same manufacturers. Hence, they can understand why friends and families are the 'weakness' of humans and also something important to them. By doing so, the engineers hope to increase the androids' connection to humans to lessen the chances that they might rebel against human's control or viewing human's life as worthless.

               In most part, it has worked out pretty successfully, although there were times when it backfired somehow. The particular case is concerned K-150 Tomsk who's known for being what would classify in humans as 'overly emotional' due to the loss of his older sibling, K-141 Kursk. His behavior tends to become a bit erratic during the period of year when the anniversary of the accident rolls in. Also another noteworthy case is the project 941 Akula SSBNs, which the entire class of six androids strongly rejected the siblings bond and treated each other hostilely. 

              Still, familial bonds outside of siblings are not really taken seriously among them. Ladnyy, for example, is often upset when Grigorovich calls him like an older family member (grandpa), despite they're distantly related by that Grigorovich is the fifth modification of the ship in the same project as Ladnyy (1135 and 11356). The submarines born from Sevmash predominately view those from different classes as 'distant relatives' but practically treat each others as friends.


zinaframe_by_colorlessocean-dc1j6xr.png

  Crossover with city OCs explanation

                This crossover resulted from the fact that I first taken interest in modern Russian navy warships because of the research I did for one city OC. Due to in reality, various cities and locality in Russia do have certain type of connection with the warship (taking patronage over a ship or being the place where ships are constructed), these city OCs will take the roles of guidance, non-blood related parent figures or a regional commander. A few may appear in an additional role as coordinators, as their cities host the industrial complex which produced assorted component for certain group of armaments (i.e. - Rybinsk works closely with several Sukhoi jets as the Saturn Enterprise which manufactures the engines for these androids located in Rybinsk).


1167003?

Yaroslavl

[ Valentin Medeveditsin ]
           A father figure of the Paltus-class diesel-electric submarine B-808 Yaroslavl, whom Valentin took patronage in 1999, and three Dugong-class landing craft androids of the Baltic Fleet.
1262551?

Arkhangelsk

[ Zinaida Beleshkina ]
          Because her region hosts one of the biggest industrial complexes supplying the state with nuclear submarine construction, to all nuclear power submarines born in the Sevmash Shipyard in Severodvinsk she's their mother figure and often called as Mother, Mom, Mamochka, etc.

List of submarine androids who regard her as their mother:
Project 941 Akula - TK-208 Dmitriy Donskoy / TK-17 Arkhangelsk and TK-20 Severstal
Project 667BDR Kalmar - K-223 Podolsk / K-433 Sveyatoy Georgiy Pobedonosets and K-44 Ryazan
Project 667BDRM Delfin - BS-64 Podmoskovye / K-114 Tula and K-18 Kareliya
Project 949A Antey - K-119 Voronezh / K-442 Chelyabinsk / K-456 Tver / K-266 Oryol / K-186 Omsk and K-150 Tomsk
Project 955 Borey - K-535 Yuriy Dolgorukiy / K-550 Aleksandr Nevskiy and K-551 Vladimir Monomakh
Project 885 Yasen - K-560 Severodvinsk and K-561 Kazan

c297846_7f9b0138dfcef1ab2324927a58559dc4

Kamchatka

[ Nikita Kazakov ]
          The embodiment of the Kamchatka peninsula which hosts the Vilyuchinsk Base, where the nuclear submarines of the Pacific Fleet are stationed. He's the regional commander of the Pacific Fleet's nuclear submarine division. He also provides patronage to two of the Paltus-class submarines of the Pacific Fleet - B-464 Ust'-Kamchatsk and B-494 Ust'-Bolsheretsk.
c559927_674f3484416d6971643f1798cfbb7379

Kursk

[ Sveyatoslav Chernichenko ]
          Currently the patron and father figure of Baltic Fleet's Steregushchiy-class corvette, name ship Steregushchiy. Previously he was also the patron of K-141 Kursk.

c306985_54b3dfefe2d4c635883c990211f4669f

Krasnoyarsk

[ Yakov Nagorkin ]
          The embodiment of the Krasnoyarsk Kray, hosting the industrial complex 'Krasmash' which manufactures the Sineva and Layner SLBMs used by the project 667BDR and 667BDRM androids in the Pacific Fleet and Northern Fleet.

wipblabla_by_colorlessocean-dbticd3.png

Rybinsk

[ Konstantin Zyulin ]
          Hosting the NPO Saturn Enterprise, the manufacturer of engines used by Su-27, Su-33, Su-34 and Su-57.




  IN-DEPTH ANDROID'S FUNCTION EXPLANATION  

yurkaframe_by_colorlessocean-dc1j6sb.png

  'Assigned diminutive'

               Calling people with diminutives is part of Russian tradition. There are diminutives which seemingly act as a 'default' for each name; i.e. - 'Sasha' for Aleksandr, 'Kolya' for Nikolay, 'Volodya' for Vladimir and so forth. Because the majority of warship androids didn't have a chance to choose their own names as they carry the names of various important people (historical rulers, military commanders and politicians from the past), there are times when too many ships with the same first names are assigned to the same fleet. The most outstanding case being there are three 'Nikolay' in the Northern Fleet (Kuznetsov, Chiker and Kulakov) and within the Fregat-class itself there are both Nikolay Kulakov and Nikolay Vinogradov.

               In such situation when these ships somehow are assigned to join force in the same mission, it will be too confusing to use the same 'default' diminutive on all of them during communication. Hence a scheme is established to assign a diminutive in the 'sole personal diminutive' fashion for ships carrying personal names of humans. In the case of the four Nikolay ships, Kuznetsov as the most important ship takes the most common diminutive 'Kolya' while the other three settled with the more uncommon versions of their choice ('Nikasha' for Kulakov, 'Kolyusha' for Chiker and 'Nikolka' for Vinogradov)


yamalframe_by_colorlessocean-dc1j54m.png

   Fuel

          The two main types of fuel are oil and nuclear fuel comprised of uranium-235. The latter type is only available for small selection of warship and submarine androids. While their inner system makes it possible for them to consume organic food of humans, this only serves as a tactic to create an illusion that they are no different from ordinary human. The androids have no use for calories and nutrient unlike humans and the foods usually give a very low energy output to them.

          Oil fuel comes in the shape of either drinking cartons, similar to a carton of milk or fruit juice, made of sheet metal or metal cans for increased durability during missions outside of the base. The amount consume each time depends on both the type of the androids, with the warship incline to consume more than the aircraft and ground androids, and the duration between each refueling (i.e. - if they go on a long mission and come back straight to the base without any refueling in between, they're likely to be starving and consume a lot).

          On the opposite, uranium-235 fuel comes in a shape of small capsule, almost imitating human's medicine. The capsule shell is made of metal and each case which is given to the androids when it's a time for their refueling consists of six capsules in total. When refueling happens, the android will be assisted by engineers who will extract one out of six old capsules from the internal reactor. After that the android will swallow one of the new capsules and wait until their inner mechanics safely places the new capsule into the recently vacated spot. After monitoring that it occurs, two more aged capsules will be extracted and again, android swallow two new capsules. This procedure will repeat until all six capsules are extracted and replaced.


yashframe_by_colorlessocean-dc1j6ft.png

  Sleep/ temporary system shutting down

          Being armaments, sometimes they need to operate at 24 hours for extended period. Requiring sleep as the part of maintenance would be much inconvenient. Therefore, they can operate without sleep for several days to a few months. It's only when they are not on a task and staying at their base that they can 'shut down' their system to cool down and thus seemingly pretend to 'sleep'. Those who operate using fuel as their source of energy tend to need more frequent 'sleep' to preserve their fuel, in comparison to those using nuclear energy which requires refueling only once every five years and almost have unlimited energy during the period.

          In their respective bases, the androids are provided with basic living accommodation; a living quarter for them to pair up as roommates with all the basic amenity as given to human personnel. Most often, the same type of armament androids will be paired up as roommates but it can be rearranging (i.e. - how Shaposhnikov requests to be roomed with Irtyush, the hospital ship of the PF, because he doesn't want to be a roommate with Tributs, his 'fiend').


nikashaframe_by_colorlessocean-dc1j6tm.p

  Armament control / built in sensors

          The level of sensitivity to perception of the basic senses in androids are significantly heightened in comparison to humans due to various sensors. They can tell the temperature of something before even touching it by using heat sensors located on several parts of their body (tip of fingers, hands, arms, shoulders, chest, back, feet, etc.) which are more accurate than human's sensory input.

          Although considered non-official task, many times androids are used to detect if there is any poison or dangerous substance in food. Tastes and smells are the type of sensory inputs that the androids, even though can not really sensing favors and odors, can rapidly distinguish as it breaks down into a stream of data. With heightened sensitivity using sensors, they can tell the exact type of dangerous substance in food or if the food is unhealthy (too spicy or salty) to ordinary humans' taste. Also, with the sensors, they can even detect colorless and odorless poisonous gas.

          Concerning armaments control, their armaments are being controlled through signal from sensors inside the inorganic brain. During their missions, androids may carry additional radars and other external sensors which work coordinately with their internal sensors to enhance their sensory ability to detect targets from longer range.


podolskframe_by_colorlessocean-dc1j62s.p

  Repairing/modernization deactivation

          Deactivation will occur when repair or modernization plan to alter their basic bodily structure. In case of repair or modernization of their equipment or armaments which regularly don't have a function in their daily life in the base and only equip during military missions, then the system deactivation on androids is not necessary. That being said, sometimes androids are still active and move about within the territory of the facility where they were sent for repair or modernization. For example, Marshal Ustinov spent five years at the Zvyozdochka Shipyard for modernization but more than a half of that period, he was roaming around familiarized himself with the birthplace of his many submarine colleagues and hanged out with those staying in the same shipyard.

           Under the circumstance which required the android to be deactivated for bodily structure modification, the engineers will have the android laid down on a special platform with can withstand the weight of the android then deactivate the system. The android will then enter a similar state to a patient who went through anesthesia and the team of engineers will proceed with the bodily modification before reactivating the android once the modification complete. Such case as BS-64 Podmoskovye who has been heavily altered in bodily structure to convert from SSBN to a spy submarine stayed in the deactivated period for almost a decade.


kosekframe_by_colorlessocean-dc1j6uk.png

  Weakness/strength by type (ship/aircraft/land)


::STRENGTHS:: 

  • ♦Aircraft -- Highest flexibility and agility among all type (the fighter jets sub-type can even perform somersault or dash at the speed of over 120 km/h even without engines equipped) / easiest to move across the country / the smaller ones are among the lightest in weight (merely over 100 kilograms)
  • ♦Ground androids -- Moderate attacking power and ability to withstand attack from the enemy / relatively easy to move across the country
  • ♦Warship -- Those that use nuclear fuel are among the most fuel efficiency type / the submarine type are among the best in stealth ability / large number of weapons especially the missiles

::WEAKNESSES::

  • ♦Aircraft -- Inflicting the lightest damaging power among the all three types / cannot swim so falling in water most likely resulting in being written off / vulnerable to direct hit attack / very limited amount of weapon
  • ♦Ground androids -- Those with more weight tend to have balance issue / cannot swim so falling in water most likely resulting in being written off / limited amount of weapons
  • ♦Warship -- The most difficult type of move from one point to other, as leaving them on land for an extended period will make them lose their sense of balancing themselves above water (so mostly they can only move from point A to point B through water only) / low agility and flexibility in comparison to the other two types (the submarine type has significant difficulty with jumping)


kommunaframe_by_colorlessocean-dc1j67j.p

  Aging

          For the androids, their 'aging' is more in the sense of 'object aging', not biologically aging like humans. However, as years pass, they'll gradually become less young than their initial look (equivalent to humans in their early 20's) because in each repair and modernization they receive during their lifespan, the engineers will slowly 'add up' age to their appearance, as not to raise suspicion among non-military humans and enemy which will eventually lead to the discovery that which personnel is androids as oppose to ordinary humans.

          Even so, the 'age' which is added to their outer appearance isn't always matching their actual age; TK-208 Smitry Donskoy even though has been commissioned in 1981, still looks to be in the late 30's to 40 range, despite if his years of serving adding to the initial age of 20 will make him fitting to be in 50's range of human's year.


sevaframe_by_colorlessocean-dc1j5qd.png

  'Emergency control password'

               'Emergency control password' is a method to utilize when an android refuses to comply with the order. Each warship android will have their very own 'secret' password which once spoken in the range where the hearing sense of the android can pick the word up, will be able to seize up the control over the android from his own free will. The android then will enter the state similar to being paralyzed, losing control over his own body and his hearing sense will immediately shut down for the duration of a few minutes. During this time the inorganic brain of the android will lose it ability to asset the information from various sensory data gathering method (hearing and seeing) to prevent them from being able to read lips and guess their own 'emergency password'. Also, when the password triggers the control seizing, the inorganic brain will automatically erase all memories gained within the duration of five minutes before and after the password being received.

                When control is seized, humans then able to issue order for the android to carry out, prioritize that order over everything. The examples of this usage of 'emergency control password' were when Admiral Kuznetsov and Admiral Panteleyev both refused to transfer to their assigned fleets. Triggered by passwords, they eventually went to their designated base without consent.

                Usually, the passwords are kept secret from all armament androids. In an unusual case when the password for one android is utilized in the presence of another android, the 'witness' android will later be triggered by his own password and ordered to erase the memory of the period when he witnessed the usage of password on another android clean. In the plot, even the high ranked commanders in the army don't necessarily know all the passwords for every android serving in the Russian arm forces. Only a couple of OCs have the extensive knowledge of passwords for the androids; Zinaida knows all passwords for her 'submarine children' and Major General Aleksandr Linkonovskiy - the specialist coordinator on overseeing the armament androids who knows passwords for every armament android existing in this plot.




  IN-DEPTH GEOGRAPHY AND STRUCTURE EXPLANATION  

levframe_by_colorlessocean-dc1j7bh.png


  Differences between fleets and responsible patrol range

               Because the naval androids have a more complicated restriction regarding moving across the country, they are assigned to permanent bases while the aircraft and 'ground' androids tend to move around a lot. The map below shows the basis of bases of all five fleets and major shipyards nearby, which are the 'birthplaces' of most warship androids.

mainmap_by_colorlessocean-dc1ip9a.png


petyaframe_by_colorlessocean-dc1j6dw.pngFocus on :: Northern Fleet

Flagship - project 1144 Orlan 'Pyotr Velikiy'

northern_by_colorlessocean-dc1ispm.png

               The Northern fleet is the largest and most powerful out of the five fleets of Russian Navy. Currently, they host the sole vessel with the capability to operate aircraft as main offensive tactic - the flagship of Russian Navy, Admiral Flota Sovetskogo Soyuza Kuznetsov. Also the other unique vessel is the only nuclear powered surface ship, Pyotr Velikiy who serves as the fleet flagship.


     ►Responsible patrolling area -- Most of the northern seas bordering Russian arctic region (Barents Sea / White Sea / Kara Sea / Laptaev Sea / East Siberia Sea), North Atlantic and occasionally operate in the Mediterranean Sea.

     ►Headquarter, bases and facilities -- The biggest base and the fleet HQ is in Severomorsk, Murmansk Oblast. Most active ships serving this fleet are stationed here, except for Admiral Kuznetsov who is in Murmansk, the main administrative center of the region 30 kilometers down south of Severomorsk. The smaller 'White Sea Base' is located in Severodvinsk of Akhangelsk oblast, where the major shipyard/repair center 'Sevmash' and 'Zvyozdochka' are situated.

     ►Local climate -- Being entirely in the Arctic Circle, they live in a harsh climate where winter lasts from October to mid of June. Although with the presence of Gulf Stream which carries warm-temperature current reaching even the northern Murmansk, those on the Barents Sea rarely find trouble with iced-up sea surface while the freezing surface occurs regularly in the White Sea every winter.


nastyaframe_by_colorlessocean-dc1j6et.pnFocus on :: Baltic Fleet

Flagship - project 956 Sarych 'Nastoychivyy'

baltic_by_colorlessocean-dc1iuxh.png


Zoom on the Gulf of Finland area - Kronstadt and Saint Petersburg

stp_by_colorlessocean-dc3d0is.png


Zoom on Kaliningrad enclave 

kalinin_by_colorlessocean-dc3d1ed.png

               The Baltic Fleet is considered the founding fleet of Russian Navy back in the era of Peter the Great during the early 18th century. They were hit hard by the crisis during the last years of the USSR Now they're relatively small in comparison to all other open-sea type fleets, save for only the Caspian Flotilla. Historically, the fleet is also famous for their strong participation in the Russian Revolution in 1917.


     ►Responsible patrolling area -- The Baltic Sea, sometimes cross into the Atlantic Ocean in joint missions with the Northern Fleet, also make their appearance in the Mediterranean Sea and even cross the Suez Canal to the Red Sea every once in a while.

     ►Headquarter, bases and facilities -- The main HQ is located in Kaliningrad, with the Baltiysk Base hosting the majority of the fleet warships. The Yantar Shipyard in Kaliningrad serves as the facility for androids creation and repair center. For the Gulf of Finland region, Konstradt is a relatively small base in comparison to Baltiysk but here is the location of three important shipyards which are the backbone of warship androids creation for decades.

     ►Local climate -- The Gulf of Finland area is colder and the Baltic Sea here frozen in winter, icebreaker is often required to clear the route for surface ships. The Kaliningrad Oblast is noticeably has a milder winter, though windier, and the sea is accessible all year round being ice-free even in winter.


varyagframe_by_colorlessocean-dc1j4tp.pnFocus on :: Pacific Fleet

Flagship - project 1164 Atlant 'Varyag'

pf_by_colorlessocean-dc1iw0b.png

               The sole fleet on the Asian part of Russia, they used to be the second most powerful fleet among the five, losing only to the Northern Fleet. The same catastrophic period which reduced the Baltic Fleet to a small fleet also diminished the easternmost fleet to less than 1/10 of their strength in the USSR era. They are famous of constantly being exposed to natural disasters that hardly ever happen to other fleets; volcano eruption, earthquakes and though rarely, Tsunami. However, they always strongly reject that Godzilla isn't included in their list of disasters...


     ►Responsible patrolling area -- The entire Pacific Ocean, nonetheless mainly concentrate in the Northern Pacific than the southern part, The Bering Sea, the Chukchi Sea (rarely), the entire Asia-Pacific region (Sea of Japan, Okhotsk Sea, East China Sea, South China Sea and Indian Ocean)

     ►Headquarter, bases and facilities -- The fleet's main HQ is located in Vladivostok, close to the border with China and North Korea. All the surface ships are stationed here along with the small diesel-electric Paltus-class submarines. The major repairing facility of the fleet is the Zvezda Shipyard in Bolshoy Kamen, across the Bay of Ussuriy from Vladivostok. Near the HQ is the small repairing facility 'Dalzavod'. Farther away northern east is the Kamchatka Peninsula, hosting the main base of the nuclear powered submarines division 'Vilyuchinsk'. The main android creation facility in this region is the Amur Shipyard in Komsomolsk-na-Amure, Khabarovsk Krai.

     ►Local climate -- Winter in Vladivostok tends to be dry and rather cold from the Siberian high pressure, while in Kamchatka is often hit by winter cyclone which dumps meters of snow several times each winter. The Kamchatka base is also more prone to earthquakes, as the major fault line of Kuril-Kamchatka Trench runs along the southern part of the peninsula. Given such unstable seismic activities, it's little surprise that they also brace themselves for volcano eruptions and sometimes Tsunami warning frequently. With the presence of cold temperature current Oyashio, both bases are troubled by iced-up sea every winter. During summer though, Vladivostok is often becoming foggy and rainy.


slavaframe_by_colorlessocean-dc1j77r.pngFocus on :: Black Sea Fleet

Flagship - project 1164 Atlant 'Moskva'

bs_by_colorlessocean-dc3cufh.png

               Once the most powerful fleet in the Black Sea, the disintegration of the USSR and the creation of Ukrainian Navy following the independence of Ukraine weakened them significantly. Sevastopol on the Crimean Peninsula which served as the main HQ in the USSR era now belongs to Ukraine, and the Russian Black Sea Fleet signed the contract to rent the base from Ukraine. The navies of two nations share the HQs in the same city after the distribution agreement of warship androids on each of them. With the Bosphorus Strait straddling and blocking the clear access to other open seas, they are deemed as being the most difficult to encounter among the four open-sea fleets.


     ►Responsible patrolling area -- Black sea, the Sea of Azov, every now and then granted access to the Mediterranean Sea and very rarely, in part of the Red Sea and the Indian Ocean.

     ►Headquarter, bases and facilities -- Their main HQ still remains in Sevastopol. The newer Novorossiysk Base is gradually being completed but suffering trouble with fierce wind along the eastern coast of Black Sea. Most facilities nowadays are under the supervision of Ukraine - the shipyards in Mykolaiv, and shipyard/repairing centers in both Feodosia and Kerch.

     ►Local climate -- While the winter is mild in temperature, the positive point is balanced by the fierce wind of Black Sea. With the warm, pleasant summer makes the area popular as summer destination. Although rarely occurred, sometime the area can be shaken by a medium earthquake.


tatarframe_by_colorlessocean-dc1j6v5.pngFocus on :: Caspian Flotilla

Flagship - project 1166 Gepard 'Tatarstan'

cas_by_colorlessocean-dc3czdc.png

               The smallest and the lone fleet in a confinement of closed water body. Most ships stationed here are those that are small enough to travel along the rivers, which are the only option for them to access the nearest Sea of Azov through the Don River. Due to the little importance of the Caspian Sea to Russia these days, they lack the deployment of submarines.


     ►Responsible patrolling area -- Caspian Sea

     ►Headquarter, bases and facilities -- The main HQ, along with small base, located in Astrakhan, the administrative center of an oblast of the same name. The major base which hosts the majority of the ship is in Makhachkala, Republic of Dagestan near the border with Azerbaijan.

     ►Local climate -- The uniqueness of local climate for the Caspian Flotilla is the dryness in both winter and summer from aituation in the arid area. Summer is rather hot and winter is very mild, with almost no chance for snow fall. They also suffer from dust particles which is carried over the Caspian Sea from deserts in Kazakhstan and Turkmenistan.


mityaframe_by_colorlessocean-dc1j9gn.png

  Rough timeline


1976 -- Kirov's construction commenced

 |

1977 -- TK-208's construction began / icebreaker Arktika became the first surface vessel to reach the exact northernmost point of North Pole in August

 |

 |

1979 -- The Soviet-Afghan War began in December (**starting point of the economic trouble in the USSR)

 |

1980 -- Kirov was commissioned and started his deployment in the USSR's Navy (**main starting point of the plot)

 |

1981 -- TK-208 and Kulakov were both commissioned and deployed to the Northern Fleet in December.

 |

1982 -- Riga, later Admiral Kuznetsov's construction began / Ka-27 began his deployment on the TAVKR

 |

1983 -- Slava was commissioned and moved to Sevastopol / 'Borislav' had his creation commenced / in September there was a tension between the USSR and US regarding the shoot down of Korean Airline flight 007

 |

1984 -- Severomorsk ammo storage explosion in May

 | 

1985 -- The second Orlan, Frunze, was commissioned and sent to temporarily stay with the Northern Fleet, he was the first person to 'decode' Kirov's strange way of communication and wrote a manual for Kalinin

 |

1986 -- Chernobyl nuclear power plant accident occurred on 26th April / Yuriy Andropov, later Pyotr Velikiy, had his construction started / Marshal Ustinov commissioned and sent Severomorsk

|

1987 -- Three Fregat androids - Admiral Zakharov, Admiral Tributs and Marshal Shaposhnikov transferred to the Pacific Fleet, the latter two began their rivalry

|

1988 -- Peretroika was implemented, leading to the revival of call for independence in many republics within the USSR / Black Sea Bumping Incident which Bezzavetnyy (Ladnyy's older sibling) went to harass the ships of the US Navy in an attempt to drive them off the USSR's territorial water / USSR began to withdraw troops from Afghanistan

|

1989 -- Slava went to participate in the Malta Summit / Kirov went out to the sea for the last time in a failed mission to rescue K-278 Komsomolets / Tbilitsi (Kuznetsov) was launched / Chervona Ukrayna left Mykolaiv for the final time as he was commissioned / Kalinin and TK-20 (the final Akula) arrived to Severomorsk

 |

1990 -- Lithuania, Latvia and Estonia declared independent from the USSR and cutting off Kaliningrad in process / TK-208 was sent back to Severodvinsk for modernization

|

1991 -- Decision to put Kirov to sleep (deactivate him) / Slava headed back to Mykolaiv for scheduled maintenance before Ukraine declared independent in August / a failed coup in Moscow led to the end of the KGB /Kulakov entered a scheduled repair which lasted until 2010 / TK-17 suffered an accident which is the sole case of the entire 941 class / Kuznetsov fled from Ukrainian territory in December / the USSR officially ceased its existence on December 26th 1991

 | 

1992 -- Admiral Zakharov lost in a major fire resulting from accident / Panteleyev attempted his self harm in summer before being sent to Pacific Fleet in December / the disagreement between the newly established Ukrainian Navy and Russian Navy resulted in B-871 Alrosa being held hostage

 |

1993 -- Minsk and Novorossiysk, two TAVKRs serving the Pacific Fleet who also born in Mykolaiv, were both decommissioned

 |

1994 -- Marshal Ustinov went on his final friendly visit trip to the US and Canada before being sent to St. Petersburg for a repair

|

1995 -- Three out of six androids that made up the original members of the Russkiye Vityazi aerobatic team perished in an accident in Vietnam.

 |

1996 -- Moskva fled from Mykolaiv and survived being cannibalized to complete 'Borislav' / Chervona Ukraina renamed to Varyag

|

1997 -- Marshal Ustinov returned to active duty

|

1998 -- Pyotr Velikiy was commissioned and arrived in April

|

1999 -- Kuznetsov's incomplete younger brother was sold to China /, Admiral Lazarev was deactivated due to the lack of fund to keep him in operation / Kirov was relocated to Severodvinsk for impending repair

2000 -- Moskva and Varyag became flagships of their respective fleets / K-141 Kursk perished in an accident during a large naval exercise in the Northern Fleet in August

 |

 |

2002 -- TK-208 returned to the Russian Navy as a test bed for Bulava missiles / TK-20 Severstal was pulled out of active duty

 |

 |

 |

2005 -- Sidor fell into the sea for the first time

 |

 |

 |

2010 -- The Vostok 2010 naval exercise hosted by the PF saw both Moskva and Pyotr Velikiy visited Vladivostok for the first time / Russia and Ukraine entered negotiation over the fate of 'Borislav' but no agreement was made 

 |

2011 -- After years of modification and reconstruction, the second project 1143.5 was completed as CV-16 Liaoning.

 |

2012 -- Liaoning was commissioned into the Chinese Navy as the prototype aircraft carrier

 |

 |

 |

 |

2017 -- 'Borislav' was demilitarized in March, losing his immunity and eventually entered the disposal process at last


  AU Plots   

               These AU plots present either alternated details in the timeline or tweak in characters' concept for entertaining purpose (i.e. - 'what ifs' scenario and changing physical appearance according to age). As of February 2018, there are two AU plot ideas:

  •       ► Slava 3+1 :: focuses on the scenario if the negotiation between Ukraine and Russia regarding the future of the fourth Atlant cruiser was agreed and 'Borislav' was sold to Russia. Certainly the main alternated settling of the entire project won't change in this AU thus there will 100% never be a plot about the conflict between Russia and Ukraine. Such scenario of 'Borislav' returned to Ukraine to aid Russian side like Moskva in the real life is not going to happen.
  •      ► Daycare AU :: focuses on 'what if androids, before their deployment in army, actually 'born' in a shape of little boy?'. Mainly the plot will roll along the line of 'how the older androids are going to deal with looking after the kids' and not concentrate on the violent side of their existence (using armament and such). This Au will ignore the timeline from the actual history above in order to create situations to maximize the entertainment aspect (i.e. - Kirov is alive and well even to the period when both K-141 Kursk and K-150 Tomsk arrive in the Northern Fleet).


sashkaframe_by_colorlessocean-dc1j9lx.pn

  Code of conduct for androids

          Warfare androids are kept away from coming into contact with civilians outside of military settlement on regular basis except in a special occasion which they're being the centerpiece of showcase like airshow, military parade, friendly visit to foreign countries and such. Although mainly the androids are instructed to be friendly toward humans, there are still a few restrictions on how far they can form a connection with humans.


  •      They are not allowed to use physical force to harm humans at any circumstance, even to protect themselves -- As normal pistol or revolver firearms can't inflict any physical damage to them, they're mostly immune to physical assault by ordinary humans, whom in most cases don't possess any more destructive weapons than those. Under such circumstance, androids are instructed to always leave the humans without initiating any physical contact with them. At most all they can do is restraint the human, in case one doing something which endangers the base or other people, from running away or causing anymore damage.
  •      They are not to form any relationship with humans past the friend level --Being overly attached to mortals like humans is believed to lower the capability of rational judgement in emergency situations. Therefore, androids are ordered to keep their connection with humans on casual level and always prioritize the protection of the territory of state over humans they're familiar with, even if those are their own commanders.
  •      In case that some contact with non-military personnel humans is needed, they must never let out a clue that they're non-human -- Sometime they're allowed to make contact with civilians near the base like grocery shopping or observing some festivities to learn more about humans. This rule is less strict on androids whose base is located within closed military settlement, whose population is rather familiar with the presence of the androids, which normally does not grant access to even Russian citizens who have no military connection, let alone foreigners. For those whose base located in 'open city' like the Pacific Fleet HQ in Vladivostok, the androids are required to be more cautious to interact with civilians.
  •      Self-defense using their weapons, even for the 'light' ones like AK-630, needed authorization from human commanders -- This extreme case is only when they're ambushed by organized crime gangs using warfare weapons like machine gun, rocket launcher, etc. -  many of which aimed to obtain some of the androids in working condition to further their illegal arm dealing scheme.

Comments


So much info! Love how detailed everything is, I gotta sit down and read all of it sometime.   

          Thank you :) It's a relieve to finally push this out since the old version lacks so many info. If any part doesn't make sense, please let me know! 

Will do!

Oh and since I am currently totally obsessed with it, have you tried WorldAnvil? It's a relatively new website that is perfect for organizing and sharing worldbuilding stuff in a sort of Wikipedia-like documentation. With the amount of worldbuilding you've done here I think it would maybe be handy for you.

           Not yet, but I have checked it out a bit after you've mentioned it in your bulletin. I guess I'll see what kind of attitude that community has before joining, since the setting of my OCs could be quite troublesome if people do not understand that it doesn't directly link to the current conflicts in Syria and Ukraine. Admittedly, I'm rather paranoid about being dragged into politics debates. It took me a few months before finally joining TH after someone first introduced this site to me because I wasn't sure if the real world-based setting will get me in trouble.   

Oh, I don't think people would engage you there tbh. I mean, first of all there are no forums or anything (yet?) and from what I can tell, all the community building happens on their discord server which has 2k+ people. I checked it and it seemed like a really friendly and accepting place. Especially if you put up a disclaimer or something, you should be fine. 

If you do end up joining make sure to link me to your profile so I can follow you!

          Thank you so much for the advice! I'll see what I can do. The thought of building everything from scratch again, just what I have been doing here on TH and pretty much abandon the progress on the my original dA account, surely tires me out a bit just to think about it.   

3 Replies