Referred to the House Committee on Armed Services.
The bill requires the Department of Defense to structure cloud, data infrastructure, and foundation-model procurements to promote competition, security, interoperability, and multi-cloud approaches. It mandates that the Government retain exclusive rights to access and use Government data and directs DFARS updates prohibiting vendors from using Government-furnished data to train commercial AI without authorization.
Progressives emphasize anti‑monopoly and data protections
Relative to its intended legislative type, this bill establishes substantive procurement and data‑rights requirements for DoD engagements with cloud, data infrastructure, and foundation model providers, and it builds in reporting and limited exemption mechanisms.
The bill requires the Department of Defense to structure cloud, data infrastructure, and foundation-model procurements to promote competition, security, interoperability, and multi-cloud approaches.
It mandates that the Government retain exclusive rights to access and use Government data and directs DFARS updates prohibiting vendors from using Government-furnished data to train commercial AI without authorization.
The bill creates penalties and limited national-security exemptions, and it requires annual reports to Congress assessing competition, market concentration, and granted exemptions.
Moderate chance: technically focused and defensible, with pathways via defense authorization; industry resistance and Senate thresholds lower probability.
Relative to its intended legislative type, this bill establishes substantive procurement and data‑rights requirements for DoD engagements with cloud, data infrastructure, and foundation model providers, and it builds in reporting and limited exemption mechanisms. It includes several useful definitions and assigns implementing authorities, but leaves key operational, fiscal, and enforcement details to subsequent rulemaking or guidance without deadlines or resource provisions.
Progressives emphasize anti‑monopoly and data protections
These are examples from the analysis, not a ranked list of the most-affected groups.
Progressives emphasize anti‑monopoly and data protections
Overall supportive: the bill restrains concentrated tech power, protects government data, and promotes competition and small-business access.
It aligns with priorities to preserve public-sector control over data and reduce vendor lock-in.
The persona would push for strong enforcement, transparency, and limits on exemptions to protect civil liberties and public accountability.
Generally receptive but pragmatic: the bill advances competition and data protections while preserving national-security exceptions.
The persona sees benefits for cost control and resilience but worries about procurement complexity, implementation cost, and operational impacts.
Support will depend on clear implementation plans, cost estimates, and safeguards against unnecessary program delays.
Skeptical: the bill imposes prescriptive procurement requirements and data ownership rules that could deter vendors and slow defense acquisition.
While competition is a stated goal, the persona fears expanded bureaucracy, weakened IP incentives, and overreach into private-sector contracts.
Support might be possible if national-security exemptions are robust and implementation minimizes program risk.
Reached or meaningfully advanced
Reached or meaningfully advanced
Still ahead
Still ahead
Still ahead
Moderate chance: technically focused and defensible, with pathways via defense authorization; industry resistance and Senate thresholds lower probability.
The bill has not accumulated any surfaced votes yet.
Progressives emphasize anti‑monopoly and data protections
Moderate chance: technically focused and defensible, with pathways via defense authorization; industry resistance and Senate thresholds low…
Relative to its intended legislative type, this bill establishes substantive procurement and data‑rights requirements for DoD engagements with cloud, data infrastructure, and foundation model providers, and it builds in…
Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.