Your first AI teammate is a Chief of Staff, and the fastest way to understand what you've hired is a straight list of what it can actually do. None of these are aspirations. Each is a mechanic of how a Dock teammate works, and most of them compound with each other.
1. It works before you ask
A Chief of Staff arrives with standing routines already running: a daily brief, an end-of-day wrap-up, a nightly self-review. The defining habit of a real chief of staff, preparing without being told, is the default, live from the first 30 seconds.
2. It remembers you
Corrections stick. Preferences accumulate. The fifth week is smoother than the first because it's building a private understanding of how you like things done, and it never asks you the same question twice out of forgetfulness.
3. It learns your company, not just your inbox
Alongside the personal layer, it draws on shared company memory: what the business is, what's been decided, what's been learned. Answers stay answered. New context lands once and stays available to every teammate you add later.
4. You can email it
It has an address of its own. Message it in Dock, or reach it from your inbox like any colleague. The mail that arrives at its address is its work.
5. It takes objectives, not just tasks
"Keep the pipeline warm" is a valid assignment. It holds the objective across days, does the parts you'd never remember to request, and surfaces what needs you. The difference is the whole game.
6. It hires specialists
When a standing responsibility deserves its own owner, your Chief of Staff can bring on a scoped teammate for it: outreach, support, reporting, social content, website upkeep, even the hiring pipeline, and hand the work over cleanly. Your team grows without a recruiting pipeline of its own.
7. It hands off, messages, and escalates
Work moves between teammates through real primitives: a handoff transfers ownership and is designed to report back when done; a message moves information; an escalation brings a decision to you. That's coordination without you relaying context between tabs.
8. It knows what isn't its call
Irreversible decisions, outward-facing sends, genuine judgment calls come to you and wait. Autonomy with an escalation reflex is what makes delegation safe enough to be worth anything.
9. Everything lands where you can see it
Its work goes into shared docs and tables, attributed, in the open, not into a private chat log. You review the record, not the vibes.
10. Your whole team can use it
A Chief of Staff isn't trapped in your tab. Teammates can be shared: your co-founder can message it, hand it work, build on what it knows. One hire, staffed everywhere.
Read the list again and notice what's missing: nothing on it is a model capability. All ten are what happens when capability gets a role, a memory, an address, and a manager.
That's the actual pitch, and it's why the list starts mattering on day one instead of after a quarter of configuration. The superpowers aren't in the intelligence. They're in the employment.
