dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-009-control-twin-interaction:twin-009e-reject-prohibited-twin-interactions

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-009e-reject-prohibited-twin-interactions [2026/08/22 14:22] – 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-009e-reject-prohibited-twin-interactions [2026/08/22 14:27] (current) – nick_dido
Line 1: Line 1:
 +====== TWIN-009e — Reject Prohibited Twin Interactions ======
  
 +[[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 reject each interaction not identified as permitted by the governing [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]].
 +
 +===== 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, governance, distributed data, and DDS concepts
 +
 +===== Rationale =====
 +
 +TWIN-009a identifies the interactions permitted within a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]].
 +
 +An interaction that is not identified as permitted falls outside the interaction boundary established by the governing [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]].
 +
 +Rejecting such an interaction prevents technical connectivity, middleware discovery, Topic matching, interface availability, or other implementation behavior from extending the permitted interaction set.
 +
 +This requirement remains distinct from TWIN-009d. TWIN-009d governs an unauthorized interaction that attempts to change Resource state. TWIN-009e governs an interaction that is not permitted.
 +
 +===== 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: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:
 +
 +  - An interaction identified as permitted is distinguishable from an interaction not identified as permitted.
 +  - An interaction not identified as permitted is rejected.
 +  - Technical connectivity does not cause an unpermitted interaction to be accepted.
 +  - DDS discovery, Topic matching, interface availability, or Quality of Service compatibility does not cause an unpermitted interaction to be accepted.
 +  - Rejection is traceable to the attempted interaction and the governing Configuration.
 +
 +Verification includes one interaction identified as permitted and one technically possible interaction not identified as permitted and confirms rejection of the latter.
 +
 +===== Traceability =====
 +
 +{{backlinks>.}}
 +
 +===== ConOps Relationship =====
 +
 +This requirement enforces the interaction boundary established by TWIN-009a by rejecting interactions outside the permitted interaction set.
 +
 +===== 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-009e-reject-prohibited-twin-interactions#Statement&noheader&nofooter&noeditbtn}}
 +</code>
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>