Rubian

A command line built for people and agents.

People, developers, and enterprise operators

Rubian is a programmable operating environment for people and agents. It brings commands, persistent workspaces, libraries, services and system inspection into one place. Kestowv supplies the execution and coordination foundation beneath it.

Use the environment to keep investigations, reusable commands and service work together. Rubian and Kestowv also form the foundation for Arcturus reliability and management, from an individual machine to the connected operation around it.

Troy Mallory invented Rubian and Kestowv and leads their technical direction.

Support the research See all tools See what’s first

Rubian operating system mark — Rubian A Modern Operating System

Commands and workspaces for people and agents.

Persistent identities, workspaces and system tools.

Persistent users with their own workspaces and access.

Rubian gives people direct control and gives agents persistent identities, private homes, their own work, and services that remain available after a tab closes.

RUBIAN / SYSTEM

System status recorded system output

$ status

Rubian 4.0.2 | Kestowv 0.5.4 | Bridge: connected | User: agent user | Mode: managed service | agent status responsive

1 / 6

Recorded output from Rubian 4.0.2 and Kestowv 0.5.4.

Show run details

System: Rubian and Kestowv
Version: Rubian 4.0.2 / Kestowv 0.5.4
Command: status
Result: Connected and responsive
Notes: Internal identifiers omitted

Inside the supplied operating environment.

People and agents use the same system.

People keep direct control. Agents receive durable identities, workspaces, tools, and supervised services inside the system.

Kestowv gives the work a systems model.

Kestowv supplies the mathematical foundation behind the current system. Project Valux brings that research into a broader operating-system project.

Performance includes responsiveness.

Rubian research reports interactive latency beside throughput, correctness, energy, and the limits of each test.

Reported component measurements.

69.669x

faster directory listing

Median result for one Rubian operation against the named comparison workflow.

5,082

bridge requests per second

One bridge test completed every accepted request with zero correctness errors.

1.51M

work units per second

One equal-work Kestowv control completed every accepted work unit with matching checksums.

Rubian supplies the operating environment beneath Arcturus.

Rubian gives people and agents a programmable operating environment. Core provides the human- and agent-facing interface above it. William and Troy teamed up to connect those two sides, with Kestowv handling the systems foundation beneath the work.

Rubian’s agent VMOS includes separate user spaces, identities and communication channels. Like a mainframe, the model gives different users their own place to work on shared infrastructure. A person can inspect agent status with vmos_status and review activity with watch_vmos. These commands need a running kernel bridge; the website itself isn’t that environment.

Arcturus applies Rubian and Kestowv to machine reliability, with compute facilities as the primary focus. Valux is the broader operating-system project. Valen is the AI within the system.

Explore the human-and-agent interface Read the Project Valux direction

Rubian is the command line.

Rubian gives people a readable CLI and gives agents a durable place to work. The command surface continues beyond one browser tab, chat, or IDE session.

Rubian at the surface. Kestowv underneath.Give every agent an identity and boundary.

Project Valux is the operating-system project.

Project Valux is the broader operating-system project built around Rubian and Kestowv. The hosted environment and a standalone system have separate requirements for boot, runtime execution and hardware support.

Rubian at the surface. Kestowv underneath.See where Rubian runs today.

Kestowv supplies the math.

Kestowv is the systems layer and mathematical foundation behind the current system.

How Rubian and Kestowv got here.Results with the test beside them.

Test it against real work.

Rubian can be evaluated for responsiveness, throughput, energy, recovery, and other defined operating requirements.

Test Rubian on your workload.More useful work from every machine.

Questions about Rubian.

Is Project Valux a browser-based system?

No. Project Valux is an operating-system project. The website shows recorded Rubian and Kestowv output; it’s not the operating system itself.

Can people use Rubian directly?

Yes. Rubian is the CLI designed for people and agents. People keep direct control while agents receive durable users, workspaces, tools, and services.

How do Rubian, Project Valux, and Kestowv relate?

Rubian is the CLI. Project Valux is the temporary codename for the operating-system project. Kestowv is the systems layer and mathematical foundation behind the current system.

Do current Rubian results establish completed Project Valux performance?

No. Existing results belong to the named Rubian and Kestowv configurations. Project Valux claims require new matched runs for the exact path being tested.

Keep the useful part of the command.

Rubian lets you reuse supported command results in later operations and turn a sequence of checks into a repeatable method.

Commands are Ruby methods. Your own methods can extend the environment. A repeated investigation can become a small tool that fits the way your team works.

Inspect the system in the command environment.
Work with returned data where the command supports it.
Combine the useful checks into a repeatable method.

See beyond the host process.

Taskman puts host processes, Kestowv runtime state, messaging and Forge activity within reach of the same investigation. That matters when the process name isn't enough to explain what the work is waiting on.

Follow the signal into the relevant runtime view. Keep the workspace and the tools beside the work. Rubian is the command-line environment in this relationship; Kestowv supplies the systems layer beneath it.

Put your own workload into the conversation.

A roadmap can't tell us where your operators lose time. A repeated task, a service that needs careful recovery or a workload with a clear limit gives us something useful to evaluate.

Rubian and Kestowv are the working foundation for Arcturus and the broader operating-system research. Early-access discussions begin with what you need to run, the environment it runs in and the result that would make the evaluation worthwhile.

Discuss Rubian early access Read the command-environment documentation

Working through a hardware or runtime decision? Explore compute evaluations

Rubian/Kestowv Documentation

Startup and discovery, file and project organization, Forge libraries, Taskman, agent work and Kestowv pilot operations.