Multi-Source Divergence Detection (MSDD) binds what a provider asserts and what is separately observed into the same structure, without merging them into a single reconciled value.
Signing a relayed claim does not upgrade it. It produces a signed relayed claim. MSDD keeps the two kinds of evidence apart on purpose, so a verifier can see that they disagree, and can see it without access to the execution environment and without a trusted execution environment.
Most attestation collapses everything into one field. The provider says which model served the request, that string gets signed, and the signature makes it look settled. All the signature proves is that the provider said it.
Model identity, build version, and configuration usually arrive as provider assertions. Nothing outside the provider corroborates them.
When asserted and observed values are reconciled into one number before signing, the disagreement is destroyed at exactly the moment it becomes interesting.
A trusted execution environment can raise the evidentiary grade, but it requires specific silicon, specific attestation profiles, and provider cooperation. Most inference does not run that way.
Two sources, carried side by side, bound to the same response, never averaged.
The provider's own statement is captured as an assertion and labelled as one. Its evidentiary basis travels with it, so nobody downstream mistakes a relayed value for a witnessed one.
A second value is separately observed outside the provider's own reporting path. It comes from a different source than the assertion, which is the entire reason it has corroborating value.
Both are bound into signed or linked structures covering the same response content. They remain separately addressable. A verifier reads both and compares them.
No trusted execution environment is required. Divergence is detected from the structure of the evidence rather than from a hardware root. A verifier needs the signed or linked structures. It does not need access to the execution environment, the provider's infrastructure, or an enclave attestation profile.
The output is not a verdict. It is a comparison that a third party can perform themselves and reach the same result.
| State | What it means | What it does not mean |
|---|---|---|
| Agreement | The asserted value and the separately observed value line up for this response. | It does not prove the assertion is true. It shows two sources are consistent. |
| Divergence | The two sources disagree for this response, and the disagreement is bound to specific content. | It does not by itself identify the cause, which may be substitution, misconfiguration, or a reporting error. |
| Single source only | Only an assertion is available and no separate observation was bound. | It is not a failure. It is an honest statement that corroboration is absent. |
Recording which values are witnessed and which are relayed, per field, inside the signature, is the design. Detectability after the fact is the guarantee that MSDD offers.
MSDD is one of four families filed on July 31, 2026, alongside Foretoken™, Stipryn™, and Bonded Performance Attestation (BPA). It is the route to raising the evidentiary grade of a provider-reported field without hardware attestation underneath it.
Commits to a streamed run before the first token and seals it at the close. Read
Fixes the required proof level before a request is transmitted. Read
Binds asserted and separately observed values without merging them.
Binds a declared performance budget and the actual distribution to the same response. Read
This is filed work and is not yet a public endpoint. The receipt discipline underneath it is live now: canonicalize, hash, sign, verify, and check it yourself in the browser.
Multi-Source Divergence Detection (MSDD). Patent pending, filed July 31, 2026. Binds provider-asserted and separately observed values without merging them, detectable by a verifier without a trusted execution environment. Hive Civilization Inc.