Astrolobe OS

ASTROLOBE OS

ONE COMPUTER, OR AN ENTIRE WORLD.
High above Earth, a workstation is waiting for you.
Walk in. Approach your desk. Sit down. The monitors come alive.
Astrolobe OS is a computer you can enter.
Inside the orbital station is a working desktop with its own applications, files, windows, settings, and system tools. You can organize your work, browse the real web, make something, play a game, and come back to the same place. The room isn't decoration around a launcher. The computer is part of the experience.
Beneath the screens is a command-driven state engine. A Python kernel owns the computer's internal model; Godot gives it an interactive, three-dimensional form. Governed commands are validated, committed or rejected, and recorded in structured receipts. Supported event sequences can be replayed to reconstruct system state and check the result.
This is a Windows-hosted environment, not a replacement for Windows. But the computer you see has real rules for what it is, what it can do, and how its state changes.
Sit down to make something. Explore the station. Launch into a robot battle, a puzzle, or a mystery. Return to your desk when you're ready.
It's a working computing environment, a software platform, and a playable world connected together.
THE DESKTOP IS REAL SOFTWARE
Astrolobe OS contains a functioning desktop environment, not a collection of decorative buttons.
Open, move, resize, minimize, restore, focus, and close application windows.

Use a desktop, Start menu, taskbar, application search, and system settings.

Create folders, work with documents, and organize files inside the Astrolobe environment.

Open real websites through Astrolobe Browser, rather than a fictional in-game internet.

Use Notes and a bounded command shell to work with Astrolobe's files and application services.

Follow application activity through system tools, notifications, and event history.

Personalize the desktop with themes, wallpapers, and display preferences.

Use supported gamepads as well as mouse and keyboard input.

Astrolobe has its own file and application boundaries. It does not replace Windows or provide unrestricted control of your Windows files and processes. Connections to the host PC are handled through specific, permissioned interfaces.
The desktop has an actual system behind it. Programs have identities and lifecycles. Windows have ownership and focus. Files and settings have state. Actions can succeed, fail, and produce records explaining the result.
You're not looking at a computer-shaped menu. You're using the computer that lives inside the world.
A BROWSER FOR THE REAL INTERNET
Astrolobe Browser is designed to bring real websites into the desktop. It is not a simulated search engine or a set of scripted pages. The application includes a profile system intended to keep different browsing identities and sign-ins separate.
Like the rest of Astrolobe's software, its exact release integration and supported behavior will be confirmed against the shipping build.
YOUR DESK. YOUR WAY TO WORK.
The orbital environment gives that computer a physical place to exist.
Take your place at a personal workstation overlooking Earth.

Use a single-screen desk or a three-screen Creator Station.

Arrange your workspace around applications, creative work, or games.

Explore a space designed to make the act of using a computer feel like being somewhere.

Use display layouts designed for a wide range of screen shapes, from 4:3 to super-ultrawide.

The main workstation is your personal computing environment. The larger Command Center is a separate experience within the Astrolobe world.
THE SHARED COMMAND CENTER — IN DEVELOPMENT
The Command Center is being developed as an online collaborative space: ten surrounding offices, each with a desk, gathered around a central twelve-screen room. The design is intended to let people bring their own computer presence into a shared workspace, collaborate, and move between private desks and a common room.
This multiplayer projection experience is under active development and is not being represented here as a completed day-one feature.
GO PLAY
Astrolobe OS is also home to original games. The games belong to the wider computing experience: you return to a place, not merely a launch menu.
TERMINAL ORION — A ROBOT WAR ACROSS SPACE
Terminal Orion is a movement-driven robot combat experience built around mechanical bodies, energy management, authored arenas, and fast decisions.
The release plan includes several distinct ways to play:
Online Multiplayer — Beta: Team battles, free-for-all, objective modes, and competitive playlists, with bots designed to fill available slots.

Arenas: Compact 2v2 and 3v3 spaces built for immediate fights, readable geometry, and very little room to hide.

Skirmish: Offline matches against AI opponents, so a battle doesn't depend on a live lobby.

Infected: Round-based survival against hostile machines, including runners, crawlers, ranged threats, environmental defenses, and boss encounters.

Forge: Construction tools for building combat spaces, placing modular structures, gravity lifts, teleporters, and arena elements.

Custom Games: Create your own matches and rules, with local split-screen play for up to four players among the intended launch features.

Astrolobe is targeting a substantial day-one collection of authored maps, including more than 35 multiplayer maps. The exact launch inventory and online features will be confirmed against the qualified release build.
FOUR PLAYERS. ONE SCREEN. YOUR RULES.
Local split-screen is a major part of the Terminal Orion plan. Custom Games and Infected are being built for up to four people sharing one PC, each with their own controller and view of the action. Final mode-by-mode support will be stated with the release build.
THE ORION UNIVERSE BEGINS SMALL
ORION ZERO begins with a machine smaller than a bug.
You awaken in a petri dish among tiny mechanical life-forms competing for energy. Survive, grow, and uncover the Seed. The world expands from microscopic survival to larger bodies, an industrial facility, and eventually the spacefaring conflict of Terminal Orion.
Orion Zero is part of the developing Orion story universe; its final playable release scope will be identified separately from Terminal Orion's confirmed multiplayer modes.
MORE WORLDS INSIDE ASTROLOBE
Astrolobe is being built as a home for different kinds of original games—not only one shooter.
Grapple Grid: Arcade action driven by momentum, grappling, score pressure, bosses, and multiple ways to play.

Astral Ante: Texas Hold'em poker at a space desk, away from the battlefield.

Phantom Ports: A network-signal puzzle game about connections, logic, and learning how a system behaves.

Morrow Bellweather: An unsettling narrative mystery told through records, software, and a company that knows more than it should.

The House Keeps Ten: A horror anthology conceived as another experience to discover within the Astrolobe environment.

These are first-party experiences in the Astrolobe ecosystem. The final list of games bundled with the OS purchase will be confirmed before release; a title's presence in the wider catalog does not by itself mean its current build is ready to ship.
GO WORK. GO CREATE.
The computer isn't only there to play games. Astrolobe's first-party software is designed for everyday tasks, creative work, experimentation, and project organization.
The desktop and software lineup includes core utilities such as Files, Notes, Settings, system tools, and the Astrolobe command environment. Additional first-party application integrations are being developed, including:
Astrolobe Browser: Visit real websites from the Astrolobe desktop, with a profile system designed for distinct browsing identities.

Astrolobe Canvas: A drawing studio for creating and exporting original artwork.

Astrolobe Creator Studio: A workspace for planning and organizing video content.

Astrolobe Research Studio: A research and science workbench.

Astrolobe Drift Studio: Personalized ambient and screensaver experiences.

ASTROLOBE STATION AND HUB
Astrolobe's broader work platform connects the desktop idea to real project coordination.
Station is designed to organize projects, tasks, and AI-assisted work. Hub coordinates live workers, assignments, status, and handoffs so multiple sessions can work from a shared operational picture.
These are separate capabilities within the Astrolobe ecosystem. Their exact customer-facing integration and inclusion in the OS release package remain subject to final qualification.
The idea is simple: open the computer to play, or open it because you have something to make.
MORE INFORMATION — HOW THE COMPUTER ACTUALLY WORKS
Astrolobe OS is a command-driven, receipt-backed state computer presented as a desktop and an inhabitable world.
It is not a new bootable operating system or a replacement for Windows. It is an application-level computing environment with its own model of what the computer is doing.
1. THE KERNEL OWNS THE STATE
Kernel4, written in Python, maintains the authoritative model of the Astrolobe environment: application and process identities, window ownership and focus, file structures, command execution, settings, session and power states, notifications, and supported game/application state.
Godot provides the 3D station, monitors, desktop presentation, window visuals, and input interface. It displays a representation of the kernel's state. For governed operations, drawing something on the screen is not the same as committing a change to the computer.
2. INPUT BECOMES A GOVERNED REQUEST
Mouse, keyboard, application, dialog, automation, and recovery routes are distinguished by the command architecture.
For governed mutations, a request identifies the command, operation, originating interface, relevant capability, payload, and expected authority generation. The system checks the request against its allowed operations and current state.
Supported file commands include create, copy, rename, move, delete to trash, restore, purge, open for writing, save, save as, and overwrite. Invalid, unauthorized, stale, and conflicting requests can be rejected rather than silently applied.
3. COMMITTED OPERATIONS PRODUCE RECEIPTS
Kernel4 uses a durable SQLite-backed authority and an associated content store for governed file operations.
A transaction receipt identifies the command and operation, whether it committed or was rejected, the affected file identities, and—when committed—the authority generation before and after the change. It contains a SHA-256 digest of the command and a SHA-256 digest of the receipt itself.
The generation check helps prevent an outdated command from overwriting newer state. The command identity also supports idempotency checks, so a repeated request can be recognized instead of blindly applied twice.
When a file mutation is committed, the system can produce a separate, hashed projection of the changes, linked to its receipt. The interface then displays the resulting state.
These are structured transaction records, not just lines of decorative terminal text. Hashes provide integrity checking; they should not be confused with digital signatures or a claim of tamper-proof storage.
4. EVENTS SUPPORT REPLAY
The event architecture defines ordered records with event identifiers, sequence numbers, timestamps, originating services, and causation/correlation identifiers. Different classes of records have different retention rules.
The deterministic replay implementation begins from a defined starting state and processes a supported, ordered input-event stream through the kernel. It can repeat the same stream from the same seed and compare the resulting state hashes. A matching final hash shows that the modeled system state was reproduced under those conditions.
This is state replay, not a video recording. It is not a promise that every pointer movement becomes a permanent transaction or that ar