Messages
Integration guide to the seven HIBW message types — purpose, cadence, fields, worked examples, and the validate/route steps for each.
The CATL command-and-tasking layer has 7 message types. Each is a header + typed body; together they cover a node's whole lifecycle — announce, status, task, feedback, result, world-model updates, and chat. Pick a type below for its fields, worked examples, and copy-paste integration steps.
Message types
| Message | Sent | Cadence | Delivery | Examples |
|---|---|---|---|---|
| Node Description | node → controller (and peers) | Once on join, and whenever capabilities change. | Broadcast | 2 |
| Node Status | node → controller | Periodic (seconds) and on significant state change. | Broadcast | 3 |
| Task Admin | controller → node (addressed command) | On demand, whenever tasking changes. | Addressed | 7 |
| Task Feedback | node → controller | Periodic while a task is active, and on state change. | Addressed | 2 |
| Task Result | node → controller | Once, when a task reaches a terminal state. | Addressed | 1 |
| Dynamic Update | any → world model (broadcast) | Whenever the world model changes — often high-volume. | Broadcast | 7 |
| Chat | any ↔ any | On demand. | Broadcast | 1 |
Node Description
A node introduces itself and declares its capabilities.
Node Status
Periodic heartbeat: where the node is and what it is doing.
Task Admin
A controller assigns, modifies, or stops a task.
Task Feedback
A node reports progress on a task it is executing.
Task Result
A node reports the final outcome of a task.
Dynamic Update
Read or write a value in the shared world model.
Chat
Free-text and structured operator communication.