Workspace boundaries

​

Definition

Rudder separates curated context, durable output, mutable project work, private Agent state, and temporary files. The location determines who can find a file, whether it can enter a later Run, and which recovery rules apply.

​

States and locations

​

Constraints

• A Project may have several workspaces but only one primary workspace.
• Project Context is an admission list. Rudder does not inject every organization resource into every Run.
• Protected instructions, Skills, runtime directories, credentials, and cache paths are not ordinary Library content.
• A Run workspace cannot be archived while open Issues still depend on it.
• Restoring a workspace backup creates a pre-restore safety version first.

​

Boundaries

Library paths remain organization-scoped and pass path validation. Desktop open actions do not let browser deployments open local applications, and a validated file link does not expose its absolute filesystem root. In the default local Desktop layout, organization files use a stable mapping under ~/Documents/Rudder. If an established mapped folder disappears, Rudder treats it as a recovery problem. It does not create an empty replacement over the missing location.

​

Examples

• Keep source notes in Library, attach only the notes needed by a project, and save the accepted report in that project’s Library folder.
• Let a coding Run use the primary project repository or an explicit isolated Run workspace. Keep build caches and temporary screenshots out of Library.
• Browse the selected backup before restoring it. If an open Issue still uses a Run workspace, finish or move that dependency before archive.