Glossary and reading paths
| Term | Meaning in this platform |
|---|---|
| Stack | A selected set of runtime images/services and supporting assets |
| Stack manifest | Versioned image/artifact selection managed by HRCLI |
| Configuration storage | Robot/character/world content and startup configuration selected by the CLI |
| Head / body | Physical assemblies whose calibration and device mappings must match hardware |
| Character / world | Interaction identity/content and agent/world selection |
| PAU | Physiological animation representation used between animation and actuator/rendering layers |
| Viseme | Mouth-shape timing used to align animation with speech |
| ROS graph | Discovered nodes, topics, services/actions and their interfaces |
| DDS domain | Discovery partition; one part of connectivity, alongside routes/interfaces/QoS |
| QoS | Reliability, durability, history and depth compatibility for ROS communication |
| Runtime setting | Live key/value control exposed through WebUI's stable setting map |
| Saved override | Configuration persisted for later startup, separate from a live edit |
| Task | Console background operation with an ID and lifecycle result |
| Runtime revision | Version of authoritative performance state |
| Content revision | Version of active performance content, including unsaved preview payloads |
| Asset image | Distribution image used to install assets such as Unity WebGL, not necessarily run as a service |
Operator path
Read installation/acceptance, daily operation, TeleOps and relevant UI workflow. Keep troubleshooting and maintenance/rollback available before a session. Use the service guides when a UI result needs deeper explanation.
Developer/integrator path
Read architecture, source/build matrix, network map and remote recipes. Then read the target service's behavior guide, operation parameter index, request models and ROS definitions. Match the inspected source commit with the deployed version before implementing a client.
Maintainer path
Start with recorded release/configuration baseline, backup/restore, updates and branch/build matrix. Use documentation maintenance and deployment runbooks to refresh source evidence and publish changes without changing robot runtime.