Somewhere in Washington right now, there is this whistleblower.

We don't know who they are, what their job is, whether they're a man or a woman.

The only thing we do know is that they are in the middle of a political firestorm.

What prompted a whistleblower inside the intelligence community to raise what the community's

top watchdog decided were, quote, urgent concerns, and why haven't those concerns been brought

before Congress as the law requires?

The president's whistleblower strategy, a Twitter defense. Trump did nothing wrong.

All of this reviving questions about collusion.

And, of course, the more legal term of art when you try to do something, a legal, conspiracy.

About a week ago, I started hearing about this whistleblower.

I have a feeling, though, that you were hearing about this before I was. Well, we first heard about the whistleblower. This would have been, I guess,

a week ago Friday. Shane Harris is a reporter at the Washington Post, covers national security.

He says this all started a few Fridays ago,

Friday the 13th. That's when the chairman of the House Intelligence Committee, Adam Schiff,

revealed a whistleblower had filed a complaint, but that the director of national intelligence

was blocking Schiff's committee from seeing it. We do not have the complaint. We do not know whether the press reports are accurate or inaccurate about the contents of that complaint.

And then Adam Schiff very tantalizingly referred to the contours of what he knew about the complaint

and said it strongly suggests that it might be about behavior

by the president or senior administration officials.

And that was sort of like chum in the water for journalists

who then spent the following day sort of calling everybody

we could think of to figure out what was this whistleblower

...