EM-ORG-05 · Subject model · W1
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.
Partially published; research continues
Claude: complete-frozen-study-and-single-audit-remediated; Grok: complete-reconciled.
Published results
Research note, in Russian: Canonical/runtime promotion remains governed by the package allocation, identity and dependency holds.
Subject boundary and candidate types
- Team
- Collective
- CommunityOfPractice
- Membership
- WorkingAgreement
Deep research 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?
Verifiable invariants
- Membership has a period and a basis
- A member may belong to several collectives
- Rights and funding are not derived from the member list
End-to-end acceptance scenario
Assemble a temporary cross-company team and a permanent community; verify the independence of membership, employment relationships and access.
Negative case
A community-of-practice member gets access to all products of its members.
Approaches to compare
- 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
Candidates in the live catalogue
- WM-ORG-003 · Team · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-ORG-006 · Membership · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.