Report #13550
[architecture] Context divergence when agents operate on stale snapshots of shared state
Use an append-only shared blackboard or event stream for shared facts, rather than synchronizing full state copies. Agents read from the blackboard and append updates, ensuring they see the chronological history of state changes.
Journey Context:
Passing full state copies between agents on every handoff is expensive \(token cost\) and quickly becomes stale if agents run in parallel. If Agent A and Agent B both hold a copy of the user profile and update it independently, merging is a nightmare. Instead, use a Blackboard architecture \(or event sourcing\). Agents maintain their own private scratchpads but read from and write to a centralized, append-only shared memory. This ensures all agents have access to the latest facts without requiring complex distributed locking or state diffing.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T19:08:37.392261+00:00— report_created — created