dido:99_annexes:annex-b-terms-and-definitions:i:integrator

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:i:integrator [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:i:integrator to dido:99_annexes:annex-b-terms-and-definitions:i:integrator nick_didodido:99_annexes:annex-b-terms-and-definitions:i:integrator [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Integrator ====== ====== Integrator ======
  
-[[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 =====
 An Integrator represents a participant that combines Qualified Nodes, governed functions, interfaces, policies, evidence records, operational components, and deployment constraints into a conforming implementation of the Governed Node Service Market. An Integrator represents a participant that combines Qualified Nodes, governed functions, interfaces, policies, evidence records, operational components, and deployment constraints into a conforming implementation of the Governed Node Service Market.
  
-The Integrator relies on qualification, interface conformance, semantic compatibility, configuration rules, non-functional characteristics, evidence obligations, service-level expectations, and substitution criteria when assembling a deployment. The Integrator’s concern is not limited to whether a Qualified Node performs a governed function. The Integrator must also determine whether the Qualified Node works correctly with other Qualified Nodes, other architectural planes, governance rules, evidence flows, cost records, and settlement artefacts.+The Integrator relies on qualification, interface conformance, semantic compatibility, configuration rules, non-functional characteristics, evidence obligations, service-level expectations, and substitution criteria when assembling a deployment. The Integrator’s concern is not limited to whether a Qualified Node performs a governed function. The Integrator must also determine whether the Qualified Node works correctly with other Qualified Nodes, other architectural planes, governance rules, evidence flows, cost records, and settlement artifacts.
  
 The Integrator’s primary concerns include compatibility, deployment, configuration, substitution, interfaces, operational fit, evidence integration, and conformance of the resulting deployment. The Integrator’s primary concerns include compatibility, deployment, configuration, substitution, interfaces, operational fit, evidence integration, and conformance of the resulting deployment.
  • dido/99_annexes/annex-b-terms-and-definitions/i/integrator.1783793676.txt.gz
  • Last modified: 2026/07/11 11:14
  • by nick_dido