This is an old revision of the document!
TWIN-010c — Require Authorization for State-Changing Interactions
Statement
The DIDO-TE SHALL require authorization for each permitted interaction that changes the state of a Twin Realization, Node, or Resource.
Source
-
[DTE1] U.S. Patent Application US20220237111A1, modification of virtual and physical Twin Nodes, comparison of results, and validation
-
[DTE2] Non-Traditional BAA Submission, Digital Twin concepts, scenario testing, integration, monitoring, and Twin Nodes Selection
-
[DTE9] Distributed Immutable Data Object Reference Architecture (DIDO-RA), Digital Twin and governance concepts
Rationale
Permission to perform an interaction does not establish authority to change the state of another entity.
State-changing interactions can alter the conditions under which Test Execution, synchronization, comparison, or Validation occurs. Such interactions therefore require an authorization decision in addition to being identified as permitted.
This requirement establishes the authorization requirement. TWIN-010d separately prevents execution when the required authorization is absent or denied.
Technical connectivity, interface availability, DDS discovery, Topic matching, or communication compatibility does not establish authorization.
Applies To
Verification
Verification confirms that:
-
Each permitted state-changing interaction requires an authorization decision.
-
A permitted interaction that does not change state does not acquire a state-change authorization requirement solely because it participates in a Twin Relationship.
-
The authorization requirement identifies the interaction and the entity whose state may change.
-
Interaction permission does not substitute for authorization.
-
Interaction direction does not substitute for authorization.
-
Technical connectivity or interface access does not establish authorization.
Verification includes at least one permitted state-changing interaction and confirms that authorization is required independently of interaction permission.
Traceability
ConOps Relationship
This requirement establishes the authorization prerequisite for permitted state-changing interactions after interaction permission and direction have been defined.
Delivery Phase
TBD
Requirement Status
Draft
Statement Reference
{{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-require-authorization-for-state-changing-interactions#Statement&noheader&nofooter&noeditbtn}}
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.