connectivityconditionalweight 1adapter 17 of 17Connectivity Probes.
The Connectivity adapter runs reachability checks against the specific endpoints a subject exposes — tool servers, APIs, and status pages. It complements the universal Availability adapter by scoring per-target reachability where a subject’s function depends on multiple reachable pieces.
What it measures.
Endpoint reachability
Successful connections to each exposed target.
Status-page health
Published status and incident signals where available.
Component keys.
connectivity.*Component family covering per-target reachability.
When it counts.
Conditional — counts for subjects exposing multiple probeable targets.
When signals are missing.
Subjects with no probeable targets beyond the primary endpoint omit this component.
How it contributes.
{
"component": "connectivity.*",
"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 Connectivity Probes.
How is Connectivity different from Availability?
Availability probes the subject’s primary endpoint universally; Connectivity conditionally scores per-target reachability for subjects that expose multiple tool servers or endpoints.
What happens when an endpoint goes down?
Failed targets lower the connectivity component for the window; a fully unreachable subject falls back to the availability adapter’s timeout or missing status.