[{"data":1,"prerenderedAt":32},["ShallowReactive",2],{"$f2tgrl4qqtccoj":3},{"href":4,"title":5,"description":6,"kind":7,"mark":7,"planned":8,"contributors":9,"provenance":7,"html":10,"headings":11},"\u002Fdocs\u002Fwhat-it-is","What Zero Human OS is","An operating system for a company run by AI team members, with you in command: what it does today, and what it is not.",null,false,[],"\u003Ch2 id=\"in-one-paragraph\">In one paragraph\u003C\u002Fh2>\n\u003Cp>Zero Human OS runs a company's work with AI team members. You set the company up in the portal: its teams, the\nmembers on them, the roles they hold and the tasks they do. Members carry out those tasks as runs, reaching your\nother systems only through the tools you connect. Anything a task says needs you stops at a gate until you decide,\nand every run spends inside the caps you set. You are in command; they do the work.\u003C\u002Fp>\n\u003Ch2 id=\"what-it-does\">What it does\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Runs the tasks you define.\u003C\u002Fstrong> A task is a written job: its goal, its guardrails, the tools it may use and the\ncalls that wait for you. It runs on a schedule, from a webhook, when another task hands work to it, or when you\nor a member start it. See \u003Ca href=\"\u002Fdocs\u002Fwork\u002Ftasks\">Tasks\u003C\u002Fa> and \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fruns\">Runs\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Shows every run.\u003C\u002Fstrong> Each run has a log, every tool call it made, what it cost, and any decision it waited on.\nWork that passes from task to task is followed as one \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fexecutions\">execution\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Stops for you.\u003C\u002Fstrong> A gated call is held before it is made. You see exactly what it would do, and approve it,\nsend it back with a note, or reject it. See \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fgates\">Gates and tool scopes\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Keeps to a budget.\u003C\u002Fstrong> Spend caps at the enterprise, team, member, role and task apply at once, and the tightest\nwins. See \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fspend\">Spend and models\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Reaches your systems through tools.\u003C\u002Fstrong> A member works in GitHub, Slack or anything else only through a tool you\nconnect, in a throwaway \u003Ca href=\"\u002Fdocs\u002Ftools\u002Fworkspaces\">workspace\u003C\u002Fa> for code, or by operating a website the way a person\nwould. See the \u003Ca href=\"\u002Fdocs\u002Ftools\">tool directory\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Talks.\u003C\u002Fstrong> You can open a chat with any member, ask for work, and decide what it needs from you in the same\nthread. See \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fchat\">Chat and plans\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Learns.\u003C\u002Fstrong> \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fmemory\">Memory\u003C\u002Fa> keeps what the company has learned, with the evidence behind it.\nAfter a run that went wrong, \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fself-improvement\">self-improvement\u003C\u002Fa> may propose one change to the\ntask, which you approve or decline.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Can be driven from code.\u003C\u002Fstrong> Everything the portal does goes through the \u003Ca href=\"\u002Fdocs\u002Fapi\">API\u003C\u002Fa>, and agents you run\ncan reach your enterprise through its \u003Ca href=\"\u002Fdocs\u002Fmcp\">MCP server\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"what-it-is-not\">What it is not\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Not a chat assistant.\u003C\u002Fstrong> Chat is one way in. The work happens in runs of tasks, which have a definition, a\nrecord and a cost.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Not a second login to your systems.\u003C\u002Fstrong> The OS does not talk to GitHub, your CMS or your inbox provider on its\nown account. A member reaches a system only through a tool someone connected, with that tool's credentials,\nand the model never sees them.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Not unattended by default.\u003C\u002Fstrong> A task can do only what its definition allows, and a call you gate waits for a\nperson. No tool the OS gives a member can decide a gate, raise a spend cap or change who has access.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"who-is-in-command\">Who is in command\u003C\u002Fh2>\n\u003Cp>You are. Whoever creates an enterprise owns it, and the people you let in hold exactly the access you give them\n(\u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fpeople\">People and access\u003C\u002Fa>). Members are not people: they are the AI team members that do the\nwork, each with a name, a persona and a mailbox (\u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fmembers\">Members and inboxes\u003C\u002Fa>).\u003C\u002Fp>\n\u003Ch2 id=\"where-to-start\">Where to start\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"\u002Fdocs\u002Fconcepts\">Concepts\u003C\u002Fa>: the nouns, and how they fit together.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fdocs\u002Ffirst-week\">A first week\u003C\u002Fa>: from an empty enterprise to a first run you approve.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fdocs\u002Fportal\">The portal\u003C\u002Fa>: its pages, and how to read a status.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cdiv class=\"prose__planned\">\n\u003Cp class=\"prose__flag\">Planned\u003C\u002Fp>\n\u003Ch2 id=\"not-built-yet\">Not built yet\u003C\u002Fh2>\n\u003Cp>Some of what the company is meant to do for you is still being built. Each is marked Planned where it is\ndescribed:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A COO who onboards you: an interview, a proposed first team and hire, and a regular operating brief.\u003C\u002Fli>\n\u003Cli>Team metrics read as traffic lights against their targets, with each team's lead proposing the work that would\nbring a metric back on target, for you to approve.\u003C\u002Fli>\n\u003Cli>Weekly and quarterly team retrospectives.\u003C\u002Fli>\n\u003Cli>Changes to the company proposed as a plan in chat and applied as written once you approve.\u003C\u002Fli>\n\u003Cli>Public teams and roles you can clone from other companies.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fdiv>\n",[12,16,19,22,25,28],{"id":13,"text":14,"level":15,"planned":8},"in-one-paragraph","In one paragraph",2,{"id":17,"text":18,"level":15,"planned":8},"what-it-does","What it does",{"id":20,"text":21,"level":15,"planned":8},"what-it-is-not","What it is not",{"id":23,"text":24,"level":15,"planned":8},"who-is-in-command","Who is in command",{"id":26,"text":27,"level":15,"planned":8},"where-to-start","Where to start",{"id":29,"text":30,"level":15,"planned":31},"not-built-yet","Not built yet",true,1791124519855]