Anthropic → LLNL
Directly documented interface
Deployment
An identified institution reports deploying or using the named provider system, possibly through intermediaries.
provider → user. Supplier → research user. Defence context follows the reported national-security applications.
Displayed claim → analysis (if present) → coded attributes → interface / instrument → atomic evidence → source version
Instrument and timeline
- Instrument
- Claude for Enterprise deployment
- Bindingness
- Contract terms not established
- Announced
- 2025-07-09
- Observed by
- 2025-07-09 · upper-bound
- Effective period
- Unknown → Unknown
- Event
- Reported deployment
- Status at cutoff
- unresolved/unknown
- Last confirmation
- 2025-07-09
Coding-agent availability in July 2026 is a different product/interface and cannot verify the Enterprise deployment agreement.
- Supplier → research user. Defence context follows the reported national-security applications.
- Continuity through cutoff unresolved.
Status investigation
Checked 2026-09-12; assessed as of 2026-09-12. Last confirmation does not establish uninterrupted continuity.
- amendments
- unknown
- expiry
- unknown
- termination
- investigated within listed sources
- restrictions
- investigated within listed sources
- succession
- see succession.json
- conflicts
- Coding-agent availability in July 2026 is a different product/interface and cannot verify the Enterprise deployment agreement.
Search queries
- "anthropic" "llnl" deployment 2026 amendment termination expiry status before:2026-09-13
Analytical assessment
No reviewed analytical conclusion is attached. This does not establish independence or absence of an institutional constraint.
Coded attributes
technical-control: shared-constrained
Practical ability to alter the model, its availability, or safeguards in the specified deployment. Contract clauses alone are insufficient.
Actor × exact model/deployment × period. Anthropic provision and replacement of Claude models for DoW, contrasted with deployed operational control; 2025–August 2026; assessed 2026-08-27.
Anthropic provides model artifacts and responds to feedback; DoW and cloud providers independently gate operational deployment. Existing deployed models are outside Anthropic technical alteration or shutdown. Consequential functions are divided across institutions, satisfying shared/constrained control without attributing a real-time veto.
Supporting evidence: court-model-provision court-update-gate . Counterevidence: contractual-control court-static-deployment
- Coding applies only to stated context and date, not a permanent institutional rank.
Published rubric anchors
- little-control
- No demonstrated practical control over the specified consequential operation, with affirmative contrary evidence.
- shared-constrained
- Consequential controls divided among actor, host, customer or enforceable technical constraints.
- substantial
- Actor demonstrably retains major development, update or access controls in this environment.
- dominant-lifecycle
- Actor demonstrably controls development, deployment, updates and access across the specified lifecycle without a consequential independent controller.
Unresolved when necessary evidence is missing or adjacent anchors cannot be distinguished. No numeric conversion. Absence requires affirmative remit or operational evidence, not missing sources.
Atomic evidence and exact sources
Anthropic reported expanded Claude deployment at LLNL, including biosecurity research applications.
- Source
- LLNL expands Claude for Enterprise use · Anthropic
- Version
- 2025-07-11; retrieved 2026-09-12
- Exact locator
- Opening paragraph; Security & compliance for national security missions, Computational Biology bullet
- Limit
- Supplier-reported deployment; independent outcomes, contract terms and present status are unverified.
Retrieved bytes SHA-256: 8b962ac8bf213ee49849ea47fc0b93494fd6bf59a5f52171d451dab6ce11624a
Anthropic could not technologically enforce contractual usage restrictions and lacked direct visibility into DoW use.
- Source
- Anthropic v DoW: summary judgment, document 250 · US District Court, Northern District of California
- Version
- 2026-08-27; retrieved 2026-09-12
- Exact locator
- Printed page 6
- Limit
- Specific deployed environment; does not imply no control over future development, contracts or provision.
LLNL reported an organization-wide Claude for Enterprise rollout.
- Source
- Claude for Enterprise facility-wide rollout · LLNL
- Version
- 2025-08-18; retrieved 2026-09-12
- Exact locator
- Opening body paragraphs
- Limit
- Rollout announcement does not measure realized outcomes or continuing contract terms.
Retrieved bytes SHA-256: edb6a0a4c4edc09fb73f4f682ddf31c78e541095b0457c5fe6c455aeec36d7bd
Blackhole permits Codex and Claude Code agents on Livermore Computing systems.
- Source
- Technical Bulletin 608: Blackhole sandbox · LLNL
- Version
- 2026-07-09; retrieved 2026-09-12
- Exact locator
- Opening paragraph and Getting Started
- Limit
- Enabled execution, not measured usage, direct procurement or Enterprise-contract continuity.
Retrieved bytes SHA-256: 115de6169c60d4eb32e7b4dea4b037b7f1d6ecff0cd80c304b7356cf811cbf5b
The court describes deployed DoW Claude models as static and beyond Anthropic technological access, alteration or shutdown.
- Source
- Anthropic v DoW: summary judgment, document 250 · US District Court, Northern District of California
- Version
- 2026-08-27; retrieved 2026-09-12
- Exact locator
- Printed page 17, Section II.F, first paragraph
- Limit
- Applies to deployed models described in this litigation, not future model provision or hosted consumer services.
The court records that replacement Claude models undergo third-party cloud-provider and DoW security testing and evaluation before operational approval.
- Source
- Anthropic v DoW: summary judgment, document 250 · US District Court, Northern District of California
- Version
- 2026-08-27; retrieved 2026-09-12
- Exact locator
- Printed page 17, Section II.F, first paragraph
- Limit
- Identifies a deployment approval gate, not complete interpretability, universal evaluation sufficiency or provider substitutability.
The court records Anthropic providing models to DoW or a primary defense contractor and responding to DoW evaluation feedback and requests.
- Source
- Anthropic v DoW: summary judgment, document 250 · US District Court, Northern District of California
- Version
- 2026-08-27; retrieved 2026-09-12
- Exact locator
- Printed page 17, Section II.F, first paragraph
- Limit
- Provision is distinct from control over deployed inference; future supply terms and update alternatives are unspecified.
Supporting and conflicting evidence
Interface support: llnl-deployment, llnl-rollout. Counterevidence: llnl-sandbox-models
Substantive review
evidence/llnl-deployment: approved · agent reviewer codex-research-checker · 2026-09-12
Anthropic describes expanded LLNL Claude deployment and the Computational Biology application. Attribution to the supplier and unverified outcomes are retained. Checked locator: Opening paragraph; Security & compliance for national security missions, Computational Biology bullet. Source version: 2025-07-11.
Approval fingerprint: 1e7930e6d70cddee066b09a959f5046c89228cfdbf91ecb37db5b43d6212271a
evidence/contractual-control: approved · agent reviewer codex-research-checker · 2026-09-12
Judgment page6 distinguishes contractual conditions from technical enforcement and use visibility in the specified environment; later provision and lifecycle control are expressly not excluded. Checked locator: Printed page 6. Source version: 2026-08-27.
Approval fingerprint: 1e7930e6d70cddee066b09a959f5046c89228cfdbf91ecb37db5b43d6212271a
evidence/llnl-rollout: approved · agent reviewer codex-research-checker · 2026-09-12
LLNL August18 announcement independently reports the Enterprise rollout. A rollout is not evidence of beneficial outcomes or current contract terms. Checked locator: Opening body paragraphs. Source version: 2025-08-18.
Approval fingerprint: 1e7930e6d70cddee066b09a959f5046c89228cfdbf91ecb37db5b43d6212271a
evidence/llnl-sandbox-models: approved · agent reviewer codex-research-checker · 2026-09-12
LLNL Bulletin608 opening and Getting Started permit Codex and Claude Code in Blackhole; availability does not establish utilization or provider-operated model service. Checked locator: Opening paragraph and Getting Started. Source version: 2026-07-09.
Approval fingerprint: 1e7930e6d70cddee066b09a959f5046c89228cfdbf91ecb37db5b43d6212271a
instruments/llnl-claude: approved · agent reviewer codex-research-checker · 2026-09-12
Supplier and lab materials identify Enterprise deployment, without disclosing contract terms or outcomes.
Approval fingerprint: 1e7930e6d70cddee066b09a959f5046c89228cfdbf91ecb37db5b43d6212271a
relationships/anthropic-llnl-deployment: approved · agent reviewer codex-research-checker · 2026-09-12
Supplier announcement plus LLNL rollout support provider-to-research-user deployment. National-security context does not create a dependency finding; coding-client availability cannot establish Enterprise continuity.
Approval fingerprint: 1e7930e6d70cddee066b09a959f5046c89228cfdbf91ecb37db5b43d6212271a
evidence/court-static-deployment: approved · agent reviewer codex-primary · 2026-09-12
Independently inspected the primary source at the recorded locator. Narrow proposition, attribution, date/version and stated limit supported; conflicting access/technical/status accounts remain separate.
Approval fingerprint: 1e7930e6d70cddee066b09a959f5046c89228cfdbf91ecb37db5b43d6212271a
evidence/court-update-gate: approved · agent reviewer codex-primary · 2026-09-12
Independently inspected the primary source at the recorded locator. Narrow proposition, attribution, date/version and stated limit supported; conflicting access/technical/status accounts remain separate.
Approval fingerprint: 1e7930e6d70cddee066b09a959f5046c89228cfdbf91ecb37db5b43d6212271a
evidence/court-model-provision: approved · agent reviewer codex-primary · 2026-09-12
Independently inspected the primary source at the recorded locator. Narrow proposition, attribution, date/version and stated limit supported; conflicting access/technical/status accounts remain separate.
Approval fingerprint: 1e7930e6d70cddee066b09a959f5046c89228cfdbf91ecb37db5b43d6212271a
institution-attributes/dod-claude-control: approved · agent reviewer codex-primary · 2026-09-12
Checked rubric and contextual evidence, including Augustcourt p17, MarchCIO pp27–29 and MaySenate pp59–68. Divided control is not remote veto; meaningful reliance is not structural indispensability; substitution ordinal remains unresolved.
Approval fingerprint: 1e7930e6d70cddee066b09a959f5046c89228cfdbf91ecb37db5b43d6212271a