[{"data":1,"prerenderedAt":389},["ShallowReactive",2],{"$f3bd4vhrlq1jvv":3},[4,11,16,21,26,31,36,41,46,51,56,61,66,71,76,82,87,92,97,102,107,112,117,122,127,132,137,142,147,152,157,162,167,172,177,182,187,192,197,202,207,212,217,222,228,233,238,243,248,253,258,263,269,274,279,284,289,294,299,304,309,314,319,324,329,334,339,344,349,354,359,364,369,374,379,384],{"href":5,"title":6,"description":7,"kind":8,"mark":8,"planned":9,"contributors":10,"provenance":8,"express":9,"bridge":9},"\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,"express":9,"bridge":9},"\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,"express":9,"bridge":9},"\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,"express":9,"bridge":9},"\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,"express":9,"bridge":9},"\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,"express":9,"bridge":9},"\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,"express":9,"bridge":9},"\u002Fdocs\u002Fcompany\u002Fbilling","Billing","Your plan, how you pay for it, what changing plan does, what is billed past what the plan includes, and what happens when a renewal fails.",[],{"href":42,"title":43,"description":44,"kind":8,"mark":8,"planned":9,"contributors":45,"provenance":8,"express":9,"bridge":9},"\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":47,"title":48,"description":49,"kind":8,"mark":8,"planned":9,"contributors":50,"provenance":8,"express":9,"bridge":9},"\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":52,"title":53,"description":54,"kind":8,"mark":8,"planned":9,"contributors":55,"provenance":8,"express":9,"bridge":9},"\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, or a few at once on the Enterprise plan.",[],{"href":57,"title":58,"description":59,"kind":8,"mark":8,"planned":9,"contributors":60,"provenance":8,"express":9,"bridge":9},"\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":62,"title":63,"description":64,"kind":8,"mark":8,"planned":9,"contributors":65,"provenance":8,"express":9,"bridge":9},"\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":67,"title":68,"description":69,"kind":8,"mark":8,"planned":9,"contributors":70,"provenance":8,"express":9,"bridge":9},"\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":72,"title":73,"description":74,"kind":8,"mark":8,"planned":9,"contributors":75,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Fconcepts","Concepts","The nouns of Zero Human OS, what each one is, and how they fit together.",[],{"href":77,"title":78,"description":79,"kind":8,"mark":8,"planned":80,"contributors":81,"provenance":8,"express":9,"bridge":9},"\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":83,"title":84,"description":85,"kind":8,"mark":8,"planned":9,"contributors":86,"provenance":8,"express":9,"bridge":9},"\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":88,"title":89,"description":90,"kind":8,"mark":8,"planned":9,"contributors":91,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Fcontrol\u002Fisolation","Isolation and retention","What stays inside your enterprise, what a model is and is not shown, how long run history is kept, and what closing an enterprise deletes.",[],{"href":93,"title":94,"description":95,"kind":8,"mark":8,"planned":9,"contributors":96,"provenance":8,"express":9,"bridge":9},"\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":98,"title":99,"description":100,"kind":8,"mark":8,"planned":80,"contributors":101,"provenance":8,"express":9,"bridge":9},"\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":103,"title":104,"description":105,"kind":8,"mark":8,"planned":9,"contributors":106,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Fcontrol\u002Fself-improvement","Self-improvement","After an execution that went wrong, the OS proposes one change to one of its tasks. You decide, and an approved change is a new version you can see.",[],{"href":108,"title":109,"description":110,"kind":8,"mark":8,"planned":9,"contributors":111,"provenance":8,"express":9,"bridge":9},"\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":113,"title":114,"description":115,"kind":8,"mark":8,"planned":9,"contributors":116,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Femail\u002Faddresses-and-domains","Addresses and domains","Every enterprise receives mail on its own host under zerohuman.com. An owner can also attach a domain the company owns, prove it, and move the domain's mail onto Zero Human, one record at a time and with a way back.",[],{"href":118,"title":119,"description":120,"kind":8,"mark":8,"planned":80,"contributors":121,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Femail\u002Fconnect-a-mail-app","Connect a mail app","Read and send your own mail over IMAP and SMTP, with a separate app password for each mail app.",[],{"href":123,"title":124,"description":125,"kind":8,"mark":8,"planned":9,"contributors":126,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Femail\u002Flimits","Limits","Every limit on mail in Zero Human, in one table, each with the page that explains it.",[],{"href":128,"title":129,"description":130,"kind":8,"mark":8,"planned":9,"contributors":131,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Femail\u002Fmail-in-tasks","Mail in tasks","A member's tasks read, file and answer the member's own mailbox with the OS's built-in mail tools. Every send waits for approval on the exact message first.",[],{"href":133,"title":134,"description":135,"kind":8,"mark":8,"planned":9,"contributors":136,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Femail\u002Fmcp-and-api","Mail over MCP and the API","A person reads and answers their own mailbox from an agent over the enterprise's MCP server, or from code over the API. A member's mailbox is read over the API, and worked by its own tasks.",[],{"href":138,"title":139,"description":140,"kind":8,"mark":8,"planned":9,"contributors":141,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Femail\u002Fmember-mailboxes","Member mailboxes","Every member has a mailbox at its own address. Its tasks read, file and answer it, every send waits for approval, and the enterprise owner can work it by hand in the portal.",[],{"href":143,"title":144,"description":145,"kind":8,"mark":8,"planned":9,"contributors":146,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Femail\u002Foverview","Email","Every member, and every person an owner gives an address to, has a mailbox in Zero Human. This section explains all of it: addresses and domains, the mailboxes, writing mail, safety, retention, and reaching mail from an agent or from code.",[],{"href":148,"title":149,"description":150,"kind":8,"mark":8,"planned":9,"contributors":151,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Femail\u002Fperson-mailboxes","Person mailboxes","An owner can give any person in the enterprise an address. Its mailbox is that person's alone: they read it, answer it and file it in the portal, from their own agent, or from code, and nothing they send waits for approval.",[],{"href":153,"title":154,"description":155,"kind":8,"mark":8,"planned":9,"contributors":156,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Femail\u002Fretention-and-deletion","Retention and deletion","Mail is kept for your plan's period and then deleted, received and sent alike. Deleting a mail by hand removes it at once, for good.",[],{"href":158,"title":159,"description":160,"kind":8,"mark":8,"planned":9,"contributors":161,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Femail\u002Fsafety-and-deliverability","Safety and deliverability","How mail is checked on the way in and held to account on the way out: spam scoring, what an unknown recipient gets, who may send from which address, bounces and complaints, and how mail proves where it came from.",[],{"href":163,"title":164,"description":165,"kind":8,"mark":8,"planned":9,"contributors":166,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Femail\u002Ftroubleshooting","Troubleshooting","What to check when mail did not arrive, when mail is marked as spam, when a send is refused, and when a domain's records do not check.",[],{"href":168,"title":169,"description":170,"kind":8,"mark":8,"planned":9,"contributors":171,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Femail\u002Fwriting-mail","Writing mail","How a mail is written and what it carries, from the portal, a task, an agent or code: formatting and Markdown, attachments, Cc and Bcc, quoted text, signatures, and the contacts a mailbox writes to.",[],{"href":173,"title":174,"description":175,"kind":8,"mark":8,"planned":9,"contributors":176,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Fengineering-team","An engineering team on your repository","From a repository and an empty enterprise to a cloned engineering team working on it: the steps, what only you can do, and a prompt your coding assistant can follow.",[],{"href":178,"title":179,"description":180,"kind":8,"mark":8,"planned":9,"contributors":181,"provenance":8,"express":9,"bridge":9},"\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":183,"title":184,"description":185,"kind":8,"mark":8,"planned":9,"contributors":186,"provenance":8,"express":9,"bridge":9},"\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":188,"title":189,"description":190,"kind":8,"mark":8,"planned":9,"contributors":191,"provenance":8,"express":9,"bridge":9},"\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":193,"title":194,"description":195,"kind":8,"mark":8,"planned":80,"contributors":196,"provenance":8,"express":9,"bridge":9},"\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":198,"title":199,"description":200,"kind":8,"mark":8,"planned":9,"contributors":201,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Fmcp\u002Ferrors","Errors","What each refusal from the MCP server means, and what to do about it.",[],{"href":203,"title":204,"description":205,"kind":8,"mark":8,"planned":9,"contributors":206,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Fmcp\u002Ftools","MCP tools","Every tool the OS's MCP server offers, generated from the tool catalog.",[],{"href":208,"title":209,"description":210,"kind":8,"mark":8,"planned":9,"contributors":211,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Fplaybooks\u002Fgmail-assistant","Gmail Assistant","Find personal emails that need a reply, prepare drafts in your voice, and learn from the replies you choose to send.",[],{"href":213,"title":214,"description":215,"kind":8,"mark":8,"planned":9,"contributors":216,"provenance":8,"express":9,"bridge":9},"\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":218,"title":219,"description":220,"kind":8,"mark":8,"planned":9,"contributors":221,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Ftools\u002Fbridges","Bridges","The Zero Human bridges: what each reads, what it writes, and how to connect it.",[],{"href":223,"title":224,"description":225,"kind":226,"mark":8,"planned":9,"contributors":227,"provenance":8,"express":9,"bridge":9},"\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":229,"title":230,"description":231,"kind":8,"mark":8,"planned":9,"contributors":232,"provenance":8,"express":9,"bridge":9},"\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":234,"title":235,"description":236,"kind":8,"mark":8,"planned":9,"contributors":237,"provenance":8,"express":9,"bridge":9},"\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":239,"title":240,"description":241,"kind":8,"mark":8,"planned":9,"contributors":242,"provenance":8,"express":9,"bridge":9},"\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":244,"title":245,"description":246,"kind":8,"mark":8,"planned":9,"contributors":247,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Ftools\u002Fbuilt-in\u002Fmemory","Memory tools","The memory.* tools: ask enterprise memory a question, and teach it a note.",[],{"href":249,"title":250,"description":251,"kind":8,"mark":8,"planned":9,"contributors":252,"provenance":8,"express":9,"bridge":9},"\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":254,"title":255,"description":256,"kind":8,"mark":8,"planned":9,"contributors":257,"provenance":8,"express":9,"bridge":9},"\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":259,"title":260,"description":261,"kind":8,"mark":8,"planned":9,"contributors":262,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Ftools\u002Fbuilt-in\u002Fworkspace","Workspace tools","The workspace.* tools: read, search, change, commit and push a throwaway clone of a repository.",[],{"href":264,"title":265,"description":266,"kind":267,"mark":8,"planned":9,"contributors":268,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Ftools\u002Fdataforseo","DataForSEO","Search results, keywords, backlinks and on-page audits, through DataForSEO's own hosted MCP server, on your own DataForSEO account.","integrates",[],{"href":270,"title":271,"description":272,"kind":267,"mark":8,"planned":9,"contributors":273,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Ftools\u002Fgithub","GitHub","Issues, pull requests, reviews and checks, through GitHub's own hosted MCP server.",[],{"href":275,"title":276,"description":277,"kind":267,"mark":8,"planned":9,"contributors":278,"provenance":8,"express":80,"bridge":9},"\u002Fdocs\u002Ftools\u002Fgmail","Gmail","Search and read a mailbox, label mail and prepare drafts, through Google's own hosted Gmail MCP server.",[],{"href":280,"title":281,"description":282,"kind":267,"mark":8,"planned":9,"contributors":283,"provenance":8,"express":9,"bridge":80},"\u002Fdocs\u002Ftools\u002Fgoogle","Google Search Console and GA4","Search performance, index status, sessions and key events, read-only, by signing in with Google.",[],{"href":285,"title":286,"description":287,"kind":267,"mark":8,"planned":9,"contributors":288,"provenance":8,"express":80,"bridge":80},"\u002Fdocs\u002Ftools\u002Flinkedin","LinkedIn","Posts on LinkedIn as a member, or a company page they run, through a Zero Human bridge, by signing in with LinkedIn.",[],{"href":290,"title":291,"description":292,"kind":267,"mark":8,"planned":9,"contributors":293,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Ftools\u002Fmetabase","Metabase","Questions, dashboards and queries, through the MCP server built into your own Metabase, connected with OAuth.",[],{"href":295,"title":296,"description":297,"kind":267,"mark":8,"planned":9,"contributors":298,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Ftools\u002Foutrank","Outrank","Writer questions for scheduled articles, through Outrank's MCP server, which you host.",[],{"href":300,"title":301,"description":302,"kind":267,"mark":8,"planned":9,"contributors":303,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Ftools\u002Fpostmark","Postmark","Transactional email from your own Postmark account, through Postmark's MCP server, which you host.",[],{"href":305,"title":306,"description":307,"kind":267,"mark":8,"planned":9,"contributors":308,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Ftools\u002Fsentry","Sentry","Issues, events and traces, through Sentry's own hosted MCP server, connected with OAuth.",[],{"href":310,"title":311,"description":312,"kind":267,"mark":8,"planned":9,"contributors":313,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Ftools\u002Fslack","Slack","Messages, channels, search and files, through Slack's own hosted MCP server.",[],{"href":315,"title":316,"description":317,"kind":267,"mark":8,"planned":9,"contributors":318,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Ftools\u002Fviralbrain","ViralBrain","LinkedIn posts, through ViralBrain's own hosted MCP server, on your own ViralBrain account.",[],{"href":320,"title":321,"description":322,"kind":226,"mark":8,"planned":9,"contributors":323,"provenance":8,"express":9,"bridge":9},"\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":325,"title":326,"description":327,"kind":8,"mark":8,"planned":9,"contributors":328,"provenance":8,"express":9,"bridge":9},"\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":330,"title":331,"description":332,"kind":267,"mark":8,"planned":9,"contributors":333,"provenance":8,"express":9,"bridge":80},"\u002Fdocs\u002Ftools\u002Fx","X","Posts on X (formerly Twitter) as your own account, and reads how those posts did, through a Zero Human bridge and an X app your company registers.",[],{"href":335,"title":336,"description":337,"kind":267,"mark":8,"planned":9,"contributors":338,"provenance":8,"express":9,"bridge":80},"\u002Fdocs\u002Ftools\u002Fyoutube","YouTube","Uploads videos and thumbnails to your own YouTube channel through a Zero Human bridge, signed in with Google.",[],{"href":340,"title":341,"description":342,"kind":8,"mark":8,"planned":9,"contributors":343,"provenance":8,"express":9,"bridge":9},"\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":345,"title":346,"description":347,"kind":8,"mark":8,"planned":9,"contributors":348,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Fwork\u002Fbuilt-in-tasks","Built-in tasks","The tasks every enterprise gets with the OS, updated through releases.",[],{"href":350,"title":351,"description":352,"kind":8,"mark":8,"planned":9,"contributors":353,"provenance":8,"express":9,"bridge":9},"\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":355,"title":356,"description":357,"kind":8,"mark":8,"planned":9,"contributors":358,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Fwork\u002Fexecutions","Executions","The connected runs of more than one task: one piece of work as it moves from member to member.",[],{"href":360,"title":361,"description":362,"kind":8,"mark":8,"planned":9,"contributors":363,"provenance":8,"express":9,"bridge":9},"\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":365,"title":366,"description":367,"kind":8,"mark":8,"planned":9,"contributors":368,"provenance":8,"express":9,"bridge":9},"\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":370,"title":371,"description":372,"kind":8,"mark":8,"planned":9,"contributors":373,"provenance":8,"express":9,"bridge":9},"\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":375,"title":376,"description":377,"kind":8,"mark":8,"planned":9,"contributors":378,"provenance":8,"express":9,"bridge":9},"\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.",[],{"href":380,"title":381,"description":382,"kind":8,"mark":8,"planned":9,"contributors":383,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Fwork\u002Ftool-slots","Tool slots","Name a task's tools by a slot, such as a code host, and let each company fill it with the tool it connected, so one task works with any vendor.",[],{"href":385,"title":386,"description":387,"kind":8,"mark":8,"planned":9,"contributors":388,"provenance":8,"express":9,"bridge":9},"\u002Fdocs\u002Fwork\u002Fwriting-a-task","Writing a clonable task","The rules for a task that works in an enterprise that is not its author's, each with the mistake it prevents, and a checklist to run before you publish one.",[],1794928143247]