🜁 AetherOS Core Philosophy

Purpose

AetherOS provides a minimal, trusted, predictable foundation built on upstream Linux ecosystems.

It preserves upstream development models while adding disciplined tooling, reproducible installation paths, and explicit trust boundaries.

AetherOS is not a fork — it is a framework for clarity.

Why AetherOS Exists

Traditional Linux distributions make assumptions:

• default package sets
• opinionated desktops
• implicit trust inheritance
• hidden automation
• unpredictable dependency chains

AetherOS removes assumptions and replaces them with intentional choices:

• minimal environment
• explicit package and repo origins
• reproducible installation paths
• user-defined system roles

Core Principles

1. Upstream Alignment

AetherOS maintains alignment with its base distro:

• no silent patching
• no diverging from native package managers
• repo priority behavior must be explicit and auditable

This avoids fragmentation and preserves user expectations.

2. Minimal Baseline with Remote Control Support

Every edition begins as a minimal environment containing only:

• networking stack
• SSH server
• minimal tooling required to update + verify packages

This enables:

• remote installation and configuration
• automation-friendly provisioning
• lightweight live environment workflows

Minimalism does not mean isolation — only intentional components.

3. Reproducible Installation via Rust TUI

AetherOS provides a reproducible installer implemented in Rust:

• no Python dependency chain
• deterministic components and behavior
• same installer UX across all editions
• scriptable profiles and automation hooks

The installer guides without abstracting system state.

4. Predictability Over Convenience

Predictability means:

• no hidden defaults
• no automatic background configuration
• no assumptions about workloads
• clear paths for rollback/upgrade
• transparent repo trust hierarchy

AetherOS avoids “magic” in favor of control.

5. Explicit Trust Boundaries

AetherOS enforces clear boundaries for:

• package provenance
• signing keys + subkeys
• repo ordering / update source priority
• optional risk escalation via repo selection

A system must be able to answer “why do I trust this software?”

6. Edition Identity Through Upstream + Element

Each edition reflects an upstream base and philosophical role:

• 🔥 Ignis — curated, stable Arch snapshot repo
• 🌬 Aer — rolling Arch upstream + fast overlay repo
• 💧 Aqua — Fedora minimal + stable cadence
• 🪨 Terra — Debian LTS minimal and conservative

Elements express risk tolerance and lifecycle, not branding fluff.

Access + Security Defaults

AetherOS provides universal remote-access guarantees:

• SSH enabled with transparent configuration
• live environment root password defaults to toor
• installer allows users to:
  • change password
  • remove password
  • disable password authentication entirely

This balances usability + security while remaining transparent and intentional.

What AetherOS Will Not Do

AetherOS avoids behaviors that erode trust:

• inventing a new package format
• modifying upstream packages silently
• enabling background services without disclosure
• shipping unnecessary software “for convenience”
• masking risk from users

The system stays intentional, visible, and auditable.

Long-Term Vision

AetherOS builds toward a Linux ecosystem where systems are:

• minimal and composable
• upstream-compatible
• remotely provisionable
• reproducible end-to-end
• predictable and secure by discipline
• transparent at every trust boundary

AetherOS gives users tools, not assumptions.

Edition Philosophies

The following editions apply the core principles to specific upstream bases. Each balances minimalism, predictability, and user control differently.