OpenAI's October 6 introduction of AgentKit includes a visual canvas for composing and versioning multi-agent workflows, a connector registry, interface components, and expanded evaluation tools. The release makes a useful class of artificial intelligence (AI) systems easier to see and assemble.
Ease of assembly should not be confused with absence of engineering.
The Department of Defense's (DoD) August 20 announcement realigns the Chief Digital and Artificial Intelligence Office (CDAO) under the Under Secretary of Defense for Research and Engineering (USD(R&E)). The stated goal is to accelerate artificial intelligence (AI) transformation by placing data, analytics, and AI closer to the department's broader technology enterprise.
Organizational charts matter. They establish authority, access, and incentives. They do not, by themselves, create adoption.
Anthropic's April 28 analysis of artificial intelligence (AI) use in software development finds that a substantial share of coding interactions appears automation-oriented. It also finds user-facing application work is common, suggesting some people use AI to build beyond their previous technical reach.
These are useful observations. They still do not tell a leader whether an engineering organization is more productive.
Students do not wait for an institutional operating model. They find a useful tool and fold it into the work.
Anthropic's April 8 Education Report analyzes roughly one million anonymized conversations associated with higher education. The study identifies four interaction patterns spanning direct and collaborative problem solving and output creation. It also finds that students frequently delegate analytical and creative work—not only routine recall.
Conversations about artificial intelligence and work often begin at the wrong level. They ask which jobs will disappear, then argue over forecasts that are too coarse to guide an actual organization.
Anthropic's first Economic Index, published February 10, analyzes how people use Claude across occupational tasks. The report finds usage concentrated in particular kinds of work and distinguishes between automation, where the model performs a task, and augmentation, where people and the model work together.
In late 2023, twenty civilian agencies reported roughly 1,200 current and planned uses of artificial intelligence. It was an irresistible number. Read quickly, it sounded like proof that artificial intelligence (AI) was spreading across the federal government at scale.
The U.S. Government Accountability Office (GAO) found something more complicated. Only five of the twenty agencies provided complete information for every reported use case. Two inventories included systems that the agencies later determined were not AI at all. Many entries lacked basic information such as lifecycle stage or whether the use could be publicly released.
The inventory documented attention. It did not establish adoption, readiness, value, or control.
That distinction remains important because federal AI inventories have continued to grow. The number of ideas in a spreadsheet will always rise faster than the number of capabilities that survive acquisition, integration, evaluation, workforce adoption, and sustained operation. Leaders need to know which kind of growth they are looking at.
A good artificial intelligence portfolio begins with permission to say that artificial intelligence (AI) is not the answer.
That sounds obvious. In practice, organizations often begin in the opposite place. A new model becomes available, leaders announce an adoption goal, and teams are asked to find use cases. The search produces a familiar list—summarization, forecasting, chatbots, anomaly detection, document review—before anyone has defined the mission problem, the current baseline, or the decision the system is supposed to improve.
The result may be technically interesting. It is not yet a strategy.
A federal AI use case should be written as a testable claim: for a defined group of people, performing a specific mission task under known conditions, this capability will improve a measurable outcome enough to justify its cost and risk. If the claim cannot be stated, challenged, and evaluated, the agency does not have a use case. It has a technology theme.