Ontology

Nodes are non-divisible components with exactly one element kind and one layer. Relationships are asserted in canonical direction only; inverses are declared with owl:inverseOf. Domain and range are enforced by SHACL. Machine-readable files: kg/ara-ontology.ttl, kg/ara-shapes.ttl.

Element kinds

Kind	Definition	Components
Software component	An active, executable unit of behaviour (agent, service, controller, pipeline stage).	938
Data store	A persistent or durable store of data read and written at runtime (vector index, graph store, checkpoint store, log store).	117
Data artifact	A passive, versioned structural object that shapes behaviour: prompt template, policy, schema, configuration, state definition.	364
Model asset	A trained machine-learning model or compiled inference engine (weights, adapters, optimized engine).	63
Interface	A point of access exposing a component's services through a defined protocol or contract (API, tool protocol endpoint).	34
Infrastructure resource	A compute, accelerator, network, or execution-isolation resource on which software, models, or stores are deployed.	33
Human role	A human responsibility that participates in the architecture's runtime or governance (reviewer, operator, auditor, end user).	38

Relationship types (30)

Relationship	Category	Subject kinds	Object kinds	Definition	ArchiMate	Edges
`ara:configures` inverse: is configured by	structural	Data artifact	Data artifact, Data store, Human role, Infrastructure resource, Interface, Model asset, Software component	The data artifact (prompt, schema, configuration, rule set) determines how the object behaves.	Association (directed) / Influence	423
`ara:deployedOn` inverse: hosts	structural	Data store, Model asset, Software component	Infrastructure resource, Software component	The subject is deployed onto, hosted by, or executes within the object (including isolation sandboxes, GPU partitions, and inference servers hosting models).	Assignment (inverse)	221
`ara:exposes` inverse: is exposed by	structural	Software component	Interface	The software component makes its services available through the interface.	Composition (component–interface)	36
`ara:caches` inverse: is cached by	dependency	Data store, Software component	Interface, Software component	The subject stores and replays results of the object to avoid recomputation.	Serving	21
`ara:delegatesTo` inverse: receives delegation from	dependency	Software component	Software component	The subject hands a sub-task, with its goal and context, to the object, which completes it with some autonomy.	Serving (inverse) + Triggering	10
`ara:invokes` inverse: is invoked by	dependency	Human role, Software component	Interface, Software component	The subject calls the object's service (request–response or streaming) and consumes its result.	Serving (inverse)	729
`ara:reads` inverse: is read by	dependency	Software component	Data artifact, Data store	The subject retrieves information from the data store or data artifact.	Access (read)	652
`ara:writes` inverse: is written by	dependency	Software component	Data artifact, Data store	The subject creates, updates, or deletes information in the data store or data artifact.	Access (write)	328
`ara:emitsTelemetryTo` inverse: receives telemetry from	dynamic	Data artifact, Data store, Human role, Infrastructure resource, Interface, Model asset, Software component	Data store, Software component	The subject emits traces, logs, metrics, or audit events to the object.	Flow	147
`ara:escalatesTo` inverse: receives escalation from	dynamic	Software component	Human role, Software component	When confidence, risk, or policy thresholds are crossed, the subject hands control of a case to the object.	Triggering	86
`ara:routesTo` inverse: is routed to by	dynamic	Software component	Interface, Software component	The subject selects the object as the destination of a request according to a routing policy (intent, cost, load, capability).	Flow	117
`ara:sendsDataTo` inverse: receives data from	dynamic	Data artifact, Data store, Human role, Infrastructure resource, Interface, Model asset, Software component	Data artifact, Data store, Human role, Infrastructure resource, Interface, Model asset, Software component	Information flows from the subject to the object (push, stream, or event).	Flow	490
`ara:triggers` inverse: is triggered by	dynamic	Human role, Software component	Human role, Software component	An event or completion in the subject causes the object to start behaviour (temporal/causal, typically asynchronous).	Triggering	133
`ara:approves` inverse: requires approval from	control	Human role, Software component	Software component	The subject must grant explicit approval before the object's gated actions take effect (human-in-the-loop gate).	Influence	17
`ara:constrains` inverse: is constrained by	control	Data artifact, Software component	Data artifact, Data store, Human role, Infrastructure resource, Interface, Model asset, Software component	The subject (typically a policy or limit) restricts the permissible behaviour, resources, or action space of the object.	Influence	117
`ara:controlsAccessTo` inverse: has access controlled by	control	Software component	Data artifact, Data store, Human role, Infrastructure resource, Interface, Model asset, Software component	The subject authenticates principals and authorises (or denies) their access to the object.	Serving / Influence	30
`ara:failsOverTo` inverse: is failover for	control	Interface, Software component	Interface, Software component	When the subject is unavailable or degraded, requests are served by the object instead (fallback / graceful degradation).	Association (directed)	17
`ara:guards` inverse: is guarded by	control	Software component	Data artifact, Data store, Human role, Infrastructure resource, Interface, Model asset, Software component	The subject inspects the object's inputs, outputs, or actions at runtime and can block, modify, or redirect them.	Influence (−) / Serving	118
`ara:orchestrates` inverse: is orchestrated by	control	Software component	Software component	The subject coordinates the object's execution: sequencing, scheduling, lifecycle, and state transitions.	Triggering + Assignment	134
`ara:overrides` inverse: is overridden by	control	Human role, Software component	Software component	The subject can pre-empt, halt, roll back, or replace the object's decisions after they are taken (human-on/over-the-loop).	Influence	24
`ara:scales` inverse: is scaled by	control	Software component	Data store, Infrastructure resource, Software component	The subject adjusts the number of replicas or the resource allocation of the object in response to demand signals.	Influence	24
`ara:audits` inverse: is audited by	assurance	Human role, Software component	Data artifact, Data store, Human role, Infrastructure resource, Interface, Model asset, Software component	The subject examines the object's records or behaviour for conformance with policy, regulation, or standards.	Association (directed)	60
`ara:evaluates` inverse: is evaluated by	assurance	Human role, Software component	Data artifact, Data store, Human role, Infrastructure resource, Interface, Model asset, Software component	The subject measures the quality, accuracy, or safety of the object's outputs or behaviour against criteria (offline or online).	Association (directed)	177
`ara:monitors` inverse: is monitored by	assurance	Human role, Software component	Data artifact, Data store, Human role, Infrastructure resource, Interface, Model asset, Software component	The subject continuously observes the object's health, performance, cost, or drift and raises signals on anomalies.	Association (directed)	150
`ara:optimizes` inverse: is optimized by	lifecycle	Software component	Model asset	The subject transforms the model asset into a more efficient form without retraining its task behaviour (quantization, compilation, pruning).	Realization	18
`ara:produces` inverse: is produced by	lifecycle	Software component	Data artifact, Data store, Model asset	The subject generates the object as an output artifact (build-time or batch), as distinct from runtime writes to a store.	Realization / Access (write)	56
`ara:trains` inverse: is trained by	lifecycle	Software component	Model asset	The subject creates or updates the model asset's parameters (pre-training, fine-tuning, PEFT, preference optimisation).	Realization	35
`ara:alternativeTo` inverse: is target of alternativeTo	variability	Data artifact, Data store, Human role, Infrastructure resource, Interface, Model asset, Software component	Data artifact, Data store, Human role, Infrastructure resource, Interface, Model asset, Software component	Subject and object are substitutable variants of the same variation point: both specialize, directly or transitively, a common ancestor component. Alternatives MAY be combined unless linked by ara:excludes.	Association (undirected)	429
`ara:excludes` inverse: is target of excludes	variability	Data artifact, Data store, Human role, Infrastructure resource, Interface, Model asset, Software component	Data artifact, Data store, Human role, Infrastructure resource, Interface, Model asset, Software component	Subject and object must not both be selected in one architecture configuration (feature-model 'excludes' constraint).		2
`ara:specializes` inverse: is specialized by	variability	Data artifact, Data store, Human role, Infrastructure resource, Interface, Model asset, Software component	Data artifact, Data store, Human role, Infrastructure resource, Interface, Model asset, Software component	The subject is a concrete variant (or narrower role) of the object; it fulfils the object's responsibility in a particular way and inherits its relationships.	Specialization	487