System overview

The System section presents the components that an administrator can inspect or configure through the web interface. It does not catalogue every internal detail: it explains the purpose of each page, the actions it permits, and the checks required after a change.

The six areas

AreaWhat it governsTypical action
ModelsThe LLM contracts, embedding model, and vision model that are actually configured.Inspect a functional tier or change an editable configuration.
ServicesHealth, desired state, and placement of supervised components.Restart a known service and verify that it becomes healthy again.
LRE (Long Run Engine)Long-running, persistent workloads divided into accountable units.Monitor a workload's progress, events, limits, and artifacts.
SafetyDeterministic signatures that decide whether a command is allowed, requires approval, or is forbidden.Understand why a particular action was admitted or stopped.
UsersIdentity, role, autonomy, paired channels, and preferences.Create a guest and grant only the autonomy they need.
DevicesPaired computers on which remote executors can run.Pair, inspect, or revoke a device.

Inspect before acting

The administration pages keep several easily confused conditions separate. A process may be running without being healthy; a component may be healthy while one of its functions remains deliberately inactive; a capability may be installed but disabled. Likewise, pairing a channel or device does not automatically grant every action. Identity, autonomy, policy, and executor authority remain separate controls.

A dependable change always follows the same sequence: read the effective state, choose an action from the closed catalog, wait for the system to converge, then check health and desired state again. The interface does not expose a generic shell and does not turn arbitrary values into system commands.

Administrative access. These pages may contain operational configuration and user data. Open them only through a trusted administrator session. The public documentation contains neither secrets nor personal values.

Finding your way around the web interface

The real Metnos Services screen, showing System navigation and component cards in an Italian-language instance.
The Services page provides an orientation point between System navigation and the operational state of each component.
  1. System navigation. Direct links to the six areas covered in this section.
  2. Overview. Summarises the number of installed and running services and shows the refresh interval.
  3. Component card. Separates process state, application health, and desired state.
  4. Feature and process kept separate. The LRE worker can be healthy while the feature remains deliberately disabled.
  5. Bounded actions. The interface displays only actions admitted for that service and its current state.

Captured from the real web interface of an Italian-language instance. Identifying values, where present in this section, have been replaced with anonymous examples.