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.
Anthropic's April 23 report documents case studies on the malicious use of Claude. The cases include influence operations, credential-related activity, recruitment fraud, and a novice actor using artificial intelligence to advance malware development.
The details matter, but the report's most important feature is the loop it implies: observe abuse, interpret the pattern, change defenses, and share what others can use.
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.
Federal artificial intelligence (AI) policy changed substantially between 2024 and 2025. The need to know which systems government uses, who owns them, how they affect people, and what evidence supports them did not.
That is the enduring idea behind the Federal AI Governance and Transparency Act. Introduced as House bill H.R. 7532 in March 2024, the bipartisan proposal would have consolidated several federal AI governance requirements in statute. It directed agencies to create governance charters for certain systems, strengthened the Office of Management and Budget's government-wide role, expanded public visibility, and required contractors to provide information agencies would need for oversight.
Its most useful contribution was not a particular form or office. It was the recognition that accountable AI requires an institutional memory: a durable connection between the system, its public purpose, the decisions made about it, and the evidence available to challenge those decisions.
By the time a Freedom of Information Act request reaches an analyst, the hardest problem may already be years old.
The relevant records may be scattered across email, shared drives, case systems, collaboration tools, contractor environments, and personal filing habits. The request may cross several components with different search practices. Reviewers may need to reconstruct context that was obvious when the work occurred but disappeared when people moved on.
That is the operating reality behind the 2024 NextGen FOIA Tech Showcase. The Chief Freedom of Information Act (FOIA) Officers Council invited vendors to demonstrate artificial intelligence (AI), electronic discovery, search, case-processing, and redaction tools that might improve federal disclosure work.
The technology can help. It cannot repair missing records, unclear ownership, inconsistent retention, or a workflow no one has measured from end to end. If agencies treat FOIA as a document-processing problem that begins when a request arrives, they will automate the visible end of a much larger knowledge-management failure.
More orbital data does not automatically produce a better collision warning.
A useful warning depends on the quality and timing of observations, the model used to estimate an object's orbit, the uncertainty attached to that estimate, the way several sources are combined, and whether a satellite operator can act on the result. Two providers can observe the same object and produce different answers without either behaving irrationally.
That is what made a small 2024 procurement by the Office of Space Commerce (OSC) more interesting than the original announcement suggested. OSC, part of the National Oceanic and Atmospheric Administration (NOAA), hired Kayhan Space and SpaceNav to evaluate the accuracy, consistency, and quality of commercial space situational awareness (SSA) products created by three other companies. The work supported a limited pathfinder for the emerging Traffic Coordination System for Space (TraCSS).
The government was not only buying data. It was buying an independent way to learn which data and services were useful, under which conditions, and according to which evidence.