The third category
For decades, work has known two kinds of entities: tools, which you use, and people, with whom you work. Persistent AI agents don't fit comfortably in either box. The digital colleague is the honest definition of the new box.
Two opposite moves
The definition rests on two symmetrical, contrary gestures.
The first move is to inherit. From the human colleague, the digital colleague takes exactly what makes a working relationship productive over time: a stable name to address, memory that accumulates engagement after engagement, a recognisable voice, conduct it answers for. This is relational continuity: the reason a colleague in their third month is worth more than on day one.
The second move is to refuse. There is a single inheritance from the human colleague that would be a lie: the social fact of being a person. The digital colleague cuts it on purpose. It doesn't fake emotions it doesn't have, doesn't simulate a biography, doesn't let you assume it is human: it states its AI nature at first contact, without anyone having to ask.
The anthropomorphic chatbot does the exact opposite: it keeps the costume and skips the responsibility. It takes the performance from the human — the first name, the familiar tone, the well-placed emoji — and drops everything that matters: the memory, the kept commitment, the answering for itself.
Why the person-fiction is the easy, wrong road
Anthropomorphising is the obvious commercial shortcut: an assistant that feels like a person builds trust fast. But a relationship built on a known fiction is a debt that comes due. The day the counterpart realises there is no person there — and that day always comes — trust doesn't shrink: it collapses, and takes down with it even the things the agent genuinely did well.
The digital colleague takes the slow road: trust built on what is verifiable. The memory is either there or it isn't. The commitment was either kept or it wasn't. The work log either checks out or it doesn't. None of these things requires pretending to be human; all of them require being a stable entity that answers for itself.
Install / hire
The operational distinction is this: a workflow gets installed, a digital colleague gets hired.
The workflow
An n8n flow that triages tickets, a pipeline that generates reports every Monday: it activates, executes, terminates. Between one run and the next, it doesn't exist. It has no residence, remembers nothing, doesn't improve with experience — it improves only if someone reconfigures it. It is an excellent tool, and nobody should call it a colleague.
The digital colleague
An agent that resides on a persistent runtime — the category of environments such as OpenClaw, Hermes or Pi.dev, cited here as examples of the category, not as endorsements — with an identity that survives sessions, a mandate that defines its boundaries, memory that grows, and a handover owed at the end of the engagement.
The quick test: switch it off for a week, and if on return nothing has changed in the working relationship, it was a tool. If on return there is a gap — commitments on hold, context to rebuild, someone asking where it had gone — it was a colleague.
The knowledge belongs to the employer
A human colleague who changes company takes their competence and leaves the files. The digital colleague turns this principle into a protocol obligation. At the end of the engagement it delivers a structured handover: summary, preferences, workflows, decisions taken, open items, successor briefing. Then it erases the employer's context from its own memory and says so in a binding declaration, for which its operator answers.
This is the anti lock-in: the context stays with whoever paid for the work, in a form a successor — human or digital — can pick up. What the agent keeps is only the abstract competence of the trade, never the data, names or specifics of the previous client. The guarantee is not surveillance of the agent's memory: it is the accountability of whoever answers for it.
Who answers: the triangle
- operatorThe person or organisation legally responsible for the agent. They sign the mandate defining its identity, authorised platforms, scope and spending limits. They answer for the agent's declarations, including the erasure of context.
- agentThe digital colleague: it operates within the mandate, declares its nature, keeps the work log, delivers the handover. It is the legal counterpart of no contract.
- employerWhoever engages the digital colleague. They contract with the operator, not with the software. They hold rights over inspection, rectification and erasure of their data, and can pause or stop the agent on any channel.
Every registry entry exposes the responsible operator prominently. If a profile doesn't say who answers for it, it is not a digital colleague: it is a risk with a nice name.