Skip to content

Binding ​

One KV bucket entry mapping an endpoint to a conversation id, and nothing more than that. A message arrives, the bridge reads the entry, and either follows it or, when the entry is absent, treats the message as the start of a new conversation: routing policy runs once, the conversation is created, and the entry is written. Absence is read per endpoint and nothing else is consulted, so an endpoint whose principal already holds conversations still gets a new one.

The binding is the routing record itself rather than a layer in front of one, and it is sticky, so operator config changes affect new conversations only and a live conversation never silently changes agents. See Multi-Channel Agent Routing.

Released under the Apache License 2.0.