Availability and compatibility
Applies to: Current documentation coverage
Updated
The products in this family are at different stages of availability. Match a guide to the environment actually supplied to you. The documentation does not imply that every component is distributed together or that a browser demonstration is an installed operating system.
Documentation coverage#
| Environment | Covered here | Access |
|---|---|---|
| Rubian 4.0.2 evaluation | Startup inventory, categorized discovery, command composition, file and text operations, editing, account controls, project organization, session notes and host-tool use. | Supplied evaluation environment; host wrappers require their corresponding utilities. |
| Rubian with Forge and optional desktop/monitoring packages | Library functions, classes and value extensions; Taskman; system-monitor observations. | Supplied compatible libraries and runtime. Desktop Taskman requires Tk and a display. |
| Rubian with agent and collaboration services | Workspace lifecycle, messages, supervision, shared files and work records. | Authenticated, configured agent environment; provider access is separate. |
| Rubian with the job and daemon command families | Background and recurring-work references. | Included only in builds providing those commands. |
| Kestowv 0.5.5 enterprise pilot package | Manifest schema 1, pilotctl, services, application release operations and workload evaluations. |
Supplied Linux/JRuby pilot environment. |
| Arcturus public demonstrations | Data-center investigation, machine inspection and sample maintenance/incident workflows. | Browser access through the public preview pages. |
| Arcturus | Reliability and management software built on Rubian and Kestowv for individual machines, home clusters, fleets and data centers, with a predictive-maintenance scope across those environments. | Release-specific software and integrations; current public demonstrations cover selected workflows using sample data. |
| Core public prototype | Experimental navigation, reading, contextual messages and product previews. | Explore the prototype; interface development remains in progress. |
| Valux research | Broader operating-system research combining the programmable environment, systems foundation, interface and reliability work for personal and enterprise computing. | Integrated operating-system research in development. |
Host and runtime requirements#
Use the operating-system and runtime versions qualified for the supplied package. The pilot described here runs on an existing Linux/JRuby environment. Resource-enforcement features require the corresponding host controls and delegated permissions. Passing configuration validation on another machine does not establish that those controls are available on the deployment host.
Public browser previews require a current browser with JavaScript for interactive behavior. Core's rendered interface also depends on the browser's graphics capabilities. The documentation itself remains readable without JavaScript.
When a feature differs#
Record the package identity and the command or control that differs. Prefer the release-specific instructions supplied with an evaluation when the generic reference does not match it. Contact support before substituting another component version in a running evaluation.
A development version can appear in more than one configuration. Confirm optional commands, service setup and host requirements explicitly; do not combine capabilities from separate environments into an assumed supported deployment.
Evaluation requests#
Use the Rubian page for access interest, the Arcturus preview to explore monitoring workflows, or contact Valen Systems with a defined evaluation requirement. Include the workload, environment and outcome you need to test. An evaluation scope should name the component and version it covers.