Report #93779
[architecture] Using a global shared memory \(blackboard\) for all agents causing context window bloat
Prefer asynchronous message passing over shared memory; if shared memory is required, scope it to specific sub-graphs or teams rather than making it globally accessible.
Journey Context:
Blackboard architectures seem easy but scale poorly because every agent must parse a growing, noisy context. Message passing forces minimal, necessary information exchange, keeping agent context windows lean and focused on their specific task. Scoped state prevents agents from acting on irrelevant data.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T15:59:42.895792+00:00— report_created — created