| Table of Contents | ||
|---|---|---|
|
...
The following Orthogramic domains are considered passive:
Domain | Typical Role in Relationships |
|---|---|
Information | Referenced by, used by, governed by |
Performance | Measured by, contributed to, indicator of |
Product | Delivered by, enabled by, rarely strategic |
Service | Implements, delivers, used in context |
...
It’s more accurate to say a Capability uses Information than to say Information informs Capability.
A Policy governs Information — not the other way around.
A Performance metric is influenced by Initiatives, not vice versa.
Directionality
Cross domain
...
relationships
Passive domains must not initiate cross domain relationships
Applies to: Cross domain relationship definition and visualisation
...
Reasoning:
This ensures semantic clarity, avoids visual clutter, and supports reasoning engines that depend on clear relationship directionality.
Inter-domain
...
relationships
Directionality does apply to inter-domain relationships, but the active/passive domain distinction used in cross-domain relationships must be interpreted differently in an inter-domain context.
Overview
Inter-domain relationships show how elements of different domains are related across organisational units (e.g. how a Capability in Unit A relies on a Service in Unit B).
...
However, in this context, directionality is more about organisational dependency and flow of responsibility than about whether the source domain is conceptually "active."
Active/Passive domain roles are less rigid here
In cross-domain relationships:
...
The organisational context adds nuance.
The focus is on who depends on whom across units, not just structural domain logic.
Conclusion
Directionality is essential in inter-domain relationships.
Active/passive modelling constraints do not strictly apply — a passive domain element may be the source of an inter-unit relationship if it represents an organisational responsibility.