TL;DR
Provide a mechanism post platform logistics requests from circuits similar to how requester chests operate.What?
In the hub signal UI, have a means to user define some signal IDs. For UI implementation simplicity, it may be easier to have the number fixed (5 for eg). Each of these signal ID would be a signal that is accepted a a logistics request setter.For example, support in the UI you defined a signal ID of Biter Egg item, then when a biter egg signal was sent to the hub, the item + amount would become an active logistics request. A value of zero of course cancels the request.
Why?
When dealing with items that can spoil or items that are consumed as delivered, you may not want those items to be continually refilled while in orbit. In the case of biter eggs, you probably don't want 10000 hatching biter eggs on your platform and thus would be forced to dump them overboard when they arrive due to a fixed logistics requests that rocket silo will attempt to satisfy. Better to not request them at all and leave them in their spawners on the ground.Perhaps a simpler option maybe be an additional hub UI checkbox label set logistics request that would change how signals sent to platform are exposed:
If the signal corresponds to an item - it is handled as a logistics request, otherwise it is a platform signal. That could have been default behaviour, however existing platform may already be using item signal and such a change would break existing builds. A checkbox would serve to explicitly enable a new behaviour.