Trump signs downsized AI order after weeks of reversals

A new, scaled‑back U.S. executive order on artificial intelligence asks major labs to submit powerful models for a voluntary government security review before release, echoing but softening earlier proposals for much longer delays and stricter controls. Commenters are split on whether this is a reasonable cybersecurity measure or primarily a way for the administration to gain leverage over AI companies and shape model “ideology” via procurement power, building on the prior “Preventing Woke AI” order. Many also worry the framework will entrench large incumbents, marginalize open‑weight and foreign models, and do little to address deeper safety or civil liberties concerns.

Scope and Content of the EO

  • Seen by several as relatively “thin”: restates cyber priorities, asks agencies to improve cybersecurity and maybe use AI, and to prioritize prosecuting cybercrime.
  • A key concrete piece: directs NIST/CAISI to build (partly classified) benchmarks for cyber capabilities and to define what counts as a “covered frontier model.”
  • Asks some AI companies to submit powerful models for voluntary review 30 days before release (down from an earlier 90‑day draft).
  • Some view it as a continuation/expansion of earlier “woke AI” procurement rules that tie federal purchasing to model “ideology” and “neutrality.”

Legal Status and Enforcement

  • Multiple commenters emphasize that executive orders aren’t laws and directly bind only the federal government.
  • Others stress de facto leverage: federal contracts, “supply chain risk” labels, targeted regulatory or prosecutorial attention, tariffs, immigration/H‑1B or tax enforcement can coerce compliance even without formal mandates.
  • Debate over courts: some point to a long list of successful legal challenges; others argue recent events show limits of judicial constraint in practice.

Ideology, Censorship, and Government Leverage

  • Concern that procurement rules and review processes will be used to pressure models toward specific political narratives, suppress criticism, or surveil users.
  • Counterpoint: the text formally applies only to government procurement; no private vendor is legally forced to change outputs, they can just lose federal business—though critics say this is a distinction without much practical difference given training costs.

Safety, Security, and Evaluation Process

  • Some see the EO as a reasonable response to “frontier”/Mythos-level capabilities and as helping labs coordinate safely without antitrust issues.
  • Others doubt it’s really about safety, expecting politicized “security” checks or superficial tests.
  • Questions about how a 30‑day review can meaningfully evaluate threats; references to UK AISI/US CAISI red‑teaming as partial precedent.
  • Debate over secrecy: classified benchmarks are defended as analogous to undisclosed exploits; critics say secrecy leaves domestic systems vulnerable and invites insider trading on early access.

Market Impact and Open vs Closed Models

  • Many see the EO as moat‑building for large US incumbents, especially if “voluntary” reviews evolve into de facto licensing.
  • Fears it will be used against open‑weight and non‑US models (e.g., Chinese labs), justifying bans or restrictions under “safety” or “financial risk.”
  • Discussion that major US firms mostly avoid true open‑source frontier models to keep inference profitable; a few smaller or lagging models are open but not state‑of‑the‑art.
  • Sharp criticism of certain labs for lobbying against open weights and portraying them as inherently dangerous (cyber, CBRN).
  • Counter‑view: open‑sourcing powerful dual‑use models meaningfully increases bio/cyber risk, and the open community can’t match hyperscale data centers anyway.
  • Pro‑open side argues that closed models centralize power, enable surveillance and propaganda, and “gatekeep” a foundational technology; open weights are framed as essential for freedom, tinkering, and pluralism.

Review Delays and International Competition

  • Many think a mandatory 90‑day pre‑release review would be “insane” given competitive dynamics and the pace of progress; 30 days is seen as less damaging.
  • Others ask why any rush is needed at all if society functioned fine pre‑LLMs and the technology may be dangerous.
  • Some note that US law can’t bind foreign labs; others argue coordination among major powers could still emerge, with US moves as an opening bid.
  • Claims that some US states have “banned” specific foreign models are contested as overstated and limited to state‑device usage.

Broader Political and Institutional Context

  • Recurrent theme: fear that neutral civil‑service expertise has been gutted, making “politically neutral” oversight unrealistic.
  • Discussion of DOJ resource constraints: very few cybercrime convictions, extremely selective case choice, plus shifting focus toward immigration and politically driven priorities.
  • Some say many prosecutors are quitting or resisting cases they see as legally or ethically dubious.
  • Others respond that prosecutors who won’t prosecute federal crimes should leave; pushback follows about what counts as a “crime” under an administration alleging many weak cases.

Existential Risk and AGI Doom

  • One line of discussion dismisses AI‑doom scenarios as implausible, arguing that an all‑powerful AGI would require unrealistic computational feats (e.g., “simulating reality faster than reality”) and likely a very different “genesis code” than current LLM scaling.
  • Others point out that prominent people take existential risk seriously, but critics say being “smart” doesn’t make their premises sound.
  • Overall, the thread shows strong skepticism that current frontier LLMs are close to civilization‑ending AGI, especially while discourse remains focused on parameters, transformers, and benchmarks.