
A former longtime Coats aide pushed back on the notion that the DNI was the author. “I doubt it. Not his style. He’s the kind of guy who will share news in private, but at the end of the day, he’s really focused on what’s best for the country. Sounds trite, but he’d make his feelings known to POTUS and stay out of the fray,” this person told CNBC.
Coats himself called speculation that he wrote it “patently false.”
The op-ed, which the Times published Wednesday afternoon, describes a coordinated effort within the administration to undermine Trump, who he or she described as “amoral,” and “frustrate parts of his agenda and his worst inclinations.” The author also wrote that this internal resistance wants the administration to succeed, while praising some policy victories, such as a broad tax cut package last year.
The Times, in turn, defended its rationale for running the column by saying, “publishing this essay anonymously is the only way to deliver an important perspective to our readers.”
The official who wrote the piece described talk among Cabinet members about possibly using the 25th Amendment to remove Trump from office. The amendment went into effect in 1967, four years after President John F. Kennedy was assassinated, as a way to clarify constitutional lines of succession in the event a president dies or is incapacitated.
A White House official, speaking on condition of anonymity, told CNBC there was never any talk of the 25th Amendment inside the Cabinet, and that the White House has no concerns about command and control of the administration.
The official also told CNBC there was no specific meeting to discuss “Lodestar” on Wednesday night.
Trump responded to the piece by lashing out at the media and the anonymous author. NBC News reported that several of the president’s aides and allies have described his mood as “volcanic.”
On Wednesday night, one of his tweets said “TREASON?”
The president continued venting his rage and frustration Thursday morning on Twitter.
from News Viral View https://ift.tt/2Q7UhaF
via IFTTT
0 comments:
Post a Comment