GIOS Studioalpha · read-only
Filesystem Explorer
Given an approved computer plan, how is work represented inside a filesystem? Node/volume model only — the runtime touches no filesystem. Approval-gated. Read-only.
3
Sessions
11
Nodes
14
Operations
8
Approval barriers
Filesystem pipeline representationwaiting_approval
1 volume · 3 node · 5 op · 2 snapshot
snapshotread_filewrite_filediff1 approval
Filesystem build-artifact representationwaiting_approval
1 volume · 3 node · 4 op · 0 snapshot
read_filecreate_directoryset_permissionwatch2 approval
Filesystem archive representationwaiting_approval
2 volume · 5 node · 5 op · 0 snapshot
copycreate_linkcreate_filemovedelete2 destructive5 approval
The Universal Filesystem Runtime owns only filesystem semantics (volumes, directories, files, links, paths, permissions, snapshots, diffs, watchers, artifacts). It represents HOW work maps onto a filesystem; it never reads, writes, or watches anything — real I/O is owned by the future Broker, gated on a binding Policy allow.