Digital Twin Knowledge Graph Model
Authoritative schema, relationship taxonomy, and analytical engines that make the twin reason about resilience.
Customer- or revenue-facing capability with measurable SLOs and business impact.
End-to-end workflow that consumes one or more services to deliver business outcome.
Logical software product composed of one or more deployable components.
Independently deployable component exposing APIs or events.
Structured datastore: OLTP, OLAP, KV, time-series, graph, vector.
Block, object, or file storage volume holding application or DB data.
VPC, subnet, VLAN, transit gateway, or load-balanced edge.
Compute, function, queue, or managed service instance.
Geographic failure domain (e.g. us-east-1, westeurope).
IdP, directory, or PAM controlling authentication and authorization.
Preventive, detective, or responsive control (WAF, EDR, DLP, SIEM rule).
Backup product or vault holding recoverable copies.
Standby site, runbook, or DR orchestrator that restores service.
Human or service principal with assigned roles and entitlements.