Thread by @DanLamothe

If you were paying attention, you may have noticed that @PressSec and @StateDeputySpox commented on this scoop published Tuesday morning.

A couple of important points worth making to follow:

washingtonpost.com/national-secur…

@PressSec @StateDeputySpox If you saw the first version of the story, you would have seen no comments on the record from the White House and State Department in the story. That wasn't for a lack of trying. I communicated with them through the weekend and as late as Monday night shortly before 11 p.m.

At the State Department, @StateDeputySpox had a prepared statement that she read at the tail end of her briefing. Here it is in its entirety:

As you might notice, she doesn't reference @washingtonpost directly. But it's plain as day she's talking about this story. She dismisses the comments as "cherry-picked," as though there wasn't a cornucopia of similar options from which to choose.

. @StateDeputySpox also said that some of the claims were false and "shamefully so."

Which ones? Elaboration would be appreciated.

And is the department really sure about that, in all that chaos?

I would note that there were *several* other situations detailed in my story today that were not previously reported.

They include a reported civilian death because of a stun grenade and a firefight between Marines & Afghan strike unit members who were there to work together.

In the latter cases, I got zero pushback from the Pentagon. These are new details, but they're not untrue.

I also included an on-the-record comment from @PentagonPresSec, which I appreciated. I wanted to be fair.

No one is reporting that all State Department personnel were laying down on the job. We are reporting that U.S. military officers deeply involved in the evacuation were frustrated with the civilian colleagues, and citing specific reasons why.

More to come tomorrow. Not done with this story yet.