Phase 60

Networking And GitHub

m3OS can use authenticated outbound network tooling for real developer workflows: DNS works, HTTPS is trustworthy enough for the supported use cases, git can speak to remotes, and the GitHub CLI runs inside the OS.

Planned

Learning goal

Understand how DNS resolution, HTTPS, and authenticated developer tooling build on the earlier security and networking layers.

Why this phase matters

How it works in m3OS

The roadmap entry defines the learning scope for this phase; a deeper implementation doc has not been matched yet.

How it builds on earlier phases

This phase builds on Cross Compiled Toolchains and turns that foundation into Networking And GitHub.

Implementation outline

Define the supported resolver and HTTPS trust configuration for the phase.
Choose and implement the supported git remote transport path.
Bundle and validate the GitHub CLI workflow.
Test authenticated remote workflows inside the supported environment.
Update support docs and post-1.0 roadmap notes to match the shipped behavior.

Task progress snapshot

No checklist tasks were discovered for this phase yet.

Documentation targets

Documentation deliverables have not been listed yet.

Deferred follow-on work

Full workstation-grade browser and GUI networking stack
Rich credential-helper ecosystems
Large language-specific package managers that depend on heavier runtimes
Broad general internet-client expectations beyond the supported developer tools

Source materials

Roadmap entry

Important code

Code spotlight cards

When the phase lands, bump kernel/Cargo.toml and any release/version references to 0.60.0.

View on GitHub

Key files

kernel/Cargo.toml — When the phase lands, bump kernel/Cargo.toml and any release/version references to 0.60.0.

How real OSes differ

Mature systems support far more network tools, trust stores, background services, and credential helpers than m3OS should assume here.
The goal is not to duplicate a modern Linux workstation; it is to support a small, credible remote developer workflow.
Strong trust boundaries matter even more once the system starts handling real authenticated network traffic.

Success criteria

The supported resolver configuration works for the documented outbound environment.
The chosen HTTPS trust path is documented and used by the supported developer tools.
git can perform the documented remote workflows inside m3OS.
The GitHub CLI can complete the documented authenticated workflows inside m3OS.
The phase docs clearly describe the supported remote workflows and their limits.

Related phases

Keep exploring the roadmap

Cross Compiled Toolchains

m3OS can host larger post-1.0 development tools built on the host and bundled into the disk image. git, Python, and Clang become routine parts of the developer environment instead of future one-off experiments.

Node.js

Node.js runs natively inside m3OS with the documented level of runtime and networking support, and npm can install the packages needed by the later CLI-agent phase.