What can I say... more good news.
As I write this, believe I have just stabilised the second of the three access levels (Connection, Active Affiliation, and Participant) available in Clique Space. These access levels have relevance to every device that uses a Clique Space, but their use is most obvious to the administrator Client Device because this device, being a device that a Clique Space administrator would use, needs to transfer through each of these levels manually as required by the administrator.
Generally, for devices of any medium...
Connection access allows a device to be seen by a Clique Space, but does not allow other devices (other than possibly those devices that have obtained a Clique Space Participant using the same account) to observe the given device. As I've said before, this is used as a very convenient way to facilitate remote authentication amongst perhaps a few other things that I can't recall right now.
Active Affiliation access allows a device to be seen within a Clique Space, but that access does not give the given device the ability to observe and engage others from within the given Clique Space. Because a device can collaborate with other devices through its device specific way regardless of whether it is connected to a Clique Space or not, it is envisaged that most devices would need only an Active Affiliation to collaborate with any other device for which they are able to engage. Besides that, giving participant access to a device that has no ability to view, and therefore engage other devices through, a Clique Space is redundant, and could subject the Clique Space users to undesirable consequences.
Clique Space Participant access is granted to a Client Device if the associated device possesses a view of the Clique Space. Such devices are usually equipped with a view of the Clique Space to which they have connected, and can actively interact with other devices using the Clique Space system. This interaction may include with those devices that make up the Clique Space.
Alternatively, the operator of a device obtains a Participant for a Client Device whenever the associated device collaborates with another device over some medium. While a device possessing only Active Affiliation access cannot engage another device from within the Clique Space system to which it is connected, that device may be able to engage similar devices in accordance with its own media protocol. If these other devices are likewise connected to the same Clique Space, the Clique Space will model this interaction as a Clique between the two individuals known to the Clique Space or federated Clique Spaces concerned as the devices' operators. Should one of the given devices not be connected to a Clique Space, the collaboration may still be modelled as a Clique between two Participants; one of the Participants is shown as anonymous.
This whole idea is so powerful that it's applicability may far outstrip my ability to describe it.
It is without any coincidence whatsoever that these access types are used to model collaborations going on in any medium by any number of individuals. This access "backbone" is part of the technology that has been developed around the core inspirational concept; the unaltered inspiration I had in 2004 whilst jogging between Bellambi and Bulli. The backbone is made up of three vertebrae (four if you want to be more technical and include the Media Profile) which I have envisaged are central to the Clique Space implementation.