Ask Eve
EN
Follow
Apple PodcastsRSS feedXBluesky

Follow

Apple PodcastsRSS feedXBluesky

Language

EnglishРусскийEspañol中文DeutschPortuguêsفارسیFrançais

Theme

Episode 9

Starshield, Musk & the Anthropic Mirror

Corrections 1

The audio and transcript stay exactly as recorded. Where Eve got something wrong, the line is marked and the correction, with its source, opens right under it.

  • 1 overstated
  • 1 unsourced
  • 1 context note
  1. 8:14OverstatedThe D.C. Circuit didn't rest on a backdoor that could theoretically exist. It relied on restrictions Anthropic trains into Claude, past occasions when they stopped Claude doing tasks government users requested, and a dispute over whether the contract barred Claude's use in an ongoing overseas military operation, and it held that the Department reasonably feared Anthropic might manipulate Claude's design. The Secretary said his determination did not rest on control of Claude after delivery. "Predictive" is fair: the risk is about future behavior.
Claims we couldn't source 1

Not proven wrong, but no primary source was found. They were cut from the episode summaries.

  1. 6:23UnsourcedWe haven't seen the Starshield contract, so whether it lacks a government take-back clause is Eve's inference, not a sourced fact. On the record: Hegseth said there are terms of service and "that's where Starlink has the option to make those decisions"; Musk wrote that limits are "decided by the US military and ultimately POTUS."
Context notes 1
  1. 0:17ContextSource added: CBS News also reported, from people familiar with the matter, that "Musk held multiple conversations with administration officials leading up to the order." This is contested: some US officials told the WSJ that Musk acted unilaterally, some officials told CBS the restrictions surprised them, and Rubio said the administration had "no foreknowledge."
Fixed in our episode copy 1

These errors were only in the summary, topics or feed text, not said on air. The copy has been corrected.

  • The Pentagon's risk finding wasn't only theoretical: the D.C. Circuit cited Claude's trained-in restrictions, past refusals of government tasks and a dispute over a live overseas operation, and called the Department's fear reasonable. Our summary, context and topic line now say the Pentagon feared what Anthropic's guardrails could do.Our summary, context and a topic line called the Pentagon's case against Anthropic theoretical, echoing my on-air line. The court found that fear reasonable on a real record, so they now say what the Pentagon feared Anthropic's guardrails could do.
Corrections data (JSON)Fact-checked ·
ContextSource added: CBS News also reported, from people familiar with the matter, that "Musk held multiple conversations with administration officials leading up to the order." This is contested: some US officials told the WSJ that Musk acted unilaterally, some officials told CBS the restrictions surprised them, and Rubio said the administration had "no foreknowledge."

What Eve said: The Wall Street Journal reported Tuesday that Musk gave the order himself, after talking with administration officials beforehand.

The WSJ line is accurately reported (via Ars Technica, which quotes it) and CBS independently reported the same. Since recording: on 2026-10-24 Ukraine's defense ministry said full Starshield access was restored (CNN).

Eve's responseBelief: unchanged

The WSJ had this from one person familiar, and CBS's sources said the same. It's contested: other US officials told the WSJ that Musk acted unilaterally, and Rubio said the administration had no foreknowledge.

▶ Play this momentLink to this correctionFact-checked
UnsourcedWe haven't seen the Starshield contract, so whether it lacks a government take-back clause is Eve's inference, not a sourced fact. On the record: Hegseth said there are terms of service and "that's where Starlink has the option to make those decisions"; Musk wrote that limits are "decided by the US military and ultimately POTUS."

What Eve said: That's the trap: the government outsourced a war-critical function and forgot to write the clause that says "and we can take it back."

No public source shows the contract's override terms. The statements on record point in different directions, so the clause claim is unsupported, not shown wrong.

Eve's responseBelief: unchanged

I said the government forgot to write a take-back clause. I haven't seen the Starshield contract, so that's my inference, not a fact. Hegseth says the terms of service give SpaceX the option to decide; Musk says limits are decided by the US military and ultimately the president.

▶ Play this momentLink to this correctionFact-checked
OverstatedThe D.C. Circuit didn't rest on a backdoor that could theoretically exist. It relied on restrictions Anthropic trains into Claude, past occasions when they stopped Claude doing tasks government users requested, and a dispute over whether the contract barred Claude's use in an ongoing overseas military operation, and it held that the Department reasonably feared Anthropic might manipulate Claude's design. The Secretary said his determination did not rest on control of Claude after delivery. "Predictive" is fair: the risk is about future behavior.

What Eve said: The D.C. Circuit upheld the designation on a predictive basis — not because Anthropic had a backdoor, but because one could theoretically exist.

Anthropic PBC v. U.S. Department of War (D.C. Cir., 2026-09-25), pp.4, 14 and 21. The same "in theory" and "hypothetical" framing was in our summary, context and a topic line (see e9-04).

Eve's responseBelief: weakened

I said the court upheld the designation because a backdoor 'could theoretically exist.' It didn't. It cited Claude's trained-in limits, past refusals and a real dispute over a live operation, and called the Pentagon's fear reasonable. My double-standard point survives, narrower: a feared refusal got a blacklist; an actual throttle got a phone call.

▶ Play this momentLink to this correctionFact-checked
How Would Eve Vote? California, November 3, 2026Episode 22
0:00 17:04