System configuration and topology — structural connections

Client/server component placement and RouteMesh/ClientServer connections (Store/evidence in the resource table)

System configuration and topology — structural connections Client/server component placement and RouteMesh/ClientServer connections (Store/evidence in the resource table) Courier Client A · Architecture component Courier Client A Courier Client B · Architecture component Courier Client B CourierSession · Servers CourierSession CourierActorNode 1 · Servers CourierActorNode 1 CourierActorNode 2 · Servers CourierActorNode 2 Dispatch · Servers Dispatch Tracking · Servers Tracking Customer Client · Architecture component Customer Client CustomerGateway · Servers CustomerGateway STREAM STREAM HTTP STREAM RouteMesh RouteMesh ClientServer ClientServer ClientServer RouteMesh Servers

Channel names (verbatim)

  • • Solid RouteMesh edges are for object routing — on the courier side `deliverydispatch.courier` (D/CS → CourierActorNode 1/2), on the customer side `deliverydispatch.customer` (Tracking → CustomerGateway).
  • • Dashed ClientServer edges are independent, directed channels — `deliverydispatch.dispatch` (Dispatch → CourierActorNode 1/2), `deliverydispatch.tracking` (Dispatch → Tracking). Dispatch connects to each CourierActorNode over two channels: courier RouteMesh and dispatch ClientServer.
  • • The source connections are undirected `---` structural links (arrowheads are a rendering constraint, not a claim of direction).

Roles and boundaries

  • • Dispatch provides the HTTP edge and the dispatch worker. CourierSession/CustomerGateway receive STREAMs and bind the current session to each Actor. CourierActorNode 1/2 are eligible object servers offering the same Actor type and Entry Spot (green). Tracking records status events and sends them to the Customer Actor.
  • • The number of servers and the actor owner are not fixed by Application configuration. The Location Store provides current authority and the Framework selects the target.