Contact: Event Stream

[digitalextremist]

Like Launchers wait to react to contact via Mountpoint instances, reacting directly to other Artillery installations is natural next, via Contact especially in connection with time sequencing via Triggers #12. Different from Artillery::Shell::Request which conforms to a more sequential use, such as via a Vue.js interface, with steps, fragments of data, etc. Artillery::Shell::Contact would be full-form data to be processed or reacted to intelligently.

Artillery::Shell::Contact would have everything necessary in it to perform an action without intervention, versus an Artillery::Shell::Request which is more of member of a series of interactions with the Participant present.

Artillery::Shell::Contact would be more like their activity away from direct experience. Like an Event in their stream of consciousness, or that of a group, but possibly also something generated by one of their devices, such as a car registering that its charging cycle is complete, or it is nearly out of gas, or a banking account crossed a set threshold.

These would be predisposed to asynchronous behaviors, like triggers #12, and essentially are like triggers in the sense that they don't come from requests, but they aren't at preset times. They occur in reality on its own, without any session or intention.