Onboarding a Person, Onboarding an Agent
Start Here
The single decision that made this project tractable was to stop asking “how do I configure an AI?” and start asking “how would I onboard a new person?”
Everything else in this blueprint follows from that. Not as a metaphor — as a checklist I already knew how to write.
The two lists are the same list
Section titled “The two lists are the same list”When you onboard a colleague, you do a specific set of things. Every one of them has a direct equivalent.
| What you give a new employee | What you give an agent | Step |
|---|---|---|
| A name and a work email address | Its own name, and its own mailbox — not an alias of yours | 1 · 2 |
| A desk and a computer | A dedicated machine that stays on, with its own user account | 3 |
| Accounts and software access | Its own credentials for the calendar, mail, lists and tools it needs | 4 · 5 |
| A permission level — what they may approve, spend or sign | The permission layers, its own credentials, and hard limits it cannot cross | 6 |
| A written role and reporting line | A job description, and a clear line about what it brings to me | 7 |
| A way to talk to the team | Channels the household already uses, addressed by name in groups | 8 |
| Access to the files and context they need | Memory and a wiki it can read, and that I can read back | 9 |
| A manager who reviews the work | Approval gates, and a person on anything irreversible | 6 |
| A probation period | The first week of watching, then tuning what it says and when | The Build Order |
| A handbook | The operating rules file loaded before every conversation | 1 |
Read that table down the left column and it is an ordinary onboarding. Read it down the right and it is a technical project. They are the same work.
You give them access. You give them a computer. You give them a role. That is the whole thing — and it should not be difficult for an agent, because you already know how to do it for a person.
Why the framing works so well
Section titled “Why the framing works so well”It forces the right questions. Software thinking asks what features do I want? Onboarding asks questions that actually matter: who is this? What may they decide alone? What must they never do without asking? Who do they answer to? Every one of those became a real design decision in my setup, and I would not have asked any of them otherwise.
It gives you an order. Nobody gives a new hire system access before they exist as a person in the organisation. Identity first, then a machine, then access, then the work. That order is the spine of this whole blueprint, and it is not arbitrary — it is how the dependencies actually run.
It gives you a bar for success. Would I give this to a new colleague on their first week? That question resolves most permission arguments in seconds. If you would not hand a new hire the ability to send mail as you, do not hand it to an agent.
It sets the stakes correctly. A new colleague does not need to be trusted blindly on day one. They start with limited access, prove themselves, and earn more. An agent is the same. You do not have to get it all right up front.
What an agent needs less of
Section titled “What an agent needs less of”Worth saying plainly, because it cuts against the instinct that this is exotic and difficult.
| A person needs | An agent needs |
|---|---|
| A salary and a contract | Nothing |
| Physical space, a desk, a chair | None — it lives on one small machine |
| Training on how your household works | A few pages of files, read before every conversation |
| To be told things twice | It remembers, if you set memory up |
| Sleep | Not applicable — it works while you do |
| Notice, handover, a replacement | A backup, restored in about an hour |
It is genuinely less work than onboarding a person. No payroll, no desk, no induction, no small talk about the weather.
What is harder than a person
Section titled “What is harder than a person”Two things, and they are worth knowing before you start.
You cannot have a quiet word with it. With a colleague, you say “don’t do that again” and it lands. With an agent, a correction only sticks if you change its access or correct its memory. Anything else is a hope. That is why Step 6 is enforceable by access rather than by instruction, and why memory records what you said rather than what it concluded.
Revocation is total and mechanical. Removing a person’s access is a conversation. Removing an agent’s is one credential, and you had better know which capability it carried. Hence the capability map.
The point
Section titled “The point”It should not be difficult. If you can onboard an employee — give them a name, a computer, access, a role, and someone to answer to — you can onboard an agent, because it is the same list with fewer items on it.
What you cannot skip is the rigour. With a new colleague, a missed step is a bad week. With an agent, a missed step is a permanent capability, because nobody gets tired and nobody forgets. That is the only reason this blueprint is careful — not because the work is hard, but because it does not wear off.