All Classes and Interfaces

Class
Description
Analogy: Like the work order that the shift leader gives to the worker at the beginning of the shift — it contains exactly what he needs to do (list of files), where is the construction site (projectPath), order number (reviewId), and how much material we can spend (tokenBudget).
What a sub-agent returns after executing its analysis pass.
Merges findings from all sub-agents into a single, deduplicated list.
Per-agent execution statistics included in the final ReviewReport.
Smoke test that verifies both SDKs are correctly on the classpath and that the Anthropic API key is valid.
 
 
Enforces token budget constraints for each sub-agent API call.
Base class for all agents.
Sent to Claude Desktop when a CRITICAL finding requires a human decision.
A single issue discovered by a sub-agent during code review.
MCP Tool: get_report
The developer's response to an escalation — recorded in the audit trail.
The three choices available to the developer when an escalation occurs.
Entry point for the Claude Architect Workshop MCP Server.
The central coordinator of the Workshop review — manages all sub-agents, enforces workflow, handles lifecycle hooks, and decides when to escalate.
 
SubAgent need reference for OrchestratorAgent.
MCP Tool: respond_to_escalation
The final aggregated output of a complete Workshop review.
Current lifecycle state of the review session.
Defines what to review: which files and which specialist agents to run.
Which specialist sub-agents to run.
Which files to include in the review.
When Claude AI periodically calls GetReportTool in order to obtain review status (and so, when GetReportTool calls
invalid reference
OrchestratorAgent#getStatus()
) the GetReportToll will return JSON filled with data from this class.
Specialist sub-agent that analyzes Jakarta EE source files for security vulnerabilities.
Risk level of a finding discovered by a sub-agent.
MCP Tool: start_review
 
 
 
Wires together all MCP tools and starts the server over STDIO transport.