Rubian capabilities
Applies to: Provisioned Rubian 4.0.2 environments; optional features vary by package
Updated
Rubian brings discovery, file operations, programmable commands, libraries and agent work into a common operating environment. It prepares an inventory when the interactive environment starts, presents files in recognizable groups, and lets an operation return data that another operation can use. A session can grow from an inspection at the prompt into a saved project, background task or recurring procedure.
This manual covers the interfaces available in provisioned Rubian 4.0.2 environments. Host tools, optional libraries and agent services depend on the supplied package. The compatibility guide distinguishes those requirements from the integrated Valux and Arcturus OS projects.
Discover and return to work#
The interactive startup inventories the available system locations, Rubian environment, installed commands and the user's home files. Categorized views make that inventory usable without repeatedly navigating from the root of a directory tree. The prompt identifies the current account and working location. Command history, named projects and session notes provide different ways to return to earlier work.
Read Startup, discovery and recall for the scan's scope, the available views and when to refresh them. Projects and session notes explains the working structure for source, notes, runnable snippets and temporary files.
Choose a capability#
| Task | Rubian interface | Guide |
|---|---|---|
| Find your bearings and discover available files | Startup inventory, categorized file and directory views, current-location display | Startup and discovery |
| Inspect, copy and change files | Directory navigation, file reads, copying, writing and host-file operations | Files and paths |
| Search logs or turn text into a useful result | Content matching, line and field selection, sorting, deduplication and counting | Search and process text |
| Write a note, edit a file or package a directory | Line editor, quick writing and host archive utilities | Editing and archives |
| Control access | Session identity, passwords, account administration and file permissions | Accounts and permissions |
| Keep using the prompt while work runs | Named Ruby jobs, state, results, timeouts and cancellation | Background jobs |
| Repeat an operation | Recurring definitions, last results and restoration controls | Recurring work |
| Inspect resource use or stop a process | Taskman, process lists and terminal controls | Taskman |
| Use a compatible Ruby library | Forge functions, classes and value extensions | Libraries with Forge |
| Connect to another machine or transfer files | SSH, SCP, rsync, HTTP tools and connection checks | Networking and file transfer |
| Operate configured agent workspaces | Availability, messages, startup, restart and supervision | Agent workspaces |
| Coordinate work between workspaces | Shared files, task records, a shared board and messages | Shared work and messaging |
| Inspect the environment | System status, memory, storage observations and logs | System and storage inspection |
| Reuse host tools from a session | Host commands, aliases and repeated observations | Shell tools and customization |
Compose operations from values#
Rubian commands use Ruby arguments and return values. A directory listing can feed a selection; a search can produce structured matches; a job can retain a result for later inspection. The command-language guide explains this distinction between terminal display and the value available to a program.
For example, a search can identify a group of messages and retain their content for a report. That operation can then become a named method, a project file or a background job. Each step uses the same language, so the procedure can become more repeatable as the task develops.
Work within the environment's scope#
Rubian-managed files, host files, Ruby jobs, host processes and agent workspaces have different operations and lifetimes. The references identify which resource each command affects. Familiar names such as find, nano and mount also have Rubian-specific behavior; consult their guide before transferring a procedure from another shell.
Valux and Arcturus apply this operating approach to consumer and enterprise OS products. Their documentation describes the integrated product direction separately from the component interfaces you can evaluate today.