Differences

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

--- dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-009-control-twin-interaction:start [2026/08/22 13:57] – [Contents] nick_dido
+++ dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-009-control-twin-interaction:start [2026/08/22 14:09] (current) – nick_dido
@@ Line 3: / Line 3: @@
 [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:start|Go to C.3.3 Twin Node Requirements]]
-TWIN-010 is a non-leaf requirement group governing interactions among [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realizations]] and between a Twin Realization and another entity participating in a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]].
+TWIN-009 is a non-leaf requirement group governing interactions among [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realizations]] and between a Twin Realization and another entity participating in a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]].
 A Twin Relationship does not, by itself, grant a Twin Realization authority to modify another Twin Realization, a corresponding [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]], or another [[dido:99_annexes:annex-b-terms-and-definitions:r:resource|Resource]].
@@ Line 11: / Line 11: @@
 Communication connectivity, DDS discovery, Topic matching, [[dido:99_annexes:annex-b-terms-and-definitions:q:qos|Quality of Service]] compatibility, or possession of a technically usable interface does not establish permission to perform an interaction.
-Conformance is assessed against the individual leaf requirements listed below. TWIN-010 does not establish a separate conformance obligation.
+Conformance is assessed against the individual leaf requirements listed below. TWIN-009 does not establish a separate conformance obligation.
 ===== Requirements =====
 ^ Requirement ID ^ Requirement Title ^ Purpose ^
-| TWIN-010a | Identify Permitted Twin Interactions | Identify the interactions permitted for a Twin Relationship. |
+| TWIN-009a | Identify Permitted Twin Interactions | Identify the interactions permitted for a Twin Relationship. |
-| TWIN-010b | Specify Twin Interaction Direction | Specify the permitted direction of each configured interaction. |
+| TWIN-009b | Specify Twin Interaction Direction | Specify the permitted direction of each configured interaction. |
-| TWIN-010c | Require Authorization for Resource State Changes | Require authorization for each permitted interaction that changes the state of a Resource. |
+| TWIN-009c | Require Authorization for Resource State Changes | Require authorization for each permitted interaction that changes the state of a Resource. |
-| TWIN-010d | Prevent Unauthorized Resource State Changes | Prevent execution of a state-changing interaction with a Resource that lacks authorization. |
+| TWIN-009d | Prevent Unauthorized Resource State Changes | Prevent an unauthorized interaction from changing the state of a Resource. |
-| TWIN-010e | Reject Prohibited Twin Interactions | Reject interactions that are not permitted by the governing Configuration. |
+| TWIN-009e | Reject Prohibited Twin Interactions | Reject interactions that are not permitted by the governing Configuration. |
 ===== Contents =====
-{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-009-control-twin-interaction#1|js navbar nocookie maxjs#1 id#dido_te_twin_010_requirements_nav}}
+  * [[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|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:twin-009b-specify-twin-interaction-direction|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:twin-009c-require-authorization-for-resource-state-changes|TWIN-009c — Require Authorization for Resource State Changes]]
+  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-009-control-twin-interaction:twin-009d-prevent-unauthorized-resource-state-changes|TWIN-009d — Prevent Unauthorized Resource State Changes]]
+  * [[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|TWIN-009e — Reject Prohibited Twin Interactions]]
+{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-009-control-twin-interaction#1|js navbar nocookie maxjs#1 id#dido_te_twin_009_requirements_nav}}
 ===== Source =====
@@ Line 86: / Line 92: @@
 ===== Notes for Editors =====
-TWIN-010 is a non-leaf requirement group and does not contain an independent normative Statement or Verification section.
+TWIN-009 is a non-leaf requirement group and does not contain an independent normative Statement or Verification section.
 The explicit child links under Contents remain while the subordinate requirement pages are being created and reviewed. After all child pages exist, you may remove the explicit links because the ''indexmenu'' automatically discovers them.
@@ Line 94: / Line 100: @@
 Do not infer interaction permission from technical connectivity, DDS discovery, Topic matching, API availability, or Quality of Service compatibility.
-TWIN-010 governs permission and control of interaction. Communication Configuration remains governed by TWIN-003e, Quality of Service Configuration by TWIN-003f, synchronization by TWIN-006, and general Security requirements by C.4.
+TWIN-009 governs permission and control of interaction. Communication Configuration remains governed by TWIN-003e, Quality of Service Configuration by TWIN-003f, synchronization by TWIN-006, and general Security requirements by C.4.
 ----