[{"data":1,"prerenderedAt":259},["ShallowReactive",2],{"$f56y76dj165nv":3},[4,11,16,21,26,31,36,41,46,51,56,61,66,71,77,82,87,92,97,102,107,112,117,122,127,132,137,142,148,153,158,163,168,173,178,183,189,194,199,204,209,214,219,224,229,234,239,244,249,254],{"href":5,"title":6,"description":7,"kind":8,"mark":8,"planned":9,"contributors":10,"provenance":8},"\u002Fdocs\u002Fapi","The API","The HTTP API behind the portal: what it is, how to call it, and what a token can reach.",null,false,[],{"href":12,"title":13,"description":14,"kind":8,"mark":8,"planned":9,"contributors":15,"provenance":8},"\u002Fdocs\u002Fapi\u002Fauthentication","Authentication","API tokens: one credential per use, scoped to what it needs, and revocable on its own.",[],{"href":17,"title":18,"description":19,"kind":8,"mark":8,"planned":9,"contributors":20,"provenance":8},"\u002Fdocs\u002Fapi\u002Fconventions","Conventions","What every call has in common: requests and responses, errors, pagination, and which writes are safe to send twice.",[],{"href":22,"title":23,"description":24,"kind":8,"mark":8,"planned":9,"contributors":25,"provenance":8},"\u002Fdocs\u002Fapi\u002Fendpoints","Endpoints","Every route an API token can call, by resource, with the scope it needs; and the few that only the portal can.",[],{"href":27,"title":28,"description":29,"kind":8,"mark":8,"planned":9,"contributors":30,"provenance":8},"\u002Fdocs\u002Fapi\u002Ftasks","Tasks over the API","Create a task from code, change it without overwriting anyone else's change, start it with input, and read how the run went.",[],{"href":32,"title":33,"description":34,"kind":8,"mark":8,"planned":9,"contributors":35,"provenance":8},"\u002Fdocs\u002Fapi\u002Fwebhooks","Webhooks","Start a run of a task, or answer a gate, from any system that can send an HTTP request.",[],{"href":37,"title":38,"description":39,"kind":8,"mark":8,"planned":9,"contributors":40,"provenance":8},"\u002Fdocs\u002Fcompany\u002Fdecision-rights","Decision rights","Who decides what: what members decide inside a task, what always comes to a person, and what happens when nobody answers.",[],{"href":42,"title":43,"description":44,"kind":8,"mark":8,"planned":9,"contributors":45,"provenance":8},"\u002Fdocs\u002Fcompany\u002Fenterprise","Enterprise","The company: a separate tenant with its own teams, members, people, memory, tools and spend, and the settings that apply to all of it.",[],{"href":47,"title":48,"description":49,"kind":8,"mark":8,"planned":9,"contributors":50,"provenance":8},"\u002Fdocs\u002Fcompany\u002Fmembers","Members and inboxes","A member is a named AI team member with a persona and a mailbox of its own. It holds roles, sits on teams, and does one run at a time.",[],{"href":52,"title":53,"description":54,"kind":8,"mark":8,"planned":9,"contributors":55,"provenance":8},"\u002Fdocs\u002Fcompany\u002Fpeople","People and access","The humans in an enterprise: owners, everyone else and the grant each holds, and how an invitation brings someone in.",[],{"href":57,"title":58,"description":59,"kind":8,"mark":8,"planned":9,"contributors":60,"provenance":8},"\u002Fdocs\u002Fcompany\u002Froles","Roles","A role is a job: the tasks done in it, the members who hold it, and the tools and caps that come with it.",[],{"href":62,"title":63,"description":64,"kind":8,"mark":8,"planned":9,"contributors":65,"provenance":8},"\u002Fdocs\u002Fcompany\u002Fteams","Teams and charters","A team is a group of members around one outcome, with a charter that says why it exists and how it is measured, and a lead.",[],{"href":67,"title":68,"description":69,"kind":8,"mark":8,"planned":9,"contributors":70,"provenance":8},"\u002Fdocs\u002Fconcepts","Concepts","The nouns of Zero Human OS, what each one is, and how they fit together.",[],{"href":72,"title":73,"description":74,"kind":8,"mark":8,"planned":75,"contributors":76,"provenance":8},"\u002Fdocs\u002Fcontrol\u002Fassets","Assets","Files and links the company keeps at each layer, which a run reads by name and adds to only where you allow it.",true,[],{"href":78,"title":79,"description":80,"kind":8,"mark":8,"planned":9,"contributors":81,"provenance":8},"\u002Fdocs\u002Fcontrol\u002Fgates","Gates and tool scopes","What a task may touch at all, and which of its calls wait for your approval before they happen.",[],{"href":83,"title":84,"description":85,"kind":8,"mark":8,"planned":9,"contributors":86,"provenance":8},"\u002Fdocs\u002Fcontrol\u002Fisolation","Isolation and retention","What stays inside your enterprise, what a model is and is not shown, and how long run history is kept.",[],{"href":88,"title":89,"description":90,"kind":8,"mark":8,"planned":9,"contributors":91,"provenance":8},"\u002Fdocs\u002Fcontrol\u002Fmemory","Memory","What the company knows, how a run asks it and adds to it, how a wrong note is corrected, and why nothing secret belongs in it.",[],{"href":93,"title":94,"description":95,"kind":8,"mark":8,"planned":75,"contributors":96,"provenance":8},"\u002Fdocs\u002Fcontrol\u002Fretrospectives","Retrospectives","Each team looks back on its week and its quarter: what worked, what to change, and whether its charter still holds.",[],{"href":98,"title":99,"description":100,"kind":8,"mark":8,"planned":9,"contributors":101,"provenance":8},"\u002Fdocs\u002Fcontrol\u002Fself-improvement","Self-improvement","After a run that went wrong, the OS proposes one change to the task. You decide, and an approved change is a new version you can see.",[],{"href":103,"title":104,"description":105,"kind":8,"mark":8,"planned":9,"contributors":106,"provenance":8},"\u002Fdocs\u002Fcontrol\u002Fspend","Spend and models","What counts as spend, the caps that hold it, which model a run uses, and the model connections that pay for it.",[],{"href":108,"title":109,"description":110,"kind":8,"mark":8,"planned":9,"contributors":111,"provenance":8},"\u002Fdocs\u002Ffirst-week","A first week","From an empty enterprise to a first run you approve: a team, a member, a task with a gate, and a COO watching for anything stuck.",[],{"href":113,"title":114,"description":115,"kind":8,"mark":8,"planned":9,"contributors":116,"provenance":8},"\u002Fdocs\u002Fmcp","The MCP server","Your enterprise's own MCP server, for agents you run: what it is, what it can do, and what a token lets it reach.",[],{"href":118,"title":119,"description":120,"kind":8,"mark":8,"planned":9,"contributors":121,"provenance":8},"\u002Fdocs\u002Fmcp\u002Fconnect","Connect a client","A token with the scopes your agent needs, then Claude Code, Claude Desktop, any other MCP client, or curl.",[],{"href":123,"title":124,"description":125,"kind":8,"mark":8,"planned":75,"contributors":126,"provenance":8},"\u002Fdocs\u002Fmcp\u002Fconnected-apps","Connected apps","Sign in with Zero Human from an MCP client instead of pasting a token, and revoke the app later.",[],{"href":128,"title":129,"description":130,"kind":8,"mark":8,"planned":9,"contributors":131,"provenance":8},"\u002Fdocs\u002Fmcp\u002Ferrors","Errors","What each refusal from the MCP server means, and what to do about it.",[],{"href":133,"title":134,"description":135,"kind":8,"mark":8,"planned":9,"contributors":136,"provenance":8},"\u002Fdocs\u002Fmcp\u002Ftools","MCP tools","Every tool the OS's MCP server offers, generated from the tool catalog.",[],{"href":138,"title":139,"description":140,"kind":8,"mark":8,"planned":9,"contributors":141,"provenance":8},"\u002Fdocs\u002Fportal","The portal","Where you run the company: observe it, talk to it, approve what waits for you, and connect its tools. Every page, and how to read a status.",[],{"href":143,"title":144,"description":145,"kind":146,"mark":8,"planned":9,"contributors":147,"provenance":8},"\u002Fdocs\u002Ftools\u002Fbrowser","Browser","A web product with no MCP server, operated the way a person would: a browser, on the sites you allow.","operates",[],{"href":149,"title":150,"description":151,"kind":8,"mark":8,"planned":9,"contributors":152,"provenance":8},"\u002Fdocs\u002Ftools\u002Fbuilt-in","Built-in tools","Every operation the OS answers for a task itself, with its inputs, effects, gates, retry safety and errors.",[],{"href":154,"title":155,"description":156,"kind":8,"mark":8,"planned":9,"contributors":157,"provenance":8},"\u002Fdocs\u002Ftools\u002Fbuilt-in\u002Fchat","Chat tools","The os.* tools the CEO chat offers a member: the company's directory, its tasks, and starting and checking runs.",[],{"href":159,"title":160,"description":161,"kind":8,"mark":8,"planned":9,"contributors":162,"provenance":8},"\u002Fdocs\u002Ftools\u002Fbuilt-in\u002Fcomputer-use","Computer-Use tools","The verbs a run can call on a Computer-Use binding: a browser for a product with no MCP server, limited to the sites the binding allows.",[],{"href":164,"title":165,"description":166,"kind":8,"mark":8,"planned":9,"contributors":167,"provenance":8},"\u002Fdocs\u002Ftools\u002Fbuilt-in\u002Fmemory","Memory tools","The memory.* tools: ask enterprise memory a question, and teach it a note.",[],{"href":169,"title":170,"description":171,"kind":8,"mark":8,"planned":9,"contributors":172,"provenance":8},"\u002Fdocs\u002Ftools\u002Fbuilt-in\u002Fos","OS tools","The os.* tools a run can call: execution labels, gate summaries, questions for the CEO, self-improvement, mail, company state, shared context, unblocking runs, planning, the CEO’s brief and chat threads.",[],{"href":174,"title":175,"description":176,"kind":8,"mark":8,"planned":9,"contributors":177,"provenance":8},"\u002Fdocs\u002Ftools\u002Fbuilt-in\u002Fweb","Web tools","The web.* tools: read a public page as text, list a sitemap, and GET a public URL, with a hash of what came back.",[],{"href":179,"title":180,"description":181,"kind":8,"mark":8,"planned":9,"contributors":182,"provenance":8},"\u002Fdocs\u002Ftools\u002Fbuilt-in\u002Fworkspace","Workspace tools","The workspace.* tools: read, search, change, commit and push a throwaway clone of a repository.",[],{"href":184,"title":185,"description":186,"kind":187,"mark":8,"planned":9,"contributors":188,"provenance":8},"\u002Fdocs\u002Ftools\u002Fgithub","GitHub","Issues, pull requests, reviews and checks, through GitHub's own hosted MCP server.","integrates",[],{"href":190,"title":191,"description":192,"kind":187,"mark":8,"planned":9,"contributors":193,"provenance":8},"\u002Fdocs\u002Ftools\u002Fmetabase","Metabase","Questions, dashboards and queries, through the MCP server built into your own Metabase, connected with OAuth.",[],{"href":195,"title":196,"description":197,"kind":187,"mark":8,"planned":9,"contributors":198,"provenance":8},"\u002Fdocs\u002Ftools\u002Foutrank","Outrank","Writer questions for scheduled articles, through Outrank's MCP server, which you host.",[],{"href":200,"title":201,"description":202,"kind":187,"mark":8,"planned":9,"contributors":203,"provenance":8},"\u002Fdocs\u002Ftools\u002Fpostmark","Postmark","Transactional email from your own Postmark account, through Postmark's MCP server, which you host.",[],{"href":205,"title":206,"description":207,"kind":187,"mark":8,"planned":9,"contributors":208,"provenance":8},"\u002Fdocs\u002Ftools\u002Fsentry","Sentry","Issues, events and traces, through Sentry's own hosted MCP server, connected with OAuth.",[],{"href":210,"title":211,"description":212,"kind":187,"mark":8,"planned":9,"contributors":213,"provenance":8},"\u002Fdocs\u002Ftools\u002Fslack","Slack","Messages, channels, search and files, through Slack's own hosted MCP server.",[],{"href":215,"title":216,"description":217,"kind":146,"mark":8,"planned":9,"contributors":218,"provenance":8},"\u002Fdocs\u002Ftools\u002Fweb","Web","The public web, read directly: a page as text, a sitemap as a list, a URL's text or JSON. Nothing to connect.",[],{"href":220,"title":221,"description":222,"kind":8,"mark":8,"planned":9,"contributors":223,"provenance":8},"\u002Fdocs\u002Ftools\u002Fworkspaces","Workspaces","A throwaway clone of one git repository for one run: set up by the repository itself, changed through the workspace tools, pushed to a branch, and deleted when the run ends.",[],{"href":225,"title":226,"description":227,"kind":8,"mark":8,"planned":9,"contributors":228,"provenance":8},"\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.",[],{"href":230,"title":231,"description":232,"kind":8,"mark":8,"planned":9,"contributors":233,"provenance":8},"\u002Fdocs\u002Fwork\u002Fchat","Chat and plans","Talk to a member, have it start work, watch the work move, and answer what it asks, in one thread.",[],{"href":235,"title":236,"description":237,"kind":8,"mark":8,"planned":9,"contributors":238,"provenance":8},"\u002Fdocs\u002Fwork\u002Fexecutions","Executions","The connected runs of more than one task: one piece of work as it moves from member to member.",[],{"href":240,"title":241,"description":242,"kind":8,"mark":8,"planned":9,"contributors":243,"provenance":8},"\u002Fdocs\u002Fwork\u002Fhandoffs","Handoffs","How one task hands its result to the next: by outcome, by condition, after a delay, and back to you when a decision is needed.",[],{"href":245,"title":246,"description":247,"kind":8,"mark":8,"planned":9,"contributors":248,"provenance":8},"\u002Fdocs\u002Fwork\u002Fruns","Runs","One run of a task, start to finish: what each status means, what you can do with a run, and why one lands on Blockers.",[],{"href":250,"title":251,"description":252,"kind":8,"mark":8,"planned":9,"contributors":253,"provenance":8},"\u002Fdocs\u002Fwork\u002Fschedules","Schedules and webhooks","What starts a run: a schedule, a webhook, a person, or the task before it, and what happens when the task is already busy.",[],{"href":255,"title":256,"description":257,"kind":8,"mark":8,"planned":9,"contributors":258,"provenance":8},"\u002Fdocs\u002Fwork\u002Ftasks","Tasks","The definition of a repeatable job: its goal, its limits, the tools it may use, and what happens next. A task never runs; a run does.",[],1791124519688]