Organizational structure
A versioned graph of organizational units, positions, teams and assignments along independent axes.
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 landscape
- Entry kind
- landscape
- Domain
- EnterpriseLND
- Industry
- Cross-industry
- Tags
- EM-LND-01W1landscapeOrganizationLandscapeStructureAxisStructureSnapshot
What it is Filled
A versioned graph of organizational units, positions, teams and assignments along independent axes.
Why it exists Filled
A versioned graph of organizational units, positions, teams and assignments along independent axes.
Distinguishing features Derived, awaiting review
- Axis and period are mandatory
- A cycle is forbidden only where a hierarchy is required
- Person and Unit are not copied
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: A matrix assignment breaks the single-manager rule for the whole organization.
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
Куратор мета-моделей Vercy
Master systems
- Реестр моделей
- sources.yaml
- vercy.lock
- политики
Links to other meta-models Filled
references
- WM-ORG-002 - conceptual-candidate
- WM-ORG-003 - conceptual-candidate
- WM-ORG-004 - conceptual-candidate
- WM-ORG-016 - conceptual-candidate
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Derived, awaiting review
- OrganizationLandscape
- StructureAxis
- StructureSnapshot
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
- Vercy composition and whole-object: a separate landscape object and delegation
- ArchiMate/ISO 42010: views, questions and representation rules
- Compare participants' domain models and the practical assembly of the permitted context
Open questions
- How to distinguish the administrative, functional and project axes?
- Where is a single parent admissible?
- How to see the structure as of a date before a reorganization?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-lnd-01/brief.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.