013!

Ophiuchus and White were in one of the buildings of the facility near the beach, immersed in frenetic activity. The room was filled with control panels, tangled cables, and disassembled equipment. The constant sound resulting from their interaction with the panels and electronic devices filled the air, creating an atmosphere of intense concentration.

Ophiuchus was immersed in the task of optimizing the system for the Operators. His agile fingers danced across the panels, adjusting parameters, reviewing algorithms, and optimizing communication protocols. Each action had a clear purpose, and every decision was made with precision.

Beside him, White demonstrated her skill in coding communication systems and interactions between units. Her green eyes fixed on the screen in front of her, she typed with agility, crafting complex instructions for Ophiuchus. Each line of code was a crucial link in the network they were weaving, connecting the puzzle pieces to create a cohesive and efficient system.

The Operators were scattered throughout the room, each interacting with the panels in front of them. Their voices blended into a constant murmur of analysis and suggestions. The room seemed alive, pulsating with energy and the minds that would operate it.

For the first time in many years, the Operators displayed expressions of contentment. Subtle smiles played on their lips, and a glint of excitement lit up their eyes. The opportunity to assist a human was a source of pride and motivation.

As Ophiuchus continued to adjust the system's parameters, a soft sound caught his attention. His keen ears identified the distant tinkling of bells echoing through the air. He momentarily diverted his gaze and spotted a familiar figure approaching rapidly. Astrid, with her translucent wings fluttering frantically, flew towards him.

With a quick and precise gesture, Ophiuchus extended his arms and caught Astrid in mid-air. He held her gently, allowing her wings to gradually calm down. "I told you I'd be fine," he said with a warm smile.

Astrid's wings continued to emit the soft sound of bells, an echo of the agitation she was feeling. Ophiuchus observed her tenderly, recognizing the effort she had made. "Congratulations on your progress," he praised, his voice filled with genuine appreciation.

However, Astrid seemed frustrated with Ophiuchus's attempt to divert her from her indignation. She impatiently flapped her wings, her eyes fixed on the panels and the Operators who were working tirelessly.

Ophiuchus refocused his attention on the displayed data. "I could feel them, like you did," he confidently inquired, initiating a conversation with Astrid as he continued to adjust the system. His voice flowed smoothly, like a melody accompanying his interaction with the panels.

The fairy finally landed on one of the nearby tables, curiously looking at the numbers and graphs displayed. The Operators watched the scene with interest, a mixture of surprise and curiosity reflected on their faces.

White, who was immersed in coding, briefly lifted her eyes and observed the interaction between Ophiuchus and Astrid. A look of surprise crossed her eyes as she admired the multitasking ability he was displaying. She couldn't help but feel a sense of pride in working alongside him.

Minutes passed, and finally, the system was complete. The Operators, now seated in their chairs, began interacting with the system, testing its functionalities and looking for possible flaws.

One of the Operators raised her hand to get attention.

White responded promptly, "Yes, 6O."

The Operator's voice resonated in the room, carrying an expectant tone. "We need means to communicate more efficiently and in real-time."

Ophiuchus, who was standing beside White, nodded in understanding. "I understand. For now, we can use short-range devices that allow real-time data transmission. Although data encryption is not an immediate concern, we will need to address that issue in the future."

Operator 6O nodded, satisfied with the response. She understood the complexity of the demands and the importance of ensuring secure communication.

...

The organizational classification of YoRHa unit androids was simple:

A - Attacker: specialized in close combat, with exceptional running abilities and an experimental "berserk mode" ("mode B") used only in this variant. Obsolete but known to have been present among the YoRHa android prototypes deployed during the Pearl Harbor Descent.

B - Battler: all-purpose combat unit, a hybrid of prototype models A and G.

D - Defender: focused on defensive tactics such as the use of barriers, and heavily fortified against the Logic Virus.

E - Executioner: combat model designed specifically for anti-android operations. Model E units are often secretly deployed and given another type designation, tasked with monitoring and, if necessary, eliminating androids who have violated YoRHa policies in some way, including those at risk of desertion or in unauthorized possession of classified information. Model E units are functionally similar to model B, regardless of their designation.

G - Gunner: specialized in long-range combat, equipped with an advanced assault rifle model but did not carry melee combat weapons. Obsolete but known to have been present among the YoRHa android prototypes deployed during the Pearl Harbor Descent.

H - Healer: specialized repair unit, with additional tools for both physical damage repair and data corruption and electronic warfare handling.

O - Operator: logistical model, providing information and missions to field units, as well as collecting and compiling command-level data for operations. The O series was not designed for combat.

S - Scanner: reconnaissance unit with additional sensor capabilities and a comprehensive set of hackers for data collection. Model S units are particularly unique, being the only currently produced male YoRHa androids, due to tests finding that male combat-focused models were stronger but poor in cooperation.

...

According to the data presented by White, there were a total of 210 YoRHa units in the city:

B: 90 D: 30 E: 30 H: 30 O: 15 S: 15

However, Ophiuchus was going to reactivate units A and G. Previously, the standard team composition consisted of 1 Defender, 3 Battlers, 1 Healer, and the last member could vary between an Executioner or a Scanner. With the data from the YoRHa prototypes, Ophiuchus was confident in adapting the new units.

Devola, Popola, and White were part of the project. During this period, the upgrade of the units was occurring constantly. Each awakened unit would get accustomed to their new roles, now that they had organs and physiological needs. They also underwent practical combat training.

In the current composition, there were a total of 30 fully functional teams. However, with the reactivation of two 'new' units, this number increased. Ophiuchus designated them as an extermination team: 1 Attacker, 2 Gunners, 1 Healer, and 1 Executioner. In this configuration, the Executioner would function as a Battler, capable of switching between A and G.

Therefore, Ophiuchus worked even harder on the recovery of units that had been neutralized, corrupted, or had deserted. His task had become more manageable with the assistance of the H units, operating in the Cradle, expediting the development process in the recovery, verification, and data assimilation stages. Additionally, White had brought backup data for units that had been deactivated over time.