LumaCogent Returns Suite — Phase 3 Technical Architecture
System Interaction Diagram
All components across four layers with directed, typed arrows — event bus as central nervous system
DocumentSystem Interaction Diagram V1
OwnerSolutions Architect
StatusIn Review
Architecture RefTechnical Architecture V2
Date2026-04-30
Interaction Type Key
Event (SQS)— async message published to or consumed from the event bus
API Call— synchronous REST call to or from an external system
OI Core Query— synchronous agent → OI Core context fetch (<500ms SLA)
Proactive Signal— OI Core → agent mesh (ANOMALY_DETECTED, RMA_STALL_RISK, etc.)
Tool Invocation— agent → capability layer service (code-level enforced via tool access registry)
Learning Signal— human override captured by Learning Agent → OI Core learning pipeline
Full System Interaction Map — V2 Architecture
All layers, all components, all interaction types. Arrows are directed. SQS is the central nervous system — all capability layer services publish here; all agents and OI Core subscribe.
Changelog
Date
Update
2026-04-30
V1 created — system interaction diagram produced from V2 Technical Architecture (agent-first, OI Core-driven). Shows all four layers, SQS event bus as central nervous system, eight agents, six OI Core subsystems, nine capability layer services, five Human Interface components, and six external system groups. All interaction types typed and directed: event, API call, OI Core query, proactive signal, tool invocation, learning signal. Callouts: agent runtime cycle and authority boundary enforcement.