Writing
Notes on AI employees
64 pieces for operators on one-process builds and the parts that still need a person. RSS
· Foundations
AI employee FAQ
The questions people actually type, answered the way I answer them on a thirty-minute call.
· Foundations
What an AI employee actually is
An AI employee is a named worker for one written process, not a chat box with a job title.
· Foundations
AI employee vs chatbot
A chatbot answers. An AI employee finishes a job and leaves a record you can audit.
· Foundations
What changed about AI agents in 2026
More agents sat in real workflows in 2026. Governance did not catch up. Owners still matter.
· Foundations
What an AI employee cannot do
It cannot invent policy, close harm alone, or sit outside the law. Drafting is not deciding.
· Foundations
When not to hire an AI employee
If the process is folklore, the stakes have no gate, or nobody owns misses, do not hire yet.
· Foundations
One process, not a platform
Hire one written process. A platform is a year. A queue is a week.
· Foundations
Human in the loop is the job
The person on the gate is not a fallback. They are the job you actually hired.
· Foundations
AI employee vs copilot
A copilot sits next to a person. An AI employee owns the queue when the person is not there.
· Foundations
AI employee vs RPA
RPA repeats a click path. An AI employee reads messy input and still has to stop at a gate.
· Foundations
How to explain an AI employee to your board
Tell the board it is one worker, one process, a cost, an owner, and a gate. Not a platform.