Skip to content
Librux Runtime Kernel for Robotics development
Librux Runtime Kernel for Robotics development

    Concepts Overview

    Use this section to understand the Librux robot model before reading operator procedures, SDK tutorials, or protocol references.

    The Concepts section is ordered from philosophy to model to runtime operation.

    philosophy -> robot model -> subsystem roles -> binding -> lifecycle -> communication -> managed runtime -> host boundary

    The vocabulary order is intentional.

    • robot composition: platform, application, deployment
    • subsystem roles: gateway, component, compound, app
    • spec families: message, API contract, component, capability
    • runtime flow: declaration, binding, lifecycle, communication, launch, resource admission, route

    Concept Map

    Area Question it answers Start here
    Philosophy Why does Librux define a robot before it defines processes? Design Philosophy
    Robot composition How are platform, application, and deployment separated? Robot, Application, And Deployment
    Subsystems and interfaces What are gateway, component, compound, and app subsystems? Subsystems, Roles, And Interfaces
    Binding How does deployment choose concrete providers without hardcoding topology into code? Subsystem Binding Model
    Lifecycle How is a subsystem state different from an OS process state? Subsystem Lifecycle
    Communication When should Event, Control, Procedure, Operation, or WebSocket be used? Communication Surfaces
    Managed packages How do reusable packages, installation, instances, and package frontends work? Managed Packages and Runtime Instances
    Resource authority How does Librux admit CPU, network, CAN, serial, device, and frontend resources? Resource Authority
    Federation How do multiple hosts participate without per-subsystem cross-host sockets? Federation and Host Control
    Timing How is cross-host timing state represented and accepted? Federation Time Model
    Differentiation What makes Librux different from node graphs, message buses, direct sockets, launchers, and single-host IPC? Differentiators

    If you are new to Librux, read the pages in this order.

    1. Design Philosophy
    2. Robot, Application, And Deployment
    3. Subsystems, Roles, And Interfaces
    4. Subsystem Binding Model
    5. Subsystem Lifecycle
    6. Communication Surfaces
    7. Managed Packages and Runtime Instances
    8. Resource Authority
    9. Federation and Host Control
    10. Federation Time Model
    11. Differentiators

    Implementation-specific pages are kept in Reference, including runtime layout, package layout, protocol details, and spec lookup.

    Use Operate for host operation and Develop for SDK and tutorial workflows.