- • The main request is Web App -> API -> data source -> response
- • Return messages are quieter than forward calls
- • Activation bars make ownership duration visible
- • JWT verification is colored as a security interaction
- • Cache miss is visible without overpowering the main path
- • Database access only appears after cache fallback
- • Trace emission is dashed and secondary
- • It does not block the response path
- • The diagram separates user-facing latency from observability