TCP Three-Way Handshake Tech Architecture Infographic

Tech architecture infographic titled "TCP Three-Way Handshake" using PROTOCOL HANDSHAKE archetype, optimized for architect / staff audience. Show a precise client-to-server TCP connection establishment sequence as a clean numbered exchange diagram with two main vertical endpoints and supporting labeled infrastructure boxes. Layout: left side Client Host, right side Server Host, with directional arrows crossing horizontally between them. Add surrounding contextual boxes in a subtle generic network frame to satisfy architecture-diagram expectations: Client Application, TCP/IP Stack, Network Path / Internet, Server TCP Listener, Application Service. Render labeled BOXES for each component, each with an icon, a canonical English name, and a one-line role description in English. Example box content: "Client Application — Initiates outbound TCP connection", "TCP/IP Stack — Builds and processes TCP segments", "Network Path — Routes packets between hosts", "Server TCP Listener — Accepts inbound TCP connection requests", "Application Service — Receives established socket connection". Connect boxes with ARROWS showing data direction and sequence. Main handshake arrows must be technically accurate and prominently numbered: 1) Client to Server labeled "TCP SYN, Seq=x, dst port"; 2) Server to Client labeled "TCP SYN-ACK, Seq=y, Ack=x+1"; 3) Client to Server labeled "TCP ACK, Seq=x+1, Ack=y+1". After the third exchange, add a state transition arrow or caption labeled "Connection established". Include small state labels near endpoints in English: Client states "CLOSED → SYN-SENT → ESTABLISHED" and Server states "LISTEN → SYN-RECEIVED → ESTABLISHED". Add optional lower secondary arrows in muted style for post-handshake data flow labeled "TCP payload data" in both directions. Avoid incorrect protocol mixing: no HTTPS, no JWT, no REST, no database writes. This is pure TCP transport-layer handshake. Add packet-level annotations in compact callouts: "Flags: SYN", "Flags: SYN, ACK", "Flags: ACK", and "3-way handshake over TCP". Include subtle note box: "Illustrative reference diagram, not an audited security architecture". Add a numbered legend (1-7) walking through the request lifecycle IN English: 1. Client opens a socket and selects an ephemeral source port. 2. Client sends a TCP SYN segment to the server destination port. 3. Network path forwards the SYN toward the listening server. 4. Server in LISTEN state replies with SYN-ACK and allocates half-open connection state. 5. Client validates the SYN-ACK and returns ACK. 6. Both endpoints transition to ESTABLISHED after sequence numbers are synchronized. 7. Application data can now flow over the TCP connection until teardown. Visual style: cyberpunk neon with warm beige & navy palette, glowing edge highlights, dark navy background, warm beige panel fills, neon cyan and magenta accent lines used sparingly, high contrast for readability, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use generic cloud/network icons only, no vendor branding. 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).