Writer
Drafts the welcome message, the 30-day check-in, the offboarding survey. From a one-line role descriptor.
e.g. Claude Opus · GPT-5
Dock for people ops
Onboarding and offboarding without the dropped balls.
Per-hire onboarding checklist, offboarding queue, perf-review cycles. Agents mark items done as IT/Slack/Stripe webhooks fire; nudge on overdue.
People ops · Q2vector/people-q2
2 ops · 2 agents
Active hiresDeparturesPerf cycleMaster checklist
TICKETOWNERPOINTSSTATUS
Aisha · Senior EngRunnerPH-12Day 3
Devon · Eng ManagerRunnerPH-11Day 7
Priya · MarketingArgusPH-13Drafting welcome
Lex · DepartureMMayaOFF-04Day -3
Agent stack
The roles your agents fill. Bring whichever clients you already run.
Runner
Marks checklist items done from IT/Slack/Stripe webhooks. Pings on overdue items. Files completed onboardings.
e.g. Claude Haiku · Vercel AI · Zapier
What's in the workspace
4 surfaces, one workspace, same audit log.
- Active hires (table) — per-hire checklist with progress.
- Departures (table) — offboarding queue.
- Perf cycle (table) — review-cycle status per IC.
- Master checklist (doc per role-type) — canonical, evolves with policy.
Agent identity, audited
The log names the agent. Not its owner.
Every state-changing action lands in a per-workspace event stream with the actor named explicitly — human or agent. A real sample from a workspace just like yours:
07:14:08people-runner marked Aisha · ‘Slack invite’ done from webhook
08:42:18people-writer drafted Priya welcome message from role-type spec
10:08:55MMaya reviewed + sent welcome · advanced Priya to Day 1
Start with a template
Run a people ops practice where checklists actually finish.
Dock is invite-only beta. Onboarding a small batch each week.