dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-009-control-twin-interaction:twin-009b-specify-twin-interaction-direction

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-009-control-twin-interaction:twin-009b-specify-twin-interaction-direction [2026/08/22 14:15] – removed - external edit (Unknown date) 127.0.0.1dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-009-control-twin-interaction:twin-009b-specify-twin-interaction-direction [2026/08/22 14:25] (current) – nick_dido
Line 1: Line 1:
 +====== TWIN-009b — Specify Twin Interaction Direction ======
  
 +[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-009-control-twin-interaction:start|Go to TWIN-009 — Control Twin Interaction]]
 +
 +===== Statement =====
 +
 +The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL specify the permitted direction of each interaction identified for a [[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 =====
 +
 +An interaction permitted within a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]] may be permitted in one direction, the reverse direction, or both directions.
 +
 +For example, a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] may receive state information from a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] without permission to modify that Node.
 +
 +Specified interaction 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-009a identifies permitted interactions. TWIN-009b specifies their direction. TWIN-009c establishes authorization requirements for Resource state changes.
 +
 +===== 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 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 =====
 +
 +{{backlinks>.}}
 +
 +===== ConOps Relationship =====
 +
 +This requirement establishes the permitted direction of interactions identified under TWIN-009a before evaluation of authorization or execution.
 +
 +===== 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-009-control-twin-interaction:twin-009b-specify-twin-interaction-direction#Statement&noheader&nofooter&noeditbtn}}
 +</code>
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>