TWIN-002c — Preserve Twin Realization Association

Go to TWIN-002 — Associate Twin Realizations

Statement

The DIDO-TE SHALL preserve the association between a Twin Realization and its Twin Identity until the association is explicitly changed or removed through a governed operation.

Source

, virtual and physical Twin Node concepts and identifiers shared among Twin Nodes[DTE2] Non-Traditional BAA Submission, F17, Twin Nodes Selection

Rationale

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.

Applies To

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

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

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

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