Pentagon adds ‘ideological neutrality’ guidance to AI purchasing

The Pentagon has given its AI buyers templates and contract language to enforce the White House’s “truth-seeking” and “ideological neutrality” directives. An October 20, 2026, memorandum makes the distinction explicit: compliance is mandatory, while acquisition teams can tailor the paperwork to the context and risk of each purchase, DefenseScoop reported.

John Tenaglia, the principal director for Defense Pricing, Contracting, and Acquisition Policy, sent the guidance to acquisition leaders across the Army, Navy and Air Force. Recipients also included U.S. Special Operations Command, U.S. Cyber Command, U.S. Transportation Command, and Defense Department agencies and field activities.

The standard comes from the White House

The memo implements earlier policy rather than setting out a separate definition of acceptable AI behavior. Tenaglia described it as supporting President Donald Trump’s executive order, “Preventing Woke AI in the Federal Government,” and an Office of Management and Budget memo titled “Increasing Public Trust in Artificial Intelligence Through Unbiased AI Principles.”

Trump’s executive order, issued in 2025, requires large language models—the text-generating AI systems covered by the directive—to respond truthfully to requests for facts or analysis. It calls for historical accuracy, scientific inquiry and objectivity. It also requires models to acknowledge uncertainty when reliable information is incomplete or contradictory.

The order pairs those accuracy requirements with a political-content standard. It says models must not manipulate responses to favor ideological positions such as diversity, equity and inclusion, or DEI. Developers must not intentionally encode partisan or ideological judgments into outputs unless those judgments are prompted by, or otherwise readily accessible to, the user.

It is designed to be flexible, allowing DoW Components to tailor the language to fit the specific context and risk level of their individual AI acquisitions

John Tenaglia, October 20 memorandum. DoW is the administration’s preferred name for the Defense Department.

Three documents carry the rules into a purchase

The new guidance supplies three attachments for contracting and program staff. Together, they address different stages of an acquisition: choosing what transparency to require, telling prospective vendors what evidence to submit, and putting obligations into the contract. The templates are intended to document, solicit and enforce compliance with the administration’s principles.

• A memorandum for the office requesting the purchase selects the appropriate transparency requirements for that acquisition.
• Standard solicitation language tells vendors which documents they must provide to demonstrate compliance.
• Formal contract language can be included in a Statement of Work or Performance Work Statement, which describes the contractor’s required work, in solicitations and final contracts.

Tenaglia’s memo also recommends that contracting language define key terms and clearly explain submission requirements. Providing the relevant documentation should be a formal part of the proposal process, placing the compliance evidence alongside the vendor’s bid rather than leaving it as an informal exchange.

A supplier’s access to evidence matters

For a large language model purchase, an attachment requires the Pentagon to obtain enough information from the contractor to determine compliance with the executive order. But it recognizes that contractors will not all have the same information available to them.

The amount and type of evidence depend on the contractor’s place in the software supply chain and its relationship with the model developer. Sources closer to the original developer will generally have more information, the attachment says. That distinction makes the supplier’s relationship with the developer relevant to the documentation buyers can obtain.