Here we describe the platform spaces provisioned by meet.coop, incuding the specific privileges, obligations, protocols and sanctions of platform spaces (POPS).
Platform spaces are one element of the **stack of spaces** provisioned by meet.coop: see Spaces
Platform spaces are digitally mediated spaces where participants interact with FLOSS tools running on distributed servers across the internet, via their individual devices and web browsers. xxx. FLOSS - free-libre open-source software
Seen as commons, platform spaces are commons of **running code** (distinct from the commons *of code* that constitute the realm of FLOSS. Thus they call for protocols that differ from those of FLOSS. They also call for protocols that differ in some respects from those for media spaces (commons of asynchronous media) and venue spaces (commons of capability, live mutual engagement and relationship).
The platform spaces of meet.coop constitute the toolstack(s) - public and back-end - that are the operational core of the commons that meet.coop provides for members. See Toolstack.
# Privileges, obligations, protocols and sanctions in platform spaces > To be expanded xxx * Provisioning/curating platform spaces - sysadmin activity in the Tech circle xxx * Stewarding platform spaces - overview of platforms, in the Board of stewards and All-hands xxx * Mobilising media spaces - dialogues and exchanges in the forum, handbook, website, and in [BBBÂ ](https://handbook.meet.coop/doc/big-blue-button-9yrmPlQrts)/ [Greenlight recordings](https://handbook.meet.coop/doc/greenlight-WzD0xgrD1o) xxx