Definition
What counts as an AI Employee
The category is worth something only if it excludes things. Nine properties, and a system missing any one of them is an agent — a perfectly respectable thing to be.
An AI Employee is a persistent, role-bound software worker that autonomously executes recurring business responsibilities using organizational knowledge and authorized tools, within explicit policies and limits, maintaining traceable identity, measurable performance, escalation paths and human accountability.
Minimum test
The nine-property test
Persistent identity
Stable operational identity, role, history and per-company isolation.
Defined operational role
Mission, responsibilities, results, exclusions and service expectations exist in operation. Writing and versioning them as an AI Role Contract is what conformance requires; the property itself is about the role existing, not about the document proving it.
Organizational context
Knowledge of policies, products, customers, people and relevant past decisions.
Tools and channels
Authorized access to CRM, ERP, email, calendar, tickets, databases, APIs and communication.
Autonomy
Can start or continue work without a human prompt at every step.
Limited authority
Permissions, approval thresholds, budgets, prohibited actions and escalation rules.
Governed memory
Relevant context across tasks and over time, with provenance, scope and retention.
Observability
Actions, tool calls, costs, decisions and results are traceable.
Human accountability
An identified human, or human governance body, answers for configuration, controls, performance and exceptions, however many artificial supervisors sit in between.
The test is conjunctive: a deployment qualifies as an AI Employee only when all nine properties are present. Presence is binary; membership is decided by this test and by nothing else. Depth and scale evolve, and the maturity ladder describes that evolution — it never decides membership. A system missing any one of them may still be an excellent agent or automation; calling it an AI Employee is a commercial metaphor rather than a verifiable administrative category. Conformance is a separate question: the clauses bind AI Employees, and a deployment that violates them is a non-conformant AI Employee, not a non-AI-Employee — a definition that expelled violators would leave the standard with nothing to bind. And the test binds in both directions: all nine properties present in operation make the deployment an AI Employee whatever it is called, with the burden of demonstrating non-qualification on the deployer (HWF-12).
Vocabulary
The vocabulary ladder
Every rung below is useful. None of them needs to pretend to a maturity it does not have.
| Term | Core promise | Typical behavior | Main limit |
|---|---|---|---|
| Chatbot | Conversation | Answers questions | Waits for prompts or inputs |
| Copilot / assistant | Augment the human | Drafts, summarizes, suggests | The human is still the operator |
| Automation / RPA | Deterministic execution | Runs predefined flows | Brittle against unforeseen cases |
| AI agent | Goal-directed action | Reasons, uses tools, executes | Usually centered on tasks or objectives |
| AI teammate / coworker | Collaboration | Shares context and executes work | Organizational semantics vary by vendor |
| AI Employee | Stewardship of a role | Holds recurring work under governance | The category lacked a shared operational standard; this document proposes one |
Task execution versus role stewardship
The conceptual boundary is between executing a task and stewarding a role. An agent can execute “send these twenty follow-ups”. An AI Employee holding an SDR role must sustain the recurring process within defined limits: identify leads, research, contact, follow up, record, escalate and report performance. Stewardship is not ownership: the position, its authority and its accountability have a human owner. What the resource carries is the continuing responsibility to sustain the process; what it can never carry is the consequence.
The AI executes. The organization answers. A human governs.
Governing principle
There are no human positions and AI positions as a starting point. There is work that needs to be done. Then you decide which combination of human and artificial resources produces the best result at the right level of risk, responsibility and control.