Uses of Interface
com.tnsai.agents.validation.Validator
Packages that use Validator
-
Uses of Validator in com.tnsai.agents.validation
Subinterfaces of Validator in com.tnsai.agents.validationModifier and TypeInterfaceDescriptioninterfaceMarker forValidators 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 intoAgentBuilder.withReachabilityChecks(true)(issue #85 phase 2a). -
Uses of Validator in com.tnsai.agents.validation.validators
Classes in com.tnsai.agents.validation.validators that implement ValidatorModifier and TypeClassDescriptionfinal classAGENT-V008 —@ActionSpecmethod names must be unique across every role attached to an agent.final classAGENT-V007 — Verify every@Capability-annotated interface implemented by an attached role can be fully reflected upon at build time.final classBuild-time syntax check for declarative@Contractexpressions (AGENT-V013).final classTwo-headed LLM capability validator.final classAGENT-V005 — opt-in reachability probe for the configuredLLMClient.final classAGENT-V002 — LLM should normally be present.final classAGENT-V011 — opt-in reachability probe for every MCP server URL referenced by an@MCPToolaction across the agent's roles.final classAGENT-V010 — opt-in reachability probe for the configuredMemoryStore.final classAGENT-V009 — Catches malformedResilienceconfigurations at build time.final classAGENT-V001 — at least oneRoleis required.final classAGENT-V012 — when an agent is configured withAgentBuilder.tenantId(...), every wired component that holds tenant-scoped state must opt into theTenantAwaremarker SPI.final classAGENT-V006 — at least one registered tool declares@Tool(requiresConfirmation = true)but the agent has noToolCallFilterconfigured to gate the call.