Architecture

Documentation Index

Fetch the complete documentation index at: https://lab.pollack.ai/llms.txt

Use this file to discover all available pages before exploring further.

​

Module Structure

bud/
├── bud-core          Pure Java library (zero Spring dependencies)
├── bud-mcp-server    Spring Boot app with @McpTool annotations
└── bud-acp-server    ACP agent — LLM classification + orchestration

​

bud-core

• TemplateExtractor — Extracts reference projects from classpath using JDK ClassLoader + manifest files
• PomMutator — Read/write Maven POM files (add/remove dependencies, set versions, add plugins)
• JavaParserRefactor — AST-based package rename for extracted projects
• RecipeCatalog — Composable recipes (actuator, security, CI, native image, etc.)
• StartersCatalog — Searchable index of Spring Boot starters
• BootProjectAnalyzer — Analyze existing projects for dependencies, structure, test strategy
• BudWorkflow — Full pipeline orchestrator: normalize → classify → resolve → plan → execute → recipes → explain
• ExecutionPlanner — Routes resolved intents to CACHE, INITIALIZR, or EXPAND tiers
• TemplateSemanticCache — Subset-matching cache: intent capabilities ⊆ reference project capabilities

​

bud-mcp-server

​

bud-acp-server

• Classifier (Sonnet via your approved CLI, ~$0.01/call) — Analyzes prompts via structured output JSON schema. Extracts capabilities, domain entities, best-fit reference project, and overlay level.
• Expander (Sonnet via your approved CLI, ~$0.19/call) — Generates domain-specific code for EXPAND-tier requests. Only invoked for business domain prompts.

​

Three-Tier Routing

"create a greeting api"           → CACHE (spring-boot-rest reference project)
"spring boot app with Gradle"     → INITIALIZR (start.spring.io)
"build a customer management app" → EXPAND (reference project + AI domain code gen)

​

Protocol Stack

┌─────────────────────────────────────┐
│  JetBrains IDE (AI Chat)            │
│  ← ACP protocol (stdio NDJSON)   → │
├─────────────────────────────────────┤
│  BudAgent (@AcpAgent)               │
│  ← BudWorkflow pipeline →          │
├─────────────────────────────────────┤
│  LlmIntentClassifier (Sonnet)       │
│  ← AgentClient SDK →               │
├─────────────────────────────────────┤
│  Your Approved CLI (Expander)       │
│  ← MCP protocol (stdio JSON-RPC) → │
├─────────────────────────────────────┤
│  Bud MCP Server (23 tools)          │
│  ← Java method calls →              │
├─────────────────────────────────────┤
│  bud-core (pure Java)               │
└─────────────────────────────────────┘

1. ACP — IDE ↔ BudAgent (session management, prompt/response)
2. MCP — Claude Code ↔ Bud MCP Server (tool discovery, tool invocation)

​

Enterprise Model

• No API key — Bud delegates all LLM calls to your enterprise-approved agentic CLI (Claude Code, Gemini CLI, Codex, etc.)
• No billing exposure — the CLI handles authentication and billing
• No compliance review — your IT department already approved the CLI
• Swap providers freely — change your CLI, Bud keeps working. No vendor lock-in on the AI side.
• Deterministic tools — the 23 MCP tools don’t call any LLM; scaffolding is pure code operations

​

Key Dependencies