You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RELAY spec v1.9 (release) adds §13.7, a normative cross-language library-architecture convention so the same protocol in Go/Rust/C++ is structurally common (same module taxonomy, identical module names, idiomatic packaging aside). cpp-RCP currently targets spec 1.0 and passes relay conform.
§13.7 alignment for cpp-RCP
Align module organisation to the §13.7 registry (the RCP control-plane set: authz, e2e, federation, firmware, deadline, faultinject, iso21434, codegen, capi, bridges, …) as go-RCP/rust-RCP do.
§13.7 essentials: the RELAY adapter module is named adapt (entry point adapt(<iface>) → Node); the in-process virtual transport is virtual (not virtual_bus); mock is mandatory; the standard module-name registry (socketcan, safety, dbc, isotp, j1939, obdii, uds, recorder, codegen, the RCP control-plane set, bridges, capi) uses identical names across languages.
Spec-version uplift
Uplift the targeted spec version from 1.0 to 1.9 (SpecVersion/version output) once aligned, so relay versions shows the fleet converged on the current spec.
No changes are requested to RELAY. Verify with relay conform --strict <binary> after.
Done in PR #27 (v1.1.0): bumped kRelaySpecVersion 1.0→1.10 and added the relay::INode cross-language alias (§13.7); core/adapt/mock taxonomy already compliant.
Activity
feat: uplift to RELAY spec v1.10 — crossbar send sink + continuous co…
SoundMatt commentedon Jun 19, 2026
Done in PR #27 (v1.1.0): bumped kRelaySpecVersion 1.0→1.10 and added the relay::INode cross-language alias (§13.7); core/adapt/mock taxonomy already compliant.