Ironflow PubSub Flow Diagram

Subject mapping

system.run.{id}.completed to public.{envID}.system.run.{id}.completed
events:{name} to public.{envID}.events.{name}
entity:{type}.{id}.{event} to public.{envID}.entity.{type}.{id}.{event}
topic:{name} to public.{envID}.topic.{name}

Two ways in, one mapping

system.* is published in-process by the engine, topic:{name} by the Publish RPC
events:{name} and entity events are outbox rows in the event's transaction
The subject mapping is identical either way — only the caller differs

Notifications only

A subscriber reading PUBSUB never writes to the DB — the DB stays the source of truth
Wildcard patterns share an ephemeral consumer, exact patterns use core NATS; replay (up to 1000) takes a private consumer after its snapshot
Groups keep membership in consumer_groups and consumer_members