TWIN-009a — Identify Permitted Twin Interactions

Go to TWIN-009 — Control Twin Interaction

Statement

The DIDO-TE SHALL identify each permitted interaction for every 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

A Twin Relationship may involve multiple forms of interaction, including observation, information exchange, synchronization, simulation, invocation, or state-changing operations.

The existence of a Twin Relationship does not grant unrestricted authority to perform every technically possible interaction.

Identification of permitted interactions establishes the semantic and governance boundary for interaction among participating Twin Realizations, Nodes, and other Resources.

Technical connectivity, DDS discovery, Topic matching, API availability, or compatible Quality of Service characteristics do not establish interaction permission.

The governing Configuration provides the controlled basis for identifying the interactions permitted by the Twin Relationship.

Applies To

Verification

Verification confirms that:

Each Twin Relationship identifies its permitted interactions.Each permitted interaction identifies the participating entities to which the permission applies.An interaction not identified as permitted is distinguishable from a permitted interaction.Technical connectivity, discovery, Topic matching, API availability, or Quality of Service compatibility does not establish interaction permission.Each identified interaction permission is traceable to the governing Configuration.Verification includes a Twin Relationship with at least one permitted interaction and at least one technically possible interaction that is not permitted and confirms that the two are distinguishable.

Traceability

ConOps Relationship

This requirement establishes the set of interactions permitted within a Twin Relationship before evaluation of interaction direction, authorization, or execution.

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-009-control-twin-interaction:twin-009a-identify-permitted-twin-interactions#Statement&noheader&nofooter&noeditbtn}}

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