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-010-control-twin-interaction:twin-010c-authorize-state-changing-twin-interactions [2026/08/21 16:28] – created nick_dido
+++ dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-010-control-twin-interaction:twin-010c-authorize-state-changing-twin-interactions [2026/08/21 16:56] (current) – removed nick_dido
@@ Line 1: / Line 1: @@
-====== TWIN-010c — Authorize State-Changing 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 authorize each permitted interaction that changes the state of a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]], or [[dido:99_annexes:annex-b-terms-and-definitions:r:resource|Resource]] before executing that interaction.
-===== 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, scenario testing, integration, monitoring, 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, governance, and DDS concepts
-===== Rationale =====
-A [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]] may permit interactions that alter the state of a participating [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]], or other [[dido:99_annexes:annex-b-terms-and-definitions:r:resource|Resource]].
-Permission to perform an interaction does not, by itself, establish authority to execute a state-changing interaction under every condition.
-Authorization provides the controlled decision that permits a state-changing interaction to execute under the governing conditions.
-Requiring authorization before execution prevents observation capability, communication access, DDS discovery, Topic matching, API availability, or possession of a technically usable interface from being interpreted as authority to modify another entity.
-Authorization remains distinct from interaction permission and direction. TWIN-010a identifies permitted interactions, TWIN-010b specifies their permitted direction, and this requirement governs authorization of state-changing interactions before execution.
-===== 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:d:dds|DDS]]
-  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]
-  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]
-===== Verification =====
-Verification confirms that:
-  - Each permitted state-changing interaction is subject to authorization before execution.
-  - An authorized state-changing interaction can execute when the governing authorization conditions are satisfied.
-  - A state-changing interaction cannot execute when authorization is absent or denied.
-  - Authorization applies to the specific interaction and target entity for which it was granted.
-  - Interaction permission or direction does not replace authorization for a state-changing interaction.
-  - Technical connectivity, DDS discovery, Topic matching, API availability, or interface access does not establish authorization.
-  - The authorization decision is traceable to the state-changing interaction that it governs.
-Verification includes one authorized state-changing interaction and one unauthorized state-changing interaction and confirms that only the authorized interaction executes.
-===== Traceability =====
-{{backlinks>.}}
-===== ConOps Relationship =====
-This requirement governs authorization of permitted state-changing interactions after interaction permission and direction have been established and before execution occurs.
-Authorization decisions support controlled modification of Twin Realizations, Nodes, and Resources during Test Execution and related operations.
-===== 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-010c-authorize-state-changing-twin-interactions#Statement&noheader&nofooter&noeditbtn}}
-</code>
-----
-<WRAP centeralign>
-© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
-</WRAP>