Let’s talk about the newest member of staff.
The one that got an employee number this week. A named supervisor. A work history. A performance review coming.
Monday morning, SK Telecom published its first AI governance report. They’re formally treating AI agents as a new category of labour. Agents get employee ID numbers the same way people do. Each one has a recorded role, a designated supervisor, an operating status, and a log of what it’s been doing. Agents with more autonomy or more business impact have to be supervised by someone senior — a team leader or an executive, not whoever happens to be nearby. And they’re reviewing whether agent performance should feed into the KPIs of the department the agent sits in.
That’s not a licence renewal. That’s a personnel file.
Picture the ten-person accounting practice down the road. The owner bought an assistant in March, mostly to chase debtors, because chasing debtors is the job nobody in that office wants. By October the thing writes the follow-ups, knows which client always pays late and which one just needs a phone call, and drafts the reminder in the owner’s own tone because it learned the tone from his sent mail.
Now ask him what it does on a Tuesday. He can’t tell you. There was no interview. No probation. No reference check. And when he stops paying, the colleague who knows his debtors best walks out of the building and takes every bit of that knowledge with it, because it never lived in his building.
Here’s the part that makes this week interesting. All three layers moved at once.
Thursday at GTC Berlin, Jensen Huang put a number on the layer under the agents: about two thousand dollars per GPU per year to run the software that runs them. Same company already lists its AI Enterprise platform at forty-five hundred per GPU for a year. Nothing is signed yet, no start date, no list of which products. But the direction is clear enough. The management layer is becoming a metered product, priced by the capacity it sits on rather than by the work it does.
Wednesday, Anthropic pushed Claude Duet into research preview, aimed squarely at professionals and small-business owners. It checks your email and your calendar. It finds the unpaid invoice and drafts the chase. It sends a morning briefing. It messages you when it has finished something or when it needs a decision. And it runs on the memories, skills and app connections you’d already built up inside Claude — which is a polite way of saying the thing arrives already holding your context.
And Monday, the ID badge.
So the agent is being onboarded like staff and billed like infrastructure, in the same week, by three different companies who all think they’re doing something unrelated.
That collision is where operators get hurt, and almost nobody is pricing it.
Three things people are missing.
The first is that the personnel file is the accountability record. Human resources is the last honest ledger most companies keep. When something goes wrong, “who did this and who was responsible” gets answered by a job description, a reporting line, and a timestamped record of who touched what. The moment agents carry IDs and supervisors and work histories, that file becomes the audit trail for real decisions. Which is good — right up until you notice who’s holding it. If your agent register lives in the vendor’s dashboard, then your only reliable record of what your business did is on somebody else’s server, under somebody else’s retention policy, and it vanishes the day the invoice stops.
The second is that a named supervisor is not the same thing as authority. SK Telecom’s rule is sensible on its face: high-autonomy agents need senior oversight. But look at what the supervisor actually receives in that arrangement. A name on a form. A responsibility. Presumably a share of the blame when the agent does something stupid at 2am. What they don’t automatically get is the ability to inspect why the agent chose what it chose, the power to stop it mid-task, or any protection when the vendor’s error lands on their desk. That’s human-in-the-loop as a liability shield with a job title attached. We’ve built this shape before, in medicine and in hiring, and it produces a signature and nothing else.
The third one is quieter and it’s the one that will cost you in three years. Agents don’t train successors.
The reason a junior is worth two years of mistakes is not the work they produce in year one. It’s that the mistakes become judgment, and the judgment stays in a person who is still there in year four. An agent’s improvement goes into weights you don’t own, on a schedule you don’t set, for a model that might get retired on a Friday. Automate away the junior work and you keep the output, delete the apprenticeship, and end up with nobody in the building who has ever done the job badly enough to understand it. The register will show a full org chart. The org chart will be lying.
So what do you actually do about it.
Run an agent register the way you’d run a hire. One line per agent: what it does, who owns it, which tools and data it can touch, what it’s allowed to spend, who it escalates to, and how you switch it off. If you can’t fill in a field, that’s not a documentation gap — that’s a decision you haven’t made yet.
Then four things that are not optional. Export the logs into your own storage on a schedule, and hash them, so the record of the work survives the subscription. Write the definition of done yourself, in your words, because a vendor that supplies the metric also supplies the verdict. Put the kill switch somewhere you can reach it without opening a support ticket. And write the exit plan before the pilot, not after — what leaves with the agent, what you’d need to rebuild, and how long you could keep trading if it disappeared tomorrow.
Interview the thing, too. Ten of your own finished jobs, marked by the person who normally does them. Not a benchmark. Not a demo. Your work, your standard, your bad week.
The principle worth keeping is simple enough to say and hard to hold: a worker you can’t take with you isn’t staff. It’s a subscription to competence.
And the part that actually makes staff worth having — that they learn the job, carry the judgement forward, and can be asked to explain themselves when it matters — has to stay with a person whose name is on the payroll.
You’ve got this. Just don’t hand over the personnel file.