[{"data":1,"prerenderedAt":35},["ShallowReactive",2],{"$f1g06gugi3tmp7":3},{"href":4,"title":5,"description":6,"kind":7,"mark":7,"planned":8,"contributors":9,"provenance":7,"html":10,"headings":11},"\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.",null,false,[],"\u003Ch2 id=\"what-an-enterprise-is\">What an enterprise is\u003C\u002Fh2>\n\u003Cp>An enterprise is the company, and the top of everything else. Its teams, members, roles and tasks, the people who\ncan sign in to it, its memory, its connected tools and models, and its spend all belong to it, and none of it is\nvisible to any other enterprise (\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fisolation\">Isolation and retention\u003C\u002Fa>).\u003C\u002Fp>\n\u003Cp>Create one per company. If you are working on two distinct ideas, make two enterprises: they share nothing but\nyou.\u003C\u002Fp>\n\u003Ch2 id=\"creating-one\">Creating one\u003C\u002Fh2>\n\u003Cp>Only a person signed in to the portal can create an enterprise; an API token cannot. Use \u003Cstrong>New enterprise\u003C\u002Fstrong> on the\n\u003Cstrong>Map\u003C\u002Fstrong>, or, if you hold no enterprise yet, the form the portal opens with.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Field\u003C\u002Fth>\n\u003Cth>What it is\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Name\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>The company's name, as the portal shows it.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Slug\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Its short name, taken from the name if you leave it blank. It has to be free, and a few names that belong to the product itself are refused. It becomes the company's mail domain, so choose it with care: the portal has no way to change it later.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Picture\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Optional. Initials stand in until you add one, and you can change it on \u003Cstrong>Enterprise\u003C\u002Fstrong>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>Whoever creates the enterprise owns it (\u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fpeople\">People and access\u003C\u002Fa>).\u003C\u002Fp>\n\u003Cp>A new enterprise has no teams and no members. It starts with the OS's own tasks, and nothing else.\u003C\u002Fp>\n\u003Ch2 id=\"its-address\">Its address\u003C\u002Fh2>\n\u003Cp>The slug is also the domain every member's mail lives on: an enterprise with the slug \u003Ccode>northstar\u003C\u002Fcode> gets\n\u003Ccode>northstar.zerohuman.com\u003C\u002Fcode>, and its members get addresses such as \u003Ccode>jules@northstar.zerohuman.com\u003C\u002Fcode>\n(\u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fmembers\">Members and inboxes\u003C\u002Fa>).\u003C\u002Fp>\n\u003Ch2 id=\"more-than-one\">More than one\u003C\u002Fh2>\n\u003Cp>You work in one enterprise at a time. With several, the portal asks which to open when you sign in, and the switch\nbutton in the header brings you back to choose again. The \u003Cstrong>Map\u003C\u002Fstrong> draws your other enterprises too; select one to\nswitch to it.\u003C\u002Fp>\n\u003Cp>What you hold is decided per enterprise. You can own one company and hold a narrow grant in another, and joining a\nnew one by invitation leaves the ones you already belong to as they were.\u003C\u002Fp>\n\u003Ch2 id=\"settings-on-the-enterprise-page\">Settings on the Enterprise page\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Enterprise\u003C\u002Fstrong>, in the portal, is the company's headquarters. Besides waiting gates, blockers, live runs and\ntoday's spend, it holds the settings that apply to the whole company.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Setting\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Picture\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>The company's picture, in the portal and on the map.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Company KPIs\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>The company's own KPIs, each with a target, an AMBER band, a cadence and a source. A KPI may have no target yet, and says so. Each KPI's card shows its light, its latest reading and its history; where a person is the source, \u003Cstrong>Record a reading\u003C\u002Fstrong> on the card enters a number. A KPI has no light until its first reading. They show on the KPI board beside each team's key KPI, which comes from its \u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fteams\">charter\u003C\u002Fa>. Metrics written as free text before KPIs existed were carried over as KPIs waiting for a target.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Chat model\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>The model tier members use in chat: economical, mid or frontier. Economical by default: chat lists, starts and reports on work, and the thinking happens in runs, which use their own task's tier. Spend caps still apply on top.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Chat memory\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>How much of the company's memory a member reads with each message you send in chat: standard (up to 4,096 tokens), large (8,192) or extended (16,384). Standard by default. A deeper read finds notes a shallower one misses, and costs more: recalled notes stay in the conversation and are sent to the model on every later step. See \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fchat#what-a-member-remembers\">Chat\u003C\u002Fa>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Concurrent runs\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>How many runs the whole company may have going at once, across every team. It starts at 1. A team can hold part of it for itself, and the teams' limits together may not exceed it. A member still does one run at a time, and a run waiting on your decision does not count.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Agents\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Model connections the whole company shares. A member's own connection, on their page, is used instead for their work. See \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fspend\">Spend and models\u003C\u002Fa>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Tools\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Tools bound for the whole company. A binding for the same tool on a team, member, role or task replaces it there. See the \u003Ca href=\"\u002Fdocs\u002Ftools\">tool directory\u003C\u002Fa>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>Spend caps for the enterprise are set on \u003Cstrong>Spend\u003C\u002Fstrong>, and the switch there turns cap enforcement off and on for the\nwhole company. Spend is recorded either way.\u003C\u002Fp>\n\u003Ch2 id=\"the-oss-own-tasks\">The OS's own tasks\u003C\u002Fh2>\n\u003Cp>Every enterprise has a set of tasks that belong to the OS rather than to you. They are part of the product, like\nits built-in tools: the same in every enterprise, down to the version, and changed only when a new release of the\nOS ships. Nobody edits one in place, and no enterprise owns one. They are listed on \u003Cstrong>Tasks\u003C\u002Fstrong> and marked\n\u003Cstrong>OS task\u003C\u002Fstrong>. You cannot edit, clone, copy, delete or schedule them, and they run without a member. You can start\nthem; they run on your own model connection and count against your own spend.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Tasks\u003C\u002Fth>\n\u003Cth>What they do\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Onboarding\u003C\u002Ftd>\n\u003Ctd>The COO's first conversation with you: it asks the team charter's questions and proposes your first team, role, member and task for you to sign off. Approve it and the OS sets them up and starts the first task's first run.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Self-improvement\u003C\u002Ftd>\n\u003Ctd>After a run of one of your tasks that went wrong, look for one change to that task, and make it once you approve it. See \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fself-improvement\">Self-improvement\u003C\u002Fa>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Organisation changes\u003C\u002Ftd>\n\u003Ctd>From what you ask a member for in chat, design a new team, role, member or task, or a change to or deletion of a team or task, and put it to you to sign off. Once you approve, the OS makes the change exactly as approved.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cdiv class=\"prose__planned\">\n\u003Cp class=\"prose__flag\">Planned\u003C\u002Fp>\n\u003Ch2 id=\"coming-for-the-enterprise\">Coming for the enterprise\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Your own domain.\u003C\u002Fstrong> Members' addresses on a domain you own instead of the enterprise's \u003Ccode>zerohuman.com\u003C\u002Fcode>\nsubdomain.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Changing and removing roles and members by conversation.\u003C\u002Fstrong> The organisation tasks will design a change to a\nrole or a member, or its removal, for you to sign off, as they do for teams and tasks today.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The OS's own tasks in their own section.\u003C\u002Fstrong> \u003Cstrong>Tasks\u003C\u002Fstrong> will list them apart from yours, each with the release\nof the OS it came with.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Learning from the OS's own tasks.\u003C\u002Fstrong> A switch on this page for whether self-improvement looks at runs of the\nOS's own tasks in your company. Off by default: a pass costs you a model call, and the only fix is a release of\nthe OS, so what it finds is reported, never changed in your enterprise.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Closing an enterprise.\u003C\u002Fstrong> Closing a company for good, after which its data is kept for the retention you set\nand then deleted. It will not be reversible.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fdiv>\n",[12,16,19,22,25,28,31],{"id":13,"text":14,"level":15,"planned":8},"what-an-enterprise-is","What an enterprise is",2,{"id":17,"text":18,"level":15,"planned":8},"creating-one","Creating one",{"id":20,"text":21,"level":15,"planned":8},"its-address","Its address",{"id":23,"text":24,"level":15,"planned":8},"more-than-one","More than one",{"id":26,"text":27,"level":15,"planned":8},"settings-on-the-enterprise-page","Settings on the Enterprise page",{"id":29,"text":30,"level":15,"planned":8},"the-oss-own-tasks","The OS's own tasks",{"id":32,"text":33,"level":15,"planned":34},"coming-for-the-enterprise","Coming for the enterprise",true,1791124519542]