TWIN-010b — Specify Twin Interaction Direction

Go to TWIN-010 — Control Twin Interaction

Statement

The DIDO-TE SHALL specify the permitted direction of each interaction identified for a Twin Relationship.

Source

, virtual and physical Twin Node concepts, modification of Twin Nodes, comparison of results, and validation[DTE2] Non-Traditional BAA Submission, Digital Twin concepts, monitoring, scenario testing, integration, and Twin Nodes Selection[DTE9] Distributed Immutable Data Object Reference Architecture (DIDO-RA), Digital Twin, distributed data, DDS publish-subscribe, and Quality of Service concepts

Rationale

An interaction permitted within a Twin Relationship may be permitted in one direction, the reverse direction, or both directions.

For example, a Twin Realization may receive state information from a Node without having permission to modify that Node.

Explicit direction prevents bidirectional interaction from being inferred from connectivity, observation capability, DDS publication and subscription relationships, or access to an interface.

Interaction direction remains distinct from interaction permission and authorization. TWIN-010a identifies permitted interactions. TWIN-010b specifies their direction. TWIN-010c governs authorization requirements for state-changing interactions.

Applies To

Verification

Verification confirms that:

Each permitted interaction has a specified direction.The specified direction identifies the originating and receiving entities.A unidirectional interaction does not imply permission for the reverse interaction.A bidirectional interaction is distinguishable from a unidirectional interaction.Communication connectivity, DDS publication and subscription relationships, interface availability, or Quality of Service compatibility do not override the specified interaction direction.The specified interaction direction is traceable to the governing Configuration.Verification includes at least one unidirectional interaction and confirms that the reverse interaction is not treated as permitted.

Traceability

ConOps Relationship

This requirement establishes the permitted direction of interactions identified under TWIN-010a before authorization or execution is evaluated.

Delivery Phase

TBD

Requirement Status

Draft

Statement Reference

{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-010-control-twin-interaction:twin-010b-specify-twin-interaction-direction#Statement&noheader&nofooter&noeditbtn}}

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.