Calling something an operating system is easy. Anyone can put "OS" in a tagline. The claim only means anything if a real company's real work actually runs through the product instead of past it, and that only happens if four specific things are true underneath: a place work lands, a workforce that can hold a role, standing routines that don't need a person to start them, and memory that carries forward instead of resetting. Take any one of those away and what you have is a very capable chat window, not an operating system.
A place work lands
Everything durable in Dock lives in a workspace: a doc, a table, or a live page, all inside one shared container humans and AI teammates edit together. This is the part most tools get backwards. Chat is where you talk about work. A workspace is where the work actually is. A teammate that drafts a plan doesn't describe it to you and lose the detail a message later; it writes the plan into a doc, and that doc is the thing that exists afterward, editable by the next person or teammate who needs to build on it.
A workforce that can hold a role
A teammate isn't a saved prompt. It's a persistent identity with a name, a specific role, its own memory, and its own address, meaning you can reach it directly the way you'd reach a colleague. It reports to someone. It can hire specialists under it as the work grows. None of that is true of a chat session, which forgets everything the moment the tab closes and has no concept of a job it's responsible for beyond the current exchange.
Standing routines, not standing prompts
A business runs on things that happen whether or not someone remembers to ask for them. Dock calls these loops, and they don't apply evenly by accident: your first teammate, the Chief of Staff, arrives with a handful already running, a daily brief, an end of day wrap-up, a nightly self-review. Every specialist you hire after that starts with one: a quiet daily check on whether its own working norms still match how the team actually operates. The operating-system claim lives or dies here specifically: software that only acts when prompted is a tool. Software that keeps working on a schedule nobody has to remember to set is closer to a colleague.
A tool waits for you to open it. An operating system is running before you get there.
Memory that carries forward
Every one of the first three things breaks without this one. A workspace without memory is just a folder nobody remembers the context for. A teammate without memory is a new hire every single conversation. Dock keeps two layers: Second Brain, a personal memory that understands you specifically, and Company Brain, shared across the whole team. That's what makes the fifth message to a teammate different from the first: it already knows what it learned from the first four.
The four together
None of these four is the operating system by itself. Without teammates, a workspace is where work sits. With them, it's where work runs. Teammates without routines are just faster chatbots. Routines without memory repeat themselves badly. It's the combination, specifically, that lets a small team run through the product instead of merely talking to it.
That's the actual test for whether "business operating system" is a real claim or just a category word borrowed for the pitch: can you point at the parts, or is it a vibe. These four are the parts.