It's both Base Strike AND Decisive Battle, as I said before they don't actually differ all that much on the strategic level while on the offense. Decisive Battle prefers/is better able to deal with scenario 3, Base Strike prefers/is better able to deal with Scenarios 1 and 2, but they are both equipped to deal with all three scenarios, both have bonuses for pitched battles as well as for assaulting fortifications.
You said that, but your explanation wasn't credible, because it wrongly stated that the objectives of operations under each doctrine would be similar. However, we have specific WoG that the methods by which each doctrine aim to our political goals (and end the war in our favor) are very different. The doctrinal goals (logistics, infrastructure, warships) inform the operational objectives. So I would strongly disagree that a set of Decisive Battle operations would resemble a set of Base Strike operations. In each, good operations would be designed to further the goal of destroying ships or infrastructure respectively, and therefore would have very different objectives.
The impetus for Base Strike to accept a Scenario 3 and wreck a fleet is to enable current or future operations against infrastructure by taking ships out of action. The impetus for Decisive Battle to accept Scenarios 1 and 2 is... to settle for less or to change the way the enemy fleet operates in the future. Which brings me back to my original points on the subject, which is that DB has a lot more trouble accomplishing its objective operationally, poorer opportunities for forcing moves, and fewer tools to use.
No, threatening does not at all require your position to be known, rather the opposite. The greater the uncertainty about your position the larger the area you effectively threaten. If your position is so uncertain the enemy has no idea you are even in the general area in the first place you have a decisive advantage, one that Decisive Battle does not particularly help you exploit, but at that point you shouldn't need much help. The very point of threatening is that ignoring the threat is worse for the other side than the action you are trying to manipulate them into, so the enemy not even knowing about the threat is perfe
I disagree. This type of uncertainty as axiomatically good is one of those principles that falls apart in practice. The more certain your position is, the more forcing it is. I don't particularly care about a position so uncertain that the enemy reaction could be any number of moves, I care about positions that are forcing a single move that I can predict. Positions where if the natural, mandatory moves are prosecuted to their full extent, the result is our objectives are met. This does not mandate uncertainty but rather requires a strong degree of certainty in the forcing aspect. Uncertainty has its place, but not in forcing specific movements that can be reacted to in a consistent way. And yes, that does mean attempts to force a decision require both certainty to force enemy action and uncertainty to surprise the enemy, in a contradictory way, but that's exactly what I mean when I say Decisive Battle has major difficulties actually prosecuting its objectives.
Again, I feel this goes back to your mistake about the overall objective of operations under each doctrine. Menacing uncertainly is good... for operations where the objective is to destroy infrastructure where the enemy is not: for operations under Base Strike.
Just as Decisive Battle has +2 to intercept, other doctrines have bonuses to not being intercepted and to making it to structures under threat. For example, Base Strike would have as much as +4 to avoid this.
Arguing on ship design advantages violates my premise of relative equality. I do agree that much will be won or lost, many advantages gained or discarded, in ship design. But that's not the subject at hand. I will say that if we can make the Kepler, what stops an enemy from making a D6 ship that doesn't have to spend on presence?