Implementation
Implementation Notes for Isolating Agent Scratch Space From Shared State
Agents need somewhere to think, and giving them scratch space that cannot leak into shared state keeps drafts from being mistaken for decisions.
Half-finished reasoning looks exactly like finished reasoning to a downstream reader. The fix is structural: drafts live where only their author can see them.
Isolation mechanics
- Scratch namespaces are per-agent and excluded from workflow reads.
- Promotion to shared state is an explicit, validated, audited write.
- Scratch content expires with the task instead of accumulating.
Use the blackboard schema, architecture guide, and examples to keep drafts from ever being read as decisions.