Systems

A System groups related Resources (and optional Subsystems) so you can share, browse, and version them together. Every System starts with a baseline branch. Edits to the branch create commits. For the conceptual model, see Systems and Subsystems. For branches, commits, and change requests, see Branches.

Browse Systems

1. Click Systems in the sidebar (or navigate to /systems).
2. You see a grid of system cards showing each System's name, description, creator, and creation date.
3. Use the global Search in the header (or press ⌘ K / Ctrl K) to find Systems by name or creator.
4. Systems load in pages. If more are available, a Load more button appears at the bottom of the grid.

Each system card displays:

• The System name (clickable — opens the System)
• Open this branch: with a branch picker to open the System on a chosen branch
• The creator's name and avatar
• The creation date
• An optional infosec badge if information security levels are enabled

Create a System

1. Navigate to the Systems page.
2. Click the Create button (with plus icon) in the top-right corner.
3. In the Create system dialog:
   • Enter a Name (defaults to "Untitled system").
   • Enter a Description (required).
4. Click Create.
5. You are redirected to the new System's detail page.

View System Details

1. From the Systems page, click a system card (or choose a branch with Open this branch:).
2. The System detail page has two main panels:
   • Left panel: Branch switcher and the Resource tree for the selected branch (or commit).
   • Right panel: Preview, metadata, and activity for the selected Resource or Subsystem.
3. Breadcrumbs at the top show: Systems > System Name. Hover over the System name to see its description.

Switch branches or open commit history from the branch controls in the left panel. Full steps are in Branches.

Edit a System

1. Open the System you want to edit.
2. Click the ⋯ (more options) menu in the top-right corner of the page.
3. Select Edit system details.
4. Update the Name and/or Description in the dialog.
5. Click Update.

Required role: Editor, Administrator, or Owner.

Copy System link, title, or ID

1. Open the System.
2. Click the ⋯ menu in the top-right corner.
3. Open Copy, then choose:
   • Copy URL — copies a link to the System
   • Copy title — copies the System name
   • Copy title as link — copies the name as a markdown link
   • Copy ID — copies the System ID

Archive a System

1. Open the System you want to archive.
2. Click the ⋯ menu in the top-right corner.
3. Select Archive system.
4. Confirm the action in the dialog that appears.

You can also archive a System from the Systems grid by clicking the ⋯ menu on the system card and selecting Archive.

Required role: Owner only.

Compare versions

1. Open a System.
2. In Commit history, click Compare versions (available when the branch has at least two commits).
3. In the diff viewer, choose the versions to compare and review what changed.

Required role: Viewer or above.

Edit Resources on a branch

To change which Resources and Subsystems a branch tracks:

1. Open the System and select the branch you want to change.
2. Click Edit files in the left panel.
3. In the builder:
   • Under FILES, add or remove tracked Resources from the library (or upload new files).
   • Under SYSTEMS, add or remove Subsystems (see System composition).
   • Organize Resources into folders in the tree when needed.
4. Click Save. Saving creates a new commit on the branch.

Required role: Editor or above.

For creating branches, browsing commit history, and merging with change requests, see Branches.

Accept newer Resource versions

When tracked Resources or Subsystems have newer versions available on the current branch, a New versions available banner appears in the left panel. Click Accept changes to create a commit that advances the branch to those versions.

Required role: Editor or above.

Upload files to a System

Drag and drop

1. Open the System detail page.
2. Drag files from your computer and drop them anywhere on the page.
3. The Upload Spec dialog appears — fill in metadata (display name, tags, infosec level, and so on).
4. After upload completes, add the files to the current branch with Edit files if they are not tracked yet.

Using the file tree

1. Click Edit files, then use Upload under FILES in the builder.
2. Select files from your computer and complete the upload dialog.

Required role: Editor or above.

Browse the Resource tree

1. Open a System and select a branch (or open a commit from commit history).
2. The left panel shows a file tree with:
   • Subsystems (when present), then tracked Resources.
   • Resources organized in a hierarchical folder structure when folders are in use.
   • Artifact groups nested under their parent files (grouped by the job that produced them).
   • Job group nodes showing the tool/function name that produced the artifacts (click the job name to view job details).
3. Click any file to view its preview, metadata, and actions in the right panel.

Folders

Folders organize Resources in a System into a hierarchy so a large System reads like a familiar directory tree — for example engineering/aero/ and scratch/. Folders are layout only: there is no separate folder object, and they do not grant or restrict access.

• Path-based. A folder exists only because Resources live in it. Empty folders disappear when the last Resource leaves them.
• Per branch. The layout belongs to the branch you are editing. Earlier commits keep the layout they were captured with.
• Saved as commits. Creating folders and moving Resources are edits. Save produces a new commit; Cancel discards the draft.

Browse folders

1. Open a System and select a branch or commit.
2. The left panel file tree shows Resources organized into their folders.
3. Click a folder to expand or collapse it; click a Resource to view its preview, metadata, and actions in the right panel.

Organize Resources into folders

Folder changes are made while editing the branch. Click Edit files, make your changes, then Save.

Create a folder

1. Open the System, select a branch, and click Edit files.
2. In the file tree, click New folder.
3. Type a folder name and click Create.
4. Move at least one Resource into the folder before you save — you cannot save while an empty folder exists.

Folder names can contain spaces and other characters; the platform stores them safely and displays the name you entered.

Move Resources into a folder

• Drag a Resource in the tree and drop it onto a folder to move it there.
• To move several at once, select multiple Resources and drag them onto the target folder together.
• Drop a Resource onto the System root to move it out of any folder.

Nest folders

Create a folder inside another, or drag a folder into another folder, to build a deeper hierarchy such as engineering/aero/.

Rename a folder

Rename a folder from the tree (the dialog reopens titled Rename folder). Renaming updates the location of every Resource inside it (and any nested folders), so the whole subtree moves with the new name.

Save folder changes

1. Make your folder and Resource changes while editing.
2. If any folder is empty, a reminder appears — "Add a file to each folder or remove it — empty folders can't be saved" — and saving stays disabled until you resolve it.
3. Click Save to capture a new commit with the new folder structure.
4. To abandon your changes, Cancel the draft — the System returns to its last saved state.

Required role: Editor or above on the System.

What folders do not change

• Resource names. Moving a Resource into a folder does not rename it. Renaming a Resource's display name is a separate action (see Files and Content).
• Access control. Folders do not grant or restrict access. Sharing and permissions are managed at the System and Resource level (see Sharing and Access Control).
• History. Earlier commits keep the folder layout they were captured with; reorganizing Resources does not rewrite past commits.

Download files

1. Open a System and select a branch or commit.
2. In the top action bar, click the Download button.
3. A Download selected files panel appears. Select the files you want from the tree.
4. Click Download to download the selected files.

System composition

You can track other Systems inside a System alongside Resources. Linked Systems appear as Subsystems in the Resource tree and can nest when those Systems track their own Subsystems.

View Subsystems in the file tree

1. Open a System and select a branch (or commit).
2. In the left panel file tree, Subsystem rows appear above tracked files (network icon and System name).
3. Expand a Subsystem to browse its tracked files and any nested Subsystems.
4. Click a Subsystem to open its summary in the right panel (System ID, classification, link metadata, and which version is tracked).
5. Click a file under a Subsystem to preview it in the right panel.

Use the Subsystem context menu (right-click) to Open subsystem, open Copy (Copy URL, Copy title, Copy title as link, or Copy ID), Set version source (baseline or a specific tag), Edit system details, Share, or Untrack subsystem.

Required role: Editor or above to add, change, or remove tracked Systems.

Add or edit tracked Systems

1. Open a System, select a branch, and click Edit files.
2. The builder splits the explorer:
   • Top: current tracked Subsystems and files for the branch.
   • Bottom: SYSTEMS and FILES library panels.
3. Under SYSTEMS, search or browse available Systems and click one to add it, or use Create system to add a new System inline.
4. For each tracked System, choose the version source — baseline or a specific tag — from the dropdown next to the System name when available.
5. Under FILES, add or remove tracked files as usual.
6. Click Save to create a commit on the branch.

You cannot add the current System or a System already tracked on the branch. Remove a draft Subsystem with the × control or Untrack subsystem in the context menu.

System Documents

Experimental feature

Enable System Documents in Application Settings → Experimental Features. See Settings.

When enabled:

1. A Documents section appears in the Resource tree.
2. Click a document to open it in the Document Editor in the right panel.
3. Toggle between View mode and Edit mode using the ?mode=edit URL parameter or the edit toggle in the UI.
4. Documents support export.

Edit permissions are controlled per-document based on individual document access grants.

For external runs whose outputs are uploaded back to the System, see Workflow log.