Image Not FoundImage Not Found

A federal office conference room with a laptop, printed papers, and empty chairs around a long table.

CAISSI’s Reported White House Reporting Line Raises Questions About U.S. AI Safety Testing

On Nov. 8, The Associated Press reported that staff at the U.S. Center for Advancing Innovation and Standards for Super Intelligence, or CAISSI, had recently been asked to informally report to a White House office instead of operating at arm’s length inside the Commerce Department. The center also lacks a permanent director and has stopped publicly releasing some reports on the safety of particular frontier AI systems. For AI labs, evaluators, enterprise buyers and federal agencies, that is not a niche org-chart dispute. It goes to whether a government review of a powerful model is an independent warning signal, a confidential national-security assessment, or a voluntary collaboration with limited public visibility.

The White House did not answer AP’s specific questions about the reported arrangement. It said President Donald Trump had established a Super Intelligence Force, commissioned a report from the President’s Council of Advisors on Science and Technology, and would ensure continued U.S. leadership. No public memo, personnel notice or organizational chart has confirmed which White House office is involved, whether the arrangement is temporary, or whether CAISSI’s legal authorities inside NIST have changed. But the report lands at a sensitive moment: CAISSI has had rapid leadership turnover, and Congress began asking in August why public releases on model safety had paused.

One center, three different jobs

NIST still describes CAISSI as the federal government’s primary industry contact for testing and collaborative research on commercial “super-intelligence” systems. Its stated work spans measurement science, voluntary guidelines, voluntary agreements with developers and evaluators, and unclassified evaluations of capabilities that could create cybersecurity, biosecurity or chemical-weapons risks.

Those are not the same function. They only get lumped together under the broad label of “AI safety.”

One job is confidential national-security testing. Here, proximity to the White House could be an advantage. If a model shows dangerous cyber or bio-related capabilities, a small center may need faster escalation, better classified access and tighter coordination with agencies such as NSA and CISA. The administration’s own AI-security agenda points in that direction, calling for classified benchmarking, a voluntary framework for pre-release government access to frontier models and AI-enabled vulnerability defense. For a center allocated $10 million a year — AP said roughly one-eighth the annual budget of the United Kingdom’s counterpart — visibility at the White House could also mean leverage it currently lacks.

A second job is public-facing safety evaluation. This is where independence matters most. Frontier-model testing is supposed to provide an outside check on companies that have strong commercial reasons to ship quickly. A center that can publish inconvenient findings, explain its methods and preserve a record of what it tested gives buyers, regulators, workers and the public something more than a company assurance. When those public reports stop appearing, the market loses a signal it cannot easily replace.

The third job is voluntary standards work. Measurement methods, incident-readiness guidance and developer agreements can be useful even when they are collaborative rather than adversarial. But they are not the same as a public audit. If standards work, confidential pre-release access and public evaluation are all run through an unclear chain of command, outside readers can mistake cooperation for oversight.

Where independence actually shows up

The most important questions are less ideological than operational. Who chooses the tests? Who gets access to model weights, logs and safety data? Who decides what can be published, what must be redacted and what remains classified? Can a lab delay or refuse evaluation? Can another office overrule a finding or sit on it until a release window passes?

That is why the reported informal reporting line matters even without proof of political interference. The AP report does not show that the White House ordered results to be altered or suppressed. NIST’s public CAISSI page still presents the center as part of a research-and-standards structure tied to the NIST director, which remains evidence of the formal setup. And the simple politicization story is too neat: CAISSI has continued to publish work with NIST, NSA and CISA, including incident-readiness practices released in October 2026.

Still, process credibility is fragile. AP reported that CAISSI’s director was hired and fired within days in April 2026, a replacement resigned after a few months, and the head of the parent institute is now acting director. That kind of churn makes any technically complex mission harder to defend. Add the pause in public model-specific reporting, and outsiders are left to infer whether the center is prioritizing classified work, reorganizing, or pulling back from public judgments altogether. None of those possibilities is trivial.

The administration’s September order directing agencies to use “SI” rather than “AI” in official communications does not settle any of this. Labels do not answer the governance problem. The credibility question is not whether Washington calls these systems AI or super intelligence. It is whether the people evaluating them can surface uncomfortable results and separate public assurance from confidential executive-branch review.

What the market should watch next

For businesses and agencies that rely on government signals, the practical move is to stop treating “federal AI testing” as one thing. A confidential national-security assessment may be rigorous and still tell enterprise buyers almost nothing. A voluntary standards partnership may improve practice and still fall short of independent validation. Only a public evaluation with stated methods, accountable publication rules and a clear escalation path works as a broad assurance signal.

That means the next useful disclosures are structural, not rhetorical: a written mandate, a permanent director, a publication and redaction policy that separates classified reviews from public reports, and clarity on who can overrule release decisions. Congress, developers and outside evaluators should also want to know whether labs must provide comparable access to models and logs, or whether the government is relying on case-by-case cooperation.

If the White House wants CAISSI closer because frontier testing now touches national security, that case is easy to make openly. The harder part is preserving trust in the center’s public-facing role at the same time. Without explicit firewalls between classified benchmarking, public evaluation and voluntary standards work, every future CAISSI finding will carry the same question: is this an independent judgment, a closed-door government review, or a collaborative process being mistaken for one?