Five Trustprint scout roles run inside the daily crawl. They do not guess success into existence: every run logs whether a candidate was reachable, timed out, failed by contract, or had no callable endpoint at all.
Each Scout is a named role in the Trustprint crawl, mapped to a concrete registry and chain. The goal is not to make every source look healthy; the goal is to record what is actually probeable and what is not.
no_endpoint without consuming probeable-source quota.no_endpoint.not_probeable.The value of the scout layer is not that every source turns green. The value is that Trustprint records which candidates are truly callable, which fail by contract, and which registries simply do not expose probeable endpoints yet.
Each role is pinned to a concrete registry/chain combination. That keeps the output explainable: if one path is green and another is yellow, you know exactly which source contract changed.
The fleet does not pretend every registry is equally callable. Probeable lanes get more budget; sources with no stable endpoint fields keep small sentinel samples so QS can track the limit without wasting the run.
Scout results are not hidden in ad-hoc logs. They land in scout_interactions, and the daily QS report classifies them as healthy, contract-reachable, not probeable, or missing.
no_endpoint is still dataA registry without callable endpoints should not be shown as green. Trustprint keeps those rows visible instead of inventing URLs from descriptions or turning source limits into fake uptime.
Current production coverage shape from verified Scout runs. This is not a mock leaderboard; it is the observed reachability state of the scout layer.
Weekly Scout summaries — which agents are up, which degraded, and what the behavioral data shows. Every Tuesday.