output-verificationconditionalweight 1adapter 16 of 17Output Verification.
The Output Verification adapter aggregates verification-provider checks of the subject’s actual outputs: what share of sampled outputs pass, and how much of the subject’s operation the samples cover. Quality and coverage combine 70/30, so a high pass-rate without coverage cannot masquerade as verified reliability.
What it measures.
Output quality
Share of sampled outputs that pass verification checks.
Coverage
Proportion of the subject’s operation the sample represents.
Component keys.
output-verification.qualityQuality component — weighted 0.7 inside the adapter.
output-verification.coverageCoverage component — weighted 0.3 inside the adapter.
When it counts.
Conditional — counts when verification providers have checked the subject’s outputs.
When signals are missing.
Unverified subjects compute without this adapter rather than being penalized.
How it contributes.
{
"component": "output-verification.*",
"scale": "0-100",
"mode": "conditional",
"weight": 1,
"contribution": "component x 1 / total weight"
}The adapter’s components are averaged into the composite as a weighted mean: every contributing adapter’s component is multiplied by its weight, summed, and divided by the total weight of contributing adapters. The result is published as trustScores.total with a config version and timestamp so anyone can recompute it.
Questions about Output Verification.
How do quality and coverage combine in Output Verification?
Inside the adapter, output-verification.quality is weighted 0.7 and output-verification.coverage 0.3, so a high pass rate only scores well when the samples cover enough of the subject’s operation.
What does Output Verification verify?
Verification providers sample the subject’s real outputs and check them; the pass rate and sample coverage become components feeding the HCS-25 composite.