Jonathan_S wrote:cthia wrote:
I don't suppose that you'll argue with preset primitives existing in a Case Zulu? Which is the point of a Case Zulu—where the need of second guessing one's responsibility and bailiwick has been removed. I would imagine that Case Zulu rules and regulations are forever being updated and rewritten as the Kingdom expands. Hell, I imagine a major update of Case Zulu specifics after the Star Kingdom became the Star Empire.
Actually I doubt Manticore would go down the route of prescribing mandatory actions for each level of command based on a case Zulu.
Even something as simple as relaying the invasion warning to the nodal defense force responsible for that area leaves that nodal force's commanders with multiple conflicting responsibilities.
Yes they need to defend the threatened system - but not at the risk of leaving other systems and assets within his area of responsibility unprotected/underprotected. The commander has to make a judgement call about whether or how to reallocated his forces in response to the case Zulu and there are too many variables to have predefined everything to the point where no second guessing is required.
Is the attack a feint to weaken defenses elsewhere?
If the local force strong enough to defend the system or should they simply picket while screaming for more help?
Did the attack leave the attacker's base underdefended - should you temporarily ignore the loss of a less important system to strike will all your weight at the enemy's local base?
etc. etc. etc.
Second guessing your various (and often conflicting) command responsibilities seem increased under Case Zulu rather than removed...
I disagree in part. But first, let us establish the scenario of most importance as far as Manticore is concerned. The imminent invasion of the Manticore Binary System. Every other concern becomes secondary to the defense of the Home system. If an enemy gets itself into position and controls the orbitals, "Check and Mate." Then it doesn't matter at all about any other nodal or command considerations. Game over.
If it isn't hardwired that
certain of your forces
must respond in a Case Zulu, then you run the very same risk of Santino-and-Young-like idiots refusing to comply amidst their own reasoning buried within simple cowardice and fear! Or
ignorance. You are setting yourself up for what happened with Young and
Warlock.Sure, there are other variables that might need to be considered
pursuant to official rules and regulations, but I won't agree that the main component of the decision process isn't already written in stone.
Or you expose yourself to selfish-ass imbeciles like Pavel Young claiming that he thought the system that
he was in, say Trevor's Star if he'd been in Honor's place, was more important. Just to save his own ass.
I'm not advocating against a command being free of decisions. Just free
of a lack of specifics.Scenario:The Battle of Manticore was won by the Peeps because after all was said and done, too many RMN commands exercised their own initiative and
failed to return. Hardly anyone did.
To ensure reliability, you have to hardwire certain realities into a Case Zulu.
I would even imagine that an officer who has a feeling that it is a feint and that his own area of command will be attacked, realizes that he makes the decision not to respond at his own peril, and may face a court-martial if the home system lives. Yet I imagine that he does it at his own risk anyways, truly for the "Honor of the Queen," but he is prepared to suffer the consequences.
But that does not change certain preexisting imperatives of a Case Zulu. Or what is the point of issuing a potentially impotent emergency warning of invasion? Impotent if certain responses aren't assured.
