# On multi-agent services and design guidelines **URL:** \ **Category:** Development & Maintenance\ **Created:** [September 24, 2020, 5:56pm UTC](https://forum.opencyphal.org/t/on-multi-agent-services-and-design-guidelines/947 "2020-09-24T17:56:36Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\ **Post date:** [July 23, 2021, 9:52am UTC](https://forum.opencyphal.org/t/on-multi-agent-services-and-design-guidelines/947/10 "2021-07-23T09:52:15Z")
Necroposting but it is important for maintaining a less fragmented picture here. This thread is tightly related to the following: > [@Choosing Message and Service IDs](https://forum.opencyphal.org/t/choosing-message-and-service-ids/889/3): > > Thanks for the explanation. I’m still a bit unclear though. Are you saying that the subject IDs will need to be assigned dynamically? If so, is there a well known fixed subject ID that can be used to assign system specific subject IDs? Almost like how TCP port 80 is used to distribute out random unused ports to actually serve data during a transfer. It would be really helpful to have an example of recommended device provisioning in a system. For example, if the device has no UI, it must have a … --- _[View the full topic](https://forum.opencyphal.org/t/on-multi-agent-services-and-design-guidelines/947)._