9.3 Qualification-Based Eligibility

Go up to Market Operating Model

Qualification-Based Eligibility identifies whether a Node or Service Provider qualifies to receive governed work for a defined governed function under stated constraints.

The Governed Node Service Market does not treat all connected Nodes as eligible. Eligibility depends on a recognised qualification for the governed function, supported Non-Functional Characteristics, applicable Qualification Evidence, jurisdictional constraints, residency constraints, sovereignty constraints, policy obligations, evidence obligations, service-level expectations, suspension status, and market rules.

A Qualified Service Provider establishes organizational accountability for one or more governed functions. A Qualified Node establishes operational eligibility to perform a governed function. The market uses Qualification Profiles and Qualification Evidence to determine whether the Qualified Service Provider and Qualified Node satisfy the eligibility requirements for the requested work.

Qualification-Based Eligibility supports governed competition. Qualified Nodes compete only when they satisfy the same required governed function, policy constraints, evidence obligations, and Non-Functional Characteristic expectations. A Node that fails a required qualification criterion does not enter the eligible set for that work assignment.

Eligibility may vary by governed function, jurisdiction, deployment context, policy class, information class, evidence obligation, or service-level expectation. A Node may qualify for one governed function but not another. A Node may qualify in one jurisdiction but not another. A Node may qualify for one evidence obligation but not another.

Qualification-Based Eligibility also supports suspension and restoration. A Node that loses qualification, fails required evidence obligations, accumulates relevant Non-Performance Indicators, or violates market rules may lose eligibility until the required review, correction, or requalification restores the recognised qualification.

Example

A semantic validation Node has recognised qualification for FX transaction validation in one jurisdiction. The same Node does not have a recognised qualification for sanctions screening or transaction validation in another jurisdiction. The market includes the Node in the eligible set for the qualified validation work only when the applicable policy, evidence, residency, sovereignty, service-level, and Non-Functional Characteristic requirements are satisfied.