====== TWIN-002c — Preserve Twin Realization Association ======

[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-002-associate-twin-realizations:start|Go to TWIN-002 — Associate Twin Realizations]]

===== Statement =====

The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL preserve the association between a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] and its [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identity|Twin Identity]] unless a governed operation changes or removes the association.
===== Source =====

  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1] U.S. Patent Application US20220237111A1]], virtual and physical Twin Node concepts and identifiers shared among Twin Nodes
  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2] Non-Traditional BAA Submission]], F17, //Twin Nodes Selection//

===== Rationale =====

A [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] remains meaningful only while its relationship to the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identity|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 [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]], comparison of Twin Realizations, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] across the lifecycle of the twin relationship.

===== 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_identity|Twin Identity]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identifier|Twin Identifier]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization_identifier|Twin Realization Identifier]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_node|Twin Node]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]

===== Verification =====

Verification confirms that:

  - A Twin Realization remains associated with the same Twin Identity across restart, redeployment, or equivalent lifecycle events.
  - A change to implementation-specific resource identifiers does not alter the Twin Identity associated with the Twin Realization.
  - A Configuration change does not alter the Twin Identity association unless the change explicitly includes an authorized reassociation.
  - Discovery, communication matching, or DDS entity changes do not alter the Twin Identity association.
  - 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.

===== Traceability =====

{{backlinks>.}}

===== ConOps Relationship =====

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

===== 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-002-associate-twin-realizations:twin-002c-preserve-twin-realization-association#Statement&noheader&nofooter&noeditbtn}}
</code>

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>