Definition
Rudder uses several file boundaries because background context, durable output, and mutable execution work have different jobs.
Project resources are an admission list, not every file in the organization.
An output should remain connected to the Chat, Issue, Run, or project that
produced it instead of existing only inside a transcript.
One illustrative case
A consulting team prepares a client brief. Source notes live in Library and are attached to the project as curated resources. The Agent works in the project’s repository through a run workspace, then saves the final brief in the project Library folder and links it from the review Issue. A later run can find the accepted brief without inheriting every scratch file from the first attempt.
When each location is useful
Use Library for files that should remain part of the organization record. Add a file as a project resource only when project-linked runs should receive it as starting context. Use a project workspace for repository work and a run workspace when changes need an explicit isolation strategy. Keep temporary artifacts outside Library unless they are part of the final evidence. On the default local Desktop layout, organization files live in a mapped folder under~/Documents/Rudder. The mapping uses organization identity, so renaming
the organization does not silently move its files.