Topology mirrors real NimBus conventions: one Service Bus topic per endpoint (topic name = endpoint id),
event-type forward subscriptions route copies to each subscriber's endpoint topic, and
[SessionKey]-ordered sessions block on failure — successors park on the endpoint's
Deferred subscription. Every handler outcome flows through the central Resolver topic into
Cosmos DB (ResolutionStatus: Pending · Deferred · Failed · DeadLettered · Completed · Skipped), where the
WebApp and the Ops Triage AI agent act on blocked sessions via the Manager topic.
The AI agents are illustrative consumers — they are not part of the NimBus codebase.