← Catalogue
World Models · legacy example

Organizational Unit

This meta-model describes the internal anatomy of an organization: units, their hierarchy and reporting lines, the mandates and established positions inside them, and how the structure changes over time. It is its own model because internal structure evolves on the organization's own cadence, is governed by the parent organization rather than by registrars, and is consumed by employment, charters and procurement without needing full organizational identity semantics.

AI YAMLAGENTS.mdSource
IDworld.o2-organizational-unit
Version history0.2.0-legacy
CategoryReference example
IndustryCross-industry
Domainorganizations
Tagsorganizational, unit
Data structure

Bundles and layers

Bundle

structure

What units exist and how they nest

Layers

unitDirectory`: units, their kinds and names · `hierarchy`: containment and reporting lines, including dotted lines

Bundle

mandate

What each unit is for and who sits in it

Layers

remit`: delegated mandate and scope of each unit · `establishedPositions`: posts, grades and the headcount plan

Bundle

evolution

How the structure changes

Layers

reorganization`: acts that create, merge, move or disband units · `staffingSnapshot`: recorded headcounts over time

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Service layers

How this specification operates

Dimension & namespace

  • REFERENCE `world.organization` (O1): the parent organization whose structure this is.
  • REFERENCE `world.charter` (O4): unit mandates trace to powers delegated under the charter.
  • REFERENCE `world.employment` (O3): role assignments there fill established positions here.
  • REFERENCE `world.stewardship` (S1) and `world.accessGrant` (S2): ownership and access grants over structure data.
  • MIX-IN `world.auditTrail` (S4): audit facets on reorganization and mandate events.
  • imports: w3c-org (EXTEND): organizational unit and reporting semantics specialized by this model.

Canon, patches & standards

  • REFERENCE `world.organization` (O1): the parent organization whose structure this is.
  • REFERENCE `world.charter` (O4): unit mandates trace to powers delegated under the charter.
  • REFERENCE `world.employment` (O3): role assignments there fill established positions here.
  • REFERENCE `world.stewardship` (S1) and `world.accessGrant` (S2): ownership and access grants over structure data.
  • MIX-IN `world.auditTrail` (S4): audit facets on reorganization and mandate events.
  • imports: w3c-org (EXTEND): organizational unit and reporting semantics specialized by this model.

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

  • `orgChartDisclosure`: structure-only access for partners, auditors or counterparties.
  • `aggregateStaffingReport`: periodic anonymized headcount statistics without position detail.
  • `reorganizationNotice`: advance notice of structural change to affected parties.

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

The parent organization owns the structure record; units have no standing of their own. Access is granted by the parent organization under the S1/S2 models of this catalogue.

Existing assembly

Objects, relationships, events and projections

Objects

  • `unit`: an internal organizational unit; key attributes: name, kind reference, validity period, status.
  • `unitKind`: a classifier of units (department, branch, committee, team); key attributes: scheme, code, description.
  • `reportingLine`: a directed reporting relation between units; key attributes: kind (administrative, functional), validity.
  • `unitMandate`: the remit assigned to a unit; key attributes: scope text, source delegation, validity.
  • `establishedPosition`: a post seated in a unit; key attributes: title, grade, occupancy status, validity.
  • `headcountSnapshot`: a dated headcount measurement; key attributes: date, filled count, established count, basis.
  • `reorganizationAct`: a decision that reshapes structure; key attributes: decision date, effective date, affected units, kind.

Relationships

  • `unit` -> belongsTo -> `world.organization` (n:1): every unit resolves to its parent organization (O1).
  • `unit` -> partOf -> `unit` (n:1): structural containment forming the hierarchy.
  • `unit` -> reportsTo -> `unit` (n:m): reporting lines, possibly distinct from containment.
  • `unitMandate` -> assignedTo -> `unit` (n:1): the remit a unit carries.
  • `establishedPosition` -> seatedIn -> `unit` (n:1): where a post lives.
  • `headcountSnapshot` -> measures -> `unit` (n:1): a dated staffing measurement of one unit.
  • `reorganizationAct` -> reshapes -> `unit` (n:m): the units a reorganization creates, merges, moves or disbands.

Events

  • `unitEstablished`: a new unit was created within the organization.
  • `unitRenamed`: a unit's name or kind changed.
  • `unitReparented`: a unit moved to a different parent in the hierarchy.
  • `unitsMerged`: two or more units were combined.
  • `unitDisbanded`: a unit ceased to exist.
  • `mandateAssigned`: a remit was assigned to or withdrawn from a unit.
  • `headcountRecorded`: a staffing snapshot was taken.

Projections

  • `orgChart`: hierarchy, unit names and reporting lines; omits mandates and headcount.
  • `mandateRegister`: which unit may do what internally; omits staffing data.
  • `staffingTrend`: headcount time series at an aggregation level; omits unit detail below a disclosure threshold.