Chain of Command – Snippet 36

Chain of Command – Snippet 36

“How serious was the damage?”

“Cruiser Four-Two-Eight was a total loss, of course, when it exited jump space into a planetoid. A fire lance hit disabled the jump drive of Four-Two-Nine and the captain jettisoned the entire module to avoid contamination. It can maneuver but will use most of its reaction mass to decelerate and return to our fleet rendezvous. It will arrive in twelve days. Five-Two-Two has only intermittent power, has lost its coil gun and most of its sensor array, and is not immediately repairable. Five-Oh-One is lightly damaged and will be operational as soon as we are.”

So–discounting Cruiser Four-Two-Nine, which could not jump and so could not join the other ships in their next attack maneuver–they had only two operational cruisers left, including the flagship. Two ships to face whatever remained of the Human fleet, which included at least two cruisers and three destroyers at K’tok, two cruisers at Mogo, and seven more destroyers unaccounted for. The First Fleet had had fewer ships destroyed, lost fewer lives, than had the enemy, but the balance of force had changed hardly at all. Nuvaash took a breath to steady his voice before speaking.

“The new missiles performed well, Admiral.”

e-Lapeela looked up sharply but Nuvaash met his gaze and after a moment the admiral cocked his head to the side in a shrug.

“We expected to take out every starship. It worked well in testing but the test sequence, for reasons of secrecy, was limited. No weapon ever seems to perform as well in the field as in the tests.  Still, we dealt them a shattering blow: eight ships destroyed versus only one of ours. It may not seem so here, surrounded by casualties and damage, but this was a great victory.”

“But to what end?” Nuvaash said. “They still hold K’tok.”

“To what end? I told you others waited in the shadows to join us. Victories steel their courage, quicken their blood, broaden their vision. Because of this victory–and that is exactly how it will be perceived, regardless of how much damage we sustained–others will join us. First a trickle, but like water cutting a sand bar, a trickle widens the passage and more water follows.

“And I have just received word by jump courier. The government has released the cruiser division on Akaampta from Cottohazz duty to my command, and the Home Fleet is readying another squadron to join us. Our enterprise prospers.”

“Not of the ground, I am afraid,” Nuvaash said. “We are stalemated. Human orbital bombardment has become less effective both in terms of volume and accuracy, and the Human ground forces have taken casualties which they seem unable to replace immediately. These are both fruits, in my opinion, of our earlier attack.  All of our heavy ground force units took severe casualties in the aftermath of the invasion, however, and our three regular mobile cohorts have been rendered ineffective for offensive operations. If we are to resume the ground offensive we must reinforce out ground forces.”

“Reinforce? How?”

“We are receiving three transports from home, carrying between them a reinforced ground brigade. I believe we can land part of a lift cavalry squadron by reentry gliders.”

“Reentry gliders?” the admiral demanded. “While the Humans hold orbital space? That would be suicidal for the transports.”

“If we used the transports, that would be so. But out cruisers have the ability to carry a limited number of reentry gliders in place of external ordnance modules.  The extent to which the detonation of Human nuclear warheads interfered with our sensors during the last attack suggests a way for a ship or two to make a high speed approach and exit, dropping the reinforcements into the atmosphere as we pass.”

“We?” the admiral said.

Nuvaash shifted his position and let his earns fold back slightly in the position of respect.

“As the attack profile I am outlining is hazardous and untested, I assumed the admiral would lead the first raid in the flagship.”

e-Lappela leaned back in this chair and smiled. “I am surprised, Nuvaash. You strike me as cautious rather than aggressive, and yet now you recommend another audacious attack.”

“I recommend nothing, admiral. I only point out the facts as I understand them.”

And one of the facts he understood now was that the admiral was a murderer. But how many supposedly glorious triumphs throughout history, he wondered, were secretly purchased with murder?

*****

Sam glided through the hatch to the wardroom and clipped his tether to end of the main table. No other officers were present and so Sam ordered cheese enchiladas for lunch and prepared to eat alone. That was fine; he had a lot of reading to catch up on.

Second Principle of Naval Leadership: Be technically and tactically proficient.

He put on viewer glasses and started re-reading TM-01 Deep Space Tactical Principles.

After five minutes Lieutenant Rice, the boat’s beefy supply officer appeared, drew a bulb of coffee from the dispenser, and clipped his tether next to Sam’s.

“How’s it going, Moe?” Sam asked, taking off his viewer glasses.

“Not too good, Cap’n. I mean, we’re in good shape, but the grunts down in the dirt are in trouble. With most of the cruisers gone we’ve only got ground bombardment coverage about a third of the time. The uBakai are starting to close in with mobile troops whenever there’s no one in a firing position. For now they’re okay but that Limey battalion is going to run short of ammunition if things heat up much.”

“Ammunition? Don’t they have their fabricators with them?”

“No, sir. The cohort’s fabricator platoon never got down to planet surface. It was going to come down the needle with its gear but was still onboard HMS Furious when the uBakai attack came. That’s the British transport that got nailed.”

“Aren’t there backup British fabricators in the fleet train?”

“There were, sir. They were aboard FS Mistral, the French auxiliary vessel we lost.”

That was a problem, but Sam didn’t see it as insurmountable. He’d spent enough years in the fabricator business to understand their versatility.

“The other two cohorts down there have their own fabricators, right? There’s nothing the Brits need they can’t fabricate for them.”

“Not quite, sir. Seems like no one has the software code to load the output specifications for the British munitions into the US or Indian fabricators. The British cohort HQ has the specs in their tactical data base. They just can’t get the other cohort fabricators to accept it. I talked to the task force N-4 and he says they’re trying to get the go-codes from home by jump courier missile, but they’re still negotiating with the fabricator manufacturers.”

“Who’s that?” Sam asked, but was suddenly reluctant to hear the answer.

“SubcontininenTech made the Indian fabricators, Dynamic Paradigms made the US ones.”

Of course, the company he worked for, squabbling over intellectual property while people’s lives were at stake.

“Okay, keep me apprised, Moe. Any deterioration on the ground, let me know right away.”

Moe raised his eyebrows slightly in surprise, but nodded. Of course he was surprised. Why would a destroyer captain in orbit be this interested in whether or not fabricators were working on the ground?

“Remember, I worked for Dynamic Paradigms until I got activated,” Sam explained. “Professional curiosity.”

It wasn’t the truth, or at least not the entire truth, the important truth, but it satisfied Moe, and for now that was all that mattered. Still, this new wrinkle was one more thing for him to worry about, one more tough call he might have to make fairly soon.

In his seven years at Dynamic Paradigms, he’d done a variety of jobs, but most of his time was spent in the Product Support Division, making sure installed fabricators worked as advertised. Sometimes all the different interfaces got scrambled, the processor locked up, and you had to just reset everything. Even when power was pulled from the unit, even when there was no available interface, the e-synaptic core of the processor was still alive, still barely powered by waste heat generators, waiting for the master cheat code which would reopen the system and let technicians reprogram it.

The code was all but unbreakable, a precise series of signals of different intensities, durations, and at different radio frequencies. But a handful of product support supervisors knew the code, and Sam had eventually been one of them. He knew the code which would unlock the Dynamic Paradigms fabricators in the US Marine cohort’s support platoon and let it accept the production instructions for the British munitions.

The problem was those codes were among the most closely guarded corporate proprietary secrets Dynamic Paradigms had. He had signed more non-disclosure agreements than he could remember. In addition, each code shared with an employee contained one signal sequence which was unique to that employee, so any use of it was immediately traceable. If he revealed that code now he was never going back to his old job, or any other job for any fabricator firm, or any corporate position anywhere that involved access to proprietary information. He would make himself unemployable, permanently, and in a pretty lousy job market to boot.

But his old company still might come through, do the right thing, and turn over the cheat codes. If not …well, no point in dwelling on that now.

 

This entry was posted in OtherAuthors, Snippets. Bookmark the permalink.

24 Responses to Chain of Command – Snippet 36

  1. Westrim says:

    Maybe it’s because of the snippet format, but I feel acutely aware of every Chekhov’s gun we see getting its hammer cocked, and the fabricator code is yet another one on what is becoming quite the gun rack in this story.

    All this talk of ground combat from both sides makes me interested in a third viewpoint down on the ground. What happened that led to NATO standardization going by the wayside? What are the human colonists on the planet up to?

    • Randomiser says:

      “Some” US president decided NATO was outdated and too expensive?

    • Robert Krawitz says:

      Chekhov’s armory, more like…

    • Richard H says:

      The colonist POV could be interesting, but I have a feeling we’ll never see them. More than any snippet before, K’tok is very obviously Guadalcanal. Forward resupply from warships is fairly distinctive from that.

      It could be interesting to see what the local populace actually thinks of their planet’s primary access to space turning into a war zone, though. I agree.

      • Dave Lachlan says:

        I doubt that the colonists will have any say in any of this.

        I’d love to see a nod to colonist coast watchers – perhaps some Human miners in the asteroid belt.. perhaps BHP employees ;)

  2. Robert says:

    I speculated several snippets back that Bitka’s business background is going to become important to this story line. It seems to be borne out by these recent developments. I suspect also that Dynamic Paradigms may end up in trouble, or at least greatly embarrassed, by some of the developments of this story. Does Dynamic Paradigms use “profits before peace” as its business mantra?

    • Mike says:

      It looks like this is going to be used to get Bitka moved out of his “I can do anything without consequence because my real career is back home” comfort zone.

  3. Randomiser says:

    He carries this unbreakably complex code of durations, intensities and frequencies in his head? Or he just happens to have packed it in his luggage? Really?!?

    But if he does have them he doesn’t have to reveal them to anyone. Just take a quick trip down the needle, chuck everyone out of the room, put on his product support executive hat, do his stuff, and let the techs back in to their miraculously unlocked fabricators. All under military orders in a war zone. If his company wants any arm of government to keep buying stuff from them after the war, there won’t be any complaints.

    • Mike says:

      Yeah, this whole thing is somewhat contrived.

    • Robert says:

      Does he have to reveal the code to a person? The fabricator probably stores the activation code so that an audit of the machine reveals who activated it when and (more or less) for what purpose.

      • Richard H says:

        Aside from the bizarre characterization, this seems more like an admin backdoor than anything else. As a programmer, I’m interested in learning how they manage to salt the user/password combo in a way that isn’t spoofable. (I’m not actually interested in learning how they do it in a science fiction book, but this seems like the hard part.)

      • Dave Lachlan says:

        The fabricator can become a casualty of war once no longer needed.. “Yes Sir, I need to access the machine on regular intervals as there is a tricky IP self destruct feature.. I can guarantee that it will self destruct if anyone else tries to do anything with the coding or download usage specs etc. Even so the work around may fry the machine at some stage anyway.”

        • Dave Lachlan says:

          Or he can just be honest with the Duchess – and look at a life long career on Her Majesty’s Service.

          • Mike says:

            Navies aren’t exactly like corporations, are they? I mean, you can’t just quit your job at the US Navy and make a lateral move to the UK Navy, can you? What about your nationality?

            • Dave Lachlan says:

              Sam breaching the IP could get the US government sued (he is their employee etc), they may then happily throw him out, he would be black banned from legitimate corporations, which leaves “free lancing” and the UK secret service might value his skills/knowledge/contacts. When corporations are more than just global, nationalism might be less relevant.

          • Anonymouse says:

            I am throwing in with Dave on both points here.

            Sam gets the fabricator code to the Red Duchess. British Naval Intelligence gives the codes to the ground forces.

            The fabricators are destroyed by the last fire lance of the last battle of the war.

            Or the fabricators killed themselves. (I can go either way here.)

      • Randomiser says:

        The log sure isn’t going to detail the secret code. The fact that the m/c can be reset and the general method can’t be secret, otherwise they couldn’t be IP. The actual code and procedure is the secret and he isn’t disclosing those just by using them himself.

  4. TJ says:

    I could see the company going one of two ways if Bitka survives.
    Fire Bitka /take to court.
    Promote employee as war hero noting company did it all it could to keep humans alive.

    My experience with real life corporations suggests either is actually possible.

    Besides they can always bill nations for war supplies after wards

  5. Randomiser says:

    WEBSITE REDESIGN

    Off topic but I cant see anywhere else to put this. The new design looks cleaner and clearer than before and its easier to get to the snippets. However could we please have the count of comments for each snippet and the direct link to them back? I sometimes drop back 2 or 3 times to see how discussion is going and it is convenient to be able to tell right away whether there is anything new then jump straight to the comments.

    Also the 1,2,3,4 etc bar at the bottom of the page is currently broken and gets a 404 error

    The snippets still don’t work on my phone. In portrait the text is all visible but in such a tiny font it is unreadable, i.e. the page doesn’t resize appropriately for the screen. In landscape they would be just about readable but the list of links on the RHS appears over the text making it illegible.

  6. Courtenay says:

    On my browser the “Jump to the Snippets” line at the start of the page does not work. It is not clickable. I second the motion about including the count of the snippets. Finally, is there a difference between the “Continue Reading” line the “Read more” button? If not, one should be gotten rid of. If there is, please explain! Thank you.

Leave a Reply

Your email address will not be published. Required fields are marked *