Phase1 v4.2.0 Stable — VFS / Dev Quick Start
Phase1 currently supports a practical dev workflow through its internal VFS plus guarded host-tool integration. You do not need a bespoke compiler target right now for normal C/Python-style development.
Think of it like this:
Phase1 VFS file → Phase1 command → guarded host toolchain → output back into Phase1
1. Working inside the Phase1 VFS
Inside Phase1, the VFS supports normal file-style commands such as:
txt ls cd pwd mkdir touch cat cp mv rm tree
Example:
txt mkdir /home/dev cd /home/dev touch hello.c
You can create or edit files locally inside Phase1, then run them through the available language commands.
2. Running Python
Python is one of the tested paths.
txt python -c "print('hello from Phase1')"
or:
txt python hello.py
3. Compiling C with GCC/Clang
C compilation has been tested through the host compiler path.
txt gcc hello.c
Phase1 looks for a host compiler such as gcc or clang, runs it through a guarded execution layer, and returns the output.
So the project does not currently require a custom Phase1 compiler backend for this workflow.
4. Copying and moving files
Inside the VFS, use:
txt cp source.txt copy.txt mv old.txt new.txt
For host ↔ VFS workflows, Phase1 uses the guarded storage/workspace model rather than unrestricted host filesystem access. The default workspace is:
txt phase1.workspace
Host-integrated operations are intentionally guarded for safety. Mutating host actions require explicit trust flags:
txt PHASE1_SAFE_MODE=0 PHASE1_ALLOW_HOST_TOOLS=1
Useful host-side helper checks:
txt cargo run --bin phase1-storage -- storage status cargo run --bin phase1-storage -- storage doctor cargo run --bin phase1-storage -- lang roadmap
5. Git / Rust / other languages
Git and Rust support are part of the storage/runtime roadmap and helper system. GCC/Clang and Python are the primary tested paths right now.