Standard Library
What HORUS gives you out of the box: message types the runtime already knows how to move, and pre-built nodes you can wire in rather than implement.
Included messages
Message types are built in and shared across all three language bindings — a message published by a Rust node is the same type a Python or C++ node subscribes to.
- Message Types — the built-in types and what each is for
- Custom Messages — when the built-in set is not enough: define a message once and use it from Rust, C++ and Python
Per-language message documentation, grouped by domain, lives in each API reference: Rust · Python · C++.
Included nodes
- Using Pre-Built Nodes — the idiomatic way to assemble an application out of ready-made components rather than writing every node
- Package Management — installing node packages and declaring them in your manifest
Related
- Core Concepts — what nodes and topics are, before what ships with them
- Multi-Language — how the shared type system works across bindings
- Recipes — whole working configurations assembled from these pieces