[{"data":1,"prerenderedAt":32},["ShallowReactive",2],{"$f133hq7ovelxb3":3},{"href":4,"title":5,"description":6,"kind":7,"mark":7,"planned":8,"contributors":9,"provenance":7,"express":8,"bridge":8,"html":10,"headings":11},"\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.",null,false,[],"\u003Ch2 id=\"the-rule\">The rule\u003C\u002Fh2>\n\u003Cp>Members decide inside their tasks. People decide everything a task says must wait, and everything about the\ncompany itself: its structure, its limits, and who can reach it.\u003C\u002Fp>\n\u003Cp>A member works within four limits, all set by people: the task's \u003Cstrong>guardrails\u003C\u002Fstrong> (the standing rules it is given),\nits \u003Cstrong>tools\u003C\u002Fstrong> (the only operations it can call), its \u003Cstrong>gates\u003C\u002Fstrong> (the calls that wait for a person) and its\n\u003Cstrong>spend\u003C\u002Fstrong> (the caps that apply). Inside them, the member's call is the decision. Outside them, the member cannot\nact at all.\u003C\u002Fp>\n\u003Ch2 id=\"who-decides-what\">Who decides what\u003C\u002Fh2>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Decision\u003C\u002Fth>\n\u003Cth>Who decides\u003C\u002Fth>\n\u003Cth>Where\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>How to do the work inside a task\u003C\u002Ftd>\n\u003Ctd>The member doing the run, within the task's guardrails, tools, gates and spend.\u003C\u002Ftd>\n\u003Ctd>The run\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>A call the task gates, such as publishing a post or sending a payment\u003C\u002Ftd>\n\u003Ctd>A person whose access covers gates. Owners hold everything.\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Gates\u003C\u002Fstrong>, the run's page, or the chat that started the run\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>A question a task puts to you\u003C\u002Ftd>\n\u003Ctd>A person, the same way: a task's question to you is always a gate.\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Gates\u003C\u002Fstrong>, or a chat with the member it came from\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Merging a pull request\u003C\u002Ftd>\n\u003Ctd>A person, always. A task that can merge must declare a gate on it, or it cannot be saved.\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Gates\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>A new team, member, role or task, or a change to one\u003C\u002Ftd>\n\u003Ctd>A person with access to that part of the company. A member can design the change and ask you to sign off, but cannot make it.\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Teams\u003C\u002Fstrong>, \u003Cstrong>Members\u003C\u002Fstrong>, \u003Cstrong>Roles\u003C\u002Fstrong>, \u003Cstrong>Tasks\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Spend caps\u003C\u002Ftd>\n\u003Ctd>A person with access to spend.\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Spend\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Who can reach the enterprise, and what they hold\u003C\u002Ftd>\n\u003Ctd>An owner.\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>People\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>A change the OS proposes to a task after a run went wrong\u003C\u002Ftd>\n\u003Ctd>A person, or a task you have given the tools to decide them. An approved change can never widen the task's tools, drop its gates or raise its spend.\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Self-Improvement\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>A system can decide for you only with credentials you gave it: an \u003Ca href=\"\u002Fdocs\u002Fapi\u002Fauthentication\">API token\u003C\u002Fa> scoped to\ndecide gates, or your enterprise's \u003Ca href=\"\u002Fdocs\u002Fapi\u002Fwebhooks\">webhook\u003C\u002Fa> secret. Treat either as you would your own\nsignature.\u003C\u002Fp>\n\u003Ch2 id=\"what-no-member-can-do\">What no member can do\u003C\u002Fh2>\n\u003Cp>No tool the OS gives a member can approve or reject a gate, change a spend cap, bind a tool, or change who has\naccess. Members run tasks; they do not change the rules those tasks run under.\u003C\u002Fp>\n\u003Cp>The COO's task, \u003Cstrong>Keep the enterprise on track\u003C\u002Fstrong>, reads what is stuck and names the move that would unblock it and\nwho can make it. It never makes the move itself, and never touches a gate.\u003C\u002Fp>\n\u003Ch2 id=\"deciding-a-gate\">Deciding a gate\u003C\u002Fh2>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Answer\u003C\u002Fth>\n\u003Cth>What happens\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Approve\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>The call runs exactly as it was stored when the run stopped: what you saw is what happens.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Reject\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>The call is never made, and the run is cancelled. A question the task asked you is the exception: rejecting it is an answer, so the run carries on knowing you declined, with your note as the reason.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Request changes\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>The work goes back with your note, to the task the gated task names for it. It needs a note, and works only on a task that says where changes go.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"when-nobody-answers\">When nobody answers\u003C\u002Fh2>\n\u003Cp>A gate waits. It is marked on \u003Cstrong>Gates\u003C\u002Fstrong> once it has waited an hour, and marked aged at 24 hours. The owners are\nreminded by email at 24 hours and again at 48 hours. It then waits until someone decides it or its run is cancelled:\nan approval is never cancelled because time passed, and never approved because time passed.\u003C\u002Fp>\n\u003Cp>A run waiting at a gate does not hold its member or count against the company's concurrent runs, so the rest of the\nwork carries on while it waits.\u003C\u002Fp>\n\u003Cdiv class=\"prose__planned\">\n\u003Cp class=\"prose__flag\">Planned\u003C\u002Fp>\n\u003Ch2 id=\"coming-for-decision-rights\">Coming for decision rights\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Leads who decide inside their charter.\u003C\u002Fstrong> A team's lead taking the calls that stay within the team's charter,\nso they do not all come to you.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Work to hit a metric, proposed and approved.\u003C\u002Fstrong> For a team metric that is at risk or off target, the lead\nproposes the work to bring it back, and you approve it. Silence never approves.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fdiv>\n",[12,16,19,22,25,28],{"id":13,"text":14,"level":15,"planned":8},"the-rule","The rule",2,{"id":17,"text":18,"level":15,"planned":8},"who-decides-what","Who decides what",{"id":20,"text":21,"level":15,"planned":8},"what-no-member-can-do","What no member can do",{"id":23,"text":24,"level":15,"planned":8},"deciding-a-gate","Deciding a gate",{"id":26,"text":27,"level":15,"planned":8},"when-nobody-answers","When nobody answers",{"id":29,"text":30,"level":15,"planned":31},"coming-for-decision-rights","Coming for decision rights",true,1794928142768]