How Rubian and Kestowv got here.

Researchers, engineers, journalists, and partners

Project Valux brings the Rubian CLI and Kestowv systems model into the operating-system work still being built.

Rubian began as a real operating environment.

The environment developed durable users, workspaces, commands, tools, services, and a direct shell over years of work.

Kestowv expanded the systems model.

Kestowv supplies the systems layer and mathematical foundation used by the current system.

Every result belongs to a named system.

Published research identifies the Rubian or Kestowv release, measured outcome, correctness status, and limitation.

Results with the test beside them.Same work. Same answer. Then compare.

Project Valux is the next stage of the work.

The operating-system project is applying the strongest research concepts closer to the machine and testing them with new matched benchmarks.

Rubian at the surface. Kestowv underneath.Same work. Same answer. Then compare.

Give the research a job to answer for.

A service that won't settle after a restart, a repeated command sequence or a workload that crowds out its neighbors can expose a useful systems question. The question gets stronger when we can name the expected result and repeat the conditions.

Rubian and Kestowv let us explore that work through an operating environment and a systems layer. Project Valux is the wider effort. Each test should say which part was used, what was measured and what the result doesn't establish.

Discuss a workload evaluation Support the research

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.