The day software started talking to software

What we're tracking

• •When half the traffic is not a person Most communication tools were designed around a simple assumption: a message has a human sender. Permissions, notifications and audit trails all lean on that idea. When a share of the messages in a channel start coming from automated agents, the assumption quietly breaks. You are no longer only managing conversations between colleagues. You are managing a space where code posts, reads and reacts alongside people.
• •Governance of what a meeting leaves behind A video call used to be ephemeral. Now a single meeting can produce a recording, a transcript and a set of AI-generated notes, and each of those is a data object that lives somewhere, under some policy, visible to some people. Many organisations have never written that policy down, which means the default behaviour of the tool becomes the policy by accident.
• •The cost sitting behind the agents Automated agents and AI notes do not run on nothing. They run on model providers, and the economics of those providers are now part of your supply chain whether you contract with them directly or not. When a vendor you depend on raises prices or changes terms, the cost flows down to you.
• •When commercial demand overtakes the original customer A company's revenue mix tells you who it is really built to serve, and that mix shifting is a signal about the wider market. TechCrunch reported that Palantir's U.S. commercial revenue surpassed its U.S. government revenue for the first time [4]. A firm long associated with the public sector now earns more from ordinary businesses.
• •One maintainer, one assistant Not every item today is about scale. GitHub described a project that turns any place on Earth into a Minecraft world, built by one person, where GitHub Copilot now helps him maintain it alone [5]. On its own it is a small story. As a pattern it is worth noticing.
• •What to take from the day The common thread is that the actor on the other side of your software is increasingly not a person. That raises governance questions in your chat tool, in your meetings, in your cost base and in the small projects you quietly depend on. None of it argues against adopting these tools. It argues for adopting them with the record, the policy and the exit intact. For the previous day's reading, see yesterday's briefing.