Skip to content

Understand Valence#

This section covers the catalog, channel classes, ground truth, safety, capabilities, the existing ecosystem and security. Wire numbers live in the generated registry reference.

Page Covers
How it works Catalog, channel, shadow, intent
Anatomy of a frame Frame header and the two payload encodings
Capabilities and custom hardware Mandatory and optional hub and client features
What it replaces What Valence takes over and what it leaves alone
Ecosystem and compatibility How Valence fits alongside existing firmwares
Security model and the audit What is defended, what is not, and what the fuzzing found
For everyone What Valence means for a machine owner

Core principles#

Self-description. The hub publishes a catalog: every channel, type, unit, limit and access level it has. A client reads it and builds its interface from it.

Hub authority. A client sends intent. The hub applies what it can and echoes what it applied. A client's shadow updates from the hub, never from its own request.

Deadman and ESTOP. A session that owns a motion source and goes silent trips its deadman, and the hub releases the source. ESTOP is role-exempt, jumps every queue and latches until it is explicitly cleared.