MIRA Breaking News
Market Update
MIRA Rollout: 7 Markets Live in Under 12 Months
·
System Alert
The Historic Retirement of SPICS
·
New Feature
MIRA Insights: Capturing Institutional Memory
·
Market Update
MIRA Rollout: 7 Markets Live in Under 12 Months
·
System Alert
The Historic Retirement of SPICS
·
New Feature
MIRA Insights: Capturing Institutional Memory
·
Relationship Types
Define the named edge types used across the ontology graph.
Define New Relationship Type
| Name | Directionality | Description | In Use | |
|---|---|---|---|---|
| composedOf system | A → B | Structural decomposition — aggregate composes its constituent parts | — | protected |
|
|
||||
| CONSUMES system | A → B | Entity A uses or requires Entity B as input. | — | protected |
|
|
||||
| CONTAINS system | A → B | Entity A structurally or logically contains Entity B. | — | protected |
|
|
||||
| DEPENDS_ON system | A → B | Entity A depends on Entity B to function or exist. | — | protected |
|
|
||||
| flowsThrough system | A → B | Interface touched by the process | — | protected |
|
|
||||
| fulfilsItem system | A → B | Delivery note item fulfils a sales order item | — | protected |
|
|
||||
| hasBPMNDiagram system | A → B | Process entity links to a BPMN diagram shadow entity | — | protected |
|
|
||||
| hasCancellationCode system | A → B | Line-specific rejection detail | — | protected |
|
|
||||
| hasColumnName system | A → B | Links a field entity to its scoped physical column-name concept | — | protected |
|
|
||||
| hasDataType system | A → B | Links a field entity to the shared data-type singleton concept | — | protected |
|
|
||||
| hasException system | A → B | Process entity has an exceptions / edge cases section | — | protected |
|
|
||||
| hasExtension system | A → B | Header to postal/charge extension | — | protected |
|
|
||||
| hasHeader system | A → B | Links a delivery note to its originating sales order header | — | protected |
|
|
||||
| hasInput system | A → B | Process entity has an inputs section | — | protected |
|
|
||||
| hasItem system | A → B | Sales order to line relationship | — | protected |
|
|
||||
| hasItemText system | A → B | Line level descriptive text | — | protected |
|
|
||||
| hasKPI system | A → B | Process entity has a KPIs / metrics section | — | protected |
|
|
||||
| hasOutput system | A → B | Process entity has an outputs section | — | protected |
|
|
||||
| hasOverview system | A → B | Process entity has an overview section | — | protected |
|
|
||||
| hasProcessFlow system | A → B | Process entity has a process flow section with step-by-step explanation | — | protected |
|
|
||||
| hasProperty system | A → B | Links a concept entity to one of its field/property child entities | — | protected |
|
|
||||
| hasPurpose system | A → B | Process entity has a purpose section | — | protected |
|
|
||||
| hasRelatedGuide system | A → B | Process entity links to a related KB article guide | — | protected |
|
|
||||
| hasReservationType system | A → B | Reservation orchestration signal | — | protected |
|
|
||||
| hasScope system | A → B | Process entity has a scope section | — | protected |
|
|
||||
| hasSelectionType system | A → B | Delivery creation mode | — | protected |
|
|
||||
| hasStatusCode system | A → B | Current lifecycle code | — | protected |
|
|
||||
| integratesWith system | A → B | System-to-system interface | — | protected |
|
|
||||
| linkedToScreen system | A → B | Screen knowledge model association | — | protected |
|
|
||||
| managedBy system | A → B | Responsible persona | — | protected |
|
|
||||
| monitors system | A → B | Oversight responsibility | — | protected |
|
|
||||
| performedBy system | A → B | Role accountable for execution or approval | — | protected |
|
|
||||
| PRODUCES system | A → B | Entity A creates or outputs Entity B. | — | protected |
|
|
||||
| publishedBy system | A → B | Automation that issues doc | — | protected |
|
|
||||
| REFERENCES system | A → B | Entity A refers to or points to Entity B without ownership. | — | protected |
|
|
||||
| relatesToArtifact system | A → B | General conceptual dependency | — | protected |
|
|
||||
| relatesToPart system | A → B | Part data in focus | — | protected |
|
|
||||
| relatesToPricing system | A → B | Pricing control interplay | — | protected |
|
|
||||
| requiresConfirmation system | A → B | Closure that depends on shipment confirmation | — | protected |
|
|
||||
| targetsMarket system | A → B | Market or LC scope | — | protected |
|
|
||||
| triggeredBy system | A → B | Lists triggers such as batch jobs or inbound sources | — | protected |
|
|
||||
| TRIGGERS system | A → B | Entity A causes or initiates Entity B. | — | protected |
|
|
||||
| usesSystem system | A → B | Runtime systems required | — | protected |
|
|
||||
| writtenToTable system | A → B | Specifies the PostgreSQL table storing the entity | — | protected |
|
|
||||
Asymmetric: direction matters (A → B ≠ B → A). Symmetric: direction is equivalent (A ↔ B, e.g. RELATED_TO). System types are seeded defaults and cannot be deleted or renamed.