# Independent review request: EM-ORG-05 Collectives, Teams and Membership

Review this Enterprise boundary independently using public organization, team, membership and access-control practice where useful. Separate standards evidence from design inference. Do not invent a Vercy identifier.

WM-ORG-003 Team and WM-ORG-006 Membership are existing non-canonical drafts. WM-ORG-003 contains team-scoped membership assignments; WM-ORG-006 owns governed belonging. WM-ORG-006 lacks independent external review.

Proposed decision: **PROFILE WM-ORG-003 and REUSE WM-ORG-006**, no new ID. Rename the nested team record to TeamAssignment: staffing/participation with role, period, allocation and employer/on-behalf-of references. WM-ORG-006 Membership has a scheme, admission decision/basis, standing, validity, terms, role and evidence; it may outlive an assignment.

An inter-company collaboration has optional containment, one or more sponsors, zero or more managing organizations and exactly one record authority. A CommunityOfPractice is a standing collaboration whose participants hold WM-ORG-006 memberships. Temporary project/delivery teams may use assignments without membership.

WorkingAgreement is an owned charter component when collective-specific and a referenced instrument when reusable or multi-party. TechnicalDomain is a classifier; governance belongs to the community that stewards it.

Test: a community member must not gain access to products of other members. Acceptance: a temporary two-company team and a permanent community keep assignment, membership, employment and access independently dated.

Return at most 1000 words with: Verdict per type; assignment/membership mastership; inter-company cardinalities; community profile; working-agreement/domain boundary; access prohibitions; scenario results; migration relations; publication blockers.