Executive summary
embabel/embabel-agent falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 67 out of 100 and is rated Adequate, and 33 of its 35 critical findings are security problems in the build pipeline.
Production Readiness, at 57, is the weakest lens and counts most in the score. The best first step is protecting outgoing calls with timeouts, worth about 5 points. Stopping the five pipeline steps that hand secrets to unpinned tools comes next, worth about 2 points. Raising Production Readiness to 70 would lift the score to about 73.
Twenty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eight secrets can leak from the build pipeline, and two pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version, limiting each secret to its own step and passing outside input through environment variables would close these risks. The inner part of the code that depends on an outer part needs turning around so it points inward.
The product code is 115,995 lines, about €610,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Production Readiness rose from 57 to 70, the lowest score rated Strong, the score would rise from 67 to about 73.
New since the last survey: 152 findings
- Cognitive Complexity · LlmOptions.copyDefault (cognitive 24) embabel-agent-common/embabel-agent-ai/src/main/kotlin/com/embabel/common/ai/model/LlmOptions.kt
- Code Duplication · Near-duplicate member pair (84 shared lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/progressive/UnfoldingTool.kt
- Code Duplication · Near-duplicate member pair (42 shared lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt
- Code Duplication · Edited copy of a member (50 corresponding lines) embabel-agent-autoconfigure/embabel-agent-platform-autoconfigure/src/main/java/com/embabel/agent/autoconfigure/platform/QuiteMcpClientAutoConfiguration.java
- Code Duplication · Edited copy of a member (70 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/agentic/playbook/PlaybookTool.kt
- Code Duplication · Edited copy of a member (62 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/plan/utility/HybridUtilityPlanner.kt
- Code Duplication · Edited copy of a member (37 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/AgentMetadataReader.kt
- Code Duplication · Edited copy of a member (53 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/streaming/StreamingChatClientOperations.kt
- Code Duplication · Edited copies of one member (4 members, 47+ corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-bedrock-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/bedrock/BedrockModelsConfig.kt
- Code Duplication · Edited copy of a member (45 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/dsl/TypedAgentScopeBuilder.kt
- Code Duplication · Edited copy of a member (35 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DefaultActionMethodManager.kt
- Code Duplication · Edited copy of a member (35 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-dashscope-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/dashscope/DashScopeModelsConfig.kt
- Code Duplication · Edited copy of a member (37 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/Blackboard.kt
- Code Duplication · Edited copy of a member (40 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/agent/AgentTool.kt
- Code Duplication · Edited copy of a member (38 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/TypeBasedInputSchema.kt
- Code Duplication · Edited copies of one member (3 members, 27+ corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/blackboard/BlackboardTools.kt
- Code Duplication · Edited copy of a member (28 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-oci-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/ocigenai/OciGenAiChatModel.kt
- Code Duplication · Edited copy of a member (31 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/ActionMethodArgumentResolver.kt
- Code Duplication · Edited copies of one member (3 members, 28+ corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-google-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/googlegenai/GoogleGenAiModelLoader.kt
- Code Duplication · Edited copy of a member (22 corresponding lines) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/ingestion/InMemoryContentChunker.kt
- Code Duplication · Edited copy of a member (26 corresponding lines) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/support/AssetViewSearchOperations.kt
- Code Duplication · Edited copy of a member (25 corresponding lines) embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt
- Code Duplication · Edited copy of a member (32 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/agent/DefaultProcessCallbackTools.kt
- Code Duplication · Edited copy of a member (24 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-google-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/googlegenai/GoogleGenAiModelsConfig.kt
- Code Duplication · Edited copy of a member (20 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DefaultActionMethodManager.kt
- Code Duplication · Edited copies of one member (3 members, 30+ corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-anthropic-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/anthropic/AnthropicModelsConfig.kt
- Code Duplication · Edited copy of a member (18 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-oci-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/ocigenai/OciGenAiChatModel.kt
- Code Duplication · Edited copy of a member (21 corresponding lines) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/tools/CoreSearchTools.kt
- Code Duplication · Edited copies of one member (4 members, 24+ corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/blackboard/BlackboardTools.kt
- Code Duplication · Edited copy of a member (20 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-minimax-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/minimax/MiniMaxModelsConfig.kt
- Code Duplication · Edited copy of a member (27 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-google-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/googlegenai/GoogleGenAiModelsConfig.kt
- Code Duplication · Edited copy of a member (15 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DefaultActionMethodManager.kt
- Code Duplication · Edited copy of a member (21 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-byok-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/byok/CredentialEndpointConfig.kt
- Code Duplication · Edited copy of a member (21 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt
- Code Duplication · Edited copy of a member (19 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/support/BranchingAction.kt
- Code Duplication · Edited copy of a member (23 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/ArtifactSinkingTool.kt
- Code Duplication · Edited copy of a member (12 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/dsl/TypedAgentScopeBuilder.kt
- Code Duplication · Edited copy of a member (17 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt
- Code Duplication · Edited copy of a member (25 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/process/AgentProcessTools.kt
- Code Duplication · Edited copy of a member (18 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/common/ai/model/local/LocalModelRoleResolver.kt
- Code Duplication · Edited copy of a member (15 corresponding lines) embabel-agent-observability/src/main/java/com/embabel/agent/observability/tracing/EmbabelLlmObservationConvention.java
- Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/support/InMemoryNamedEntityDataRepository.kt
- Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/client/spi/SpringRestClientA2AHttpClient.kt
- Code Duplication · Edited copy of a member (17 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/guardrails/llmOperationGuardRails.kt
- Code Duplication · Edited copy of a member (22 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/chat/support/console/ChatConsole.kt
- Code Duplication · Edited copy of a member (18 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/common/ai/model/ConfigurableEmbeddingRoleResolver.kt
- Code Duplication · Edited copy of a member (10 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-oci-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/ocigenai/OciGenAiChatModel.kt
- Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/server/support/AutonomyA2ARequestHandler.kt
- Code Duplication · Edited copy of a member (10 corresponding lines) embabel-agent-autoconfigure/embabel-agent-observability-autoconfigure/src/main/java/com/embabel/agent/autoconfigure/observability/HttpRequestObservationFilter.java
- Code Duplication · Edited copy of a member (16 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/Condition.kt
- Code Duplication · Edited copy of a member (10 corresponding lines) embabel-agent-openai/src/main/kotlin/com/embabel/agent/openai/OpenAiCompatibleModelFactory.kt
- Code Duplication · Edited copy of a member (18 corresponding lines) embabel-agent-jdbc/src/main/kotlin/com/embabel/agent/jdbc/JdbcAgentProcessSnapshotStore.kt
- Code Duplication · Edited copy of a member (9 corresponding lines) embabel-agent-observability/src/main/java/com/embabel/agent/observability/tracing/EmbabelSpanEventListener.java
- Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/support/GitHubSkillDefinitionLoader.kt
- Code Duplication · Edited copy of a member (9 corresponding lines) embabel-agent-observability/src/main/java/com/embabel/agent/observability/tracing/EmbabelSpanEventListener.java
- Code Duplication · Edited copy of a member (14 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/ActionContext.kt
- Code Duplication · Edited copy of a member (26 corresponding lines) embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/async/McpAsyncPromptFactory.kt
- Code Duplication · Edited copy of a member (10 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/JvmType.kt
- Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-minimax-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/minimax/MiniMaxModelsConfig.kt
- Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/ReplanningToolFactory.kt
- Code Duplication · Edited copy of a member (9 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-oci-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/ocigenai/OciGenAiChatModel.kt
- Code Duplication · Edited copy of a member (15 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-bedrock-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/bedrock/BedrockModelsConfig.kt
- Code Duplication · Edited copy of a member (13 corresponding lines) embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/async/McpAsyncServerStrategy.kt
- Code Duplication · Edited copies of one member (5 members, 10+ corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/messagePromptBuilders.kt
- Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-bedrock-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/bedrock/BedrockModelsConfig.kt
- Code Duplication · Edited copy of a member (9 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/workflow/control/ScatterGatherBuilder.kt
- Code Duplication · Edited copy of a member (13 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/loop/streaming/StreamingToolLoop.kt
- Code Duplication · Edited copy of a member (6 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/persistence/BlackboardPersistence.kt
- Code Duplication · Edited copy of a member (5 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/MultimodalContent.kt
- Code Duplication · Edited copy of a member (3 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-cloudflare-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/cloudflare/CloudflareModelsConfig.kt
- Code Duplication · Edited copy of a member (15 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/InMemoryBlackboard.kt
- Code Duplication · Edited copy of a member (8 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/agentic/playbook/PlaybookTool.kt
- Code Duplication · Edited copy of a member (9 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/channel/OutputChannel.kt
- Code Duplication · Edited copy of a member (7 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/support/DelegatingCreating.kt
- Code Duplication · Duplicated block (56 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/progressive/UnfoldingTool.kt
- Code Duplication · Duplicated block (29 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt
- Code Duplication · Duplicated block (24–28 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/streaming/StreamingChatClientOperations.kt
- Code Duplication · Duplicated block (27 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/ConcurrentAgentProcess.kt
- Code Duplication · Duplicated block (22–23 lines × 4) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/AbstractLlmOperations.kt
- Code Duplication · Duplicated block (23 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt
- Code Duplication · Duplicated block (20–22 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt
- Code Duplication · Duplicated block (18–20 lines × 3) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt
- Code Duplication · Duplicated block (20 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/workflow/loop/RepeatUntil.kt
- Code Duplication · Duplicated block (19–20 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/ChatClientLlmOperations.kt
- Code Duplication · Duplicated block (19 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/progressive/UnfoldingTool.kt
- Code Duplication · Duplicated block (17–19 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/file/FileReadTools.kt
- Code Duplication · Duplicated block (18 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt
- Code Duplication · Duplicated block (18 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/blackboard/BlackboardTools.kt
- Code Duplication · Duplicated block (16–17 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/AgentMetadataReader.kt
- Code Duplication · Duplicated block (17 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt
- Code Duplication · Duplicated block (16 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/support/OperationContextDelegate.kt
- Code Duplication · Duplicated block (14–16 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/Blackboard.kt
- Code Duplication · Duplicated block (16 lines × 2) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/support/AssetViewSearchOperations.kt
- Code Duplication · Duplicated block (15 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt
- Code Duplication · Duplicated block (14 lines × 4) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt
- Code Duplication · Duplicated block (13–14 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/AgentMetadataReader.kt
- Code Duplication · Duplicated block (14 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt
- Code Duplication · Duplicated block (14 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-minimax-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/minimax/MiniMaxModelsConfig.kt
- Code Duplication · Duplicated block (12–13 lines × 3) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt
- Code Duplication · Duplicated block (11–13 lines × 3) embabel-agent-autoconfigure/models/embabel-agent-google-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/googlegenai/GoogleGenAiModelLoader.kt
Fixed since the last survey: 66 findings
- Code Duplication · Near-duplicate member pair (83 shared lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/progressive/UnfoldingTool.kt
- Code Duplication · Near-duplicate member pair (42 shared lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt
- Code Duplication · Duplicated block (56 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/progressive/UnfoldingTool.kt
- Code Duplication · Duplicated block (28 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt
- Code Duplication · Duplicated block (24–28 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/streaming/StreamingChatClientOperations.kt
- Code Duplication · Duplicated block (25–27 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/ConcurrentAgentProcess.kt
- Code Duplication · Duplicated block (23 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt
- Code Duplication · Duplicated block (20–21 lines × 4) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/AbstractLlmOperations.kt
- Code Duplication · Duplicated block (18–20 lines × 3) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt
- Code Duplication · Duplicated block (20 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt
- Code Duplication · Duplicated block (19–20 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/ChatClientLlmOperations.kt
- Code Duplication · Duplicated block (17–19 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/file/FileReadTools.kt
- Code Duplication · Duplicated block (18 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/blackboard/BlackboardTools.kt
- Code Duplication · Duplicated block (16–17 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/AgentMetadataReader.kt
- Code Duplication · Duplicated block (17 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt
- Code Duplication · Duplicated block (16 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/support/OperationContextDelegate.kt
- Code Duplication · Duplicated block (14–16 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/Blackboard.kt
- Code Duplication · Duplicated block (16 lines × 2) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/support/AssetViewSearchOperations.kt
- Code Duplication · Duplicated block (15 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt
- Code Duplication · Duplicated block (13–14 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/AgentMetadataReader.kt
- Code Duplication · Duplicated block (14 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt
- Code Duplication · Duplicated block (14 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-minimax-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/minimax/MiniMaxModelsConfig.kt
- Code Duplication · Duplicated block (11–13 lines × 3) embabel-agent-autoconfigure/models/embabel-agent-google-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/googlegenai/GoogleGenAiModelLoader.kt
- Code Duplication · Duplicated block (12–13 lines × 2) embabel-agent-rag/embabel-agent-rag-tika/src/main/kotlin/com/embabel/agent/rag/ingestion/HtmlContentParser.kt
- Code Duplication · Duplicated block (10–12 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/blackboard/BlackboardTools.kt
- Code Duplication · Duplicated block (10–11 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/agent/AgentTool.kt
- Code Duplication · Duplicated block (11 lines × 2) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/ingestion/InMemoryContentChunker.kt
- Code Duplication · Duplicated block (10 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt
- Code Duplication · Duplicated block (10 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt
- Code Duplication · Duplicated block (10 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/agentic/playbook/PlaybookToolInjectionStrategy.kt
- Code Duplication · Duplicated block (10 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/guardrails/llmOperationGuardRails.kt
- Code Duplication · Duplicated block (10 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-lmstudio-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/lmstudio/LmStudioModelsConfig.kt
- Code Duplication · Duplicated block (9 lines × 2) embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/server/support/AutonomyA2ARequestHandler.kt
- Code Duplication · Duplicated block (9 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/progressive/UnfoldingTool.kt
- Code Duplication · Duplicated block (8–9 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/ChatClientLlmOperations.kt
- Code Duplication · Duplicated block (8 lines × 4) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/NamedEntityDataRepository.kt
- Code Duplication · Duplicated block (8 lines × 3) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/ingestion/InMemoryContentChunker.kt
- Code Duplication · Duplicated block (7 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-byok-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/byok/CredentialEndpointConfig.kt
- Code Duplication · Duplicated block (5 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DefaultActionMethodManager.kt
- Code Duplication · Duplicated block (5 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-google-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/googlegenai/GoogleGenAiModelsConfig.kt
- Code Duplication · Duplicated block (6 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/MultimodalContent.kt
- Code Duplication · Duplicated block (8 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/AgenticTool.kt
- Code Duplication · Duplicated block (8 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/AgenticTool.kt
- Code Duplication · Duplicated block (5 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/AgentProcess.kt
- Code Duplication · Duplicated block (7 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/streaming/StreamingChatClientOperations.kt
- Code Duplication · Duplicated block (12 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/streaming/StreamingChatClientOperations.kt
- Code Duplication · Duplicated block (10 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/streaming/StreamingChatClientOperations.kt
- Code Duplication · Duplicated block (7 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-anthropic-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/anthropic/AnthropicModelLoader.kt
- Code Duplication · Duplicated block (5 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-cloudflare-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/cloudflare/CloudflareModelsConfig.kt
- Code Duplication · Duplicated block (12 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-gemini-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/gemini/GeminiModelLoader.kt
- Code Duplication · Duplicated block (18 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/progressive/UnfoldingTool.kt
- Code Duplication · Duplicated block (17 lines × 2) embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/support/GitHubSkillDefinitionLoader.kt
- Code Duplication · Duplicated block (16 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DefaultActionMethodManager.kt
- Code Duplication · Duplicated block (13 lines × 3) embabel-agent-autoconfigure/models/embabel-agent-anthropic-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/anthropic/AnthropicModelsConfig.kt
- Code Duplication · Duplicated block (12 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-google-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/googlegenai/GoogleGenAiModelsConfig.kt
- Code Duplication · Duplicated block (11 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-dashscope-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/dashscope/DashScopeModelsConfig.kt
- Code Duplication · Duplicated block (9 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-dashscope-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/dashscope/DashScopeModelsConfig.kt
- Code Duplication · Duplicated block (9 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-cloudflare-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/cloudflare/CloudflareModelsConfig.kt
- Churn × Complexity Hotspots · Hotspot: embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/AbstractAgentProcess.kt embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/AbstractAgentProcess.kt
- Churn × Complexity Hotspots · Hotspot: embabel-agent-observability/src/main/java/com/embabel/agent/observability/metrics/EmbabelMetricsEventListener.java embabel-agent-observability/src/main/java/com/embabel/agent/observability/metrics/EmbabelMetricsEventListener.java
- Churn × Complexity Hotspots · Repeated repair: embabel-agent-autoconfigure/embabel-agent-observability-autoconfigure/src/main/java/com/embabel/agent/autoconfigure/observability/ObservabilityAutoConfiguration.java embabel-agent-autoconfigure/embabel-agent-observability-autoconfigure/src/main/java/com/embabel/agent/autoconfigure/observability/ObservabilityAutoConfiguration.java
- Explicit Debt · TodoComment embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/server/support/AutonomyA2ARequestHandler.kt
- Explicit Debt · TodoComment embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/server/support/AutonomyA2ARequestHandler.kt
- Explicit Debt · TodoComment embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/server/support/AutonomyA2ARequestHandler.kt
- Secrets (history) · High secret: WD-SECRET-0005 embabel-agent-api/docker-compose.yml
- Secrets (history) · High secret: WD-SECRET-0005 embabel-agent-api/src/main/resources/application-neo.yml
Rebuild cost: about €610,000 · Estimate
| Cost to rebuild | €200,000 to €1,000,000, for 3,353 to 10,637 hours of work, about 4.2 person-years for 2 to 8 engineers |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 67. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Large: 115,995 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 agent.spi.common | 2 common.ai.prompt | 3 common.util | 4 plan | 5 agent.api.tool.Tool | 6 agent.core.internal | 7 common.ai.decision | 8 plan.common.condition | 9 agent.api.tool.agentic | 10 common.ai.classification | 11 agent.api.common.support | 12 agent.tools.file | 13 agent.api.reference | 14 chat | 15 agent.api.tool.callback | 16 agent.spi.loop | 17 agent.spi | 18 common.ai.model | 19 agent.api.tool | 20 agent.spi.support.decision | 21 common.ai.autoconfig | 22 agent.skills.script | 23 agent.spi.config.spring | 24 agent.api.common.autonomy | 25 agent.spi.support | 26 agent.core.support | 27 agent.api.event | 28 agent.core | 29 agent.api.channel | 30 agent.api.dsl | 31 agent.api.common | 32 agent.api.annotation.support | 33 agent.rag.tools | 34 agent.shell | 35 agent.spi.support.springai | 36 chat.agent | 37 agent.openai | 38 agent.rag.service | 39 agent.rag.model | 40 agent.rag.ingestion |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 agent.spi.common | ||||||||||||||||||||||||||||||||||||||||
| 2 common.ai.prompt | ||||||||||||||||||||||||||||||||||||||||
| 3 common.util | ||||||||||||||||||||||||||||||||||||||||
| 4 plan | ||||||||||||||||||||||||||||||||||||||||
| 5 agent.api.tool.Tool | 10 | |||||||||||||||||||||||||||||||||||||||
| 6 agent.core.internal | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 7 common.ai.decision | 8 | 2 | ||||||||||||||||||||||||||||||||||||||
| 8 plan.common.condition | 11 | |||||||||||||||||||||||||||||||||||||||
| 9 agent.api.tool.agentic | 7 | 2 | 5 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 10 common.ai.classification | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 11 agent.api.common.support | 3 | 5 | 2 | 5 | 12 | 9 | 6 | 3 | 11 | 5 | 35 | 17 | ||||||||||||||||||||||||||||
| 12 agent.tools.file | 5 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 13 agent.api.reference | 1 | 2 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 14 chat | 1 | 7 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 15 agent.api.tool.callback | 3 | 12 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 16 agent.spi.loop | 1 | 6 | 6 | 1 | 15 | 3 | 1 | |||||||||||||||||||||||||||||||||
| 17 agent.spi | 2 | 4 | 1 | 1 | 5 | 1 | 4 | 10 | ||||||||||||||||||||||||||||||||
| 18 common.ai.model | 3 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 19 agent.api.tool | 1 | 59 | 1 | 9 | ||||||||||||||||||||||||||||||||||||
| 20 agent.spi.support.decision | 1 | 1 | 28 | 21 | 4 | 1 | 6 | |||||||||||||||||||||||||||||||||
| 21 common.ai.autoconfig | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 agent.skills.script | 2 | 5 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 23 agent.spi.config.spring | 1 | 1 | 3 | 5 | 3 | 1 | 2 | 2 | 10 | 1 | 8 | 1 | ||||||||||||||||||||||||||||
| 24 agent.api.common.autonomy | 2 | 1 | 1 | 2 | 20 | |||||||||||||||||||||||||||||||||||
| 25 agent.spi.support | 2 | 1 | 4 | 4 | 18 | 3 | 1 | 6 | 1 | 11 | 17 | 10 | 26 | 3 | 1 | 4 | 9 | 31 | 1 | 7 | 1 | |||||||||||||||||||
| 26 agent.core.support | 3 | 1 | 7 | 2 | 1 | 6 | 3 | 2 | 9 | 5 | 8 | 1 | 2 | 52 | 1 | 11 | ||||||||||||||||||||||||
| 27 agent.api.event | 5 | 1 | 5 | 1 | 52 | |||||||||||||||||||||||||||||||||||
| 28 agent.core | 1 | 5 | 1 | 12 | 2 | 6 | 6 | 4 | 2 | 14 | ||||||||||||||||||||||||||||||
| 29 agent.api.channel | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 agent.api.dsl | 3 | 1 | 1 | 1 | 1 | 1 | 15 | 11 | ||||||||||||||||||||||||||||||||
| 31 agent.api.common | 9 | 1 | 1 | 2 | 1 | 2 | 1 | 7 | 3 | 1 | 4 | 14 | 5 | 1 | 1 | 4 | 50 | 2 | 2 | |||||||||||||||||||||
| 32 agent.api.annotation.support | 1 | 5 | 5 | 1 | 30 | 12 | ||||||||||||||||||||||||||||||||||
| 33 agent.rag.tools | 2 | 4 | 3 | 1 | 5 | 1 | 23 | 7 | ||||||||||||||||||||||||||||||||
| 34 agent.shell | 1 | 2 | 1 | 1 | 6 | 6 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 35 agent.spi.support.springai | 1 | 1 | 5 | 3 | 2 | 8 | 4 | 10 | 9 | 3 | 6 | 3 | 4 | 4 | 1 | |||||||||||||||||||||||||
| 36 chat.agent | 12 | 1 | 1 | 1 | 9 | 3 | 2 | |||||||||||||||||||||||||||||||||
| 37 agent.openai | 1 | 17 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 agent.rag.service | 2 | 2 | 2 | 1 | 11 | 2 | ||||||||||||||||||||||||||||||||||
| 39 agent.rag.model | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 agent.rag.ingestion | 2 | 22 |
5→19 agent.api.tool.Tool uses agent.api.tool part of a loop✕
- Connections
- 10 pairs of types, where a type in agent.api.tool.Tool uses a type in agent.api.tool.
- The types involved
com.embabel.agent.api.tool.Tool.Companion→com.embabel.agent.api.tool.ArtifactSinkcom.embabel.agent.api.tool.Tool.Companion→com.embabel.agent.api.tool.ArtifactSinkFactorycom.embabel.agent.api.tool.Tool.Companion→com.embabel.agent.api.tool.DelegatingToolcom.embabel.agent.api.tool.Tool.Companion→com.embabel.agent.api.tool.MethodToolFactorycom.embabel.agent.api.tool.Tool.Companion→com.embabel.agent.api.tool.ReplanContextcom.embabel.agent.api.tool.Tool.Companion→com.embabel.agent.api.tool.ReplanDecisioncom.embabel.agent.api.tool.Tool.Companion→com.embabel.agent.api.tool.ReplanningToolFactorycom.embabel.agent.api.tool.Tool.Companion→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.tool.Tool.Companion→com.embabel.agent.api.tool.TypedToolFactorycom.embabel.agent.api.tool.Tool.ContextAwareFunction→com.embabel.agent.api.tool.ToolCallContext
- Direction
- agent.api.tool.Tool uses agent.api.tool, so a change to agent.api.tool can break agent.api.tool.Tool, while a change to agent.api.tool.Tool can't break agent.api.tool.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→14 agent.core.internal uses chat part of a loop✕
- Connections
- 1 pair of types, where a type in agent.core.internal uses a type in chat.
- The types involved
com.embabel.agent.core.internal.LlmOperations→com.embabel.chat.Message
- Direction
- agent.core.internal uses chat, so a change to chat can break agent.core.internal, while a change to agent.core.internal can't break chat.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→18 agent.core.internal uses common.ai.model part of a loop✕
- Connections
- 1 pair of types, where a type in agent.core.internal uses a type in common.ai.model.
- The types involved
com.embabel.agent.core.internal.LlmOperations→com.embabel.common.ai.model.LlmOptions
- Direction
- agent.core.internal uses common.ai.model, so a change to common.ai.model can break agent.core.internal, while a change to agent.core.internal can't break common.ai.model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→26 agent.core.internal uses agent.core.support part of a loop✕
- Connections
- 1 pair of types, where a type in agent.core.internal uses a type in agent.core.support.
- The types involved
com.embabel.agent.core.internal.LlmOperations→com.embabel.agent.core.support.LlmInteraction
- Direction
- agent.core.internal uses agent.core.support, so a change to agent.core.support can break agent.core.internal, while a change to agent.core.internal can't break agent.core.support.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→27 agent.core.internal uses agent.api.event part of a loop✕
- Connections
- 1 pair of types, where a type in agent.core.internal uses a type in agent.api.event.
- The types involved
com.embabel.agent.core.internal.LlmOperations→com.embabel.agent.api.event.LlmRequestEvent
- Direction
- agent.core.internal uses agent.api.event, so a change to agent.api.event can break agent.core.internal, while a change to agent.core.internal can't break agent.api.event.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→28 agent.core.internal uses agent.core part of a loop✕
- Connections
- 2 pairs of types, where a type in agent.core.internal uses a type in agent.core.
- The types involved
com.embabel.agent.core.internal.LlmOperations→com.embabel.agent.core.Actioncom.embabel.agent.core.internal.LlmOperations→com.embabel.agent.core.AgentProcess
- Direction
- agent.core.internal uses agent.core, so a change to agent.core can break agent.core.internal, while a change to agent.core.internal can't break agent.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→10 common.ai.decision uses common.ai.classification part of a loop✕
- Connections
- 8 pairs of types, where a type in common.ai.decision uses a type in common.ai.classification.
- The types involved
com.embabel.common.ai.decision.AnswerRules→com.embabel.common.ai.classification.FailureReasoncom.embabel.common.ai.decision.ChoiceQuestionSpec→com.embabel.common.ai.classification.Categorycom.embabel.common.ai.decision.ChoiceQuestionSpec→com.embabel.common.ai.classification.ClassificationResultcom.embabel.common.ai.decision.DecisionResponse→com.embabel.common.ai.classification.FailureReasoncom.embabel.common.ai.decision.DecisionService→com.embabel.common.ai.classification.ClassificationServicecom.embabel.common.ai.decision.DecisionServiceMetadata→com.embabel.common.ai.classification.ClassificationServiceMetadatacom.embabel.common.ai.decision.OutcomeRules→com.embabel.common.ai.classification.Categorycom.embabel.common.ai.decision.OutcomeRules→com.embabel.common.ai.classification.ClassificationResult
- Direction
- common.ai.decision uses common.ai.classification, so a change to common.ai.classification can break common.ai.decision, while a change to common.ai.decision can't break common.ai.classification.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→18 common.ai.decision uses common.ai.model part of a loop✕
- Connections
- 2 pairs of types, where a type in common.ai.decision uses a type in common.ai.model.
- The types involved
com.embabel.common.ai.decision.DecisionService→com.embabel.common.ai.model.ModelTypecom.embabel.common.ai.decision.DecisionServiceMetadata→com.embabel.common.ai.model.ModelType
- Direction
- common.ai.decision uses common.ai.model, so a change to common.ai.model can break common.ai.decision, while a change to common.ai.decision can't break common.ai.model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→4 plan.common.condition uses plan✕
- Connections
- 11 pairs of types, where a type in plan.common.condition uses a type in plan.
- The types involved
com.embabel.plan.common.condition.ConditionAction→com.embabel.plan.Actioncom.embabel.plan.common.condition.ConditionGoal→com.embabel.plan.Goalcom.embabel.plan.common.condition.ConditionPlan→com.embabel.plan.Actioncom.embabel.plan.common.condition.ConditionPlan→com.embabel.plan.Goalcom.embabel.plan.common.condition.ConditionPlan→com.embabel.plan.Plancom.embabel.plan.common.condition.ConditionPlanner→com.embabel.plan.Plannercom.embabel.plan.common.condition.ConditionPlanningSystem→com.embabel.plan.PlanningSystemcom.embabel.plan.common.condition.ConditionStep→com.embabel.plan.Stepcom.embabel.plan.common.condition.ConditionWorldState→com.embabel.plan.WorldStatecom.embabel.plan.common.condition.SimpleConditionAction→com.embabel.plan.WorldStatecom.embabel.plan.common.condition.SimpleConditionGoal→com.embabel.plan.WorldState
- Direction
- plan.common.condition uses plan, so a change to plan can break plan.common.condition, while a change to plan.common.condition can't break plan.
- Position
- Below the diagonal: plan.common.condition uses a module listed above it, which is the healthy direction.
9→5 agent.api.tool.agentic uses agent.api.tool.Tool✕
- Connections
- 7 pairs of types, where a type in agent.api.tool.agentic uses a type in agent.api.tool.Tool.
- The types involved
com.embabel.agent.api.tool.agentic.AgenticTool→com.embabel.agent.api.tool.Tool.Parametercom.embabel.agent.api.tool.agentic.AgenticToolSupport→com.embabel.agent.api.tool.Tool.Resultcom.embabel.agent.api.tool.agentic.DomainBoundTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.api.tool.agentic.DomainBoundTool→com.embabel.agent.api.tool.Tool.InputSchemacom.embabel.agent.api.tool.agentic.DomainBoundTool→com.embabel.agent.api.tool.Tool.Metadatacom.embabel.agent.api.tool.agentic.DomainBoundTool→com.embabel.agent.api.tool.Tool.Resultcom.embabel.agent.api.tool.agentic.DomainToolFactory→com.embabel.agent.api.tool.Tool.Definition
- Direction
- agent.api.tool.agentic uses agent.api.tool.Tool, so a change to agent.api.tool.Tool can break agent.api.tool.agentic, while a change to agent.api.tool.agentic can't break agent.api.tool.Tool.
- Position
- Below the diagonal: agent.api.tool.agentic uses a module listed above it, which is the healthy direction.
9→18 agent.api.tool.agentic uses common.ai.model part of a loop✕
- Connections
- 2 pairs of types, where a type in agent.api.tool.agentic uses a type in common.ai.model.
- The types involved
com.embabel.agent.api.tool.agentic.AgenticExecutionConfig→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.api.tool.agentic.AgenticTool→com.embabel.common.ai.model.LlmOptions
- Direction
- agent.api.tool.agentic uses common.ai.model, so a change to common.ai.model can break agent.api.tool.agentic, while a change to agent.api.tool.agentic can't break common.ai.model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→19 agent.api.tool.agentic uses agent.api.tool part of a loop✕
- Connections
- 5 pairs of types, where a type in agent.api.tool.agentic uses a type in agent.api.tool.
- The types involved
com.embabel.agent.api.tool.agentic.AgenticExecutionConfig→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.tool.agentic.AgenticTool→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.tool.agentic.DomainBoundTool→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.tool.agentic.DomainToolFactory→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.tool.agentic.DomainToolTracker→com.embabel.agent.api.tool.Tool
- Direction
- agent.api.tool.agentic uses agent.api.tool, so a change to agent.api.tool can break agent.api.tool.agentic, while a change to agent.api.tool.agentic can't break agent.api.tool.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→28 agent.api.tool.agentic uses agent.core part of a loop✕
- Connections
- 3 pairs of types, where a type in agent.api.tool.agentic uses a type in agent.core.
- The types involved
com.embabel.agent.api.tool.agentic.AgenticToolSupport→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.tool.agentic.DomainToolPredicate→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.tool.agentic.DomainToolTracker→com.embabel.agent.core.AgentProcess
- Direction
- agent.api.tool.agentic uses agent.core, so a change to agent.core can break agent.api.tool.agentic, while a change to agent.api.tool.agentic can't break agent.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→31 agent.api.tool.agentic uses agent.api.common part of a loop✕
- Connections
- 1 pair of types, where a type in agent.api.tool.agentic uses a type in agent.api.common.
- The types involved
com.embabel.agent.api.tool.agentic.AgenticSystemPromptCreator→com.embabel.agent.api.common.ExecutingOperationContext
- Direction
- agent.api.tool.agentic uses agent.api.common, so a change to agent.api.common can break agent.api.tool.agentic, while a change to agent.api.tool.agentic can't break agent.api.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→7 common.ai.classification uses common.ai.decision✕
- Connections
- 3 pairs of types, where a type in common.ai.classification uses a type in common.ai.decision.
- The types involved
com.embabel.common.ai.classification.ClassificationRequest→com.embabel.common.ai.decision.DecisionRequestcom.embabel.common.ai.classification.ClassificationSpec→com.embabel.common.ai.decision.ChoiceQuestionSpeccom.embabel.common.ai.classification.ClassificationSpec→com.embabel.common.ai.decision.DecisionSpec
- Direction
- common.ai.classification uses common.ai.decision, so a change to common.ai.decision can break common.ai.classification, while a change to common.ai.classification can't break common.ai.decision.
- Position
- Below the diagonal: common.ai.classification uses a module listed above it, which is the healthy direction.
10→18 common.ai.classification uses common.ai.model part of a loop✕
- Connections
- 2 pairs of types, where a type in common.ai.classification uses a type in common.ai.model.
- The types involved
com.embabel.common.ai.classification.ClassificationServiceMetadata→com.embabel.common.ai.model.ModelMetadatacom.embabel.common.ai.classification.ClassificationServiceMetadata→com.embabel.common.ai.model.ModelType
- Direction
- common.ai.classification uses common.ai.model, so a change to common.ai.model can break common.ai.classification, while a change to common.ai.classification can't break common.ai.model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→2 agent.api.common.support uses common.ai.prompt✕
- Connections
- 3 pairs of types, where a type in agent.api.common.support uses a type in common.ai.prompt.
- The types involved
com.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.common.ai.prompt.PromptContributorcom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.common.ai.prompt.PromptContributorcom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.common.ai.prompt.PromptContributor
- Direction
- agent.api.common.support uses common.ai.prompt, so a change to common.ai.prompt can break agent.api.common.support, while a change to agent.api.common.support can't break common.ai.prompt.
- Position
- Below the diagonal: agent.api.common.support uses a module listed above it, which is the healthy direction.
11→4 agent.api.common.support uses plan✕
- Connections
- 5 pairs of types, where a type in agent.api.common.support uses a type in plan.
- The types involved
com.embabel.agent.api.common.support.BranchingAction→com.embabel.plan.WorldStatecom.embabel.agent.api.common.support.ConsumerAction→com.embabel.plan.WorldStatecom.embabel.agent.api.common.support.MultiTransformationAction→com.embabel.plan.WorldStatecom.embabel.agent.api.common.support.SupplierAction→com.embabel.plan.WorldStatecom.embabel.agent.api.common.support.TransformationAction→com.embabel.plan.WorldState
- Direction
- agent.api.common.support uses plan, so a change to plan can break agent.api.common.support, while a change to agent.api.common.support can't break plan.
- Position
- Below the diagonal: agent.api.common.support uses a module listed above it, which is the healthy direction.
11→6 agent.api.common.support uses agent.core.internal✕
- Connections
- 2 pairs of types, where a type in agent.api.common.support uses a type in agent.core.internal.
- The types involved
com.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.core.internal.LlmOperationscom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.core.internal.LlmOperations
- Direction
- agent.api.common.support uses agent.core.internal, so a change to agent.core.internal can break agent.api.common.support, while a change to agent.api.common.support can't break agent.core.internal.
- Position
- Below the diagonal: agent.api.common.support uses a module listed above it, which is the healthy direction.
11→9 agent.api.common.support uses agent.api.tool.agentic✕
- Connections
- 5 pairs of types, where a type in agent.api.common.support uses a type in agent.api.tool.agentic.
- The types involved
com.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.agent.api.tool.agentic.DomainToolPredicatecom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.api.tool.agentic.DomainToolPredicatecom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.api.tool.agentic.DomainToolSourcecom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.api.tool.agentic.DomainToolPredicatecom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.api.tool.agentic.DomainToolSource
- Direction
- agent.api.common.support uses agent.api.tool.agentic, so a change to agent.api.tool.agentic can break agent.api.common.support, while a change to agent.api.common.support can't break agent.api.tool.agentic.
- Position
- Below the diagonal: agent.api.common.support uses a module listed above it, which is the healthy direction.
11→14 agent.api.common.support uses chat part of a loop✕
- Connections
- 12 pairs of types, where a type in agent.api.common.support uses a type in chat.
- The types involved
com.embabel.agent.api.common.support.DelegatingCreating→com.embabel.chat.Messagecom.embabel.agent.api.common.support.DelegatingRendering→com.embabel.chat.AssistantMessagecom.embabel.agent.api.common.support.DelegatingRendering→com.embabel.chat.Conversationcom.embabel.agent.api.common.support.DelegatingStreaming→com.embabel.chat.Messagecom.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.chat.AssistantMessagecom.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.chat.Messagecom.embabel.agent.api.common.support.DelegatingThinking→com.embabel.chat.AssistantMessagecom.embabel.agent.api.common.support.DelegatingThinking→com.embabel.chat.Messagecom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.chat.AssistantMessagecom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.chat.Messagecom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.chat.AssistantMessagecom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.chat.Message
- Direction
- agent.api.common.support uses chat, so a change to chat can break agent.api.common.support, while a change to agent.api.common.support can't break chat.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→15 agent.api.common.support uses agent.api.tool.callback part of a loop✕
- Connections
- 9 pairs of types, where a type in agent.api.common.support uses a type in agent.api.tool.callback.
- The types involved
com.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.agent.api.tool.callback.ToolCallInspectorcom.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.agent.api.tool.callback.ToolLoopInspectorcom.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.agent.api.tool.callback.ToolLoopTransformercom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.api.tool.callback.ToolCallInspectorcom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.api.tool.callback.ToolLoopInspectorcom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.api.tool.callback.ToolLoopTransformercom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.api.tool.callback.ToolCallInspectorcom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.api.tool.callback.ToolLoopInspectorcom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.api.tool.callback.ToolLoopTransformer
- Direction
- agent.api.common.support uses agent.api.tool.callback, so a change to agent.api.tool.callback can break agent.api.common.support, while a change to agent.api.common.support can't break agent.api.tool.callback.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→16 agent.api.common.support uses agent.spi.loop part of a loop✕
- Connections
- 6 pairs of types, where a type in agent.api.common.support uses a type in agent.spi.loop.
- The types involved
com.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.agent.spi.loop.ToolInjectionStrategycom.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.agent.spi.loop.ToolNotFoundPolicycom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.spi.loop.ToolInjectionStrategycom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.spi.loop.ToolNotFoundPolicycom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.spi.loop.ToolInjectionStrategycom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.spi.loop.ToolNotFoundPolicy
- Direction
- agent.api.common.support uses agent.spi.loop, so a change to agent.spi.loop can break agent.api.common.support, while a change to agent.api.common.support can't break agent.spi.loop.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→18 agent.api.common.support uses common.ai.model part of a loop✕
- Connections
- 3 pairs of types, where a type in agent.api.common.support uses a type in common.ai.model.
- The types involved
com.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.common.ai.model.LlmOptions
- Direction
- agent.api.common.support uses common.ai.model, so a change to common.ai.model can break agent.api.common.support, while a change to agent.api.common.support can't break common.ai.model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→19 agent.api.common.support uses agent.api.tool part of a loop✕
- Connections
- 11 pairs of types, where a type in agent.api.common.support uses a type in agent.api.tool.
- The types involved
com.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.agent.api.tool.ToolCallContextcom.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.agent.api.tool.ToolObjectcom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.api.tool.ToolCallContextcom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.api.tool.ToolObjectcom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.api.tool.ToolCallContextcom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.api.tool.ToolObjectcom.embabel.agent.api.common.support.SelfToolGroup→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.common.support.SelfToolPublisher→com.embabel.agent.api.tool.Tool
- Direction
- agent.api.common.support uses agent.api.tool, so a change to agent.api.tool can break agent.api.common.support, while a change to agent.api.common.support can't break agent.api.tool.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→26 agent.api.common.support uses agent.core.support part of a loop✕
- Connections
- 5 pairs of types, where a type in agent.api.common.support uses a type in agent.core.support.
- The types involved
com.embabel.agent.api.common.support.BranchingAction→com.embabel.agent.core.support.AbstractActioncom.embabel.agent.api.common.support.MultiTransformationAction→com.embabel.agent.core.support.AbstractActioncom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.core.support.LlmInteractioncom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.core.support.LlmUsecom.embabel.agent.api.common.support.TransformationAction→com.embabel.agent.core.support.AbstractAction
- Direction
- agent.api.common.support uses agent.core.support, so a change to agent.core.support can break agent.api.common.support, while a change to agent.api.common.support can't break agent.core.support.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→28 agent.api.common.support uses agent.core part of a loop✕
- Connections
- 35 pairs of types, where a type in agent.api.common.support uses a type in agent.core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.embabel.agent.api.common.support.BindFieldsToBlackboardKt→com.embabel.agent.core.Blackboardcom.embabel.agent.api.common.support.BranchingAction→com.embabel.agent.core.ActionQoscom.embabel.agent.api.common.support.BranchingAction→com.embabel.agent.core.ActionStatuscom.embabel.agent.api.common.support.BranchingAction→com.embabel.agent.core.DomainTypecom.embabel.agent.api.common.support.BranchingAction→com.embabel.agent.core.ProcessContextcom.embabel.agent.api.common.support.BranchingAction→com.embabel.agent.core.ToolGroupRequirementcom.embabel.agent.api.common.support.ConsumerAction→com.embabel.agent.core.ActionQoscom.embabel.agent.api.common.support.ConsumerAction→com.embabel.agent.core.ToolGroupRequirementcom.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.agent.core.ToolGroupcom.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.agent.core.ToolGroupRequirementcom.embabel.agent.api.common.support.MultiTransformationAction→com.embabel.agent.core.ActionQoscom.embabel.agent.api.common.support.MultiTransformationAction→com.embabel.agent.core.ActionStatuscom.embabel.agent.api.common.support.MultiTransformationAction→com.embabel.agent.core.IoBindingcom.embabel.agent.api.common.support.MultiTransformationAction→com.embabel.agent.core.JvmTypecom.embabel.agent.api.common.support.MultiTransformationAction→com.embabel.agent.core.ProcessContextcom.embabel.agent.api.common.support.MultiTransformationAction→com.embabel.agent.core.ToolGroupRequirementcom.embabel.agent.api.common.support.MultiTransformationActionKt→com.embabel.agent.core.IoBindingcom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.core.Actioncom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.core.ToolGroupcom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.core.ToolGroupRequirementcom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.core.ToolGroupcom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.core.ToolGroupRequirementcom.embabel.agent.api.common.support.SelfToolGroup→com.embabel.agent.core.ToolGroupcom.embabel.agent.api.common.support.SelfToolGroup→com.embabel.agent.core.ToolGroupDescriptioncom.embabel.agent.api.common.support.SelfToolGroup→com.embabel.agent.core.ToolGroupMetadata
- Direction
- agent.api.common.support uses agent.core, so a change to agent.core can break agent.api.common.support, while a change to agent.api.common.support can't break agent.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→31 agent.api.common.support uses agent.api.common part of a loop✕
- Connections
- 17 pairs of types, where a type in agent.api.common.support uses a type in agent.api.common.
- The types involved
com.embabel.agent.api.common.support.BranchingAction→com.embabel.agent.api.common.Transformationcom.embabel.agent.api.common.support.ConsumerAction→com.embabel.agent.api.common.Transformationcom.embabel.agent.api.common.support.DelegatingCreating→com.embabel.agent.api.common.CreationExamplecom.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.agent.api.common.AgentImagecom.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.agent.api.common.ContextualPromptElementcom.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.agent.api.common.InteractionIdcom.embabel.agent.api.common.support.DelegatingStreamingPromptRunner→com.embabel.agent.api.common.PromptRunnercom.embabel.agent.api.common.support.MultiTransformationAction→com.embabel.agent.api.common.Transformationcom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.api.common.AgentImagecom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.api.common.ContextualPromptElementcom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.api.common.InteractionIdcom.embabel.agent.api.common.support.OperationContextDelegate→com.embabel.agent.api.common.OperationContextcom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.api.common.AgentImagecom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.api.common.ContextualPromptElementcom.embabel.agent.api.common.support.PromptExecutionDelegate→com.embabel.agent.api.common.InteractionIdcom.embabel.agent.api.common.support.SupplierAction→com.embabel.agent.api.common.Transformationcom.embabel.agent.api.common.support.TransformationAction→com.embabel.agent.api.common.Transformation
- Direction
- agent.api.common.support uses agent.api.common, so a change to agent.api.common can break agent.api.common.support, while a change to agent.api.common.support can't break agent.api.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→3 agent.tools.file uses common.util✕
- Connections
- 5 pairs of types, where a type in agent.tools.file uses a type in common.util.
- The types involved
com.embabel.agent.tools.file.DefaultFileReadTools→com.embabel.common.util.StringTransformercom.embabel.agent.tools.file.DefaultFileTools→com.embabel.common.util.StringTransformercom.embabel.agent.tools.file.FileReadTools→com.embabel.common.util.StringTransformercom.embabel.agent.tools.file.LocalDirectory→com.embabel.common.util.StringTransformercom.embabel.agent.tools.file.WellKnownFileContentTransformers→com.embabel.common.util.StringTransformer
- Direction
- agent.tools.file uses common.util, so a change to common.util can break agent.tools.file, while a change to agent.tools.file can't break common.util.
- Position
- Below the diagonal: agent.tools.file uses a module listed above it, which is the healthy direction.
12→11 agent.tools.file uses agent.api.common.support✕
- Connections
- 2 pairs of types, where a type in agent.tools.file uses a type in agent.api.common.support.
- The types involved
com.embabel.agent.tools.file.FileReadTools→com.embabel.agent.api.common.support.SelfToolPublishercom.embabel.agent.tools.file.FileWriteTools→com.embabel.agent.api.common.support.SelfToolPublisher
- Direction
- agent.tools.file uses agent.api.common.support, so a change to agent.api.common.support can break agent.tools.file, while a change to agent.tools.file can't break agent.api.common.support.
- Position
- Below the diagonal: agent.tools.file uses a module listed above it, which is the healthy direction.
12→13 agent.tools.file uses agent.api.reference part of a loop✕
- Connections
- 1 pair of types, where a type in agent.tools.file uses a type in agent.api.reference.
- The types involved
com.embabel.agent.tools.file.LocalDirectory→com.embabel.agent.api.reference.LlmReference
- Direction
- agent.tools.file uses agent.api.reference, so a change to agent.api.reference can break agent.tools.file, while a change to agent.tools.file can't break agent.api.reference.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→31 agent.tools.file uses agent.api.common part of a loop✕
- Connections
- 1 pair of types, where a type in agent.tools.file uses a type in agent.api.common.
- The types involved
com.embabel.agent.tools.file.PatternSearch→com.embabel.agent.api.common.Asyncer
- Direction
- agent.tools.file uses agent.api.common, so a change to agent.api.common can break agent.tools.file, while a change to agent.tools.file can't break agent.api.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→2 agent.api.reference uses common.ai.prompt✕
- Connections
- 1 pair of types, where a type in agent.api.reference uses a type in common.ai.prompt.
- The types involved
com.embabel.agent.api.reference.LlmReference→com.embabel.common.ai.prompt.PromptContributor
- Direction
- agent.api.reference uses common.ai.prompt, so a change to common.ai.prompt can break agent.api.reference, while a change to agent.api.reference can't break common.ai.prompt.
- Position
- Below the diagonal: agent.api.reference uses a module listed above it, which is the healthy direction.
13→3 agent.api.reference uses common.util✕
- Connections
- 2 pairs of types, where a type in agent.api.reference uses a type in common.util.
- The types involved
com.embabel.agent.api.reference.LlmReference→com.embabel.common.util.StringTransformercom.embabel.agent.api.reference.UnfoldingReference→com.embabel.common.util.StringTransformer
- Direction
- agent.api.reference uses common.util, so a change to common.util can break agent.api.reference, while a change to agent.api.reference can't break common.util.
- Position
- Below the diagonal: agent.api.reference uses a module listed above it, which is the healthy direction.
13→12 agent.api.reference uses agent.tools.file✕
- Connections
- 1 pair of types, where a type in agent.api.reference uses a type in agent.tools.file.
- The types involved
com.embabel.agent.api.reference.LocalDirectoryReference→com.embabel.agent.tools.file.LocalDirectory
- Direction
- agent.api.reference uses agent.tools.file, so a change to agent.tools.file can break agent.api.reference, while a change to agent.api.reference can't break agent.tools.file.
- Position
- Below the diagonal: agent.api.reference uses a module listed above it, which is the healthy direction.
13→19 agent.api.reference uses agent.api.tool part of a loop✕
- Connections
- 4 pairs of types, where a type in agent.api.reference uses a type in agent.api.tool.
- The types involved
com.embabel.agent.api.reference.LlmReference→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.reference.LlmReferenceKt→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.reference.SimpleLlmReference→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.reference.UnfoldingReference→com.embabel.agent.api.tool.Tool
- Direction
- agent.api.reference uses agent.api.tool, so a change to agent.api.tool can break agent.api.reference, while a change to agent.api.reference can't break agent.api.tool.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→2 chat uses common.ai.prompt✕
- Connections
- 1 pair of types, where a type in chat uses a type in common.ai.prompt.
- The types involved
com.embabel.chat.Conversation→com.embabel.common.ai.prompt.PromptContributor
- Direction
- chat uses common.ai.prompt, so a change to common.ai.prompt can break chat, while a change to chat can't break common.ai.prompt.
- Position
- Below the diagonal: chat uses a module listed above it, which is the healthy direction.
14→13 chat uses agent.api.reference✕
- Connections
- 7 pairs of types, where a type in chat uses a type in agent.api.reference.
- The types involved
com.embabel.chat.Asset→com.embabel.agent.api.reference.LlmReferenceProvidercom.embabel.chat.AssetView→com.embabel.agent.api.reference.LlmReferencecom.embabel.chat.ByteArrayMaterializableAsset→com.embabel.agent.api.reference.LlmReferencecom.embabel.chat.DurableAsset→com.embabel.agent.api.reference.LlmReferencecom.embabel.chat.LlmReferenceProviderAsset→com.embabel.agent.api.reference.LlmReferenceProvidercom.embabel.chat.PathMaterializableAsset→com.embabel.agent.api.reference.LlmReferencecom.embabel.chat.StreamMaterializableAsset→com.embabel.agent.api.reference.LlmReference
- Direction
- chat uses agent.api.reference, so a change to agent.api.reference can break chat, while a change to chat can't break agent.api.reference.
- Position
- Below the diagonal: chat uses a module listed above it, which is the healthy direction.
14→19 chat uses agent.api.tool part of a loop✕
- Connections
- 1 pair of types, where a type in chat uses a type in agent.api.tool.
- The types involved
com.embabel.chat.AssetTracker→com.embabel.agent.api.tool.Tool
- Direction
- chat uses agent.api.tool, so a change to agent.api.tool can break chat, while a change to chat can't break agent.api.tool.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→28 chat uses agent.core part of a loop✕
- Connections
- 1 pair of types, where a type in chat uses a type in agent.core.
- The types involved
com.embabel.chat.Chatbot→com.embabel.agent.core.Budget
- Direction
- chat uses agent.core, so a change to agent.core can break chat, while a change to chat can't break agent.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→29 chat uses agent.api.channel part of a loop✕
- Connections
- 2 pairs of types, where a type in chat uses a type in agent.api.channel.
- The types involved
com.embabel.chat.ChatSession→com.embabel.agent.api.channel.OutputChannelcom.embabel.chat.Chatbot→com.embabel.agent.api.channel.OutputChannel
- Direction
- chat uses agent.api.channel, so a change to agent.api.channel can break chat, while a change to chat can't break agent.api.channel.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→5 agent.api.tool.callback uses agent.api.tool.Tool✕
- Connections
- 3 pairs of types, where a type in agent.api.tool.callback uses a type in agent.api.tool.Tool.
- The types involved
com.embabel.agent.api.tool.callback.AfterToolCallContext→com.embabel.agent.api.tool.Tool.Resultcom.embabel.agent.api.tool.callback.AfterToolResultContext→com.embabel.agent.api.tool.Tool.Resultcom.embabel.agent.api.tool.callback.ToolResultContext→com.embabel.agent.api.tool.Tool.Result
- Direction
- agent.api.tool.callback uses agent.api.tool.Tool, so a change to agent.api.tool.Tool can break agent.api.tool.callback, while a change to agent.api.tool.callback can't break agent.api.tool.Tool.
- Position
- Below the diagonal: agent.api.tool.callback uses a module listed above it, which is the healthy direction.
15→14 agent.api.tool.callback uses chat✕
- Connections
- 12 pairs of types, where a type in agent.api.tool.callback uses a type in chat.
- The types involved
com.embabel.agent.api.tool.callback.AfterIterationContext→com.embabel.chat.Messagecom.embabel.agent.api.tool.callback.AfterIterationContext→com.embabel.chat.ToolCallcom.embabel.agent.api.tool.callback.AfterLlmCallContext→com.embabel.chat.Messagecom.embabel.agent.api.tool.callback.AfterToolCallContext→com.embabel.chat.ToolCallcom.embabel.agent.api.tool.callback.AfterToolResultContext→com.embabel.chat.Messagecom.embabel.agent.api.tool.callback.AfterToolResultContext→com.embabel.chat.ToolCallcom.embabel.agent.api.tool.callback.BeforeLlmCallContext→com.embabel.chat.Messagecom.embabel.agent.api.tool.callback.BeforeToolCallContext→com.embabel.chat.ToolCallcom.embabel.agent.api.tool.callback.CallbackContext→com.embabel.chat.Messagecom.embabel.agent.api.tool.callback.SlidingWindowTransformer→com.embabel.chat.Messagecom.embabel.agent.api.tool.callback.ToolLoopTransformer→com.embabel.chat.Messagecom.embabel.agent.api.tool.callback.ToolResultContext→com.embabel.chat.ToolCall
- Direction
- agent.api.tool.callback uses chat, so a change to chat can break agent.api.tool.callback, while a change to agent.api.tool.callback can't break chat.
- Position
- Below the diagonal: agent.api.tool.callback uses a module listed above it, which is the healthy direction.
15→19 agent.api.tool.callback uses agent.api.tool part of a loop✕
- Connections
- 1 pair of types, where a type in agent.api.tool.callback uses a type in agent.api.tool.
- The types involved
com.embabel.agent.api.tool.callback.BeforeLlmCallContext→com.embabel.agent.api.tool.Tool
- Direction
- agent.api.tool.callback uses agent.api.tool, so a change to agent.api.tool can break agent.api.tool.callback, while a change to agent.api.tool.callback can't break agent.api.tool.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→28 agent.api.tool.callback uses agent.core part of a loop✕
- Connections
- 1 pair of types, where a type in agent.api.tool.callback uses a type in agent.core.
- The types involved
com.embabel.agent.api.tool.callback.AfterLlmCallContext→com.embabel.agent.core.Usage
- Direction
- agent.api.tool.callback uses agent.core, so a change to agent.core can break agent.api.tool.callback, while a change to agent.api.tool.callback can't break agent.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→9 agent.spi.loop uses agent.api.tool.agentic✕
- Connections
- 1 pair of types, where a type in agent.spi.loop uses a type in agent.api.tool.agentic.
- The types involved
com.embabel.agent.spi.loop.ToolChainingInjectionStrategy→com.embabel.agent.api.tool.agentic.DomainToolTracker
- Direction
- agent.spi.loop uses agent.api.tool.agentic, so a change to agent.api.tool.agentic can break agent.spi.loop, while a change to agent.spi.loop can't break agent.api.tool.agentic.
- Position
- Below the diagonal: agent.spi.loop uses a module listed above it, which is the healthy direction.
16→14 agent.spi.loop uses chat✕
- Connections
- 6 pairs of types, where a type in agent.spi.loop uses a type in chat.
- The types involved
com.embabel.agent.spi.loop.LlmMessageRequest→com.embabel.chat.Messagecom.embabel.agent.spi.loop.LlmMessageResponse→com.embabel.chat.Messagecom.embabel.agent.spi.loop.LlmMessageSender→com.embabel.chat.Messagecom.embabel.agent.spi.loop.ToolInjectionContext→com.embabel.chat.Messagecom.embabel.agent.spi.loop.ToolLoop→com.embabel.chat.Messagecom.embabel.agent.spi.loop.ToolLoopResult→com.embabel.chat.Message
- Direction
- agent.spi.loop uses chat, so a change to chat can break agent.spi.loop, while a change to agent.spi.loop can't break chat.
- Position
- Below the diagonal: agent.spi.loop uses a module listed above it, which is the healthy direction.
16→15 agent.spi.loop uses agent.api.tool.callback✕
- Connections
- 6 pairs of types, where a type in agent.spi.loop uses a type in agent.api.tool.callback.
- The types involved
com.embabel.agent.spi.loop.ConfigurableToolLoopFactory→com.embabel.agent.api.tool.callback.ToolCallInspectorcom.embabel.agent.spi.loop.ConfigurableToolLoopFactory→com.embabel.agent.api.tool.callback.ToolLoopInspectorcom.embabel.agent.spi.loop.ConfigurableToolLoopFactory→com.embabel.agent.api.tool.callback.ToolLoopTransformercom.embabel.agent.spi.loop.ToolLoopFactory→com.embabel.agent.api.tool.callback.ToolCallInspectorcom.embabel.agent.spi.loop.ToolLoopFactory→com.embabel.agent.api.tool.callback.ToolLoopInspectorcom.embabel.agent.spi.loop.ToolLoopFactory→com.embabel.agent.api.tool.callback.ToolLoopTransformer
- Direction
- agent.spi.loop uses agent.api.tool.callback, so a change to agent.api.tool.callback can break agent.spi.loop, while a change to agent.spi.loop can't break agent.api.tool.callback.
- Position
- Below the diagonal: agent.spi.loop uses a module listed above it, which is the healthy direction.
16→18 agent.spi.loop uses common.ai.model part of a loop✕
- Connections
- 1 pair of types, where a type in agent.spi.loop uses a type in common.ai.model.
- The types involved
com.embabel.agent.spi.loop.NativeStructuredOutputRequest→com.embabel.common.ai.model.NativeStructuredOutputMode
- Direction
- agent.spi.loop uses common.ai.model, so a change to common.ai.model can break agent.spi.loop, while a change to agent.spi.loop can't break common.ai.model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→19 agent.spi.loop uses agent.api.tool part of a loop✕
- Connections
- 15 pairs of types, where a type in agent.spi.loop uses a type in agent.api.tool.
- The types involved
com.embabel.agent.spi.loop.AutoCorrectionPolicy→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.loop.ConfigurableToolLoopFactory→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.loop.ConfigurableToolLoopFactory→com.embabel.agent.api.tool.ToolCallContextcom.embabel.agent.spi.loop.ImmediateThrowPolicy→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.loop.LlmMessageRequest→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.loop.LlmMessageSender→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.loop.ToolInjectionContext→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.loop.ToolInjectionResult→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.loop.ToolInjectionStrategy→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.loop.ToolLoop→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.loop.ToolLoopFactory→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.loop.ToolLoopFactory→com.embabel.agent.api.tool.ToolCallContextcom.embabel.agent.spi.loop.ToolLoopResult→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.loop.ToolNotFoundPolicy→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.loop.UnfoldingToolInjectionStrategy→com.embabel.agent.api.tool.Tool
- Direction
- agent.spi.loop uses agent.api.tool, so a change to agent.api.tool can break agent.spi.loop, while a change to agent.spi.loop can't break agent.api.tool.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→28 agent.spi.loop uses agent.core part of a loop✕
- Connections
- 3 pairs of types, where a type in agent.spi.loop uses a type in agent.core.
- The types involved
com.embabel.agent.spi.loop.LlmMessageResponse→com.embabel.agent.core.Usagecom.embabel.agent.spi.loop.ToolLoopResult→com.embabel.agent.core.BlackboardUpdatercom.embabel.agent.spi.loop.ToolLoopResult→com.embabel.agent.core.Usage
- Direction
- agent.spi.loop uses agent.core, so a change to agent.core can break agent.spi.loop, while a change to agent.spi.loop can't break agent.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→31 agent.spi.loop uses agent.api.common part of a loop✕
- Connections
- 1 pair of types, where a type in agent.spi.loop uses a type in agent.api.common.
- The types involved
com.embabel.agent.spi.loop.ConfigurableToolLoopFactory→com.embabel.agent.api.common.Asyncer
- Direction
- agent.spi.loop uses agent.api.common, so a change to agent.api.common can break agent.spi.loop, while a change to agent.spi.loop can't break agent.api.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→2 agent.spi uses common.ai.prompt✕
- Connections
- 2 pairs of types, where a type in agent.spi uses a type in common.ai.prompt.
- The types involved
com.embabel.agent.spi.LlmService→com.embabel.common.ai.prompt.PromptContributorcom.embabel.agent.spi.LlmService→com.embabel.common.ai.prompt.PromptContributorConsumer
- Direction
- agent.spi uses common.ai.prompt, so a change to common.ai.prompt can break agent.spi, while a change to agent.spi can't break common.ai.prompt.
- Position
- Below the diagonal: agent.spi uses a module listed above it, which is the healthy direction.
17→4 agent.spi uses plan✕
- Connections
- 4 pairs of types, where a type in agent.spi uses a type in plan.
- The types involved
com.embabel.agent.spi.PlannerFactory→com.embabel.plan.Plancom.embabel.agent.spi.PlannerFactory→com.embabel.plan.Plannercom.embabel.agent.spi.PlannerFactory→com.embabel.plan.PlanningSystemcom.embabel.agent.spi.PlannerFactory→com.embabel.plan.WorldState
- Direction
- agent.spi uses plan, so a change to plan can break agent.spi, while a change to agent.spi can't break plan.
- Position
- Below the diagonal: agent.spi uses a module listed above it, which is the healthy direction.
17→8 agent.spi uses plan.common.condition✕
- Connections
- 1 pair of types, where a type in agent.spi uses a type in plan.common.condition.
- The types involved
com.embabel.agent.spi.PlannerFactory→com.embabel.plan.common.condition.WorldStateDeterminer
- Direction
- agent.spi uses plan.common.condition, so a change to plan.common.condition can break agent.spi, while a change to agent.spi can't break plan.common.condition.
- Position
- Below the diagonal: agent.spi uses a module listed above it, which is the healthy direction.
17→16 agent.spi uses agent.spi.loop✕
- Connections
- 1 pair of types, where a type in agent.spi uses a type in agent.spi.loop.
- The types involved
com.embabel.agent.spi.LlmService→com.embabel.agent.spi.loop.LlmMessageSender
- Direction
- agent.spi uses agent.spi.loop, so a change to agent.spi.loop can break agent.spi, while a change to agent.spi can't break agent.spi.loop.
- Position
- Below the diagonal: agent.spi uses a module listed above it, which is the healthy direction.
17→18 agent.spi uses common.ai.model part of a loop✕
- Connections
- 5 pairs of types, where a type in agent.spi uses a type in common.ai.model.
- The types involved
com.embabel.agent.spi.AutoLlmSelectionCriteriaResolver→com.embabel.common.ai.model.ModelSelectionCriteriacom.embabel.agent.spi.DefaultAutoLlmSelectionCriteriaResolver→com.embabel.common.ai.model.ModelSelectionCriteriacom.embabel.agent.spi.LlmService→com.embabel.common.ai.model.LlmMetadatacom.embabel.agent.spi.LlmService→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.spi.ToolDecorator→com.embabel.common.ai.model.LlmOptions
- Direction
- agent.spi uses common.ai.model, so a change to common.ai.model can break agent.spi, while a change to agent.spi can't break common.ai.model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→19 agent.spi uses agent.api.tool part of a loop✕
- Connections
- 1 pair of types, where a type in agent.spi uses a type in agent.api.tool.
- The types involved
com.embabel.agent.spi.ToolDecorator→com.embabel.agent.api.tool.Tool
- Direction
- agent.spi uses agent.api.tool, so a change to agent.api.tool can break agent.spi, while a change to agent.spi can't break agent.api.tool.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→27 agent.spi uses agent.api.event part of a loop✕
- Connections
- 4 pairs of types, where a type in agent.spi uses a type in agent.api.event.
- The types involved
com.embabel.agent.spi.OperationScheduler→com.embabel.agent.api.event.ActionExecutionStartEventcom.embabel.agent.spi.OperationScheduler→com.embabel.agent.api.event.ToolCallRequestEventcom.embabel.agent.spi.ProntoOperationScheduler→com.embabel.agent.api.event.ActionExecutionStartEventcom.embabel.agent.spi.ProntoOperationScheduler→com.embabel.agent.api.event.ToolCallRequestEvent
- Direction
- agent.spi uses agent.api.event, so a change to agent.api.event can break agent.spi, while a change to agent.spi can't break agent.api.event.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→28 agent.spi uses agent.core part of a loop✕
- Connections
- 10 pairs of types, where a type in agent.spi uses a type in agent.core.
- The types involved
com.embabel.agent.spi.AgentProcessIdGenerator→com.embabel.agent.core.Agentcom.embabel.agent.spi.AgentProcessIdGenerator→com.embabel.agent.core.ProcessOptionscom.embabel.agent.spi.BlackboardProvider→com.embabel.agent.core.Blackboardcom.embabel.agent.spi.ContextRepository→com.embabel.agent.core.Contextcom.embabel.agent.spi.PlannerFactory→com.embabel.agent.core.ProcessOptionscom.embabel.agent.spi.ToolDecorator→com.embabel.agent.core.Actioncom.embabel.agent.spi.ToolDecorator→com.embabel.agent.core.AgentProcesscom.embabel.agent.spi.ToolGroupResolver→com.embabel.agent.core.ToolGroupMetadatacom.embabel.agent.spi.ToolGroupResolver→com.embabel.agent.core.ToolGroupRequirementcom.embabel.agent.spi.ToolGroupResolver→com.embabel.agent.core.ToolGroupResolution
- Direction
- agent.spi uses agent.core, so a change to agent.core can break agent.spi, while a change to agent.spi can't break agent.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→7 common.ai.model uses common.ai.decision✕
- Connections
- 3 pairs of types, where a type in common.ai.model uses a type in common.ai.decision.
- The types involved
com.embabel.common.ai.model.DecisionModelProvider→com.embabel.common.ai.decision.DecisionServicecom.embabel.common.ai.model.DecisionServiceRegistry→com.embabel.common.ai.decision.DecisionCapabilitiescom.embabel.common.ai.model.DecisionServiceRegistry→com.embabel.common.ai.decision.DecisionService
- Direction
- common.ai.model uses common.ai.decision, so a change to common.ai.decision can break common.ai.model, while a change to common.ai.model can't break common.ai.decision.
- Position
- Below the diagonal: common.ai.model uses a module listed above it, which is the healthy direction.
18→10 common.ai.model uses common.ai.classification✕
- Connections
- 2 pairs of types, where a type in common.ai.model uses a type in common.ai.classification.
- The types involved
com.embabel.common.ai.model.DecisionServiceRegistry→com.embabel.common.ai.classification.ClassificationServicecom.embabel.common.ai.model.DecisionServiceRegistry→com.embabel.common.ai.classification.ClassificationServiceMetadata
- Direction
- common.ai.model uses common.ai.classification, so a change to common.ai.classification can break common.ai.model, while a change to common.ai.model can't break common.ai.classification.
- Position
- Below the diagonal: common.ai.model uses a module listed above it, which is the healthy direction.
18→17 common.ai.model uses agent.spi✕
- Connections
- 3 pairs of types, where a type in common.ai.model uses a type in agent.spi.
- The types involved
com.embabel.common.ai.model.ConfigurableModelProvider→com.embabel.agent.spi.LlmServicecom.embabel.common.ai.model.CredentialLlmServiceFactory→com.embabel.agent.spi.LlmServicecom.embabel.common.ai.model.ModelProvider→com.embabel.agent.spi.LlmService
- Direction
- common.ai.model uses agent.spi, so a change to agent.spi can break common.ai.model, while a change to common.ai.model can't break agent.spi.
- Position
- Below the diagonal: common.ai.model uses a module listed above it, which is the healthy direction.
19→3 agent.api.tool uses common.util✕
- Connections
- 1 pair of types, where a type in agent.api.tool uses a type in common.util.
- The types involved
com.embabel.agent.api.tool.ToolObject→com.embabel.common.util.StringTransformer
- Direction
- agent.api.tool uses common.util, so a change to common.util can break agent.api.tool, while a change to agent.api.tool can't break common.util.
- Position
- Below the diagonal: agent.api.tool uses a module listed above it, which is the healthy direction.
19→5 agent.api.tool uses agent.api.tool.Tool✕
- Connections
- 59 pairs of types, where a type in agent.api.tool uses a type in agent.api.tool.Tool. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.embabel.agent.api.tool.AgenticTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.api.tool.AgenticTool→com.embabel.agent.api.tool.Tool.Metadatacom.embabel.agent.api.tool.AgenticTool→com.embabel.agent.api.tool.Tool.Parametercom.embabel.agent.api.tool.AgenticTool→com.embabel.agent.api.tool.Tool.Resultcom.embabel.agent.api.tool.ArtifactSinkingTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.api.tool.ArtifactSinkingTool→com.embabel.agent.api.tool.Tool.Metadatacom.embabel.agent.api.tool.ArtifactSinkingTool→com.embabel.agent.api.tool.Tool.Resultcom.embabel.agent.api.tool.ConditionalReplanningTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.api.tool.ConditionalReplanningTool→com.embabel.agent.api.tool.Tool.Metadatacom.embabel.agent.api.tool.ConditionalReplanningTool→com.embabel.agent.api.tool.Tool.Resultcom.embabel.agent.api.tool.ContextAwareFunctionalTool→com.embabel.agent.api.tool.Tool.ContextAwareFunctioncom.embabel.agent.api.tool.ContextAwareFunctionalTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.api.tool.ContextAwareFunctionalTool→com.embabel.agent.api.tool.Tool.Metadatacom.embabel.agent.api.tool.ContextAwareFunctionalTool→com.embabel.agent.api.tool.Tool.Resultcom.embabel.agent.api.tool.DelegatingTool→com.embabel.agent.api.tool.Tool.Resultcom.embabel.agent.api.tool.DescribedTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.api.tool.DescribedTool→com.embabel.agent.api.tool.Tool.Metadatacom.embabel.agent.api.tool.DomainTypeInputSchema→com.embabel.agent.api.tool.Tool.InputSchemacom.embabel.agent.api.tool.DomainTypeInputSchema→com.embabel.agent.api.tool.Tool.Parametercom.embabel.agent.api.tool.FunctionalTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.api.tool.FunctionalTool→com.embabel.agent.api.tool.Tool.Functioncom.embabel.agent.api.tool.FunctionalTool→com.embabel.agent.api.tool.Tool.Metadatacom.embabel.agent.api.tool.FunctionalTool→com.embabel.agent.api.tool.Tool.Resultcom.embabel.agent.api.tool.JavaMethodTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.api.tool.KotlinMethodTool→com.embabel.agent.api.tool.Tool.Definition
- Direction
- agent.api.tool uses agent.api.tool.Tool, so a change to agent.api.tool.Tool can break agent.api.tool, while a change to agent.api.tool can't break agent.api.tool.Tool.
- Position
- Below the diagonal: agent.api.tool uses a module listed above it, which is the healthy direction.
19→18 agent.api.tool uses common.ai.model✕
- Connections
- 1 pair of types, where a type in agent.api.tool uses a type in common.ai.model.
- The types involved
com.embabel.agent.api.tool.AgenticTool→com.embabel.common.ai.model.LlmOptions
- Direction
- agent.api.tool uses common.ai.model, so a change to common.ai.model can break agent.api.tool, while a change to agent.api.tool can't break common.ai.model.
- Position
- Below the diagonal: agent.api.tool uses a module listed above it, which is the healthy direction.
19→28 agent.api.tool uses agent.core part of a loop✕
- Connections
- 9 pairs of types, where a type in agent.api.tool uses a type in agent.core.
- The types involved
com.embabel.agent.api.tool.AgenticTool→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.tool.DomainTypeInputSchema→com.embabel.agent.core.DomainTypecom.embabel.agent.api.tool.ReplanContext→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.tool.ReplanDecision→com.embabel.agent.core.BlackboardUpdatercom.embabel.agent.api.tool.ReplanningToolBlackboardUpdater→com.embabel.agent.core.Blackboardcom.embabel.agent.api.tool.Subagent→com.embabel.agent.core.Agentcom.embabel.agent.api.tool.Subagent→com.embabel.agent.core.AgentPlatformcom.embabel.agent.api.tool.Subagent→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.tool.Subagent→com.embabel.agent.core.ProcessOptions
- Direction
- agent.api.tool uses agent.core, so a change to agent.core can break agent.api.tool, while a change to agent.api.tool can't break agent.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→1 agent.spi.support.decision uses agent.spi.common✕
- Connections
- 1 pair of types, where a type in agent.spi.support.decision uses a type in agent.spi.common.
- The types involved
com.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.agent.spi.common.RetryProperties
- Direction
- agent.spi.support.decision uses agent.spi.common, so a change to agent.spi.common can break agent.spi.support.decision, while a change to agent.spi.support.decision can't break agent.spi.common.
- Position
- Below the diagonal: agent.spi.support.decision uses a module listed above it, which is the healthy direction.
20→6 agent.spi.support.decision uses agent.core.internal✕
- Connections
- 1 pair of types, where a type in agent.spi.support.decision uses a type in agent.core.internal.
- The types involved
com.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.agent.core.internal.LlmOperations
- Direction
- agent.spi.support.decision uses agent.core.internal, so a change to agent.core.internal can break agent.spi.support.decision, while a change to agent.spi.support.decision can't break agent.core.internal.
- Position
- Below the diagonal: agent.spi.support.decision uses a module listed above it, which is the healthy direction.
20→7 agent.spi.support.decision uses common.ai.decision✕
- Connections
- 28 pairs of types, where a type in agent.spi.support.decision uses a type in common.ai.decision. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.common.ai.decision.DecisionCapabilitiescom.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.common.ai.decision.DecisionRequestcom.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.common.ai.decision.DecisionResponsecom.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.common.ai.decision.DecisionServicecom.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.common.ai.decision.PropositionQuestionSpeccom.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.common.ai.decision.PropositionRequestcom.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.common.ai.decision.PropositionResultcom.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.common.ai.decision.RatingQuestionSpeccom.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.common.ai.decision.RatingResultcom.embabel.agent.spi.support.decision.OperationBoundDecisionService→com.embabel.common.ai.decision.DecisionCapabilitiescom.embabel.agent.spi.support.decision.OperationBoundDecisionService→com.embabel.common.ai.decision.DecisionRequestcom.embabel.agent.spi.support.decision.OperationBoundDecisionService→com.embabel.common.ai.decision.DecisionResponsecom.embabel.agent.spi.support.decision.OperationBoundDecisionService→com.embabel.common.ai.decision.DecisionServicecom.embabel.agent.spi.support.decision.OperationBoundDecisionService→com.embabel.common.ai.decision.DecisionServiceMetadatacom.embabel.agent.spi.support.decision.OperationBoundDecisionService→com.embabel.common.ai.decision.DecisionSpeccom.embabel.agent.spi.support.decision.OperationBoundDecisionService→com.embabel.common.ai.decision.PropositionQuestionSpeccom.embabel.agent.spi.support.decision.OperationBoundDecisionService→com.embabel.common.ai.decision.PropositionRequestcom.embabel.agent.spi.support.decision.OperationBoundDecisionService→com.embabel.common.ai.decision.PropositionResultcom.embabel.agent.spi.support.decision.OperationBoundDecisionService→com.embabel.common.ai.decision.RatingQuestionSpeccom.embabel.agent.spi.support.decision.OperationBoundDecisionService→com.embabel.common.ai.decision.RatingResultcom.embabel.agent.spi.support.decision.OperationBoundServices→com.embabel.common.ai.decision.DecisionServicecom.embabel.agent.spi.support.decision.PromptedProposition→com.embabel.common.ai.decision.PropositionRequestcom.embabel.agent.spi.support.decision.PromptedProposition→com.embabel.common.ai.decision.PropositionResultcom.embabel.agent.spi.support.decision.PromptedQuestionSet→com.embabel.common.ai.decision.DecisionRequestcom.embabel.agent.spi.support.decision.PromptedQuestionSet→com.embabel.common.ai.decision.DecisionResponse
- Direction
- agent.spi.support.decision uses common.ai.decision, so a change to common.ai.decision can break agent.spi.support.decision, while a change to agent.spi.support.decision can't break common.ai.decision.
- Position
- Below the diagonal: agent.spi.support.decision uses a module listed above it, which is the healthy direction.
20→10 agent.spi.support.decision uses common.ai.classification✕
- Connections
- 21 pairs of types, where a type in agent.spi.support.decision uses a type in common.ai.classification.
- The types involved
com.embabel.agent.spi.support.decision.LlmClassificationService→com.embabel.common.ai.classification.ClassificationRequestcom.embabel.agent.spi.support.decision.LlmClassificationService→com.embabel.common.ai.classification.ClassificationResultcom.embabel.agent.spi.support.decision.LlmClassificationService→com.embabel.common.ai.classification.ClassificationServicecom.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.common.ai.classification.ClassificationRequestcom.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.common.ai.classification.ClassificationResultcom.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.common.ai.classification.FailureReasoncom.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.common.ai.classification.ModelProvenancecom.embabel.agent.spi.support.decision.OperationBoundClassificationService→com.embabel.common.ai.classification.ClassificationRequestcom.embabel.agent.spi.support.decision.OperationBoundClassificationService→com.embabel.common.ai.classification.ClassificationResultcom.embabel.agent.spi.support.decision.OperationBoundClassificationService→com.embabel.common.ai.classification.ClassificationServicecom.embabel.agent.spi.support.decision.OperationBoundClassificationService→com.embabel.common.ai.classification.ClassificationServiceMetadatacom.embabel.agent.spi.support.decision.OperationBoundClassificationService→com.embabel.common.ai.classification.ClassificationSpeccom.embabel.agent.spi.support.decision.OperationBoundDecisionService→com.embabel.common.ai.classification.ClassificationRequestcom.embabel.agent.spi.support.decision.OperationBoundDecisionService→com.embabel.common.ai.classification.ClassificationResultcom.embabel.agent.spi.support.decision.OperationBoundDecisionService→com.embabel.common.ai.classification.ClassificationSpeccom.embabel.agent.spi.support.decision.OperationBoundServices→com.embabel.common.ai.classification.ClassificationServicecom.embabel.agent.spi.support.decision.PromptedClassification→com.embabel.common.ai.classification.ClassificationRequestcom.embabel.agent.spi.support.decision.PromptedClassification→com.embabel.common.ai.classification.ClassificationResultcom.embabel.agent.spi.support.decision.PromptedClassification→com.embabel.common.ai.classification.ModelProvenancecom.embabel.agent.spi.support.decision.PromptedProposition→com.embabel.common.ai.classification.ModelProvenancecom.embabel.agent.spi.support.decision.PromptedQuestionSet→com.embabel.common.ai.classification.ModelProvenance
- Direction
- agent.spi.support.decision uses common.ai.classification, so a change to common.ai.classification can break agent.spi.support.decision, while a change to agent.spi.support.decision can't break common.ai.classification.
- Position
- Below the diagonal: agent.spi.support.decision uses a module listed above it, which is the healthy direction.
20→14 agent.spi.support.decision uses chat✕
- Connections
- 4 pairs of types, where a type in agent.spi.support.decision uses a type in chat.
- The types involved
com.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.chat.Messagecom.embabel.agent.spi.support.decision.PromptedClassification→com.embabel.chat.Messagecom.embabel.agent.spi.support.decision.PromptedProposition→com.embabel.chat.Messagecom.embabel.agent.spi.support.decision.PromptedQuestionSet→com.embabel.chat.Message
- Direction
- agent.spi.support.decision uses chat, so a change to chat can break agent.spi.support.decision, while a change to agent.spi.support.decision can't break chat.
- Position
- Below the diagonal: agent.spi.support.decision uses a module listed above it, which is the healthy direction.
20→17 agent.spi.support.decision uses agent.spi✕
- Connections
- 1 pair of types, where a type in agent.spi.support.decision uses a type in agent.spi.
- The types involved
com.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.agent.spi.LlmService
- Direction
- agent.spi.support.decision uses agent.spi, so a change to agent.spi can break agent.spi.support.decision, while a change to agent.spi.support.decision can't break agent.spi.
- Position
- Below the diagonal: agent.spi.support.decision uses a module listed above it, which is the healthy direction.
20→18 agent.spi.support.decision uses common.ai.model✕
- Connections
- 6 pairs of types, where a type in agent.spi.support.decision uses a type in common.ai.model.
- The types involved
com.embabel.agent.spi.support.decision.BindingSelector→com.embabel.common.ai.model.ServiceSelectorcom.embabel.agent.spi.support.decision.LlmDecisionService→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.spi.support.decision.OperationBoundClassificationService→com.embabel.common.ai.model.ModelTypecom.embabel.agent.spi.support.decision.OperationBoundDecisionService→com.embabel.common.ai.model.ModelTypecom.embabel.agent.spi.support.decision.OperationBoundServices→com.embabel.common.ai.model.DecisionServiceRegistrycom.embabel.agent.spi.support.decision.OperationBoundServices→com.embabel.common.ai.model.ServiceSelector
- Direction
- agent.spi.support.decision uses common.ai.model, so a change to common.ai.model can break agent.spi.support.decision, while a change to agent.spi.support.decision can't break common.ai.model.
- Position
- Below the diagonal: agent.spi.support.decision uses a module listed above it, which is the healthy direction.
21→7 common.ai.autoconfig uses common.ai.decision✕
- Connections
- 1 pair of types, where a type in common.ai.autoconfig uses a type in common.ai.decision.
- The types involved
com.embabel.common.ai.autoconfig.DecisionModelsRegistrar→com.embabel.common.ai.decision.DecisionService
- Direction
- common.ai.autoconfig uses common.ai.decision, so a change to common.ai.decision can break common.ai.autoconfig, while a change to common.ai.autoconfig can't break common.ai.decision.
- Position
- Below the diagonal: common.ai.autoconfig uses a module listed above it, which is the healthy direction.
21→18 common.ai.autoconfig uses common.ai.model✕
- Connections
- 1 pair of types, where a type in common.ai.autoconfig uses a type in common.ai.model.
- The types involved
com.embabel.common.ai.autoconfig.LlmAutoConfigMetadata→com.embabel.common.ai.model.PerTokenPricingModel
- Direction
- common.ai.autoconfig uses common.ai.model, so a change to common.ai.model can break common.ai.autoconfig, while a change to common.ai.autoconfig can't break common.ai.model.
- Position
- Below the diagonal: common.ai.autoconfig uses a module listed above it, which is the healthy direction.
22→5 agent.skills.script uses agent.api.tool.Tool✕
- Connections
- 2 pairs of types, where a type in agent.skills.script uses a type in agent.api.tool.Tool.
- The types involved
com.embabel.agent.skills.script.ScriptTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.skills.script.ScriptTool→com.embabel.agent.api.tool.Tool.Result
- Direction
- agent.skills.script uses agent.api.tool.Tool, so a change to agent.api.tool.Tool can break agent.skills.script, while a change to agent.skills.script can't break agent.api.tool.Tool.
- Position
- Below the diagonal: agent.skills.script uses a module listed above it, which is the healthy direction.
22→12 agent.skills.script uses agent.tools.file✕
- Connections
- 5 pairs of types, where a type in agent.skills.script uses a type in agent.tools.file.
- The types involved
com.embabel.agent.skills.script.AbstractContainerSkillScriptExecutionEngine→com.embabel.agent.tools.file.FileToolscom.embabel.agent.skills.script.ConfinedInputResolver→com.embabel.agent.tools.file.FileToolscom.embabel.agent.skills.script.DockerSkillScriptExecutionEngine→com.embabel.agent.tools.file.FileToolscom.embabel.agent.skills.script.PodmanSkillScriptExecutionEngine→com.embabel.agent.tools.file.FileToolscom.embabel.agent.skills.script.ProcessSkillScriptExecutionEngine→com.embabel.agent.tools.file.FileTools
- Direction
- agent.skills.script uses agent.tools.file, so a change to agent.tools.file can break agent.skills.script, while a change to agent.skills.script can't break agent.tools.file.
- Position
- Below the diagonal: agent.skills.script uses a module listed above it, which is the healthy direction.
22→13 agent.skills.script uses agent.api.reference✕
- Connections
- 1 pair of types, where a type in agent.skills.script uses a type in agent.api.reference.
- The types involved
com.embabel.agent.skills.script.ScriptArtifact→com.embabel.agent.api.reference.LlmReference
- Direction
- agent.skills.script uses agent.api.reference, so a change to agent.api.reference can break agent.skills.script, while a change to agent.skills.script can't break agent.api.reference.
- Position
- Below the diagonal: agent.skills.script uses a module listed above it, which is the healthy direction.
22→14 agent.skills.script uses chat✕
- Connections
- 1 pair of types, where a type in agent.skills.script uses a type in chat.
- The types involved
com.embabel.agent.skills.script.ScriptArtifact→com.embabel.chat.MaterializableAsset
- Direction
- agent.skills.script uses chat, so a change to chat can break agent.skills.script, while a change to agent.skills.script can't break chat.
- Position
- Below the diagonal: agent.skills.script uses a module listed above it, which is the healthy direction.
22→19 agent.skills.script uses agent.api.tool✕
- Connections
- 1 pair of types, where a type in agent.skills.script uses a type in agent.api.tool.
- The types involved
com.embabel.agent.skills.script.ScriptTool→com.embabel.agent.api.tool.Tool
- Direction
- agent.skills.script uses agent.api.tool, so a change to agent.api.tool can break agent.skills.script, while a change to agent.skills.script can't break agent.api.tool.
- Position
- Below the diagonal: agent.skills.script uses a module listed above it, which is the healthy direction.
23→3 agent.spi.config.spring uses common.util✕
- Connections
- 1 pair of types, where a type in agent.spi.config.spring uses a type in common.util.
- The types involved
com.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.common.util.EmbabelObjectMapperHolder
- Direction
- agent.spi.config.spring uses common.util, so a change to common.util can break agent.spi.config.spring, while a change to agent.spi.config.spring can't break common.util.
- Position
- Below the diagonal: agent.spi.config.spring uses a module listed above it, which is the healthy direction.
23→6 agent.spi.config.spring uses agent.core.internal✕
- Connections
- 1 pair of types, where a type in agent.spi.config.spring uses a type in agent.core.internal.
- The types involved
com.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.agent.core.internal.LlmOperations
- Direction
- agent.spi.config.spring uses agent.core.internal, so a change to agent.core.internal can break agent.spi.config.spring, while a change to agent.spi.config.spring can't break agent.core.internal.
- Position
- Below the diagonal: agent.spi.config.spring uses a module listed above it, which is the healthy direction.
23→16 agent.spi.config.spring uses agent.spi.loop✕
- Connections
- 3 pairs of types, where a type in agent.spi.config.spring uses a type in agent.spi.loop.
- The types involved
com.embabel.agent.spi.config.spring.ToolLoopFactoryConfiguration→com.embabel.agent.spi.loop.EmptyResponsePolicycom.embabel.agent.spi.config.spring.ToolLoopFactoryConfiguration→com.embabel.agent.spi.loop.ToolLoopFactorycom.embabel.agent.spi.config.spring.ToolLoopFactoryConfiguration→com.embabel.agent.spi.loop.ToolNotFoundPolicy
- Direction
- agent.spi.config.spring uses agent.spi.loop, so a change to agent.spi.loop can break agent.spi.config.spring, while a change to agent.spi.config.spring can't break agent.spi.loop.
- Position
- Below the diagonal: agent.spi.config.spring uses a module listed above it, which is the healthy direction.
23→17 agent.spi.config.spring uses agent.spi✕
- Connections
- 5 pairs of types, where a type in agent.spi.config.spring uses a type in agent.spi.
- The types involved
com.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.agent.spi.AutoLlmSelectionCriteriaResolvercom.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.agent.spi.ContextRepositorycom.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.agent.spi.OperationSchedulercom.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.agent.spi.ToolDecoratorcom.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.agent.spi.ToolGroupResolver
- Direction
- agent.spi.config.spring uses agent.spi, so a change to agent.spi can break agent.spi.config.spring, while a change to agent.spi.config.spring can't break agent.spi.
- Position
- Below the diagonal: agent.spi.config.spring uses a module listed above it, which is the healthy direction.
23→18 agent.spi.config.spring uses common.ai.model✕
- Connections
- 3 pairs of types, where a type in agent.spi.config.spring uses a type in common.ai.model.
- The types involved
com.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.common.ai.model.ConfigurableModelProviderPropertiescom.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.common.ai.model.ModelProvidercom.embabel.agent.spi.config.spring.EmbeddingTrackingConfiguration→com.embabel.common.ai.model.TokenCountEstimator
- Direction
- agent.spi.config.spring uses common.ai.model, so a change to common.ai.model can break agent.spi.config.spring, while a change to agent.spi.config.spring can't break common.ai.model.
- Position
- Below the diagonal: agent.spi.config.spring uses a module listed above it, which is the healthy direction.
23→21 agent.spi.config.spring uses common.ai.autoconfig✕
- Connections
- 1 pair of types, where a type in agent.spi.config.spring uses a type in common.ai.autoconfig.
- The types involved
com.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.common.ai.autoconfig.ProviderInitialization
- Direction
- agent.spi.config.spring uses common.ai.autoconfig, so a change to common.ai.autoconfig can break agent.spi.config.spring, while a change to agent.spi.config.spring can't break common.ai.autoconfig.
- Position
- Below the diagonal: agent.spi.config.spring uses a module listed above it, which is the healthy direction.
23→25 agent.spi.config.spring uses agent.spi.support part of a loop✕
- Connections
- 2 pairs of types, where a type in agent.spi.config.spring uses a type in agent.spi.support.
- The types involved
com.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.agent.spi.support.AgenticEventListenerToolsStatscom.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.agent.spi.support.RankingProperties
- Direction
- agent.spi.config.spring uses agent.spi.support, so a change to agent.spi.support can break agent.spi.config.spring, while a change to agent.spi.config.spring can't break agent.spi.support.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→27 agent.spi.config.spring uses agent.api.event part of a loop✕
- Connections
- 2 pairs of types, where a type in agent.spi.config.spring uses a type in agent.api.event.
- The types involved
com.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.agent.api.event.AgenticEventListenercom.embabel.agent.spi.config.spring.EmbeddingTrackingConfiguration→com.embabel.agent.api.event.EmbeddingEventListener
- Direction
- agent.spi.config.spring uses agent.api.event, so a change to agent.api.event can break agent.spi.config.spring, while a change to agent.spi.config.spring can't break agent.api.event.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→28 agent.spi.config.spring uses agent.core part of a loop✕
- Connections
- 10 pairs of types, where a type in agent.spi.config.spring uses a type in agent.core.
- The types involved
com.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.agent.core.AgentPlatformcom.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.agent.core.AgentProcessRepositorycom.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.agent.core.ToolGroupcom.embabel.agent.spi.config.spring.AiBuilderImpl→com.embabel.agent.core.AgentPlatformcom.embabel.agent.spi.config.spring.AiBuilderImpl→com.embabel.agent.core.ProcessOptionscom.embabel.agent.spi.config.spring.InfrastructureInjectionConfiguration→com.embabel.agent.core.AgentPlatformcom.embabel.agent.spi.config.spring.InfrastructureInjectionConfigurationKt→com.embabel.agent.core.AgentPlatformcom.embabel.agent.spi.config.spring.InfrastructureInjectionConfigurationKt→com.embabel.agent.core.AgentProcesscom.embabel.agent.spi.config.spring.InfrastructureInjectionConfigurationKt→com.embabel.agent.core.ProcessOptionscom.embabel.agent.spi.config.spring.ToolGroupsConfiguration→com.embabel.agent.core.ToolGroup
- Direction
- agent.spi.config.spring uses agent.core, so a change to agent.core can break agent.spi.config.spring, while a change to agent.spi.config.spring can't break agent.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→29 agent.spi.config.spring uses agent.api.channel part of a loop✕
- Connections
- 1 pair of types, where a type in agent.spi.config.spring uses a type in agent.api.channel.
- The types involved
com.embabel.agent.spi.config.spring.AgentPlatformConfiguration→com.embabel.agent.api.channel.OutputChannel
- Direction
- agent.spi.config.spring uses agent.api.channel, so a change to agent.api.channel can break agent.spi.config.spring, while a change to agent.spi.config.spring can't break agent.api.channel.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→31 agent.spi.config.spring uses agent.api.common part of a loop✕
- Connections
- 8 pairs of types, where a type in agent.spi.config.spring uses a type in agent.api.common.
- The types involved
com.embabel.agent.spi.config.spring.AiBuilderImpl→com.embabel.agent.api.common.Aicom.embabel.agent.spi.config.spring.AiBuilderImpl→com.embabel.agent.api.common.AiBuildercom.embabel.agent.spi.config.spring.AsyncConfiguration→com.embabel.agent.api.common.Asyncercom.embabel.agent.spi.config.spring.InfrastructureInjectionConfiguration→com.embabel.agent.api.common.Aicom.embabel.agent.spi.config.spring.InfrastructureInjectionConfiguration→com.embabel.agent.api.common.AiBuildercom.embabel.agent.spi.config.spring.InfrastructureInjectionConfiguration→com.embabel.agent.api.common.ExecutingOperationContextcom.embabel.agent.spi.config.spring.InfrastructureInjectionConfigurationKt→com.embabel.agent.api.common.ExecutingOperationContextcom.embabel.agent.spi.config.spring.ToolLoopFactoryConfiguration→com.embabel.agent.api.common.Asyncer
- Direction
- agent.spi.config.spring uses agent.api.common, so a change to agent.api.common can break agent.spi.config.spring, while a change to agent.spi.config.spring can't break agent.api.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→32 agent.spi.config.spring uses agent.api.annotation.support part of a loop✕
- Connections
- 1 pair of types, where a type in agent.spi.config.spring uses a type in agent.api.annotation.support.
- The types involved
com.embabel.agent.spi.config.spring.SpringContextProvider→com.embabel.agent.api.annotation.support.ContextProvider
- Direction
- agent.spi.config.spring uses agent.api.annotation.support, so a change to agent.api.annotation.support can break agent.spi.config.spring, while a change to agent.spi.config.spring can't break agent.api.annotation.support.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→4 agent.api.common.autonomy uses plan✕
- Connections
- 2 pairs of types, where a type in agent.api.common.autonomy uses a type in plan.
- The types involved
com.embabel.agent.api.common.autonomy.DefaultPlanLister→com.embabel.plan.Plancom.embabel.agent.api.common.autonomy.PlanLister→com.embabel.plan.Plan
- Direction
- agent.api.common.autonomy uses plan, so a change to plan can break agent.api.common.autonomy, while a change to agent.api.common.autonomy can't break plan.
- Position
- Below the diagonal: agent.api.common.autonomy uses a module listed above it, which is the healthy direction.
24→8 agent.api.common.autonomy uses plan.common.condition✕
- Connections
- 1 pair of types, where a type in agent.api.common.autonomy uses a type in plan.common.condition.
- The types involved
com.embabel.agent.api.common.autonomy.DefaultPlanLister→com.embabel.plan.common.condition.ConditionPlanningSystem
- Direction
- agent.api.common.autonomy uses plan.common.condition, so a change to plan.common.condition can break agent.api.common.autonomy, while a change to agent.api.common.autonomy can't break plan.common.condition.
- Position
- Below the diagonal: agent.api.common.autonomy uses a module listed above it, which is the healthy direction.
24→23 agent.api.common.autonomy uses agent.spi.config.spring✕
- Connections
- 1 pair of types, where a type in agent.api.common.autonomy uses a type in agent.spi.config.spring.
- The types involved
com.embabel.agent.api.common.autonomy.AutonomyProperties→com.embabel.agent.spi.config.spring.AgentPlatformProperties
- Direction
- agent.api.common.autonomy uses agent.spi.config.spring, so a change to agent.spi.config.spring can break agent.api.common.autonomy, while a change to agent.api.common.autonomy can't break agent.spi.config.spring.
- Position
- Below the diagonal: agent.api.common.autonomy uses a module listed above it, which is the healthy direction.
24→27 agent.api.common.autonomy uses agent.api.event part of a loop✕
- Connections
- 2 pairs of types, where a type in agent.api.common.autonomy uses a type in agent.api.event.
- The types involved
com.embabel.agent.api.common.autonomy.Autonomy→com.embabel.agent.api.event.AgenticEventListenercom.embabel.agent.api.common.autonomy.GoalNotApproved→com.embabel.agent.api.event.AgentPlatformEvent
- Direction
- agent.api.common.autonomy uses agent.api.event, so a change to agent.api.event can break agent.api.common.autonomy, while a change to agent.api.common.autonomy can't break agent.api.event.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→28 agent.api.common.autonomy uses agent.core part of a loop✕
- Connections
- 20 pairs of types, where a type in agent.api.common.autonomy uses a type in agent.core.
- The types involved
com.embabel.agent.api.common.autonomy.AgentProcessExecution→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.common.autonomy.Autonomy→com.embabel.agent.core.Agentcom.embabel.agent.api.common.autonomy.Autonomy→com.embabel.agent.core.AgentPlatformcom.embabel.agent.api.common.autonomy.Autonomy→com.embabel.agent.core.AgentScopecom.embabel.agent.api.common.autonomy.Autonomy→com.embabel.agent.core.Goalcom.embabel.agent.api.common.autonomy.Autonomy→com.embabel.agent.core.ProcessOptionscom.embabel.agent.api.common.autonomy.DefaultPlanLister→com.embabel.agent.core.AgentPlatformcom.embabel.agent.api.common.autonomy.DefaultPlanLister→com.embabel.agent.core.ProcessOptionscom.embabel.agent.api.common.autonomy.GoalChoiceApprovalRequest→com.embabel.agent.core.Goalcom.embabel.agent.api.common.autonomy.GoalNotApproved→com.embabel.agent.core.AgentPlatformcom.embabel.agent.api.common.autonomy.GoalNotApproved→com.embabel.agent.core.Goalcom.embabel.agent.api.common.autonomy.NoAgentFound→com.embabel.agent.core.Agentcom.embabel.agent.api.common.autonomy.NoGoalFound→com.embabel.agent.core.Goalcom.embabel.agent.api.common.autonomy.PlanLister→com.embabel.agent.core.Goalcom.embabel.agent.api.common.autonomy.PlanLister→com.embabel.agent.core.ProcessOptionscom.embabel.agent.api.common.autonomy.ProcessExecutionException→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.common.autonomy.ProcessExecutionFailedException→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.common.autonomy.ProcessExecutionStuckException→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.common.autonomy.ProcessExecutionTerminatedException→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.common.autonomy.ProcessWaitingException→com.embabel.agent.core.AgentProcess
- Direction
- agent.api.common.autonomy uses agent.core, so a change to agent.core can break agent.api.common.autonomy, while a change to agent.api.common.autonomy can't break agent.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→1 agent.spi.support uses agent.spi.common✕
- Connections
- 2 pairs of types, where a type in agent.spi.support uses a type in agent.spi.common.
- The types involved
com.embabel.agent.spi.support.LlmDataBindingProperties→com.embabel.agent.spi.common.RetryTemplateProvidercom.embabel.agent.spi.support.RankingProperties→com.embabel.agent.spi.common.RetryProperties
- Direction
- agent.spi.support uses agent.spi.common, so a change to agent.spi.common can break agent.spi.support, while a change to agent.spi.support can't break agent.spi.common.
- Position
- Below the diagonal: agent.spi.support uses a module listed above it, which is the healthy direction.
25→2 agent.spi.support uses common.ai.prompt✕
- Connections
- 1 pair of types, where a type in agent.spi.support uses a type in common.ai.prompt.
- The types involved
com.embabel.agent.spi.support.MessagePromptBuildersKt→com.embabel.common.ai.prompt.PromptContributor
- Direction
- agent.spi.support uses common.ai.prompt, so a change to common.ai.prompt can break agent.spi.support, while a change to agent.spi.support can't break common.ai.prompt.
- Position
- Below the diagonal: agent.spi.support uses a module listed above it, which is the healthy direction.
25→3 agent.spi.support uses common.util✕
- Connections
- 4 pairs of types, where a type in agent.spi.support uses a type in common.util.
- The types involved
com.embabel.agent.spi.support.DefaultToolDecorator→com.embabel.common.util.StringTransformercom.embabel.agent.spi.support.OutputTransformingTool→com.embabel.common.util.StringTransformercom.embabel.agent.spi.support.OutputTransformingToolCallback→com.embabel.common.util.StringTransformercom.embabel.agent.spi.support.SpringContextPlatformServices→com.embabel.common.util.EmbabelObjectMapperHolder
- Direction
- agent.spi.support uses common.util, so a change to common.util can break agent.spi.support, while a change to agent.spi.support can't break common.util.
- Position
- Below the diagonal: agent.spi.support uses a module listed above it, which is the healthy direction.
25→4 agent.spi.support uses plan✕
- Connections
- 4 pairs of types, where a type in agent.spi.support uses a type in plan.
- The types involved
com.embabel.agent.spi.support.DefaultPlannerFactory→com.embabel.plan.Plancom.embabel.agent.spi.support.DefaultPlannerFactory→com.embabel.plan.Plannercom.embabel.agent.spi.support.DefaultPlannerFactory→com.embabel.plan.PlanningSystemcom.embabel.agent.spi.support.DefaultPlannerFactory→com.embabel.plan.WorldState
- Direction
- agent.spi.support uses plan, so a change to plan can break agent.spi.support, while a change to agent.spi.support can't break plan.
- Position
- Below the diagonal: agent.spi.support uses a module listed above it, which is the healthy direction.
25→5 agent.spi.support uses agent.api.tool.Tool✕
- Connections
- 18 pairs of types, where a type in agent.spi.support uses a type in agent.api.tool.Tool.
- The types involved
com.embabel.agent.spi.support.AgentProcessBindingTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.spi.support.AgentProcessBindingTool→com.embabel.agent.api.tool.Tool.Metadatacom.embabel.agent.spi.support.AgentProcessBindingTool→com.embabel.agent.api.tool.Tool.Resultcom.embabel.agent.spi.support.EventPublishingTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.spi.support.EventPublishingTool→com.embabel.agent.api.tool.Tool.Metadatacom.embabel.agent.spi.support.EventPublishingTool→com.embabel.agent.api.tool.Tool.Resultcom.embabel.agent.spi.support.ExceptionSuppressingTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.spi.support.ExceptionSuppressingTool→com.embabel.agent.api.tool.Tool.Metadatacom.embabel.agent.spi.support.ExceptionSuppressingTool→com.embabel.agent.api.tool.Tool.Resultcom.embabel.agent.spi.support.MetadataEnrichingTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.spi.support.MetadataEnrichingTool→com.embabel.agent.api.tool.Tool.Metadatacom.embabel.agent.spi.support.MetadataEnrichingTool→com.embabel.agent.api.tool.Tool.Resultcom.embabel.agent.spi.support.ObservabilityTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.spi.support.ObservabilityTool→com.embabel.agent.api.tool.Tool.Metadatacom.embabel.agent.spi.support.ObservabilityTool→com.embabel.agent.api.tool.Tool.Resultcom.embabel.agent.spi.support.OutputTransformingTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.spi.support.OutputTransformingTool→com.embabel.agent.api.tool.Tool.Metadatacom.embabel.agent.spi.support.OutputTransformingTool→com.embabel.agent.api.tool.Tool.Result
- Direction
- agent.spi.support uses agent.api.tool.Tool, so a change to agent.api.tool.Tool can break agent.spi.support, while a change to agent.spi.support can't break agent.api.tool.Tool.
- Position
- Below the diagonal: agent.spi.support uses a module listed above it, which is the healthy direction.
25→6 agent.spi.support uses agent.core.internal✕
- Connections
- 3 pairs of types, where a type in agent.spi.support uses a type in agent.core.internal.
- The types involved
com.embabel.agent.spi.support.AbstractLlmOperations→com.embabel.agent.core.internal.LlmOperationscom.embabel.agent.spi.support.LlmRanker→com.embabel.agent.core.internal.LlmOperationscom.embabel.agent.spi.support.SpringContextPlatformServices→com.embabel.agent.core.internal.LlmOperations
- Direction
- agent.spi.support uses agent.core.internal, so a change to agent.core.internal can break agent.spi.support, while a change to agent.spi.support can't break agent.core.internal.
- Position
- Below the diagonal: agent.spi.support uses a module listed above it, which is the healthy direction.
25→8 agent.spi.support uses plan.common.condition✕
- Connections
- 1 pair of types, where a type in agent.spi.support uses a type in plan.common.condition.
- The types involved
com.embabel.agent.spi.support.DefaultPlannerFactory→com.embabel.plan.common.condition.WorldStateDeterminer
- Direction
- agent.spi.support uses plan.common.condition, so a change to plan.common.condition can break agent.spi.support, while a change to agent.spi.support can't break plan.common.condition.
- Position
- Below the diagonal: agent.spi.support uses a module listed above it, which is the healthy direction.
25→14 agent.spi.support uses chat✕
- Connections
- 6 pairs of types, where a type in agent.spi.support uses a type in chat.
- The types involved
com.embabel.agent.spi.support.AbstractLlmOperations→com.embabel.chat.Messagecom.embabel.agent.spi.support.MessagePromptBuildersKt→com.embabel.chat.Messagecom.embabel.agent.spi.support.SpringContextPlatformServices→com.embabel.chat.ConversationFactoryProvidercom.embabel.agent.spi.support.StructuredOutputLlmMessageSender→com.embabel.chat.Messagecom.embabel.agent.spi.support.ThinkingCapturingLlmMessageSender→com.embabel.chat.Messagecom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.chat.Message
- Direction
- agent.spi.support uses chat, so a change to chat can break agent.spi.support, while a change to agent.spi.support can't break chat.
- Position
- Below the diagonal: agent.spi.support uses a module listed above it, which is the healthy direction.
25→15 agent.spi.support uses agent.api.tool.callback✕
- Connections
- 1 pair of types, where a type in agent.spi.support uses a type in agent.api.tool.callback.
- The types involved
com.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.api.tool.callback.ToolLoopInspector
- Direction
- agent.spi.support uses agent.api.tool.callback, so a change to agent.api.tool.callback can break agent.spi.support, while a change to agent.spi.support can't break agent.api.tool.callback.
- Position
- Below the diagonal: agent.spi.support uses a module listed above it, which is the healthy direction.
25→16 agent.spi.support uses agent.spi.loop✕
- Connections
- 11 pairs of types, where a type in agent.spi.support uses a type in agent.spi.loop.
- The types involved
com.embabel.agent.spi.support.StructuredOutputLlmMessageSender→com.embabel.agent.spi.loop.LlmMessageResponsecom.embabel.agent.spi.support.StructuredOutputLlmMessageSender→com.embabel.agent.spi.loop.LlmMessageSendercom.embabel.agent.spi.support.StructuredOutputLlmMessageSender→com.embabel.agent.spi.loop.NativeStructuredOutputRequestcom.embabel.agent.spi.support.ThinkingCapturingLlmMessageSender→com.embabel.agent.spi.loop.LlmMessageResponsecom.embabel.agent.spi.support.ThinkingCapturingLlmMessageSender→com.embabel.agent.spi.loop.LlmMessageSendercom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.spi.loop.LlmMessageSendercom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.spi.loop.NativeStructuredOutputRequestcom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.spi.loop.ToolInjectionStrategycom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.spi.loop.ToolLoopcom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.spi.loop.ToolLoopFactorycom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.spi.loop.ToolLoopResult
- Direction
- agent.spi.support uses agent.spi.loop, so a change to agent.spi.loop can break agent.spi.support, while a change to agent.spi.support can't break agent.spi.loop.
- Position
- Below the diagonal: agent.spi.support uses a module listed above it, which is the healthy direction.
25→17 agent.spi.support uses agent.spi✕
- Connections
- 17 pairs of types, where a type in agent.spi.support uses a type in agent.spi.
- The types involved
com.embabel.agent.spi.support.AbstractLlmOperations→com.embabel.agent.spi.AutoLlmSelectionCriteriaResolvercom.embabel.agent.spi.support.AbstractLlmOperations→com.embabel.agent.spi.LlmServicecom.embabel.agent.spi.support.AbstractLlmOperations→com.embabel.agent.spi.ToolDecoratorcom.embabel.agent.spi.support.DefaultAgentProcessIdGenerator→com.embabel.agent.spi.AgentProcessIdGeneratorcom.embabel.agent.spi.support.DefaultPlannerFactory→com.embabel.agent.spi.PlannerFactorycom.embabel.agent.spi.support.DefaultToolDecorator→com.embabel.agent.spi.ToolDecoratorcom.embabel.agent.spi.support.DefaultToolDecorator→com.embabel.agent.spi.ToolGroupResolvercom.embabel.agent.spi.support.InMemoryContextRepository→com.embabel.agent.spi.ContextRepositorycom.embabel.agent.spi.support.ProcessOptionsOperationScheduler→com.embabel.agent.spi.ActionExecutionSchedulecom.embabel.agent.spi.support.ProcessOptionsOperationScheduler→com.embabel.agent.spi.OperationSchedulercom.embabel.agent.spi.support.ProcessOptionsOperationScheduler→com.embabel.agent.spi.ToolCallSchedulecom.embabel.agent.spi.support.RegistryToolGroupResolver→com.embabel.agent.spi.ToolGroupResolvercom.embabel.agent.spi.support.SpringContextPlatformServices→com.embabel.agent.spi.OperationSchedulercom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.spi.AutoLlmSelectionCriteriaResolvercom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.spi.LlmServicecom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.spi.ToolDecoratorcom.embabel.agent.spi.support.ToolResolutionHelper→com.embabel.agent.spi.ToolDecorator
- Direction
- agent.spi.support uses agent.spi, so a change to agent.spi can break agent.spi.support, while a change to agent.spi.support can't break agent.spi.
- Position
- Below the diagonal: agent.spi.support uses a module listed above it, which is the healthy direction.
25→18 agent.spi.support uses common.ai.model✕
- Connections
- 10 pairs of types, where a type in agent.spi.support uses a type in common.ai.model.
- The types involved
com.embabel.agent.spi.support.AbstractLlmOperations→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.spi.support.AbstractLlmOperations→com.embabel.common.ai.model.ModelProvidercom.embabel.agent.spi.support.DefaultToolDecorator→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.spi.support.EventPublishingTool→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.spi.support.LlmRanker→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.spi.support.SpringContextPlatformServices→com.embabel.common.ai.model.DecisionServiceRegistrycom.embabel.agent.spi.support.SpringContextPlatformServices→com.embabel.common.ai.model.ModelProvidercom.embabel.agent.spi.support.ToolDecoratorsKt→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.common.ai.model.ModelProvider
- Direction
- agent.spi.support uses common.ai.model, so a change to common.ai.model can break agent.spi.support, while a change to agent.spi.support can't break common.ai.model.
- Position
- Below the diagonal: agent.spi.support uses a module listed above it, which is the healthy direction.
25→19 agent.spi.support uses agent.api.tool✕
- Connections
- 26 pairs of types, where a type in agent.spi.support uses a type in agent.api.tool. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.embabel.agent.spi.support.AbstractLlmOperations→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.AgentProcessBindingTool→com.embabel.agent.api.tool.DelegatingToolcom.embabel.agent.spi.support.AgentProcessBindingTool→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.AgentProcessBindingTool→com.embabel.agent.api.tool.ToolCallContextcom.embabel.agent.spi.support.DefaultToolDecorator→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.EventPublishingTool→com.embabel.agent.api.tool.DelegatingToolcom.embabel.agent.spi.support.EventPublishingTool→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.EventPublishingTool→com.embabel.agent.api.tool.ToolCallContextcom.embabel.agent.spi.support.ExceptionSuppressingTool→com.embabel.agent.api.tool.DelegatingToolcom.embabel.agent.spi.support.ExceptionSuppressingTool→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.ExceptionSuppressingTool→com.embabel.agent.api.tool.ToolCallContextcom.embabel.agent.spi.support.MetadataEnrichingTool→com.embabel.agent.api.tool.DelegatingToolcom.embabel.agent.spi.support.MetadataEnrichingTool→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.MetadataEnrichingTool→com.embabel.agent.api.tool.ToolCallContextcom.embabel.agent.spi.support.ObservabilityTool→com.embabel.agent.api.tool.DelegatingToolcom.embabel.agent.spi.support.ObservabilityTool→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.ObservabilityTool→com.embabel.agent.api.tool.ToolCallContextcom.embabel.agent.spi.support.OutputTransformingTool→com.embabel.agent.api.tool.DelegatingToolcom.embabel.agent.spi.support.OutputTransformingTool→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.OutputTransformingTool→com.embabel.agent.api.tool.ToolCallContextcom.embabel.agent.spi.support.StructuredOutputLlmMessageSender→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.ThinkingCapturingLlmMessageSender→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.ToolDecoratorsKt→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.api.tool.ToolCallContext
- Direction
- agent.spi.support uses agent.api.tool, so a change to agent.api.tool can break agent.spi.support, while a change to agent.spi.support can't break agent.api.tool.
- Position
- Below the diagonal: agent.spi.support uses a module listed above it, which is the healthy direction.
25→23 agent.spi.support uses agent.spi.config.spring✕
- Connections
- 3 pairs of types, where a type in agent.spi.support uses a type in agent.spi.config.spring.
- The types involved
com.embabel.agent.spi.support.DefaultProcessIdGeneratorProperties→com.embabel.agent.spi.config.spring.AgentPlatformPropertiescom.embabel.agent.spi.support.InMemoryAgentProcessRepository→com.embabel.agent.spi.config.spring.ProcessRepositoryPropertiescom.embabel.agent.spi.support.InMemoryContextRepository→com.embabel.agent.spi.config.spring.ContextRepositoryProperties
- Direction
- agent.spi.support uses agent.spi.config.spring, so a change to agent.spi.config.spring can break agent.spi.support, while a change to agent.spi.support can't break agent.spi.config.spring.
- Position
- Below the diagonal: agent.spi.support uses a module listed above it, which is the healthy direction.
25→24 agent.spi.support uses agent.api.common.autonomy✕
- Connections
- 1 pair of types, where a type in agent.spi.support uses a type in agent.api.common.autonomy.
- The types involved
com.embabel.agent.spi.support.SpringContextPlatformServices→com.embabel.agent.api.common.autonomy.Autonomy
- Direction
- agent.spi.support uses agent.api.common.autonomy, so a change to agent.api.common.autonomy can break agent.spi.support, while a change to agent.spi.support can't break agent.api.common.autonomy.
- Position
- Below the diagonal: agent.spi.support uses a module listed above it, which is the healthy direction.
25→26 agent.spi.support uses agent.core.support part of a loop✕
- Connections
- 4 pairs of types, where a type in agent.spi.support uses a type in agent.core.support.
- The types involved
com.embabel.agent.spi.support.AbstractLlmOperations→com.embabel.agent.core.support.LlmInteractioncom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.core.support.LlmCallcom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.core.support.LlmInteractioncom.embabel.agent.spi.support.ToolResolutionHelper→com.embabel.agent.core.support.LlmInteraction
- Direction
- agent.spi.support uses agent.core.support, so a change to agent.core.support can break agent.spi.support, while a change to agent.spi.support can't break agent.core.support.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→27 agent.spi.support uses agent.api.event part of a loop✕
- Connections
- 9 pairs of types, where a type in agent.spi.support uses a type in agent.api.event.
- The types involved
com.embabel.agent.spi.support.AbstractLlmOperations→com.embabel.agent.api.event.LlmRequestEventcom.embabel.agent.spi.support.AgenticEventListenerToolsStats→com.embabel.agent.api.event.AgentProcessEventcom.embabel.agent.spi.support.AgenticEventListenerToolsStats→com.embabel.agent.api.event.AgenticEventListenercom.embabel.agent.spi.support.AgenticEventListenerToolsStats→com.embabel.agent.api.event.ToolCallResponseEventcom.embabel.agent.spi.support.ProcessOptionsOperationScheduler→com.embabel.agent.api.event.ActionExecutionStartEventcom.embabel.agent.spi.support.ProcessOptionsOperationScheduler→com.embabel.agent.api.event.ToolCallRequestEventcom.embabel.agent.spi.support.SpringContextPlatformServices→com.embabel.agent.api.event.AgenticEventListenercom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.api.event.LlmRequestEventcom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.api.event.ToolLoopStartEvent
- Direction
- agent.spi.support uses agent.api.event, so a change to agent.api.event can break agent.spi.support, while a change to agent.spi.support can't break agent.api.event.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→28 agent.spi.support uses agent.core part of a loop✕
- Connections
- 31 pairs of types, where a type in agent.spi.support uses a type in agent.core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.embabel.agent.spi.support.AbstractLlmOperations→com.embabel.agent.core.Actioncom.embabel.agent.spi.support.AbstractLlmOperations→com.embabel.agent.core.AgentProcesscom.embabel.agent.spi.support.AgentProcessAccessor→com.embabel.agent.core.AgentProcesscom.embabel.agent.spi.support.AgentProcessBindingTool→com.embabel.agent.core.AgentProcesscom.embabel.agent.spi.support.AgentScanningPostProcessorDelegate→com.embabel.agent.core.AgentPlatformcom.embabel.agent.spi.support.DefaultAgentProcessIdGenerator→com.embabel.agent.core.Agentcom.embabel.agent.spi.support.DefaultAgentProcessIdGenerator→com.embabel.agent.core.ProcessOptionscom.embabel.agent.spi.support.DefaultPlannerFactory→com.embabel.agent.core.ProcessOptionscom.embabel.agent.spi.support.DefaultToolDecorator→com.embabel.agent.core.Actioncom.embabel.agent.spi.support.DefaultToolDecorator→com.embabel.agent.core.AgentProcesscom.embabel.agent.spi.support.EventPublishingTool→com.embabel.agent.core.Actioncom.embabel.agent.spi.support.EventPublishingTool→com.embabel.agent.core.AgentProcesscom.embabel.agent.spi.support.HierarchyAwareEvictionPolicy→com.embabel.agent.core.AgentProcesscom.embabel.agent.spi.support.InMemoryAgentProcessRepository→com.embabel.agent.core.AbstractAgentProcessRepositorycom.embabel.agent.spi.support.InMemoryAgentProcessRepository→com.embabel.agent.core.AgentProcesscom.embabel.agent.spi.support.InMemoryContext→com.embabel.agent.core.Blackboardcom.embabel.agent.spi.support.InMemoryContext→com.embabel.agent.core.Contextcom.embabel.agent.spi.support.InMemoryContextRepository→com.embabel.agent.core.Contextcom.embabel.agent.spi.support.MetadataEnrichingTool→com.embabel.agent.core.ToolGroupMetadatacom.embabel.agent.spi.support.ProcessOptionsOperationScheduler→com.embabel.agent.core.Delaycom.embabel.agent.spi.support.RegistryToolGroupResolver→com.embabel.agent.core.ToolGroupcom.embabel.agent.spi.support.RegistryToolGroupResolver→com.embabel.agent.core.ToolGroupMetadatacom.embabel.agent.spi.support.RegistryToolGroupResolver→com.embabel.agent.core.ToolGroupRequirementcom.embabel.agent.spi.support.RegistryToolGroupResolver→com.embabel.agent.core.ToolGroupResolutioncom.embabel.agent.spi.support.SpringContextPlatformServices→com.embabel.agent.core.AgentPlatform
- Direction
- agent.spi.support uses agent.core, so a change to agent.core can break agent.spi.support, while a change to agent.spi.support can't break agent.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→29 agent.spi.support uses agent.api.channel part of a loop✕
- Connections
- 1 pair of types, where a type in agent.spi.support uses a type in agent.api.channel.
- The types involved
com.embabel.agent.spi.support.SpringContextPlatformServices→com.embabel.agent.api.channel.OutputChannel
- Direction
- agent.spi.support uses agent.api.channel, so a change to agent.api.channel can break agent.spi.support, while a change to agent.spi.support can't break agent.api.channel.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→31 agent.spi.support uses agent.api.common part of a loop✕
- Connections
- 7 pairs of types, where a type in agent.spi.support uses a type in agent.api.common.
- The types involved
com.embabel.agent.spi.support.AbstractLlmOperations→com.embabel.agent.api.common.Asyncercom.embabel.agent.spi.support.AgenticEventListenerToolsStats→com.embabel.agent.api.common.ToolStatscom.embabel.agent.spi.support.AgenticEventListenerToolsStats→com.embabel.agent.api.common.ToolsStatscom.embabel.agent.spi.support.ExecutorAsyncer→com.embabel.agent.api.common.Asyncercom.embabel.agent.spi.support.SpringContextPlatformServices→com.embabel.agent.api.common.Asyncercom.embabel.agent.spi.support.SpringContextPlatformServices→com.embabel.agent.api.common.PlatformServicescom.embabel.agent.spi.support.ToolLoopLlmOperations→com.embabel.agent.api.common.Asyncer
- Direction
- agent.spi.support uses agent.api.common, so a change to agent.api.common can break agent.spi.support, while a change to agent.spi.support can't break agent.api.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→32 agent.spi.support uses agent.api.annotation.support part of a loop✕
- Connections
- 1 pair of types, where a type in agent.spi.support uses a type in agent.api.annotation.support.
- The types involved
com.embabel.agent.spi.support.AgentScanningPostProcessorDelegate→com.embabel.agent.api.annotation.support.AgentMetadataReader
- Direction
- agent.spi.support uses agent.api.annotation.support, so a change to agent.api.annotation.support can break agent.spi.support, while a change to agent.spi.support can't break agent.api.annotation.support.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→2 agent.core.support uses common.ai.prompt✕
- Connections
- 3 pairs of types, where a type in agent.core.support uses a type in common.ai.prompt.
- The types involved
com.embabel.agent.core.support.LlmCallImpl→com.embabel.common.ai.prompt.PromptContributorcom.embabel.agent.core.support.LlmInteraction→com.embabel.common.ai.prompt.PromptContributorcom.embabel.agent.core.support.LlmUse→com.embabel.common.ai.prompt.PromptContributorConsumer
- Direction
- agent.core.support uses common.ai.prompt, so a change to common.ai.prompt can break agent.core.support, while a change to agent.core.support can't break common.ai.prompt.
- Position
- Below the diagonal: agent.core.support uses a module listed above it, which is the healthy direction.
26→3 agent.core.support uses common.util✕
- Connections
- 1 pair of types, where a type in agent.core.support uses a type in common.util.
- The types involved
com.embabel.agent.core.support.DefaultAgentPlatform→com.embabel.common.util.EmbabelObjectMapperHolder
- Direction
- agent.core.support uses common.util, so a change to common.util can break agent.core.support, while a change to agent.core.support can't break common.util.
- Position
- Below the diagonal: agent.core.support uses a module listed above it, which is the healthy direction.
26→4 agent.core.support uses plan✕
- Connections
- 7 pairs of types, where a type in agent.core.support uses a type in plan.
- The types involved
com.embabel.agent.core.support.AbstractAction→com.embabel.plan.WorldStatecom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.plan.Goalcom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.plan.WorldStatecom.embabel.agent.core.support.ConcurrentAgentProcess→com.embabel.plan.WorldStatecom.embabel.agent.core.support.SimpleAgentProcess→com.embabel.plan.Plancom.embabel.agent.core.support.SimpleAgentProcess→com.embabel.plan.Plannercom.embabel.agent.core.support.SimpleAgentProcess→com.embabel.plan.WorldState
- Direction
- agent.core.support uses plan, so a change to plan can break agent.core.support, while a change to agent.core.support can't break plan.
- Position
- Below the diagonal: agent.core.support uses a module listed above it, which is the healthy direction.
26→5 agent.core.support uses agent.api.tool.Tool✕
- Connections
- 2 pairs of types, where a type in agent.core.support uses a type in agent.api.tool.Tool.
- The types involved
com.embabel.agent.core.support.RenamedTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.core.support.RenamedTool→com.embabel.agent.api.tool.Tool.Metadata
- Direction
- agent.core.support uses agent.api.tool.Tool, so a change to agent.api.tool.Tool can break agent.core.support, while a change to agent.core.support can't break agent.api.tool.Tool.
- Position
- Below the diagonal: agent.core.support uses a module listed above it, which is the healthy direction.
26→6 agent.core.support uses agent.core.internal✕
- Connections
- 1 pair of types, where a type in agent.core.support uses a type in agent.core.internal.
- The types involved
com.embabel.agent.core.support.DefaultAgentPlatform→com.embabel.agent.core.internal.LlmOperations
- Direction
- agent.core.support uses agent.core.internal, so a change to agent.core.internal can break agent.core.support, while a change to agent.core.support can't break agent.core.internal.
- Position
- Below the diagonal: agent.core.support uses a module listed above it, which is the healthy direction.
26→8 agent.core.support uses plan.common.condition✕
- Connections
- 6 pairs of types, where a type in agent.core.support uses a type in plan.common.condition.
- The types involved
com.embabel.agent.core.support.AbstractAction→com.embabel.plan.common.condition.ConditionDeterminationcom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.plan.common.condition.WorldStateDeterminercom.embabel.agent.core.support.BlackboardWorldState→com.embabel.plan.common.condition.ConditionWorldStatecom.embabel.agent.core.support.BlackboardWorldStateDeterminer→com.embabel.plan.common.condition.ConditionDeterminationcom.embabel.agent.core.support.BlackboardWorldStateDeterminer→com.embabel.plan.common.condition.WorldStateDeterminercom.embabel.agent.core.support.SimpleAgentProcess→com.embabel.plan.common.condition.WorldStateDeterminer
- Direction
- agent.core.support uses plan.common.condition, so a change to plan.common.condition can break agent.core.support, while a change to agent.core.support can't break plan.common.condition.
- Position
- Below the diagonal: agent.core.support uses a module listed above it, which is the healthy direction.
26→15 agent.core.support uses agent.api.tool.callback✕
- Connections
- 3 pairs of types, where a type in agent.core.support uses a type in agent.api.tool.callback.
- The types involved
com.embabel.agent.core.support.LlmInteraction→com.embabel.agent.api.tool.callback.ToolCallInspectorcom.embabel.agent.core.support.LlmInteraction→com.embabel.agent.api.tool.callback.ToolLoopInspectorcom.embabel.agent.core.support.LlmInteraction→com.embabel.agent.api.tool.callback.ToolLoopTransformer
- Direction
- agent.core.support uses agent.api.tool.callback, so a change to agent.api.tool.callback can break agent.core.support, while a change to agent.core.support can't break agent.api.tool.callback.
- Position
- Below the diagonal: agent.core.support uses a module listed above it, which is the healthy direction.
26→16 agent.core.support uses agent.spi.loop✕
- Connections
- 2 pairs of types, where a type in agent.core.support uses a type in agent.spi.loop.
- The types involved
com.embabel.agent.core.support.LlmInteraction→com.embabel.agent.spi.loop.ToolInjectionStrategycom.embabel.agent.core.support.LlmInteraction→com.embabel.agent.spi.loop.ToolNotFoundPolicy
- Direction
- agent.core.support uses agent.spi.loop, so a change to agent.spi.loop can break agent.core.support, while a change to agent.core.support can't break agent.spi.loop.
- Position
- Below the diagonal: agent.core.support uses a module listed above it, which is the healthy direction.
26→17 agent.core.support uses agent.spi✕
- Connections
- 9 pairs of types, where a type in agent.core.support uses a type in agent.spi.
- The types involved
com.embabel.agent.core.support.ConcurrentAgentProcess→com.embabel.agent.spi.PlannerFactorycom.embabel.agent.core.support.DefaultAgentPlatform→com.embabel.agent.spi.AgentProcessIdGeneratorcom.embabel.agent.core.support.DefaultAgentPlatform→com.embabel.agent.spi.BlackboardProvidercom.embabel.agent.core.support.DefaultAgentPlatform→com.embabel.agent.spi.ContextRepositorycom.embabel.agent.core.support.DefaultAgentPlatform→com.embabel.agent.spi.OperationSchedulercom.embabel.agent.core.support.DefaultAgentPlatform→com.embabel.agent.spi.PlannerFactorycom.embabel.agent.core.support.DefaultAgentPlatform→com.embabel.agent.spi.ToolGroupResolvercom.embabel.agent.core.support.InMemoryBlackboardProvider→com.embabel.agent.spi.BlackboardProvidercom.embabel.agent.core.support.SimpleAgentProcess→com.embabel.agent.spi.PlannerFactory
- Direction
- agent.core.support uses agent.spi, so a change to agent.spi can break agent.core.support, while a change to agent.core.support can't break agent.spi.
- Position
- Below the diagonal: agent.core.support uses a module listed above it, which is the healthy direction.
26→18 agent.core.support uses common.ai.model✕
- Connections
- 5 pairs of types, where a type in agent.core.support uses a type in common.ai.model.
- The types involved
com.embabel.agent.core.support.AbstractAgentProcess→com.embabel.common.ai.model.EmbeddingServiceMetadatacom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.common.ai.model.LlmMetadatacom.embabel.agent.core.support.LlmCallImpl→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.core.support.LlmInteraction→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.core.support.LlmUse→com.embabel.common.ai.model.LlmOptions
- Direction
- agent.core.support uses common.ai.model, so a change to common.ai.model can break agent.core.support, while a change to agent.core.support can't break common.ai.model.
- Position
- Below the diagonal: agent.core.support uses a module listed above it, which is the healthy direction.
26→19 agent.core.support uses agent.api.tool✕
- Connections
- 8 pairs of types, where a type in agent.core.support uses a type in agent.api.tool.
- The types involved
com.embabel.agent.core.support.ExternalToolExtractor→com.embabel.agent.api.tool.Toolcom.embabel.agent.core.support.LlmCallImpl→com.embabel.agent.api.tool.Toolcom.embabel.agent.core.support.LlmInteraction→com.embabel.agent.api.tool.Toolcom.embabel.agent.core.support.LlmInteraction→com.embabel.agent.api.tool.ToolCallContextcom.embabel.agent.core.support.RenamedTool→com.embabel.agent.api.tool.DelegatingToolcom.embabel.agent.core.support.RenamedTool→com.embabel.agent.api.tool.Toolcom.embabel.agent.core.support.ToolUtilsKt→com.embabel.agent.api.tool.Toolcom.embabel.agent.core.support.ToolUtilsKt→com.embabel.agent.api.tool.ToolObject
- Direction
- agent.core.support uses agent.api.tool, so a change to agent.api.tool can break agent.core.support, while a change to agent.core.support can't break agent.api.tool.
- Position
- Below the diagonal: agent.core.support uses a module listed above it, which is the healthy direction.
26→25 agent.core.support uses agent.spi.support✕
- Connections
- 1 pair of types, where a type in agent.core.support uses a type in agent.spi.support.
- The types involved
com.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.spi.support.AgenticEventListenerToolsStats
- Direction
- agent.core.support uses agent.spi.support, so a change to agent.spi.support can break agent.core.support, while a change to agent.core.support can't break agent.spi.support.
- Position
- Below the diagonal: agent.core.support uses a module listed above it, which is the healthy direction.
26→27 agent.core.support uses agent.api.event part of a loop✕
- Connections
- 2 pairs of types, where a type in agent.core.support uses a type in agent.api.event.
- The types involved
com.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.api.event.ProcessKilledEventcom.embabel.agent.core.support.DefaultAgentPlatform→com.embabel.agent.api.event.AgenticEventListener
- Direction
- agent.core.support uses agent.api.event, so a change to agent.api.event can break agent.core.support, while a change to agent.core.support can't break agent.api.event.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→28 agent.core.support uses agent.core part of a loop✕
- Connections
- 52 pairs of types, where a type in agent.core.support uses a type in agent.core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.embabel.agent.core.support.AbstractAction→com.embabel.agent.core.Actioncom.embabel.agent.core.support.AbstractAction→com.embabel.agent.core.ActionQoscom.embabel.agent.core.support.AbstractAction→com.embabel.agent.core.IoBindingcom.embabel.agent.core.support.AbstractAction→com.embabel.agent.core.ToolGroupRequirementcom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.core.Actioncom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.core.ActionInvocationcom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.core.ActionStatuscom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.core.Agentcom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.core.AgentProcesscom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.core.AgentProcessStatusCodecom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.core.Bindablecom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.core.Blackboardcom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.core.EarlyTerminationcom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.core.EmbeddingInvocationcom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.core.LlmInvocationcom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.core.ProcessContextcom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.core.ProcessOptionscom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.core.Usagecom.embabel.agent.core.support.ActionQosExtensionsKt→com.embabel.agent.core.Actioncom.embabel.agent.core.support.BlackboardWorldState→com.embabel.agent.core.Blackboardcom.embabel.agent.core.support.BlackboardWorldStateDeterminer→com.embabel.agent.core.Conditioncom.embabel.agent.core.support.BlackboardWorldStateDeterminer→com.embabel.agent.core.ProcessContextcom.embabel.agent.core.support.ConcurrentAgentProcess→com.embabel.agent.core.ActionStatuscom.embabel.agent.core.support.ConcurrentAgentProcess→com.embabel.agent.core.Agentcom.embabel.agent.core.support.ConcurrentAgentProcess→com.embabel.agent.core.AgentProcess
- Direction
- agent.core.support uses agent.core, so a change to agent.core can break agent.core.support, while a change to agent.core.support can't break agent.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→29 agent.core.support uses agent.api.channel part of a loop✕
- Connections
- 1 pair of types, where a type in agent.core.support uses a type in agent.api.channel.
- The types involved
com.embabel.agent.core.support.DefaultAgentPlatform→com.embabel.agent.api.channel.OutputChannel
- Direction
- agent.core.support uses agent.api.channel, so a change to agent.api.channel can break agent.core.support, while a change to agent.core.support can't break agent.api.channel.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→31 agent.core.support uses agent.api.common part of a loop✕
- Connections
- 11 pairs of types, where a type in agent.core.support uses a type in agent.api.common.
- The types involved
com.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.api.common.PlatformServicescom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.api.common.TerminationSignalcom.embabel.agent.core.support.AbstractAgentProcess→com.embabel.agent.api.common.ToolsStatscom.embabel.agent.core.support.ConcurrentAgentProcess→com.embabel.agent.api.common.PlatformServicescom.embabel.agent.core.support.DefaultAgentPlatform→com.embabel.agent.api.common.Asyncercom.embabel.agent.core.support.DefaultAgentPlatform→com.embabel.agent.api.common.PlatformServicescom.embabel.agent.core.support.LlmCall→com.embabel.agent.api.common.ContextualPromptElementcom.embabel.agent.core.support.LlmCallImpl→com.embabel.agent.api.common.ContextualPromptElementcom.embabel.agent.core.support.LlmInteraction→com.embabel.agent.api.common.ContextualPromptElementcom.embabel.agent.core.support.LlmInteraction→com.embabel.agent.api.common.InteractionIdcom.embabel.agent.core.support.SimpleAgentProcess→com.embabel.agent.api.common.PlatformServices
- Direction
- agent.core.support uses agent.api.common, so a change to agent.api.common can break agent.core.support, while a change to agent.core.support can't break agent.api.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→4 agent.api.event uses plan✕
- Connections
- 5 pairs of types, where a type in agent.api.event uses a type in plan.
- The types involved
com.embabel.agent.api.event.AgentProcessPlanFormulatedEvent→com.embabel.plan.Plancom.embabel.agent.api.event.AgentProcessPlanFormulatedEvent→com.embabel.plan.WorldStatecom.embabel.agent.api.event.AgentProcessReadyToPlanEvent→com.embabel.plan.WorldStatecom.embabel.agent.api.event.GoalAchievedEvent→com.embabel.plan.Goalcom.embabel.agent.api.event.GoalAchievedEvent→com.embabel.plan.WorldState
- Direction
- agent.api.event uses plan, so a change to plan can break agent.api.event, while a change to agent.api.event can't break plan.
- Position
- Below the diagonal: agent.api.event uses a module listed above it, which is the healthy direction.
27→14 agent.api.event uses chat✕
- Connections
- 1 pair of types, where a type in agent.api.event uses a type in chat.
- The types involved
com.embabel.agent.api.event.LlmRequestEvent→com.embabel.chat.Message
- Direction
- agent.api.event uses chat, so a change to chat can break agent.api.event, while a change to agent.api.event can't break chat.
- Position
- Below the diagonal: agent.api.event uses a module listed above it, which is the healthy direction.
27→18 agent.api.event uses common.ai.model✕
- Connections
- 5 pairs of types, where a type in agent.api.event uses a type in common.ai.model.
- The types involved
com.embabel.agent.api.event.EmbeddingEvent→com.embabel.common.ai.model.EmbeddingServiceMetadatacom.embabel.agent.api.event.EmbeddingRequestEvent→com.embabel.common.ai.model.EmbeddingServiceMetadatacom.embabel.agent.api.event.EmbeddingResponseEvent→com.embabel.common.ai.model.EmbeddingServiceMetadatacom.embabel.agent.api.event.LlmRequestEvent→com.embabel.common.ai.model.LlmMetadatacom.embabel.agent.api.event.ToolCallRequestEvent→com.embabel.common.ai.model.LlmOptions
- Direction
- agent.api.event uses common.ai.model, so a change to common.ai.model can break agent.api.event, while a change to agent.api.event can't break common.ai.model.
- Position
- Below the diagonal: agent.api.event uses a module listed above it, which is the healthy direction.
27→26 agent.api.event uses agent.core.support✕
- Connections
- 1 pair of types, where a type in agent.api.event uses a type in agent.core.support.
- The types involved
com.embabel.agent.api.event.LlmRequestEvent→com.embabel.agent.core.support.LlmInteraction
- Direction
- agent.api.event uses agent.core.support, so a change to agent.core.support can break agent.api.event, while a change to agent.api.event can't break agent.core.support.
- Position
- Below the diagonal: agent.api.event uses a module listed above it, which is the healthy direction.
27→28 agent.api.event uses agent.core part of a loop✕
- Connections
- 52 pairs of types, where a type in agent.api.event uses a type in agent.core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.embabel.agent.api.event.AbstractAgentProcessEvent→com.embabel.agent.core.ActionInvocationcom.embabel.agent.api.event.AbstractAgentProcessEvent→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.event.AbstractAgentProcessEvent→com.embabel.agent.core.AgentProcessStatusReportcom.embabel.agent.api.event.ActionExecutionResultEvent→com.embabel.agent.core.Actioncom.embabel.agent.api.event.ActionExecutionResultEvent→com.embabel.agent.core.ActionStatuscom.embabel.agent.api.event.ActionExecutionResultEvent→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.event.ActionExecutionStartEvent→com.embabel.agent.core.Actioncom.embabel.agent.api.event.ActionExecutionStartEvent→com.embabel.agent.core.ActionStatuscom.embabel.agent.api.event.ActionExecutionStartEvent→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.event.AgentDeploymentEvent→com.embabel.agent.core.Agentcom.embabel.agent.api.event.AgentDeploymentEvent→com.embabel.agent.core.AgentPlatformcom.embabel.agent.api.event.AgentPlatformEvent→com.embabel.agent.core.AgentPlatformcom.embabel.agent.api.event.AgentProcessCompletedEvent→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.event.AgentProcessCreationEvent→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.event.AgentProcessEmbeddingEvent→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.event.AgentProcessEvent→com.embabel.agent.core.InProcesscom.embabel.agent.api.event.AgentProcessFailedEvent→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.event.AgentProcessFinishedEvent→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.event.AgentProcessPausedEvent→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.event.AgentProcessPlanFormulatedEvent→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.event.AgentProcessReadyToPlanEvent→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.event.AgentProcessStuckEvent→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.event.AgentProcessTerminatedEvent→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.event.AgentProcessWaitingEvent→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.event.DynamicAgentCreationEvent→com.embabel.agent.core.Agent
- Direction
- agent.api.event uses agent.core, so a change to agent.core can break agent.api.event, while a change to agent.api.event can't break agent.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→1 agent.core uses agent.spi.common✕
- Connections
- 1 pair of types, where a type in agent.core uses a type in agent.spi.common.
- The types involved
com.embabel.agent.core.ActionQos→com.embabel.agent.spi.common.RetryProperties
- Direction
- agent.core uses agent.spi.common, so a change to agent.spi.common can break agent.core, while a change to agent.core can't break agent.spi.common.
- Position
- Below the diagonal: agent.core uses a module listed above it, which is the healthy direction.
28→4 agent.core uses plan✕
- Connections
- 5 pairs of types, where a type in agent.core uses a type in plan.
- The types involved
com.embabel.agent.core.Agent→com.embabel.plan.PlanningSystemcom.embabel.agent.core.AgentProcess→com.embabel.plan.Goalcom.embabel.agent.core.AgentProcess→com.embabel.plan.Plannercom.embabel.agent.core.AgentProcess→com.embabel.plan.WorldStatecom.embabel.agent.core.Goal→com.embabel.plan.WorldState
- Direction
- agent.core uses plan, so a change to plan can break agent.core, while a change to agent.core can't break plan.
- Position
- Below the diagonal: agent.core uses a module listed above it, which is the healthy direction.
28→6 agent.core uses agent.core.internal✕
- Connections
- 1 pair of types, where a type in agent.core uses a type in agent.core.internal.
- The types involved
com.embabel.agent.core.ProcessContext→com.embabel.agent.core.internal.LlmOperations
- Direction
- agent.core uses agent.core.internal, so a change to agent.core.internal can break agent.core, while a change to agent.core can't break agent.core.internal.
- Position
- Below the diagonal: agent.core uses a module listed above it, which is the healthy direction.
28→8 agent.core uses plan.common.condition✕
- Connections
- 12 pairs of types, where a type in agent.core uses a type in plan.common.condition.
- The types involved
com.embabel.agent.core.Action→com.embabel.plan.common.condition.ConditionActioncom.embabel.agent.core.ActionMetadata→com.embabel.plan.common.condition.ConditionDeterminationcom.embabel.agent.core.Agent→com.embabel.plan.common.condition.ConditionPlanningSystemcom.embabel.agent.core.AgentSystemStep→com.embabel.plan.common.condition.ConditionStepcom.embabel.agent.core.AndCondition→com.embabel.plan.common.condition.ConditionDeterminationcom.embabel.agent.core.ComputedBooleanCondition→com.embabel.plan.common.condition.ConditionDeterminationcom.embabel.agent.core.Condition→com.embabel.plan.common.condition.ConditionDeterminationcom.embabel.agent.core.Goal→com.embabel.plan.common.condition.ConditionDeterminationcom.embabel.agent.core.Goal→com.embabel.plan.common.condition.ConditionGoalcom.embabel.agent.core.NotCondition→com.embabel.plan.common.condition.ConditionDeterminationcom.embabel.agent.core.OrCondition→com.embabel.plan.common.condition.ConditionDeterminationcom.embabel.agent.core.UnknownCondition→com.embabel.plan.common.condition.ConditionDetermination
- Direction
- agent.core uses plan.common.condition, so a change to plan.common.condition can break agent.core, while a change to agent.core can't break plan.common.condition.
- Position
- Below the diagonal: agent.core uses a module listed above it, which is the healthy direction.
28→17 agent.core uses agent.spi✕
- Connections
- 2 pairs of types, where a type in agent.core uses a type in agent.spi.
- The types involved
com.embabel.agent.core.AgentPlatform→com.embabel.agent.spi.ToolGroupResolvercom.embabel.agent.core.ToolConsumer→com.embabel.agent.spi.ToolGroupResolver
- Direction
- agent.core uses agent.spi, so a change to agent.spi can break agent.core, while a change to agent.core can't break agent.spi.
- Position
- Below the diagonal: agent.core uses a module listed above it, which is the healthy direction.
28→18 agent.core uses common.ai.model✕
- Connections
- 6 pairs of types, where a type in agent.core uses a type in common.ai.model.
- The types involved
com.embabel.agent.core.AgentProcess→com.embabel.common.ai.model.LlmMetadatacom.embabel.agent.core.AgentProcess→com.embabel.common.ai.model.ModelMetadatacom.embabel.agent.core.EmbeddingInvocation→com.embabel.common.ai.model.EmbeddingServiceMetadatacom.embabel.agent.core.EmbeddingInvocationHistory→com.embabel.common.ai.model.EmbeddingServiceMetadatacom.embabel.agent.core.LlmInvocation→com.embabel.common.ai.model.LlmMetadatacom.embabel.agent.core.LlmInvocationHistory→com.embabel.common.ai.model.LlmMetadata
- Direction
- agent.core uses common.ai.model, so a change to common.ai.model can break agent.core, while a change to agent.core can't break common.ai.model.
- Position
- Below the diagonal: agent.core uses a module listed above it, which is the healthy direction.
28→19 agent.core uses agent.api.tool✕
- Connections
- 6 pairs of types, where a type in agent.core uses a type in agent.api.tool.
- The types involved
com.embabel.agent.core.ProcessOptions→com.embabel.agent.api.tool.ToolCallContextcom.embabel.agent.core.ReplanRequestedException→com.embabel.agent.api.tool.ToolControlFlowSignalcom.embabel.agent.core.ToolConsumer→com.embabel.agent.api.tool.Toolcom.embabel.agent.core.ToolGroup→com.embabel.agent.api.tool.Toolcom.embabel.agent.core.ToolGroupImpl→com.embabel.agent.api.tool.Toolcom.embabel.agent.core.ToolSpec→com.embabel.agent.api.tool.Tool
- Direction
- agent.core uses agent.api.tool, so a change to agent.api.tool can break agent.core, while a change to agent.core can't break agent.api.tool.
- Position
- Below the diagonal: agent.core uses a module listed above it, which is the healthy direction.
28→27 agent.core uses agent.api.event✕
- Connections
- 4 pairs of types, where a type in agent.core uses a type in agent.api.event.
- The types involved
com.embabel.agent.core.AgentProcess→com.embabel.agent.api.event.ProcessKilledEventcom.embabel.agent.core.EarlyTermination→com.embabel.agent.api.event.AbstractAgentProcessEventcom.embabel.agent.core.ProcessContext→com.embabel.agent.api.event.AgenticEventListenercom.embabel.agent.core.ProcessOptions→com.embabel.agent.api.event.AgenticEventListener
- Direction
- agent.core uses agent.api.event, so a change to agent.api.event can break agent.core, while a change to agent.core can't break agent.api.event.
- Position
- Below the diagonal: agent.core uses a module listed above it, which is the healthy direction.
28→29 agent.core uses agent.api.channel part of a loop✕
- Connections
- 2 pairs of types, where a type in agent.core uses a type in agent.api.channel.
- The types involved
com.embabel.agent.core.ProcessContext→com.embabel.agent.api.channel.OutputChannelcom.embabel.agent.core.ProcessOptions→com.embabel.agent.api.channel.OutputChannel
- Direction
- agent.core uses agent.api.channel, so a change to agent.api.channel can break agent.core, while a change to agent.core can't break agent.api.channel.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→31 agent.core uses agent.api.common part of a loop✕
- Connections
- 14 pairs of types, where a type in agent.core uses a type in agent.api.common.
- The types involved
com.embabel.agent.core.Agent→com.embabel.agent.api.common.StuckHandlercom.embabel.agent.core.AgentPlatform→com.embabel.agent.api.common.PlatformServicescom.embabel.agent.core.AgentScope→com.embabel.agent.api.common.StuckHandlercom.embabel.agent.core.AgentScopeImpl→com.embabel.agent.api.common.StuckHandlercom.embabel.agent.core.AndCondition→com.embabel.agent.api.common.OperationContextcom.embabel.agent.core.ComputedBooleanCondition→com.embabel.agent.api.common.OperationContextcom.embabel.agent.core.Condition→com.embabel.agent.api.common.OperationContextcom.embabel.agent.core.LlmInvocationHistory→com.embabel.agent.api.common.ToolsStatscom.embabel.agent.core.NotCondition→com.embabel.agent.api.common.OperationContextcom.embabel.agent.core.OrCondition→com.embabel.agent.api.common.OperationContextcom.embabel.agent.core.ProcessContext→com.embabel.agent.api.common.PlatformServicescom.embabel.agent.core.ProcessOptions→com.embabel.agent.api.common.PlannerTypecom.embabel.agent.core.ToolGroupRequirement→com.embabel.agent.api.common.TerminationScopecom.embabel.agent.core.UnknownCondition→com.embabel.agent.api.common.OperationContext
- Direction
- agent.core uses agent.api.common, so a change to agent.api.common can break agent.core, while a change to agent.core can't break agent.api.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→14 agent.api.channel uses chat✕
- Connections
- 1 pair of types, where a type in agent.api.channel uses a type in chat.
- The types involved
com.embabel.agent.api.channel.MessageOutputChannelEvent→com.embabel.chat.Message
- Direction
- agent.api.channel uses chat, so a change to chat can break agent.api.channel, while a change to agent.api.channel can't break chat.
- Position
- Below the diagonal: agent.api.channel uses a module listed above it, which is the healthy direction.
29→28 agent.api.channel uses agent.core✕
- Connections
- 1 pair of types, where a type in agent.api.channel uses a type in agent.core.
- The types involved
com.embabel.agent.api.channel.OutputChannelEvent→com.embabel.agent.core.InProcess
- Direction
- agent.api.channel uses agent.core, so a change to agent.core can break agent.api.channel, while a change to agent.api.channel can't break agent.core.
- Position
- Below the diagonal: agent.api.channel uses a module listed above it, which is the healthy direction.
30→2 agent.api.dsl uses common.ai.prompt✕
- Connections
- 3 pairs of types, where a type in agent.api.dsl uses a type in common.ai.prompt.
- The types involved
com.embabel.agent.api.dsl.AgentBuilder→com.embabel.common.ai.prompt.PromptContributorcom.embabel.agent.api.dsl.AgentBuilder→com.embabel.common.ai.prompt.PromptContributorConsumercom.embabel.agent.api.dsl.AgentKt→com.embabel.common.ai.prompt.PromptContributor
- Direction
- agent.api.dsl uses common.ai.prompt, so a change to common.ai.prompt can break agent.api.dsl, while a change to agent.api.dsl can't break common.ai.prompt.
- Position
- Below the diagonal: agent.api.dsl uses a module listed above it, which is the healthy direction.
30→4 agent.api.dsl uses plan✕
- Connections
- 1 pair of types, where a type in agent.api.dsl uses a type in plan.
- The types involved
com.embabel.agent.api.dsl.AgentBuilder→com.embabel.plan.WorldState
- Direction
- agent.api.dsl uses plan, so a change to plan can break agent.api.dsl, while a change to agent.api.dsl can't break plan.
- Position
- Below the diagonal: agent.api.dsl uses a module listed above it, which is the healthy direction.
30→11 agent.api.dsl uses agent.api.common.support✕
- Connections
- 1 pair of types, where a type in agent.api.dsl uses a type in agent.api.common.support.
- The types involved
com.embabel.agent.api.dsl.TypedAgentScopeBuilderKt→com.embabel.agent.api.common.support.Branch
- Direction
- agent.api.dsl uses agent.api.common.support, so a change to agent.api.common.support can break agent.api.dsl, while a change to agent.api.dsl can't break agent.api.common.support.
- Position
- Below the diagonal: agent.api.dsl uses a module listed above it, which is the healthy direction.
30→18 agent.api.dsl uses common.ai.model✕
- Connections
- 1 pair of types, where a type in agent.api.dsl uses a type in common.ai.model.
- The types involved
com.embabel.agent.api.dsl.AgentBuilder→com.embabel.common.ai.model.LlmOptions
- Direction
- agent.api.dsl uses common.ai.model, so a change to common.ai.model can break agent.api.dsl, while a change to agent.api.dsl can't break common.ai.model.
- Position
- Below the diagonal: agent.api.dsl uses a module listed above it, which is the healthy direction.
30→19 agent.api.dsl uses agent.api.tool✕
- Connections
- 1 pair of types, where a type in agent.api.dsl uses a type in agent.api.tool.
- The types involved
com.embabel.agent.api.dsl.AgentBuilder→com.embabel.agent.api.tool.Tool
- Direction
- agent.api.dsl uses agent.api.tool, so a change to agent.api.tool can break agent.api.dsl, while a change to agent.api.dsl can't break agent.api.tool.
- Position
- Below the diagonal: agent.api.dsl uses a module listed above it, which is the healthy direction.
30→26 agent.api.dsl uses agent.core.support✕
- Connections
- 1 pair of types, where a type in agent.api.dsl uses a type in agent.core.support.
- The types involved
com.embabel.agent.api.dsl.AgentBuilder→com.embabel.agent.core.support.LlmCall
- Direction
- agent.api.dsl uses agent.core.support, so a change to agent.core.support can break agent.api.dsl, while a change to agent.api.dsl can't break agent.core.support.
- Position
- Below the diagonal: agent.api.dsl uses a module listed above it, which is the healthy direction.
30→28 agent.api.dsl uses agent.core✕
- Connections
- 15 pairs of types, where a type in agent.api.dsl uses a type in agent.core.
- The types involved
com.embabel.agent.api.dsl.AgentBuilder→com.embabel.agent.core.Actioncom.embabel.agent.api.dsl.AgentBuilder→com.embabel.agent.core.ActionQoscom.embabel.agent.api.dsl.AgentBuilder→com.embabel.agent.core.Agentcom.embabel.agent.api.dsl.AgentBuilder→com.embabel.agent.core.AgentScopecom.embabel.agent.api.dsl.AgentBuilder→com.embabel.agent.core.Conditioncom.embabel.agent.api.dsl.AgentBuilder→com.embabel.agent.core.Exportcom.embabel.agent.api.dsl.AgentBuilder→com.embabel.agent.core.Goalcom.embabel.agent.api.dsl.AgentBuilder→com.embabel.agent.core.IoBindingcom.embabel.agent.api.dsl.AgentBuilder→com.embabel.agent.core.ToolGroupRequirementcom.embabel.agent.api.dsl.AgentKt→com.embabel.agent.core.Agentcom.embabel.agent.api.dsl.TypedAgentScopeBuilder→com.embabel.agent.core.Actioncom.embabel.agent.api.dsl.TypedAgentScopeBuilder→com.embabel.agent.core.AgentScopecom.embabel.agent.api.dsl.TypedAgentScopeBuilder→com.embabel.agent.core.Conditioncom.embabel.agent.api.dsl.TypedAgentScopeBuilder→com.embabel.agent.core.Goalcom.embabel.agent.api.dsl.TypedAgentScopeBuilderKt→com.embabel.agent.core.Agent
- Direction
- agent.api.dsl uses agent.core, so a change to agent.core can break agent.api.dsl, while a change to agent.api.dsl can't break agent.core.
- Position
- Below the diagonal: agent.api.dsl uses a module listed above it, which is the healthy direction.
30→31 agent.api.dsl uses agent.api.common part of a loop✕
- Connections
- 11 pairs of types, where a type in agent.api.dsl uses a type in agent.api.common.
- The types involved
com.embabel.agent.api.dsl.AgentBuilder→com.embabel.agent.api.common.OperationContextcom.embabel.agent.api.dsl.AgentBuilder→com.embabel.agent.api.common.Transformationcom.embabel.agent.api.dsl.AgentBuilder→com.embabel.agent.api.common.TransformationActionContextcom.embabel.agent.api.dsl.BiInputActionContext→com.embabel.agent.api.common.ActionContextcom.embabel.agent.api.dsl.BiInputActionContext→com.embabel.agent.api.common.InputsActionContextcom.embabel.agent.api.dsl.MapperKt→com.embabel.agent.api.common.OperationContextcom.embabel.agent.api.dsl.TypedAgentScopeBuilder→com.embabel.agent.api.common.ActionContextcom.embabel.agent.api.dsl.TypedAgentScopeBuilder→com.embabel.agent.api.common.Transformationcom.embabel.agent.api.dsl.TypedAgentScopeBuilderKt→com.embabel.agent.api.common.InputActionContextcom.embabel.agent.api.dsl.TypedAgentScopeBuilderKt→com.embabel.agent.api.common.OperationContextcom.embabel.agent.api.dsl.TypedAgentScopeBuilderKt→com.embabel.agent.api.common.TransformationActionContext
- Direction
- agent.api.dsl uses agent.api.common, so a change to agent.api.common can break agent.api.dsl, while a change to agent.api.dsl can't break agent.api.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→2 agent.api.common uses common.ai.prompt✕
- Connections
- 9 pairs of types, where a type in agent.api.common uses a type in common.ai.prompt.
- The types involved
com.embabel.agent.api.common.ActionContext→com.embabel.common.ai.prompt.PromptContributorcom.embabel.agent.api.common.Actor→com.embabel.common.ai.prompt.PromptContributorcom.embabel.agent.api.common.ContextualPromptElement→com.embabel.common.ai.prompt.PromptContributioncom.embabel.agent.api.common.ContextualPromptElement→com.embabel.common.ai.prompt.PromptContributorcom.embabel.agent.api.common.ContextualPromptElement→com.embabel.common.ai.prompt.PromptElementcom.embabel.agent.api.common.ContextualPromptElementImpl→com.embabel.common.ai.prompt.PromptContributionLocationcom.embabel.agent.api.common.OperationContext→com.embabel.common.ai.prompt.PromptContributorcom.embabel.agent.api.common.PromptRunner→com.embabel.common.ai.prompt.PromptContributorcom.embabel.agent.api.common.PromptRunner→com.embabel.common.ai.prompt.PromptElement
- Direction
- agent.api.common uses common.ai.prompt, so a change to common.ai.prompt can break agent.api.common, while a change to agent.api.common can't break common.ai.prompt.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→4 agent.api.common uses plan✕
- Connections
- 1 pair of types, where a type in agent.api.common uses a type in plan.
- The types involved
com.embabel.agent.api.common.TransformationKt→com.embabel.plan.WorldState
- Direction
- agent.api.common uses plan, so a change to plan can break agent.api.common, while a change to agent.api.common can't break plan.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→6 agent.api.common uses agent.core.internal✕
- Connections
- 1 pair of types, where a type in agent.api.common uses a type in agent.core.internal.
- The types involved
com.embabel.agent.api.common.PlatformServices→com.embabel.agent.core.internal.LlmOperations
- Direction
- agent.api.common uses agent.core.internal, so a change to agent.core.internal can break agent.api.common, while a change to agent.api.common can't break agent.core.internal.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→7 agent.api.common uses common.ai.decision✕
- Connections
- 2 pairs of types, where a type in agent.api.common uses a type in common.ai.decision.
- The types involved
com.embabel.agent.api.common.Ai→com.embabel.common.ai.decision.DecisionServicecom.embabel.agent.api.common.OperationContextAi→com.embabel.common.ai.decision.DecisionService
- Direction
- agent.api.common uses common.ai.decision, so a change to common.ai.decision can break agent.api.common, while a change to agent.api.common can't break common.ai.decision.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→9 agent.api.common uses agent.api.tool.agentic✕
- Connections
- 1 pair of types, where a type in agent.api.common uses a type in agent.api.tool.agentic.
- The types involved
com.embabel.agent.api.common.PromptRunner→com.embabel.agent.api.tool.agentic.ToolChaining
- Direction
- agent.api.common uses agent.api.tool.agentic, so a change to agent.api.tool.agentic can break agent.api.common, while a change to agent.api.common can't break agent.api.tool.agentic.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→10 agent.api.common uses common.ai.classification✕
- Connections
- 2 pairs of types, where a type in agent.api.common uses a type in common.ai.classification.
- The types involved
com.embabel.agent.api.common.Ai→com.embabel.common.ai.classification.ClassificationServicecom.embabel.agent.api.common.OperationContextAi→com.embabel.common.ai.classification.ClassificationService
- Direction
- agent.api.common uses common.ai.classification, so a change to common.ai.classification can break agent.api.common, while a change to agent.api.common can't break common.ai.classification.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→13 agent.api.common uses agent.api.reference✕
- Connections
- 1 pair of types, where a type in agent.api.common uses a type in agent.api.reference.
- The types involved
com.embabel.agent.api.common.PromptRunner→com.embabel.agent.api.reference.LlmReference
- Direction
- agent.api.common uses agent.api.reference, so a change to agent.api.reference can break agent.api.common, while a change to agent.api.common can't break agent.api.reference.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→14 agent.api.common uses chat✕
- Connections
- 7 pairs of types, where a type in agent.api.common uses a type in chat.
- The types involved
com.embabel.agent.api.common.ExecutingOperationContext→com.embabel.chat.Messagecom.embabel.agent.api.common.MultimodalContent→com.embabel.chat.ContentPartcom.embabel.agent.api.common.PlatformServices→com.embabel.chat.ConversationFactoryProvidercom.embabel.agent.api.common.PromptRunner→com.embabel.chat.AssistantMessagecom.embabel.agent.api.common.PromptRunner→com.embabel.chat.Messagecom.embabel.agent.api.common.PromptRunnerOperations→com.embabel.chat.AssistantMessagecom.embabel.agent.api.common.PromptRunnerOperations→com.embabel.chat.Message
- Direction
- agent.api.common uses chat, so a change to chat can break agent.api.common, while a change to agent.api.common can't break chat.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→15 agent.api.common uses agent.api.tool.callback✕
- Connections
- 3 pairs of types, where a type in agent.api.common uses a type in agent.api.tool.callback.
- The types involved
com.embabel.agent.api.common.PromptRunner→com.embabel.agent.api.tool.callback.ToolCallInspectorcom.embabel.agent.api.common.PromptRunner→com.embabel.agent.api.tool.callback.ToolLoopInspectorcom.embabel.agent.api.common.PromptRunner→com.embabel.agent.api.tool.callback.ToolLoopTransformer
- Direction
- agent.api.common uses agent.api.tool.callback, so a change to agent.api.tool.callback can break agent.api.common, while a change to agent.api.common can't break agent.api.tool.callback.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→16 agent.api.common uses agent.spi.loop✕
- Connections
- 1 pair of types, where a type in agent.api.common uses a type in agent.spi.loop.
- The types involved
com.embabel.agent.api.common.PromptRunner→com.embabel.agent.spi.loop.ToolNotFoundPolicy
- Direction
- agent.api.common uses agent.spi.loop, so a change to agent.spi.loop can break agent.api.common, while a change to agent.api.common can't break agent.spi.loop.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→17 agent.api.common uses agent.spi✕
- Connections
- 4 pairs of types, where a type in agent.api.common uses a type in agent.spi.
- The types involved
com.embabel.agent.api.common.Ai→com.embabel.agent.spi.LlmServicecom.embabel.agent.api.common.OperationContextAi→com.embabel.agent.spi.LlmServicecom.embabel.agent.api.common.PlatformServices→com.embabel.agent.spi.OperationSchedulercom.embabel.agent.api.common.PromptRunner→com.embabel.agent.spi.LlmService
- Direction
- agent.api.common uses agent.spi, so a change to agent.spi can break agent.api.common, while a change to agent.api.common can't break agent.spi.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→18 agent.api.common uses common.ai.model✕
- Connections
- 14 pairs of types, where a type in agent.api.common uses a type in common.ai.model.
- The types involved
com.embabel.agent.api.common.ActionContext→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.api.common.Actor→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.api.common.Ai→com.embabel.common.ai.model.EmbeddingServicecom.embabel.agent.api.common.Ai→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.api.common.Ai→com.embabel.common.ai.model.ModelSelectionCriteriacom.embabel.agent.api.common.Ai→com.embabel.common.ai.model.ServiceSelectorcom.embabel.agent.api.common.OperationContext→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.api.common.OperationContextAi→com.embabel.common.ai.model.EmbeddingServicecom.embabel.agent.api.common.OperationContextAi→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.api.common.OperationContextAi→com.embabel.common.ai.model.ModelSelectionCriteriacom.embabel.agent.api.common.OperationContextAi→com.embabel.common.ai.model.ServiceSelectorcom.embabel.agent.api.common.PlatformServices→com.embabel.common.ai.model.DecisionServiceRegistrycom.embabel.agent.api.common.PlatformServices→com.embabel.common.ai.model.ModelProvidercom.embabel.agent.api.common.PromptRunner→com.embabel.common.ai.model.LlmOptions
- Direction
- agent.api.common uses common.ai.model, so a change to common.ai.model can break agent.api.common, while a change to agent.api.common can't break common.ai.model.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→19 agent.api.common uses agent.api.tool✕
- Connections
- 5 pairs of types, where a type in agent.api.common uses a type in agent.api.tool.
- The types involved
com.embabel.agent.api.common.ActionContext→com.embabel.agent.api.tool.ToolObjectcom.embabel.agent.api.common.OperationContext→com.embabel.agent.api.tool.ToolObjectcom.embabel.agent.api.common.PromptRunner→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.common.PromptRunner→com.embabel.agent.api.tool.ToolCallContextcom.embabel.agent.api.common.PromptRunner→com.embabel.agent.api.tool.ToolObject
- Direction
- agent.api.common uses agent.api.tool, so a change to agent.api.tool can break agent.api.common, while a change to agent.api.common can't break agent.api.tool.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→24 agent.api.common uses agent.api.common.autonomy✕
- Connections
- 1 pair of types, where a type in agent.api.common uses a type in agent.api.common.autonomy.
- The types involved
com.embabel.agent.api.common.PlatformServices→com.embabel.agent.api.common.autonomy.Autonomy
- Direction
- agent.api.common uses agent.api.common.autonomy, so a change to agent.api.common.autonomy can break agent.api.common, while a change to agent.api.common can't break agent.api.common.autonomy.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→26 agent.api.common uses agent.core.support✕
- Connections
- 1 pair of types, where a type in agent.api.common uses a type in agent.core.support.
- The types involved
com.embabel.agent.api.common.PromptRunner→com.embabel.agent.core.support.LlmUse
- Direction
- agent.api.common uses agent.core.support, so a change to agent.core.support can break agent.api.common, while a change to agent.api.common can't break agent.core.support.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→27 agent.api.common uses agent.api.event✕
- Connections
- 4 pairs of types, where a type in agent.api.common uses a type in agent.api.event.
- The types involved
com.embabel.agent.api.common.PlatformServices→com.embabel.agent.api.event.AgenticEventListenercom.embabel.agent.api.common.StuckHandlerResult→com.embabel.agent.api.event.AbstractAgentProcessEventcom.embabel.agent.api.common.SupplierActionContext→com.embabel.agent.api.event.AgenticEventListenercom.embabel.agent.api.common.TransformationActionContext→com.embabel.agent.api.event.AgenticEventListener
- Direction
- agent.api.common uses agent.api.event, so a change to agent.api.event can break agent.api.common, while a change to agent.api.common can't break agent.api.event.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→28 agent.api.common uses agent.core✕
- Connections
- 50 pairs of types, where a type in agent.api.common uses a type in agent.core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.embabel.agent.api.common.ActionContext→com.embabel.agent.core.Actioncom.embabel.agent.api.common.ActionContext→com.embabel.agent.core.ProcessContextcom.embabel.agent.api.common.ActionContext→com.embabel.agent.core.ToolGroupRequirementcom.embabel.agent.api.common.AgentBackedAgentFunction→com.embabel.agent.core.Agentcom.embabel.agent.api.common.AgentBackedAgentFunction→com.embabel.agent.core.AgentPlatformcom.embabel.agent.api.common.AgentBackedAgentFunction→com.embabel.agent.core.AgentScopecom.embabel.agent.api.common.AgentBackedAgentFunction→com.embabel.agent.core.ProcessOptionscom.embabel.agent.api.common.AgentFunction→com.embabel.agent.core.AgentScopecom.embabel.agent.api.common.AgentPlatformBackedAgentFunction→com.embabel.agent.core.AgentPlatformcom.embabel.agent.api.common.AgentPlatformBackedAgentFunction→com.embabel.agent.core.AgentScopecom.embabel.agent.api.common.AgentPlatformBackedAgentFunction→com.embabel.agent.core.ProcessOptionscom.embabel.agent.api.common.AgentPlatformTypedOps→com.embabel.agent.core.AgentPlatformcom.embabel.agent.api.common.AiBuilder→com.embabel.agent.core.LlmVerbositycom.embabel.agent.api.common.AiBuilder→com.embabel.agent.core.ProcessOptionscom.embabel.agent.api.common.ExecutingOperationContext→com.embabel.agent.core.Agentcom.embabel.agent.api.common.ExecutingOperationContextImpl→com.embabel.agent.core.Blackboardcom.embabel.agent.api.common.ExecutingOperationContextImpl→com.embabel.agent.core.Operationcom.embabel.agent.api.common.ExecutingOperationContextImpl→com.embabel.agent.core.ProcessContextcom.embabel.agent.api.common.ExecutingOperationContextImpl→com.embabel.agent.core.ToolGroupRequirementcom.embabel.agent.api.common.MulticastStuckHandler→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.common.OperationContext→com.embabel.agent.core.AgentPlatformcom.embabel.agent.api.common.OperationContext→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.common.OperationContext→com.embabel.agent.core.Blackboardcom.embabel.agent.api.common.OperationContext→com.embabel.agent.core.Operationcom.embabel.agent.api.common.OperationContext→com.embabel.agent.core.ProcessContext
- Direction
- agent.api.common uses agent.core, so a change to agent.core can break agent.api.common, while a change to agent.api.common can't break agent.core.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→29 agent.api.common uses agent.api.channel✕
- Connections
- 2 pairs of types, where a type in agent.api.common uses a type in agent.api.channel.
- The types involved
com.embabel.agent.api.common.ExecutingOperationContext→com.embabel.agent.api.channel.OutputChannelEventcom.embabel.agent.api.common.PlatformServices→com.embabel.agent.api.channel.OutputChannel
- Direction
- agent.api.common uses agent.api.channel, so a change to agent.api.channel can break agent.api.common, while a change to agent.api.common can't break agent.api.channel.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
31→30 agent.api.common uses agent.api.dsl✕
- Connections
- 2 pairs of types, where a type in agent.api.common uses a type in agent.api.dsl.
- The types involved
com.embabel.agent.api.common.ExecutingOperationContext→com.embabel.agent.api.dsl.TypedAgentScopeBuildercom.embabel.agent.api.common.OperationContextKt→com.embabel.agent.api.dsl.TypedAgentScopeBuilder
- Direction
- agent.api.common uses agent.api.dsl, so a change to agent.api.dsl can break agent.api.common, while a change to agent.api.common can't break agent.api.dsl.
- Position
- Below the diagonal: agent.api.common uses a module listed above it, which is the healthy direction.
32→4 agent.api.annotation.support uses plan✕
- Connections
- 1 pair of types, where a type in agent.api.annotation.support uses a type in plan.
- The types involved
com.embabel.agent.api.annotation.support.DefaultActionMethodManager→com.embabel.plan.WorldState
- Direction
- agent.api.annotation.support uses plan, so a change to plan can break agent.api.annotation.support, while a change to agent.api.annotation.support can't break plan.
- Position
- Below the diagonal: agent.api.annotation.support uses a module listed above it, which is the healthy direction.
32→5 agent.api.annotation.support uses agent.api.tool.Tool✕
- Connections
- 5 pairs of types, where a type in agent.api.annotation.support uses a type in agent.api.tool.Tool.
- The types involved
com.embabel.agent.api.annotation.support.CurriedActionTool→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.api.annotation.support.CurriedActionTool→com.embabel.agent.api.tool.Tool.InputSchemacom.embabel.agent.api.annotation.support.CurriedActionTool→com.embabel.agent.api.tool.Tool.Metadatacom.embabel.agent.api.annotation.support.CurriedActionTool→com.embabel.agent.api.tool.Tool.ParameterTypecom.embabel.agent.api.annotation.support.CurriedActionTool→com.embabel.agent.api.tool.Tool.Result
- Direction
- agent.api.annotation.support uses agent.api.tool.Tool, so a change to agent.api.tool.Tool can break agent.api.annotation.support, while a change to agent.api.annotation.support can't break agent.api.tool.Tool.
- Position
- Below the diagonal: agent.api.annotation.support uses a module listed above it, which is the healthy direction.
32→19 agent.api.annotation.support uses agent.api.tool✕
- Connections
- 5 pairs of types, where a type in agent.api.annotation.support uses a type in agent.api.tool.
- The types involved
com.embabel.agent.api.annotation.support.ActionMethodManager→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.annotation.support.AgentMetadataReader→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.annotation.support.CurriedActionTool→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.annotation.support.DefaultActionMethodManager→com.embabel.agent.api.tool.Toolcom.embabel.agent.api.annotation.support.SupervisorAction→com.embabel.agent.api.tool.Tool
- Direction
- agent.api.annotation.support uses agent.api.tool, so a change to agent.api.tool can break agent.api.annotation.support, while a change to agent.api.annotation.support can't break agent.api.tool.
- Position
- Below the diagonal: agent.api.annotation.support uses a module listed above it, which is the healthy direction.
32→26 agent.api.annotation.support uses agent.core.support✕
- Connections
- 1 pair of types, where a type in agent.api.annotation.support uses a type in agent.core.support.
- The types involved
com.embabel.agent.api.annotation.support.SupervisorAction→com.embabel.agent.core.support.AbstractAction
- Direction
- agent.api.annotation.support uses agent.core.support, so a change to agent.core.support can break agent.api.annotation.support, while a change to agent.api.annotation.support can't break agent.core.support.
- Position
- Below the diagonal: agent.api.annotation.support uses a module listed above it, which is the healthy direction.
32→28 agent.api.annotation.support uses agent.core✕
- Connections
- 30 pairs of types, where a type in agent.api.annotation.support uses a type in agent.core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.embabel.agent.api.annotation.support.ActionMethodArgumentResolver→com.embabel.agent.core.IoBindingcom.embabel.agent.api.annotation.support.ActionMethodManager→com.embabel.agent.core.Actioncom.embabel.agent.api.annotation.support.ActionQosProvider→com.embabel.agent.core.ActionQoscom.embabel.agent.api.annotation.support.AgentMetadataReader→com.embabel.agent.core.Actioncom.embabel.agent.api.annotation.support.AgentMetadataReader→com.embabel.agent.core.AgentScopecom.embabel.agent.api.annotation.support.AgentMetadataReader→com.embabel.agent.core.ComputedBooleanConditioncom.embabel.agent.api.annotation.support.AgentMetadataReader→com.embabel.agent.core.Conditioncom.embabel.agent.api.annotation.support.AgentMetadataReader→com.embabel.agent.core.Goalcom.embabel.agent.api.annotation.support.BlackboardArgumentResolver→com.embabel.agent.core.IoBindingcom.embabel.agent.api.annotation.support.CurriedActionTool→com.embabel.agent.core.Actioncom.embabel.agent.api.annotation.support.CurriedActionTool→com.embabel.agent.core.AgentProcesscom.embabel.agent.api.annotation.support.CurriedActionTool→com.embabel.agent.core.Blackboardcom.embabel.agent.api.annotation.support.CurriedActionTool→com.embabel.agent.core.IoBindingcom.embabel.agent.api.annotation.support.DefaultActionMethodManager→com.embabel.agent.core.Actioncom.embabel.agent.api.annotation.support.DefaultActionMethodManager→com.embabel.agent.core.IoBindingcom.embabel.agent.api.annotation.support.DefaultActionQosProvider→com.embabel.agent.core.ActionQoscom.embabel.agent.api.annotation.support.EmptyDataDictionary→com.embabel.agent.core.DataDictionarycom.embabel.agent.api.annotation.support.EmptyDataDictionary→com.embabel.agent.core.DomainTypecom.embabel.agent.api.annotation.support.StateActionMethodManager→com.embabel.agent.core.Actioncom.embabel.agent.api.annotation.support.StateActionMethodManager→com.embabel.agent.core.IoBindingcom.embabel.agent.api.annotation.support.SupervisorAction→com.embabel.agent.core.Actioncom.embabel.agent.api.annotation.support.SupervisorAction→com.embabel.agent.core.ActionStatuscom.embabel.agent.api.annotation.support.SupervisorAction→com.embabel.agent.core.IoBindingcom.embabel.agent.api.annotation.support.SupervisorAction→com.embabel.agent.core.ProcessContextcom.embabel.agent.api.annotation.support.SupervisorAgentFactory→com.embabel.agent.core.Action
- Direction
- agent.api.annotation.support uses agent.core, so a change to agent.core can break agent.api.annotation.support, while a change to agent.api.annotation.support can't break agent.core.
- Position
- Below the diagonal: agent.api.annotation.support uses a module listed above it, which is the healthy direction.
32→31 agent.api.annotation.support uses agent.api.common✕
- Connections
- 12 pairs of types, where a type in agent.api.annotation.support uses a type in agent.api.common.
- The types involved
com.embabel.agent.api.annotation.support.ActionMethodArgumentResolver→com.embabel.agent.api.common.OperationContextcom.embabel.agent.api.annotation.support.ActionMethodManager→com.embabel.agent.api.common.TransformationActionContextcom.embabel.agent.api.annotation.support.AgentMetadataReader→com.embabel.agent.api.common.OperationContextcom.embabel.agent.api.annotation.support.AiArgumentResolver→com.embabel.agent.api.common.OperationContextcom.embabel.agent.api.annotation.support.BlackboardArgumentResolver→com.embabel.agent.api.common.OperationContextcom.embabel.agent.api.annotation.support.DefaultActionMethodManager→com.embabel.agent.api.common.ActionContextcom.embabel.agent.api.annotation.support.DefaultActionMethodManager→com.embabel.agent.api.common.TransformationActionContextcom.embabel.agent.api.annotation.support.OperationContextArgumentResolver→com.embabel.agent.api.common.OperationContextcom.embabel.agent.api.annotation.support.ProcessContextArgumentResolver→com.embabel.agent.api.common.OperationContextcom.embabel.agent.api.annotation.support.ProvidedArgumentResolver→com.embabel.agent.api.common.OperationContextcom.embabel.agent.api.annotation.support.StateActionMethodManager→com.embabel.agent.api.common.OperationContextcom.embabel.agent.api.annotation.support.StateActionMethodManager→com.embabel.agent.api.common.TransformationActionContext
- Direction
- agent.api.annotation.support uses agent.api.common, so a change to agent.api.common can break agent.api.annotation.support, while a change to agent.api.annotation.support can't break agent.api.common.
- Position
- Below the diagonal: agent.api.annotation.support uses a module listed above it, which is the healthy direction.
33→2 agent.rag.tools uses common.ai.prompt✕
- Connections
- 2 pairs of types, where a type in agent.rag.tools uses a type in common.ai.prompt.
- The types involved
com.embabel.agent.rag.tools.ToolishRag→com.embabel.common.ai.prompt.PromptContributorcom.embabel.agent.rag.tools.TryHyDE→com.embabel.common.ai.prompt.PromptContributor
- Direction
- agent.rag.tools uses common.ai.prompt, so a change to common.ai.prompt can break agent.rag.tools, while a change to agent.rag.tools can't break common.ai.prompt.
- Position
- Below the diagonal: agent.rag.tools uses a module listed above it, which is the healthy direction.
33→5 agent.rag.tools uses agent.api.tool.Tool✕
- Connections
- 4 pairs of types, where a type in agent.rag.tools uses a type in agent.api.tool.Tool.
- The types involved
com.embabel.agent.rag.tools.TextSearchTools→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.rag.tools.TextSearchTools→com.embabel.agent.api.tool.Tool.Resultcom.embabel.agent.rag.tools.ToolishRag→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.rag.tools.ToolishRag→com.embabel.agent.api.tool.Tool.Result
- Direction
- agent.rag.tools uses agent.api.tool.Tool, so a change to agent.api.tool.Tool can break agent.rag.tools, while a change to agent.rag.tools can't break agent.api.tool.Tool.
- Position
- Below the diagonal: agent.rag.tools uses a module listed above it, which is the healthy direction.
33→13 agent.rag.tools uses agent.api.reference✕
- Connections
- 3 pairs of types, where a type in agent.rag.tools uses a type in agent.api.reference.
- The types involved
com.embabel.agent.rag.tools.RagServiceReference→com.embabel.agent.api.reference.LlmReferencecom.embabel.agent.rag.tools.ToolishRag→com.embabel.agent.api.reference.EagerSearchcom.embabel.agent.rag.tools.ToolishRag→com.embabel.agent.api.reference.LlmReference
- Direction
- agent.rag.tools uses agent.api.reference, so a change to agent.api.reference can break agent.rag.tools, while a change to agent.rag.tools can't break agent.api.reference.
- Position
- Below the diagonal: agent.rag.tools uses a module listed above it, which is the healthy direction.
33→18 agent.rag.tools uses common.ai.model✕
- Connections
- 1 pair of types, where a type in agent.rag.tools uses a type in common.ai.model.
- The types involved
com.embabel.agent.rag.tools.RagOptions→com.embabel.common.ai.model.LlmOptions
- Direction
- agent.rag.tools uses common.ai.model, so a change to common.ai.model can break agent.rag.tools, while a change to agent.rag.tools can't break common.ai.model.
- Position
- Below the diagonal: agent.rag.tools uses a module listed above it, which is the healthy direction.
33→19 agent.rag.tools uses agent.api.tool✕
- Connections
- 5 pairs of types, where a type in agent.rag.tools uses a type in agent.api.tool.
- The types involved
com.embabel.agent.rag.tools.ContextualTool→com.embabel.agent.api.tool.Toolcom.embabel.agent.rag.tools.RagServiceReference→com.embabel.agent.api.tool.Toolcom.embabel.agent.rag.tools.TextSearchTools→com.embabel.agent.api.tool.Toolcom.embabel.agent.rag.tools.ToolishRag→com.embabel.agent.api.tool.DelegatingToolcom.embabel.agent.rag.tools.ToolishRag→com.embabel.agent.api.tool.Tool
- Direction
- agent.rag.tools uses agent.api.tool, so a change to agent.api.tool can break agent.rag.tools, while a change to agent.rag.tools can't break agent.api.tool.
- Position
- Below the diagonal: agent.rag.tools uses a module listed above it, which is the healthy direction.
33→31 agent.rag.tools uses agent.api.common✕
- Connections
- 1 pair of types, where a type in agent.rag.tools uses a type in agent.api.common.
- The types involved
com.embabel.agent.rag.tools.RagServiceReference→com.embabel.agent.api.common.PromptRunner
- Direction
- agent.rag.tools uses agent.api.common, so a change to agent.api.common can break agent.rag.tools, while a change to agent.rag.tools can't break agent.api.common.
- Position
- Below the diagonal: agent.rag.tools uses a module listed above it, which is the healthy direction.
33→38 agent.rag.tools uses agent.rag.service part of a loop✕
- Connections
- 23 pairs of types, where a type in agent.rag.tools uses a type in agent.rag.service.
- The types involved
com.embabel.agent.rag.tools.CoreSearchToolsKt→com.embabel.agent.rag.service.ResultExpandercom.embabel.agent.rag.tools.DualShotRagServiceSearchTools→com.embabel.agent.rag.service.RagResponseSummarizercom.embabel.agent.rag.tools.FinderTools→com.embabel.agent.rag.service.FinderOperationscom.embabel.agent.rag.tools.RagOptions→com.embabel.agent.rag.service.ContentElementSearchcom.embabel.agent.rag.tools.RagOptions→com.embabel.agent.rag.service.EntitySearchcom.embabel.agent.rag.tools.RagOptions→com.embabel.agent.rag.service.RagHintcom.embabel.agent.rag.tools.RagOptions→com.embabel.agent.rag.service.RagRequestRefinementcom.embabel.agent.rag.tools.RagOptions→com.embabel.agent.rag.service.RagServicecom.embabel.agent.rag.tools.RagOptions→com.embabel.agent.rag.service.RetrievableResultsFormattercom.embabel.agent.rag.tools.RegexSearchTools→com.embabel.agent.rag.service.RegexSearchOperationscom.embabel.agent.rag.tools.RegexSearchTools→com.embabel.agent.rag.service.RetrievableResultsFormattercom.embabel.agent.rag.tools.ResultExpanderTools→com.embabel.agent.rag.service.ResultExpandercom.embabel.agent.rag.tools.SectionReadingTools→com.embabel.agent.rag.service.SectionReadercom.embabel.agent.rag.tools.TextSearchTools→com.embabel.agent.rag.service.ResultExpandercom.embabel.agent.rag.tools.TextSearchTools→com.embabel.agent.rag.service.RetrievableResultsFormattercom.embabel.agent.rag.tools.TextSearchTools→com.embabel.agent.rag.service.TextSearchcom.embabel.agent.rag.tools.ToolishRag→com.embabel.agent.rag.service.RetrievableResultsFormattercom.embabel.agent.rag.tools.ToolishRag→com.embabel.agent.rag.service.SearchOperationscom.embabel.agent.rag.tools.ToolishRag→com.embabel.agent.rag.service.VectorSearchcom.embabel.agent.rag.tools.TypeRetrievalTools→com.embabel.agent.rag.service.TypeRetrievalOperationscom.embabel.agent.rag.tools.VectorSearchTools→com.embabel.agent.rag.service.ResultExpandercom.embabel.agent.rag.tools.VectorSearchTools→com.embabel.agent.rag.service.RetrievableResultsFormattercom.embabel.agent.rag.tools.VectorSearchTools→com.embabel.agent.rag.service.VectorSearch
- Direction
- agent.rag.tools uses agent.rag.service, so a change to agent.rag.service can break agent.rag.tools, while a change to agent.rag.tools can't break agent.rag.service.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→39 agent.rag.tools uses agent.rag.model part of a loop✕
- Connections
- 7 pairs of types, where a type in agent.rag.tools uses a type in agent.rag.model.
- The types involved
com.embabel.agent.rag.tools.ContextualTool→com.embabel.agent.rag.model.Retrievablecom.embabel.agent.rag.tools.CoreSearchToolsKt→com.embabel.agent.rag.model.Retrievablecom.embabel.agent.rag.tools.RegexSearchTools→com.embabel.agent.rag.model.Chunkcom.embabel.agent.rag.tools.ResultsEvent→com.embabel.agent.rag.model.Retrievablecom.embabel.agent.rag.tools.TextSearchTools→com.embabel.agent.rag.model.Retrievablecom.embabel.agent.rag.tools.ToolishRag→com.embabel.agent.rag.model.Retrievablecom.embabel.agent.rag.tools.VectorSearchTools→com.embabel.agent.rag.model.Retrievable
- Direction
- agent.rag.tools uses agent.rag.model, so a change to agent.rag.model can break agent.rag.tools, while a change to agent.rag.tools can't break agent.rag.model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→3 agent.shell uses common.util✕
- Connections
- 1 pair of types, where a type in agent.shell uses a type in common.util.
- The types involved
com.embabel.agent.shell.ShellCommands→com.embabel.common.util.EmbabelObjectMapperHolder
- Direction
- agent.shell uses common.util, so a change to common.util can break agent.shell, while a change to agent.shell can't break common.util.
- Position
- Below the diagonal: agent.shell uses a module listed above it, which is the healthy direction.
34→14 agent.shell uses chat✕
- Connections
- 2 pairs of types, where a type in agent.shell uses a type in chat.
- The types involved
com.embabel.agent.shell.ShellCommands→com.embabel.chat.Chatbotcom.embabel.agent.shell.TerminalServices→com.embabel.chat.ChatSession
- Direction
- agent.shell uses chat, so a change to chat can break agent.shell, while a change to agent.shell can't break chat.
- Position
- Below the diagonal: agent.shell uses a module listed above it, which is the healthy direction.
34→18 agent.shell uses common.ai.model✕
- Connections
- 1 pair of types, where a type in agent.shell uses a type in common.ai.model.
- The types involved
com.embabel.agent.shell.ShellCommands→com.embabel.common.ai.model.ModelProvider
- Direction
- agent.shell uses common.ai.model, so a change to common.ai.model can break agent.shell, while a change to agent.shell can't break common.ai.model.
- Position
- Below the diagonal: agent.shell uses a module listed above it, which is the healthy direction.
34→19 agent.shell uses agent.api.tool✕
- Connections
- 1 pair of types, where a type in agent.shell uses a type in agent.api.tool.
- The types involved
com.embabel.agent.shell.ShellCommands→com.embabel.agent.api.tool.ToolCallContext
- Direction
- agent.shell uses agent.api.tool, so a change to agent.api.tool can break agent.shell, while a change to agent.shell can't break agent.api.tool.
- Position
- Below the diagonal: agent.shell uses a module listed above it, which is the healthy direction.
34→24 agent.shell uses agent.api.common.autonomy✕
- Connections
- 6 pairs of types, where a type in agent.shell uses a type in agent.api.common.autonomy.
- The types involved
com.embabel.agent.shell.FormatProcessOutputKt→com.embabel.agent.api.common.autonomy.AgentProcessExecutioncom.embabel.agent.shell.ShellCommands→com.embabel.agent.api.common.autonomy.AgentProcessExecutioncom.embabel.agent.shell.ShellCommands→com.embabel.agent.api.common.autonomy.Autonomycom.embabel.agent.shell.TerminalServices→com.embabel.agent.api.common.autonomy.GoalChoiceApprovalRequestcom.embabel.agent.shell.TerminalServices→com.embabel.agent.api.common.autonomy.GoalChoiceApprovalResponsecom.embabel.agent.shell.TerminalServices→com.embabel.agent.api.common.autonomy.GoalChoiceApprover
- Direction
- agent.shell uses agent.api.common.autonomy, so a change to agent.api.common.autonomy can break agent.shell, while a change to agent.shell can't break agent.api.common.autonomy.
- Position
- Below the diagonal: agent.shell uses a module listed above it, which is the healthy direction.
34→28 agent.shell uses agent.core✕
- Connections
- 6 pairs of types, where a type in agent.shell uses a type in agent.core.
- The types involved
com.embabel.agent.shell.ShellCommands→com.embabel.agent.core.AgentPlatformcom.embabel.agent.shell.ShellCommands→com.embabel.agent.core.AgentProcesscom.embabel.agent.shell.ShellCommands→com.embabel.agent.core.Blackboardcom.embabel.agent.shell.ShellCommands→com.embabel.agent.core.ProcessOptionscom.embabel.agent.shell.ShellCommands→com.embabel.agent.core.Verbositycom.embabel.agent.shell.TerminalServices→com.embabel.agent.core.AgentPlatform
- Direction
- agent.shell uses agent.core, so a change to agent.core can break agent.shell, while a change to agent.shell can't break agent.core.
- Position
- Below the diagonal: agent.shell uses a module listed above it, which is the healthy direction.
34→29 agent.shell uses agent.api.channel✕
- Connections
- 1 pair of types, where a type in agent.shell uses a type in agent.api.channel.
- The types involved
com.embabel.agent.shell.TerminalServices→com.embabel.agent.api.channel.OutputChannel
- Direction
- agent.shell uses agent.api.channel, so a change to agent.api.channel can break agent.shell, while a change to agent.shell can't break agent.api.channel.
- Position
- Below the diagonal: agent.shell uses a module listed above it, which is the healthy direction.
34→31 agent.shell uses agent.api.common✕
- Connections
- 2 pairs of types, where a type in agent.shell uses a type in agent.api.common.
- The types involved
com.embabel.agent.shell.ShellCommands→com.embabel.agent.api.common.Asyncercom.embabel.agent.shell.ShellCommands→com.embabel.agent.api.common.ToolsStats
- Direction
- agent.shell uses agent.api.common, so a change to agent.api.common can break agent.shell, while a change to agent.shell can't break agent.api.common.
- Position
- Below the diagonal: agent.shell uses a module listed above it, which is the healthy direction.
35→2 agent.spi.support.springai uses common.ai.prompt✕
- Connections
- 1 pair of types, where a type in agent.spi.support.springai uses a type in common.ai.prompt.
- The types involved
com.embabel.agent.spi.support.springai.SpringAiLlmService→com.embabel.common.ai.prompt.PromptContributor
- Direction
- agent.spi.support.springai uses common.ai.prompt, so a change to common.ai.prompt can break agent.spi.support.springai, while a change to agent.spi.support.springai can't break common.ai.prompt.
- Position
- Below the diagonal: agent.spi.support.springai uses a module listed above it, which is the healthy direction.
35→3 agent.spi.support.springai uses common.util✕
- Connections
- 1 pair of types, where a type in agent.spi.support.springai uses a type in common.util.
- The types involved
com.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.common.util.EmbabelObjectMapperHolder
- Direction
- agent.spi.support.springai uses common.util, so a change to common.util can break agent.spi.support.springai, while a change to agent.spi.support.springai can't break common.util.
- Position
- Below the diagonal: agent.spi.support.springai uses a module listed above it, which is the healthy direction.
35→5 agent.spi.support.springai uses agent.api.tool.Tool✕
- Connections
- 5 pairs of types, where a type in agent.spi.support.springai uses a type in agent.api.tool.Tool.
- The types involved
com.embabel.agent.spi.support.springai.SpringInputSchema→com.embabel.agent.api.tool.Tool.InputSchemacom.embabel.agent.spi.support.springai.SpringInputSchema→com.embabel.agent.api.tool.Tool.Parametercom.embabel.agent.spi.support.springai.SpringToolCallbackWrapper→com.embabel.agent.api.tool.Tool.Definitioncom.embabel.agent.spi.support.springai.SpringToolCallbackWrapper→com.embabel.agent.api.tool.Tool.Metadatacom.embabel.agent.spi.support.springai.SpringToolCallbackWrapper→com.embabel.agent.api.tool.Tool.Result
- Direction
- agent.spi.support.springai uses agent.api.tool.Tool, so a change to agent.api.tool.Tool can break agent.spi.support.springai, while a change to agent.spi.support.springai can't break agent.api.tool.Tool.
- Position
- Below the diagonal: agent.spi.support.springai uses a module listed above it, which is the healthy direction.
35→14 agent.spi.support.springai uses chat✕
- Connections
- 3 pairs of types, where a type in agent.spi.support.springai uses a type in chat.
- The types involved
com.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.chat.Messagecom.embabel.agent.spi.support.springai.MessageConvertersKt→com.embabel.chat.Messagecom.embabel.agent.spi.support.springai.SpringAiLlmMessageSender→com.embabel.chat.Message
- Direction
- agent.spi.support.springai uses chat, so a change to chat can break agent.spi.support.springai, while a change to agent.spi.support.springai can't break chat.
- Position
- Below the diagonal: agent.spi.support.springai uses a module listed above it, which is the healthy direction.
35→15 agent.spi.support.springai uses agent.api.tool.callback✕
- Connections
- 2 pairs of types, where a type in agent.spi.support.springai uses a type in agent.api.tool.callback.
- The types involved
com.embabel.agent.spi.support.springai.SpringAiToolCallbackListener→com.embabel.agent.api.tool.callback.ToolCallInspectorcom.embabel.agent.spi.support.springai.SpringAiToolCallbackListenerKt→com.embabel.agent.api.tool.callback.ToolCallInspector
- Direction
- agent.spi.support.springai uses agent.api.tool.callback, so a change to agent.api.tool.callback can break agent.spi.support.springai, while a change to agent.spi.support.springai can't break agent.api.tool.callback.
- Position
- Below the diagonal: agent.spi.support.springai uses a module listed above it, which is the healthy direction.
35→16 agent.spi.support.springai uses agent.spi.loop✕
- Connections
- 8 pairs of types, where a type in agent.spi.support.springai uses a type in agent.spi.loop.
- The types involved
com.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.agent.spi.loop.LlmMessageSendercom.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.agent.spi.loop.ToolLoopFactorycom.embabel.agent.spi.support.springai.SpringAiLlmMessageSender→com.embabel.agent.spi.loop.LlmMessageRequestcom.embabel.agent.spi.support.springai.SpringAiLlmMessageSender→com.embabel.agent.spi.loop.LlmMessageResponsecom.embabel.agent.spi.support.springai.SpringAiLlmMessageSender→com.embabel.agent.spi.loop.RequestAwareLlmMessageSendercom.embabel.agent.spi.support.springai.SpringAiLlmMessageSender→com.embabel.agent.spi.loop.StructuredOutputRequestcom.embabel.agent.spi.support.springai.SpringAiLlmService→com.embabel.agent.spi.loop.LlmMessageSendercom.embabel.agent.spi.support.springai.SpringAiNativeStructuredOutputConfigurer→com.embabel.agent.spi.loop.StructuredOutputRequest
- Direction
- agent.spi.support.springai uses agent.spi.loop, so a change to agent.spi.loop can break agent.spi.support.springai, while a change to agent.spi.support.springai can't break agent.spi.loop.
- Position
- Below the diagonal: agent.spi.support.springai uses a module listed above it, which is the healthy direction.
35→17 agent.spi.support.springai uses agent.spi✕
- Connections
- 4 pairs of types, where a type in agent.spi.support.springai uses a type in agent.spi.
- The types involved
com.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.agent.spi.AutoLlmSelectionCriteriaResolvercom.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.agent.spi.LlmServicecom.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.agent.spi.ToolDecoratorcom.embabel.agent.spi.support.springai.SpringAiLlmService→com.embabel.agent.spi.LlmService
- Direction
- agent.spi.support.springai uses agent.spi, so a change to agent.spi can break agent.spi.support.springai, while a change to agent.spi.support.springai can't break agent.spi.
- Position
- Below the diagonal: agent.spi.support.springai uses a module listed above it, which is the healthy direction.
35→18 agent.spi.support.springai uses common.ai.model✕
- Connections
- 10 pairs of types, where a type in agent.spi.support.springai uses a type in common.ai.model.
- The types involved
com.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.common.ai.model.ModelProvidercom.embabel.agent.spi.support.springai.ChatModelCallEvent→com.embabel.common.ai.model.LlmMetadatacom.embabel.agent.spi.support.springai.EmbeddingModelCallEvent→com.embabel.common.ai.model.EmbeddingServiceMetadatacom.embabel.agent.spi.support.springai.SpringAiLlmMessageSender→com.embabel.common.ai.model.LlmMetadatacom.embabel.agent.spi.support.springai.SpringAiLlmService→com.embabel.common.ai.model.AiModelcom.embabel.agent.spi.support.springai.SpringAiLlmService→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.spi.support.springai.SpringAiLlmService→com.embabel.common.ai.model.OptionsConvertercom.embabel.agent.spi.support.springai.SpringAiLlmService→com.embabel.common.ai.model.PricingModelcom.embabel.agent.spi.support.springai.SpringAiNativeStructuredOutputConfigurer→com.embabel.common.ai.model.LlmMetadata
- Direction
- agent.spi.support.springai uses common.ai.model, so a change to common.ai.model can break agent.spi.support.springai, while a change to agent.spi.support.springai can't break common.ai.model.
- Position
- Below the diagonal: agent.spi.support.springai uses a module listed above it, which is the healthy direction.
35→19 agent.spi.support.springai uses agent.api.tool✕
- Connections
- 9 pairs of types, where a type in agent.spi.support.springai uses a type in agent.api.tool.
- The types involved
com.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.springai.SpringAiLlmMessageSender→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.springai.SpringAiMcpToolFactory→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.springai.SpringAiToolExtractor→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.springai.SpringAiUtilsKt→com.embabel.agent.api.tool.ToolObjectcom.embabel.agent.spi.support.springai.SpringToolCallbackAdapter→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.springai.SpringToolCallbackAdapterKt→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.springai.SpringToolCallbackWrapper→com.embabel.agent.api.tool.Toolcom.embabel.agent.spi.support.springai.SpringToolCallbackWrapper→com.embabel.agent.api.tool.ToolCallContext
- Direction
- agent.spi.support.springai uses agent.api.tool, so a change to agent.api.tool can break agent.spi.support.springai, while a change to agent.spi.support.springai can't break agent.api.tool.
- Position
- Below the diagonal: agent.spi.support.springai uses a module listed above it, which is the healthy direction.
35→21 agent.spi.support.springai uses common.ai.autoconfig✕
- Connections
- 3 pairs of types, where a type in agent.spi.support.springai uses a type in common.ai.autoconfig.
- The types involved
com.embabel.agent.spi.support.springai.SpringAiLlmMessageSender→com.embabel.common.ai.autoconfig.NativeSupportcom.embabel.agent.spi.support.springai.SpringAiLlmService→com.embabel.common.ai.autoconfig.NativeSupportcom.embabel.agent.spi.support.springai.SpringAiNativeStructuredOutputConfigurer→com.embabel.common.ai.autoconfig.NativeSupport
- Direction
- agent.spi.support.springai uses common.ai.autoconfig, so a change to common.ai.autoconfig can break agent.spi.support.springai, while a change to agent.spi.support.springai can't break common.ai.autoconfig.
- Position
- Below the diagonal: agent.spi.support.springai uses a module listed above it, which is the healthy direction.
35→25 agent.spi.support.springai uses agent.spi.support✕
- Connections
- 6 pairs of types, where a type in agent.spi.support.springai uses a type in agent.spi.support.
- The types involved
com.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.agent.spi.support.LlmDataBindingPropertiescom.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.agent.spi.support.LlmOperationsPromptsPropertiescom.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.agent.spi.support.MaybeReturncom.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.agent.spi.support.OutputConvertercom.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.agent.spi.support.ToolLoopLlmOperationscom.embabel.agent.spi.support.springai.SpringAiOutputConverterAdapter→com.embabel.agent.spi.support.OutputConverter
- Direction
- agent.spi.support.springai uses agent.spi.support, so a change to agent.spi.support can break agent.spi.support.springai, while a change to agent.spi.support.springai can't break agent.spi.support.
- Position
- Below the diagonal: agent.spi.support.springai uses a module listed above it, which is the healthy direction.
35→26 agent.spi.support.springai uses agent.core.support✕
- Connections
- 3 pairs of types, where a type in agent.spi.support.springai uses a type in agent.core.support.
- The types involved
com.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.agent.core.support.LlmInteractioncom.embabel.agent.spi.support.springai.ChatModelCallEvent→com.embabel.agent.core.support.LlmInteractioncom.embabel.agent.spi.support.springai.SpringAiToolExtractor→com.embabel.agent.core.support.ExternalToolExtractor
- Direction
- agent.spi.support.springai uses agent.core.support, so a change to agent.core.support can break agent.spi.support.springai, while a change to agent.spi.support.springai can't break agent.core.support.
- Position
- Below the diagonal: agent.spi.support.springai uses a module listed above it, which is the healthy direction.
35→27 agent.spi.support.springai uses agent.api.event✕
- Connections
- 4 pairs of types, where a type in agent.spi.support.springai uses a type in agent.api.event.
- The types involved
com.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.agent.api.event.LlmRequestEventcom.embabel.agent.spi.support.springai.ChatModelCallEvent→com.embabel.agent.api.event.AbstractAgentProcessEventcom.embabel.agent.spi.support.springai.EmbeddingModelCallEvent→com.embabel.agent.api.event.EmbeddingEventcom.embabel.agent.spi.support.springai.InstrumentedChatModel→com.embabel.agent.api.event.LlmRequestEvent
- Direction
- agent.spi.support.springai uses agent.api.event, so a change to agent.api.event can break agent.spi.support.springai, while a change to agent.spi.support.springai can't break agent.api.event.
- Position
- Below the diagonal: agent.spi.support.springai uses a module listed above it, which is the healthy direction.
35→28 agent.spi.support.springai uses agent.core✕
- Connections
- 4 pairs of types, where a type in agent.spi.support.springai uses a type in agent.core.
- The types involved
com.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.agent.core.Actioncom.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.agent.core.AgentProcesscom.embabel.agent.spi.support.springai.ChatModelCallEvent→com.embabel.agent.core.AgentProcesscom.embabel.agent.spi.support.springai.SpringAiUtilsKt→com.embabel.agent.core.Usage
- Direction
- agent.spi.support.springai uses agent.core, so a change to agent.core can break agent.spi.support.springai, while a change to agent.spi.support.springai can't break agent.core.
- Position
- Below the diagonal: agent.spi.support.springai uses a module listed above it, which is the healthy direction.
35→31 agent.spi.support.springai uses agent.api.common✕
- Connections
- 1 pair of types, where a type in agent.spi.support.springai uses a type in agent.api.common.
- The types involved
com.embabel.agent.spi.support.springai.ChatClientLlmOperations→com.embabel.agent.api.common.Asyncer
- Direction
- agent.spi.support.springai uses agent.api.common, so a change to agent.api.common can break agent.spi.support.springai, while a change to agent.spi.support.springai can't break agent.api.common.
- Position
- Below the diagonal: agent.spi.support.springai uses a module listed above it, which is the healthy direction.
36→14 chat.agent uses chat✕
- Connections
- 12 pairs of types, where a type in chat.agent uses a type in chat.
- The types involved
com.embabel.chat.agent.AgentProcessChatSession→com.embabel.chat.ChatSessioncom.embabel.chat.agent.AgentProcessChatSession→com.embabel.chat.ChatTriggercom.embabel.chat.agent.AgentProcessChatSession→com.embabel.chat.Conversationcom.embabel.chat.agent.AgentProcessChatSession→com.embabel.chat.ConversationFactorycom.embabel.chat.agent.AgentProcessChatSession→com.embabel.chat.UserMessagecom.embabel.chat.agent.AgentProcessChatbot→com.embabel.chat.ChatSessioncom.embabel.chat.agent.AgentProcessChatbot→com.embabel.chat.Chatbotcom.embabel.chat.agent.AgentProcessChatbot→com.embabel.chat.ConversationFactorycom.embabel.chat.agent.ConversationContinues→com.embabel.chat.AssistantMessagecom.embabel.chat.agent.DefaultChatAgentBuilder→com.embabel.chat.AssistantMessagecom.embabel.chat.agent.DefaultChatAgentBuilder→com.embabel.chat.ChatTriggercom.embabel.chat.agent.DefaultChatAgentBuilder→com.embabel.chat.Conversation
- Direction
- chat.agent uses chat, so a change to chat can break chat.agent, while a change to chat.agent can't break chat.
- Position
- Below the diagonal: chat.agent uses a module listed above it, which is the healthy direction.
36→18 chat.agent uses common.ai.model✕
- Connections
- 1 pair of types, where a type in chat.agent uses a type in common.ai.model.
- The types involved
com.embabel.chat.agent.DefaultChatAgentBuilder→com.embabel.common.ai.model.LlmOptions
- Direction
- chat.agent uses common.ai.model, so a change to common.ai.model can break chat.agent, while a change to chat.agent can't break common.ai.model.
- Position
- Below the diagonal: chat.agent uses a module listed above it, which is the healthy direction.
36→24 chat.agent uses agent.api.common.autonomy✕
- Connections
- 1 pair of types, where a type in chat.agent uses a type in agent.api.common.autonomy.
- The types involved
com.embabel.chat.agent.DefaultChatAgentBuilder→com.embabel.agent.api.common.autonomy.Autonomy
- Direction
- chat.agent uses agent.api.common.autonomy, so a change to agent.api.common.autonomy can break chat.agent, while a change to chat.agent can't break agent.api.common.autonomy.
- Position
- Below the diagonal: chat.agent uses a module listed above it, which is the healthy direction.
36→27 chat.agent uses agent.api.event✕
- Connections
- 1 pair of types, where a type in chat.agent uses a type in agent.api.event.
- The types involved
com.embabel.chat.agent.ListenerProvider→com.embabel.agent.api.event.AgenticEventListener
- Direction
- chat.agent uses agent.api.event, so a change to agent.api.event can break chat.agent, while a change to chat.agent can't break agent.api.event.
- Position
- Below the diagonal: chat.agent uses a module listed above it, which is the healthy direction.
36→28 chat.agent uses agent.core✕
- Connections
- 9 pairs of types, where a type in chat.agent uses a type in agent.core.
- The types involved
com.embabel.chat.agent.AgentProcessChatSession→com.embabel.agent.core.AgentProcesscom.embabel.chat.agent.AgentProcessChatbot→com.embabel.agent.core.AgentPlatformcom.embabel.chat.agent.AgentProcessChatbot→com.embabel.agent.core.Budgetcom.embabel.chat.agent.AgentProcessChatbot→com.embabel.agent.core.Verbositycom.embabel.chat.agent.AgentSource→com.embabel.agent.core.Agentcom.embabel.chat.agent.BlackboardFormatter→com.embabel.agent.core.Blackboardcom.embabel.chat.agent.DefaultBlackboardFormatter→com.embabel.agent.core.Blackboardcom.embabel.chat.agent.DefaultChatAgentBuilder→com.embabel.agent.core.Agentcom.embabel.chat.agent.DefaultChatAgentBuilder→com.embabel.agent.core.ToolGroup
- Direction
- chat.agent uses agent.core, so a change to agent.core can break chat.agent, while a change to chat.agent can't break agent.core.
- Position
- Below the diagonal: chat.agent uses a module listed above it, which is the healthy direction.
36→29 chat.agent uses agent.api.channel✕
- Connections
- 3 pairs of types, where a type in chat.agent uses a type in agent.api.channel.
- The types involved
com.embabel.chat.agent.AgentProcessChatSession→com.embabel.agent.api.channel.OutputChannelcom.embabel.chat.agent.AgentProcessChatbot→com.embabel.agent.api.channel.OutputChannelcom.embabel.chat.agent.ListenerProvider→com.embabel.agent.api.channel.OutputChannel
- Direction
- chat.agent uses agent.api.channel, so a change to agent.api.channel can break chat.agent, while a change to chat.agent can't break agent.api.channel.
- Position
- Below the diagonal: chat.agent uses a module listed above it, which is the healthy direction.
36→31 chat.agent uses agent.api.common✕
- Connections
- 2 pairs of types, where a type in chat.agent uses a type in agent.api.common.
- The types involved
com.embabel.chat.agent.AgentProcessChatbot→com.embabel.agent.api.common.PlannerTypecom.embabel.chat.agent.DefaultChatAgentBuilder→com.embabel.agent.api.common.TransformationActionContext
- Direction
- chat.agent uses agent.api.common, so a change to agent.api.common can break chat.agent, while a change to chat.agent can't break agent.api.common.
- Position
- Below the diagonal: chat.agent uses a module listed above it, which is the healthy direction.
37→17 agent.openai uses agent.spi✕
- Connections
- 1 pair of types, where a type in agent.openai uses a type in agent.spi.
- The types involved
com.embabel.agent.openai.OpenAiCompatibleModelFactory→com.embabel.agent.spi.LlmService
- Direction
- agent.openai uses agent.spi, so a change to agent.spi can break agent.openai, while a change to agent.openai can't break agent.spi.
- Position
- Below the diagonal: agent.openai uses a module listed above it, which is the healthy direction.
37→18 agent.openai uses common.ai.model✕
- Connections
- 17 pairs of types, where a type in agent.openai uses a type in common.ai.model.
- The types involved
com.embabel.agent.openai.CapabilityAwareOpenAiOptionsConverter→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.openai.CapabilityAwareOpenAiOptionsConverter→com.embabel.common.ai.model.OptionsConvertercom.embabel.agent.openai.Gpt5ChatOptionsConverter→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.openai.Gpt5ChatOptionsConverter→com.embabel.common.ai.model.OptionsConvertercom.embabel.agent.openai.OpenAiChatOptionsConverter→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.openai.OpenAiChatOptionsConverter→com.embabel.common.ai.model.OptionsConvertercom.embabel.agent.openai.OpenAiClientTimeouts→com.embabel.common.ai.model.OptionsConvertercom.embabel.agent.openai.OpenAiCompatibleModelFactory→com.embabel.common.ai.model.EmbeddingServicecom.embabel.agent.openai.OpenAiCompatibleModelFactory→com.embabel.common.ai.model.OptionsConvertercom.embabel.agent.openai.OpenAiCompatibleModelFactory→com.embabel.common.ai.model.PricingModelcom.embabel.agent.openai.OpenAiReadTimeoutOptionsConverter→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.openai.OpenAiReadTimeoutOptionsConverter→com.embabel.common.ai.model.OptionsConvertercom.embabel.agent.openai.OpenAiReasoningEffortKt→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.openai.OpenAiReasoningEffortOptionsConverter→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.openai.OpenAiReasoningEffortOptionsConverter→com.embabel.common.ai.model.OptionsConvertercom.embabel.agent.openai.StandardOpenAiOptionsConverter→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.openai.StandardOpenAiOptionsConverter→com.embabel.common.ai.model.OptionsConverter
- Direction
- agent.openai uses common.ai.model, so a change to common.ai.model can break agent.openai, while a change to agent.openai can't break common.ai.model.
- Position
- Below the diagonal: agent.openai uses a module listed above it, which is the healthy direction.
37→21 agent.openai uses common.ai.autoconfig✕
- Connections
- 1 pair of types, where a type in agent.openai uses a type in common.ai.autoconfig.
- The types involved
com.embabel.agent.openai.OpenAiCompatibleModelFactory→com.embabel.common.ai.autoconfig.NativeSupport
- Direction
- agent.openai uses common.ai.autoconfig, so a change to common.ai.autoconfig can break agent.openai, while a change to agent.openai can't break common.ai.autoconfig.
- Position
- Below the diagonal: agent.openai uses a module listed above it, which is the healthy direction.
37→35 agent.openai uses agent.spi.support.springai✕
- Connections
- 1 pair of types, where a type in agent.openai uses a type in agent.spi.support.springai.
- The types involved
com.embabel.agent.openai.OpenAiCompatibleModelFactory→com.embabel.agent.spi.support.springai.SpringAiNativeStructuredOutputConfigurer
- Direction
- agent.openai uses agent.spi.support.springai, so a change to agent.spi.support.springai can break agent.openai, while a change to agent.openai can't break agent.spi.support.springai.
- Position
- Below the diagonal: agent.openai uses a module listed above it, which is the healthy direction.
38→18 agent.rag.service uses common.ai.model✕
- Connections
- 2 pairs of types, where a type in agent.rag.service uses a type in common.ai.model.
- The types involved
com.embabel.agent.rag.service.RagServiceEnhancerProperties→com.embabel.common.ai.model.LlmOptionscom.embabel.agent.rag.service.SearchOperationsBuilder→com.embabel.common.ai.model.EmbeddingService
- Direction
- agent.rag.service uses common.ai.model, so a change to common.ai.model can break agent.rag.service, while a change to agent.rag.service can't break common.ai.model.
- Position
- Below the diagonal: agent.rag.service uses a module listed above it, which is the healthy direction.
38→28 agent.rag.service uses agent.core✕
- Connections
- 2 pairs of types, where a type in agent.rag.service uses a type in agent.core.
- The types involved
com.embabel.agent.rag.service.NamedEntityDataRepository→com.embabel.agent.core.DataDictionarycom.embabel.agent.rag.service.NamedEntityDataRepository→com.embabel.agent.core.DomainType
- Direction
- agent.rag.service uses agent.core, so a change to agent.core can break agent.rag.service, while a change to agent.rag.service can't break agent.core.
- Position
- Below the diagonal: agent.rag.service uses a module listed above it, which is the healthy direction.
38→31 agent.rag.service uses agent.api.common✕
- Connections
- 2 pairs of types, where a type in agent.rag.service uses a type in agent.api.common.
- The types involved
com.embabel.agent.rag.service.PromptRunnerRagResponseSummarizer→com.embabel.agent.api.common.PromptRunnercom.embabel.agent.rag.service.RagServiceEnhancer→com.embabel.agent.api.common.OperationContext
- Direction
- agent.rag.service uses agent.api.common, so a change to agent.api.common can break agent.rag.service, while a change to agent.rag.service can't break agent.api.common.
- Position
- Below the diagonal: agent.rag.service uses a module listed above it, which is the healthy direction.
38→33 agent.rag.service uses agent.rag.tools✕
- Connections
- 1 pair of types, where a type in agent.rag.service uses a type in agent.rag.tools.
- The types involved
com.embabel.agent.rag.service.PromptRunnerRagResponseSummarizer→com.embabel.agent.rag.tools.RagOptions
- Direction
- agent.rag.service uses agent.rag.tools, so a change to agent.rag.tools can break agent.rag.service, while a change to agent.rag.service can't break agent.rag.tools.
- Position
- Below the diagonal: agent.rag.service uses a module listed above it, which is the healthy direction.
38→39 agent.rag.service uses agent.rag.model part of a loop✕
- Connections
- 11 pairs of types, where a type in agent.rag.service uses a type in agent.rag.model.
- The types involved
com.embabel.agent.rag.service.ContentElementSearch→com.embabel.agent.rag.model.ContentElementcom.embabel.agent.rag.service.NamedEntityDataRepository→com.embabel.agent.rag.model.NamedEntitycom.embabel.agent.rag.service.NamedEntityDataRepository→com.embabel.agent.rag.model.NamedEntityDatacom.embabel.agent.rag.service.NamedEntityDataRepository→com.embabel.agent.rag.model.RelationshipDirectioncom.embabel.agent.rag.service.NamedEntityDataRepository→com.embabel.agent.rag.model.RelationshipNavigatorcom.embabel.agent.rag.service.NavigableRagService→com.embabel.agent.rag.model.Retrievablecom.embabel.agent.rag.service.RagResponse→com.embabel.agent.rag.model.Retrievablecom.embabel.agent.rag.service.ResultExpander→com.embabel.agent.rag.model.ContentElementcom.embabel.agent.rag.service.RetrievableResultsFormatter→com.embabel.agent.rag.model.Retrievablecom.embabel.agent.rag.service.SectionReader→com.embabel.agent.rag.model.Chunkcom.embabel.agent.rag.service.SimpleRetrievableResultsFormatter→com.embabel.agent.rag.model.Retrievable
- Direction
- agent.rag.service uses agent.rag.model, so a change to agent.rag.model can break agent.rag.service, while a change to agent.rag.service can't break agent.rag.model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
38→40 agent.rag.service uses agent.rag.ingestion part of a loop✕
- Connections
- 2 pairs of types, where a type in agent.rag.service uses a type in agent.rag.ingestion.
- The types involved
com.embabel.agent.rag.service.IngestingSearchOperationsBuilder→com.embabel.agent.rag.ingestion.ContentChunkercom.embabel.agent.rag.service.SearchOperationsBuilder→com.embabel.agent.rag.ingestion.ChunkTransformer
- Direction
- agent.rag.service uses agent.rag.ingestion, so a change to agent.rag.ingestion can break agent.rag.service, while a change to agent.rag.service can't break agent.rag.ingestion.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
39→28 agent.rag.model uses agent.core✕
- Connections
- 2 pairs of types, where a type in agent.rag.model uses a type in agent.core.
- The types involved
com.embabel.agent.rag.model.NamedEntityData→com.embabel.agent.core.DomainTypecom.embabel.agent.rag.model.SimpleNamedEntityData→com.embabel.agent.core.DomainType
- Direction
- agent.rag.model uses agent.core, so a change to agent.core can break agent.rag.model, while a change to agent.rag.model can't break agent.core.
- Position
- Below the diagonal: agent.rag.model uses a module listed above it, which is the healthy direction.
39→38 agent.rag.model uses agent.rag.service✕
- Connections
- 1 pair of types, where a type in agent.rag.model uses a type in agent.rag.service.
- The types involved
com.embabel.agent.rag.model.RelationshipNavigator→com.embabel.agent.rag.service.RetrievableIdentifier
- Direction
- agent.rag.model uses agent.rag.service, so a change to agent.rag.service can break agent.rag.model, while a change to agent.rag.model can't break agent.rag.service.
- Position
- Below the diagonal: agent.rag.model uses a module listed above it, which is the healthy direction.
40→12 agent.rag.ingestion uses agent.tools.file✕
- Connections
- 2 pairs of types, where a type in agent.rag.ingestion uses a type in agent.tools.file.
- The types involved
com.embabel.agent.rag.ingestion.HierarchicalContentReader→com.embabel.agent.tools.file.FileReadToolscom.embabel.agent.rag.ingestion.TikaHierarchicalContentReader→com.embabel.agent.tools.file.FileReadTools
- Direction
- agent.rag.ingestion uses agent.tools.file, so a change to agent.tools.file can break agent.rag.ingestion, while a change to agent.rag.ingestion can't break agent.tools.file.
- Position
- Below the diagonal: agent.rag.ingestion uses a module listed above it, which is the healthy direction.
40→39 agent.rag.ingestion uses agent.rag.model✕
- Connections
- 22 pairs of types, where a type in agent.rag.ingestion uses a type in agent.rag.model.
- The types involved
com.embabel.agent.rag.ingestion.AbstractChunkTransformer→com.embabel.agent.rag.model.Chunkcom.embabel.agent.rag.ingestion.ChunkTransformationContext→com.embabel.agent.rag.model.ContentRootcom.embabel.agent.rag.ingestion.ChunkTransformationContext→com.embabel.agent.rag.model.Sectioncom.embabel.agent.rag.ingestion.ChunkTransformer→com.embabel.agent.rag.model.Chunkcom.embabel.agent.rag.ingestion.ContentChunker→com.embabel.agent.rag.model.Chunkcom.embabel.agent.rag.ingestion.ContentChunker→com.embabel.agent.rag.model.NavigableContainerSectioncom.embabel.agent.rag.ingestion.ContentFormatParser→com.embabel.agent.rag.model.MaterializedDocumentcom.embabel.agent.rag.ingestion.ContentFormatParserUtils→com.embabel.agent.rag.model.LeafSectioncom.embabel.agent.rag.ingestion.ContentFormatParserUtils→com.embabel.agent.rag.model.MaterializedDocumentcom.embabel.agent.rag.ingestion.ContentFormatParserUtils→com.embabel.agent.rag.model.NavigableSectioncom.embabel.agent.rag.ingestion.ContentRefreshPolicy→com.embabel.agent.rag.model.NavigableDocumentcom.embabel.agent.rag.ingestion.DirectoryParsingResult→com.embabel.agent.rag.model.NavigableDocumentcom.embabel.agent.rag.ingestion.HierarchicalContentReader→com.embabel.agent.rag.model.NavigableDocumentcom.embabel.agent.rag.ingestion.HtmlContentParser→com.embabel.agent.rag.model.MaterializedDocumentcom.embabel.agent.rag.ingestion.InMemoryContentChunker→com.embabel.agent.rag.model.Chunkcom.embabel.agent.rag.ingestion.InMemoryContentChunker→com.embabel.agent.rag.model.ContentRootcom.embabel.agent.rag.ingestion.InMemoryContentChunker→com.embabel.agent.rag.model.LeafSectioncom.embabel.agent.rag.ingestion.InMemoryContentChunker→com.embabel.agent.rag.model.NavigableContainerSectioncom.embabel.agent.rag.ingestion.InMemoryContentChunker→com.embabel.agent.rag.model.Sectioncom.embabel.agent.rag.ingestion.MarkdownContentParser→com.embabel.agent.rag.model.MaterializedDocumentcom.embabel.agent.rag.ingestion.PlainTextContentParser→com.embabel.agent.rag.model.MaterializedDocumentcom.embabel.agent.rag.ingestion.TikaHierarchicalContentReader→com.embabel.agent.rag.model.MaterializedDocument
- Direction
- agent.rag.ingestion uses agent.rag.model, so a change to agent.rag.model can break agent.rag.ingestion, while a change to agent.rag.ingestion can't break agent.rag.model.
- Position
- Below the diagonal: agent.rag.ingestion uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 34 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | Medium |
| A02:2025 — Security Misconfiguration | 4 | Medium |
Roadmap
Top priorities: Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry); Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release; Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry). | +5.2 pts | Medium | Outbound HTTP resilience |
| Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.0 pts | Medium | Release Hygiene |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.9 pts | Low | Supply-chain Provenance & Signing |
| Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose. | +1.8 pts | Medium | Web-Security Posture |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with pom.xml. | +0.9 pts | Low | ADR Quality |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. | +0.5 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/ChatClientLlmOperations.kt | 5.6 | Mixed | God Classes: ClassTooLong: ChatClientLlmOperations |
| embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/AgentMetadataReader.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/workflow/loop/RepeatUntil.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| embabel-agent-api/src/main/kotlin/com/embabel/agent/api/dsl/TypedAgentScopeBuilder.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.1 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| embabel-agent-shell/src/main/kotlin/com/embabel/agent/shell/TerminalServices.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/StateActionMethodManager.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/workflow/loop/RepeatUntilAcceptable.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/BlackboardWorldStateDeterminer.kt | 6.9 | Mixed | Explicit Debt: TodoComment |
| embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt | 7.0 | Mixed | God Classes: ClassTooLong: ToolLoopLlmOperations |
| embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/support/BranchingAction.kt | 7.0 | Mixed | Code Duplication: Edited copy of a member (19 corresponding lines) |
| embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/ingestion/InMemoryContentChunker.kt | 7.0 | Mixed | Cyclomatic Complexity: InMemoryContentChunker.splitText (cyclomatic 22) |
| embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt | 7.0 | Mixed | Cyclomatic Complexity: DomainTypeInputSchema.buildParameterSchema (cyclomatic 20) |
| embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DefaultActionMethodManager.kt | 7.0 | Mixed | Cognitive Complexity: DefaultActionMethodManager.invokeActionMethodKotlinReflect (cognitive 26) |
| embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/progressive/UnfoldingTool.kt | 7.1 | Mixed | Cognitive Complexity: Factory.fromInstanceKotlin (cognitive 18) |
| embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/streaming/StreamingChatClientOperations.kt | 7.1 | Mixed | Code Duplication: Edited copy of a member (53 corresponding lines) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 62 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 62 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 410 of 438 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java, .kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.java, .kt), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because repo.embabel.com — the registry that answers it — was asked and did not reply (the build stopped because repo.embabel.com, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it, so the dependency graph was not resolved). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add repo.embabel.com to the allowlist and re-run — not to build anything.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (embabel-agent-dependencies/pom.xml), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Osv-scanner exited 127 with no findings — dependency CVEs were not measured. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/client/A2AHttpClientFactory.kt`, `embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/MethodDefinedOperationNameGenerator.kt`, `embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/InteractionId.kt`, `embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/StuckHandler.kt`, `embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/Transformation.kt`, … (+62 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D43 Malicious Dependencies — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Osv-scanner exited 127 with no findings — dependency CVEs were not measured. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The frontend declares that it computes whether a construction is produced or passed, yet 2013 of 2357 constructions arrived without the answer. Arm two skipped them; it did not clear them.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Java, Kotlin, Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin, Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 49 further occurrence(s) are not listed individually; the score already reflects all 89.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
14 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was EmbabelSpanEventListener.onProcessEvent at 33. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being InMemoryPropertyFilter.matches at 22 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: embabel-agent-api/src/main/kotlin/com/embabel/agent/filter/InMemoryPropertyFilter.kt (InMemoryPropertyFilter.matches at 22), embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/spring/SpringVectorStoreVectorSearch.kt (SpringVectorStoreVectorSearchKt.toSpringAiExpression at 20), embabel-agent-observability/src/main/java/com/embabel/agent/observability/metrics/EmbabelMetricsEventListener.java (EmbabelMetricsEventListener.onProcessEvent at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 14 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with EmbabelSpanEventListener.onProcessEvent (cyclomatic 33), LoggingAgenticEventListener.onProcessEvent (cyclomatic 30), FileReadToolsKt.globToRegex (cyclomatic 30). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 14 together lifts Cyclomatic Complexity from 8.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
24 method(s) exceeded the cognitive complexity threshold of 15; the worst was InMemoryContentChunker.splitText at 53.
What to do
- Bring the 24 bodies over 15 down to 15 or less in Cognitive Complexity — start with InMemoryContentChunker.splitText (cognitive 53), FileReadToolsKt.globToRegex (cognitive 50), AgentMetadataReader.createAgentMetadata (cognitive 44). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 24 together lifts Cognitive Complexity from 6.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
20 god class(es) detected.
What to do
- Resolve the 7 MethodTooLong finding(s) in God Classes — start with ChatClientLlmOperations.kt (2), RepeatUntilAcceptable.kt, AgentMetadataReader.kt. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 5 TooManyMethods finding(s) in God Classes — start with ObservabilityProperties.java, ConfigurableModelProvider.kt, LuceneSearchOperations.kt. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 ClassTooLong finding(s) in God Classes — start with ToolLoopLlmOperations.kt, LuceneSearchOperations.kt, ChatClientLlmOperations.kt. — One of this dimension's main actionable groups (4 warning-level).
D4 · Code Duplication
74 duplicated block group(s) detected. 3.8 % of the production lines (4,381 of 115,995) are in a reported copy. A further 76 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 8 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with DefaultActionMethodManager.kt, CredentialEndpointConfig.kt, StreamingChatClientOperations.kt. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 7 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with DefaultActionMethodManager.kt (2), AutonomyA2ARequestHandler.kt, UnfoldingTool.kt. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 6 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with DomainTypeInputSchema.kt (2), PlaybookToolInjectionStrategy.kt, llmOperationGuardRails.kt. — One of this dimension's main actionable groups (6 warning-level).
D5 · Coupling
84 production modules (Maven+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 7 module(s) off the main sequence, with abstractness counted on 52 of the 84 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 7 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (7 warning-level).
D6 · Cohesion (LCOM4)
0 of 243 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 16 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 92 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 381 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/AgentMetadataReader.kt (5×23=115); embabel-agent-observability/src/main/java/com/embabel/agent/observability/tracing/EmbabelSpanEventListener.java (3×33=99) Repeated repair below the complexity floor: embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/tools/ToolishRag.kt (3 of 5 changes were fixes); embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/tools/CoreSearchTools.kt (3 of 5 changes were fixes); embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/server/support/AutonomyA2ARequestHandler.kt (3 of 4 changes were fixes)
What to do
- Resolve the 6 Repeated repair finding(s) in Churn × Complexity Hotspots — start with ToolishRag.kt, CoreSearchTools.kt, AutonomyA2ARequestHandler.kt. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with AgentMetadataReader.kt, EmbabelSpanEventListener.java. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
151 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is embabel-agent-rag/embabel-agent-rag-lucene/src/main/kotlin/com/embabel/agent/rag/lucene/LuceneSearchOperations.kt. Counted over 602 of the 972 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 7 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (7 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
36 deducted task-comment markers across 115995 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 36 TodoComment finding(s) in Explicit Debt — start with BlackboardWorldStateDeterminer.kt (3), TypedAgentScopeBuilder.kt (3), AgentPlatformTypedOps.kt (2). — One of this dimension's main actionable groups (36 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 37 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with pom.xml. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
3 of 52 build units (Maven) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
32 % of calls cross a namespace and 37 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
34 finding(s): 0 critical, 33 high, 1 medium, 0 low. 23 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 5 file(s) — `.github/scripts/sync-primary-to-upgrade.sh`, `embabel-agent-observability/src/main/java/com/embabel/agent/observability/mdc/MdcPropagationEventListener.java` (line 72, line 76, line 77, …), `embabel-agent-observability/src/main/java/com/embabel/agent/observability/metrics/EmbabelMetricsEventListener.java` (line 104, line 108, line 113, …), `embabel-agent-observability/src/main/java/com/embabel/agent/observability/tracing/EmbabelSpanEventListener.java` (line 110, line 115, line 120, …), `REDACTED` (line 67) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 21 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (21 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: osv-scanner exited 127 with no findings — dependency CVEs were not measured), so this is not the whole dependency surface and the result is reported at reduced confidence.
D31 · IaC & Container Security
4 finding(s): 0 critical, 0 high, 4 medium, 0 low.
What to do
- Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
D34 · Knowledge Freshness
5 of 602 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/UnsupportedRequestParameterRetry.kt. Counted over 602 of the 972 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: OpenAiModelsConfig.kt↔OpenAiCustomModelsConfig.kt 69%; BranchingAction.kt↔TransformationAction.kt 54%; ContentChunker.kt↔HierarchicalContentReader.kt 50%
What to do
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with OpenAiModelsConfig.kt, BranchingAction.kt, ContentChunker.kt. — One of this dimension's main actionable groups (4 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: osv-scanner exited 127 with no findings — dependency CVEs were not measured), so this is not the whole dependency surface and the result is reported at reduced confidence.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 110 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
- `DefaultAgentPlatform` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (agents; e.g. `agents` in `deploy` at line 120). — embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/DefaultAgentPlatform.kt:43
- `AgenticEventListenerToolsStats` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (_stats; e.g. `_stats` in `record` at line 31). — embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/AgenticEventListenerToolsStats.kt:24
- `DelegatingAgentScanningBeanPostProcessor` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (agentScanningBeanPostProcessor; e.g. `agentScanningBeanPostProcessor` in `onApplicationEvent` at line 96). — embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/AutoRegistration.kt:83
- `ShellCommands` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (blackboard, persistentToolCallContext, openMode, defaultProcessOptions, agentProcesses; e.g. `blackboard` in `clear` at line 98). — embabel-agent-shell/src/main/kotlin/com/embabel/agent/shell/ShellCommands.kt:52
What to do
- Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
AX3 · Project dependency cycles
AX4 · Dependency direction
- `embabel-agent-domain` is a Domain project but references `embabel-agent-api`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
What to do
- Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
AX5 · Architecture & structure
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
- `PersistentAgentProcessRepository.delete` saves `AgentProcessSnapshotStore`, `AgentProcessRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/persistence/PersistentAgentProcessRepository.kt:78
- `AbstractChunkingContentElementRepository.writeAndChunkDocument` saves `NavigableDocument`, `NavigableSection`, `Chunk` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/store/AbstractChunkingContentElementRepository.kt:71
What to do
- Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 42/44 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `embabel-agent-autoconfigure/embabel-agent-mcpserver-security-autoconfigure`, `embabel-agent-test-support/embabel-agent-test-internal`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- `embabel-agent-docs/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — embabel-agent-docs/package.json:5
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
- `RestClient.create(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/client/EmbabelA2AClient.kt:49
- `RestClient.builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — embabel-agent-autoconfigure/models/embabel-agent-onnx-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/onnx/embeddings/OnnxEmbeddingAutoConfiguration.kt:74, embabel-agent-onnx/src/main/kotlin/com/embabel/agent/onnx/OnnxModelLoader.kt:36
- `HttpClient.newBuilder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — embabel-agent-autoconfigure/models/embabel-agent-onnx-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/onnx/embeddings/OnnxEmbeddingAutoConfiguration.kt:76, embabel-agent-onnx/src/main/kotlin/com/embabel/agent/onnx/OnnxModelLoader.kt:39
What to do
- Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `https://cdn.jsdelivr.net/npm/@asciidoctor/tabs@1.0.0-beta.6/dist/js/tabs.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. — embabel-agent-docs/src/main/asciidoc/docinfo-header.html:4
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `normalizeRequiredFields` is public, takes a document from its caller (line 104) and hands it to `normalizeRequiredFields`, which calls itself at line 130 with a piece of `schemaNode` — the function is not `tailrec`, so every call is a real frame — and nowhere in `normalizeRequiredFields` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `normalizeRequiredFields` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — embabel-agent-common/embabel-agent-ai/src/main/kotlin/com/embabel/common/ai/converters/jsonSchemaSupport.kt:130
- `hasUnsupportedJsonSchemaKeywords` is public and takes its `JsonNode` receiver from its caller, and it calls itself at line 323 with a piece of its receiver — the function is not `tailrec`, so every call is a real frame — and nowhere in `hasUnsupportedJsonSchemaKeywords` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `hasUnsupportedJsonSchemaKeywords` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — embabel-agent-common/embabel-agent-ai/src/main/kotlin/com/embabel/common/ai/converters/jsonSchemaSupport.kt:323
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
- `debug` at line 85 is called with an argument built by `selected.joinToString { "…" it.skill.name "…".format(it.score) }` (line 88), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/EmbeddingSkillSelector.kt:85
- `debug` at line 176 is called with an argument built by `containerCmd.joinToString("…")` (line 176), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/script/AbstractContainerSkillScriptExecutionEngine.kt:176
- `debug` at line 112 is called with an argument built by `toolsToRemove.joinToString("…")` (line 112), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:112
- `debug` at line 157 is called with an argument built by `initialWorldState.entries.joinToString { "…" it.key it.value }` (line 159), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/validation/GoapPathToCompletionValidator.kt:157
- `debug` at line 141 is called with an argument built by `state.conversationHistory.joinToString("…")` (line 143), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/loop/support/DefaultToolLoop.kt:141
- `debug` at line 121 is called with an argument built by `connectionNames.joinToString("…")` (line 123), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/config/spring/ToolGroupsConfiguration.kt:121
- `debug` at line 195 is called with an argument built by `mcpSyncClients.map { it.serverInfo }.joinToString("…", prefix = if (mcpSyncClients.isEmpty()) "…" else "…")` (line 199), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/config/spring/ToolGroupsConfiguration.kt:195
- `debug` at line 230 is called with an argument built by `gid.tools.joinToString("…")` (line 232), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/config/spring/ToolGroupsConfiguration.kt:230
- `debug` at line 152 is called with an argument built by `mergedSchemaTypes.joinToString("…")` (line 155), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — embabel-agent-api/src/main/kotlin/com/embabel/agent/core/Agent.kt:152
- `debug` at line 118 is called with an argument built by `knownConditions.sorted()` (line 122), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/BlackboardWorldStateDeterminer.kt:118
- `debug` at line 155 is called with an argument built by `knownConditions.sorted()` (line 159), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/BlackboardWorldStateDeterminer.kt:155
- `debug` at line 167 is called with an argument built by `knownConditions.sorted()` (line 170), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/BlackboardWorldStateDeterminer.kt:167
- `debug` at line 177 is called with an argument built by `agentPlatform.agents().joinToString("…")` (line 182), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/autonomy/Autonomy.kt:177
- `debug` at line 315 is called with an argument built by `agentScope.goals.joinToString("…")` (line 320), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/autonomy/Autonomy.kt:315
What to do
- In Kotlin, hand the logger a lambda it calls only when the level is on (`logger.debug { "rows: ${rows.joinToString()}" }` — kotlin-logging and Log4j 2's Kotlin API take one), or put the line behind `if (log.isDebugEnabled)` (`if (BuildConfig.DEBUG)` for a line only a debug build needs). A string template is not the fix on SLF4J or Timber: their message is a `String`, so every `joinToString` or `toJson` inside the `${…}` runs before the call is entered.
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×8) — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/support/LoadedSkill.kt:130, embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/NamedEntityDataRepository.kt:192, embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/NamedEntityDataRepository.kt:223, …
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/model/NamedEntity.kt:111, embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/TypeBasedInputSchema.kt:123
- `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×9) — embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/filter/InMemoryPropertyFilter.kt:142, embabel-agent-code/src/main/kotlin/com/embabel/coding/tools/git/GitOperations.kt:68, embabel-agent-code/src/main/kotlin/com/embabel/coding/tools/git/GitOperations.kt:88, …
What to do
- Swallowed exception (caught, then discarded)
X4 · Structured logging
- `info` at line 119 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/Skills.kt:119
- `info` at line 128 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/Skills.kt:128
- `warn` at line 138 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/Skills.kt:138
- `info` at line 140 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/Skills.kt:140
- `warn` at line 167 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/Skills.kt:167
- `info` at line 169 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/Skills.kt:169
- `warn` at line 188 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/Skills.kt:188
- `info` at line 190 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/Skills.kt:190
- `warn` at line 196 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/script/AbstractContainerSkillScriptExecutionEngine.kt:196
- `error` at line 282 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/script/AbstractContainerSkillScriptExecutionEngine.kt:282
- `error` at line 299 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/script/AbstractContainerSkillScriptExecutionEngine.kt:299
- `error` at line 302 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/script/AbstractContainerSkillScriptExecutionEngine.kt:302
- `warn` at line 533 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/script/AbstractContainerSkillScriptExecutionEngine.kt:533
- `error` at line 574 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/script/AbstractContainerSkillScriptExecutionEngine.kt:574
- `warn` at line 430 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-shell/src/main/kotlin/com/embabel/agent/shell/ShellCommands.kt:430
- `error` at line 72 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:72
- `warn` at line 118 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:118
- `debug` at line 144 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:144
- `error` at line 147 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:147
- `debug` at line 176 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:176
- `error` at line 179 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:179
- `debug` at line 208 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:208
- `error` at line 211 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:211
- `debug` at line 72 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. (×2) — embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/sync/McpServerStrategy.kt:72, embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/async/McpAsyncServerStrategy.kt:72
- `warn` at line 110 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-common/embabel-agent-webmvc/src/main/kotlin/com/embabel/agent/web/sse/SseController.kt:110
- `warn` at line 36 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-common/embabel-agent-webmvc/src/main/kotlin/com/embabel/agent/web/rest/GlobalExceptionHandler.kt:36
- `warn` at line 66 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-code/src/main/kotlin/com/embabel/coding/tools/jvm/JavaParserApiExtractor.kt:66
- `warn` at line 86 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-code/src/main/kotlin/com/embabel/coding/tools/jvm/JavaParserApiExtractor.kt:86
- `warn` at line 89 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-code/src/main/kotlin/com/embabel/coding/tools/jvm/JavaParserApiExtractor.kt:89
- `warn` at line 105 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-code/src/main/kotlin/com/embabel/coding/tools/jvm/JavaParserApiExtractor.kt:105
- `info` at line 129 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/file/FileWriteTools.kt:129
- `info` at line 141 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/file/FileWriteTools.kt:141
- `info` at line 171 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/file/FileWriteTools.kt:171
- `warn` at line 67 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/agent/AgentTool.kt:67
- `info` at line 93 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. (×2) — embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/agent/AgentTool.kt:93, embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/agent/GoalTool.kt:93
- `info` at line 83 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/agent/DefaultProcessCallbackTools.kt:83
- `info` at line 125 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/agent/DefaultProcessCallbackTools.kt:125
- `warn` at line 69 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/agent/GoalTool.kt:69
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 76% | Strong | Solid. |
| Architecture | 78% | Strong | Solid. |
| Maturity | 78% | Strong | Solid. |
| Readiness | 57% | Adequate — gated by P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 70% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 98% | Exemplary | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D11 Test Reliability — 1 observation(s) recorded · This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.java, .kt), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- X10 Duplicated predicate — 15 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 63 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (17 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (17 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (17 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (17 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (17 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (17 DOM element(s) < 25) — too little surface to assess accessibility.
- AX6 Interface segregation — AX6 reached only 7% of this repository's production lines — kotlin (108,317 lines), python (27 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~205099 lines of test source are present (.java, .kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D12 Dependency Hygiene — Dependency currency not established — repo.embabel.com did not answer
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency does not read html yet; not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .java, .kt, .py source were not judged.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 67 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 3 event handler(s); 1 CQRS handler(s)
- ED5 Idempotency — Not assessed, and this one is on us: 4 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Java, Python and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Kotlin request outside a suspend function has no caller's cancellation to honour
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 35 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dependency-rule violation: embabel-agent-domain (Domain) → embabel-agent-api (Web)
- Test declared unreliable: embabel-agent-api/src/test/kotlin/com/embabel/agent/api/dsl/MapperTest.kt embabel-agent-api/src/test/kotlin/com/embabel/agent/api/dsl/MapperTest.kt:36
- REDACTED
Serious — 306 finding(s)
- TodoComment embabel-agent-shell/src/main/kotlin/com/embabel/agent/shell/TerminalServices.kt:195
- TodoComment embabel-agent-shell/src/main/kotlin/com/embabel/agent/shell/formatProcessOutput.kt:40
- TodoComment embabel-agent-rag/embabel-agent-rag-pipeline/src/main/kotlin/com/embabel/agent/rag/service/support/FacetedRagService.kt:47
- TodoComment embabel-agent-rag/embabel-agent-rag-pipeline/src/main/kotlin/com/embabel/agent/rag/pipeline/AdaptivePipelineRagResponseEnhancer.kt:94
- TodoComment embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/BlackboardWorldStateDeterminer.kt:92
- TodoComment embabel-agent-rag/embabel-agent-rag-pipeline/src/main/kotlin/com/embabel/agent/rag/pipeline/DeduplicatingEnhancer.kt:29
- TodoComment embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/store/ChunkingContentElementRepository.kt:65
- TodoComment embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/sync/support/PerGoalMcpExportToolCallbackPublisher.kt:152
- TodoComment embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/async/support/PerGoalAsyncMcpToolExportCallbackPublisher.kt:144
- TodoComment embabel-agent-code/src/main/kotlin/com/embabel/coding/tools/jvm/MavenBuildSystemIntegration.kt:28
- TodoComment embabel-agent-api/src/test/kotlin/com/embabel/agent/api/common/thinking/support/ThinkingPromptRunnerOperationsImpl.kt:156
- TodoComment embabel-agent-api/src/test/kotlin/com/embabel/agent/api/annotation/support/conditionAnnotationActions.kt:18
- TodoComment embabel-agent-api/src/test/java/com/embabel/agent/api/common/autonomy/MultiGoal.java:72
- TodoComment embabel-agent-api/src/main/kotlin/com/embabel/ux/form/SimpleFormGenerator.kt:169
- TodoComment embabel-agent-api/src/main/kotlin/com/embabel/chat/agent/BlackboardFormatter.kt:54
- TodoComment embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/agent/GoalTool.kt:80
- TodoComment embabel-agent-api/src/main/kotlin/com/embabel/agent/test/integration/DummyObjectCreatingLlmOperations.kt:63
- TodoComment embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/AutoLlmSelectionCriteriaResolver.kt:25
- TodoComment embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/config/spring/ToolGroupsConfiguration.kt:302
- TodoComment embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/BlackboardWorldStateDeterminer.kt:58
- TodoComment embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/BlackboardWorldStateDeterminer.kt:79
- TodoComment embabel-agent-api/src/main/kotlin/com/embabel/agent/api/dsl/AgentBuilder.kt:230
- TodoComment embabel-agent-api/src/main/kotlin/com/embabel/agent/api/dsl/TypedAgentScopeBuilder.kt:399
- TodoComment embabel-agent-api/src/main/kotlin/com/embabel/agent/api/dsl/TypedAgentScopeBuilder.kt:521
- TodoComment embabel-agent-api/src/main/kotlin/com/embabel/agent/api/dsl/TypedAgentScopeBuilder.kt:531
- Swallowed exception (caught, then discarded) embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/support/LoadedSkill.kt:130
- Swallowed exception (caught, then discarded) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/NamedEntityDataRepository.kt:192
- Swallowed exception (caught, then discarded) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/NamedEntityDataRepository.kt:223
- Swallowed exception (caught, then discarded) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/NamedEntityDataRepository.kt:258
- Swallowed exception (caught, then discarded) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/NamedEntityDataRepository.kt:293
- Swallowed exception (caught, then discarded) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/model/NamedEntityInvocationHandler.kt:231
- Swallowed exception (caught, then discarded) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/filter/InMemoryPropertyFilter.kt:142
- Swallowed exception (caught, then discarded) embabel-agent-code/src/main/kotlin/com/embabel/coding/tools/git/GitOperations.kt:68
- Swallowed exception (caught, then discarded) embabel-agent-code/src/main/kotlin/com/embabel/coding/tools/git/GitOperations.kt:88
- Swallowed exception (caught, then discarded) embabel-agent-code/src/main/kotlin/com/embabel/coding/tools/git/GitOperations.kt:99
- Swallowed exception (caught, then discarded) embabel-agent-code/src/main/kotlin/com/embabel/coding/tools/git/GitOperations.kt:113
- Swallowed exception (caught, then discarded) embabel-agent-code/src/main/kotlin/com/embabel/coding/tools/git/GitOperations.kt:129
- Swallowed exception (caught, then discarded) embabel-agent-code/src/main/kotlin/com/embabel/coding/tools/git/GitOperations.kt:144
- Swallowed exception (caught, then discarded) embabel-agent-code/src/main/kotlin/com/embabel/coding/tools/git/GitOperations.kt:159
- Swallowed exception (caught, then discarded) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/UnsupportedRequestParameterRetry.kt:94
- Swallowed exception (caught, then discarded) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/progressive/UnfoldingTool.kt:730
- Swallowed exception (caught, then discarded) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/progressive/UnfoldingTool.kt:913
- Duplicated block (7 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DefaultActionMethodManager.kt:282
- Duplicated block (7 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-byok-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/byok/CredentialEndpointConfig.kt:144
- Duplicated block (7 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/streaming/StreamingChatClientOperations.kt:142
- Duplicated block (7 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-anthropic-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/anthropic/AnthropicModelLoader.kt:41
- Duplicated block (7 lines × 2) embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/script/DockerSkillScriptExecutionEngine.kt:137
- Duplicated block (7 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/ux/form/FormBinder.kt:117
- Duplicated block (7 lines × 2) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/ingestion/InMemoryContentChunker.kt:362
- Duplicated block (7 lines × 2) embabel-agent-autoconfigure/embabel-agent-platform-autoconfigure/src/main/java/com/embabel/agent/autoconfigure/platform/QuiteMcpClientAutoConfiguration.java:165
- MethodTooLong: RepeatUntilAcceptable.build embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/workflow/loop/RepeatUntilAcceptable.kt:114
- MethodTooLong: AgentMetadataReader.createAgentMetadata embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/AgentMetadataReader.kt:140
- MethodTooLong: RepeatUntil.build embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/workflow/loop/RepeatUntil.kt:77
- MethodTooLong: ToolLoopLlmOperations.doTransformWithThinkingIfPossible embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt:502
- MethodTooLong: GoapPathToCompletionValidator.validate embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/validation/GoapPathToCompletionValidator.kt:45
- MethodTooLong: ChatClientLlmOperations.doTransformWithThinkingIfPossibleSpringAi embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/ChatClientLlmOperations.kt:479
- MethodTooLong: ChatClientLlmOperations.doTransformWithThinkingSpringAi embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/ChatClientLlmOperations.kt:318
- Duplicated block (9 lines × 2) embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/server/support/AutonomyA2ARequestHandler.kt:363
- Duplicated block (9 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DefaultActionMethodManager.kt:311
- Duplicated block (9 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DefaultActionMethodManager.kt:330
- Duplicated block (9 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/progressive/UnfoldingTool.kt:485
- Duplicated block (9 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/invocation/SupervisorInvocation.kt:83
- Duplicated block (9 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/common/ai/model/ConfigurableEmbeddingRoleResolver.kt:96
- Duplicated block (9 lines × 2) embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/async/support/PerGoalStartingInputTypesPromptPublisher.kt:51
- Off the main sequence: embabel-agent-platform-autoconfigure
- Off the main sequence: embabel-agent-ai
- Off the main sequence: embabel-agent-cache-core
- Off the main sequence: embabel-agent-mcpserver
- Off the main sequence: embabel-agent-openai
- Off the main sequence: embabel-agent-api
- Off the main sequence: embabel-agent-byok
- Repeated repair: embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/tools/ToolishRag.kt embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/tools/ToolishRag.kt:329
- Repeated repair: embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/tools/CoreSearchTools.kt embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/tools/CoreSearchTools.kt:304
- Repeated repair: embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/server/support/AutonomyA2ARequestHandler.kt embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/server/support/AutonomyA2ARequestHandler.kt:82
- Repeated repair: embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/VictoolsSchemaGenerator.kt embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/VictoolsSchemaGenerator.kt:159
- Repeated repair: embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/server/support/A2AEndpointRegistrar.kt embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/server/support/A2AEndpointRegistrar.kt:125
- Repeated repair: embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/server/support/A2AStreamingHandler.kt embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/server/support/A2AStreamingHandler.kt:71
- Duplicated block (10 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt:128
- Duplicated block (10 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt:171
- Duplicated block (10 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/agentic/playbook/PlaybookToolInjectionStrategy.kt:87
- Duplicated block (10 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/guardrails/llmOperationGuardRails.kt:50
- Duplicated block (10 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-lmstudio-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/lmstudio/LmStudioModelsConfig.kt:188
- Duplicated block (10 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/streaming/StreamingChatClientOperations.kt:295
- Duplicated block (5 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DefaultActionMethodManager.kt:239
- Duplicated block (5 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-google-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/googlegenai/GoogleGenAiModelsConfig.kt:273
- Duplicated block (5 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-cloudflare-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/cloudflare/CloudflareModelsConfig.kt:135
- Duplicated block (5 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/MultimodalContent.kt:169
- Duplicated block (5 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/event/EmbeddingEvent.kt:121
- Duplicated block (5 lines × 2) embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/client/spi/SpringRestClientA2AHttpClient.kt:67
- TooManyMethods: ObservabilityProperties embabel-agent-observability/src/main/java/com/embabel/agent/observability/ObservabilityProperties.java:31
- TooManyMethods: ConfigurableModelProvider embabel-agent-api/src/main/kotlin/com/embabel/common/ai/model/ConfigurableModelProvider.kt:206
- TooManyMethods: LuceneSearchOperations embabel-agent-rag/embabel-agent-rag-lucene/src/main/kotlin/com/embabel/agent/rag/lucene/LuceneSearchOperations.kt:89
- TooManyMethods: AbstractAgentProcess embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/AbstractAgentProcess.kt:53
- TooManyMethods: LoggingAgenticEventListener embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/logging/LoggingAgenticEventListener.kt:108
- Edited copy of a member (9 corresponding lines) embabel-agent-observability/src/main/java/com/embabel/agent/observability/tracing/EmbabelSpanEventListener.java:289
- Edited copy of a member (9 corresponding lines) embabel-agent-observability/src/main/java/com/embabel/agent/observability/tracing/EmbabelSpanEventListener.java:300
- Edited copy of a member (9 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-oci-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/ocigenai/OciGenAiChatModel.kt:315
- Edited copy of a member (9 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/workflow/control/ScatterGatherBuilder.kt:95
- Edited copy of a member (9 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/channel/OutputChannel.kt:99
- Duplicated block (8 lines × 2) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/ingestion/InMemoryContentChunker.kt:250
- Duplicated block (8 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/AgenticTool.kt:177
- Duplicated block (8 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/AgenticTool.kt:190
- Duplicated block (8 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/invocation/SupervisorInvocation.kt:93
- Duplicated block (8 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/TypeBasedInputSchema.kt:135
- Outbound HTTP without resilience embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/client/EmbabelA2AClient.kt:49
- Outbound HTTP without resilience embabel-agent-autoconfigure/models/embabel-agent-onnx-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/onnx/embeddings/OnnxEmbeddingAutoConfiguration.kt:74
- Outbound HTTP without resilience embabel-agent-autoconfigure/models/embabel-agent-onnx-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/onnx/embeddings/OnnxEmbeddingAutoConfiguration.kt:76
- Outbound HTTP without resilience embabel-agent-onnx/src/main/kotlin/com/embabel/agent/onnx/OnnxModelLoader.kt:36
- Outbound HTTP without resilience embabel-agent-onnx/src/main/kotlin/com/embabel/agent/onnx/OnnxModelLoader.kt:39
- Stateful singleton: DefaultAgentPlatform embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/DefaultAgentPlatform.kt:43
- Stateful singleton: AgenticEventListenerToolsStats embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/AgenticEventListenerToolsStats.kt:24
- Stateful singleton: DelegatingAgentScanningBeanPostProcessor embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/AutoRegistration.kt:83
- Stateful singleton: ShellCommands embabel-agent-shell/src/main/kotlin/com/embabel/agent/shell/ShellCommands.kt:52
- ClassTooLong: ToolLoopLlmOperations embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt:123
- ClassTooLong: LuceneSearchOperations embabel-agent-rag/embabel-agent-rag-lucene/src/main/kotlin/com/embabel/agent/rag/lucene/LuceneSearchOperations.kt:89
- ClassTooLong: ChatClientLlmOperations embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/ChatClientLlmOperations.kt:117
- ClassTooLong: AgentMetadataReader embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/AgentMetadataReader.kt:111
- FileTooLong: support/ToolLoopLlmOperations.kt embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt
- FileTooLong: lucene/LuceneSearchOperations.kt embabel-agent-rag/embabel-agent-rag-lucene/src/main/kotlin/com/embabel/agent/rag/lucene/LuceneSearchOperations.kt
- FileTooLong: springai/ChatClientLlmOperations.kt embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/ChatClientLlmOperations.kt
- FileTooLong: model/ConfigurableModelProvider.kt embabel-agent-api/src/main/kotlin/com/embabel/common/ai/model/ConfigurableModelProvider.kt
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Change coupling: OpenAiModelsConfig.kt ↔ OpenAiCustomModelsConfig.kt embabel-agent-autoconfigure/models/embabel-agent-openai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/openai/OpenAiModelsConfig.kt:1
- Change coupling: BranchingAction.kt ↔ TransformationAction.kt embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/support/BranchingAction.kt:1
- Change coupling: ContentChunker.kt ↔ HierarchicalContentReader.kt embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/ingestion/ContentChunker.kt:1
- Change coupling: ChatClientLlmOperations.kt ↔ messageConverters.kt embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/ChatClientLlmOperations.kt:1
- Edited copy of a member (18 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-oci-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/ocigenai/OciGenAiChatModel.kt:351
- Edited copy of a member (18 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/common/ai/model/local/LocalModelRoleResolver.kt:84
- Edited copy of a member (18 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/common/ai/model/ConfigurableEmbeddingRoleResolver.kt:57
- Edited copy of a member (18 corresponding lines) embabel-agent-jdbc/src/main/kotlin/com/embabel/agent/jdbc/JdbcAgentProcessSnapshotStore.kt:119
- Edited copy of a member (15 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DefaultActionMethodManager.kt:238
- Edited copy of a member (15 corresponding lines) embabel-agent-observability/src/main/java/com/embabel/agent/observability/tracing/EmbabelLlmObservationConvention.java:64
- Edited copy of a member (15 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-bedrock-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/bedrock/BedrockModelsConfig.kt:232
- Edited copy of a member (15 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/InMemoryBlackboard.kt:182
- Edited copy of a member (10 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-oci-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/ocigenai/OciGenAiChatModel.kt:233
- Edited copy of a member (10 corresponding lines) embabel-agent-autoconfigure/embabel-agent-observability-autoconfigure/src/main/java/com/embabel/agent/autoconfigure/observability/HttpRequestObservationFilter.java:115
- Edited copy of a member (10 corresponding lines) embabel-agent-openai/src/main/kotlin/com/embabel/agent/openai/OpenAiCompatibleModelFactory.kt:524
- Edited copy of a member (10 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/JvmType.kt:329
- Members sharing a duplicated core (4 members, 50+ identical tokens) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/AbstractLlmOperations.kt:255
- Members sharing a duplicated core (4 members, 50+ identical tokens) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt:153
- Members sharing a duplicated core (4 members, 50+ identical tokens) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/NamedEntityDataRepository.kt:183
- Edited copy of a member (21 corresponding lines) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/tools/CoreSearchTools.kt:88
- Edited copy of a member (21 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-byok-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/byok/CredentialEndpointConfig.kt:138
- Edited copy of a member (21 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt:72
- Duplicated block (16 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/support/OperationContextDelegate.kt:228
- Duplicated block (16 lines × 2) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/support/AssetViewSearchOperations.kt:71
- Duplicated block (16 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DefaultActionMethodManager.kt:294
- Duplicated block (12 lines × 2) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/ingestion/InMemoryContentChunker.kt:112
- Duplicated block (12 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/streaming/StreamingChatClientOperations.kt:234
- Duplicated block (12 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-gemini-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/gemini/GeminiModelLoader.kt:61
- Hotspot: embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/AgentMetadataReader.kt embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/AgentMetadataReader.kt:140
- Hotspot: embabel-agent-observability/src/main/java/com/embabel/agent/observability/tracing/EmbabelSpanEventListener.java embabel-agent-observability/src/main/java/com/embabel/agent/observability/tracing/EmbabelSpanEventListener.java:105
- REDACTED
- REDACTED
- Edited copy of a member (37 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/AgentMetadataReader.kt:454
- Edited copy of a member (37 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/Blackboard.kt:151
- Edited copy of a member (35 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DefaultActionMethodManager.kt:281
- Edited copy of a member (35 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-dashscope-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/dashscope/DashScopeModelsConfig.kt:147
- Edited copy of a member (22 corresponding lines) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/ingestion/InMemoryContentChunker.kt:111
- Edited copy of a member (22 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/chat/support/console/ChatConsole.kt:34
- Edited copy of a member (26 corresponding lines) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/support/AssetViewSearchOperations.kt:58
- Edited copy of a member (26 corresponding lines) embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/async/McpAsyncPromptFactory.kt:51
- Edited copy of a member (25 corresponding lines) embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:160
- Edited copy of a member (25 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/process/AgentProcessTools.kt:85
- Edited copy of a member (20 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DefaultActionMethodManager.kt:325
- Edited copy of a member (20 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-minimax-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/minimax/MiniMaxModelsConfig.kt:189
- Edited copy of a member (17 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt:127
- Edited copy of a member (17 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/guardrails/llmOperationGuardRails.kt:43
- Edited copy of a member (13 corresponding lines) embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/async/McpAsyncServerStrategy.kt:65
- Edited copy of a member (13 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/loop/streaming/StreamingToolLoop.kt:211
- Duplicated block (20 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/workflow/loop/RepeatUntil.kt:190
- Duplicated block (20 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-dashscope-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/dashscope/DashScopeModelsConfig.kt:156
- Duplicated block (18 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt:426
- Duplicated block (18 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/blackboard/BlackboardTools.kt:112
- Duplicated block (16–17 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/AgentMetadataReader.kt:461
- Duplicated block (16–17 lines × 2) embabel-agent-autoconfigure/embabel-agent-platform-autoconfigure/src/main/java/com/embabel/agent/autoconfigure/platform/QuiteMcpClientAutoConfiguration.java:175
- Duplicated block (17 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt:146
- Duplicated block (17 lines × 2) embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/support/GitHubSkillDefinitionLoader.kt:72
- Duplicated block (14 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt:159
- Duplicated block (14 lines × 2) embabel-agent-autoconfigure/models/embabel-agent-minimax-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/minimax/MiniMaxModelsConfig.kt:195
- Recursive walk over a caller-supplied document has no depth cap embabel-agent-common/embabel-agent-ai/src/main/kotlin/com/embabel/common/ai/converters/jsonSchemaSupport.kt:130
- Recursive walk over a caller-supplied document has no depth cap embabel-agent-common/embabel-agent-ai/src/main/kotlin/com/embabel/common/ai/converters/jsonSchemaSupport.kt:323
- Swallowed exception (empty catch) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/model/NamedEntity.kt:111
- Swallowed exception (empty catch) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/TypeBasedInputSchema.kt:123
- EmbabelSpanEventListener.onProcessEvent (cyclomatic 33) embabel-agent-observability/src/main/java/com/embabel/agent/observability/tracing/EmbabelSpanEventListener.java:105
- LoggingAgenticEventListener.onProcessEvent (cyclomatic 30) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/logging/LoggingAgenticEventListener.kt:311
- FileReadToolsKt.globToRegex (cyclomatic 30) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/file/FileReadTools.kt:320
- AgentMetadataReader.createAgentMetadata (cyclomatic 23) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/AgentMetadataReader.kt:140
- InMemoryContentChunker.splitText (cyclomatic 22) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/ingestion/InMemoryContentChunker.kt:300
- ChatModelObservationFilter.map (cyclomatic 21) embabel-agent-observability/src/main/java/com/embabel/agent/observability/tracing/ChatModelObservationFilter.java:112
- DomainTypeInputSchema.buildParameterSchema (cyclomatic 20) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt:145
- AStarGoapPlanner.planToGoalFrom (cyclomatic 19) embabel-agent-api/src/main/kotlin/com/embabel/plan/goap/astar/AStarGoapPlanner.kt:45
- JavaFormBinder.convertToJavaType (cyclomatic 19) embabel-agent-api/src/main/kotlin/com/embabel/ux/form/FormBinder.kt:192
- SimpleInputSchema.buildParameterSchema (cyclomatic 18) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/Tool.kt:757
- GoapPathToCompletionValidator.validate (cyclomatic 18) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/validation/GoapPathToCompletionValidator.kt:45
- ParallelToolLoop.processToolCalls (cyclomatic 17) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/loop/support/ParallelToolLoop.kt:106
- PromptedQuestionSet.read (cyclomatic 17) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/decision/PromptedQuestionSet.kt:207
- DefaultFormProcessor.convertToControlValue (cyclomatic 16) embabel-agent-api/src/main/kotlin/com/embabel/ux/form/DefaultFormProcessor.kt:162
- InMemoryContentChunker.splitText (cognitive 53) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/ingestion/InMemoryContentChunker.kt:300
- FileReadToolsKt.globToRegex (cognitive 50) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/file/FileReadTools.kt:320
- AgentMetadataReader.createAgentMetadata (cognitive 44) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/AgentMetadataReader.kt:140
- AStarGoapPlanner.planToGoalFrom (cognitive 36) embabel-agent-api/src/main/kotlin/com/embabel/plan/goap/astar/AStarGoapPlanner.kt:45
- TerminalServices.formBindingResponseFromUserInput (cognitive 34) embabel-agent-shell/src/main/kotlin/com/embabel/agent/shell/TerminalServices.kt:143
- ChatModelObservationFilter.map (cognitive 31) embabel-agent-observability/src/main/java/com/embabel/agent/observability/tracing/ChatModelObservationFilter.java:112
- DefaultActionMethodManager.invokeActionMethodKotlinReflect (cognitive 26) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DefaultActionMethodManager.kt:276
- TikaHierarchicalContentReader.discoverFilesRecursive (cognitive 26) embabel-agent-rag/embabel-agent-rag-tika/src/main/kotlin/com/embabel/agent/rag/ingestion/TikaHierarchicalContentReader.kt:355
- EmbabelSpanEventListener.onProcessEvent (cognitive 26) embabel-agent-observability/src/main/java/com/embabel/agent/observability/tracing/EmbabelSpanEventListener.java:105
- JvmType.children (cognitive 25) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/JvmType.kt:108
- DefaultToolLoop.execute (cognitive 25) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/loop/support/DefaultToolLoop.kt:87
- GoapPathToCompletionValidator.validate (cognitive 25) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/validation/GoapPathToCompletionValidator.kt:45
- StateActionMethodManager.invokeStateActionMethodKotlinReflect (cognitive 24) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/StateActionMethodManager.kt:165
- LlmOptions.copyDefault (cognitive 24) embabel-agent-common/embabel-agent-ai/src/main/kotlin/com/embabel/common/ai/model/LlmOptions.kt:435
- Ci.build (cognitive 23) embabel-agent-code/src/main/kotlin/com/embabel/coding/tools/ci/Ci.kt:144
- AgentCardHandlerWebFacade.handleJsonRpc (cognitive 20) embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/server/support/A2AEndpointRegistrar.kt:125
- Factory.fromInstanceKotlin (cognitive 18) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/progressive/UnfoldingTool.kt:477
- Factory.fromInstanceJava (cognitive 18) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/progressive/UnfoldingTool.kt:597
- SpelLogicalExpression.evaluate (cognitive 18) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/expression/spel/SpelLogicalExpression.kt:36
- MarkdownContentParser.parse (cognitive 18) embabel-agent-rag/embabel-agent-rag-tika/src/main/kotlin/com/embabel/agent/rag/ingestion/MarkdownContentParser.kt:33
- InMemoryContentChunker.splitBySentences (cognitive 17) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/ingestion/InMemoryContentChunker.kt:395
- ChatModelObservationFilter.writeJson (cognitive 17) embabel-agent-observability/src/main/java/com/embabel/agent/observability/tracing/ChatModelObservationFilter.java:352
- SimpleAgentProcess.formulateAndExecutePlan (cognitive 16) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/SimpleAgentProcess.kt:130
- NamedEntity.dataDictionaryFromPackages (cognitive 16) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/model/NamedEntity.kt:86
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member pair (84 shared lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/progressive/UnfoldingTool.kt:481
- Near-duplicate member pair (42 shared lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt:145
- Edited copy of a member (50 corresponding lines) embabel-agent-autoconfigure/embabel-agent-platform-autoconfigure/src/main/java/com/embabel/agent/autoconfigure/platform/QuiteMcpClientAutoConfiguration.java:161
- Edited copy of a member (70 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/agentic/playbook/PlaybookTool.kt:146
- Edited copy of a member (62 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/plan/utility/HybridUtilityPlanner.kt:84
- Edited copy of a member (53 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/streaming/StreamingChatClientOperations.kt:343
- Edited copies of one member (4 members, 47+ corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-bedrock-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/bedrock/BedrockModelsConfig.kt:126
- Edited copy of a member (45 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/dsl/TypedAgentScopeBuilder.kt:215
- Edited copy of a member (40 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/agent/AgentTool.kt:56
- Edited copy of a member (38 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/TypeBasedInputSchema.kt:155
- Edited copies of one member (3 members, 27+ corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/blackboard/BlackboardTools.kt:106
- Edited copy of a member (28 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-oci-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/ocigenai/OciGenAiChatModel.kt:114
- Edited copy of a member (31 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/ActionMethodArgumentResolver.kt:154
- Edited copies of one member (3 members, 28+ corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-google-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/googlegenai/GoogleGenAiModelLoader.kt:117
- Edited copy of a member (32 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/agent/DefaultProcessCallbackTools.kt:51
- Edited copy of a member (24 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-google-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/googlegenai/GoogleGenAiModelsConfig.kt:268
- Edited copies of one member (3 members, 30+ corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-anthropic-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/anthropic/AnthropicModelsConfig.kt:131
- Edited copies of one member (4 members, 24+ corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/blackboard/BlackboardTools.kt:81
- Edited copy of a member (27 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-google-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/googlegenai/GoogleGenAiModelsConfig.kt:212
- Edited copy of a member (19 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/support/BranchingAction.kt:89
- Edited copy of a member (23 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/ArtifactSinkingTool.kt:94
- Edited copy of a member (12 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/dsl/TypedAgentScopeBuilder.kt:67
- Edited copies of one member (3 members, 12+ corresponding lines) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/support/InMemoryNamedEntityDataRepository.kt:198
- Edited copies of one member (3 members, 7+ corresponding lines) embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/client/spi/SpringRestClientA2AHttpClient.kt:65
- Edited copies of one member (3 members, 11+ corresponding lines) embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/server/support/AutonomyA2ARequestHandler.kt:346
- Edited copy of a member (16 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/Condition.kt:135
- Edited copies of one member (3 members, 20+ corresponding lines) embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/support/GitHubSkillDefinitionLoader.kt:64
- Edited copy of a member (14 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/ActionContext.kt:168
- Edited copies of one member (3 members, 13+ corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-minimax-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/minimax/MiniMaxModelsConfig.kt:134
- Edited copies of one member (3 members, 15+ corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/ReplanningToolFactory.kt:45
- Edited copies of one member (5 members, 10+ corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/messagePromptBuilders.kt:204
- Edited copies of one member (3 members, 8+ corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-bedrock-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/bedrock/BedrockModelsConfig.kt:300
- Edited copy of a member (6 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/persistence/BlackboardPersistence.kt:126
- Edited copy of a member (5 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/MultimodalContent.kt:108
- Edited copy of a member (3 corresponding lines) embabel-agent-autoconfigure/models/embabel-agent-cloudflare-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/cloudflare/CloudflareModelsConfig.kt:151
- Edited copy of a member (8 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/agentic/playbook/PlaybookTool.kt:259
- Edited copy of a member (7 corresponding lines) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/support/DelegatingCreating.kt:81
- Duplicated block (56 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/progressive/UnfoldingTool.kt:540
- Duplicated block (29 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt:293
- Duplicated block (24–28 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/streaming/StreamingChatClientOperations.kt:413
- Duplicated block (27 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/ConcurrentAgentProcess.kt:60
- Duplicated block (22–23 lines × 4) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/AbstractLlmOperations.kt:261
- Duplicated block (23 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt:192
- Duplicated block (20–22 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt:456
- Duplicated block (18–20 lines × 3) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt:205
- Duplicated block (19–20 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/ChatClientLlmOperations.kt:365
- Duplicated block (19 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/progressive/UnfoldingTool.kt:509
- Duplicated block (17–19 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/file/FileReadTools.kt:64
- Duplicated block (14–16 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/core/Blackboard.kt:157
- Duplicated block (15 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt:184
- Duplicated block (14 lines × 4) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt:211
- Duplicated block (13–14 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/AgentMetadataReader.kt:478
- Duplicated block (12–13 lines × 3) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/ToolLoopLlmOperations.kt:292
- Duplicated block (11–13 lines × 3) embabel-agent-autoconfigure/models/embabel-agent-google-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/googlegenai/GoogleGenAiModelLoader.kt:136
- Duplicated block (12–13 lines × 2) embabel-agent-rag/embabel-agent-rag-tika/src/main/kotlin/com/embabel/agent/rag/ingestion/HtmlContentParser.kt:84
- Duplicated block (10–12 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/blackboard/BlackboardTools.kt:140
- Duplicated block (10–11 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/agent/AgentTool.kt:60
- Duplicated block (11 lines × 2) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/ingestion/InMemoryContentChunker.kt:383
- Duplicated block (9–11 lines × 2) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/support/InMemoryNamedEntityDataRepository.kt:199
- Duplicated block (10 lines × 3) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/ingestion/InMemoryContentChunker.kt:332
- Duplicated block (8–9 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/ChatClientLlmOperations.kt:432
- Duplicated block (8 lines × 4) embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/service/NamedEntityDataRepository.kt:190
- Duplicated block (6 lines × 2) embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/MultimodalContent.kt:175
- One operation mutates 2 aggregates: PersistentAgentProcessRepository.delete embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/persistence/PersistentAgentProcessRepository.kt:78
- One operation mutates 3 aggregates: AbstractChunkingContentElementRepository.writeAndChunkDocument embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/store/AbstractChunkingContentElementRepository.kt:71
- Third-party script without Subresource Integrity embabel-agent-docs/src/main/asciidoc/docinfo-header.html:4
Minor — 97 finding(s)
- Interpolated log message defeats structured logging embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/Skills.kt:119
- Interpolated log message defeats structured logging embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/Skills.kt:128
- Interpolated log message defeats structured logging embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/Skills.kt:138
- Interpolated log message defeats structured logging embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/Skills.kt:140
- Interpolated log message defeats structured logging embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/Skills.kt:167
- Interpolated log message defeats structured logging embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/Skills.kt:169
- Interpolated log message defeats structured logging embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/Skills.kt:188
- Interpolated log message defeats structured logging embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/Skills.kt:190
- Interpolated log message defeats structured logging embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/script/AbstractContainerSkillScriptExecutionEngine.kt:196
- Interpolated log message defeats structured logging embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/script/AbstractContainerSkillScriptExecutionEngine.kt:282
- Interpolated log message defeats structured logging embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/script/AbstractContainerSkillScriptExecutionEngine.kt:299
- Interpolated log message defeats structured logging embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/script/AbstractContainerSkillScriptExecutionEngine.kt:302
- Interpolated log message defeats structured logging embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/script/AbstractContainerSkillScriptExecutionEngine.kt:533
- Interpolated log message defeats structured logging embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/script/AbstractContainerSkillScriptExecutionEngine.kt:574
- Interpolated log message defeats structured logging embabel-agent-shell/src/main/kotlin/com/embabel/agent/shell/ShellCommands.kt:430
- Interpolated log message defeats structured logging embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:72
- Interpolated log message defeats structured logging embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:118
- Interpolated log message defeats structured logging embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:144
- Interpolated log message defeats structured logging embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:147
- Interpolated log message defeats structured logging embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:176
- Interpolated log message defeats structured logging embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:179
- Interpolated log message defeats structured logging embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:208
- Interpolated log message defeats structured logging embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:211
- Interpolated log message defeats structured logging embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/sync/McpServerStrategy.kt:72
- Interpolated log message defeats structured logging embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/async/McpAsyncServerStrategy.kt:72
- Duplicated predicate embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/Aggregation.kt:45
- Duplicated predicate embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/decision/LlmDecisionService.kt:152
- Duplicated predicate embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/MethodToolFactory.kt:124
- Duplicated predicate embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/persistence/AgentProcessSnapshotFactory.kt:40
- Duplicated predicate embabel-agent-common/embabel-agent-ai/src/main/kotlin/com/embabel/common/ai/classification/ClassificationResult.kt:178
- Duplicated predicate embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/support/OperationContextDelegate.kt:172
- Duplicated predicate embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/MultimodalContent.kt:166
- Duplicated predicate embabel-agent-common/embabel-agent-ai/src/main/kotlin/com/embabel/common/ai/model/TransportFailureDiagnostics.kt:83
- Duplicated predicate embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DefaultActionMethodManager.kt:293
- Duplicated predicate embabel-agent-api/src/main/kotlin/com/embabel/agent/core/JvmType.kt:331
- Duplicated predicate embabel-agent-api/src/main/kotlin/com/embabel/agent/core/JvmType.kt:333
- Duplicated predicate embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/MultimodalContent.kt:111
- Duplicated predicate embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/MultimodalContent.kt:172
- Duplicated predicate embabel-agent-api/src/main/kotlin/com/embabel/agent/api/tool/DomainTypeInputSchema.kt:184
- Duplicated predicate embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/workflow/loop/RepeatUntil.kt:134
- Diagnostic log message is built whether or not it is wanted embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/EmbeddingSkillSelector.kt:85
- Diagnostic log message is built whether or not it is wanted embabel-agent-skills/src/main/kotlin/com/embabel/agent/skills/script/AbstractContainerSkillScriptExecutionEngine.kt:176
- Diagnostic log message is built whether or not it is wanted embabel-agent-mcp/embabel-agent-mcpserver/src/main/kotlin/com/embabel/agent/mcpserver/AbstractMcpServerConfiguration.kt:112
- Diagnostic log message is built whether or not it is wanted embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/validation/GoapPathToCompletionValidator.kt:157
- Diagnostic log message is built whether or not it is wanted embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/loop/support/DefaultToolLoop.kt:141
- Diagnostic log message is built whether or not it is wanted embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/config/spring/ToolGroupsConfiguration.kt:121
- Diagnostic log message is built whether or not it is wanted embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/config/spring/ToolGroupsConfiguration.kt:195
- Diagnostic log message is built whether or not it is wanted embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/config/spring/ToolGroupsConfiguration.kt:230
- Diagnostic log message is built whether or not it is wanted embabel-agent-api/src/main/kotlin/com/embabel/agent/core/Agent.kt:152
- Diagnostic log message is built whether or not it is wanted embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/BlackboardWorldStateDeterminer.kt:118
- Diagnostic log message is built whether or not it is wanted embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/BlackboardWorldStateDeterminer.kt:155
- Diagnostic log message is built whether or not it is wanted embabel-agent-api/src/main/kotlin/com/embabel/agent/core/support/BlackboardWorldStateDeterminer.kt:167
- Diagnostic log message is built whether or not it is wanted embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/autonomy/Autonomy.kt:177
- Diagnostic log message is built whether or not it is wanted embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/autonomy/Autonomy.kt:315
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- Off-boarding risk: anonymized user #4
- Off-boarding risk: anonymized user #5
- Off-boarding risk: anonymized user #6
- Off-boarding risk: anonymized user #7
- Orphaned file embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/UnsupportedRequestParameterRetry.kt:1
- Orphaned file embabel-agent-autoconfigure/models/embabel-agent-oci-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/ocigenai/OciGenAiEmbeddingModel.kt:1
- Orphaned file embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/DuplicateParameterTypeException.kt:1
- Orphaned file embabel-agent-autoconfigure/models/embabel-agent-oci-genai-autoconfigure/src/main/kotlin/com/embabel/agent/config/models/ocigenai/OciGenAiModelLoader.kt:1
- Orphaned file embabel-agent-autoconfigure/models/embabel-agent-oci-genai-autoconfigure/src/main/java/com/embabel/agent/autoconfigure/models/ocigenai/OciGenAiEnvironmentPostProcessor.java:1
- Silent fallback default in catch embabel-agent-api/src/main/kotlin/com/embabel/agent/tools/blackboard/BlackboardTools.kt:221
- Silent fallback default in catch embabel-agent-rag/embabel-agent-rag-core/src/main/kotlin/com/embabel/agent/rag/filter/InMemoryPropertyFilter.kt:146
- Further sole-owners (lower concentration)
- No ADRs found pom.xml:224
- Projects may be oversized for their cohesion
- High interface indirection
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No dependency-update automation embabel-agent-docs/package.json:5
- No changelog
- Silent fallback default on parse failure embabel-agent-api/src/main/kotlin/com/embabel/agent/spi/support/springai/SpringAiToolExtractor.kt:35
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-558a4a903ff64e2f8baa829740ecb875/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-558a4a903ff64e2f8baa829740ecb875/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 34 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 67 file(s) — `embabel-agent-a2a/src/main/kotlin/com/embabel/agent/a2a/client/A2AHttpClientFactory.kt`, `embabel-agent-api/src/main/kotlin/com/embabel/agent/api/annotation/support/MethodDefinedOperationNameGenerator.kt`, `embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/InteractionId.kt`, `embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/StuckHandler.kt`, `embabel-agent-api/src/main/kotlin/com/embabel/agent/api/common/Transformation.kt`, … (+62 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |