#Phase1 v4.2.0 Stable

192 messages · Page 1 of 1 (latest)

somber copper
#

Introducing Phase1 v4.2.0 Stable.

A terminal-based computing system built for safe operation, offline-first control, WASI-lite sandboxing, storage/Git/Rust workflows, Neo Tokyo operator UI, persistent history redaction, and a validated 100/100 quality score.

Built by Chase Bryan / Bryforge.

GitHub: github.com/Bryforge/phase1

nova bear
#

What can a human being do with this?

forest coral
#

the github link doesn't even work properly..

#

holy shit that's a lot of markdown files

#
fn compact_path(path: &Path) -> String {
    let raw = path.display().to_string();
    if raw == "/home" {
        "~".to_string()
    } else if raw.starts_with("/home/") {
        raw.replacen("/home", "~", 1)
    } else {
        raw
    }
}
#
//! AI-NOTE: Keep this crate free of terminal input loops and host-specific UI.
//! Core code should be deterministic, testable, and safe to call from tools.

#[path = "../../src/arena.rs"]
pub mod arena;
pub mod history;
#[path = "../../src/kernel.rs"]
pub mod kernel;
#[path = "../../src/ops_log.rs"]
pub mod ops_log;
#[path = "../../src/policy.rs"]
pub mod policy;
#[path = "../../src/registry.rs"]
pub mod registry;
#[path = "../../src/text.rs"]
pub mod text;
#

cross-crate file inclusion paths

#

instead of just structuring the crates correctly

nova bear
#

src/arena.rs seems to implement a 2D game somehow, who knows what it's doing there

#

src/browser.rsdefines a unit struct with methods which all take a &self as parameter, including a fetch_url which spawns a curl process with a 2 seconds timeout

#

and somehow tries to implement html rendering?

forest coral
nova bear
forest coral
#

"neural sync"

#

honestly entirely inscrutable as to what this does

#

i love that everything has 3 redundant ways of toggling it though

#

as far as i can tell it's a somewhat wonky looking TUI/CLI for an emulated OS that does???????? nothing particularly noteworthy

forest coral
# nova bear oh of course, that makes so much more sense now... -# still no idea why there is...
phase1://root ~ ❯ arena start
Phase1 Arena
usage : arena [start|demo|script <commands...>|roadmap|dev|test-plan|help]
play  : run `arena start`, then use w/a/s/d, fire, map, help, quit
goal  : clear hostiles, grab supplies, and reach E
note  : original ASCII arena; no proprietary game assets or WAD files are used


phase1 arena // clean-room text-mode game
asset mode: original ASCII, no external WAD or proprietary assets required
hp=30 ammo=8 dir=east kills=0 enemies=2 status=live
#############
#@..#....M..#
#.#.#.###.#.#
#.#...#...#.#
#.###.#.#.#E#
#.....#.#...#
###.#...#.###
#A..#..M..H.#
#############
safe rock
#

fastfetch

("Memory", "2.0/4.0 GiB sim".to_string()),
forest coral
#

lol

#

also curious what the 'validated 100/100 quality score' is meant to be

#

oh there's a QUALITY_AUDIT.md

#

apparently it means that cargo [check|clippy|fmt] --all-targets passes,

nova bear
#

and some clippy lints are turned off

forest coral
#

cargo deny check passes!

#
/tmp/phase1 ❯ rg -t toml -F '[dependencies]' -A3
Cargo.toml
28:[dependencies]
29-
30-[workspace]
31-members = [".", "phase1-core", "xtask"]

phase1-core/Cargo.toml
12:[dependencies]

xtask/Cargo.toml
10:[dependencies]
#

right

#

the .wasm plugins are all empty files, except for game.wasm and arena.wasm which are plain-text 'marker' files

nova bear
#

like there's this in their Cargo.toml:

[lints.clippy]
# Rust 1.95 tightened several style lints that do not change Phase1 behavior.
# Keep the quality gate stable while these areas are refactored in the next pass.
collapsible_match = "allow"
iter_skip_next = "allow"
manual_contains = "allow"
never_loop = "allow"
question_mark = "allow"
unnecessary_lazy_evaluations = "allow"

that reads like "rules have become stricter and i don't understand them"

forest coral
#

'look ma no warnings'

somber copper
nova bear
somber copper
nova bear
#

they're just full of buzzwords without any meaningful description of the project

#

it might tell a lot of things about what your project supposedly does, but i've not seen anywhere it describes what people can use it for

somber copper
#

Imagine being able to test systems level code in a safe environment that does not affect the host system

nova bear
#

ok, then do you use it for systems development?

somber copper
#

It is comparable to Qubes, but they have very different goals

somber copper
#

Right now, the stable release is the foundation for something greater. BASE1 will be capable of hardware installation

#

There is an intelligence built into the system

#

It learns you and builds itself from what you do with it

#

There is also an AI cybersecurity tool called GINA

#

It is effectively a “smart” system

#

I’m still working on furthering this atm but as it stands, it is successful in ways that I have yet to see in the computer science community

forest coral
somber copper
forest coral
#

can i copy files from the host system into the vfs?

#

the other way around?

somber copper
#

I have only tested GCC and python but support for all major programming languages is in the works for the roadmap.

#

Hold pls. I’ll make you a quick start guide for your questions

#

Right now, my main focus is the system itself and less so the features I am aiming for but they are in place for development in the future

somber copper
# forest coral how can i compile my code inside of the phase1 vfs?

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.

#

Rust/helper examples may use the guarded host-tool flow:

txt PHASE1_SAFE_MODE=0 PHASE1_ALLOW_HOST_TOOLS=1 cargo run --bin phase1-storage -- rust version

Major programming language support is planned through the runtime roadmap, but not every language should be considered stable yet.

6. Do I need a bespoke compiler target?

Not right now.

For current Phase1 development, code can target normal host-backed toolchains like Python and GCC/Clang while living inside the Phase1 VFS workflow.

A bespoke compiler target would only become necessary later if Phase1 grows into a true standalone execution target with its own ABI/syscalls/binary format. For v4.2.0 Stable, the correct path is:

txt VFS source files + guarded host toolchains + Phase1 shell/runtime commands

forest coral
#

so i can't currently run git clone or cargo build inside the VFS?

somber copper
# forest coral so i can't currently run `git clone` or `cargo build` inside the VFS?

Correct — not as fully native VFS commands yet.

Right now, Phase1 v4.2.0 can use guarded host-tool integration, so the workflow is closer to:

txt host git/cargo → Phase1 workspace/storage bridge → files available to Phase1 VFS/runtime

rather than:

txt inside Phase1 VFS → git clone → cargo build

So for now, git clone and cargo build should be treated as host-integrated / experimental, not stable native VFS features.

The tested stable paths are mainly Python and GCC/Clang-style compilation. Git, Rust, and full language toolchain support are on the roadmap, with the goal being that Phase1 can eventually manage projects, clone repos, build Rust code, and support major languages more directly from inside the Phase1 environment.

forest coral
#

i can't run python without disabling all the security layers, though

fluid stump
#

@somber copper it seems more like something imitating shell instead of actual operating system

forest coral
#

and it seems to just execute the python on my system, on my host filesystem, with no user input connected and a non-configurable timeout

#

I'm not sure what security benefit i get from anything here?

#
phase1://root ~ ❯ python -c 'with open("/etc/passwd") as f: print(f.readline())'
root:x:0:0::/root:/usr/bin/zsh
somber copper
# forest coral I'm not sure what security benefit i get from anything here?

That’s fair criticism, and I don’t want to oversell what it currently is.

Right now Phase1 is closer to a terminal-based runtime / shell environment with a VFS layer and guarded host-tool execution. It is not yet a fully independent operating system with native process isolation, native package management, or native compiler/toolchain execution inside the VFS.

For Python specifically, if running it requires disabling the security layers, then I would consider that path experimental, not a stable secure feature. The current benefit is mostly command gating, workspace separation, and limiting how host tools are invoked — but you’re right that if it just executes host Python directly without proper stdin handling, configurable timeout, and strong sandboxing, then the security story is incomplete.

The correct next step for Phase1 would be to improve this by adding:

  • proper stdin/stdout/stderr bridging
  • configurable execution timeouts
  • a real per-command permission model
  • workspace-only filesystem access
  • stronger sandboxing for host tools
  • audit logs for every host-integrated command
  • clearer separation between “native VFS command” and “host-integrated command”

So the honest answer is: Phase1 has the foundation for a protected dev environment, but Python/Git/Cargo execution is not yet where I want it to be. That feedback is valid and gives me a clear roadmap item: make host-tool execution actually sandboxed, configurable, and useful without needing to disable the safety model.

forest coral
#

Yeah for something called 'guarded host-tool execution' I would expect it to actually guard execution and not just... prevent me from running anything unless I disable all of the security. That is actively detrimental to testing code in a supposedly secure environment after all

somber copper
# forest coral Yeah for something called 'guarded host-tool execution' I would expect it to act...

You’re right. That criticism is valid.

If the current model requires disabling the safety layer to run Python or host tools, then it should not be presented as secure guarded execution yet. At best, it is an experimental host-tool bridge with restrictive gating.

A real guarded execution model should let you run code with security enabled, not force you to bypass the security model first. The guard should control execution through things like:

  • workspace-only filesystem access
  • stdin/stdout/stderr passthrough
  • configurable timeouts
  • explicit per-command permissions
  • denied access outside the Phase1 workspace
  • audit logs
  • clear distinction between VFS-native commands and host-backed commands

So I agree with you: the current behavior is detrimental for testing code in a secure environment.

I’m going to treat this as a priority fix. Until that is implemented, I’ll describe Python/Git/Cargo support as experimental host integration, not stable secure execution. Thank you.

valid verge
fluid stump
safe rock
#

i have never seen a person that abandoned it's own personhood in order to become a vessel for an LLM until today

somber copper
nova bear
#

even if your answer ends up being "this is not supported yet", you should know that yourself, right?

somber copper
nova bear
# somber copper Sorry. It’s an advanced concept in computing. Please read the manuals if you can...

You're missing my point. It's not about me specifically needing answers which I want to find in your documentation, it's about you being able to recognise a specific feature is not yet implemented without forwarding the question to an LLM. Especially for questions like "is X implemented or not" it's very slow to go through your docs as they don't mention anything "not done yet", (except for the roadmap i would assume)

somber copper
#

There is a learning curve. If it’s not for you, then I understand.

nova bear
#

I'm completely fine with steep learning curves, assuming the opposite of me would very wrong.

nova bear
# somber copper Assuming will do you no favors.

I find it weird you quote my use of "assume" to base your response on as it would be bad to "assume" things. To no longer be making assumptions, I went and read the roadmap in question. Contains nothing relevant to the project. Only things about the website, half-way seems like instructions you will give to an LLM to generate more things on the website.

So there is nowhere in your documentation or roadmap describing what features aren't implemented or planned for later, so my messages at #1502274820111466506 message still stand in my opinion.

Anyways, I feel like I'm not going to get much out of this conversation and will probably leave you do whatever you think you are doing

pearl totem
noble sparrow
#

how is this better than a firecracker/cloud-hypervisor/... vm with mounted host directories

somber copper
somber copper
#

Please also keep in mind that this project is 4 days old

somber copper
#

Nested phase1 inside of phase1 🤔

crimson cobalt
#

How do you run python in this?

#

And what even is this? Some fancy colored shell?

somber copper
crimson cobalt
somber copper
somber copper
#

Me building phase1 from within phase1

crimson cobalt
somber copper
#

Oh. Wait. Now it is.

#

Lmao yo same

crimson cobalt
somber copper
somber copper
#

I have things to do better today than argue with you over computer science

crimson cobalt
somber copper
somber copper
crimson cobalt
somber copper
#

Buddy, we are not even in the same league. I’m not competing with you. Please order my book when it comes out for $150

crimson cobalt
#

Well bye, I also have better things to do than argue

young knot
#

This is wild. What a world we are living in.

somber copper
#

🔥😎

devout lynx
#

I mean

#

Whats the point of letting an LLM doing a project that you don’t understand + does not help you with something you dealt with

#

Where does it is even useful compared to a VM?

pearl totem
# somber copper

I love how you can see they dont even read the contents of their own screenshots because every normal person using a shell would go crazy with the inconsistency of that system prompt. Sometimes, there's a prompt before a user command and sometimes before program output. Sometimes you also just dont have a prompt for your input

somber copper
#

But keep on keeping on.

#

I guess you’d know that though - ya know - if you actually knew how to read a sentence. Same with the design documentations. 😩 Jesus. It saddens me that people hate and don’t even understand what they are talking about.

#

I guess I’ll just have to keep working on it. I enjoy the pain. 😈

somber copper
devout lynx
#

First working != useful

somber copper
devout lynx
#

And also what is the point of that thing compared to vms

somber copper
#

No longer feeding trolls

#

To do list

devout lynx
devout lynx
somber copper
#

🤣 I’m the future, baby

#

Nice to meet ya

devout lynx
#

somber copper
devout lynx
#

And whyd you use it

devout lynx
somber copper
devout lynx
somber copper
devout lynx
#

Seems the opposite

somber copper
#

People here have been extremely rude

devout lynx
#

Because your project honestly looks like AI slop

somber copper
#

Fuck off idiot

devout lynx
#

Like just look at your project root

somber copper
torpid glade
somber copper
devout lynx
#

Pls wake up and uninstall this LLM from your mind

somber copper
#

I mean, it’s there an all

devout lynx
somber copper
#

Actually never mind

devout lynx
#

You did not name it ig

nova bear
#

surely this is how text alignment works in "the future"

somber copper
#

Oh wait. I am. Just flawed sometimes

somber copper
#

You have talked trash the entire way from the beginning and when I did what you couldn’t you got mad 😠 cheer up bro

#

Oh. I forgot about not feeding the trolls

#

STARVE

nova bear
somber copper
#

I can make snes run within phase1

#

Not the same

devout lynx
nova bear
somber copper
#

Uh huh sure

somber copper
nova bear
#

"Arch" as in arch linux? that's not a snes emulator, that's a linux distribution

somber copper
#

It’s for advanced emulator users

#

Probably google will help you once in awhile

nova bear
somber copper
#

And I’m building an operating system that nests itself within itself and has its own programming language and support for all major prog languages

#

So yeah 👍

#

Play games

#

You get more done that way

#

Probably haven’t even caught them all in red yet

#

??????????

#

💁🏻