====== TWIN-005c — Access Twin Realization State Values ====== [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-005-acquire-twin-state:start|Go to TWIN-005 — Access Twin Realization State]] ===== Statement ===== The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL provide access to the values that constitute the determined state of each [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] participating in [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]. ===== Source ===== * [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1] U.S. Patent Application US20220237111A1]], virtual and physical Twin Node concepts, observation of Twin Node behavior, baseline results, and comparison of results * [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2] Non-Traditional BAA Submission]], Digital Twin concepts, real-time monitoring, scenario testing, and Twin Nodes Selection * [[dido:03-dido-te:99-annexes:annex-b-references:dte-009|[DTE9] Distributed Immutable Data Object Reference Architecture (DIDO-RA)]], Digital Twin and distributed data concepts ===== Rationale ===== Determination of the state of a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] identifies its current condition. Test Execution, synchronization, simulation, comparison, and Validation also require access to the values from which that state is determined. The [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_data_mapping|Twin Data Mapping]] establishes the semantic correspondence between represented characteristics and their data representations. This requirement ensures that the resulting state values remain accessible independently of the mechanism used to obtain or transport them. Access to a state value does not, by itself, establish its [[dido:99_annexes:annex-b-terms-and-definitions:d:data_source|Data Source]], temporal context, provenance, eligibility, or authority. Those concerns are governed separately. ===== 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_relationship|Twin Relationship]] * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_data_mapping|Twin Data Mapping]] * [[dido:99_annexes:annex-b-terms-and-definitions:d:data_source|Data Source]] * [[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: - The values that constitute the determined state of each participating Twin Realization can be accessed. - Each accessed value corresponds to a represented characteristic of the governing Twin Relationship. - Each accessed value conforms to the governing Twin Data Mapping. - Values outside the represented scope of the Twin Relationship are not treated as state values solely because they are technically accessible. - Access to state values remains independent of the implementation-specific communication mechanism used to obtain those values. - Each accessed state value remains associated with the Twin Realization whose state it represents. Verification includes access to the values constituting the determined state of at least one Twin Realization during Test Execution. ===== Traceability ===== {{backlinks>.}} ===== ConOps Relationship ===== This requirement provides access to the values that constitute the determined state of a Twin Realization for synchronization, simulation, comparison, Validation, monitoring, and evidence generation. ===== 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-005-acquire-twin-state:twin-005c-access-twin-state-values#Statement&noheader&nofooter&noeditbtn}} ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.