Draw an AOA Network Diagram Representing the Project CI/CD

Tech architecture infographic titled "CI/CD Pipeline Stages" using archetype HOW-IT-WORKS. Show a left-to-right staged delivery workflow for software changes with labeled boxes and directional arrows. Include these components as clean vector boxes with small icons, canonical English names, and one-line English role descriptions: Developer Workstation — creates code changes and pipeline triggers; Git Repository — stores source code and branch history; CI Orchestrator — detects commits and coordinates automated jobs; Build Runner — compiles source and packages artifacts; Test Suite — runs unit, integration, and static analysis checks; Artifact Repository — stores versioned build outputs; CD Orchestrator — promotes approved artifacts through environments; Staging Environment — validates release candidates in production-like conditions; Approval Gate — manual or policy-based release decision; Production Environment — serves live application traffic; Monitoring Dashboard — tracks deployment health and rollback signals; Notification Service — sends pipeline status updates. Connect all boxes with arrows showing real flow direction and short English labels on each arrow: Developer Workstation to Git Repository 'git push commit'; Git Repository to CI Orchestrator 'webhook over HTTPS'; CI Orchestrator to Build Runner 'job spec'; Build Runner to Test Suite 'build artifact'; Test Suite to CI Orchestrator 'pass/fail status'; Build Runner to Artifact Repository 'versioned package'; Artifact Repository to CD Orchestrator 'fetch artifact'; CD Orchestrator to Staging Environment 'deploy via HTTPS/SSH'; Staging Environment to Approval Gate 'validation results'; Approval Gate to CD Orchestrator 'approved release'; CD Orchestrator to Production Environment 'rolling deployment'; Production Environment to Monitoring Dashboard 'metrics and logs'; Monitoring Dashboard to CD Orchestrator 'rollback signal'; CI Orchestrator and CD Orchestrator to Notification Service 'pipeline event'. Add subtle supporting infrastructure boxes to satisfy architecture expectations: Web UI / Browser — views pipeline runs and logs; Pipeline API — serves run metadata and controls; Metadata DB — stores pipeline state and history; Build Cache — accelerates dependency reuse; Job Queue — buffers pending pipeline tasks. Connect them accurately: Browser to Pipeline API 'HTTPS request'; Pipeline API to Metadata DB 'read/write run state'; CI Orchestrator to Job Queue 'enqueue job'; Job Queue to Build Runner 'dequeue task'; Build Runner to Build Cache 'restore/save cache'; Browser to Monitoring Dashboard 'HTTPS dashboard'. Add a numbered legend 1-7 in English walking through lifecycle: 1. Developer pushes code to the Git Repository. 2. A webhook over HTTPS triggers the CI Orchestrator. 3. Build Runner compiles code, restores cache, and produces artifacts. 4. Test Suite executes automated checks and returns pass or fail status. 5. Successful outputs are stored in the Artifact Repository with a version tag. 6. CD Orchestrator deploys the approved artifact to Staging, then after Approval Gate to Production. 7. Monitoring Dashboard observes health metrics and can trigger rollback actions, while Notification Service reports outcomes. Composition should feel like a project-planning network view inspired by AOA network diagram structure, but still technically accurate as a CI/CD architecture infographic with boxes and arrows. Visual style: retro 1980s computing, blueprint cyan palette, glowing cyan linework on dark blueprint background, grid paper texture, CRT-inspired highlights, precise drafting marks, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Mood: technical, methodical, architect-grade, schematic not marketing, clearly not an audited reference architecture. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real cloud-vendor logos (AWS, GCP, Azure) beyond generic cloud icons. Common protocol names (HTTPS, TCP, JWT, OAuth, REST, GraphQL) stay in canonical English form. No security-claim overstatements (do not present diagrams as audited reference architectures).