{"id":92949,"date":"2019-11-25T07:45:36","date_gmt":"2019-11-25T11:45:36","guid":{"rendered":"https:\/\/valorguardians.com\/blog\/?p=92949"},"modified":"2019-11-26T18:29:44","modified_gmt":"2019-11-26T22:29:44","slug":"navy-secretary-fired","status":"publish","type":"post","link":"https:\/\/www.azuse.cloud\/?p=92949","title":{"rendered":"Navy Secretary Fired"},"content":{"rendered":"

Well, it seems as if the infamous “loss of trust and confidence” has happened again. This time it involves the SECDEF losing trust and confidence in the SECNAV – and firing him.<\/p>\n

Here’s why. Per this AP story<\/i><\/a>, apparently the SECNAV is alleged to have proposed privately a deal to the POTUS regarding CWO<\/del> CPO Gallagher. That deal would have allowed CPO Gallagher to retire both at his current rank and without loss of his SEAL Trident.<\/p>\n

There’s just one problem. According to the SECDEF, it appears the SECNAV didn’t bother to inform him about his backchannel prosal to the POTUS. Previously, the SECDEF had backed the SECNAV regarding allowing the Navy’s admin processes against CPO Gallagher to run their course. The SECNAV thus undercut his own boss in clandestinely proposing the deal.<\/p>\n

However, in public comments two days ago the SECNAV strongly implied he was still in favor of proceeding with administrative processes against CPO Gallagher. Specifically, the SECNAV .stated publicly that he didn’t consider tweets from the POTUS to be directive in nature and would need a Presidential order to stop admin proceedings against CPO Gallagher.<\/p>\n

As a result, the SECDEF fired the SECNAV for “lack of candor”.<\/p>\n

The linked AP article goes on to say that the SECDEF has further decided that CPO Gallagher likely can’t get a “fair shake” from the Navy regarding any such admin process. The SECDEF has therefore directed that CPO Gallagher be allowed to retire at the end of this month, at his current rank (CPO) and without loss of SEAL qualification. <\/p>\n

The moral to the story: trying to play “both sides against the middle” can be quite risky. That’s especially true when the attempt involves a contentious situation where your boss has taken heat for backing you publicly. <\/p>\n

Doing something like that can get you fired, even if you’re the SECNAV.<\/p>\n","protected":false},"excerpt":{"rendered":"

Well, it seems as if the infamous “loss of trust and confidence” has happened again. This … Navy Secretary Fired<\/span>Read more<\/a><\/p>\n","protected":false},"author":623,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[84,119],"tags":[],"class_list":["post-92949","post","type-post","status-publish","format-standard","hentry","category-military-issues","category-navy"],"_links":{"self":[{"href":"https:\/\/www.azuse.cloud\/index.php?rest_route=\/wp\/v2\/posts\/92949","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.azuse.cloud\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.azuse.cloud\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.azuse.cloud\/index.php?rest_route=\/wp\/v2\/users\/623"}],"replies":[{"embeddable":true,"href":"https:\/\/www.azuse.cloud\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=92949"}],"version-history":[{"count":1,"href":"https:\/\/www.azuse.cloud\/index.php?rest_route=\/wp\/v2\/posts\/92949\/revisions"}],"predecessor-version":[{"id":92981,"href":"https:\/\/www.azuse.cloud\/index.php?rest_route=\/wp\/v2\/posts\/92949\/revisions\/92981"}],"wp:attachment":[{"href":"https:\/\/www.azuse.cloud\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=92949"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.azuse.cloud\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=92949"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.azuse.cloud\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=92949"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}