Quartz framework overview illustration prompt

Create a clean 16:9 editorial architecture illustration for a Chinese source-analysis article about Quartz Scheduler. The illustration must summarize the complete framework, not one Cron expression or one API call.

Composition:

• Left: a Java host application defining Jobs, Triggers, Calendars and listeners through the public Scheduler API.
• Center: the Quartz runtime in five visible layers: StdSchedulerFactory assembly, QuartzScheduler lifecycle, QuartzSchedulerThread timing coordinator, JobRunShell execution boundary, and pluggable JobStore plus ThreadPool SPI.
• Bottom center: two alternative state paths. One is RAMJobStore inside a single JVM. The other is JDBC JobStore backed by QRTZ tables, database locks, fired-trigger records, misfire handling, scheduler check-ins and cluster recovery.
• Right: a fixed worker pool executing Job.execute, with jobs connecting to generic business databases, HTTP APIs and files.
• Top/right boundary: optional plugins, Job/Trigger/Scheduler listeners, JMX and RMI. Show external systems as optional borders rather than core services.
• Directional flow: application registers Job plus Trigger; JobStore returns an acquired Trigger; QuartzSchedulerThread waits for its fire time; JobRunShell creates and executes the Job; completion updates Trigger and JobStore state.
• Make three state checkpoints readable: WAITING to ACQUIRED, ACQUIRED to EXECUTING, and completion back to WAITING or to COMPLETE/ERROR.

Visual style:

• Professional but approachable technical editorial diagram, deep blue and amber accents on an off-white background.
• Strong spatial hierarchy, restrained labels and generous whitespace.
• Use Chinese labels for major responsibilities and actual English identifiers only where they are Quartz concepts: Scheduler, Trigger, Job, JobStore, ThreadPool, JobRunShell, RAM, JDBC.
• No fake admin console, no code screenshots, no cloud-provider imagery, no invented metrics and no third-party logos.
• The generated image is conceptual. Exact module dependencies, startup order and execution sequence remain in Mermaid diagrams backed by the fixed source commit.