AI governance debate resumes

- Social threads debated AI as 'artificial unintelligence' and discussed agentic AI executing workflows. (x.com) - One post noted most agentic‑AI development currently involves standard software engineering, estimating about 90% code work. (x.com) - Commenters used the exchange to argue about limits of current models and when automation actually reduces human work. (x.com)

A fresh round of online debate over “agentic” artificial intelligence has shifted the argument from chatbot hype to who is responsible when software starts taking actions across real workflows. (nist.gov) In current industry usage, an AI agent is a system built on a large language model that can call tools, follow steps, and hand work between software systems instead of only answering a prompt. OpenAI says agents are designed to “coordinate tasks, connect tools, and adapt in real time,” while Microsoft describes agentic workflows as systems that gather context, route tasks, and trigger follow-up steps. (openai.com) (microsoft.com) That framing has fueled a backlash on social platforms, where posters argued that much of today’s “agentic AI” still depends on conventional engineering such as writing code, wiring tools, and defining guardrails. Anthropic said in a December 19, 2024 engineering note that teams often succeed with “simple, composable patterns rather than complex frameworks.” (anthropic.com) The policy fight has moved with the product shift. The National Institute of Standards and Technology’s Artificial Intelligence Risk Management Framework says organizations should manage risks across the design, development, deployment, and use of artificial intelligence systems, not just at the model layer. (nist.gov) International rulemakers have updated their language too. The Organisation for Economic Co-operation and Development revised its definition of an artificial intelligence system on November 8, 2023 and amended its AI recommendation again on May 3, 2024 to reflect generative and general-purpose systems. (oecd.org) That matters for the current argument because agents blur the line between a model and the software wrapped around it. Google’s cloud architecture guidance says building agentic applications requires choices about orchestration, tools, memory, evaluation, and changing workload requirements, which puts ordinary software design at the center of the system. (docs.cloud.google.com) The dispute is also about labor, not just terminology. Microsoft’s business guidance pitches agentic workflows for routine work and error reduction, while NIST’s framework warns that artificial intelligence systems can create risks for people, organizations, and society if they are poorly governed. (microsoft.com) (nist.gov) Developers building these systems are being told to stay narrow. Anthropic’s tool-writing guidance says better agent performance often comes from careful tool selection, clear boundaries, and systematic evaluation rather than simply adding more autonomy. (anthropic.com) The result is a governance debate that now sounds less like a fight over whether models can talk and more like a fight over how much real work they can safely do. The louder the claims about autonomous workflows get, the more the argument turns back to engineering choices, human oversight, and who answers when the system fails. (oecd.org)

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.