Skip to content

UML Views

UML behavioral diagrams in this baseline are split by concern. Sequence and component diagrams that explain a specific concept live in the relevant Concepts pages; this page collects the high-level cross-cutting views. Specific diagrams are embedded in:

Sequence — Task Dispatch

The sequence diagram follows PlantUML conventions: actors and participants are declared with actor, participant, and database; solid arrows (->) show requests and dotted arrows (-->) show returns; the order of declaration controls left-to-right layout; and the diagram reads top-to-bottom [PlantUML, 2025].

The flow maps the baseline runtime concepts: the User submits a task to the Orchestrator, which reads context from Memory and dispatches a subtask to Agent A. Agent A invokes the Tool Bus, receives a result, writes an artifact to Memory, and returns a partial result. The Orchestrator then sends the artifact to Agent B for verification/critique; Agent B reads the artifact from Memory and reports the quality-gate result. The Orchestrator stores the final result and delivers the artifact back to the User. This pattern separates execution from verification and treats artifacts as objects that flow between tasks.

Activity diagrams embedded in the Concepts pages use the newer PlantUML beta syntax (start, :action;, if/then/else/endif, repeat, fork, stop) to model workflows, branching, and loops [PlantUML, 2025].

KrokiKroki