Assurance statement

What a result guarantees — and what it does not

HiQS AI Resolve is in unsigned beta. Read this before treating any output as an assurance.

What a result proves

Explicit identity

A resolved route names a specific harness revision, gateway revision, model revision, the serving binding that joins them, and the exact model identifier to put on the wire. No colloquial name survives into the answer.

Deterministic replay

The same snapshot bytes, the same materialized policy, the same request and the same evaluation time always produce the same decision, trace, and digests — in the browser, in Node, and on the command line.

Traceable reasoning

Every decision carries an ordered trace of the rules that fired, with references to the claims and policy clauses involved.

Declared provenance

Every claim states who recorded it, from which source category, when, and whether a human attested to it. "Source not supplied" and "Nobody has verified this claim" are shown as such.

What a result does not prove

Not a live capability check

Nothing is called. The resolver never contacts a provider, gateway, or model. A route means the catalog says this combination is supported — not that it worked just now.

Not signed

Beta artifacts are unsigned. No signature, no key, no chain of custody. Do not use them as a production trust root.

Not truth about vendors

Synthetic fixtures are labelled Synthetic and imported data is labelled Imported. Neither is a verified statement of fact about any real vendor.

Not a quality, price, or latency judgement

No language model, ranking heuristic, popularity signal, or newest-wins rule takes part in resolution.

Not complete

Absence from the catalog means nobody has recorded it — not that it does not exist.

Why a refusal is a valid answer

A refusal is the honest result when the evidence does not support exactly one route. Refusals are typed and specific — ambiguous alias, tied gateways, no serving binding, missing compatibility assertion, unverified claim, conflicting claims, explicit denial, insufficient pin, unsupported capability, not found, missing policy, invalid snapshot, unsupported feature — so the caller can act on them. A guess that looks like success is worse than a refusal that tells you what is missing.