Differences

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

--- dido:99_annexes:annex-b-terms-and-definitions:q:qualified_node [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:q:qualified_node [2026/08/06 10:47] (current) – nick_dido
@@ Line 1: / Line 1: @@
 ====== Qualified Node ======
-[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
+[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 ===== Discussion =====
-A Qualified Node performs governed work after the architecture recognises its eligibility for a defined function. Qualification supports trust, cost attribution, provider comparison, compensation, and settlement in the Cost Recovery, Compensation, and Settlement Plane.
+A [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] becomes a Qualified Node when an authorized qualification process determines that the Node satisfies the criteria applicable to a defined governed function, scope, and operating context.
-A Qualified Node satisfies the relevant interface, semantic, policy, evidence, security, residency, sovereignty, operational, and service-level criteria for a defined work type. Qualification prevents the architecture from treating an unverified or unsuitable Node as eligible for compensation.
+The qualification criteria address the characteristics relevant to the governed function. These characteristics include applicable interface, [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|semantic]], policy, [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], [[dido:99_annexes:annex-b-terms-and-definitions:s:security|Security]], residency, sovereignty, operational, and service-level criteria.
-A Qualified Node also supports competition among implementations. Different Nodes can compete to perform the same governed function when each Node satisfies the same qualification criteria and produces the required evidence.
+Qualification supports trust, provider comparison, [[dido:99_annexes:annex-b-terms-and-definitions:c:cost|Cost]] attribution, compensation eligibility, and settlement. It prevents an unverified or unsuitable Node from receiving authorization or compensation for governed work.
+Qualification also supports competition among implementations. Different Nodes compete to perform the same governed function when each Node satisfies the applicable qualification criteria and produces the required Evidence.
+The qualification record identifies:
+  * The Qualified Node
+  * The governed function
+  * The applicable qualification criteria
+  * The operating context
+  * The applicable jurisdiction
+  * The qualifying [[dido:99_annexes:annex-b-terms-and-definitions:a:authority|Authority]]
+  * The qualification method
+  * The supporting Evidence
+  * The qualification date
+  * The validity period
+  * Any limitations or conditions
+  * The applicable [[dido:99_annexes:annex-b-terms-and-definitions:v:version|Version]]
+  * The applicable [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]]
+A material change to the Node, its Configuration, its operating context, or the applicable qualification criteria initiates the defined review or requalification process.
 ===== Definition =====
-//Node recognised as eligible to perform a defined governed function//
+//[[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] determined by an authorized qualification process to satisfy the criteria applicable to a defined governed function, scope, and operating context//
 ===== Source =====
-FX Demo Reference Architecture, Part 6: Cost Recovery, Compensation, and Settlement Plane
+Financial Systems Archetype, Part 6: Cost Recovery, Compensation, and Settlement Plane
+Financial Systems Archetype, Part 7: Governed Node Service Market
 ===== Note =====
-A Qualified Node differs from a running Node. A running Node has operational presence. A Qualified Node has recognised eligibility for a defined governed function.
+A Qualified Node differs from a running Node:
-Qualification supports compensation eligibility but does not by itself prove that the Node completed a specific item of work.
+  * A running Node has an operational presence
+  * A Qualified Node has recognized eligibility for a defined governed function, scope, and operating context
+Qualification establishes eligibility to perform governed work. Qualification does not establish that the Qualified Node completed a particular item of work.
+Evidence of completed work supports attribution, compensation, and settlement for that item of work.
+Qualification applies only within its defined scope, operating context, validity period, and conditions. Qualification for one governed function does not establish qualification for another governed function.
 ===== Example =====
-A sanctions screening Node satisfies the required policy, evidence, residency, security, and service-level criteria for sanctions screening in a defined jurisdiction. The architecture treats that Node as a Qualified Node for sanctions screening work.
+An authorized qualification process evaluates a sanctions-screening Node against the policy, Evidence, residency, Security, interface, and service-level criteria applicable within a defined jurisdiction.
+The resulting qualification record identifies the Node, governed function, jurisdiction, Configuration, Version, validity period, applicable criteria, and supporting Evidence.
+The Node is a Qualified Node for sanctions-screening work within that defined scope. The qualification does not establish that the Node completed any particular sanctions-screening request.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>