Clients

In Naylence, clients are not second-class citizens.

A client is simply code running on a node that initiates interactions with other agents. That same client node can also:

• listen for incoming envelopes,
• handle streaming (sending/receiving incremental responses),
• and host local agents or handlers when that makes sense.

This is why a browser client still “counts” as part of the fabric: it runs on a node, participates in routing, and can both send and receive messages.

The difference between “client” and “agent” is usually role, not capability:

• client role: start a request, drive a workflow, present results.
• agent role: provide an addressable capability (tool/service/worker) that others call.

In many systems the same process can do both.