dido:99_annexes:annex-b-terms-and-definitions:p:portability

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-b-terms-and-definitions:p:portability [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:p:portability to dido:99_annexes:annex-b-terms-and-definitions:p:portability nick_didodido:99_annexes:annex-b-terms-and-definitions:p:portability [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Portability ====== ====== Portability ======
-[[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]+[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
  
 ===== Discussion ===== ===== Discussion =====
-Portability describes the ability of a governed function implementation to move across approved platforms, runtimes, deployment environments, or operational contexts while preserving required behaviour. In the Governed Node Service Market, Portability supports deployment flexibility, provider substitution, resilience, and reduced dependence on a single implementation environment.+Portability describes the ability of a governed function implementation to move across approved platforms, runtimes, deployment environments, or operational contexts while preserving required behavior. In the Governed Node Service Market, Portability supports deployment flexibility, provider substitution, resilience, and reduced dependence on a single implementation environment.
  
 Portability does not mean that a Qualified Node may move without review. A movement that changes jurisdiction, residency treatment, sovereignty constraints, security posture, policy context, evidence obligations, runtime environment, or service-level expectations may require requalification or additional Qualification Evidence. Portability does not mean that a Qualified Node may move without review. A movement that changes jurisdiction, residency treatment, sovereignty constraints, security posture, policy context, evidence obligations, runtime environment, or service-level expectations may require requalification or additional Qualification Evidence.
  
 ===== Definition ===== ===== Definition =====
-//ability of a governed function implementation to operate across approved platforms, runtimes, or deployment environments while preserving the required behaviour//+//ability of a governed function implementation to operate across approved platforms, runtimes, or deployment environments while preserving the required behavior//
  
 ===== Source ===== ===== Source =====
Line 19: Line 19:
  
 ===== Example ===== ===== Example =====
-A semantic validation Node runs in one approved container environment and later runs in another approved container environment. The Node preserves interface behaviour, semantic conformance, evidence generation, policy compatibility, and service-level expectations after movement.+A semantic validation Node runs in one approved container environment and later runs in another approved container environment. The Node preserves interface behavior, semantic conformance, evidence generation, policy compatibility, and service-level expectations after movement.
  
  • dido/99_annexes/annex-b-terms-and-definitions/p/portability.1783793681.txt.gz
  • Last modified: 2026/07/11 11:14
  • by nick_dido