Ten hard filters. One inspectable report.

The Lab sends one complete Nexus service manifest and one complete Nexus search request to the canonical compatibility evaluator. Every dimension passes or blocks independently. There is no percentage score and no generated ranking.

Method basis reviewed against the repository implementation on 4 September 2026.

Exact inputs

The evaluator accepts exactly two frozen v1 contract families:

nexus_service_manifest: the provider’s versioned declaration.
nexus_search_request: the buyer requirement profile and its ten constraint groups.

The server applies the strict Nexus parser and schema validation before any comparison. It rejects malformed documents, unsupported families, duplicate object members, unsafe numbers, oversized input, and secret-bearing fields.

Do not paste credentials.

A service declaration describes requirements and boundaries. It must never contain an API key, access token, password, client secret, or private key.

The ten filters

Dimension	What is compared
Input	Required media type or schema digest against the input contract on one usable binding.
Output	Required media type or schema digest against the output contract on that same binding.
Protocol	Accepted protocol families and transports against the joint input/output binding.
Price / payment	Payment mode and, where specified, price, asset, and supported payment network.
Authority	Required write, network, secret-access, and spend authority against the buyer ceiling.
Privacy	Declared data classes, retention level, and training use against permitted bounds.
Evidence	Promised response digest, schema validation, gateway observation, and provider assertion.
Availability	The declared health state against the states accepted by the profile.
Latency	The declared maximum timeout against the profile maximum.
Side effects	Whether required external effects are accepted by the profile.

The report

The canonical result contains the policy version, evaluation time, request and manifest identifiers, input digests, one finding for each dimension, an evidence digest for each finding, and a report digest.

The interface shows submitted values beside the chosen requirements. Any suggested review text is editorial guidance, not part of the canonical report and not permission to misstate a service.

Run the worked manifest through the evaluator.

What it does not decide

The current ten-filter function does not compare the requested capability with the manifest’s capability list. That belongs to a separate Nexus search and ranking stage. A passing report therefore means contract-compatible with this profile, not “a buyer will select this service.”

It also does not prove ownership, safety, service quality, current reachability, provenance, authorization, or permission to invoke. A declaration remains a declaration unless another bounded evidence process establishes more.