Show pageOld revisionsBacklinksAdd to bookExport to PDFODT exportBack to top This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. ====== Integrator ====== [[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]] ===== 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. 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. ===== Definition ===== //participant that combines Qualified Nodes, governed functions, interfaces, policies, evidence records, and operational components into a conforming deployment// ===== Source ===== Financial Systems Archetype, Part 7: Governed Node Service Market ===== Note ===== An Integrator differs from a Buyer. A Buyer procures or selects governed functions. An Integrator combines selected components into a conforming deployment. An Integrator may also be a Buyer, Qualified Service Provider, or operator when the same participant selects, deploys, operates, or provides governed functions. ===== Example === An implementation team combines a sanctions screening Node, a semantic validation Node, a policy evaluation Node, an evidence retention Node, and Cost Recovery, Compensation, and Settlement Plane topics into an FX Demo deployment. The team verifies interface conformance, policy compatibility, evidence reference handling, service-level expectations, and Competitive Substitution rules before the deployment receives governed work. dido/99_annexes/annex-b-terms-and-definitions/i/integrator.txt Last modified: 2026/07/18 12:33by 127.0.0.1