[{"data":1,"prerenderedAt":32},["ShallowReactive",2],{"$f15iocmaqhv9bz":3},{"href":4,"title":5,"description":6,"kind":7,"mark":7,"planned":8,"contributors":9,"provenance":7,"html":10,"headings":11},"\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.",null,true,[],"\u003Ch2 id=\"what-an-asset-is\">What an asset is\u003C\u002Fh2>\n\u003Cp>An asset will be a named file or link the company keeps: a logo, a brief template, a spreadsheet, a checklist, a\nlast good example. It is not \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fmemory\">memory\u003C\u002Fa>. You do not ask an asset a question; a run reads it by\nits path, such as \u003Ccode>brand\u002Flogo.svg\u003C\u002Fcode> or \u003Ccode>briefs\u002Fseo.md\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>A link to a system you have not connected yet (a dashboard, a shared folder) will be an asset too, until you connect\nthe system as a \u003Ca href=\"\u002Fdocs\u002Ftools\">tool\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"where-assets-live\">Where assets live\u003C\u002Fh2>\n\u003Cp>Assets will sit on the same layers as the rest of the company:\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Layer\u003C\u002Fth>\n\u003Cth>What it typically holds\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Enterprise\u003C\u002Ftd>\n\u003Ctd>The brand kit, legal templates, who your customers are\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Team\u003C\u002Ftd>\n\u003Ctd>Keyword lists, a campaign calendar, the team's design exports\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Member\u003C\u002Ftd>\n\u003Ctd>Examples of how this member should write\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Role\u003C\u002Ftd>\n\u003Ctd>The brief template, the audit checklist the job uses\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Task\u003C\u002Ftd>\n\u003Ctd>The last good example, a schema, test fixtures\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>A run's own drafts and traces are not a layer. They stay on the run, and nothing carries them forward by itself.\u003C\u002Fp>\n\u003Ch2 id=\"what-a-run-reads\">What a run reads\u003C\u002Fh2>\n\u003Cp>A run will read the named files its skill asks for, from its own layers and every layer above them: task, role,\nmember, team, then enterprise. It does not load every file it could read. The skill names the paths it needs, and\nonly those are fetched.\u003C\u002Fp>\n\u003Cp>The same path further down replaces the one above it. If the enterprise keeps \u003Ccode>brand\u002Flogo.svg\u003C\u002Fcode> and the Marketing\nteam keeps its own \u003Ccode>brand\u002Flogo.svg\u003C\u002Fcode>, Marketing's runs get Marketing's file and every other run gets the\nenterprise's.\u003C\u002Fp>\n\u003Cp>Some collections (contracts, payroll) will be restricted: only the members and tasks you name can read them.\u003C\u002Fp>\n\u003Ch2 id=\"keeping-a-runs-output\">Keeping a run's output\u003C\u002Fh2>\n\u003Cp>A run's output does not become an asset by itself. To keep one, you promote it to a layer: a draft that worked\nbecomes the task's last good example. A run may promote only to a layer it has been given write access to, and that\naccess is a grant, not a default:\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Layer\u003C\u002Fth>\n\u003Cth>Who can grant write\u003C\u002Fth>\n\u003Cth>A task's own runs, by default\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Task\u003C\u002Ftd>\n\u003Ctd>A holder of the task's role, the team lead, the COO, you\u003C\u002Ftd>\n\u003Ctd>Allowed\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Member\u003C\u002Ftd>\n\u003Ctd>The member's lead, the COO, you\u003C\u002Ftd>\n\u003Ctd>Off\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Role\u003C\u002Ftd>\n\u003Ctd>The team lead, the COO, you\u003C\u002Ftd>\n\u003Ctd>Off\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Team\u003C\u002Ftd>\n\u003Ctd>The team lead, the COO, you\u003C\u002Ftd>\n\u003Ctd>Off\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Enterprise\u003C\u002Ftd>\n\u003Ctd>The COO, you\u003C\u002Ftd>\n\u003Ctd>Off\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"assets-and-clones\">Assets and clones\u003C\u002Fh2>\n\u003Cp>A task you publish will be able to share task-level assets you mark as shareable, such as a blank template or an\nexample schema. Customer files, and every asset above the task layer, are never part of a clone.\u003C\u002Fp>\n\u003Ch2 id=\"until-then\">Until then\u003C\u002Fh2>\n\u003Cp>Nothing on this page is built yet. Today a task's working knowledge lives in its skill text and in\n\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fmemory\">memory\u003C\u002Fa>, a run's files live in its \u003Ca href=\"\u002Fdocs\u002Ftools\u002Fworkspaces\">workspace\u003C\u002Fa> until the run ends,\nand the links a piece of work produces (the issue, the pull request, the preview) are attached to its\n\u003Ca href=\"\u002Fdocs\u002Fwork\u002Fexecutions\">execution\u003C\u002Fa>.\u003C\u002Fp>\n",[12,17,20,23,26,29],{"id":13,"text":14,"level":15,"planned":16},"what-an-asset-is","What an asset is",2,false,{"id":18,"text":19,"level":15,"planned":16},"where-assets-live","Where assets live",{"id":21,"text":22,"level":15,"planned":16},"what-a-run-reads","What a run reads",{"id":24,"text":25,"level":15,"planned":16},"keeping-a-runs-output","Keeping a run's output",{"id":27,"text":28,"level":15,"planned":16},"assets-and-clones","Assets and clones",{"id":30,"text":31,"level":15,"planned":16},"until-then","Until then",1791124519583]