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

Differences

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

Link to this comparison view

Both sides previous 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-009a-identify-permitted-twin-interactions [2026/08/22 14:14] – ↷ Page moved from dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-009-control-twin-interaction_start:twin-009a-identify-permitted-twin-interactions to dido:03-dido-te:99-annexes:annex-c-requirem nick_didodido: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 [2026/08/22 14:24] (current) – nick_dido
Line 1: Line 1:
-====== TWIN-010a — Identify Permitted Twin Interactions ======+====== TWIN-009a — Identify Permitted 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-010 — Control Twin Interaction]]+[[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 ===== ===== 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]].+The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL identify each permitted interaction for every [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]].
  
 ===== Source ===== ===== Source =====
Line 19: Line 19:
 The existence of a Twin Relationship does not grant unrestricted authority to perform every technically possible interaction. 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]].+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. 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.
Line 41: Line 41:
 Verification confirms that: Verification confirms that:
  
-  - Each Twin Relationship identifies the interactions permitted among its participating entities.+  - Each Twin Relationship identifies its permitted interactions.
   - Each permitted interaction identifies the participating entities to which the permission applies.   - Each permitted interaction identifies the participating entities to which the permission applies.
   - An interaction not identified as permitted is distinguishable from a permitted interaction.   - 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. +  - Technical connectivity, discovery, Topic matching, API availability, or Quality of Service compatibility does not establish interaction permission. 
-  - The identified interaction permissions are traceable to the governing Configuration.+  - 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.+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 ===== ===== Traceability =====
Line 55: Line 55:
 ===== ConOps Relationship ===== ===== ConOps Relationship =====
  
-This requirement establishes the set of interactions permitted within a Twin Relationship before evaluating the direction, authorization, or execution of those interactions.+This requirement establishes the set of interactions permitted within a Twin Relationship before evaluation of interaction direction, authorization, or execution.
  
 ===== Delivery Phase ===== ===== Delivery Phase =====
Line 68: Line 68:
  
 <code dokuwiki> <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}}+{{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}}
 </code> </code>
  
  • 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.txt
  • Last modified: 2026/08/22 14:24
  • by nick_dido