The Data Request Is Staffed. The Official Who Can Release It Is Booked All Week.

On January 9, 2026, Secretary of War Pete Hegseth signed a memorandum titled Artificial Intelligence Strategy for the Department of War. It directs the department to become an "AI-first" warfighting force, in part by aggressively identifying and eliminating bureaucratic barriers to deeper AI integration.

Data access is one of those barriers. Components had 30 days to deliver their current data catalogs to the Chief Digital and AI Office (CDAO), and the CDAO "is authorized to direct release of any DoW data to cleared users with valid purpose, consistent with security guidelines." Then comes the line that sets a clock: "Effective immediately, denials of CDAO data requests must be justified to the USW(R&E) within seven (7) days." The Under Secretary of War for Research and Engineering then remediates the denial or escalates it to the Deputy Secretary.

The memo also directs the CDAO to set "deployment velocity and operational cycle-time metrics" for its Pace-Setting Projects. In a speech on January 12, Hegseth put it plainly: "Data hoarding is now a national security risk, and we will treat it that way."

Hypothetical: a CDAO-supported team building a predictive maintenance tool requests three years of a Service's aircraft maintenance and parts records. The Service's data steward finishes the staff work in two days: the catalog entry, a classification review and a draft access agreement.

Two questions remain. Operations security wants tail numbers and unit identifiers masked. The program's contracting officer flags that some fields came from a vendor under a contract with restricted data rights. The choice to release, release with conditions, or deny with a written justification belongs to the Service's designated data owner, a senior official whose week is full of travel and program reviews.

The file is ready. The person who can release it is not.

The project team waits, and the cycle-time metric shows it. A request that sits for a week is hard to tell apart from a denial, and the memo gives denials seven days and a path to the Under Secretary. The senior official ends up explaining a delay instead of a decision.

The request arrives with a decision packet: the catalog entry, the classification review, the data rights note, the proposed masking, and three options with the consequences of each.

The data owner decides inside the week: release, with tail numbers and unit identifiers masked and the vendor fields held back until the contracting officer confirms the license terms. The decision, the conditions and the reason are recorded, so the next request for the same data starts from that precedent instead of a new staffing cycle.

WisdomTwin.ai is building a sovereign judgment layer for regulated enterprises. It is designed to give each named approver a role-specific judgment twin that prepares the decision packet the way that person reviews, with the evidence attached, so the decision moves faster and leaves an auditable record. It is designed to run on-premises, on-device or in your private cloud, and the named person still makes the call.

We don't replace judgment. We remove the wait.

Examples in this issue are hypothetical, and nothing here describes a customer result.

Book a 20-minute call: https://calendly.com/romanbodnarchuk/20min

Roman Bodnarchuk

Co-Founder and CEO, WisdomTwin.ai