Skip to main content
ParalleliX Docs

// Section 4.1 · Protocol

Capability Match

1 min4.1Protocol
// 1 of 4 · request routing

The binary filter. Yes or no, before anything else.

// 4.1 · capability match · signal 1 of 4

Every routing decision starts with the same question: can this node run this class of work? The answer is binary. Yes means the node enters the candidate pool for the next signal. No means the node is filtered out. There is no partial match, no preference weighting at this stage. The unit of work is the dispatched item: a whole inference request on the live AI path, served end to end by one node, or a sub-task on the general parallelizable-workload path.

Five declared workload classes

// declared at registration · class-based routing is planned

ai.training, ai.inferenceAIDistributed model training, inference, data preprocessing.
science.simulationSCIENCEClimate, genomics, physics, materials simulation.
data.analyticsDATARisk modelling, fraud, healthcare, supply-chain ops.
blockchain.proofBLOCKCHAINzk-batches, oracle aggregation, off-chain proofs.
media.renderRENDER2D/3D rendering, video encoding, AR/VR scenes.

How the filter applies

// work class meets node capability set

// REQUEST
req_a3f1
class: ai.inference
tier: 3
size: medium
→MATCHclass ∩ declared_classes
// CANDIDATE POOL
nd_4f7c · [ai.training, ai.inference, science.simulation]
nd_8e91 · [media.render]
nd_c027 · [ai.training, blockchain.proof]
nd_d104 · [data.analytics, science.simulation]

// 2 of 4 nodes survive the binary filter; the next 3 signals run on this pool only

Routing posture

// declarations exist now · class-based routing is planned

// 1DECLARED, NOT ROUTED

Capability declarations are recorded at registration. The scheduler treats every capable node as eligible for every request. Capability is a metadata field, not a routing filter.

// 2DECLARED, OBSERVED

Capability declarations remain unchanged. Reputation and uptime get observed per class ahead of the routing transition.

// 3DECLARED, ROUTED

Workload-class optimisation ships. Work class becomes a binary filter at dispatch. Mis-declared capabilities are flagged at re-dispatch reconciliation.

// Reading path

Sub-Task Routing hubWorkloads and Roadmap · the five classes in full detailScale Model · where heterogeneous workload support sits