doover-data-management

Publish-subscribe communication uses named channels where agents publish data and subscribe to receive updates across devices, apps, and users. Define channels for your data streams, configure publishers to send events, and have workers subscribe to receive and process those events in real time.

Tag-based state management stores and retrieves structured state through the tag_values channel, making it visible across all agents and apps. Use tags to persist coordinator decisions, worker statuses, or shared configuration so any agent can read the current state without polling.

UI coordination uses two dedicated channels: ui_state to publish interface updates and ui_cmds to dispatch commands. Agents publish UI state changes to keep interfaces synchronized, while commands flow back to trigger actions, enabling dynamic interfaces driven by inter-agent data flows.

Yes. A coordinator publishes statuses to tag_values and telemetry to channels, while workers subscribe, process data, and report their status back via tags. This pattern orchestrates multiple agents, collects their statuses, and disseminates commands across the platform.

The channel-based architecture scales across devices, apps, and users reporting telemetry to a central UI. It handles scenarios where data streams, tags, and UI state must be consistently shared and synchronized across many agents with cross-app visibility.