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.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseORG
- Industry
- Cross-industry
- Tags
- EM-ORG-04W1subjectOrganizationalUnitUnitMandateUnitTypeStructuralPlacement
What it is Filled
A unit as a stable unit of responsibility. The org chart is a separate landscape; a team may be an independent collective.
Why it exists Filled
A unit as a stable unit of responsibility. The org chart is a separate landscape; a team may be an independent collective.
Distinguishing features Derived, awaiting review
- A parent is scoped by axis, scenario and period
- Renaming preserves the ID
- Managerial affiliation does not determine the employer
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: A product team drawn from different departments is forced under a single administrative parent.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
Корпоративный секретарь / владелец организационной модели
Master systems
- Корпоративный реестр
- HRIS
- реестры юрлиц
Links to other meta-models Filled
neighbor
- EM-ORG-01
- EM-ORG-06
- EM-PEO-02
references
- WM-ORG-002 - conceptual-candidate
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Derived, awaiting review
- OrganizationalUnit
- UnitMandate
- UnitType
- StructuralPlacement
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
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
Open 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?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-org-04/brief.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.