Read state and follow changes
Load a scoped snapshot, preserve newer evidence and treat reconnect as a fresh observation boundary.
Source 0.1.0 Private source package
Start with a decoded snapshot
currentState.getLayoutSnapshot takes accountId and layoutId as separate arguments. Its optional request controls accept an AbortSignal and timeoutMs. Preserve the response scope and let the SDK decoder reject malformed data.
Join snapshots and live evidence deliberately
For an approved realtime integration, establish observation before loading the snapshot and buffer changes while the read is pending. Apply only decoded, correctly scoped evidence and retain newer revisions over older snapshot values.
The source Product realtime primitive owns one connection. The application owns generation, buffering, projection and recovery. Do not infer that the direct-integration client has a realtime property or substitute undocumented socket messages.
Recover observation without replaying input
After transport or authority loss, withdraw operating input and dispose of the retired observation. Recheck scope and authority before reopening. Reconnecting must not reacquire driving control, restore speed demand or repeat a movement command.