TWIN-002c — Preserve Twin Realization Association

Go to TWIN-002 — Associate Twin Realizations

The DIDO-TE SHALL preserve the association between a Twin Realization and its Twin Identity unless a governed operation changes or removes the association.

• [DTE1] U.S. Patent Application US20220237111A1, virtual and physical Twin Node concepts and identifiers shared among Twin Nodes
• [DTE2] Non-Traditional BAA Submission, F17, Twin Nodes Selection

A Twin Realization remains meaningful only while its relationship to the applicable Twin Identity remains explicit and stable.

Preserving this association prevents a Twin Realization from silently changing the logical twin it represents because of deployment, restart, migration, Configuration change, network change, DDS discovery, or another implementation-specific event.

The requirement also supports repeatable Test Execution, comparison of Twin Realizations, and Traceability across the lifecycle of the twin relationship.

• DIDO-TE
• Twin Identity
• Twin Identifier
• Twin Realization
• Twin Realization Identifier
• Twin Node
• Configuration
• Test Execution

Verification confirms that:

1. A Twin Realization remains associated with the same Twin Identity across restart, redeployment, or equivalent lifecycle events.
2. A change to implementation-specific resource identifiers does not alter the Twin Identity associated with the Twin Realization.
3. A Configuration change does not alter the Twin Identity association unless the change explicitly includes an authorized reassociation.
4. Discovery, communication matching, or DDS entity changes do not alter the Twin Identity association.
5. An association changes only through an explicit governed reassociation or removal operation.

Verification includes persistence and recovery of a Twin Realization association across at least one lifecycle event.

This requirement supports continued use of a Twin Realization across lifecycle, Configuration, and deployment changes while preserving the logical twin represented by that realization.

TBD

Draft

{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-002-associate-twin-realizations:twin-002c-preserve-twin-realization-association#Statement&noheader&nofooter&noeditbtn}}