Collectives, Teams and Membership
Teams, temporary collectives and communities of practice; time-bounded membership and working agreements. Membership must not be conflated with employment or authority.
Bundle → Layer → Finding → Questions Filled
2 bundles · 2 layers · 4 findings · 10 questions
Collectives Teams, temporary collectives and communities with their own purpose.
Collective identity
What makes a group a managed collective with a lifecycle.
Purpose and lifecycle
A collective's purpose, start, end and owner.
- What purpose does this collective have, and who owns it?
- Is the collective temporary or permanent, and when does it end?
- Does it span several legal entities or units?
Working agreement
The agreed rules of a collective, kept as its own record.
- Which working agreement applies to this collective, and in which version?
- Who agreed to it, and when was it last revised?
Membership Time-bounded membership kept apart from employment and access.
Membership record
Who belongs, for which period and on what basis.
Membership basis
Each membership with its period and basis.
- On what basis and for which period is this person a member?
- Is the person a member of other collectives at the same time?
Separation from rights
Membership that grants neither employment nor access.
- Does membership here grant any access right, and where is that right recorded?
- Is the member's employment relationship held elsewhere and unaffected by membership?
- Does any funding depend on this member list, and through which decision?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseORG
- Industry
- Cross-industry
- Tags
- EM-ORG-05W1subjectTeamCollectiveCommunityOfPracticeMembershipWorkingAgreement
What it is Filled
Teams, temporary collectives and communities of practice; time-bounded membership and working agreements. Membership must not be conflated with employment or authority.
Why it exists Filled
Teams, temporary collectives and communities of practice; time-bounded membership and working agreements. Membership must not be conflated with employment or authority.
Distinguishing features Filled
- Membership has a period and a basis and may be held in several collectives at once.
- Membership alone establishes neither employment nor authority, access rights or funding, although a separately approved decision may make rights or funding conditional on membership.
- A collective has a purpose and lifecycle, which structural units can also have.
- Collective membership is recorded independently of any structural unit mandate or hierarchical placement.
What robots and AI may and may not do Filled
Must not
- Grant a community-of-practice member access to products of other members.
- Treat membership as evidence of employment or of a reporting line.
- Allocate funding or rights from a member list without a separate decision.
- Delete past memberships when a collective is closed.
- Add people to a collective without a stated basis.
Only with a human decision
- Granting access or funding to a collective as a whole.
- Admitting members from another company into a cross-company team.
May
- List current and past members of a collective with periods and basis.
- Show a person's memberships across collectives on a given date.
- Flag access rights that appear to derive only from a membership.
Moral aspects Filled
- Membership lists reveal people's interests and affiliations and need purpose-bound disclosure.
- Rights that leak through membership can expose confidential work to people without a need to know.
Who is affected
- Members of collectives
- Owners of shared products and data
- Partner companies in cross-company teams
Owners Filled
Steward
The collective governance steward is accountable for collective definitions, membership records and working agreements.
Master systems
- A collective registry maintains collective identities and lifecycle records.
- A membership management system maintains membership basis and effective periods.
- A document management system maintains approved working agreements.
Links to other meta-models Filled
neighbor
- EM-ORG-01
- EM-ORG-03
- EM-PEO-01
- EM-PEO-02
references
- WM-ORG-003 - conceptual-candidate
- WM-ORG-006 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by a collective identifier, with each membership identified by collective, person and period.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A record names a purpose, an owner and time-bounded memberships.
- Often confused with units, mailing lists or access groups.
Capabilities and actions required Filled
- Model temporary and cross-company teams without touching employment records.
- Keep membership history after a collective ends.
Hazards and failure modes required Filled
- Access granted by mirroring membership lists into permission groups.
- Members copied between models so that lists drift apart.
Standards and interfaces required Filled
- W3C Organization Ontology, which models membership as its own record with a role and period.
Context of use required Filled
- Used for project teams, guilds, committees and communities of practice.
- Cross-company work brings members under different employers into one collective.
Sources Filled
- W3C ORG: collectives, roles, membership and posts
- GLEIF: registered identity and consolidation relationships
- Comparison of corporate governance, the actual org structure and the HR/ERP representation
- The Organization Ontology (W3C Recommendation) - Carried over from the published world model wm-org-003-team; checked live (HTTP 200) on 2026-10-09.
- FHIR R5 Resource CareTeam - Carried over from the published world model wm-org-003-team; checked live (HTTP 200) on 2026-10-09.
- FHIR R5 Resource Group - Carried over from the published world model wm-org-003-team; checked live (HTTP 200) on 2026-10-09.
Open questions
- Which collectives have their own purpose and lifecycle?
- When is TechnicalDomain a classifier, and when a managed practice?
- How are Collective and WM-ORG-003/006 combined without copying members?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-org-05/brief.json, ver-cy/world-models/card-supplements/em-org-05.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.