OrganicOS Evolution Map

This page is the first pass at explaining how OrganicOS came together. It is based on local notes, project roots, runtime evidence, and the current portal inventory. It should be treated as a working map, not final public wording.

Core Lineage

OrganicOS did not start as one clean product repository. It evolved through several overlapping lines of work:

• a Linux host that became a heavily customized Plasma/X11 desktop;
• Organic Glass as an Electron-based shell, launcher, panel, and assistant surface;
• Nebula and OpenClaw as the assistant reasoning, memory, orchestration, and tool layer;
• Home Assistant, Kokoro, OpenWebUI, Ollama, and voice services as local automation and AI infrastructure;
• Apollo, Supernova, Moonlight, and capture work as the remote display and streaming transport layer;
• Input Nebula, ADB, scrcpy, and Waydroid as Android and phone-control layers;
• Tailscale Serve as the private HTTPS access layer for local services.

The important idea is that OrganicOS is not just a themed Linux desktop. The theme, shell, assistant, streaming, device-control, and service-mesh pieces are all attempts to make the computer feel like one adaptive environment.

Phases

Phase 0: Concept and Direction

The OrganicQuantumAiOS concept and local Organic. OS concept material establish the philosophical direction: intelligence should be structural, not bolted on as a chat app.

This phase is aspirational. It includes ideas such as AI-native OS behavior, adaptive interfaces, and deeper human-machine integration.

Phase 1: Local Desktop and Visual Identity

OrganicOS then became concrete through local shell work:

• KDE Plasma customization;
• OrganicOS shell, icon, cursor, color, boot, and wallpaper assets;
• Organic boot loop media;
• Plasma wallpaper application experiments;
• Moonlight Nebula wallpaper work;
• freeze points and rollback snapshots for known-good desktop states.

This phase made OrganicOS visible and usable on the live Linux desktop.

Phase 2: Organic Glass as the First Embodiment

Organic Glass became the main custom UI surface. It collects panels and utilities into one desktop-adjacent shell:

• launcher and app tiles;
• assistant panels;
• text assistant surface;
• Nova Terminal;
• media and nexus panels;
• overlay HUD;
• Kokoro voice/TTS surfaces;
• wrappers for Home Assistant, Jellyfin, Cockpit, OpenWebUI, and OpenClaw.

This phase moved OrganicOS from visual identity into a working interface layer.

Phase 3: Nebula and OpenClaw as System Intelligence

Nebula/OpenClaw became the working brain layer:

• memory and project context;
• tool and command orchestration;
• local system mapping;
• assistant skills;
• service awareness;
• long-running documentation and cleanup planning.

The target is one assistant identity across CLI, portal, voice, desktop UI, and remote surfaces.

Phase 4: Streaming and Remote Display

Apollo, Supernova, Moonlight, and capture work became core infrastructure, not just game-streaming extras.

This matters because OrganicOS is often operated through remoted or streamed surfaces rather than a simple local monitor. GPU capture, Supernova configuration, Moonlight Nebula, and Windows handoffs are part of the operating model.

Phase 5: Device and Android Boundary Work

Input Nebula, ADB, scrcpy, Input Leap, Waydroid, and phone mirroring extend OrganicOS beyond the Linux desktop.

The pattern is consistent with the larger vision: reduce the boundary between desktop, Android device, mobile runtime, and assistant control.

Phase 6: Local Web Portal and Documentation

The OrganicOS Portal is the current attempt to gather the system into a coherent documentation and navigation surface.

The portal should eventually explain:

• what OrganicOS is;
• which components are active;
• which repositories are canonical;
• how the system boots and runs;
• how the assistant stack works;
• how Windows, Linux, Android, and Tailscale fit together;
• what is public-safe and what must remain private.

Current Problem

The system exists, but the story is scattered across:

• local repos;
• upstream forks;
• handoff folders;
• freeze points;
• service units;
• private assistant notes;
• partial docs;
• active runtime state.

That is why GitHub currently feels confusing: the public profile does not yet reflect the real local system.

Working Summary

OrganicOS has evolved from concept, shell customization, and assistant experiments into a hybrid assistant-native operating environment. The next step is not more invention; it is consolidation:

• choose canonical repos;
• cleanly publish public-safe source;
• document the architecture;
• preserve private runtime/security details;
• turn the portal into the map that makes the system understandable.