@FourFans and @Negat0ry , you guys are going after the "illegal orders" straw man pretty hard. You can let it go. 17D is questioning the legality of the entire operation based on a court-established timeline precedent which has been repeatedly used to side-step and violate the constitution for decades before you, me, or anyone else ever considered joining the military. Vietnam, Korea, Iraq 1, Iraq 2, Afghanistan, and so on. In precisely zero of these 'operations' did Congress ever declare war. Again, you can spare me the refrain to article 8. We can all read. Someone else did a good job drawing out the distinction for you: yes, you have a basis and duty to question the legality of orders like "drop a bomb on this mosque." That's not what 17D was doing. As a line officer, you're on pretty shaky ground the second you start engaging in constitutional lawyership and pontificating about who does or doesn't have the authority to deploy me. My intent was to underscore the hypocrisy of asking questions on this basis now, after swearing an oath rooted in the very precedent he now seems to be trying to overturn. You (we) all looked at the rules of the game before we started playing, decided they were satisfactory, and now that we're on the field, some of us have started questioning the rule book because a few are upset that there's a new head coach. That's what I'm calling out. That's the opposite of the officership I'm talking about. It's rooted in self-service, not service to the country. It points either at the lack of introspection someone had when they swore the oath, or a newly found distaste for the flavor of the month. Neither are very officer-like. Feel free to misread this yet again and continue white knighting for the constitution.