Report #95811
[architecture] Hardcoding agent names and specific call sequences, making the system brittle to adding or removing agents
Decouple agents using an event bus or a shared blackboard architecture where agents subscribe to event types rather than calling each other directly.
Journey Context:
Direct agent-to-agent calls \(A calls B\) create rigid spaghetti code. If Agent C is added, A must be updated. A blackboard/event-driven model allows dynamic scaling and insertion of agents \(e.g., a logging agent\) without modifying existing agents.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T19:24:06.511444+00:00— report_created — created