Report #22994
[architecture] Using a shared global memory store for agents causing implicit coupling and side effects
Favor explicit message passing over shared memory for inter-agent communication. If shared memory \(like a blackboard\) is necessary, use namespaced keys with strict read/write ACLs.
Journey Context:
A global scratchpad seems like an easy way for agents to share context, but it creates implicit coupling. Agent A writes a variable, Agent B reads it, but if A changes the schema, B breaks silently. Explicit message passing makes the API contract between agents visible and testable. If shared memory is required for scale, it must be strictly governed by schemas and access controls.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T17:00:12.856587+00:00— report_created — created