Rivet 1.2.0 · verification-gated Beta

Architecture

Higher-level capability describes intent and competence; RobotRuntime, typed contracts, leases, preflight, and Rivet Guard remain the command authority.

Rivet layered architecture from applications through Vocation and Continuum to RobotRuntime, safety, and drivers
Applications connect through Vocation and Continuum to the guarded RobotRuntime boundary.

Safety first

Vocation, missions, Capsules, and AI integrations never bypass RobotRuntime authority, actuator leases, preflight, or Rivet Guard. Reflex and fault domains provide bounded containment; they do not certify physical safety.

Evidence before promises

The simulator exercises discovery, capability health, command and telemetry, recorder/replay, graceful shutdown, and 18 named end-to-end scenarios. rivet check-release also checks metadata, docs, assets, examples, schemas, tests, and package builds.

Explicit integrations

GPIO, camera, serial, vision, fleet transport, process isolation, production identity, and hardware-backed safety remain opt-in integration boundaries rather than hidden runtime assumptions.