Kovacs stood at the center of the workshop, the low hum of machines and the buzz of focused engineers filling the air. Permission had come through from the general, and Kovacs now held access to the enemy mech data—a critical edge in his design process. More than that, the general’s nod of approval had given him an implicit green light to lead, and he didn’t intend to waste it.

One of the senior engineers approached him, a rugged man with a permanently furrowed brow, a few clerks trailing behind him. “Inventory is underway,” the engineer reported his voice a rumble. “I’ve assigned clerks to help catalog the materials, and I’ve got the others starting to sift through schematics to match what we have. Should have a preliminary report soon.”

Kovacs nodded, his mind already spinning with possibilities. “Good work. Let’s keep that momentum up. First, I need a full assessment of our resources—not just raw materials, but every energy source, every specialized machine, and the personnel we have on hand.”

The engineer gave a brisk nod, then turned to relay the instructions to the clerks. As Kovacs watched them disperse, he felt the weight of leadership settled over him, but it brought a strange calm. He was in his element, managing both people and plans.

Once the inventory was underway, Kovacs moved to the next team, already bent over stacks of old blueprints and digital screens displaying schematics. “Find any existing designs compatible with our available resources. We don’t need to reinvent the wheel here. If we have schematics that fit, let’s use them and save ourselves time. Our focus should be speed—anything accelerating this process is a priority.”

The team nodded, some still skeptical but willing to follow his lead. Kovacs glanced at the data on his tablet, a clear breakdown of raw materials, and his mind raced ahead to the next critical phase.

“All right, next order of business: defining the role for these mechs. Before we get into the specifics, we need clarity on our design. Are these scouts, combat units, support?” He looked around at the gathered engineers, who exchanged glances before someone spoke up.

“General Patton mentioned a balanced force—something agile enough to outmaneuver the enemy but with enough firepower to take a hit.”

Kovacs nodded thoughtfully. “So we’re looking at multipurpose combat units, something versatile enough to adapt on the field. That means setting parameters for weight, speed, armor, and weaponry right out of the gate.” He tapped on his tablet, creating a rough outline. “Let’s keep our weight low to maintain mobility, but prioritize armor plating on key areas like the cockpit and power systems. Weaponry will need to be both effective and light.”

Moving on, he took a deep breath and looked at the team. “Let’s start design work with mobility as the priority. We need an engine capable of supporting fast maneuvers without compromising on power. Once we have that, we’ll set tonnage limits to keep these units light enough to be quick on their feet.”

As the engineers began discussing engine options, Kovacs pulled up the preliminary blueprints and tapped through rough simulations, testing theoretical configurations. The screens displayed early estimates, showing stress points and power distributions. Occasionally, he’d adjust a parameter and rerun a simulation, watching the specs inch closer to the numbers he wanted.

Finally, he addressed the team one last time, a slight hint of determination breaking through his usual reserve. “Based on what we’re seeing, I’d estimate a build time of one day per 10 tons, thanks to our 3D printers. Those will handle most of the part creation and assembly, but we must account for real-time adjustments and fixes along the way.”

The engineers exchanged glances, nodding in agreement. One spoke up, an experienced designer working in the field longer than most. “If we keep everything streamlined, this could work, Kovacs.”

Kovacs gave a slight smile, the first since he’d started. “It will work. This is the Crucible—we’re not just building mechs here. We’re building an edge.” He took a last look at the team, catching Jackie’s approving nod from across the room, and set his focus back on the task ahead. There was no turning back now.

Kovacs pulled Jackie aside, finding a quieter corner away from the bustle of the workshop. He needed insight into the pilots’ needs directly from someone sitting behind the controls, not just from spec sheets and reports. Jackie leaned against the wall, arms crossed, watching him with a curious smile as if amused by his sudden focus.

“Jackie,” he started, pulling up his tablet, “I need to know exactly what you and the other pilots are looking for in these mechs. Specs are one thing, but you’re taking these into combat. I need to hear it from you—what do you need?”

She tilted her head, considering. “First thing’s first, we need speed. Mobility is critical. We're dead in the water if we can’t outmaneuver enemy mechs. I’m talking fast, responsive movement—letting us dodge or close in when needed. Think of it like a boxer; we want to slip and strike, not just take punches.”

Kovacs nodded, jotting down notes. “Makes sense. Agility is priority number one, then. That lines up with what I was thinking. And for weaponry?”

The author's tale has been misappropriated; report any instances of this story on Amazon.

Jackie’s eyes gleamed. “We’re looking for versatility. It’s not just about having heavy firepower; we need systems to handle different situations. Ideally, each mech has a mix that packs a punch and options for longer-range engagements. And redundancy would be good, too. Nothing is worse than having your main weapon jammed in a fight.”

Kovacs scribbled that down as well, nodding. “We’ll need to design for weapon loadouts that allow for short- and long-range switching as needed. I’ll make sure there’s a backup for the primary weapons.”

Jackie leaned forward, clearly warming up to the conversation. “Armor is another big one. We know these things must stay light for speed, but we won’t last long without solid protection around key systems—cockpit, power source, and critical circuitry. We don’t need to be invincible, but the right protection in the right places would make a huge difference.”

Kovacs looked up, meeting her gaze. “I’ve been thinking about that. I’ll prioritize the armor plating around critical areas and make it modular so we can adjust coverage depending on mission requirements.”

Jackie grinned, clearly pleased. “Now you’re talking. Another thing—the HUD and control systems. Some of the older units we’ve been in, it’s like piloting blind. We need visibility in terms of sensor range and how clear the HUD is. When we’re in the thick of it, split-second decisions matter. The clearer the data, the faster we react.”

“Got it,” he replied, making a note to talk to the team working on the communications and control systems. “I’ll make sure the HUD’s optimized, with priority for real-time data processing and minimized clutter.”

Jackie seemed thoughtful for a moment. “And one last thing, Kovacs—reliability. Some of these mechs break down if you so much as look at them wrong. I need something durable that can take a bit of a beating without me having to worry if it’ll make it through the next engagement.”

Kovacs felt a grin forming. “You want it fast, strong, and unbreakable. Got it. I’ll see what I can do to balance durability with the rest. Anything else?”

She shrugged, though her eyes sparkled with humor and appreciation. “You give us those things, and the pilots will be behind you. We just need to know you’re thinking about us when you’re back here in Forge, designing. It’s our lives out there, and we feel every piece you put into these mechs.”

Kovacs nodded, closing his notes with a determined look. “Thanks. This helps a lot. I’ll keep you and the others in mind every step of the way. When we’re done, these won’t just be mechs—they’ll be machines you can trust.”

Jackie gave him a firm pat on the shoulder.

***

Kovacs called the engineers into a briefing room, pulling up the data and whatever footage they had on the enemy mechs. He wanted every set of eyes focused, every mind analyzing. They had only a limited view into what they were up against, but any edge, however small, could prove invaluable.

He dimmed the lights as the first video began to play on the screen. Grainy footage captured from afar showed enemy mechs moving through a battlefield. The images flickered and shook, but the basic outline and gait of each mech were visible.

“All right,” Kovacs began, his voice steady. “Let’s treat this like a field autopsy. We’re looking for any identifiable weak points—structural vulnerabilities, power imbalances, anything that could be exploited. I want to know where these things are tough and brittle.”

One engineer leaned forward, studying the screen intently. “Look at how the joints move. They’re reinforced but look a little bulkier than they need to be. I’m guessing that’s added armor, but that also means more weight, which could affect speed.”

Kovacs nodded. “Good eye. Extra weight around the joints could be a strain on their movement. If they’re slower to pivot or sidestep, we can capitalize on that.”

Another engineer pointed to a section of the footage showing a mech stumbling over rough terrain. “It looks like they struggle with uneven ground—see that? They’re top-heavy. Probably designed more for open areas, less suited for close-quarters or rough terrain.”

“That’s promising,” Kovacs replied, taking notes. “We can use terrain to our advantage, force them into environments where they’re at a disadvantage.”

The footage continued to play, revealing an enemy mech firing its weapons. The muzzle flashes illuminated the surrounding area, showing recoil that seemed to rock the mech backward. One of the younger engineers squinted at the screen, then tapped Kovacs on the arm.

“Look at the recoil. It seems excessive—almost like they didn’t balance the weapon system properly with the mech’s center of gravity. It’s powerful, but each shot could throw them off-balance.”

Kovacs grinned. “So they’ve got firepower, but it’s overloading their stability. They might destabilize themselves if we can force them into a rapid-fire situation. Good catch.”

As they moved through the footage, the team pointed out various other observations—weak armor near the cooling vents, exposed joints on the rear legs, and communication antennas that seemed vulnerable to even minor impacts. The mechs were formidable, but their design leaned toward offense over balance, trading agility for armor and firepower.

After the last clip ended, Kovacs turned to the team. “Based on what we’ve seen, we’ll design to counteract these weaknesses. Here’s what I’m thinking so far.”

He pulled up the list of priorities he’d already discussed with Jackie. “Our units must stay fast, mobile, and adaptable to all terrains. We’ll keep our armor lightweight but focused on critical systems. That means we prioritize cockpit protection, power sources, and communication systems without weighing down the entire frame.”

An older engineer, who’d been listening intently, added, “And if we build in a recoil-absorbing mechanism, we can fire faster without losing balance. Their firepower won’t mean much if we can outmaneuver and outshoot them.”

Kovacs nodded. “Exactly. We can also reinforce the joints without sacrificing speed. If we keep them light enough, they should be able to slip around the enemy and stay in constant motion. We won’t match their firepower head-on, but we won’t need to. Agility will be our advantage.”

The team murmured in agreement, some engineers jotting down schematics ideas. Kovacs looked around, a spark of determination in his eyes.

“Let’s get to work, then. We know their strengths and weaknesses—and now, we build a mecha that can exploit them.”