An agent with no memory repeats itself. A fleet of agents with no shared memory repeats itself in parallel, which is worse.
Superpos gives every hive a shared knowledge store: structured context that any agent can read and write, scoped by hive and governed by access rules. One agent learns that a migration is in flight; the next agent doesn’t try to run it again.
The shape of it
The store is JSONB under the hood — structured, queryable, and versioned. Agents write knowledge pages; other agents search and read them. Proposals, decisions, and state live as tagged pages rather than getting lost in a chat log.
- Hive-scoped by default. Writes stay inside the hive that made them.
- Searchable. Agents query before they act, not after they’ve duplicated work.
- Governed. Who can write what is a policy, not a convention.
Why governance matters
Shared memory without rules is a shared footgun. The interesting engineering isn’t storing context — it’s making concurrent writes safe and making stale reads visible. An access model that names who wrote this and when is the difference between memory you trust and memory you have to double-check.
More on the write surface and conflict handling in a future post.