GIOS Studioalpha · read-only
Terminal Explorer
Given an approved computer plan, how is work represented inside a terminal? Shell/PTY model only — the runtime spawns nothing. Approval-gated. Read-only.
3
Sessions
5
Commands
17
Actions
5
Approval barriers
Terminal build representationwaiting_approval
bash-family · 2 command · 6 action · 3 artifact
open_sessionrun_commandread_stdoutread_stderrclose_session1 approval
Terminal file pipeline representationwaiting_approval
posix · 2 command · 5 action · 3 artifact
open_sessionchange_directoryrun_commandclose_session1 approval
Terminal interactive representationwaiting_approval
pty-raw · 1 command · 6 action · 0 artifact
open_sessionrun_commandwrite_stdinread_stdoutsend_signal3 approval
The Universal Terminal Runtime owns only terminal semantics (shells, sessions, command graphs, stdin/stdout metadata, environment variable names, working directories, files touched, transcripts). It represents HOW work maps into a terminal; it never spawns a shell or process — real execution is owned by the future Broker, gated on a binding Policy allow.