Subscription

In one line: a view published to remote consumers, streaming its deltas over a transport.

When the consumer of a view is remote — a connected client, another process — a subscription publishes the view and pushes its Added/Removed/Modified deltas out as it refreshes, with per-subscription priority and overload throttling. It's the same view + delta machinery from views, wired to a transport, so a client can mirror "the units near my camera" without re-querying.

You register a PublishedView (managed by a PublishedViewRegistry). Reach for it when you're building a server, not a single-process simulation.

How it relates

• View — a subscription is a view published outward.
• Query — the underlying question the view answers.
• System — subscription output is driven at tick end, alongside the tick lifecycle.

In the API

• PublishedView — a view published to subscribers.
• PublishedViewRegistry — the registry that manages published views.

Learn & use

• Narrative: Guide ch.4 §4 — subscriptions
• Feature detail: subscriptions · published views · incremental sync