TWIN-009e — Reject Prohibited Twin Interactions

Go to TWIN-009 — Control Twin Interaction

Statement

The DIDO-TE SHALL reject each interaction not identified as permitted by the governing Configuration.

Source

, virtual and physical Twin Node concepts, modification of Twin Nodes, comparison of results, and validation[DTE2] Non-Traditional BAA Submission, Digital Twin concepts, monitoring, scenario testing, integration, and Twin Nodes Selection[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 Twin Relationship.

An interaction that is not identified as permitted falls outside the interaction boundary established by the governing 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

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

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

{{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}}

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.