Remove ads

To Boldly Go... (a Starfleet quest)

Linked contents
To Boldly Go... (a Starfleet quest) Starfleet Ship Design Bureau, Refit ("To Boldly Go...")
Reader mode
Man what a punch to the gut... still positive from the turn is possibly ending the Dawai war. Ajam will be remembered. still cloaked mines... I am pushing short range sensors this research phase
 
Derek58 said:
Now that we have contact with Bajor, I think our chances are rather good that we can completely butterfly away the Occupation, preventing decades of death and suffering from ever happening :)

Oh nice, no need to halt an active build then.
Click to expand...
Click to shrink...

The Federation knew about Bajor in canon, and Bajor at this time is almost literally a harder sell to the Federation than the Apinae are. They are isolationist and have an extremely rigid caste system.
 
My reactions to the captain's log post:

Wait, there's already a USS Intrepid? What class?

Yay Saavik! You found the Bajorans!

I'm not entirely clear on what the situation was regarding the Miracht. Did the Betazoid envoy actually sleep with the Gaeni CEO, and if so how does the whole "telepathy matter" resolve the issue?

"If Sarek is one thing and one thing alone, it's old." *snrk*

I... oh. Oh no.

[sits there, desolate for a little while]

OneirosTheWriter said:
Last post before bed, as far as Member World berths, you have two berths of the right size open - at the Grand Hive of Apinae, and at the Gaeni Manufacturing Cooperative.
Click to expand...
Click to shrink...
If we can find a berth capable of accomodating in Excelsior on a member world I'd advocate doing it. Then again, we may have to accept starting one less ConnieBee this year anyway, if only because we'll need the resources to pay for the repairs. In that case, bumping the Connie from the three-megaton berth at Utopia Planitia is the most logical response.

@Briefvoice, what do you think? Can you estimate the likely repair costs on the Courageous and run the numbers?

[Vulcan hat still on]

This does create problems for our goal of having five five-year missions running concurrently in 2311, though. We'll have Courageous physically repaired in time, but will we have enough people to crew her?

It... looks like we do, actually. The reserve pool for the Explorer Corps is 3.5/5.60/7.25, considerably more than the casualties aboard Courageous. However, it does underline the need to keep up Explorer Corps personnel numbers. Maybe we should bump the Betazoid counselors up on our priority list.

[Takes Vulcan hat off]

We really, really do need to do something about the Syndicate. I favor this strongly, as they are implicated now in at least one terrorist attack (on the Amarki), and in selling advanced weapons to the Cardassians.

On the other hand, we're probably going to take some pounding during this snakepit, precisely because this was a Starfleet Intelligence operation gone wrong when we went poking around in a Syndicate-held system on our own initiative. It's fully in line with other missions we tacitly approved of (like the one where the Enterprise-B burned out a Cardassian forward base)... but that is itself the problem.
 
Hmm, looks like the canon colors of the Bajoran Provisional Government were red and gold? A bit unfortunate that they are right between the Seyek and the Cardassians. Maybe I should just steal the red from the Seyek and give them some other color. Or just wait with that until they become an affiliate anyway, which should be next quarter anyway.
 
Last edited:
AKuz said:
The Federation knew about Bajor in canon, and Bajor at this time is almost literally a harder sell to the Federation than the Apinae are. They are isolationist and have an extremely rigid caste system.
Click to expand...
Click to shrink...
We don't have to integrate them in order to butterfly the Occupation away. We just have to find an outcome that does NOT result in Cardassia militarily occupying and brutalizing the planet.
 
I'm actually kinda sad (I can be a very sensitive person, I straight up bawled through the last half hour of PMMM) Poor Maryam, I hope your loss means something.
 
So that +25 boost, I believe that puts us positive with the dawiar, maybe we should diplo push them. Also Qloath are at 64 so they are closing in on affiliate status
 
Simon_Jester said:
We don't have to integrate them in order to butterfly the Occupation away. We just have to find an outcome that does NOT result in Cardassia militarily occupying and brutalizing the planet.
Click to expand...
Click to shrink...

Considering that the Cardies have been supplying the Dawiar with torps, there's absolutely nothing stopping us from supplying the Bajorans with weapons if the Cardies start getting antsy around Bajor. Lets us apply some pressure on them for a change.
 
AKuz said:
The Federation knew about Bajor in canon, and Bajor at this time is almost literally a harder sell to the Federation than the Apinae are. They are isolationist and have an extremely rigid caste system.
Click to expand...
Click to shrink...
Yea, but from looking at the Occupation on Memory Alpha, it appears that the reason the Federation didn't interfere in canon was because the Bajorans were all ready a client race of the Cardassians.

We prevent that from happening, we can stay involved and prevent the Occupation.
 
@Briefvoice:

That being the case, since our resources are fully committed to new construction for the foreseeable future, repairing the Courageous most likely means cancelling (or at least deferring) the construction of one of our ConnieBees. Therefore, it is logical to put Courageous in the three-megaton berth at Utopia Planitia, since that berth is probably best suited to the repair work, and since we have to cancel plans for one of our ConnieBees anyway.

Also, the only available berths are in Apiata space (a long way to tow Courageous's disabled hulk) or Gaeni space (and I don't think we want the Gaeni working on one of our Excelsiors. We have enough problems, thankyouverymuch).

SynchronizedWritersBlock said:
I don't mean fault. I mean that this was a risk we undertook, not one uninvited.
Click to expand...
Click to shrink...
[Admiral talking to Council hat on]

"Yes, Starfleet undertook a mission that placed the Courageous at risk. It was a necessary risk that we undertook for compelling reasons. Our sole objective at Yvresse V was to unlock the mysteries of a Cardassian secret weapon. Any covertness in our own approach to the Syndicate was purely a result of the Syndicate's own failure to be forthcoming regarding their dealings with the Cardassians, despite or perhaps because of the evidence tying them to past incidents.

"This entire incident underlines that the Syndicate has a proven ability to provide significant support to dangerous external opponents, and to disable our most advanced ships when we seek to investigate their involvement in same. This underlines that the continued operations of the Orion Syndicate in or near Federation space present a grave hazard to the long term safety and stability of the Federation. While we favor a measured response, this is a rather different situation than the Polaris incident.

"This was not a diplomatic misunderstanding. The Syndicate is engaged in actions inimical to the Federation, and is willing to kill hundreds of Federation personnel to prevent investigation of these actions. While our response must remain measured and rational, it would be the height of folly for us to continue to behave as if the Syndicate did not exist, or was not a threat."
 
This kind of speech works better on success tho. Whatever our intentions, we kicked the hornet's nest, and now good people are dead, a ship is down, and we have nothing to show for it.

If you gotta raid pirate bases, you gotta succeed at it, or else we look bad. Like now.

It's a do it right or not at all kind of thing. Next snake pit's gonna suck. Good thing we have a successor ready (I'm not saying we'll need him. But.)
 
ok, this is getting kind of ridiculous. The syndicate is selling tech and Intel to the cardassians, and blowing up Starfleet vessels. Quite aside from them being slaving monsters they are actively aiding and abetting a hostile power. We need to break them, we need to damage them to the point where they cannot pose a threat to a serious opponent and are too skittish to risk brining down heat on themselves.
 
random_npc said:
ok, this is getting kind of ridiculous. The syndicate is selling tech and Intel to the cardassians, and blowing up Starfleet vessels. Quite aside from them being slaving monsters they are actively aiding and abetting a hostile power. We need to break them, we need to damage them to the point where they cannot pose a threat to a serious opponent and are too skittish to risk brining down heat on themselves.
Click to expand...
Click to shrink...
As much to the point, I do NOT think it will be the prompt consensus of the Council that Katsuragi should resign over this incident.

Aside from the obvious "we need to do something about the Syndicate" aspect, the real question is, is the Council going to be more inclined to blame the Syndicate, or to blame Starfleet?

Now, literally everything we know about the incident is the limited amount in that captain's log, plus inferences we can make from the posts involving our two favorite doctrine/design researchers. But from this, I honestly think we can make a good case that Starfleet was acting in good faith to investigate a secret weapon they had reason to believe had been funneled to Cardassia through Federation space. Did the Syndicate take the opportunity of this investigation to pounce on and attack one of our ships with sufficient force to disable it? Yes. Does that mean that demanding the resignation of the head of Starfleet is appropriate? No.
 
Reader mode
You must login or register to reply here.
Remove ads
Back
Top