/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

OpenAI VP Anna Makanju says the company is developing tools with the US DOD on open-source software and held talks on ways to assist preventing veteran suicide

Bloomberg

Context & Ripple Effects

This early engagement marks OpenAI's movement from discussing discrete Defense Department use cases into a relationship that later included an agreement to deploy its models in the DOD's classified network.

The arc also shows why narrow initial applications matter: later coverage centers on negotiations over safeguards against domestic mass surveillance, making the permitted boundaries of DOD access as consequential as the technical collaboration itself.

First-order effects

  • OpenAI and the DOD begin jointly developing tools centered on open-source software, creating a direct operational collaboration between the lab and the department.
  • The companies' discussions on preventing veteran suicide put a sensitive veteran-support use case on the table, but the report describes talks rather than a deployed service.

Second-order effects

  • The collaboration gives the DOD a channel to shape requirements for OpenAI-built tools, while OpenAI must account for Defense use constraints and scrutiny around sensitive applications.
  • As the relationship broadens, the distinction between support-oriented uses and surveillance or intelligence uses becomes a practical contracting and governance issue rather than an abstract policy question.

Third-order effects

  • If this pattern persists, frontier-model providers will increasingly need explicit use-case boundaries and oversight terms to serve defense customers without treating all government access as equivalent.
  • The later push for surveillance protections suggests that defense AI partnerships may be governed as much by model-access controls and data-use limits as by the underlying software capabilities.

The trend: This is an early data point in the rise of the state-compatible AI lab, where commercial model companies build defense partnerships while negotiating the limits of acceptable government use.

Discussion

  • @carnage4life Dare Obasanjo on threads
    Within days of people noticing that OpenAI removed the ban on using its technology for “military and warfare” applications, it has confirmed it's working with the US military on multiple projects.  It's quaint that Google employees used to stage walkouts over the company working …
  • @samfbiddle Sam Biddle on x
    Also, “national security” is of course itself a far more broad concept than “military.” This indicates to me that OpenAI could be willing to sell to the US IC. Last year the National Geospatial-Intelligence Agency mused about using ChatGPT for analysis: https://theintercept.com/.…
  • @samfbiddle Sam Biddle on x
    And here comes the spin—selling software to the military is actually about *preventing* people from dying.