Platform specification/architecture
This is the architecture of the system that platform members work within. The trust group is the concept which forms the foundation of what a platform actually is.
But more specifically, the group doesn't have just members, but also is a collection of resources such as documents, procedures and tools all working together in accord with a system to become an organisation, the details of which are defined in this specification.
Portals & structure
Each of the items mentioned above have a portal for the members to organise and govern these resource together, usually with the aim of achieving a shared vision. The portal acts as an entry point for the members to collaborate together on knowledge and tools so that they can engage in group decision-making and self governance together. Since the groups can be further divided within into a hierarchy of trust-groups, it follows that all the groups forming this use_casesinternal structure should work the same way and therefore also act as portals of organisation and governance.
Alignment to values
We must ensure in our system design the alignment with our values so that all Platforms based on it always evolve toward a more and more aligned direction over time. Alignment is not just statements made that "we promise to care about this and that", alignment to something is a process, it needs to actually exist as part of the system so that work is performed on a regular basis that ensures that the direction of the organisation really is maintaining alignment consistently throughout time with what it says it is. To really achieve this we must look carefully at the mechanism we're creating with our system description to see what its bottom lines really are; whether it will still be maintaining alignment to these values some time after it's been set free into the economic bottom line environment which is hostile to it. So we define here a structure which is primarily aimed at supporting this alignment, the top-level categorisation of our system is into departments.
Platform departments
We're initially basing the departments on Thomas Robertson's "seven great mechanisms" described in his 1948 book Human Ecology. This is not to say that these departments need to be fixed to number seven, or that they should be the same names or same amount of them at different scales of operation. These details can evolve through self governance just as all aspects can change. But the two key ideas here are:
- We start with departments that we know can cater for the needs of the global scale of operation
- We ensure that the principles of their operation remain consistent across all scales even if their names change or they split into more or merge into less of them in different scales of operation or specificity.