Start with what exists.
The public bootstrap is intentionally small: version output, diagnostics, module listing, and dry-run scan planning.
runtime.zero
A Rust-first terminal-native system management toolkit for people who want control without chaos.
rz0
Local control. Clear intent. No surprises. Report-first, dry-run-first, quarantine-first, explicit-confirmation-first.
- Status
- pre-alpha
- Phase
- bootstrap
- Targets
- win/mac/linux
- Mutation
- disabled
Diagnostics before action.
rz0 doctor reports local runtime state and keeps mutation capability visibly disabled.
Module boundaries stay visible.
rz0 modules separates active core primitives from planned platform and feature modules.
Dry-run is the default mental model.
rz0 scan --dry-run makes no system changes and says so directly.
First-party modules come later.
Inventory, updater, uninstall, leftovers, and quarantine capabilities should ship as explicit first-party choices.
Installation must be explainable.
Module installation needs publisher, checksum, signature, compatibility, and dry-run review before it becomes public UX.
Dangerous paths stay blocked.
Destructive workflows require report, risk review, quarantine or rollback story, and explicit confirmation.
foundation vs. first-party modules
rz0 is the safety-led foundation. Substantial capabilities live in modules users choose.
id
type
status
risk
mutates
summary
core.brandcoreactivenonenoCentralized build-time name and metadata.
core.clicoreactivenonenoSafe command parser and Phase 1 help surface.
core.doctorcoreactiveread-onlynoLocal runtime diagnostics.
core.scan-plancorestubdry-runnoDry-run-only scan placeholder.
platform.windowsplatformplannedread-onlynoWindows adapter for packages, registry, services, tasks, and AppData.
modules.updatemoduleplanneddry-rungatedInstalled-only update planning and orchestration.
modules.uninstallmoduleplannedmutatinggatedManager-native uninstall orchestration.
modules.leftoversmoduleplanneddestructivegatedReport-first leftover classification and quarantine planning.
Third-party modules may come later, but only after a hardened trust model with signing, provenance, permissions, revocation, and abuse review.
safety contract
runtime.zero is built on a clear promise.
report-first
Gather facts before taking action.
dry-run-first
Show what would happen before anything changes.
quarantine-first
Prefer quarantine and restore over deletion.
explicit-confirmation-first
Mutating actions require clear user intent.
No surprise installs. No silent modules. No credential, OAuth session, browser profile, workspace, backup, or unknown-data cleanup without explicit approval.
download / source
Current public state: source and contributor builds. Verified downloads come later.
now: source on GitHub
runtime.zero is open source. View the code, issues, roadmap, safety docs, and current command surface.
View on GitHub
contributor build
cargo install --path .
later: verified downloads
Public install commands should wait for reviewed release artifacts, checksums, signatures, and bootstrap safety.
- Cross-platform binaries
- Checksums and signatures
- Package-manager installs
- Auditable bootstrap command
Verified downloads coming later.