operator shell · command map · safe defaults

Phase1 Command Reference

A public command map for the Phase1 operator shell. This page explains the command families, intended workflow, and safety boundaries for the Rust virtual OS console.

operator basics

Start with visibility.

Use these commands to learn the shell, inspect the current environment, and find the next documented workflow. Exact availability can vary by build, so help inside Phase1 remains the source of truth.

help

Show available commands and quick operator hints.

wiki

Open the in-system documentation hub.

man <command>

Read command-specific notes when a manual entry exists.

version

Display version track and release information.

sysinfo

Inspect simulated system profile and kernel state.

roadmap

Review project roadmap and implementation direction.

files + VFS

Operate inside the virtual filesystem.

The VFS is the main learning workspace. Use it to practice shell movement, create files, inspect generated system paths, and keep host files separated from the Phase1 environment.

pwd

Print the current virtual working directory.

ls

List files and folders in the current VFS path.

cd <path>

Move through the virtual filesystem.

cat <file>

Read a file from the VFS.

echo

Print text or create simple shell output.

mkdir <dir>

Create a virtual directory.

cp

Copy virtual files when supported by the current build.

mv

Move or rename virtual files when supported by the current build.

text tools

Inspect output like an operator.

Text tools make the terminal useful for learning and debugging. They are designed to help operators search, count, preview, and filter content inside the virtual environment.

grep

Search text for matching patterns.

find

Locate virtual files and paths.

wc

Count lines, words, or bytes when available.

head

Preview the beginning of a file or output.

tail

Preview the end of a file or log output.

clear

Clear or reset terminal display state.

system + safety

Guardrails are part of the interface.

Phase1 should make system state visible. Safety commands explain the current posture, audit behavior, and host-tool boundaries. They are not production security claims.

security

Show safe-mode posture and security guidance.

audit

Inspect audit records when audit views are available.

ps

Inspect simulated process table state.

/proc

Explore generated system views in the VFS.

capabilities

Review capability metadata when supported.

safe mode

Understand default guarded behavior before enabling host workflows.

browser + network

Network workflows stay explicit.

The guarded browser is intended for inspectable terminal-first browsing. It should avoid hidden background behavior and keep active content, host trust, and network access easy to reason about.

browse

Open a URL through the guarded terminal browser path.

html

Inspect stripped or simplified page output when supported.

headers

View HTTP metadata when exposed by the current build.

safe schemes

Review supported schemes and boundary notes.

storage + runtime roadmap

Build workflows belong behind clear controls.

Storage, Git, Rust, and future language runtime workflows are planned around explicit capabilities. When a command crosses into host-backed behavior, it should stay guarded and visible.

storage

Inspect storage status and workspace behavior.

git

Planned/guarded repository workflows for clone and project setup.

cargo

Rust workflow path for build/run support where enabled.

lang

Show the language/runtime support roadmap.

runtime

Track planned runtime shells and language integrations.

doctor

Planned diagnostics for environment and build readiness.

troubleshooting

Common command issues.

  • Command not found: run help in the current build and check the wiki hub for the matching command family.
  • Host tool blocked: confirm safe-mode and trust settings before trying host-backed workflows.
  • Browser output looks limited: guarded browsing may strip or simplify active web content by design.
  • Runtime command unavailable: check the runtime roadmap; some language commands are planned rather than implemented.

boundary

Command docs are implementation guidance, not production claims.

Phase1 is a Rust virtual OS console and operator-kernel project. This command reference does not claim that Phase1 is a production operating system, daily-driver OS, hardware-validated system, complete security product, or installer-ready distribution.

Back to Wiki Hub