Interface ReachabilityValidator

All Superinterfaces:
Validator
All Known Implementing Classes:
LLMHealthcheckValidator, MCPServerReachabilityValidator, MemoryStoreReachabilityValidator

public interface ReachabilityValidator extends Validator
Marker for Validators that perform out-of-process I/O (network call, disk write probe, MCP handshake, etc.) and therefore should run only when the user has explicitly opted into AgentBuilder.withReachabilityChecks(true) (issue #85 phase 2a).

Two reasons reachability validators are gated:

  • Side effects — a probe write to a memory store touches state; a chat probe to a real LLM costs money. Default build() must stay free of network calls.
  • Latency — bounded by per-probe timeout, but even healthy networks add seconds of build time the user may not want.

AgentBuilder.validateFully() runs all reachability validators in parallel, with each probe bounded by the timeout configured on the builder (default 5s). Sync (non-reachability) validators run first and unconditionally, regardless of the opt-in flag.

Since:
0.8.4 (issue #85 phase 2a)
  • Method Summary

    Methods inherited from interface com.tnsai.agents.validation.Validator

    id, validate