Skip to content

INDEPENDENT RESEARCH / PRACTICE NOTES

Ideas in motion, not ideas behind glass.

This is my working notebook on AI engineering, strategy, knowledge infrastructure, organizational transformation, and the human systems that determine whether innovation becomes real capability.

The notes range from emerging research questions to practical operating models. Some will become papers, tools, talks, or products. Others are here because thinking improves when it is made visible.

Evidence before theater Systems over slogans Useful, accountable AI

Subscribe via RSS Follow Field Notes in any feed reader

Latest writing

Innovative Tech on Display: ONR-Backed Event Spotlights Platforms to Aid USMC’s Mine Countermeasures

ONR-Sponsored Event Displays Innovative Technology for U.S. Marine Corps’ Operations

In an event supported by the Office of Naval Research (ONR), various technologies aimed at bolstering the capability of the U.S. Marine Corps were exhibited. These tech platforms are designed to enhance mine countermeasures, intelligence, surveillance, reconnaissance, and other amphibious undertakings. The original article can be found here .

Cyber Disclosure Is a Decision Architecture

The Securities and Exchange Commission’s cybersecurity rules are often summarized through a deadline: a public company generally must file a Form 8-K within four business days after determining that a cybersecurity incident is material.

The operative phrase is not “four business days.” It is “after determining.”

A company cannot make a timely, defensible materiality decision if technical telemetry, business context, legal judgment, operational impact, and executive authority remain in separate systems and organizations. The disclosure rule therefore reaches deeper than reporting. It tests whether the company possesses a coherent decision architecture for cyber risk.

Scaling Trustworthy AI in Government Requires an Operating System

Originally published in 2024; substantially revised in 2026 to deepen the analysis and incorporate additional sources.

Government agencies do not lack AI ideas. They lack repeatable mechanisms for turning a promising use case into a capability that can be evaluated, authorized, adopted, monitored, and improved.

The usual response is to scale the technology: add compute, models, data pipelines, or platform capacity. Those investments matter. But when every program defines its own risk process, evidence package, human-oversight model, security interpretation, and approval path, the organization scales experimentation while preserving the bottlenecks that prevent adoption.

Trustworthy AI scales when the enterprise standardizes the work around the model—not merely access to the model.

The Defense Department Does Not Need More Data—It Needs Decision-Ready Data Products

The Office of the Under Secretary of Defense for Research and Engineering’s 2024 “Unleashing Data at Speed and Scale” outreach asked industry for technologies spanning collection, storage, processing, monitoring, analysis, and communication. The breadth reflected a real challenge: modern military decisions depend on data moving across sensors, networks, computing environments, organizations, classifications, and national boundaries.

It also exposed a recurring acquisition risk. When a problem is described as a list of technical functions, industry responds with products optimized for individual layers. The Department can acquire faster links, larger stores, stronger processors, and more sophisticated models while the mission thread remains fragmented.

The organizing object should be neither the technology nor “the data.” It should be a decision-ready data product with an accountable owner, defined consumers, observable quality, and a mission outcome.

A Policy Change Is Not a Defense Partnership

Revision note, July 17, 2026: The original version of this essay overstated the public record. I have not found an official January 2024 announcement of an OpenAI–Department of Defense cybersecurity partnership. What was publicly visible at the time was a change to OpenAI's usage-policy language and secondhand reporting about exploratory national-security work. OpenAI's first official announcement identified in this review of a Department of Defense pilot involving proactive cyber defense was published in June 2025. The analysis below corrects that distinction and develops the more important lesson it exposes.

In January 2024, changes to OpenAI's usage policies generated headlines suggesting that the company had opened the door to military work. The original version of this post converted that signal into a much stronger claim: that OpenAI and the Department of Defense had announced a cybersecurity collaboration at the World Economic Forum in Davos. That conclusion was not adequately supported.

The historical reporting that prompted the post described OpenAI's removal of a categorical reference to “military and warfare” from its prohibited-use language and discussed comments about possible cybersecurity applications. OpenAI's own policy changelog records a January 10, 2024 update, but a policy revision is not a contract announcement, an authority to operate, a fielded capability, or evidence of an operational partnership. The original GovCon Wire article remains useful as a record of how the change was interpreted at the time; it is not sufficient evidence for the claim this essay originally made.

That correction is more than editorial housekeeping. It reveals a recurring error in public-sector technology analysis: collapsing a chain of materially different institutional events into a single word—adoption.

Data at Speed and Scale Is a Control Problem

Calls for defense technologies that can collect, store, process, monitor, analyze, and transmit data at scale naturally attract products that maximize one dimension: sensor volume, link capacity, database throughput, analytic speed, or model performance.

Mission systems do not win by maximizing any of those quantities independently. They win by preserving a useful relationship between a changing environment and an accountable decision.

That makes data at speed and scale a control problem. The system must sense, estimate, decide, act, observe the result, and adapt—while delays, uncertainty, adversaries, and limited resources affect every stage.

Do Not Buy a Data Platform; Build a Data Capability Market

When the Department of Defense asks industry for technologies covering collection, transport, storage, processing, monitoring, and analysis, it encounters a predictable commercial response: every vendor explains why its platform should become the center of the architecture.

The Department’s problem is not a lack of platforms. It is the cost of composing capabilities across programs, vendors, clouds, classifications, and missions. Selecting another comprehensive product may solve a local integration problem while creating a larger dependency.

The alternative is not to build everything internally. It is to create a data capability market: a governed environment in which products can compete at stable architectural seams and must demonstrate evidence against shared mission threads.

READER-NEUTRAL SUBSCRIPTION

Follow Field Notes via RSS.

Copy this address into the RSS reader you already use. New notes will appear there automatically—no account, email address, or tracking required.

Open the feed