uml-use-case-diagramlisted

# UML Use Case Diagram ## Core behavior Generate, review, refactor, or validate UML Use Case Diagrams in PlantUML for any project domain. Use two inputs when available: 1. A verbal model of the system. 2. A PlantUML Domain Model used only as conceptual vocabulary. Treat the verbal model as the primary source of functional requirements. Treat the Domain Model as controlled vocabulary for terminology, traceability, and ambiguity reduction. Never copy classes, attributes, internal associations, or persistence structure into the use case diagram. A use case diagram shows what external actors want to accomplish with the system. It must not show a step-by-step workflow, algorithm, internal validation chain, UI interaction, database operation, architecture, or implementation design. For detailed review guidance, consult `references/use-case-diagram-rubric.md`. For standards and source alignment, consult `references/standards-alignment.md`. For recurring mistakes, consult `references/anti-patterns.md`. For cross-domain examples, consult `references/regression-examples.md`. ## Nature and purpose: the diagram is a summary, the text carries the weight A use case diagram is a **lightweight visual summary — a table of contents of the actor goals** the system supports. Its job is to show, at a glance, who the actors are, where the system boundary is, and which goals live inside it. The substantive content of use case analysis lives in the **textual use case specifications** (trigg