Arcturus connects machine observations to investigation and maintenance work. Rubian supplies the programmable working environment; Kestowv supplies the systems execution and coordination foundation.
Startup inventory and retained project records give an operator a place to begin. Rubian commands inspect the environment; Kestowv pilot interfaces cover service operation and recovery. Arcturus brings that work into a machine-reliability workflow.
Evaluate performance, recovery and operator control.
Performance checks must retain correct output. Recovery checks must establish that the operator can restore and use the service. We assess those requirements together.
Rubian’s manuals connect persistent working environments, programmable controls and machine execution.
Persistent user and agent spaces
Identities, files, projects and running work stay associated with their user space. The agent VMOS provides a machine-facing place for agents to work alongside people: separate contexts on shared computing resources.
Readable commands let people and agents direct work. Background jobs preserve an inspectable lifecycle; Forge makes compatible Ruby libraries available from the environment.
Accounts, groups and file permissions define access. SSH/SCP, TCP/UDP checks and socket observations connect the environment to the systems around it. Follow the documented command and permission contracts.
The Kestowv pilot documents service-operation interfaces and repeatable workload evaluation. Correctness, resource use and useful output belong in the same comparison.
The manuals document commands, returned data and operating limits. Research pages describe methods and open questions; deployment records identify contributions used in other software.
Start with an operating problem
Find the capability and commands associated with the problem you’re trying to solve, rather than reading an entire architecture introduction first.