CRS, NSA and the Question of Congressional Notification
Last week, Rep. Pete Hoekstra (R-Mich.) lashed out at the Congressional Research Service for asserting that the Bush Administration may have had a legal responsibility to notify more than just eight members of Congress regarding the NSA surveillance activity.
Rep. Hoekstra, the chairman of the House Intelligence Committee, did not merely suggest that the CRS might be wrong; he claimed that the agency was actually biased against Bush Administration policy (“Mau-Mauing the Congressional Research Service”).
In fact, however, it is increasingly clear that Rep. Hoekstra is the one who misunderstood and misrepresented the requirements of the law.
Sen. Mike DeWine (R-OH) put the matter plainly at a February 6 Senate hearing on the NSA surveillance program, explaining that the statute which permits limited notification to eight members of Congress is relevant only to covert actions, and not to the NSA program.
“When you look at that section [50 USC 413(b)], the only thing this references as far as what this Group of Eight does is receive reports in regard to covert action. So that’s really all it is. It does not cover a situation like we’re talking about here at all,” Sen. DeWine said.
“We all have a great deal of respect for these eight people… They’re leaders of the Congress. But there’s no statutory authority for this group, other than the section that has to do with covert operation, and this [the NSA activity] is not a covert operation as defined in this specific section.”
“I don’t mean to be impolite… I guess I’m just kind of a strict constructionist, kind of a conservative guy, and that’s how I read the statute,” Sen. DeWine said.
See, relatedly, “Hoekstra blasts CRS for ‘bias'” by Jackie Kucinich, The Hill, February 7.
Americans are paying too much for almost everything, because the United States has long treated its trucking industry as an artifact to be preserved rather than as an opportunity for innovation.
These ideas aim to advance the detailed policy solutions needed to foster public trust and implement fairness in the adoption of AI across diverse domains, from healthcare and government benefits to rural access, education, and worker protections.
The evidence is clear: algorithmic pay-setting is established in app-based work, and payroll/timekeeping failures show how software can produce systemic wage harm at scale
While a few states have taken steps to implement decision-making mechanisms for certain AI systems, too many leaders are simply accepting narratives about AI’s purported public benefit at face value – jumping to the “how” of AI implementation before thoroughly vetting potential systems and deciding whether they are appropriate to use at all.