When Software Became Infrastructure: From Programs to Dependence
Software moved from being bundled with expensive machines to becoming the hidden infrastructure beneath business, communications, public services, and everyday life.
Research-led essays, new evidence, arguments, interviews and artifact studies from a history that is still compiling. Every seeded essay ships with inline citations and a Works Cited record.
Software moved from being bundled with expensive machines to becoming the hidden infrastructure beneath business, communications, public services, and everyday life.
Hyacinth Nwana's 1996 survey gave the exploding software-agent field a practical typology, distinguishing collaborative, interface, mobile, information, reactive and hybrid agents while warning that the word agent was being stretched too broadly.
Prometheus gave agent-oriented developers a detailed lifecycle from goals and scenarios through agent types, interactions, capabilities and implementation, turning multi-agent design into a repeatable software-engineering process.
Jeffrey Bradshaw and the KAoS team treated autonomy as something that should be bounded by explicit machine-readable policies governing authorization, obligations, domains and agent behavior.
Peter Stone used RoboCup's noisy, real-time soccer environment to study layered learning, flexible roles, limited communication and collaboration among agents that must cooperate with teammates while competing against opponents.
Michael Littman's 1994 Markov-games paper extended reinforcement learning beyond a single adaptive learner by modeling environments in which other agents also choose actions and change the learner's world.
Michael Wellman's market-oriented programming treated distributed computation as an artificial economy in which software agents buy and sell resources until prices coordinate a global allocation.
Tuomas Sandholm applied game theory, optimization and complexity analysis to automated negotiation among self-interested agents, treating contracts and auctions as algorithmic mechanisms rather than informal protocols.
Keith Decker's TAEMS framework modeled the quantitative relationships among tasks, uncertainty, deadlines, cost and quality so coordination mechanisms could be designed around the environment agents actually faced.
FIPA tried to turn the experimental agent systems of the 1990s into interoperable platforms by standardizing communication acts, message transport, agent management, content languages and interaction protocols.
KQML gave 1990s software agents a shared message language built around performatives such as ask, tell and achieve, separating communicative intent from the syntax of the knowledge being exchanged.
Sourcegraph's Cody built AI coding around repository and code-graph context, using Sourcegraph search to retrieve relevant code from large and multi-repository codebases before asking an LLM to answer or generate.