====== TWIN-010a — Identify Permitted Twin Interactions ======

[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-010-control-twin-interaction:start|Go to TWIN-010 — Control Twin Interaction]]

===== Statement =====

The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL identify the interactions permitted among entities participating in each [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]].

===== Source =====

  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1] U.S. Patent Application US20220237111A1]], virtual and physical Twin Node concepts, modification of Twin Nodes, comparison of results, and validation
  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2] Non-Traditional BAA Submission]], Digital Twin concepts, monitoring, scenario testing, integration, and Twin Nodes Selection
  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-009|[DTE9] Distributed Immutable Data Object Reference Architecture (DIDO-RA)]], Digital Twin, distributed data, DDS publish-subscribe, and Quality of Service concepts

===== Rationale =====

A [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|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.

Explicit identification of permitted interactions establishes the semantic and governance boundary for interaction among participating [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realizations]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], and other [[dido:99_annexes:annex-b-terms-and-definitions:r:resource|Resources]].

Technical connectivity, DDS discovery, Topic matching, API availability, or compatible [[dido:99_annexes:annex-b-terms-and-definitions:q:qos|Quality of Service]] characteristics do not establish interaction permission.

The governing [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] provides the controlled basis for identifying the interactions permitted by the Twin Relationship.

===== Applies To =====

  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:r:resource|Resource]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_parameter|Communication Parameter]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:q:qos|Quality of Service]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]]

===== Verification =====

Verification confirms that:

  - Each Twin Relationship identifies the interactions permitted among its participating entities.
  - 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 by itself establish interaction permission.
  - The identified interaction permissions are 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 =====

{{backlinks>.}}

===== ConOps Relationship =====

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

===== Delivery Phase =====

TBD

===== Requirement Status =====

Draft

===== Statement Reference =====

<code dokuwiki>
{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-010-control-twin-interaction:twin-010a-identify-permitted-twin-interactions#Statement&noheader&nofooter&noeditbtn}}
</code>

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>