TWIN-001c — Identify a Twin Realization [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== TWIN-001c — Identify a Twin Realization ======

[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-001-establish-twin-identity:start|Go to TWIN-001 — Establish Twin Identity]]

===== Statement =====

The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL assign each [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] a unique [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization_identifier|Twin Realization Identifier]].

===== Source =====

  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1] U.S. Patent Application US20220237111A1]], virtual and physical Twin Node concepts
  * [[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_identity|Twin Identity]] identifies the logical twin, while a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization_identifier|Twin Realization Identifier]] identifies a particular [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] associated with that Twin Identity.

Separate identification of each Twin Realization allows DIDO-TE to distinguish among multiple realizations of the same logical twin while preserving their common [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identifier|Twin Identifier]].

The Twin Realization Identifier remains independent of implementation-specific identifiers such as container identifiers, process identifiers, host names, network addresses, DDS entity identifiers, or other resource identifiers.

This distinction supports [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]], realization selection, state acquisition, comparison, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]].

===== Applies To =====

  * [[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]]

===== Verification =====

Verification confirms that:

  - Each Twin Realization has a Twin Realization Identifier.
  - Two distinct Twin Realizations do not have the same Twin Realization Identifier within the applicable identity scope.
  - Multiple Twin Realizations associated with one Twin Identity remain individually distinguishable.
  - The Twin Realization Identifier remains distinguishable from the Twin Identifier.
  - A change to an implementation-specific resource identifier does not, by itself, change the Twin Realization Identifier.

Verification includes inspection of a Twin Identity associated with multiple Twin Realizations.

===== Traceability =====

{{backlinks>.}}

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

This requirement supports registration, Configuration, selection, observation, and comparison of individual Twin Realizations associated with a Twin Identity.

===== 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-001-establish-twin-identity:twin-001c-identify-a-twin-realization#Statement&noheader&nofooter&noeditbtn}}
</code>

----

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