[{"data":1,"prerenderedAt":35},["ShallowReactive",2],{"$f3jcm6b5crc1mh":3},{"href":4,"title":5,"description":6,"kind":7,"mark":7,"planned":8,"contributors":9,"provenance":7,"html":10,"headings":11},"\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.",null,false,[],"\u003Cp>This is what setting up a company looks like today, step by step. The example is Northstar, a young company that\nwants more organic signups and does not want its founder living in a keyword spreadsheet.\u003C\u002Fp>\n\u003Ch2 id=\"day-1-the-enterprise\">Day 1: the enterprise\u003C\u002Fh2>\n\u003Col>\n\u003Cli>\u003Cstrong>Sign in.\u003C\u002Fstrong> The portal signs you in with GitHub. Today you get in through an invitation link\n(\u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fpeople\">People and access\u003C\u002Fa>).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Create the enterprise.\u003C\u002Fstrong> If you hold none yet, the portal asks you to create one; otherwise use \u003Cstrong>New\nenterprise\u003C\u002Fstrong> on the \u003Cstrong>Map\u003C\u002Fstrong>. Give it a name and a slug (taken from the name if you leave it blank), and a\npicture if you like. The slug becomes the company's mail domain, \u003Ccode>northstar.zerohuman.com\u003C\u002Fcode>, and you are its\nowner.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Look around.\u003C\u002Fstrong> The company is empty: no teams, no members. It already has the OS's own tasks, which you can\nsee on \u003Cstrong>Tasks\u003C\u002Fstrong>: the ones that look for improvements after a run, and the ones that design a new team, role,\nmember or task when you ask for one in chat.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Connect a model.\u003C\u002Fstrong> Nothing can think until it has a model. On \u003Cstrong>Agents\u003C\u002Fstrong>, add Claude (an API key or a Claude\nlogin) or OpenRouter for the whole enterprise. A member can also have its own.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Set a cap.\u003C\u002Fstrong> On \u003Cstrong>Spend\u003C\u002Fstrong>, set a day cap on the enterprise before anything runs. The tightest cap that applies\nalways wins (\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fspend\">Spend and models\u003C\u002Fa>).\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2 id=\"day-2-one-team-one-member\">Day 2: one team, one member\u003C\u002Fh2>\n\u003Col start=\"6\">\n\u003Cli>\u003Cstrong>Charter a team.\u003C\u002Fstrong> \u003Cstrong>Teams → Create.\u003C\u002Fstrong> Call it Marketing, and answer the charter's seven questions: the\nopportunity, the purpose, what success looks like, the metrics (one per line, say "Organic signups per week"),\nthe kit it needs, its roles and its timeline (\u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fteams\">Teams and charters\u003C\u002Fa>).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Hire the specialist.\u003C\u002Fstrong> \u003Cstrong>Members → Create.\u003C\u002Fstrong> Name her Jules. Her address fills in from her name,\n\u003Ccode>jules@northstar.zerohuman.com\u003C\u002Fcode>: her name, not her job. Write her persona (a line on how she works and how she\nsounds), and put her on Marketing (\u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fmembers\">Members and inboxes\u003C\u002Fa>).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Give her a job.\u003C\u002Fstrong> \u003Cstrong>Roles → Create\u003C\u002Fstrong> a role called Onsite SEO, and add Jules as a holder\n(\u003Ca href=\"\u002Fdocs\u002Fcompany\u002Froles\">Roles\u003C\u002Fa>).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Name a lead.\u003C\u002Fstrong> On the Marketing team's page, make Jules its lead. Until a team has a lead and at least one\nmetric, it shows on \u003Cstrong>Blockers\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Connect her tools.\u003C\u002Fstrong> On Jules's page, under \u003Cstrong>Tools\u003C\u002Fstrong>, bind the systems she needs, such as your analytics\nand your CMS. A tool bound to her is hers alone; bind it on the team or the enterprise to share it\n(\u003Ca href=\"\u002Fdocs\u002Ftools\">tool directory\u003C\u002Fa>).\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2 id=\"day-3-a-task-with-a-gate\">Day 3: a task with a gate\u003C\u002Fh2>\n\u003Col start=\"11\">\n\u003Cli>\u003Cstrong>Write the task.\u003C\u002Fstrong> \u003Cstrong>Tasks → Create\u003C\u002Fstrong> Keyword research: on the Marketing team, given to the Onsite SEO role,\nso Jules does its runs. Fill in its goal, its metrics, its guardrails (the standing rules, such as "never publish\na draft"), the tools it may call, and its instructions (\u003Ca href=\"\u002Fdocs\u002Fwork\u002Ftasks\">Tasks\u003C\u002Fa>). Or start from the\n\u003Cstrong>Catalog\u003C\u002Fstrong>: \u003Cstrong>Copy\u003C\u002Fstrong> makes an editable task of your own from a public one.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Set the gate.\u003C\u002Fstrong> A second task, Content creation, drafts the post and publishes it. Draft freely; publishing\nwaits for you. Declare a gate on the CMS's publish call. The CMS token may well have write access; the post\nstill goes nowhere until you approve that call (\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fgates\">Gates and tool scopes\u003C\u002Fa>).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Chain them.\u003C\u002Fstrong> Make Content creation a successor of Keyword research, so one hands its result to the next\n(\u003Ca href=\"\u002Fdocs\u002Fwork\u002Fhandoffs\">Handoffs\u003C\u002Fa>).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Schedule it.\u003C\u002Fstrong> On Keyword research's page, under \u003Cstrong>Triggers\u003C\u002Fstrong>, give it a schedule: Mondays at 09:00\n(\u003Ca href=\"\u002Fdocs\u002Fwork\u002Fschedules\">Schedules and webhooks\u003C\u002Fa>).\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2 id=\"day-4-the-first-run\">Day 4: the first run\u003C\u002Fh2>\n\u003Col start=\"15\">\n\u003Cli>\u003Cstrong>Start it.\u003C\u002Fstrong> You need not wait for Monday: on the task's page, \u003Cstrong>Start a run\u003C\u002Fstrong>. Or open a chat with Jules and\nask her to do it; the thread follows the run (\u003Ca href=\"\u002Fdocs\u002Fwork\u002Fchat\">Chat and plans\u003C\u002Fa>).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Watch it.\u003C\u002Fstrong> \u003Cstrong>Runs\u003C\u002Fstrong> shows it moving. Its page has the log, every tool call and its result, and what it has\ncost so far. When Keyword research hands off, \u003Cstrong>Executions\u003C\u002Fstrong> follows both runs as one piece of work.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Decide.\u003C\u002Fstrong> Content creation stops at its gate. \u003Cstrong>Gates\u003C\u002Fstrong> shows the call, what the run says it does, and how\nlong it has waited. \u003Cstrong>Approve\u003C\u002Fstrong> runs exactly the stored call; \u003Cstrong>Reject\u003C\u002Fstrong> cancels it; \u003Cstrong>Request changes\u003C\u002Fstrong>, on the\nrun's page, sends it back with your note. A gate nobody answers is cancelled after 72 hours, never approved.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2 id=\"day-5-what-comes-back\">Day 5: what comes back\u003C\u002Fh2>\n\u003Col start=\"18\">\n\u003Cli>\u003Cstrong>Anything stuck\u003C\u002Fstrong> lands on \u003Cstrong>Blockers\u003C\u002Fstrong>: a failed or stalled run, a run paused on its cap, a pipeline that\nstopped. \u003Cstrong>Retry\u003C\u002Fstrong> a failed run, or \u003Cstrong>Clear\u003C\u002Fstrong> it once you have dealt with it; it stays on \u003Cstrong>Runs\u003C\u002Fstrong> either way.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>An improvement.\u003C\u002Fstrong> After a run that failed, or succeeded with a tool call failing along the way, the OS may\npropose one change to that task. It waits on \u003Cstrong>Self-Improvement\u003C\u002Fstrong>, where you approve it, and the change becomes\na new version of the task, or decline it with a reason\n(\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fself-improvement\">Self-improvement\u003C\u002Fa>).\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2 id=\"your-coo\">Your COO\u003C\u002Fh2>\n\u003Cp>The COO is a member like any other: you create them. Make an Operations team, create a member to be your COO, and\nfrom the \u003Cstrong>Catalog\u003C\u002Fstrong> clone \u003Cstrong>Keep the enterprise on track\u003C\u002Fstrong> onto Operations. The clone keeps the role the catalog\ntask is given, so give your COO that role on Operations. Give it a schedule on its page; it is written to run every\nfifteen minutes.\u003C\u002Fp>\n\u003Cp>Each run reads \u003Cstrong>Blockers\u003C\u002Fstrong> and names every stuck run: what is stuck, why, the one move that would unblock it, and\nwho can make it. It never retries, clears or cancels a run, and never touches a gate: those stay yours.\u003C\u002Fp>\n\u003Cdiv class=\"prose__planned\">\n\u003Cp class=\"prose__flag\">Planned\u003C\u002Fp>\n\u003Ch2 id=\"coming-for-the-first-week\">Coming for the first week\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>A COO who onboards you.\u003C\u002Fstrong> An interview about the company, a proposed first team, charter and hire, and default\ngates, so you do not have to invent the org chart yourself.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>An operating brief.\u003C\u002Fstrong> The COO files a regular brief: every team's metrics, what is blocked, and every decision\nstill waiting on you.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Building the company by talking to it.\u003C\u002Fstrong> Today, if you ask a member in chat for a new team, role, member or\ntask, one of the OS's own tasks designs it and puts it to you to sign off; you then create it on the page for\nit. Applying an approved change as written, with nothing to retype, is coming.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fdiv>\n",[12,16,19,22,25,28,31],{"id":13,"text":14,"level":15,"planned":8},"day-1-the-enterprise","Day 1: the enterprise",2,{"id":17,"text":18,"level":15,"planned":8},"day-2-one-team-one-member","Day 2: one team, one member",{"id":20,"text":21,"level":15,"planned":8},"day-3-a-task-with-a-gate","Day 3: a task with a gate",{"id":23,"text":24,"level":15,"planned":8},"day-4-the-first-run","Day 4: the first run",{"id":26,"text":27,"level":15,"planned":8},"day-5-what-comes-back","Day 5: what comes back",{"id":29,"text":30,"level":15,"planned":8},"your-coo","Your COO",{"id":32,"text":33,"level":15,"planned":34},"coming-for-the-first-week","Coming for the first week",true,1791124519636]