Assets
Files and links the company keeps at each layer, which a run reads by name and adds to only where you allow it.
Planned. What this page describes is not built yet.
What an asset is
An asset will be a named file or link the company keeps: a logo, a brief template, a spreadsheet, a checklist, a
last good example. It is not memory. You do not ask an asset a question; a run reads it by
its path, such as brand/logo.svg or briefs/seo.md.
A link to a system you have not connected yet (a dashboard, a shared folder) will be an asset too, until you connect the system as a tool.
Where assets live
Assets will sit on the same layers as the rest of the company:
| Layer | What it typically holds |
|---|---|
| Enterprise | The brand kit, legal templates, who your customers are |
| Team | Keyword lists, a campaign calendar, the team's design exports |
| Member | Examples of how this member should write |
| Role | The brief template, the audit checklist the job uses |
| Task | The last good example, a schema, test fixtures |
A run's own drafts and traces are not a layer. They stay on the run, and nothing carries them forward by itself.
What a run reads
A run will read the named files its skill asks for, from its own layers and every layer above them: task, role, member, team, then enterprise. It does not load every file it could read. The skill names the paths it needs, and only those are fetched.
The same path further down replaces the one above it. If the enterprise keeps brand/logo.svg and the Marketing
team keeps its own brand/logo.svg, Marketing's runs get Marketing's file and every other run gets the
enterprise's.
Some collections (contracts, payroll) will be restricted: only the members and tasks you name can read them.
Keeping a run's output
A run's output does not become an asset by itself. To keep one, you promote it to a layer: a draft that worked becomes the task's last good example. A run may promote only to a layer it has been given write access to, and that access is a grant, not a default:
| Layer | Who can grant write | A task's own runs, by default |
|---|---|---|
| Task | A holder of the task's role, the team lead, the COO, you | Allowed |
| Member | The member's lead, the COO, you | Off |
| Role | The team lead, the COO, you | Off |
| Team | The team lead, the COO, you | Off |
| Enterprise | The COO, you | Off |
Assets and clones
A task you publish will be able to share task-level assets you mark as shareable, such as a blank template or an example schema. Customer files, and every asset above the task layer, are never part of a clone.
Until then
Nothing on this page is built yet. Today a task's working knowledge lives in its skill text and in memory, a run's files live in its workspace until the run ends, and the links a piece of work produces (the issue, the pull request, the preview) are attached to its execution.