Once Admo has a set of normative expectations to waive associated with it, an End User License Agreement window for their software needs to be made to successfully facilitate the communication transaction that needs to take place to fulfil the requirements of the theory. I outline here two possibilities for the design of the agreement panel, that would be run on installation or re-request for consent. One is a two-window design, and the other multiple windows depending on how many modules are used (that is, how many normative expectations need to be waived). It could be that these are organised into some sort of hierarchy, much like their origins in section 3.2.3, or kept separate, but determining this and which sort of model is best suited for the audience is best left to further feasibility studies and trials.
The major problem with designing agreements is the need to balance the requirement for informed consent with an annoyance factor. A user may get annoyed if they are forced to do a lot of relatively minor tasks before a piece of software is installed, yet they would likely recognise the importance of gaining consent and tolerate a certain amount of this. The more ideal the consent process, the likely more annoying, which is why I propose two slightly different models, one of which is not quite as involved as the other. Ultimately, though, I suspect that the overwhelming desire to install the software would override the annoyance of the EULA windows, especially if there were obvious benefits to the requirement of such windows.