Files and artifacts
A playbook can carry authored files such as instructions, references, and schemas. A running task can also produce working files or artifacts such as a report or a generated image. Those files have different lifetimes and access rules.
Assign a lifecycle to each file
Section titled “Assign a lifecycle to each file”Authored, working, and published files
Section titled “Authored, working, and published files”| File | Scope and lifetime |
|---|---|
skills/verify-signals/SKILL.md |
Authored with the playbook and pinned with its revision |
| A generated draft in a task directory | Private to the run or member filesystem allowed by the team |
| An accepted report in Outputs | Published to an authorized workspace destination |
Retention is a workspace capability. A team must enable and verify a retained filesystem before relying on it across workflow tasks. Authorized artifact transfer, publication, and sharing are separate choices. Keep a stable reference or receipt for the exact accepted output.
Example private handoff
Section titled “Example private handoff”studio-output:run-meeting-review#/summaryThis reference selects the summary field of a completed accepted source run. Gabriel checks that the assignment is accepted under the same parent goal, team, workspace, and member scope before resolving it. Publishing the selected field to a team list still requires that destination’s grant and any applicable consent.
Failure and cleanup
Section titled “Failure and cleanup”If a retained workspace is unavailable, use the current run’s supported recovery path or ask the owner to restore it. A shared report should link to a verified accepted version rather than a transient sandbox path. When a file is revoked or removed, keep historical run receipts and apply the current access policy when opening evidence.
For a thread-scoped filesystem design, see Standard Agent Specification’s thread filesystem.
See skills, context and conversations, and the private handoff walkthrough.