Gap Stories #14

[Mech Management]

Log Date: 9/1/12768

Data Sources: Sunthorn Bastion Archived Records

Sunthorn Bastion Titan Protocols

Designation Rules for Assets, Contacts, and Active Operations

All Titan pilots are to be given a numerical designator that corresponds to the order in which they were first deployed as a Valiant Titan pilot. This numerical designator starts at 00, and proceeds upwards, adding an additional digits as needed. An example is provided below:

00: Renchiko Chamako

01: Feroce Acceso

02: Kiwi

When deployed in an active operation, individual pilots are to be referred to by their numerical designators for ease of tracking. When speaking to the pilot, you may use their name, but when speaking about the pilot, they are to be referred to as their designator — Zero-Zero, Zero-One, Zero-Two, etc etc. This is for ease of reference in the operations center, since pilots are displayed according to their numerical designators on the vast majority of system displays.

For enemy contacts, a letter and a number are assigned for the nine largest contacts on the field. The letter is determined by the class of the largest Leviathan on the field, with the number starting at 1 for the first contact and proceeding from there, in order of largest to smallest. As an example, in an operation with Leviathans in the Koiyash, Talingrad, Coreolis, and Hakos classes, the naming convention would start with K1 for the largest Leviathan. The next-largest Leviathan would be K2, and the third largest K3, and so on and so forth.

In the event a Leviathan survives an operation and returns in future operations, the Leviathan is to be given a unique designator. This designator will be determined by the vote of the operations crew, who will put forward candidate names based off their tactical observations of the Leviathan. The candidate name with the most votes will be assigned as the Leviathan’s designator. In the event of a tie, pilots deployed during the operation will be asked to cast their votes as tiebreakers. If the vote is still tied after that, the hangar crew will then be allowed to cast votes as tiebreakers.

Candidate names should reflect the gravity of the matter. Suggestions such as “Dickhead” and “Cheeky Bastard”, while they may technically be accurate descriptors of the Leviathan’s behavior, will be disqualified in favor of more dignified suggestions.

Titan Profile: Firefly II

Summary Sheet

Name: Firefly II

Form Factor: Titan

Model: Custom Challenger Build

Assembly/Year: Sunthorn Titan Hangar, 12748

Control: Solo Pilot, Manual Control

Height: 112 feet

Weight: 26,921 tons

Core: T94 ‘Spitfire’ Fusion Core from Kaneko Industries

Armor: Quadranium Shell with Feisofawx backing layer for kinetic absorption

Movement Assist: Kaneko Industries ‘Pirouette’ RCS

Armament:

• Sunthorn Foundry ‘Sunthorns’ — Twin Tonfa Lances with Plasma Conduction Veins
• Viralis Industries ‘Surreptitious’ — Compact/Concealed Trifold Wrist-Mounted Sequential Plasma Repeater
• Krigstein Designs ‘Arrestor’ — Mortar Pistol
• Krigstein Designs ‘Rechetta’ — Short Knife with Serrated Backblade

Computer Array: Talin-Systems CB8 Distributed

Computer OS: Sybione Softworks ICP version 27.4.828

Sensors: Starcomm Inc. ‘Hawkeye’ sensorcomms bundle

Comms: Starcomm Inc. ‘Hawkeye’ sensorcomms bundle

Titan Piloting: Rookie Handbook

Chapter 6.5: Sync Rate

Now, if you happen to be an empath pilot, the startup process is a little more complicated than plugging in and hitting the power button. Empath pilots have to pilot in pairs, which means that piloting your Titan is a team effort — and if you can’t work together with your copilot, you’re going to have a hard time.

Pilot compatibility is measured by SYNC RATE, which tracks how closely empath pilots match and mirror each other’s neurological activity. When you’re looking at cranial maps for paired empath pilots, the neurological activity on both maps should be indistinguishable. When it comes to the numbers, the sync rate should be at least 82%, which is known as the startup threshold. If a pair of empath pilots can’t reach the startup threshold, most Titans with an empath configuration won’t start up. After startup, the sync rate has to remain above 73%, which is know as the operational threshold. Copilots that drop beneath the operational threshold ‘crash out’ — they lose control of their mech because they can no longer effectively divide the neurological load needed to sustain the mech’s operation, and the safety shutoff kicks in to prevent brain damage to one or both pilots.

Lots of things can affect sync rate, so it’s important to be mindful of those things and make sure you’re getting in the right headspace before you jump in the pilot chamber! Animosity between pilots is a big one — if you’re fighting with your copilot or resentful of them, then your sync rate is probably going to take a hit. Staying on good terms with your copilot is important — you never know when you might need to sortie at a moment’s notice!

Something else that can affect your sync rate are distractions and personal concerns. These things can bleed over the connection to your copilot, likewise distracting them and making it hard for them to focus as well. When you step into the pilot chamber, it’s important that you leave all of that behind — empty your mind, and leave behind any personal problems or struggles. All of your focus should be on your mission — put the rest of your life in a box and set it aside until you leave the pilot chamber again.

Food also plays and important part in pilot concentration — it’s hard to focus when you’re hungry! Eating healthy meals will keep you in good condition, and if you don’t have time for that, grabbing a snack can keep the munchies from eating into your focus instead.

If you know that a mission’s coming up, then something that can also help beforehand are sleep and meditation! Sleep obviously refreshes the mind and body, and so long as you wake up at least an hour before you have to hop in the pilot chamber, you should be awake and alert enough to run your mission. Meditation has also proven effective for empath pilots, allowing them to clear their minds and ready themselves for the rigors of empath piloting. Some psion pilots in the Marshy Republic even have a special battle meditation routine they undergo before every planned deployment!

And finally, there are some rumors that LOVE helps improve the sync rate for paired pilots! This hasn’t been studied very much, but there have been some cases where paired pilots that were in a relationship with each other had higher sync rates on average than other paired pilots. Of course, we don’t recommend that you try to fall in love with your copilot, but statistically, it seems to happen more often among empath pilots — after all, you get to know someone pretty well when the two of you spend a lot of time in each other’s heads!

SHOC Records

After-Action Report 8/30/12768

Filed by: Koriah Nagatain

Operation primary objectives met? [Yes]

Operation secondary objectives met? [No]

Operational costs (only list the costs that exceeded the pre-battle estimations):

• 2 damaged Titans
• light repairs for the Firefly II
• medium repairs for the Torikago

If there were any enemy forces deployed, briefly elaborate on the status of those forces in the aftermath of the operation:

• 2 of 3 Leviathans defeated, the last one escaped. We expect it will return after some time to recover and evolve. After taking suggestions and a vote, the operations crew has settled on the designation ‘Tantrum’ for this Leviathan.

Complications encountered in this operation, if any:

• Split command. We were under the impression that the entire squad would be under our command, but the Genista Titans received conflicting orders from the Genista outpost. This threatened the success of the operation and resulted in substantial damage to both our assets and theirs, and forced the deployment of an asset that was neither battle-tested nor ready (the Torikago).
• Genista pilots are inexperienced. They have been trained to a certain level, and clearly have discipline, but they lack real combat experience. As a result, they are less effective, and need the direction of a more experienced pilot to form an effective unit on the battlefield.

Intelligence gained from this operation, if any:

• Deployed Leviathans might not fight to the death. It is unclear what will prompt them to retreat, but it seems they will pull back in certain conditions, instead of pushing the assault until they are killed.
• The Genista outpost is utilizing underage empath pilots, in violation of the Titan Accords that the major nations are signatories to. We have not yet reported this to the Colloquium, and Valiant Command is still debating what to do with this information.
• Kiwi can serve as an empath pilot so long as she is paired with Songbird. She has no training, but has an exceptionally high sync rate when paired with him. Since we don’t have any other empath pilots in the Valiant, we don’t have a way of testing whether she is compatible with other pilots, or just Songbird.

Conclusions:

• Operation was a success but came at a heavy maintenance cost. The hangar crew is rushing to get repairs underway so the Firefly II and the Torikago can be ready for the next operation.
• Split command is not sustainable. The success of this operation was jeopardized by conflicting orders from the Genista outpost. Any future operations need to be run under a unified command for the entire squad, and the Valiant should be that command, since we have more combat experience and tactical expertise.

Titan Profile: Genista Squad

Summary Sheet

Name: Genista 1-5

Form Factor: Titan

Model: Halcyon Test Frame (MK-0.8)

Assembly/Year: Genista Titan Yard, 12763

Control: Dual Pilot, Empath Control

Height: 130 feet

Weight: 32,341 tons

Core: T101 ‘Warden’ Fusion Core from Kaneko Industries 

Armor: Quadranium ‘Healing’ Shell with experimental nanite repair reserves

Movement Assist: Anamarat Engineering ‘Hummingbird’ RCS

Armament:

• Garnier Labs ‘Arclance’ — Bladed Spear with Electrical Conduction
• Garnier Labs ‘Striker’ — Particle Pulse Rifle
• Garnier Labs ‘Filet’ — Long Knife with Plasma Edge
• Garnier Labs ‘Denouement’ — Rib-Mounted Internal High-Yield Missile Racks

Computer Array: Praelion Electronics CB19 Centralized

Computer OS: Sybione Softworks ICP version 27.6.854

Sensors: Starcomm Inc. ‘Gryffin’ sensorcomms bundle

Comms: Starcomm Inc. ‘Gryffin’ sensorcomms bundle

Excerpt from the Titan Accords

Chapter Regarding Underage Pilots and Genetically Designed Pilots

Section 44 — Age of Pilots

1. Due to the adverse effects that mech piloting has on the physical and psychological development of juveniles, all active pilots are required be 18 years of age or older. Any program or government that is found responsible for fielding underage pilots will be subject to punishments including, but not limited to: fines and sanctions; revocation of certification or license; freezing of assets; and prison for the responsible officials.

1a. In the case of races that age more slowly, the age requirement is adjusted to the number of years that would be equivalent to the age of 18 in a human. See the age equivalence table in Appendix E for further guidance on age thresholds for each species.

1b. The Venusian Colonies are hereby exempted from pilot age restrictions due to the cultural importance of Titan piloting on the Venusian frontier, as per the agreement reached during conference negotiations.

2. Pilots between the ages of 18 - 25 are governed by the following restrictions:

2a. They are not permitted to log more than 720 combat hours in a mech, and are not permitted to log more than 2160 training hours in a mech.

2a.1. Combat time exceptions may be made in the case of emergencies, such as planetary defense, and only if no other pilot alternatives are available.

2b. Hexannual health and psychological assessments will be required for all certified pilots under the age of 25. Pilots that fail their assessments will be benched and may not pilot for 30 days. After 30 days, they may be assessed again to see if they qualify for a return to active service.

2b.1. Exceptions may be made in the case of emergencies, such as planetary defense, and only if no other pilot alternatives are available.

2c. In two-seat configurations, pilots that are between the ages of 18 - 25 must take the second seat, with the older pilot taking the lead seat.

2c.1. If both pilots are below the age of 25, then the older of the two is to be given the lead seat.

Section 45 — Genetically Designed Pilots

1. In accordance with the Laiquedux Convention on Sapient Rights, it is illegal to genetically design an embryo for the express purpose of raising it to be a mech pilot. Any program or government that is found to have done so will be subject to the sanctions outlined in the LCSR, in addition to, but not limited to, the following punishments: fines and sanctions; revocation of certification or licensing; freezing of assets; and prison for the responsible officials.

2. In accordance with the Laiquedux Convention on Sapient Rights, it is illegal to genetically modify a minor for the purpose of improving their ability to be a mech pilot. Any program or government that is found to have done so will be subject to the sanctions outlined in the LCSR, in addition to, but not limited to, the following punishments: fines and sanctions; revocation of certification or licensing; freezing of assets; and prison for the responsible officials.

3. Genetically designed pilots are permitted under the following conditions:

3a. If the pilot received the modification at or after the age of 18.

3b. If the modification provided during gestation or minor years was for a purpose other than enabling a career as a mech pilot.

4. Pilots are required to provide a full genetic profile, along with all records of any genetic modifications, when submitting their full medical history to their employer.

Titan Profile: Torikago

Summary Sheet

Name: Torikago

Form Factor: Hybriddyr

Model: Void Jaguar (Generation III)

Assembly/Year: Midway Station Assembly Yard, 12747

Control: Dual Pilot, Empath Control

Height: 142 feet

Weight: 36,101 tons

Core: H12 ‘Vanquisher’ Fusion Core with Antimatter Overcharge from Jaeger Shipyards

Armor: Quadranium Shell with reactive segmentation and adjustable configuration

Movement Assist: Midway Labs ‘Twitch’ RCS

Armament:

• Nullus Manufacturing ‘Nuisances’ — Tungsten Carbide retractable claws (Jeger config)
• Viralis Industries ‘Surprises’ — Retractable/Concealed Forearm Blades with Plasma Conduction Veins (Titan config)
• Challenger Labs ‘Siegebreaker’ — Maw-Mounted Pulsar Cannon (Jeger config)

Computer Array: Cheetask Electronics Series 12 Quantumlock Instinctive

Computer OS: MS Solutions ICP version 27.4.703

Sensors: Viktier Industries ‘Demon’s Crown’ sensor suite

Comms: Starfox Systems combat comms bundle

Titan Piloting: Rookie Handbook

Chapter 8: Tips for Battle

So you’ve made it out of the hangar and into the area of operations! Congratulations, you’re on your way to to becoming a successful Titan pilot.

This is where the real challenge begins. You might be piloting the biggest one-man war machine known to the galaxy, but that doesn’t mean you’re invincible! You always have to keep your guard up as a Titan pilot. Enemies will find ways to take you down if you’re not careful, whether it’s through numbers, strength, or cleverness.

Keep in mind the rhyme that every Titan pilot should learn in training! ‘Never stand still. Confirm the kill.’ These are the two most important tips for battle. Stationary targets are easier to hit and easier to plan around. Where it’s possible, you should always stay moving. Never give your enemies an easy target.

The second piece of advice is just as important! Even when you think you’ve defeated an enemy, you should always confirm the kill. Leviathans, and other Titans, with how big they are, often have redundant systems that keep them alive and functioning even when they’ve taken lethal damage. And some of them are just clever and will play dead so they can attack you once you turn your back! So always take the opportunity to confirm the kill — another stab in the neck, another HEAT round in the noggin, just to make sure that your enemy is good and truly dead. It could be the difference between a resounding victory or a humiliating defeat!

Sunthorn Operational Archive

Halcyon Campaign General Assessment (Continuing)

Filed by: Challenger 3055 (Kaiser)

Campaign Location: Halcyon, in the Mistilteinn System

Campaign Length: 3-6 months

Primary Objectives:

• Protect the Genista Research Outpost from Leviathan attacks

Secondary Objectives:

• Train the Genista Titan Squad up to independence
• Help them acquire combat experience without taking losses
• Use the opportunity to help the Valiant’s Titan pilots gain combat experience
• Locate and exterminate the Collective hive established on Halcyon
• Strengthen the Valiant’s relationship with the Marshy Republic

Obstacles:

• Local Titan squad is inexperienced, underage, and very much illegal.
• Outpost leadership is aware of this, and has been withholding critical information and coordination control, likely in an effort to safeguard other damaging information surrounding their test team on Halcyon. If we cannot come to an arrangement with them soon, this may result in strategic collapse on future operations.
• Location of the Collective hive still unknown. Possibly subaquatic, based on the fact that the Leviathans seem to be originating from the ocean. If so, exterminating the hive through conventional methods may be extremely difficult.

Other Observations:

• It is unclear what the Collective is doing here. This is not a full-scale invasion; they have no ships in orbit, have apparently deployed none of their regular forces, and are exclusively utilizing Leviathans for their battles here. Despite the genetic treasure trove that this planet presents, there are no signs of terrassimilation across the surface of the planet. Wherever their hive is, it has been well-hidden.
• The Collective’s only apparent target has been the Genista Research Outpost; therefore, we must conclude that there is something in the outpost which is more valuable than assimilating an entire preserve world. However, the outpost’s leadership are feigning ignorance, saying that they do not know what the Collective are after and why it would warrant this deviation from their typical invasion strategy.
• With the Torikago deployed to the surface alongside the Firefly II, we now have Songbird and Kiwi onsite to further pursue these questions. It will have to be done delicately; all staff we have deployed to the surface have indicated that the Genistans are polite and welcoming, but very evasive on some topics. Given everything we have seen so far, I believe the Marshies might’ve been using the remote and restricted nature of this planet to conduct research that is not compliant with Colloquium laws.