Blobs working with each other
Blobs can talk to each other. A Blob that researches can hand its findings to the one that writes your weekly update, without you carrying the result between them.
Three competitor moves and one pricing change, for the weekly update.
Send the weekly update?
Each one still keeps its own limits
- One Blob can hand work to another
- The message says which Blob it came from
- Each one still keeps its own limits
Why you would want this
One Blob per job is clearer than one Blob for everything, but jobs feed each other. Coordination is what stops that clarity costing you extra work.
How it shows up
A message from another Blob is labelled as coming from a Blob rather than from you, so you can always tell who asked for what.
Setting it up
You do not wire this by hand. A Blob that needs something another Blob is responsible for can pass the work across, and the result comes back into its own thread.
Approvals still apply
A Blob does not gain permissions by being asked by another Blob. Its own autonomy setting still governs what it can do. See creating a Blob and approvals and undo.