EM-ORG-04 · Subject model · W1
Organizational Unit and Mandate
A unit as a stable unit of responsibility. The org chart is a separate landscape; a team may be an independent collective.
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
- OrganizationalUnit
- UnitMandate
- UnitType
- StructuralPlacement
Deep research questions
- What makes a unit an independent object?
- How are administrative, functional and legal affiliation kept apart?
- How are OUMM and the current WM-ORG-002 reconciled without two owners of unit?
Verifiable invariants
- A parent is scoped by axis, scenario and period
- Renaming preserves the ID
- Managerial affiliation does not determine the employer
End-to-end acceptance scenario
An as-is/to-be restructuring preserves old assignments and does not produce a cycle in the chosen administrative axis.
Negative case
A product team drawn from different departments is forced under a single administrative parent.
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-002 · Organizational Unit · 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.