patternspandemic

I think `herd` works well.

Thanks for the info. I believe I've found a solution that will work for me given the backend I plan to use.

I like this. I'd assume any non-isolated component could still initialize a memory (not just the bot/main component). That way everything's still handled by the responsible component. With this, one...

> there are no way to reference another component: ... I see. Then having multiple named shared memories seems like a simple solution that requires only a little more thought...

Another (perhaps common) use case I've come across where inter-component memory sharing is required is with OAuth type scenarios. When looking to use various Web APIs which require authorization, access...

FYI, if anyone else is manually setting `component_id` on components to achieve inter-component memory sharing, _note_ that only one component may initialize (prepare) memories. Namely, the [first component to register...

> I don't think messing around with other components' memories is a good idea, because there is no dependency management and a component should be able to manage its memory...

Sure. Looks to be a global memory with named access to 'buckets' for organization? Works for me, I think as long as any component can initialize memories to any bucket.

I see how a global bucket wouldn't be necessary if any component could ask for a named bucket from `shared` by name. I like the idea of naming it clearly...

I like this! I am excited to see this and keyboards in 0.3 target!